Multi-Organisation OperationΒΆ
In advanced installations the system may need to be operated on a multi-organisation basis. This would be for security and/or operational reasons. By default the system is configured to use one organisation. Each organisation can have many scheduling and/or modelling datasets to be processed.
An Organisation is identified by its organisation id and account id, where organisation id is an internally used integer (i.e. 1, 2, 3, etc) and the account id is the "friendly name" (i.e. "FixiTech"). In a multi-organisation system, it is easier, and more obvious to the end-user, to identify an Organisation by it's account id. As such, the supported means of sending data into a multi-organisation system is via the Scheduling Gateway Service, which allows the organisation to be identified by its account id when logging-on and acquiring a session token.
Note
When sending data into a multi-organisation system, the relevant input row pertaining to the specific schema must be included; Scheduling data must include an Input Reference row, Modelling data must include a RAM_Update row, and System data must include a System_Input row. Note that the Scheduling Gateway Service will automatically ensure that the organisation id is filled on any input data based on the account id provided when logging-on and acquiring a session token, therefore you do not need to know the organisation id, the account id is all that matters.
When logging on to the Scheduling Workbench the account id is entered as part of the URL. See the PSO Workbench User Guide for details.