CONOPS A product of CONOPS
Module · Workflows

Approval chains leave email and run on a designed, dated, audited path.

A node-graph designer turns ECN approvals, NPI gates and buy-offs into templates with tasks, custom approval outcomes, if/else branches, reminders and escalation. Dates schedule forward or backward from the customer-order date.

In production Engineering, quality, contracts Reads the ERP, never writes to it
CONOPS | MOS · Workflows · ECN approval template
ECN raised Design review Impact > $5k? Quality approval Customer notify Released
Instances in flight
InstanceStepOwner queueDueState
ECN-2041 Quality approval Quality Today On time
ECN-2038 Design review Engineering Yesterday Escalated
ECN-2035 Customer notify Contracts +2 d Send-back 1
A template as designed: approvals with custom outcomes, a decision branch and a rework loop back to the originator.
Outcomes

What changes when Workflows is live

Approvals have a date, not a hope
Each task is scheduled forward from launch or backward from the customer-order date, so the chain shows when it must be done, not when someone remembers.
Nothing waits in a personal inbox
Tasks go to department queues, with reminders and escalation. A person out sick does not stop a release.
Every decision is on the ledger
An append-only action ledger records who approved what, with which outcome, and when. Auditors read it; nobody reconstructs it.
Feature walk-through

As built, in the order your team meets it

Screens shown are rendered stand-ins for the real views; production screenshots use seed demo data with customer names and part numbers replaced.

01 / 06

Visual node-graph designer

Drag tasks, approvals, if/else, split/merge, email, delay and webhook nodes onto a canvas. Approvals carry custom outcomes (approve, approve with changes, reject, defer) that drive the branch taken next.

  • Tasks, approvals, if/else, split and merge
  • Email, delay and webhook nodes
  • Custom approval outcomes per step
Workflows · Visual node-graph designer
Node types
Task Approval If / else Split Merge Email Delay Webhook
02 / 06

Scheduling anchored to the customer order

Per-task durations schedule the chain forward from start or backward from the customer-order date. The gate that must close before material release gets its real due date, and the late one shows up red.

Workflows · Scheduling anchored to the customer order
NPI gate review, scheduled backward from order date
Drawing review
Tooling plan
Quality plan
First-article buy-off
Release to floor
03 / 06

Department queues and reminders

Assign a step to a department rather than a name. Anyone in the queue can take it; reminders fire before the due date and escalation after it.

  • Department queues or named assignees
  • Reminder and escalation schedule per step
  • Delegation when a role is out
  • Queue dashboard by department
04 / 06

Send-back rework cycles

A rejection does not kill the instance. It sends the work back to the originating step with the reviewer's notes, counts the cycle, and reschedules downstream dates.

Workflows · Send-back rework cycles
Rework loop
Submit Review Send back (cycle 1) Resubmit Approved
05 / 06

Auto-launch by record category

A new PLM change launches the ECN template; a new NPI item launches the gate review. No one has to remember to start the process.

  • Launch rules by record category and site
  • Template versions with effective dates
  • Manual launch for one-off chains
06 / 06

Audit ledger

Every action on every instance is appended to a ledger that cannot be edited: who, what, outcome, timestamp, from which queue. Export it for the auditor or the customer.

Workflows · Audit ledger
Ledger · ECN-2041
WhenWhoStepAction
09:12 R. Ortiz Design review Approved
11:40 Quality queue Quality approval Claimed
13:05 M. Chen Quality approval Approve w/ changes
13:06 System Customer notify Scheduled +2 d
Data it reads

Nothing is written to your ERP

Workflows is a module of CONOPS | MOS (Manufacturing Operating System). It reads from the platform warehouse, which pulls change-only loads nightly from each site's ERP over a linked server. The ERP is never written to, and adding a site is configuration, not code.

How a site's ERP is onboarded

ERP datasets used by Workflows
  • Customer orders (for backward scheduling from the order date)
  • Job orders and part master (context on the instance)

Workflow instances and the ledger are application data; the ERP supplies dates and references.

Who uses it

By role

Engineering

Designs templates, owns design review and NPI gates.

Quality

Approves with outcomes, sends back with notes, reads the ledger.

Contracts

Owns customer-facing steps such as notification and flow-down acknowledgement.

Compliance

Exports the ledger; verifies the chain matched the procedure.

Roadmap, not yet shipped. An HR module is planned on the same workflow engine (PTO requests, certifications). It is not available today.
Next step

Bring one paper approval. Leave with it running as a template.

In a two-hour workshop we model one of your approval chains end to end, with the queues, outcomes and escalation rules your people already follow informally.