Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.

Prev Next

NIEM MPD Generation

Generating the IEPD can be considered an iterative process. You do not have to wait until your NIEM model is complete before you generate an IEPD from it.

Your NIEM MPD diagram should contain an instance specification of a Model Package Description. The MPD instance and its relationships to Conformance Target instances as well as other artifacts, is a representation of the MPD catalog. When you generate an MPD from your model, Enterprise Architect will generate a catalog file and other artifacts, based on the items in your MPD model. It will also generate NIEM schemas for the <<InformationModel>> packages referenced by your model. The result will be a collection of files output into the directory you specify for the generation process.

Steps for generating an MPD




Your NIEM MPD diagram should contain an Instance Specification of a Model Package Description.

Select the MPD instance, either on the diagram or in the Browser window.


Right-click on the MPD instance to open the pop-up menu or go to the 'Specialize' ribbon and select the 'Technologies > NIEM > Generate NIEM Schema' option.

The 'Generate NIEM MPD Schemas' dialog displays.


In the 'Directory' field, type or browse for the directory path into which to generate the MPD.


The 'NIEM Version' field defaults to '4.0'.   If generating a NIEM 3 IEPD, set this field to '3.0'.

The 'MPD Artifacts' panel lists the static MPD Artifacts and common Artifacts (such as Structures and Catalog) used in this model, each with its relative path.

Select or deselect the checkboxes beside these items to generate or skip these items.

The 'Namespace Schema(s)' panel shows the schema files that will be generated for the information models.

Select or deselect the checkbox beside a Namespace Schema to generate or skip that schema.

Select a Namespace Schema to display Package details for that schema.


Click on the Generate button.

Once the generation has completed successfully, clicking the View Schema button opens Windows Explorer, showing the contents of the output directory used for generation. If the Catalog Artifact has been deselected, then clicking the View Schema button will open an editor to view the schema file associated with the currently selected Namespace Package.


  • The output location of the schema file generated for a Package is specified by the 'pathURI' tag value on the Usage connector that relates the Package to the ModelPackageDescription instance specification; default values are set by the Schema Composer when the subset Packages are created, but the values can be overridden by the user