DuneSpan Platform
FLOW
FLOW is the workflow movement layer of DuneSpan: approvals, routing, file movement, department handoffs, status tracking, notifications and audit trails.
It runs on the workflow engine in Alterion Core.
It runs on the workflow engine in Alterion Core.
A deeper look
What FLOW is and what it does
FLOW is the workflow movement layer of DuneSpan. It carries work between people and departments: approvals, document routing, file movement, handoffs, status tracking, notifications and audit trails. It runs on the workflow engine in Alterion Core, which provides status, approvals, inbox, SLAs, handoffs, notifications and escalations.
Most manufacturers already know their process. What they lack is a system that holds it. Jobs wait in somebody's inbox, approvals happen over email, revisions get overwritten, and nobody can say with confidence where a job is or whose desk it is sitting on.
FLOW makes the process the product. Every stage has one owner, every handoff is automatic, and every approval, revision and document movement is recorded as it happens.
On the DuneSpan architecture diagram FLOW is coral red; the adjacent PROJECTS layer is amber.
On the architecture diagram
What FLOW covers
FLOW moves the work, names the owner, and leaves a record behind it.
As deployed
The job journey, end to end
A live FLOW deployment for a duct fabricator runs the sequence below. Each stage belongs to one role; when that role finishes, the job moves to the next person automatically, and each role's page shows only the jobs waiting on them.
Stages 1 to 6
- Sales creates the job and sends the customer an upload link
- Estimation prices the quotation
- The customer approves the quote through a price-review link
- Accounts approves the WO/DO
- Operations enters the SO number
- Production schedules and fabricates
Stages 7 to 12
- Quality Control passes or fails the job
- The Production Coordinator issues the SWO
- Accounts verifies cost
- Stores moves the job to finished goods (FGS)
- Sales Ops generates the pick slip and delivery note
- Dispatch records vehicle, driver and delivery
These stage names are configured for that client. Another client's FLOW mirrors their own approval chain.
Inside the product
Screens and features, as deployed
Configured per deployment
Approval, revision and ERP patterns
The patterns below come from CoralDune's client engagements in CAD engineering, MEP contracting and switchgear manufacturing. Each one is configured to the deployment.
Approvals and revisions
- Approval gates with states beyond yes and no, including approved as noted and approved with comments
- Configuration freeze after consultant approval; any later change reopens the gate
- NCR and disposition, with an evidence pack generated automatically at dispatch
- Every drawing and quotation revision versioned and never overwritten, with author, date and what changed
- Purchase orders matched to the quotation revision they accept
Visibility, links and ERP
- Secure shareable links for consultants and contractors, with open tracking
- Batch work orders: a large order released and tracked in batches
- Stuck work shown as stuck, with its age
- ERP linked at the sales work order stage, not at project creation
- ERP write-backs passed through human approval in FLOW
- Routing through real departments and approval limits, then a structured handoff into EPLAN and the ERP with revision and audit trail intact
Want FLOW running your approval chain?Tell us which handoffs are costing your team time.
Contact usDuneSpan Platform
FLOW
FLOW is the workflow movement layer of DuneSpan: approvals, routing, file movement, department handoffs, status tracking, notifications and audit trails.
It runs on the workflow engine in Alterion Core.
It runs on the workflow engine in Alterion Core.
A deeper look
What FLOW is and what it does
FLOW is the workflow movement layer of DuneSpan. It carries work between people and departments: approvals, document routing, file movement, handoffs, status tracking, notifications and audit trails. It runs on the workflow engine in Alterion Core, which provides status, approvals, inbox, SLAs, handoffs, notifications and escalations.
Most manufacturers already know their process. What they lack is a system that holds it. Jobs wait in somebody's inbox, approvals happen over email, revisions get overwritten, and nobody can say with confidence where a job is or whose desk it is sitting on.
FLOW makes the process the product. Every stage has one owner, every handoff is automatic, and every approval, revision and document movement is recorded as it happens.
On the DuneSpan architecture diagram FLOW is coral red; the adjacent PROJECTS layer is amber.
On the architecture diagram
What FLOW covers
FLOW moves the work, names the owner, and leaves a record behind it.
As deployed
The job journey, end to end
A live FLOW deployment for a duct fabricator runs the sequence below. Each stage belongs to one role; when that role finishes, the job moves to the next person automatically, and each role's page shows only the jobs waiting on them.
Stages 1 to 6
- Sales creates the job and sends the customer an upload link
- Estimation prices the quotation
- The customer approves the quote through a price-review link
- Accounts approves the WO/DO
- Operations enters the SO number
- Production schedules and fabricates
Stages 7 to 12
- Quality Control passes or fails the job
- The Production Coordinator issues the SWO
- Accounts verifies cost
- Stores moves the job to finished goods (FGS)
- Sales Ops generates the pick slip and delivery note
- Dispatch records vehicle, driver and delivery
These stage names are configured for that client. Another client's FLOW mirrors their own approval chain.
Inside the product
Screens and features, as deployed
Configured per deployment
Approval, revision and ERP patterns
The patterns below come from CoralDune's client engagements in CAD engineering, MEP contracting and switchgear manufacturing. Each one is configured to the deployment.
Approvals and revisions
- Approval gates with states beyond yes and no, including approved as noted and approved with comments
- Configuration freeze after consultant approval; any later change reopens the gate
- NCR and disposition, with an evidence pack generated automatically at dispatch
- Every drawing and quotation revision versioned and never overwritten, with author, date and what changed
- Purchase orders matched to the quotation revision they accept
Visibility, links and ERP
- Secure shareable links for consultants and contractors, with open tracking
- Batch work orders: a large order released and tracked in batches
- Stuck work shown as stuck, with its age
- ERP linked at the sales work order stage, not at project creation
- ERP write-backs passed through human approval in FLOW
- Routing through real departments and approval limits, then a structured handoff into EPLAN and the ERP with revision and audit trail intact
Want FLOW running your approval chain?Tell us which handoffs are costing your team time.
Contact us