FME can read and write CIM XML (CIMXML) files conforming to the Common Information Model (CIM) family of standards:
-
IEC 61970 (transmission and energy management),
-
IEC 61968 (distribution), and
-
IEC 62325 (energy markets).
The reader and writer derive their schema from user-supplied Resource Description Framework Schema (RDFS) profile files, so any CIM profile that follows the standard CIM RDFS conventions is supported, including ENTSO-E CGMES, EPRI GMDM, and vendor extensions on top of standard CIM.
The Common Information Model itself is defined in IEC 61970-301. CIMXML is a constrained profile of W3C RDF/XML, with conventions specified by the International Electrotechnical Commission (IEC) 61970-552 (CIMXML Model exchange format). CIMXML instance data omits primitive data types, so the RDFS files are the sole source of truth for attribute types (for example, whether Conductor.length is a float, an integer, or a string); the reader and writer derive the necessary XSDs from the RDFS so FME features carry correctly typed attributes.
Product and System Requirements
|
Format |
FME Platform |
Operating System |
||||
|---|---|---|---|---|---|---|
|
Reader/Writer |
FME Form |
FME Flow |
FME Flow Hosted |
Windows 64-bit |
Linux |
Mac |
|
Reader |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
|
Writer |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Reader Overview
The CIM RDF reader accepts a single CIMXML file and a list of RDFS schema files describing the CIM profile in use. At translation time, the reader processes the RDFS files into a set of XSDs and delegates the actual XML parsing to the XSD-Driven-XML reader. Each CIM class element in the input file produces one FME feature, with attributes typed according to the RDFS profile.
Real CIM profiles are typically distributed across multiple RDFS files (for example, the GMDM profile is six files; CGMES bundles may be more). The reader accepts a list of RDFS files and accumulates classes and properties from all of them before resolving cross-references.
Writer Overview
The CIM RDF writer accepts FME features and produces a CIMXML file conforming to the user-supplied RDFS profile. The writer uses the same RDFS-to-XSD schema pipeline as the reader, ensuring symmetric typing on read and write. The output is a single <rdf:RDF> document with each FME feature written as a child CIM resource.
The writer's destination feature types are derived from the RDFS files automatically. Users select the RDFS files in the writer's parameters; when the destination is added to a workspace, the feature types appear pre-populated and cannot be edited ad-hoc. This ensures the written output conforms to the declared profile.