Introduction¶
About this guide¶
This guide defines the entities and XML message definitions that make up the Scheduling Schema. It defines the referential constraints which must be followed between the entities as well as the purpose and definition of each entity.
Guiding principles¶
When interacting with PSO it is important to only send relevant data i.e. data that the DSE will actually use or that will be displayed on the workbench. Sending redundant data may impact overall performance.
Advanced Features¶
Some elements of PSO are more advanced and complex than others and can have a material impact on the scheduling performance and quality of the plans produced. Use of several of these advanced features or going beyond the limits set for the elements can only be done after guidance from IFS PSO Product Development. Advanced features are:
- Activity Groups
- Parts
- Depots
- Resource Pools
- Splittable activities
- Separation Groups
- Incentives
Backwards Compatibility¶
As a general principle, all aspects of the interface are kept backwards compatible wherever possible. This means that under normal circumstances it should always be possible to upgrade to a new version of the software without any changes being required to the integration.
If updates are made to the software that require changes to the integration for any reason, these will be documented in the 'Appendix: Deprecated and Removed Features' section of the Release Enhancements Guide.
A note about IDs¶
Warning
The maximum length for an id is now 2000 characters, rather than 32, although ids will be listed as having data type 'String(32)' in this documentation. However, the use of any id longer than 32 characters will make the performance of the system slightly slower, so it is advisable to use ids with a length of 32 or less if possible.
A note about numeric attributes¶
Warning
Numeric values must be greater than or equal to zero, unless explicitly stated otherwise. This applies to attributes of data type Double and Integer.