One integrated platform. Six modules. One orbit.

Rocket IGS is one platform built from six modules — each owning a distinct part of the orbit. Deploy the full platform or assemble the modules you need. The orbit closes either way, because the modules were designed to work as one.

  • Mission Planning sets the strategy.
  • Ground Control runs the maintenance.
  • Flight Operations runs the production.
  • Mission Control surfaces the truth.
  • Arming builds the capability.
  • Administration holds it all together.

Deployment bundles

Find yourself in five seconds.

Three ways to deploy Rocket IGS. The dot grid on each card shows exactly which of the six modules you get. Pricing belongs in the conversation — every bundle ends in a demo.

Bundle 02

Strategic CMMS

Maintenance with a brain.

For asset-intensive operations that need disciplined maintenance plus the strategy maturity to drive it forward. Reliability isn't an accident; it's a program with a roadmap.

Modules included

Mission Planning
Ground Control
Flight Operations
Mission Control
Arming
Administration

4 of 6 modules

Built for
Utilities, hospitals, aviation MRO, mining, critical infrastructure, data centers — operations where assets are the mission but there's no production line to schedule.
Talk to Us
Most complete

Bundle 01

Full Platform

The complete Rocket IGS.

For manufacturing and process operations running the full orbit. Strategy through execution through measurement, every module pulling in the same direction.

Modules included

Mission Planning
Ground Control
Flight Operations
Mission Control
Arming
Administration

6 of 6 modules

Built for
Plants where OEE-to-EBITDA, CMMS, and strategy maturity all need to move together.
Talk to Us

Bundle 03

Core CMMS

The CMMS, done right.

For facilities and operations where reliable maintenance execution is the whole job. Built on the same architecture as the Full Platform, with a clear path to grow into Mission Planning when the time is right.

Modules included

Mission Planning
Ground Control
Flight Operations
Mission Control
Arming
Administration

3 of 6 modules

Built for
Facilities management, commercial real estate, hospitality, retail, distribution centers, government — operations where the CMMS is the platform.
Talk to Us
Included Optional add-on Not included

Or start here

Not ready to deploy?Start here.

Targeting is the diagnostic on-ramp to Rocket IGS — for organizations that want to see the gaps and design the roadmap before they commit to a platform deployment. It's an engagement, not a stripped-down fourth tier.

Bundle 04 — Engagement

Targeting

The reliability program, on paper. Set the goal before you launch the mission.

Run the assessment, see the gaps, get the report, build the roadmap. When you're ready to execute, the Mission is already named and the Orbit is already designed.

Modules included

Mission Planning
Ground Control
Flight Operations
Mission Control
Arming
Administration

3 of 6 modules

Built for

Consulting engagements, board-prep maturity scoring, pre-deployment due diligence, and operations that want to mature their thinking before they invest in the full system.

Talk to Us

One platform, not a stack

Instead of Maximo, not alongside it.

Rocket IGS is built as a complete platform. Customers running Maximo, SAP PM, or other legacy CMMS today will use Rocket IGS instead — not alongside. This is intentional.

The reason the orbit closes is because every module shares the same data model, the same Failure Mode library, the same Crew Member records, and the same reliability semantics. A federation of stitched-together systems can't deliver that.

On the roadmap: integration with adjacent enterprise systems — ERP, HRIS, identity providers. Not on the roadmap: integration with competing CMMS platforms.

Rocket IGS

One orbit. One data model. The loop closes.

A federated stack

Stitched-together systems. The gaps stay open.

The integrated orbit

Six modules. One closed loop.

Mission Planning sets direction. Ground Control and Flight Operations execute. Mission Control holds the center as the visibility hub. Arming and Administration form the support layer underneath.

  1. Mission Planning Sets direction
  2. Mission Control Visibility hub
  3. Ground Control Executes maintenance
    Flight Operations Executes production

  4. Support layer

    Arming Builds capability
    Administration Holds it together

Module catalog

Verify the depth.

Five operational modules, each owning a distinct part of the orbit. Expand any card to see what it does, what it ships with, who uses it, and how it connects to the rest of the platform.

