Capital Harness Designer Modular
Configuring the FEM Task for Map Module Codes
You can use the Module Code Mapping Task flexible execution model (FEM) task to automatically create module designs from module codes.
Prerequisites
You must have configured Capital Integration Server in the capitalintegrationserverconfiguration.xml file in the config directory of your installation. See the “The capitalintegrationserverconfiguration.xml File Format” section in the clientprops.xml File Format topic of the Capital Configuration Files Reference Guide for further information.
Module codes which are already mapped to existing designs are ignored, and the task will create designs for the remaining codes.
Procedure
Open the sample XML file ModuleCodeMappingTask.xml in the doc/webservice/data folder of your Capital installation, or refer to the example file shown below.
Edit the parameters. All parameters are mandatory unless otherwise stated.
Table 37: Description of Parameters Name
Description
ProjectName
The name of the project.
DesignName
The name of the design.
PartNumber
The part number of the design.
RevisionName
The revision name of the design.
ModuleType
Whether the modules are Functional or Production Modules.
Values are:
Functional
Production
DesignAttributeConstraint
The name of the rule defined at project level which will be used to
modify the design attributes. Optional. If this
parameter is not configured then "Auto Map" will be
used. If using "Auto Map", the module code will be used
as the design name/part number.
ReleaseLevel
The draft release level to assign to any designs created
during module code mapping. If there is only one draft
release level defined then this parameter is
optional.
Save the file.
Start the FEM task.
Results
You can monitor the tasks in the Tasks Tab in the Output Window, and access the log files. You can also access the log files in your temp folder.
The following messages may be shown on the Tasks tab of the Capital Harness Designer Modular client.
Table 38: Messages Shown While Executing the FEM Task
Messages
Description
FEM Task {0} started for Project: {1} and Design: {2}:{3}:{4}
{0} FEM task name
{1} Project name
{2} Design name
{3} Part number
{4} Revision name
The FEM task has been initiated.
Project {0} not found
{0} Project name
The project specified in the configuration file cannot be
found.
Design {0}:{1}:{2} not found
{0} Design name
{1} Part number
{2} Revision name
The combination of the design name, part number and revision name
specified in the configuration file cannot be found.
Unable to acquire lock on {0} Design {1}:{2}:{3}, it is currently
locked by {4} since {5}
{0} Design type (e.g. composite)
{1} Design name
{2} Part number
{3} Revision name
{4} User name
{5} Timestamp
The design is locked, and the FEM task has been aborted.
Design {0}:{1}:{2} deleted from project {3}
{0} Design name
{1} Part number
{2} Revision name
{3} Project name
The design was deleted from the project before the FEM task
acquired a lock.
FEM task {0} cannot be performed on design {1}:{2}:{3} as the
release level does not allow edition
{0} FEM task name
{1} Design name
{2} Part number
{3} Revision name
The release level of the design prevents the user from editing it,
and therefore the FEM task cannot be run.
FEM task {0} cannot be performed on design {1}:{2}:{3} as the user
cannot edit the design
{0} FEM task name
{1} Design name
{2} Part number
{3} Revision name
Either the user does not have permission to edit the design, or
the design is assigned to a domain to which the user only has read-only access.
FEM task {0} cannot be performed on inaccessible designs
{0} FEM task name
The design is assigned to a domain where the user does not have
permission to access the design.
FEM task {0} cannot be performed on design {1}:{2}:{3} as no
license is available to open the design
{0} FEM task name
{1} Design name
{2} Part number
{3} Revision name
No license is available to run the action.
FEM task {0} cannot be performed on design {1}:{2}:{3} as the
design cannot be accessed for unspecified reason
{0} FEM task name
{1} Design name
{2} Part number
{3} Revision name
The design is not editable for a reason other than those described
in this table.
Parameter definition is invalid in the parameters file
Some of the parameters are empty or missing in the specified
parameters file.
{0} is not able to process modular designs. Please use Harness
Designer Modular instead
{0} Application name
If the specified design is a modular design, then Capital Harness
Designer Modular must be used to run the FEM task.
Design {0}:{1}:{2} does not contain any data
{0} Design name
{1} Part number
{2} Revision name
There is no data in the specified design.
Harness Design {0} has diagrams with missing style sets
The style sets are missing for one or more of the diagrams in the
design.
Task {0} failed to finish
{0} FEM task name
The FEM task failed or was only partially successful.
Task {0} completed with no errors for Project: {1} and Design:
{2}:{3}:{4}
{0} FEM task name
{1} Project name
{2} Design name
{3} Part number
{4} Revision name
The FEM task completed successfully.
The following messages are specific to the Module Code
Mapping Task.
Table 39: Messages Shown While Running Module Code Mapping by FEM Task Messages
Description
Parameter file not found
The specified parameter file cannot be
found in the doc/webservice/data folder of your
Capital installation.
Design: {0}, Part Number: {1}, Revision:
{2} is a child design. The creation of child design of
an existing child design is not supported
{0} Design name
{1} Part number
{2} Revision
Mapping module codes child designs in
the specified project, design, part number and revision,
would result in the creation of the child design of a
child design, which is not supported.
Task cannot be executed. Codes not
found.
The type of mapping specified does not
match the type of codes in the design, for example, FM
mapping is specified, but the design does not contain
any FM codes.
{0) mapping is defined but {1} codes do not exist on
design {2}
{0} Type of mapping, either Functional
or Production
{1} Module code type, either FM or
PM
{2} Design name
There are no module codes on the design of a type that match the
specified mapping type, for example, Functional mapping
is defined but the design does not contain any FM
codes.
Rule name not found
The specified naming rule cannot be
found.
Mapping cannot be completed. Design
{0}:{1}:{2} already exists
{0} Design name
{1} Part number
{2} Revision
The naming rule results in child design
names which already exist in the design, or a
combination of part number and revision which is not
unique in the database. The task is aborted and no
module codes are mapped to designs.
Multiple draft levels exist in the
project. Specify required parameter.
New module designs are assigned to a
draft release level. If multiple draft release levels
exist in the project, the required release level must be
specified as an optional parameter in the configuration
file.
Release level not found.
The release level specified in the
configuration file cannot be found.
- If the task completes successfully, module codes are mapped to designs named either after the module code, or using the specified design attribute constraint.
Examples
This is an example of the contents of a configuration file.
Copy
<?xml version="1.0" encoding="UTF-8"?>
<FEMParameters>
<!-- Project name -->
<Param name="ProjectName" value="Aerospace Modular"/>
<!-- Design name -->
<Param name="DesignName" value="Aerospace Harness"/>
<!-- Design Part number -->
<Param name="PartNumber" value="AA12346_1"/>
<!-- Design Revision name -->
<Param name="RevisionName" value="1"/>
<!-- Type of mapping, Functional or Production -->
<Param name="ModuleType" value="Functional"/>
<!-- Design attribute rule to be used during mapping -->
<Param name="DesignAttributeConstraint" value="Auto Map"/>
<!-- Draft release level to assign to new designs -->
<Param name="ReleaseLevel" value="Draft"/>
</FEMParameters>
Parent Topic:
Capital Harness Designer Modular
Capital Harness Designer User Guide, 2512
Unpublished work. © 2025 Siemens
Source: https://docs.sw.siemens.com/en-US/doc/861057055/202410078.capital_hd_user/kql1694171936212 · retrieved 2026-07-18