Configuring

the FEM Task for Module Code Assignation

You can use a flexible execution model (FEM) task to run module code assignation.

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 Capital Configuration Files Reference Guide for further information.

Procedure

1. Create an XML file similar to the example file ModuleCodeAssignationTask.xml in the doc/webservice/data folder of your Capital installation.

2. Edit the parameters. All parameters are mandatory unless otherwise stated. Table 41: Description of ParametersName

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.

AssignationType

Whether functional or production module code assignation is being performed.

PluginURL

The URL of any custom assignation plugin to be used. The URL can be found in the details screen for the plugin. Optional. If the plugin name is not defined, then any module code assignation constraints associated with the design and matching the type specified in the AssignationType parameter, will be used.

3. Start the FEM task.The following messages may be shown on the Tasks tab of the Capital Harness Designer Modular client.

Table 42: Messages Shown While Running Module Code Assignation by FEM TaskMessages

Description

Module Code Assignation started for Project: {0} and Design: {1}, Part Number: {2} Revision: {3}.

{0} - Project name {1} - Design name {2} - Part number {3} - Revision name The module code assignation FEM task has been successfully initiated.

Task cannot be executed. Define plugin URL or assign modularization constraints to the design.

The assignation plugin name is not defined, and there are no assignation constraints associated with the specified design that match the specified assignation type. The task is aborted.

Custom Constraint not found: plugin:{0}

{0} - URL of expected plugin. Custom assignation constraints on the design are being used, but the corresponding plugin cannot be found in the plugins folder.

Plugin not found. Check the plugin URL and location of the plugin.

The PluginURL parameter has a value, but the plugin cannot be found.

Mismatch between parameters.

The plugin specified is written to perform a different type of module code assignation to that defined in the AssignationType parameter.

Design not found.

Either the project name, design name, design part number or design revision is incorrect, and the design cannot be found.

Invalid assignation type.

The assignation type specified in the AssignationType parameter is not recognized.

Unable to acquire lock on {0}, it is currently locked by {1} since {2}.

{0} - Design name. {1} - Username holding the lock on the design. {2} - Timestamp of lock. The design was locked when module code assignation was attempted.

Results

The objects in the design have module codes assigned to them.

Examples

This is the contents of the example ModuleCodeAssignationTask.xml file which can be used as a template for your own 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"/>

  <!-- Part number -->
  <Param name="PartNumber" value="AA12346_1"/>

  <!-- Revision name -->
  <Param name="RevisionName" value="1"/>

  <!-- assignation type: FUNCTIONAL or PRODUCTION -->
  <Param name="AssignationType" value="PRODUCTION"/>

  <!-- optional parameter: Assignation plugin URL -->
  <Param name="PluginURL" value="plugin:Java//com.example.plugin.assignation.GenericAssignationConstraint1m"/>

</FEMParameters>

Parent Topic:

Module Code Assignation

Capital Harness Designer User Guide, 2512

Unpublished work. © 2025 Siemens