OpenCore MES Try the demo

Docs Designing the system 1

The one rule

On this page

Nothing reaches the plant except through a change request. Every change goes through four stages:

StageWhoWhat happens
DesignA designerYou draft the change: objects, rules, scripts, services, connections, schedules. Nothing you draft affects the plant yet
ReviewA reviewer (not you)Someone else reads the change and passes it, or asks for changes
ApprovalOne representative per department concernedEach department whose data or process the change touches approves or rejects it
ExecutionThe platform, when its executor saysOnce every department has approved, the change waits, approved, for the person named to execute it when you submitted it. When they press Execute, the platform publishes it in one step. No person, and no AI, publishes anything by hand (your organization may have the last approval execute it instead)
VerificationIts executorThey check it in the plant, then sign that it works, or report a problem with a picture of the page
A change to the work order object at Review, as its reviewer sees it, with Review it
A change at Review, as its reviewer sees it: what changed is counted on its tabs; Review it passes it, or asks for changes.
A change to the work order object at Review, as its reviewer sees it, with Review itA change at Review, as its reviewer sees it: what changed is counted on its tabs; Review it passes it, or asks for changes.

Three things follow from it:

  • You never approve your own change, and whoever reviews a change cannot also approve it for a department.
  • The departments that approve are worked out for you from what the change touches: its footprint. Change a quality field and Quality approves; change a service that writes lots and the lot's stewards approve.
  • Execution is all or nothing. If something the change was drafted against has changed since (someone else's change executed first), execution is refused, and the change is marked failed so you can redo it on top of the new version.
The lot object's living document: version 1 as it is live, read only, with Change it
An object's living document: the version in use, read only, its tabs as the designer has them, and Change it to start a change.
The lot object's living document: version 1 as it is live, read only, with Change itAn object's living document: the version in use, read only, its tabs as the designer has them, and Change it to start a change.

Designers, roles and approvers: three different things

They are easy to mix up, because all three are about "who may". They answer different questions:

AnswersSet whereExample
The designerHow does the system work? The objects, fields, policies, screens, layoutsA change request, in the DesignerDana adds a Picture field to Equipment
RolesWho may do what with the records? A policy ties a role to rights: read, create, write these fields, take these actionsThe object's Roles & policies tab; people are given roles in People & departmentsEngineers may upload an equipment's picture
Stewards and their approversDoes this change go live?The object's Stewards tab (departments); each department's approval steps in People & departmentsProduction signs the change that adds the field

So, for one change: the designer drafts the field and the policy; the policy's role says who will be able to use it once it is live; the stewards' approvers decide whether it goes live at all.

Two things that catch people out:

  • Several teams may design, each in its own space (People & departments → Spaces): its designers change only what is in it; the Designer's own designer role changes everything. Each list on the designer's home has a Space filter (my spaces first), each design shows its space beside its name, and a new one goes into the space the list shows (or yours).
  • "designer" and "reviewer" are roles on the Designer itself, not on your objects. A policy can only name roles the object declares. Name another and the draft says Policy "…": its roles must be roles of this object: take that role out of the policy, use one the object has, or add a role to the object and give it to people.
  • Holding a role does not make someone an approver, and being an approver gives no right on the records. A quality engineer who approves changes for Quality still needs a role on an object to open its records.