The strategy brain. Annual Missions get defined here, 90-day Orbits get prioritized here, and the gap between where the plant is and where it needs to go gets measured with rigor. Built on ReliabilityX's Holistic Reliability Framework and the 30 Major Manufacturing Loss platform — the same methodology that has guided a decade of consulting engagements. Maturity assessments tell the truth. Loss Analysis converts truth to dollars. Missions and Orbits turn dollars into a roadmap.

Key capabilities

  • Holistic Reliability Framework — the assessment structure, loss platform, and discipline-spanning view (Maintenance, Operations, Engineering, Reliability) that have guided ReliabilityX consulting engagements since 2015, now built into the platform.
  • Maintenance & Reliability Maturity Assessments — Self, Role, and Full types
  • Role-based and anonymous surveys via Event Code (no user record required)
  • Question bank by focus area: Knowledge, Existence, Robustness, Discipline, Results
  • Loss Analysis with practitioner-grade 7 Big Losses definitions
  • EBITDA-linked loss accounting — every minute converted to dollars
  • Annual Missions with assigned ownership and KPI tracking
  • 90-day Orbits with task generation, resource allocation, and risk register
  • Mission template library by loss type — the orbit knows what it's hunting before you assign the first task

Who uses it

Mission Control (CFO, Plant Manager, GM, Operations Manager). Command Center (Reliability Engineer, CI / Opex Leader).

How it connects

  • Assessment findings flow into Orbits as prioritized improvement projects.
  • Loss dollars flow into Reporting in Mission Control.
  • Orbit tasks generate Work Orders in Ground Control.
  • Training gaps from assessments drive curriculum in Arming.

Every plant has a CMMS. Few have a CMMS that knows why each PM exists. Ground Control does. Every PM gets created because a specific Failure Mode justifies it. Every work order closes with the Failure Mode tagged. Maintenance stops being a calendar of tasks and starts being a defensible reliability strategy.

Key capabilities

  • Hierarchical asset & location structure with criticality classification
  • Two-tier reliability library — master library inherited and customized per asset type, with version pinning
  • ISO 14224-aligned classification — standardized codes on demand, hidden from users who don't need them
  • Functions, Functional Failures, Failure Modes, Causes & Effects for every asset class, out of the box
  • Two reliability views — function-down (RCM) and component-up (parts/spares coverage)
  • RPN scoring (Severity, Occurrence, Detection) refinable to your context
  • Per-task strategy selection — Active, Alternative, or Rejected with documented rationale
  • Hierarchy of Controls built in — mistake-proofing first, engineering controls second, training only as supplement
  • Symptom vs. diagnosis handled honestly — operators code what they see; the system bridges to the Failure Mode
  • PM scheduling — time-based, meter-based, condition-based — against the Flight Plan
  • Work order lifecycle with Failure Mode & Cause tagged at closure
  • Spare parts inventory with criticality-driven planning; sensor integration for CBM triggers

Who uses it

Command Center (Maintenance Manager, Maintenance Supervisor, Reliability Engineer). Flight Crew (Maintenance Technician, Frontline Engineer).

How it connects

  • Receives improvement work from Orbits in Mission Planning.
  • Sends Failure Mode-tagged equipment health signals to Flight Operations.
  • Feeds every closed work order back as a reliability data point.
  • Generates defects that route through Mission Control for visibility and assignment.
  • Pre-checks training credentials in Arming before high-risk task execution.
  • Powers analytics in Mission Control: failure-without-task gaps, MTBF/MTTR, Pareto rollups.

Where production gets scheduled, executed, and measured against design rate. Weekly Flight Plans set the schedule. Maneuvers handle the changes. Real-time loss tracking attributes every minute to a category — Breakdown, Process Failure, Setup, Startup, Minor Stop, Speed Loss, or Defect — and to a specific Failure Mode pulled from the asset's reliability library. Every minute of loss becomes a reliability data point the moment it's coded.

