MicroStation: Engineering Content
Bentley Systems introduced Engineering Content with MicroStation CONNECT in 2015. Engineering Content is commonly abbreviated to EC.
EC in MicroStation is Bentley’s framework for attaching rich, structured data to design elements and models. It is built on the EC (Engineering Content) / ECObjects technology and underpins many “intelligent” workflows in the Bentley ecosystem. Below is a management‑level overview focused on what EC is, why it matters, and how it is typically used.
1. What is Engineering Content (EC)?
Engineering Content is a schema‑driven data model that allows you to define and store business information alongside geometry in DGN files. It consists of …
- ECSchemas – Formal definitions of data structures (classes, properties, relationships)
- ECClasses – Types of objects (e.g., “Equipment”, “Pipe”, “Room”, “AssetTag”)
- ECProperties – Attributes on those classes (e.g., SerialNumber, Manufacturer, PressureRating)
- ECInstances – Actual data records attached to elements or models (e.g., “Pump P-101 with SerialNumber=12345”)
In MicroStation, EC is managed by the DgnECManager and stored directly in the DGN file, so the design and its data travel together.
2. Why EC Matters for the Business
2.1 Single Source of Truth
EC allows the design file to become a single source of truth for both geometry and associated engineering data:
- Reduces reliance on disconnected spreadsheets and external databases.
- Minimizes data duplication and manual re‑entry.
- Improves consistency across disciplines and project phases.
2.2 Better Data Quality and Governance
Because EC is schema-based …
- Data structures are explicit and controlled (e.g., required fields, data types)
- Changes to data models can be governed centrally via schemas
- Validation rules can be enforced at the platform level, improving data quality
This supports corporate standards, regulatory compliance, and repeatable workflows.
2.3 Enabling Advanced Workflows
EC is the foundation for many higher-value capabilities …
- Reporting and Quantification – Structured properties enable reliable reports (e.g., equipment lists, cable schedules, room areas)
- Asset and Lifecycle Management – Design data can flow into operations, maintenance, and digital twin environments
- Automation – Scripts and tools can act on EC data to drive geometry, check rules, or generate documentation
- Interoperability – EC schemas can be aligned with industry standards or other Bentley applications, improving data exchange
3. How EC is Used in Practice
3.1 Defining the Data Model (Schemas)
Organizations define ECSchemas that reflect their business objects …
- Example: An “Equipment” base class with properties like SerialNumber and Manufacturer
- Specialized subclasses like “Pump”, “Valve”, “Instrument” inherit from Equipment and add more properties
These schemas can be …
- Developed centrally by BIM/CAD/IT standards teams
- Versioned and reused across projects
- Imported into DGN files so that all users share the same definitions
3.2 Attaching Data to Elements
Designers or automated tools attach ECInstances to elements …
- A line or solid representing a pipe can have a “Pipe” ECInstance with size, material, and specification
- A cell representing a pump can have a “Pump” ECInstance with tag, duty, and vendor information
- A model can have project‑level EC data (e.g., project ID, client, revision)
This is done programmatically via the DgnECManager or through application tools built on top of EC.
3.3 Querying and Reporting
Once EC data is in place, it can be …
- Queried (e.g., “find all Equipment where SerialNumber is not set”)
- Filtered (e.g., “all Pumps with duty > 50 kW”)
- Reported (e.g., equipment lists, room schedules, quantity take‑offs)
This supports QA/QC, design reviews, and downstream deliverables.
4. Governance and Implementation Considerations
4.1 Ownership and Standards
- Assign clear ownership for EC schemas (e.g., BIM manager, data standards team)
- Define naming conventions, versioning, and approval processes for schemas
- Align schemas with corporate standards and, where possible, industry standards
4.2 Integration with Other Systems
Plan how EC data will integrate with …
- Asset management systems (CMMS/EAM)
- Document management and CDE platforms
- Analytics and reporting tools
- Ensure key identifiers (tags, IDs) are consistent across systems
4.3 Change Management and Training
Introduce EC gradually, starting with high-value use cases (e.g., equipment data, room data). Provide training for …
- Designers (how to enter and maintain EC data)
- Power users / developers (how to build tools and reports on EC)
- Monitor adoption and data quality; refine schemas and workflows as needed
5. Strategic Benefits
When implemented well, EC delivers …
- Higher data reliability across the project lifecycle
- Reduced rework and manual data handling
- Better decision support through accurate, queryable information
- Improved handover to operations and digital twins, enabling long‑term asset value
In short, Engineering Content transforms MicroStation from a drawing tool into a data‑centric engineering platform, where geometry and information are tightly integrated and managed.
EC adds non-graphic data to MicroStation objects. You can attach data to a graphic object such as a line element, a DGN model or a DGN file.
What kind of data? Numeric and string data are most common. For example, a line element has a property length, which is available as EC data. A shape that represents a concrete slab might have a density property, taking values 'low', 'medium' or 'high'.
Engineering Content adds potential to DGN files. If DGN elements have EC data, those data can be used in several ways …
- Create labels that show EC data attached to DGN objects
- Create reports about EC data
- Exchange EC data with others apps, such as a database or spreadsheet
EC Schemas
The foundation of Engineering Content is the set of EC Schemas installed with MicroStation.
Bentley Systems Information about EC
I discovered the following by searching for Engineering Content (EC) in Be Communities …
Python Examples
MicroStation Python Examples
There are Python examples that use
DgnElementSetTool
delivered with your MicroStation installation.
You'll
find those examples
in your computer's local drive.
They are likely to be found in this folder …
C:\ProgramData\Bentley\PowerPlatformPython\Examples\Microstation\DgnElements\
LA Solutions Examples
You'll find Python examples written by LA Solutions on these pages, Engineering Content Examples.
Questions
Post questions about MicroStation programming to the MicroStation Programming Forum.
