MSO Simulation for Admin Users¶

IFS.ai MSO Simulation¶

What It Does¶

IFS.ai MSO Simulation is a what-if analysis capability within Manufacturing Scheduling and Optimization (MSO) that uses intelligent optimization algorithms to generate simulations of feasible and optimized production schedules in constraint-based manufacturing environments.

The feature allows planners to create hypothetical production scenarios and evaluate the impact of changes to resources. By comparing simulated production scenarios, users can understand the benefits and drawbacks of alternative production setups and make data-driven decisions before implementing operational changes.

Where the Results Appear¶

The processing results are displayed on the following IFS Cloud page:

• Simulation Scenario Analysis
• Simulation Resource Assignments

The following fields are populated/updated:

• Planned Start Date
• Planned Finish Date
• Resource Start Date
• Resource Finish Date
• Resource ID
• Resource Description
• Load Factor
• Hours Loaded
• Man Hours Loaded

How the Processing Works¶

Data Flow¶

1. The user triggers a Simulation from the Simulation Scenario page.
2. Load XML is produced in IFS Cloud and sent over to IFS.ai platform.
3. Static scheduling service in IFS.ai platform picks the Load XML and generates the plan.
4. Generated plan is sent back to IFS Cloud using a polling broadcast.
5. Simulation result is then populated in IFS Cloud.

Static Scheduling Service Information¶

Static Scheduling in IFS.ai platform consists of several services.

1. Static Scheduling API Service - An API for submitting static schedules to the system and being able to poll for when results are available.
2. Static Schedule Runner - An application that monitors the job list in database for schedules that need to be started and creates a Kubernetes Job to to process the input.
3. Static Scheduling Engine - The processing engine for the schedules. The application will validate the input data and configuration, process the input, write the output to the file storage, update the job status and track the tenant consumption.

Availability and Prerequisites¶

AI Services¶

• IFS.ai services are enabled.

Configuration Requirements¶

• The site must be configured for MSO scheduling on the Finite Scheduling Basic Data page, with relevant parameters defined, these parameters will be used for simulation as well.
• The selected scheduling server configuration must be connected to an operational scheduling server.
• A simulation scenario must be created for the site on the Simulation Scenario page, specifying work center resources, persons, person groups and tool instances to be considered in the simulation.
• The dataset for the scheduling scenario must be active.

Data Access and Security¶

Users must have access to the following business objects and related components:

• FNDSCH — Finite Scheduling
• SHPORD — Shop Order
• ORDSTR — Order Structure
• OPTI — Component to use Static Scheduling Services in IFS.ai

Processing respects IFS Cloud role-based security controls.

Data required for scheduling purpose is sent over to Static Scheduling Service. Input Load XML and Plan generated are stored in tenant specific storages, ensuring data integrity. Once the plan is received by IFS Cloud, both Input and Output data are deleted from IFS.ai platform.

Processing Execution¶

Trigger¶

MSO simulation is triggered only when a planner explicitly requests it using "Schedule Scenario" command in Simulation Scenario page.

Extraction and Field Mapping¶

The feature first creates unique scheduling activities for setup, runtime activities etc. in the shop order. This is included in the Input XML. Scheduling Service will broadcast the plan generated which contains allocation details of each activity. This plan is re-constructed to visualize allocations of shop orders.

Known Limitations¶

• Activities should be limited to 35,000.
• The scheduling mode Automatic is not available when the deployment model is hybrid/hosted (when deployed through IFS.ai).
• MSO simulation only facilitates resource related modifications.
• MSO simulation does not support resource calendar modifications.

Troubleshooting¶

If results are not shown, verify:

• Make sure the background job "Force Load" in the Background Jobs page is posted and executed. If there are any errors look at the details of the background job in the same page.
• Relevant Scheduling Job record in Scheduling Optimization Jobs page is at Finished status.
• Make sure the background Job "Process Schedule" is posted and executed in the Background Jobs page. If there are any errors look at the details of the background job in the same page.
• Check Scheduling Optimization Logs page for any errors.
• Check Scheduling Optimization Output Data page for the plan received.