Project Owner
Sees progress, cost and risk across the portfolio, and approves what matters.
ISETIA is a Project Management Information System and a Common Data Environment, built for construction and infrastructure projects. The plan, the documents and the decisions behind it live in the same place, so teams stop reconciling separate tools.
It is used by everyone who delivers a project, from executives to site engineers. Each works in the same environment, with the views and the access that fit the job.
| PMISProject Management Information System | CDECommon Data Environment | ISETIABoth, one platform | |
|---|---|---|---|
| What it manages | The management side of a project: the plan and schedule, responsibilities, risks and issues, cost and resources, and progress reporting | The project’s information: drawings, models and letters, each in one current version, with its history kept and access controlled | Both, on one platform, so the plan shows the information it depends on |
| The question it answers | Where does the project stand? Who is responsible? What is late? What needs a decision? | Which version is current, and who may see, change and approve it? | Which task does a drawing, a letter or a model belong to? |
| Who works in it | The project team for the detail; programme and portfolio managers for a consolidated picture | Owners, designers, contractors and suppliers, under rules on who may see, change and approve what | Everyone on the project, on the same record, each with the access their role needs |
| Typical records | Schedule, responsibilities, risks and issues, cost and resources, workflow and approvals, and reports | Every document, drawing and model with earlier versions kept, defined states and approvals, and a record of who changed what | One current version of every document, card and letter |
| What it gives a project | Visibility while there is still time to act, clear accountability and early warning of late work and overspend | Less searching and rework, fewer disputes, better collaboration across organisations and a cleaner handover | Every item with an owner, a stage and a date, and the reasons behind a change kept with the change |
| On its own | Information stays scattered, so the plan cannot show the information it depends on | Information is organised but cut off from the work, so nobody sees which task it belongs to | Neither gap: the plan and its information live on one platform |
| How ISETIA joins them | The plan, owners, risks, cost and progress in one structure, for one project or a whole portfolio | Document states managed through flows and statuses, in line with ISO 19650 | The plan shows what should happen, the CDE shows what the information was at the time, and the link between them shows why |
Together they give every decision one traceable basis.
ISETIA is the one place where everyone on the project works on the same record, each with the access their role needs.
Sees progress, cost and risk across the portfolio, and approves what matters.
Issues drawings and models, and answers comments and markups in one place.
Runs the schedule, the reviews and the approvals on behalf of the owner.
Receives the asset at handover with its documents, history and records.
Receives purchase orders and submits documents and deliveries against them.
Plans and builds against the schedule, and reports progress from site.
Work on the cards assigned to them, with access limited to their own scope.
Shares one current version of every document, card and letter.
Large projects rarely go wrong because of one big mistake. They lose time and money in the small gaps between people, tools and records.
The plan is in one tool, the drawings in a shared folder, the letters in personal mailboxes and the costs in a spreadsheet. Every question becomes a search.
On a project with many organisations, the costly problem is rarely a missing file. It is an out-of-date drawing in the hands of the person building from it.
Overdue work, unanswered letters and blocked tasks tend to surface in a meeting, when the damage is done.
When a change is disputed months later, the history has to be rebuilt from e-mail.
When budgets and actuals live in separate files, the picture arrives late and cannot be traced to the work behind it.
If each project builds its own folders, numbering and reports, nobody can read across them.
| Where time is lost | How ISETIA closes the gap |
|---|---|
| Information scattered across tools | In ISETIA, documents, letters, cost lines and models attach to the card that carries the work, so a question can be followed from the task to its evidence. |
| The wrong version in use | ISETIA keeps one current version of every document, keeps earlier versions available, and moves each document through the review and approval flow your project defines. |
| Problems seen too late | In ISETIA, overdue items are marked, unanswered and overdue letters surface by themselves, risks and issues have owners and dates, and a schedule run shows float and the critical path. |
| No record when a decision is questioned | ISETIA writes the record as the work happens: versions of every document, a stage log on every card, change logs on risks, issues and finance lines, a log of who received and opened what, and numbered letters tied to the cards they concern. |
| Cost that trails the work | In ISETIA, planned and actual cost and income are linked to the cards and structure elements they belong to, with live totals for the selected project, programme or portfolio. |
| Every project reports differently | ISETIA gives every project the same structure beneath one portfolio, and reports designed once on live data can be reused for every project. |
From the portfolio dashboard to progress reported on site, from the schedule to the money, from a drawing to the letter that sent it, one platform covers the whole of delivery. There is no gap between tools for information to fall into.
Documents keep every version. Cards keep a stage log, and risks, issues and finance lines keep a change log. Sharing is logged. When someone asks why something changed, the answer is on record.
A schedule run that calculates float and the critical path, baselines, a time-location view for linear work and 4D models on the same activities give planners the depth they need, without leaving the platform the rest of the team works in.
follow progress, risk and cost across projects and portfolios on live data.
see what is late, who is responsible and what waits for a decision.
build the schedule, run it for float and critical path, and measure variance against a baseline.
work their cards with checklists, documents and markups, and report progress from the field.
follow cost, income and resources, and keep the formal correspondence behind each matter.
issue models and drawings, link model elements to the work and exchange issues in BCF.
manage versions, flows, numbering, sharing and signatures.
work in the same platform with access limited to their role.
configure boards, forms, dictionaries, roles and integrations.
Projects change character as they go, and different modules come to the front. ISETIA stays the same place to work throughout, so what is set up at the start is still there at the end.
Portfolios, programmes and projects are created, often from a template. Administrators shape board types, forms and document flows, roles give each person the right access, and planners build the schedule, with resources and a budget behind it.
Drawings and models are issued through the Document Module, reviewed with markups and moved through approval flows. Models from several disciplines open together in the BIM Module, and problems found on a drawing or a model become tracked issues.
Site processes run on boards: requests, inspections, work orders, daily reports and meeting decisions move through stages with checklists. Progress is recorded against the schedule, formal letters are numbered and tracked, and risks and issues have owners and dates.
Planned and actual cost and income are linked to the work. Dashboards give each user a view of their own, and reports designed in the Analytic Module draw on the same live data, for one project or a whole portfolio.
Issued documents, their versions and their sharing history are already organised when the work is complete. Lessons learned are recorded with their expected savings, so the next project starts from what this one learned.
A first setup is a joint effort of ISETIA and your teams, and it follows one clear sequence. For a typical setup it takes two to three weeks.
A project rarely starts from a blank page. A new project can start from a template, schedules come in from Primavera and Microsoft Project files, and users, roles, finance lines, resources, cards and document metadata can be uploaded from Excel. Documents can be uploaded in bulk with their metadata.
You decide how much you do yourselves. Customers who receive administrator training can configure everything themselves, depending on their preference and the scope of the project. If you want ISETIA’s support during implementation, ISETIA provides it too.