Portfolio
Performance, cost and resource load across every active engagement.
- SPI / CPI rollup
- Resource heatmap
- 60-day milestone horizon
Estimating · Proposals · Scheduling
One record from first estimate to project closure.
An estimate-to-schedule platform: Orditur replaces the spreadsheet estimate, the Word proposal and the disconnected P6 file with a single system where scope, price, work and schedule stay tied together.
One record.Every surface.No re-keying.
Project IDVP-24-118 · AUTOCLAVE QUALIFICATION
Critical path Critical Non-critical Total float Data date
4
surfaces
Estimate · propose · schedule · control
1
record
No re-keying between stages
0
seat licences
Runs in the browser
The unbroken thread
Four stages. One dataset. Nothing re-keyed.
Scope priced once flows straight through to the proposal, the work breakdown structure and the critical path. Nothing is retyped, so nothing drifts.
- 01
Estimate
Scope item by item. Every deliverable — survey, design, build, test, qualification, close-out report — priced at role-level hours against a governed rate card.
- Scope templates by asset or work type
- Risk and complexity multipliers
- Live margin by line, category, project
- 02
Propose
The approved estimate becomes the proposal. Pricing tables, assumptions, exclusions and standards references assemble themselves.
- Reusable content blocks
- Your own standards and clause library
- Print-ready document, versioned
- 03
Schedule
Award converts the estimate into a work breakdown structure with a real CPM network — not a bar chart someone dragged into shape.
- FS/SS/FF/SF logic with lead and lag
- Working calendars and hard constraints
- Resource levelling within or beyond float
- 04
Control
Baseline it, then track the truth. Earned value, schedule health and variance against the number you actually sold.
- SPI / CPI to the original estimate
- DCMA-style schedule quality checks
- Client-facing shared timelines
Inside the console
Four working surfaces, one governed core.
Every surface reads the same record. Change a rate, a duration or a dependency and the consequence shows up everywhere it matters.
Estimate
Spreadsheet-grade grid with governed rates and live margin.
- Grouped by asset or work package
- Override tracking
- Contingency and markup
Schedule
Full CPM network with calendars, constraints and levelling.
- Critical path and float
- Dependency logic with lag
- Baseline variance
Client view
A read-only timeline link that shows progress and nothing else.
- Token scoped, revocable
- No rates, no cost
- Expiry dates
Position
Everything P6 schedules — plus the estimate that sold it.
One record: price the scope, send the proposal, schedule the work, track the money.
Full CPM engine with float and lag
OrditurP6MSPResource levelling within float
OrditurP6MSPEstimate and price feed the schedule
OrditurP6MSPConfigurable deliverable libraries per industry
OrditurP6MSPProposal generated from the same record
OrditurP6MSPEarned value against the sold estimate
OrditurP6MSPSchedule quality diagnostics
OrditurP6MSPClient-shareable timeline link
OrditurP6MSPRuns in a browser, no licence per seat
OrditurP6MSP
Principles · 01—05
Five rules from the board, each one a working part.
The brand marks are not decoration — every principle maps to something the product actually enforces.
01
Foundation
Build from first principles. Structure everything.
Scope, deliverables and rates defined before a single date exists.
02
Momentum
Move forward. With purpose.
CPM drives the plan; progress and earned value keep it honest.
03
Clarity
One path. No ambiguity.
One critical path, one record, one shared timeline for the client.
04
Systems
Organized. Measured. Connected.
Estimate, proposal, schedule and actuals on the same data core.
05
Precision
Every element in its place.
Resource levelling, calendars and constraints to the day.
The word
A project is warp and weft.
The word carries four senses at once, and the product is built on the same four: the plan you string, and the work you weave across it.
The entry
orditur
/ˈor.di.tur/Latin · verb · 3rd person singular present
“He, she, or it begins; commences; weaves, lays the warp.”
From the deponent verb ordior — to lay the warp threads on a loom before a single row can be woven. Figuratively: to set about, to undertake, to start the work in earnest.
“…bellum Troianum orditur.”
Horace · Ars Poetica — “he begins the Trojan War”
Not oritur (“it arises”). Nothing here arises on its own — it is strung, measured and begun on purpose.
Four senses · one record
01Estimate
“he, she, or it begins”
The estimate is the first commitment. Every downstream number descends from it.
02Proposal
“commences”
The priced scope becomes a signed obligation, with no re-keying in between.
03Baseline
“lays the warp”
The warp is the fixed thread strung before weaving. Here it is the baseline schedule.
04Execution
“weaves”
Progress, cost and float cross the baseline row by row — the weft on the warp.