Aller au contenu

SolutionsEngineering

Engineering project management software with a controlled deliverable record

Engineering work fails when the schedule, the calculation package, and the review comments live in different tools. Sigmaviu ties the WBS, baseline dates, document approvals, and open risks to one project.

Engineering managers, discipline leads, and PMO teams delivering design packages.

Schedule · project view

Live
Engineering activities with a baseline ghost bar behind current dates.

Baseline vs actual

Week 18
Foundations
Done
Structure
At risk
Envelope
Active
Commission
Queued
Engineering activities with a baseline ghost bar behind current dates.

What changes

  1. 01

    Hierarchy that survives import

    P6 XER, MS Project XML, and spreadsheets preview column mapping before commit and keep parent-child structure.

  2. 02

    Reviews with a frozen version

    Document approval can hold the version still while a workflow is open, and stop the author from approving their own issue.

  3. 03

    Slip you can see

    Baseline versus actual dates show on the schedule, with the option to raise risks from slips you confirm.

Snapshot

Schedule health

Illustrative variance — not live customer data

Sample
ActivityBaselineActualDelta
FoundationsWk 1–6Wk 1–5−1 wk
StructureWk 5–12Wk 6–13+1 wk
EnvelopeWk 11–16Wk 12–17+1 wk
CommissionWk 16–20Queued—

Distribution

On track58%
At risk27%
Late15%

How Sigmaviu handles this

WBS and Gantt

The Gantt is view-only until someone turns on Edit Schedule. Dragging stages a draft. Save and Cancel write the batch. Unsaved edits warn before you leave.

Deliverable control

Documents carry control numbers, versions, and risk class. Critical approvals can require a staff signature.

Interfaces and RFIs

Questions that affect design can sit on the project communications record and, when they are construction RFIs, on the RFI log.

Resource roles

Role hours planned on the WBS can sync to project resources so the estimate and the roster describe the same work.

A working sequence

  1. 1

    Import the plan

    Map columns, check parents and dates, then commit.

  2. 2

    Issue the package

    Route the document at the right risk class.

  3. 3

    Track the slip

    Compare baseline and actual, then decide which slips become risks.

  4. 4

    Close the discipline

    File lessons and the approved set for the next phase.

Scope

Schedule risk highlights use pattern matching against your own completed projects. They are a planning aid, not a guarantee of finish dates and not a trained industry model.

Questions buyers ask

Will an import flatten my WBS?

The preview is there so you can confirm hierarchy, dates, and phases before commit. Start and end dates stay in the columns you mapped.

Can I edit the Gantt by dragging?

Yes, in Edit Schedule. Changes stay local until you save. View mode does not write on every drag.

How are design comments stored?

On the document workflow and on project communication threads, with files from the document register rather than pasted links you cannot audit.