Production Operations (Startup & Shutdown) App
A startup and shutdown app coordinates unit startups and planned shutdowns across operations, maintenance, and technical teams, with readiness gates, step sign-offs, and a full record of who cleared what and when. Kissflow runs that coordination without another spreadsheet on a control room wall.
Trusted by energy operators worldwide
The most hazardous hours in a plant are the ones with the least structure
Steady-state operation is the safest part of the cycle. Startups and shutdowns are where process safety incidents concentrate, because the plant is outside its normal envelope, procedures are long, and several teams have to hand off cleanly under time pressure. The coordination tool at most sites is a printed sequence, a marked-up spreadsheet, and a radio.
Kissflow runs the sequence as a coordinated application. Each step has an owner, a prerequisite, and a sign-off, so a step cannot be marked complete while its prerequisite is open. Readiness gates hold the sequence at defined points until every condition for that gate is confirmed, which is exactly where informal coordination tends to skip. Progress is visible live to the control room, the field, and the shift coming on.
The record assembles as the sequence runs. When a pre-startup safety review, a shift handover, or a post-event review needs to know what condition the plant was in and who confirmed it, the answer comes from the same board the operation ran on.
The plant is least normal when the coordination is least structured
The sequence lives on paper
A printed procedure and a marked-up spreadsheet are the coordination tools for the most hazardous hours in the cycle.
Steps are signed off out of order
Nothing prevents a step being marked complete while what it depends on is still open.
Readiness gates are confirmed verbally
The hold points that matter most are cleared by conversation under time pressure.
Status is known by whoever is in the room
The field, the oncoming shift, and the control room hold different versions of where the sequence has reached.
Six process modules
Every module ships with default sequences, readiness gates, sign-off rules, and dashboards. Configure each one to your units in the visual builder.
Sequence and step management
Startup and shutdown sequences held per unit with steps, owners, prerequisites, and expected durations, versioned so the sequence in use is the current one.
Prerequisite enforcement
Steps that cannot be signed off while their prerequisites are open, so sequence integrity does not depend on the person holding the printed copy.
Readiness gates
Defined hold points where the sequence stops until every condition is confirmed, with the confirming role recorded against each condition.
Cross-team coordination
Operations, maintenance, and technical teams working the same board with their own views, so handoffs happen on the record rather than over the radio.
Live progress view
A live view of sequence position, open steps, held gates, and elapsed time against expectation, visible to the control room and the field.
Event record and review
The full record of steps, sign-offs, holds, and deviations retained for pre-startup safety review, shift handover, and post-event review.
From request to system of record in four steps
Plan
The startup or shutdown sequence is set up for the unit with its steps, owners, prerequisites, readiness gates, and expected durations, from the current versioned procedure.
Assign
Steps are distributed to operations, maintenance, and technical owners with their dependencies, so every team knows what is theirs and what it waits on.
Execute
Progress moves on a single live board with prerequisite enforcement and readiness gates holding the sequence until conditions are confirmed.
Close-out
The event is signed off and the full record of steps, holds, sign-offs, and deviations is archived against the unit for review and for the next cycle.
What changes when startup and shutdown runs on Kissflow
| Process | Before Kissflow | On Kissflow |
|---|---|---|
| Sequence control | A printed procedure and a marked-up sheet | A live board with owners and prerequisites |
| Step integrity | Depends on the person holding the copy | Prerequisites enforced before sign-off |
| Readiness gates | Confirmed verbally under time pressure | Held until every condition is confirmed on record |
| Cross-team handoff | Over the radio | On the board, with the handoff recorded |
| Live status | Known by whoever is in the control room | Visible to control room, field, and oncoming shift |
| Event record | Reconstructed after the fact | Assembled as the sequence runs |
Connects to the systems your operation already runs on
.svg){kind=logo}
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
Built for the hours when the plant is outside its envelope
Prerequisites are enforced, not trusted
A step cannot be signed off while what it depends on is still open, which is the failure mode a printed sequence cannot prevent.
Gates hold until conditions are confirmed
Readiness gates are where informal coordination skips. Making them explicit hold points is the control.
One board across every team
Operations, maintenance, and technical work the same sequence, so a handoff is a recorded event rather than a radio call.
A coordination layer, not a control system
Kissflow coordinates the people and the sequence. Your control system runs the plant, and Kissflow does not touch it.
Governed from day one
Single sign-on, role-based access, and a timestamped audit log are how the app is built. Kissflow runs in the business-process layer, segmented from the OT and control network.
Live in weeks, not a program
Configure in the visual builder, or describe the sequence and let the AI Builder generate the app. Delivery moves from weeks to days.
Related apps
SIMOPS coordination tracker
Coordinate simultaneous operations with conflict identification and controlled authorization across teams.
Asset reliability and turnaround orchestration
Coordinate turnaround scope, work packs, readiness reviews, and close-out on one board.
Shift logbook with approval
Record shift events and handover with supervisor approval and a searchable history.
We help operations leaders run the sequence on a board instead of a radio
.gif)
“If a company cannot enable everybody to use AI, they will never get the true benefit of AI. Platforms like Kissflow allow us to put that capability in the hands of our users in a safe way.”
Vagesh Dave
GVP & CIO at McDermott International, Ltd
See The Full Story
“Advanced automation of all processes is easy to set up. I cannot imagine how to manage workflows without this software.”
Tanay Tiwary
Global Head - Digitalization & Business Improvement
See the Full Story
“Kissflow supports rapid application development by building a working application prototype in the shortest amount of time.”
Maria Theresa Cabigon
CIO, SN Aboitiz Power Group
See The Full Story
See what Kissflow can do for you
Talk to usGot questions? We're here to help.
Get SupportIt coordinates unit startups and planned shutdowns across operations, maintenance, and technical teams, holding the sequence with owners, prerequisites, readiness gates, and step sign-offs, and retaining the full record of the event.
No. Kissflow coordinates the people and the procedure in the business-process layer. It does not read live process signals, control equipment, or operate on the control network.
Prerequisites are enforced, so a step cannot be marked complete while what it depends on is still open, and readiness gates hold the sequence until every condition for that gate is confirmed.
The record of steps, sign-offs, holds, and deviations is assembled as the sequence runs, which is the evidence a pre-startup safety review and a post-event review both draw on.
Yes. Fields, categories, routing rules, and escalation thresholds are configured by the process owner in the visual builder, and every change is written to the same audit log as a manual edit.
No. Kissflow runs in the business-process layer alongside the systems you already own and connects to them through APIs and integration connectors. It does not replace your EHS suite, your ERP, or your maintenance system, and it does not operate inside the control system.
No. Kissflow AI maps natural language to platform metadata and produces an inspectable blueprint, so every app is auditable and the process owner can maintain it.
Kissflow is certified to SOC 1, SOC 2, SOC 3, ISO/IEC 27001, HIPAA, GDPR, and CCPA, hosted on Google Cloud with data residency in the US, EU, APAC, and Oceania.
