DuneSpan Platform

PROJECTS

PROJECTS is the execution layer: tasks, milestones, schedules, owners and dependencies across engineering, production, certification and delivery.
In the app it sits under Project Management, as DuneSpan Projects and Tasks.

Get in touch

See FLOW

A deeper look

What PROJECTS is and what it does

PROJECTS is the execution layer of DuneSpan. Where FLOW moves a job between departments, PROJECTS breaks the work inside those stages into tasks, milestones, schedules, owners and dependencies, and tracks them through engineering, production, certification and delivery.

In the app it sits under Project Management in the sidebar, as DuneSpan Projects and Tasks: the place where a stage of work becomes a dated plan with a named owner on every line, a predecessor chain that holds, and a critical path that is visible before a delivery date moves.

In category terms FLOW belongs to the BPM and workflow-management layer, while PROJECTS belongs to the project and PMO-tools layer, the space occupied by tools such as Jira, Microsoft Project and Asana.

On the DuneSpan architecture diagram PROJECTS is amber; the adjacent FLOW layer is coral red.

On the architecture diagram

What PROJECTS covers

PortfolioProject portfolios and planning

Plan at portfolio and project level, with status, a start-date picker, a finish date and the count of critical tasks on every project header.

StructureTasks, milestones and dependencies

Tasks with durations, start and finish dates, predecessors and progress, so the plan records what genuinely has to happen before what.

ViewsGantt, Kanban and My Tasks views

One plan seen three ways: a calendar Gantt for the schedule, a drag-and-drop Kanban board for the week, and a personal board across every project.

PeopleTeam assignment and resources

Resources named against each task and members added per project, so there is always a clear answer to who owns the next piece of work.

TrackingProgress, critical path and delivery tracking

Per-task progress rolls up to the project, and critical tasks are marked in red so slippage is visible before the delivery date moves.

Across projectsMulti-project visibility

One view across every live project, filtered by project or by person, for managers who need the whole picture rather than a single job.

PROJECTS turns a stage into a dated, owned plan, and reports it back.

Inside the product

What the screens show today

All viewsProject header

Present on every view: project name and status badge, the project start-date picker, the finish date, and a count of critical tasks.

ScheduleGantt

Zoom by days, weeks, months or quarters. A task table carrying #, Task, Days, Start, Finish, Progress, Predecessors and Resources, with bars on a calendar grid, critical tasks in red, and Add task.

BoardKanban

To Do, In Progress and Done columns with task counts. Cards show the task number, duration and due date, and drag between columns.

AssignmentTeam

The task list with team members assigned per task, and Add Member for bringing someone onto the project.

Per personMy Tasks

Every task across your projects on one board: To Do, In Progress, Done, with filters for project and person, search, and a Critical tag on critical tasks.

The sidebar around these screens also carries Dashboard, Projects, WIP Tracking, Quality Control, Enterprise Intelligence, Workflow, Carbon and Price List.

Two layers, one record

How FLOW and PROJECTS work together

FLOW owns the job record and its stage. When a stage needs detailed work, FLOW raises a PROJECTS task pack, and PROJECTS reports progress back so FLOW's status stays true.

The simple version

A customer uploads drawings. FLOW creates the controlled job record and routes it to engineering. PROJECTS then manages the detailed tasks: drawing review, BoM check, procurement input, production release, quality record preparation, and the customer submission deadline.

Worked example

A fire damper order, enquiry to despatch

The module leading each step is named at the end of the line. This routing is a client design rather than a description of every deployment.

Enquiry to order

Enquiry received by portal upload or email; FLOW creates the controlled job record
Estimation task pack raised in PROJECTS, with INTELLIUM reading the drawings and flagging ambiguous items to a named engineer
Approval gate 1, internal technical review in FLOW; non-compliant lines resolved, or accepted with a reason
Offer issued, each revision versioned and attributable — FLOW
Order received; the ERP writes the sales order and stays the system of record
Submittal package generated from the same requirement register — FLOW, with PROJECTS tracking the package tasks

Approval gate 2, consultant approval in FLOW: approved, approved as noted, or revise and resubmit
Configuration freeze; production drawings and the cut list come from the approved configuration — FLOW
Work order released to production; HexaGrid OI takes over station events and QC holds
Approval gate 3, QC release in FLOW with test evidence attached to the unit serial
Despatch, with the evidence pack assembled automatically — FLOW

Submittal to despatch

In the field

What clients use PROJECTS for

CAD engineeringSubmittal packages

Drawings, calculations, certificates and samples, each one a task with an owner and a date set against the consultant's deadline.

ComplianceCertification and retest programmes

Lab bookings, budget and document revisions held together across a multi-year certification and retest plan.

Built environmentSite tasks and punch lists

Site tasks, punch lists, inspection records and handover evidence, carried as dated tasks with responsibilities and closeout.

In the CAD engineering approach, PROJECTS was positioned as the natural third step after INTELLIUM and FLOW rather than part of the starting scope.

Use cases

Where the modules come together

INTELLIUM + FLOW + LEXORARFQ to BoM automation

Less estimation effort, and structured inputs for the quote.

FLOW + PROJECTS + INTELLIUMDrawing approval workflow

Control over revision, review, approvals and handoffs.

FLOW + HexaGrid OI + ERP connectorJob and order tracking without a full MES

Live status on the floor and visibility for management.

HexaGrid OI + FLOW + PROJECTSQuality test digitisation

QC events, failures, holds, test reports and corrective actions.

FLOW Estate + PROJECTSSubmittal and approval workflow

Submissions, approvals, RFIs, comments and resubmissions.

LEXORA + CODEX knowledge + FLOWFire and life safety compliance support

Standards, test evidence and approval requirements kept accessible to the people who need them.

PROJECTS Estate + FLOWSite task and punch list control

Responsibilities, deadlines, dependencies and closeout, held in one place for the site team.

PROJECTS + HexaGrid OI Estate + LEXORAInspection and handover records

Structured evidence at handover and a searchable asset history afterwards.

Packages

Where FLOW and PROJECTS sit

Entry packageDuneSpan X

The workflow and job-record foundation. FLOW is the core module, and project basics come with it.

Adds the AI layersDuneSpan AI X

Everything in X, with INTELLIUM and LEXORA added on top. FLOW and PROJECTS come through X.

ManufacturingDuneSpan Works

The manufacturing package. FLOW is included, and PROJECTS sits alongside it for the detailed plan.

Built environmentDuneSpan Estate

FLOW Estate for submittals, approvals and RFIs; PROJECT Estate for site tasks, punch lists and handover.

Exact module scope per package is confirmed at proposal stage.

Foundations

What PROJECTS runs on

FLOW and PROJECTS both run on Alterion Core, the platform backbone: identity, roles and permissions; the company and site model; the enterprise object model of customer, job, order, drawing, BoM and task; the workflow engine; the data and file layer; and the audit trail.

Integrations

ERP connected at the sales work order stage, with the ERP remaining system of record for orders and write-backs passing through FLOW approval
CAD and CAM reached through expert packs, including a structured handoff into EPLAN
PLM, MES and CoralDune AI tools, where workflow control gains from the integration

Hosting fit

A custom CoralDune application
A managed private cloud
A SaaS-style private deployment

Both modules suit all three.

Want PROJECTS planning the work?Tell us where your delivery dates are slipping.