Ortems SolutionUpdate
Introduction:
The fix 2121 of the 2021(8.5) release of DELMIA Ortems (available on Refresh 5), introduces new collaborative actions:
- Create WO
- Split WO
- Split Operation
Those actions were available exclusively when having WIP control, now they can also be executed using collaborative work.
What is the Collaborative mode / work?
Collaborative mode allows several users to make modifications on a same planning.
The modification will be generate as events and could be of several types (DEB, CAL, etc)
From a collab user, right click in a WO or Machine Gantt chart: each action, sending a collaborative event (to share his work) is written “(Collab.)”. All actions are labeled on the Help and has a proper chapter for each subject.
For example, a collaborative user may run a scheduling optimization, but as the “Scheduling” menu is not written “Scheduling (Collab.)”, that means the result of the scheduling cannot be shared with another user. No event will be generate.
Collab can:
Perform interactive follow-up and collaborative actions. This is not the saving of the planning, but an authorization to make some collaboration actions until it is definitely save by the planner.
Theoretically :
Once the collaborator user will validate his/her modifications, these modifications will be stored in 1 of our 2 events tables with a particular status.
At this step, events will not be definitely validated and they will be processed every time a user will recall WIP.
Once the planner will validate WIP, the corresponding events will be recorded in the database. Then data are affected by the application of these events. Events are flagged are processed and then they will not be played any longer.
DB no longer saves actions to perform at recalling WIP, but DB contains data as they were impacted after playing the events.
Technically:
3 tables are used to register events:
- B_EVT : Follow-up and collaborative events.
And
- EVENTS : Collaborative events
- +EVENTS_PARAMS : Parameters of the collaborative events in table EVENTS.
A setting allows sending follow-up in EVENTS & EVENTS_PARAMS tables (LEGACY_FOLLOWUP_EVENTS).
How does it work:
In planner:
A planner makes a modification and validates WIP. The actions are logged as an event
=> if event recorded in B_EVT table, then B_EVT.EVT_MARQUEUR=1 (means event not to be played)
=> if event recorded in EVENTS & EVENTS_PARAMS tables, then EVENTS.EVT_STATUS=1 (means event not to be played)
In collab:
A collab makes a modification and confirms his modifications.
=> if event recorded in B_EVT table, then B_EVT.EVT_MARQUEUR=0 (means event to be played)
=> if event recorded in EVENTS & EVENTS_PARAMS tables, then EVENTS.EVT_STATUS=0 (means event to be played)
Each user recalling WIP will load the data and then play these events (those “to be played”).
If Planner recalls WIP, events are played and data in memory impacted by the events.
Planner validates WIP => memory pushed to DB and
=> if event recorded in B_EVT table, then B_EVT.EVT_MARQUEUR=1 (means event not to be played)
=> if event recorded in EVENTS & EVENTS_PARAMS tables, then EVENTS.EVT_STATUS=1 (means event not to be played)
But if ever it is not possible to play an event:
=> if event recorded in B_EVT table, then B_EVT.EVT_MARQUEUR=2 (means event in error and won’t be played any longer)
=> if event recorded in EVENTS & EVENTS_PARAMS tables, then EVENTS.EVT_STATUS=
- 2 (means event in error and won’t be played any longer)
- 3 (means event was rejected and won’t be played any longer)
Let's summarize EVT_STATUS value:
0 = event is not taken into account in base. It is run at every WIP recalling
1 = event is taken into account in database. It is not run anymore.
2 = event in error. Hasn't been applied for some reasons.
3 = event is rejected. Hasn’t been applied
Prerequisites:
All along this document, it is written “Collab profile users” where it is actually a Collaborative profile assigned to an environment for a user.
To be a collab on an environment, the user must be assigned with a class whose “Profile” is “COL”.
To be done or checked: launch “Environment/User Management” module and go “Users” tab, look at your user – each class is specific by environment.
Special token should be also incorporate on your license:
- OBP=>Number of PS collaborative users
- OMB=> Number of MP collaborative users
Link to a video presenting Ortems collaborative mode: https://r1132100503382-eu1-3dswym.3dexperience.3ds.com/#community:F808hrMlRu6muF3FamipVQ/post:CMMsL5bsT8Wwau-F38hnWQ
