Collaborative Scheduling
Using collaborative scheduling, you can schedule concurrently, share data models, specify permission levels, and view schedules.
About Data Model Versions
- Master data model
This model is the authoritative source of data. This model is located in the data vault.
- Published versions
A published version is a read-only copy of the data model. This version is located in the data vault. For example, planners can use a published version to distribute the schedule's final version.
- Working copies
Each user has a work-in-progress copy of the master data model. This copy is located in the data vault. Changes are automatically saved to the working copy. The user can manually save changes to the master data model.
- Local data file
This file is automatically copied from the user's working copy to the user's local machine. The user's changes are regularly copied from the local data file to the working copy in the data vault.
User roles apply to all data models. Depending on your user roles, you are authorized to perform specific functions:
- Configure collaborative scheduling
- View or modify master data or scheduling data
See About Users.
Configuring Collaborative Scheduling
The configuration must be performed by a user with the "admin" role.
Microsoft SQL Server must be installed and compatible with your Infor Production Scheduling version. See the Infor Supply Chain Planning products Hardware and Software Requirements guide.
See Setup Wizard.
Opening a Shared Data Model
When you start Infor Production Scheduling, you can open these files:
- You can open the master
data model.
When you open the master data model, your working copy is created. By default, your changes are automatically saved to your working copy. From the Database tab of the Preferences dialog box, you can modify the automatic save and update intervals. Use the menu to update your working copy from the master data model and save it to the master data model.
- You can open a published version.
- If you have not already
opened a shared data model, then you can open a local data file.
In this case, the Setup Wizard is displayed. The Setup Wizard allows you to upload the data file to the data vault.
In the model name field of the System Login dialog box, select the version that you want to open.
Working with Collaborative Scheduling
Optionally, from the Database tab of the Preferences dialog box, configure the automatic save and update intervals of your working copy. See About Preferences.
From the menu, you can perform these operations:
- Lock the master data model
- Update your working copy from the master data model
- Save your changes to the master data model
- Discard your changes and update your working copy
- Publish a read-only version
In case of conflicting schedules, the Messages dialog box displays an error message. The data conflict check includes process batches, tank batches, orders, master data, flows, and sequence rules. Except for global preferences, user preferences, and global settings, all data changes can raise a conflict. An example is changes to the work area.
Use case
Two planners are viewing the schedule.
To alleviate a potential conflict, one planner defers a production order and saves the changes.
The other planner updates the schedule and the deferred production is visible.
Example: Planner A works on long-term scheduling and Planner B works on short-term scheduling.
Planner A locks the master data model and performs long-term changes:
- Entering orders and due dates
- Evaluating capacity limitations
- Material planning, managing labor schedules and machine constraints
Planner A releases the lock.
Planner B locks the master data model and performs short-term changes:
- Batch sequencing and CIP scheduling
- Cost optimization
- Batch scheduling to ensure on-time delivery
Planner B releases the lock.
Example: Planner A works on scheduling brewing processes while planner B works on the packaging processes in a plant.
Inflow materials, by-products, resources, and labor for brewing processes and packaging processes are independent of one another.
Planner A performs changes to production tanks, batches, and resources. Planner A finishes performing the changes before planner B and saves the schedule to the master data model.
Planner B simultaneously works on the schedule. Planner B performs changes that pertain to the packaging batches and resources. Before saving, planner B verifies that Planner A's concurrent changes do not affect his work.