Turnaround Management System
One place to plan, approve and track plant shutdowns across ADNOC's sites. Built with IBM iX for one of the world's largest oil & gas companies.
Turnaround data was spread across sites and manual processes, with no single view of shutdowns or approvals.
Designed enterprise UI across web and mobile, four page templates and seven new design-system components.
A single source of truth for turnarounds, well received by stakeholders and aligned with ADNOC's standards.
Project overview
The “Turnaround Management System”, or TAMS for short is a project management platform designed by IBM iX for a prominent 12th Largest oil & gas company. Turnaround management system is a term in project management used to describe the revitalization of struggling procedures or companies by analyzing issues and creating strategic plans and implementing changes to restore efficiency.
Discipline: Product Design
Problem & solution
The problem
Managing turnaround operations across locations was complex and data-heavy. Existing tools lacked usability and a consolidated view, making it difficult to track shutdowns, manage approvals, and interpret operational data efficiently. The challenge was to present large volumes of operational data in a way that remained clear, consistent, and actionable for enterprise users.
The solution
TAMS introduced a centralized, enterprise-grade system offering a single source of truth for turnaround management. Structured dashboards, clear workflows, and data-driven reporting enabled teams to monitor and manage shutdowns more effectively across locations.
Users & lifecycle
Fills in process forms (scope, budget, risk, materials) and submits them for review.
Desktop · edit
Challenges scope, then approves, rejects or returns requests, often away from a desk.
Desktop + mobile · approve
Track progress and KPIs across sites; processes they don't own open read-only.
Desktop + mobile · view
The turnaround lifecycle
Long-term T/A plans, team formation, strategy
Scope list, budget, long-lead materials
Scope freeze and challenge, contracting
Procurement, HSE plans, job packs
Progress monitoring, emergent jobs
Close-out, cost review, lessons learned
Architecture
Every process fits one of four templates. That kept screens consistent and let engineering render pages faster with template engines.
TEMPLATE 01
KPIs and every turnaround, pre-filtered to the user's company and site.
TEMPLATE 02
A phase-by-phase checklist that highlights what's assigned to you.
TEMPLATE 03
Long forms split into sections with a sticky stepper; tabs hold sub-forms.
TEMPLATE 04
A read-only check with the approval chain and role-based actions.
Key screens
We focused on digitizing manual processes by creating a system that structures turnarounds into events, allowing for assigning teams, flagging issues, generating reports and logging lessons learned
Company, site and plant come pre-selected. An “assigned to me” toggle, colour-coded KPIs and attention flags surface what needs action first.
Planners think in rows, leadership thinks in time. The Gantt view colour-codes all six phases, so overlapping shutdowns stand out.
All six phases side by side. Finished work is ticked, your tasks are outlined in blue, and processes you can't edit open read-only.
Process status card
Default
In progress
Assigned to you
Awaiting approval
Returned
Completed
Phase complete
Not applicable yet
To create a new turnaround request, the user must assign complexity, date, budget, affected units and risk factors
Managers retain the right to challenge the scope of a turnaround, exclude work orders, and monitor the previous reviews and remarks
Before scope is frozen, managers go through each work order line by line.
Include or exclude each one from the current turnaround.
Consequence, risk metric and mitigation stay in the row.
A confirmation checkbox records the manager's sign-off.
Every editable table exports for documentation and reporting.
Some processes pull data from systems like SAP for the team to confirm; report pages turn process data into dashboards.
High-fidelity flows
The end-to-end flows behind a turnaround: proposing a budget, approving it, scoping the request and planning the phases. Each one plays through the real high-fidelity screens.
Expenditure items, documents and justification live in one editable table. Attachments, comments and the review workflow are set up before submitting.
The reviewer and approver see the workflow, the proposal and every document in one pane, and act with a comment and supporting files.
Site and plant come in first, then endorsing authorities, jobs and functional locations. TAMS flags similar shutdowns before a duplicate is created.
Phase dates are calculated from the chosen complexity, then milestones, KPIs and targets are set before the plan goes for approval.
Every screen from these flows. Scroll sideways, and click any screen to see it full length.
Design system
The existing ADNOC DEEX table couldn't handle editing: input fields were too big and rows too tall. We rebuilt it as a modular component with inline editing, search, sorting, pagination and table- and row-level actions.
Before
After · anatomy
Notes, @mentions and threads live on each process, so collaboration stays inside the product.
Also added to the DLS
Mobile
TAMS relies on large tables, which are tedious on small screens. So mobile is deliberately limited to tracking and manager approvals, with processes shown read-only.
An inbox grouped by site leads to the request summary, the risk register and a sticky Approve / Reject / Return bar.
Outcome
Stakeholders
Designs were positively received by stakeholders.
Standards
UI met ADNOC's enterprise standards and governance requirements.
Workflows
Contributed to improved clarity and usability across turnaround management workflows.
My contribution