ISETIARequest Demo

Why ISETIAOne Platform For Project Management And Project Information

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.

What A PMIS And A CDE Do For A Project

PMISProject Management Information SystemCDECommon Data EnvironmentISETIABoth, one platform
What it managesThe management side of a project: the plan and schedule, responsibilities, risks and issues, cost and resources, and progress reportingThe project’s information: drawings, models and letters, each in one current version, with its history kept and access controlledBoth, on one platform, so the plan shows the information it depends on
The question it answersWhere 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 itThe project team for the detail; programme and portfolio managers for a consolidated pictureOwners, designers, contractors and suppliers, under rules on who may see, change and approve whatEveryone on the project, on the same record, each with the access their role needs
Typical recordsSchedule, responsibilities, risks and issues, cost and resources, workflow and approvals, and reportsEvery document, drawing and model with earlier versions kept, defined states and approvals, and a record of who changed whatOne current version of every document, card and letter
What it gives a projectVisibility while there is still time to act, clear accountability and early warning of late work and overspendLess searching and rework, fewer disputes, better collaboration across organisations and a cleaner handoverEvery item with an owner, a stage and a date, and the reasons behind a change kept with the change
On its ownInformation stays scattered, so the plan cannot show the information it depends onInformation is organised but cut off from the work, so nobody sees which task it belongs toNeither gap: the plan and its information live on one platform
How ISETIA joins themThe plan, owners, risks, cost and progress in one structure, for one project or a whole portfolioDocument states managed through flows and statuses, in line with ISO 19650The 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.

Common Data Environment

ISETIA is the one place where everyone on the project works on the same record, each with the access their role needs.

Project Owner

Sees progress, cost and risk across the portfolio, and approves what matters.

Designer

Issues drawings and models, and answers comments and markups in one place.

PMC

Runs the schedule, the reviews and the approvals on behalf of the owner.

Investment Operator

Receives the asset at handover with its documents, history and records.

Supplier

Receives purchase orders and submits documents and deliveries against them.

General Contractor

Plans and builds against the schedule, and reports progress from site.

Sub Contractors

Work on the cards assigned to them, with access limited to their own scope.

Project Team

Shares one current version of every document, card and letter.


Where Projects Lose Time

Large projects rarely go wrong because of one big mistake. They lose time and money in the small gaps between people, tools and records.

20%Longer than scheduled is typical for large projects, which can also run up to 80% over budgetMcKinsey & Company, Imagining Construction’s Digital Future
5.5Hours a week spent looking for project data, as construction professionals reportFMI and PlanGrid, Construction Disconnected
48%Of rework on U.S. construction jobsites comes from miscommunication and poor project dataFMI and PlanGrid, Construction Disconnected

Information Scattered Across Tools

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.

The Wrong Version In Use

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.

Problems Seen Too Late

Overdue work, unanswered letters and blocked tasks tend to surface in a meeting, when the damage is done.

No Record When A Decision Is Questioned

When a change is disputed months later, the history has to be rebuilt from e-mail.

Cost That Trails The Work

When budgets and actuals live in separate files, the picture arrives late and cannot be traced to the work behind it.

Every Project Reports Differently

If each project builds its own folders, numbering and reports, nobody can read across them.


How ISETIA Closes The Gap

Where time is lostHow ISETIA closes the gap
Information scattered across toolsIn 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 useISETIA 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 lateIn 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 questionedISETIA 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 workIn 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 differentlyISETIA gives every project the same structure beneath one portfolio, and reports designed once on live data can be reused for every project.


Why Project Teams Choose ISETIA

  • Complete, Not Stitched Together

    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.

  • A Trail Behind Every Decision

    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.

  • Planning With Depth

    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.

What ISETIA Helps You Avoid

  • Working from an out-of-date drawing or programme
  • Searching e-mail and shared drives for the one document that matters
  • Missing a reply that was due
  • Finding out about a cost overrun late
  • Rebuilding the history of a decision for a dispute or a handover
  • Entering the same data in several systems
  • Starting every project from a blank page
  • Repeating a mistake that the last project already paid for

Built For Every Role On The Project

Owners And Authorities

follow progress, risk and cost across projects and portfolios on live data.

Project Managers

see what is late, who is responsible and what waits for a decision.

Planners And Project Controls

build the schedule, run it for float and critical path, and measure variance against a baseline.

Engineers And Site Teams

work their cards with checklists, documents and markups, and report progress from the field.

Procurement And Commercial Teams

follow cost, income and resources, and keep the formal correspondence behind each matter.

Designers And BIM Coordinators

issue models and drawings, link model elements to the work and exchange issues in BCF.

Document Controllers

manage versions, flows, numbering, sharing and signatures.

Subcontractors And Partners

work in the same platform with access limited to their role.

System Administrators

configure boards, forms, dictionaries, roles and integrations.

One Platform From First Plan To Handover

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.

Design

  • Document Control
  • Markups & Approvals
  • Model Coordination
  • Clash Review
  • Transmittals
Preconstruction

Mobilization

  • Tender
  • Schedule
  • Roles & Permissions
  • Scope & Cost
  • Templates
Preconstruction

Field Execution

  • Progress Tracking
  • Daily Reports
  • Quality & Safety
  • Issues & Risks
  • Change Management
Construction

Handover

  • Rectification
  • As-Built Documents
  • Handover Packages
  • Lessons Learned
Post Construction

Operations

  • Commissioning
  • Maintenance
  • Asset Records
Post Construction
  • Set Up And Plan

    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.

  • Design And Coordination

    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.

  • Construction And Delivery

    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.

  • Control And Reporting

    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.

  • Handover And Learning

    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.

From Kick‑Off To Go‑Live, With Your Teams And Ours

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.

  • Kick-off: a meeting with your key personnel.
  • Work with your project teams.
  • Implementation of your processes in ISETIA.
  • Training.
  • Go-live.

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.