Key capabilities

  • Weekly Flight Plans by line, product, and shift
  • Plant-wide Flight Plan — production runs, changeovers, PMs, work orders, and inspection windows in one view
  • Real-time downtime capture with operator-driven coding
  • Downtime codes linked to the Failure Mode library — a Breakdown is Bearing Failure on Pump P-101
  • Operator coding assisted by the asset's failure mode library — smart defaults from what historically fails
  • 7 Big Losses categorization with practitioner-grade definitions
  • OEE calculation with availability, performance, and quality decomposition
  • EBITDA linkage on every loss minute; Loss-by-Failure-Mode Pareto rollups
  • Three event sources, one model — operator coding, sensor signals, or work order closure
  • Maneuvers for schedule changes and product changeovers; sensor-driven counters for rate and quality

Who uses it

Mission Control (Operations Manager). Command Center (Operations Supervisor). Flight Crew (Operator).

How it connects

  • Triggers Work Orders in Ground Control when downtime indicates maintenance is needed.
  • Surfaces Failure Mode-tagged losses to Mission Planning for orbit prioritization.
  • Feeds Reporting in Mission Control with live OEE rollups by Failure Mode, asset, and class.
  • Pulls operator certification status from Arming for compliance-gated tasks like CIL completion.

The visibility layer. Defects get tracked here, communications happen here, reports roll up here. Because every work order, downtime event, and PM execution carries Failure Mode linkage, Mission Control isn't just a reporting layer — it's where your reliability program proves itself, in dollars, in MTBF, and in the gaps between the strategy you have and the failures you're actually getting.

Key capabilities

  • Defect Management across inspections, audits, and operator-reported issues
  • Comms layer: chat, notifications, alerts, and Tier meeting threads
  • Reporting and dashboards across every module; KPI rollups by site, line, crew, asset class, orbit
  • Failure-without-task analysis — maintenance strategy gaps, named and quantified
  • Task-without-failure analysis — candidates for frequency reduction, deletion, or strategy change
  • Frequency recommendations from data — reconcile library defaults with observed MTBF and P-F intervals
  • ISO 14224-aligned rollups — MTBF, MTTR, failure rate, availability by Functional Failure, Function, Class, site
  • EBITDA-ranked opportunity list — every loss source ranked by annual EBITDA impact
  • Unified Flight Plan view — production and maintenance together, one picture of the week
  • Saved and scheduled reports with role-based distribution; full audit trail across the platform

Who uses it

Everyone. This is the cross-tier visibility layer.

How it connects

  • Reads from every other module.
  • Routes defects and corrective actions to Ground Control.
  • Surfaces KPI drift and reliability gaps to Mission Planning, where they become Orbits.
  • Captures Comms threads tied to specific defects, work orders, orbits, and Failure Modes.
  • Closes the loop: strategy → work → execution → Failure Modes → truth → the next strategy.

Training built into the platform, not bolted on. Courses, assignments, completion tracking, and the linkage between training records and work execution — so a technician can't close a task that requires certifications they don't have. Arming is the third tier in the Hierarchy of Controls, not the first: the supplement that locks in the why, not the substitute for engineering the right move into the work.

Key capabilities

  • Course library with role-based and asset-specific content
  • Training assignments with due dates and completion tracking
  • Certification expiration and automated renewal triggers
  • Skills inventory by Crew Member
  • Pre-task gating — work orders that require specific training credentials
  • Training gap analysis driven by Mission Planning assessment findings
  • Self-service browsing for crew-led development

Who uses it

Mission Control (Plant Manager assessing capability gaps). Command Center (Supervisors managing crew development). Flight Crew (taking and tracking their training).

How it connects

  • Receives gap analysis from Mission Planning assessments.
  • Gates work execution in Ground Control and Flight Operations.
  • Reports completion and compliance to Mission Control.

A note on Administration

Administration isn't a buyer-facing module — it's the foundational layer that ships with every deployment. Crew Member management, role-based access control, multi-tenant data isolation, audit logging, gamification, and system configuration. Available exclusively to the tenant company administrator.

Pricing belongs in the conversation

Deploy the full platform, or assemble the modules you need.

Tell us where your plant is today and we'll show you the orbit that closes the gap — bundle, module, or a Targeting engagement to map it first.

Talk to Us See the orbit