INTRODUCTION
Electrical design teams often lose time reconciling product properties that have been typed into drawings, schedules and parts lists more than once. A change to one device can leave mismatched descriptions or symbols in another part of the project. The EPLAN Data Portal gives designers access to manufacturer-supplied component records that can be brought into an EPLAN project. For CHINT products, the workflow can begin with a search by manufacturer or part number, continue through record review and schematic placement, and extend to panel layout when the selected record includes the needed graphics or macro data. The amount of information varies by product record, EPLAN version and company setup, so the imported data still needs engineering review before release.
WHAT CHINT DATA CAN DO IN AN EPLAN PROJECT
An EPLAN part record can contain commercial and technical properties, function templates, logic macros, 2D graphics, connection-point patterns, drilling data, 3D graphics or DXF files. A record may include only some of these. The part data stores information associated with a device; a macro supplies a reusable representation or function for placing that device in a schematic or layout. They work together, but they are not interchangeable: a complete-looking part record does not guarantee that a suitable macro or 3D model is available.
CHINT reported more than 30,000 product data entries on the EPLAN platform in October 2026. That platform-wide count spans product categories and does not mean every CHINT device has every data type. The portal is a starting point for engineering documentation, not an approval stamp. Designers remain responsible for checking the selected variant against project requirements and current CHINT product documentation. CHINT describes its EPLAN data offering on its EPLAN product information page.
FIND THE CORRECT CHINT COMPONENT BEFORE IMPORTING
Start with the project specification, one-line diagram and device schedule. Search the portal by CHINT as manufacturer, then narrow the results with a full order number, product name or product group. A family name alone may return several frame sizes, pole configurations, accessory combinations or control variants. Compare the complete designation and the properties that affect the design: rated voltage and current, pole count, trip or coil option, and any required auxiliary devices.
Where the choice affects protection, coordination or physical fit, compare the portal entry with the current CHINT catalog, data sheet or product page. A nearby result is not an acceptable substitute just because its family name is familiar. Check that the record refers to the exact device and accessories selected for the project, and note any differences between the manufacturer's published values and the project schedule before importing it.
IMPORT A SINGLE PART OR BUILD A BATCH DOWNLOAD
For a single device, open the Data Portal through the EPLAN Platform, find the exact manufacturer record and use the available import command. The current EPLAN FAQ describes importing an individual part through the portal connection in the platform. If several components are needed, use the portal's selection or download options supported by the installed release and account. Access and download conditions can vary with the EPLAN service agreement and platform version; check the current requirements for the specific installation rather than relying on an older menu description.
An EDZ file is an EPLAN exchange package for parts data and associated content. When a project team receives an EDZ package, import it through the applicable parts-management import workflow, review the import options, and confirm the resulting record in Parts Management. Where the workflow offers choices such as adding new records or updating existing ones, check the target database and the effect on existing data first. Back up a production parts database before a bulk update. EPLAN’s current Data Portal guidance and EDZ FAQ describe the portal and import routes; menu labels can differ between releases.
REVIEW THE PART RECORD IN PARTS MANAGEMENT
Before using an imported item, inspect it in Parts Management. Confirm the manufacturer, order number, descriptions, technical properties, function templates and links to documentation. Check whether the record represents the base device or a particular accessory package. Look for blank or conflicting fields that could affect a bill of materials, terminal plan or project search. If a required attribute is missing, consult the current product documentation and resolve the value through the team's data-control process rather than filling it from memory.
Also confirm where the record is stored. EPLAN projects may use local or company-managed parts databases, and administrator settings can affect which records are visible to other users. The approved data workflow should preserve the project’s source and revision history so that another designer can identify the exact component record used.
For shared libraries, designate the authoritative database and decide who approves imported records. Internal fields such as stock codes or procurement categories can follow company rules, while manufacturer order numbers and technical values should remain traceable. Keep the source and revision used for the project so later updates can be compared with the released record.
MOVE FROM SCHEMATIC PLACEMENT TO DEVICE NAVIGATOR
Once the part is verified, assign it to the intended function or device in the schematic. Use the symbol or macro provided with that record when it matches the circuit representation and project conventions. Then check that the device appears consistently in the Device Navigator and that the assigned part is attached to the correct function. Function templates may help create or describe connections, but their presence and detail depend on the record. Review terminal designations, connection points and any project-specific symbol rules before treating the placement as complete.
Keep the part number aligned across the schematic, navigator and reports. If the record changes, check placed instances rather than assuming every project object has refreshed.
USE AVAILABLE 3D MACROS IN PANEL LAYOUT
Where a selected record includes a 3D macro and the EPLAN installation supports the relevant layout functions, place the device in the layout space and check its orientation, dimensions and mounting position. Use available connection definitions to support routing where those definitions and the project setup allow it. A 3D representation can help reveal space conflicts early, but it is not a substitute for the manufacturer’s dimensional drawing or the panel builder’s clearance, heat and wiring checks.
Confirm that the model matches the schematic variant and accessories. Verify terminal locations, clearances and enclosure fit. If no 3D graphic is provided, do not substitute a similar-looking model; use approved dimensional documentation. Availability remains specific to the selected record.
A layout review should include mounting hardware, rail spacing, cable bend radius, ventilation openings and access to terminals. A 3D macro may show the device envelope without modeling every service clearance. Resolve discrepancies in the project layout before issuing manufacturing documents, and keep the model linked to the same part number used in the schematic.
CARRY COMPONENT INFORMATION INTO PROJECT DOCUMENTATION
EPLAN reports and parts lists can draw on assigned project data, reducing re-entry when records are complete. Before issuing drawings, check report settings, order numbers, descriptions, quantities and procurement fields. Confirm that schematic changes appear in the reports and remove obsolete or duplicate entries.
CHECK THE PROJECT BEFORE DOCUMENT RELEASE
Before release, confirm the device variant, associated record and macro, schematic-to-navigator consistency, panel dimensions and parts list. Compare critical values with current manufacturer documents and record unresolved data gaps.
FREQUENTLY ASKED QUESTIONS
HOW OFTEN IS MANUFACTURER DATA IN THE PORTAL UPDATED?
EPLAN says manufacturers update their parts data continuously. Individual records do not necessarily change on a fixed schedule, so check the latest available revision when preparing a project release and verify critical values against the current CHINT product documentation.
DOES A PORTAL RECORD CONFIRM PRODUCT PRICE OR DELIVERY AVAILABILITY?
No. The portal supports engineering documentation; it is not a quotation or inventory service. Price, regional orderability, stock and delivery timing need confirmation from CHINT or the authorized sales channel for the project.
