Conflict Intervention
FCSI has developed functionality that helps prevent conflicting data from being generated. Utilizing core functionality we store history markers that are available to all jobs and alternatives. If a history marker is already defined, we prevent data from being updated in multiple jobs or alternatives.
Smallworld's out-of-the-box conflict resolution is very good for multiple changes on a single object. When you make changes to a geometry that results in multiple geometries and records being created, the changes may not be correctly handled during the merge and post processes. The Design Manager helps reduce this by recording areas of changes, but when geometries with large bounds are updated, the overlapping areas are too difficult to identify potential conflicts.
PNI Sheath Case Study
There are 2 designs that have inserted an optical splice onto the same sheath. The optical splices both split the same original sheath in its own design (alternative). After doing a merge and post process on one design and then a merge to the other design, the result of the original sheath is not correctly handled. Typically you will see a gap in the original path of the sheath.
Conflict Intervention
With FCSI's Conflict Intervention, the second design would not be able to insert the optical splice. This is because the change of geometry in the first design created a history marker that the second design will encounter and prevent modifications to the geometry in the second design.
History markers are created whenever you want through the use of triggers and pre action code. You customize the Conflict Intervention to meet your exact needs.
This functionality may be extended to support provisioning by creating history markers on assets used during provisioning.
