SIMOPS Planner
Plan Simultaneous Operations: build a matrix of permitted operations (MOPO) marking every activity pair Go / Restricted / Prohibited, tick off the required controls per activity, list planned activities with time windows, and flag clashes before they happen. Eight industry templates — oil & gas, refinery turnaround, construction, marine, mining, power & utilities, warehouse and aviation. Saved on your device; export CSV, PDF, PNG or JSON.
Open SIMOPS Planner →What is the SIMOPS Planner?
A free tool for planning Simultaneous Operations (SIMOPS) — where two or more activities run at the same site and time, such as a drilling rig working next to a live production or pumping station. Build a Matrix of Permitted Operations (MOPO) that marks every pair of activities as Go, Restricted or Prohibited — activities can be added, renamed or deleted at any time, and the matrix scrolls with frozen headers when it grows. Record the controls each pair needs as a per-activity checklist, one control per line with its own tick-box to confirm it is in place, then list the activities you have planned with their time windows so the tool can flag any clash before it happens. Seed it from one of eight built-in industry templates — oil & gas, refinery turnaround, construction, marine, mining, power & electrical utilities, warehouse & logistics or aviation — or start blank. Everything is saved on your device and runs offline. It is a planning aid, not a live monitoring or permit-approval system.
How to use SIMOPS Planner
- Pick a template — Choose one of the eight industry templates to pre-fill the activity list and default compatibility rules, or select Blank / custom to build your own.
- Set up the operation — Enter the operation name, location, SIMOPS controller (the single point of accountability) and date so the exported plan is properly headed.
- Tune the MOPO matrix — Click any cell to cycle the two activities between Go, Restricted and Prohibited. "+ Add activity" drops a new row in instantly as "New activity" — rename it with the ✎ button, or delete a row with ×. With many activities the matrix scrolls while the activity names and header row stay frozen, and the full-screen button in the card header expands the whole matrix to fill your screen.
- List planned activities — Add each planned activity with its type, area, start and end time. When two overlap in time and their types are Restricted or Prohibited, the Clash check flags them with the required control.
- Work through the required controls — In the Required controls accordion, open an activity to see every restricted or prohibited pair it is part of. Each control sits on its own line with its own checkbox — tick it once it is in place, edit the wording inline, remove it with ×, or add more with + Control. Use Open all / Collapse all to manage the list.
- Export — Use the Download menu to save the plan as a print-ready PDF (a summary page, the MOPO on its own landscape page sized to fit the full matrix, and the controls checklist — all selectable text), a CSV, a PNG image, or a re-importable JSON file you can reopen or share.
Frequently asked questions
What is a MOPO?
A Matrix of Permitted Operations. It cross-references every pair of concurrent activities and states whether they can run together (Go), only with controls (Restricted), or never (Prohibited). It is the core control document for any SIMOPS.
How does the clash check work?
It compares the start and end times of your planned activities. When two overlap in time and their activity types are marked Restricted or Prohibited in the matrix, it raises a clash and shows the required control, so conflicts are visible before work starts.
How are the required controls organised?
As an accordion grouped by activity: open an activity to see every restricted or prohibited pair it belongs to, and under each pair a checklist of individual controls — one per line, each with its own tick-box to mark it in place. You can edit a control's wording inline, remove it, or add more with + Control. A pair appears under both of its activities and edits sync between the two. Tick states are saved with the plan and exported in the CSV, one row per control.
Can I use it for industries other than oil and gas?
Yes. The engine is generic and ships with eight templates — oil & gas, refinery turnaround, construction, marine, mining, power & electrical utilities, warehouse & logistics and aviation — plus a blank one. You can rename, add or remove activities and rewrite every rule, so it fits any SIMOPS.
Is my data uploaded anywhere?
No. Everything is worked out and saved entirely in your browser, and stays on your device between visits. Export a JSON file if you want a backup or to share the plan.
Does it replace a permit-to-work or live monitoring system?
No. It is an offline planning aid for building the matrix and spotting clashes early. It does not approve permits, track live status or read sensors — those belong to your site's control-of-work systems.
Tips
- Name a SIMOPS controller (single point of accountability) in the setup so the exported plan shows who can stop either operation.
- Give every planned activity a start and end time — the clash check only fires on activities that overlap in time.
- Write real, specific controls on each restricted pair — one per line (gas monitoring, fire watch, exclusion zone) — and tick them off as they are put in place, so the plan shows live readiness, not just a colour.
- Export the JSON to back up or hand over a plan, and the PDF or CSV for the SIMOPS pack and the daily coordination meeting — the PDF gives the MOPO its own full-size landscape page with the controls checklist alongside.