Installation prerequisite activities
- Last UpdatedOct 15, 2025
- 5 minute read
After installing the prerequisite software, and prior to installing Composable MES, complete the following prerequisite activities.
Step 1: Configure prerequisite components
-
Open the post-install Configurator. Select Run as Administrator to enable the correct permissions.
-
Select the AVEVA Enterprise License Server component.
-
Enter the Server Name and select Test Connection.
-
Once the connection is validated successfully, select Configure.

-
Select the Common Platform System Management Server component.
-
Select the This Machine is in the System Management Server option.

-
To configure the component, select Configure.
-
Select the MES Database Setup component.
-
Enter the Server Name where the MES database is located and the MES Database Name.

-
To configure the component, select Configure.
-
Select the MES DB/MW Communication component.
-
Configure the Security settings and AVEVA Identity Manager settings.

-
Select the MES Middleware Proxy component.
-
If required, update the middleware proxy port information.

-
To configure the component, select Configure.
Step 2: Verify the AIM token
-
Verify the generated token is linked to the repository that is used for package installation. If not, generate the token and link it to the repository.
Step 3: Unblock the Composable MES installation package folder
The Composable MES installation package is provided as a ZIP folder, which contains several modules, including the Frame module, Use Case module, and Job module.
Note: Ensure that you unblock the package folder before extracting its contents.
To unblock the files:
-
Do one of the following:
-
Use the following PowerShell command below can be used to unblock all files in the folder.
get-child item <FilePathToUnblock> | unblock-file
For example: get-child item "C:\Users\winaero\Downloads" | unblock-file
-
Alternatively, select Unblock in the ZIP file Properties dialog General settings.

-
-
Repeat this step before installing any module to ensure that the specific module's folder is unblocked.
Step 4: Extract the installation package files
Extract the contents of the installation package file. The Release 1.0 package includes the following components:
|
Folder name |
Content description |
|
AM_01.00.00 |
Andon Module package |
|
FT_01.00.00 |
Frame Template package |
|
SC_01.00.00 |
Supervisor Console package |
|
TD_01.00.00 |
Task Driven package |
|
OM_01.00.00 |
Order Management Module package |
|
UC_OM_01.00.00 |
Order Management use case package |
|
JM_01.00.00 |
Job management Module package |
|
UC_JM_01.00.00 |
Job Management use case package |
|
UC_JM_CL_01.00.00 |
Job Management use case |
|
MP_01.00.00 |
Material Production Module package |
|
UC_MP_01.00.00 |
Material Production Execution use case package |
|
MC_01.00.00 |
Material Consumption Module package |
|
PE_01.00.00 |
Performance Module package |
|
UC_PE_01.00.00 |
Performance use case package |
|
UC_PE_KPI_01.00.00 |
Performance KPI use case package |
|
QM_01.00.00 |
Quality Management Module package |
|
IM_01.00.00 |
Inventory Management Module package |
|
WI_01.00.00 |
Work Instruction Module package |
Note that each folder contains a complete set of installation files. The installation files associated with each installation package are unique. For example, FT_V01.00.00 includes the following:

Note: Prior to installing a package, ensure that the files are unblocked. If the files are not unblocked, use the following command to unblock all of the files in a folder: dir " FilePathToUnblock " -Recurse | Unblock-File.
Step 5: Configure MES Client
Configure ‘MES Client’ before installing the Frame Template package. To configure MES Client for Composable MES:
-
Configure MES To use ‘OS User’.
-
Add one ‘Fact Admin’ user who can be used to authenticate API calls.
The domain user should be added in OS Group and user ‘FactAdmin’.
Note: If an Invalid Request Error occurs, ensure that you open the Enterprise Console with the Central Configuration server name.
-
Log into Work Tasks and add the configured user as Administrator in Repository Settings.
Step 6: Configure IIS Content Security Policy settings
-
Open the IIS manager.
-
Select the Work Tasks Enterprise Console connection and then open HTTP Response Header.

-
To add a new Content Security Policy, select Add and enter a name and value using the format described in the following example.
Example: Add self *. domainName by adding *.mddc.com after the initial ‘self’: self *.mddc.com
Note: Placeholder values are provided for example purpose only. Actual settings should be entered based on the particulars of the server being configured.

Step 7: Check Web Portal configuration for the Web API
-
Navigate to the Work Tasks Enterprise Console settings dialog and select Web API source.

It is recommended to have MES Web Portal installed on the same machine that Work Tasks is installed. If SQL is on another server, ensure AIM Host defined in the post-install Configurator MES DB/MW Communication component settings points to the SQL host.
