CONOPS A product of CONOPS
Module · Projects

Project plans your PMO and your engineers both use, with the floor's work rolled in.

Project, Milestone, Task and Subtask in one hierarchy, viewed as a list, a board or a Gantt. Dependencies, percent-complete roll-up, multi-site sharing and a resource calendar, on the same database as your records and workflows.

In production PMO, engineering leads Reads the ERP, never writes to it
CONOPS | MOS · Projects · Gantt
M1 · Kickoff
Tooling design
Fixture build
M2 · First article
Rate readiness
M3 · Rate release
Percent complete
46%
Healthy
Tasks late
4
Warning
Critical path slip
6 d
Critical
Milestones and tasks with dependencies; percent complete rolls up from subtasks.
Outcomes

What changes when Projects is live

One plan, three views
Engineers work the board, the PMO reads the Gantt, leadership gets the list with roll-up. Nobody maintains a second copy.
Slips are visible the day they happen
Dependencies and percent-complete roll-up mean a late subtask moves the milestone, and the milestone turns red before the review.
Sites share without losing ownership
A corporate program can span sites while each site keeps its own tasks, people and calendar.
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 / 05

Project, Milestone, Task, Subtask

A fixed four-level hierarchy keeps plans consistent across sites. Percent complete rolls up from subtasks; dates roll up from the latest child.

  • Four levels, same on every site
  • Roll-up of dates and completion
  • Owners and watchers per level
  • Templates for recurring project types
02 / 05

List, board and Gantt views

Switch views without changing data. Filters and saved views are per user; the Gantt shows dependencies and the critical path.

Projects · List, board and Gantt views
Board · Fixture build
To doIn progressBlockedDone
Order plate stock Machine base Weld jig (vendor) Design approved
Inspect locators Program OP20 Order clamps
Dry run Kickoff
03 / 05

Dependencies and critical path

Finish-to-start links with lag; the critical path is highlighted and the slip is quantified on the milestone.

  • Finish-to-start dependencies with lag
  • Critical path highlight
  • Slip in days on each milestone
04 / 05

Resource calendar

See who is loaded where across projects, by week. The calendar respects site holidays and shift patterns.

Projects · Resource calendar
Engineering load, week 42capacity
R. Ortiz 44 h
M. Chen 34 h
D. Patel 38 h
S. Lee 24 h
05 / 05

Multi-site sharing

Share a project with another site while Row-Level Security keeps every other row where it belongs. Corporate sees the roll-up across sites in one view.

  • Share by project, not by database
  • Corporate read-only roll-up
  • Per-site numbering and calendars preserved
Data it reads

Nothing is written to your ERP

Projects 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 Projects
  • Job orders (link tasks to jobs)
  • Part master and BOM structure (for NPI projects)
  • Customer orders (dates for program projects)
Who uses it

By role

PMO

Owns the Gantt, the critical path and the monthly review pack.

Engineering lead

Works the board; attaches records and workflow steps to tasks.

Site leadership

Reads milestone status and slip across projects.

Next step

See a capital project, an NPI and a kaizen on one board.

Bring one live project plan. We rebuild it in the demo environment and show the Gantt, the roll-up and how floor records attach to tasks.