Questions answered.
Most of what buyers ask about Rocket IGS lives on this page. If the question you're asking isn't here — or if you want to go deeper than the answer allows — request a Mission Briefing. That's how we go deep.
- Eight categories
- Sixty-plus questions
- ReliabilityX methodology throughout
No questions match your search. Try a different keyword.
About Rocket IGS
-
Rocket IGS is an integrated industrial operations platform for plant performance and reliability. The name stands for Internal Guidance System — the platform's job is to keep your operation on target by collecting losses, analyzing them, recommending the work to eliminate them, and closing the loop between strategy and daily execution. One platform spanning maturity assessments, strategy development, CMMS, production scheduling, OEE tracking, training, and reporting. Built on the practitioner methodology developed at ReliabilityX, the consultancy behind the platform since 2015.
-
Three audiences. Manufacturing and process operations running production lines need all three core modules — Mission Planning, Ground Control, and Flight Operations — plus the methodology layer (Recommendations and Arming) that the full platform unlocks. Asset-intensive operations like utilities, hospitals, aviation MRO, and critical infrastructure typically need Mission Planning and Ground Control (the reliability core without production scheduling). Facilities and operations focused on maintenance execution — commercial real estate, hospitality, retail, distribution — can deploy Ground Control on its own. Within each, Rocket IGS is built for the team tiers that run plants: Mission Control (top leadership), Command Center (middle management), Flight Crew (frontline operators and technicians), and Mission Stakeholders (Quality, Safety, Finance, Engineering).
-
Rocket IGS is methodology built into software, not software designed to capture maintenance data. Every Failure Mode in the library, every assessment question, every loss definition, every Mission template comes from a decade of ReliabilityX consulting engagements with real plants. Beyond that heritage, three architectural choices set it apart. First, every PM and every work order is anchored to a specific Failure Mode in a reliability library — so maintenance becomes a defensible strategy, not a calendar of tasks. Second, the library defaults to mistake-proofing and engineering controls (not training) for operator-induced and maintenance-induced failures, which is the opposite of how most CMMS platforms approach the problem. Third, the platform is one integrated system rather than a federation of bolt-ons, so the Failure Modes in maintenance, the downtime codes in production, and the opportunities in strategy all reference the same data model.
-
Other industries too. Flight Operations (production scheduling and OEE) is manufacturing-specific — but Mission Planning and Ground Control work for any asset-intensive operation: utilities, hospitals, data centers, aviation MRO, mining, telecom infrastructure. Customers in those sectors typically deploy the two modules without Flight Operations. Ground Control alone scales further down to facilities, hospitality, retail, distribution, government — customers focused on maintenance execution without a reliability program in place yet. The architectural choices that make Rocket IGS different — Reliability & Loss Library, Hierarchy of Controls, integrated platform — apply equally across all configurations. ReliabilityX has consulted across all of these sectors; the platform reflects that breadth.
-
Yes — that's one of the biggest practical differences from a typical CMMS-plus-MES stack. The Flight Plan is the unified weekly schedule for the plant. Production runs, changeovers, PMs, work orders, and inspection windows all sit in a single view. This isn't a feature bolted on; it's a consequence of the architecture. Because Flight Operations and Ground Control share the same data model, the schedule is one schedule. The recurring problem in industrial plants — operations planning the week with no visibility into maintenance, maintenance planning the week with no visibility into production — gets solved by not having two schedules to begin with.
-
Worth being explicit. Rocket IGS is not an ERP — it doesn't replace SAP or Oracle for finance, procurement, or HR. It's not an MES in the classic sense — it doesn't manage recipes, batch genealogy, or quality lab data. It's not a generic project management tool — Missions and Orbits aren't a substitute for Asana or Jira. It's not a BI platform — it has reporting, not a self-service dashboard builder. What it is: the operating system for plant performance and reliability, sitting between your ERP and your shop floor.
About the company
-
Rocket IGS is a product of ReliabilityX — a maintenance and reliability consultancy established in 2015. ReliabilityX has spent a decade running assessments, loss analyses, FMEA programs, training engagements, and full implementations across manufacturing plants, utilities, and facilities. Rocket IGS is the software platform that operationalizes that decade of practitioner experience: the assessments, the loss frameworks, the Failure Mode libraries, and the methodology that's been refined in real plants are now built into a multi-tenant platform that customers can deploy and run themselves.
-
The same team behind ReliabilityX. The platform is led by reliability and operations practitioners — three owners, each of whom spent 25+ years on the plant floor before founding the consultancy. Nobody at ReliabilityX was ever a career consultant first; they are practitioners who became consultants, not consultants who studied reliability. Two CMRP of the Year award winners — both owners of the company. That distinction — recognition from the Society for Maintenance & Reliability Professionals for sustained excellence in the discipline — is unique to ReliabilityX in the industry.
-
Both. ReliabilityX continues to offer the consulting services it's known for — assessments using the Holistic Reliability Framework, loss analyses on the 30 Major Manufacturing Loss platform, training and coaching, and full implementation engagements. Rocket IGS is a complementary offering: customers who want to internalize the methodology and run it themselves use the platform; customers who want practitioner support alongside the software engage ReliabilityX consulting as well. The two are designed to work together but can be purchased independently.
-
Yes — and many customers do. The typical pattern: ReliabilityX runs an initial assessment using the Holistic Reliability Framework, the findings inform the configuration of Mission Planning during Countdown, and ReliabilityX consultants stay engaged through the first Orbit to coach the team through change management. The platform becomes the system of record; the consultancy becomes the accelerant. Inquire during the Mission Briefing if you're interested.
-
The platform is enrolling its initial Launch Partners now. ReliabilityX has worked with organizations across manufacturing, utilities, and facilities over the past decade — including Little Potato Company, Evergy, and others — and several are evaluating the platform as their next-generation reliability system. We'll publish customer-named case studies for the platform once Launch Partners have run a full Orbit. The consulting work has its own case studies on reliabilityx.com.
-
ReliabilityX is a remote-first practitioner consultancy with team members distributed across the United States, available to customers across North America, Latin America (with Spanish-language support), and beyond. Onsite work happens at customer plants during deployment and assessment engagements; otherwise, work happens through direct communication channels.
-
ReliabilityX is a privately-held, self-funded business. Rocket IGS is a product of ReliabilityX, not a separately-funded venture. The platform's roadmap is set by the practitioner team and the Launch Partners — not by external pressure to ship features for the next round.
-
Visit reliabilityx.com for the consultancy's full offering — services, case studies, training catalog, the Maintenance and Reliability Best Practices framework, the Reliability Xchange community, Captain Unreliability® content, podcasts, blog, and videos. You'll also find publicly available training courses (virtual and self-paced) covering Planning and Scheduling, MRO, FMEA, RCFA, TPM, and Machinery Lubrication Fundamentals — many available in Spanish as well as English.
The methodology
-
Two-tier architecture. Rocket IGS maintains a master library of asset classes, Functions, Functional Failures, Failure Modes, Causes, Effects, and recommended Tasks — built on ISO 14224 standards and on a decade of ReliabilityX consulting engagements in real plants. Each tenant inherits a copy when they adopt an asset class, then customizes it: refine RPN scores, suppress inherited Failure Modes that don't apply, add tenant-specific Failure Modes, and select per-task strategies (Active, Alternative, Rejected) with documented rationale. Library upgrades are explicit — you pin to a version and choose when to upgrade. The library is content; your tenant configuration is your strategy. The two stay separate so neither contaminates the other.
-
Yes. Asset classifications, Failure Modes, Failure Mechanisms, and Cause codes all align with ISO 14224 — the standard for collection and exchange of reliability and maintenance data in petroleum, petrochemical, and natural gas industries (and increasingly applied across all asset-intensive sectors). The codes are available on demand but hidden from users by default. Practitioners who don't need to speak in codes don't have to; auditors and benchmarking exercises that require ISO 14224 alignment can access them at will.
-
The Hierarchy of Controls is the principle that for failures driven by human action (operator-induced, maintenance-induced), the strongest remedy is to make the wrong move physically impossible — mistake-proofing. The next-strongest is engineering controls (PLC interlocks, recipe locks, supervisor sign-off gates). Training is the weakest, with observed occurrence reduction roughly an order of magnitude smaller than mistake-proofing or engineering controls. Rocket IGS's library defaults to mistake-proofing first because that's what the data says actually moves the needle. Training has a role — locking in why the controls exist — but it's a supplement, not a substitute for engineering the right move into the work itself. This is a principle ReliabilityX has applied across hundreds of consulting engagements before it ever became a platform default.
-
Sure. A common operator-induced failure: wrong lubricant grade applied to a bearing during PM. The training answer: certify all maintenance techs on lubricant identification, review the SOP quarterly. The mistake-proofing answer: keyed grease guns that only fit specific fittings, color-coded lubricant containers that match the asset's labeled receiver. The training answer asks operators to remember; the mistake-proofing answer makes the wrong lubricant physically impossible to apply. Rocket IGS's library recommends the mistake-proofing remedy first and reserves training as the supplement that explains why the controls exist.
-
They don't have to. Operators code what they see — the symptom: "line stopped," "weird vibration," "product jammed." The platform bridges from symptom to underlying Failure Mode via a candidate library, surfacing the most likely Failure Modes for that symptom on that asset and letting maintenance resolve the diagnosis when they investigate. This is the opposite of platforms that demand operators pick a diagnosis from a list and end up with garbage data. Operators get the codes they can honestly use; the diagnostic discipline happens where it belongs.
-
Yes. The tenant tier of the library is yours to refine. Add Failure Modes that exist on your assets but not in the master library. Suppress modes that don't apply. Adjust RPN scores to your context. Select per-task strategies — Active, Alternative, Rejected — with rationale that survives the next reorg. Your customizations don't contaminate the master library, and library updates don't override your tenant-level choices.
-
RPN is the product of Severity, Occurrence, and Detection — each on a defined scale with anchor scores. The library carries default RPN values for every Failure Mode that you can refine to your context. Where Rocket IGS differs from most FMEA tools is the anchor discipline: Severity anchors are explicit, Occurrence anchors are tied to observed frequency, Detection anchors reflect actual detection probability rather than confidence-by-assertion. The intent is that two reliability engineers scoring the same Failure Mode arrive at scores within a defensible range, not at whatever each of them feels in the moment.
-
Mission templates are playbooks tailored to specific loss types. When Loss Analysis surfaces an opportunity, Mission Planning instantiates a template that fits — breakdowns trigger a Breakdown FMEA Review playbook, minor stops trigger an Observation-and-RCA playbook, raw material quality issues trigger an Inspection Program playbook. The template ships with task types, recommended task sequence, suggested resource allocation, and KPI baselines. You don't start a 90-day Orbit from a blank page; you start from a playbook that knows what kind of loss it's fighting. The templates reflect the structure ReliabilityX consultants have used in implementation engagements for a decade.
-
Yes, and the library is opinionated about it. For bearing, gearbox, and lubrication Failure Modes, the library includes both vibration analysis and ultrasound as strategy candidates — and defaults ultrasound to the primary recommendation because it's cheaper to deploy in-house (handheld instruments, lower training threshold) and detects lubrication condition that vibration analysis often misses. Tenants who already have a deployed vibration program override the default and run both as complementary technologies.
-
Yes — that's a deliberate design choice carried over from ReliabilityX's 30 Major Manufacturing Loss platform. The 7 Big Losses in Rocket IGS are: Breakdowns (failures requiring parts changes), Process Failures (failures resolved without parts), Setup and Adjustments, Startup Losses (yield and conformance losses during line startup and changeover), Minor Stops (under approximately 10 minutes, auto-categorized), Speed Losses (running slower than design rate), and Defects (quality losses converted to lost time). Most platforms use vendor-defined categories that don't survive contact with a real plant floor. Rocket IGS's categories match how reliability engineers and operations supervisors actually code losses when they're being honest about what happened.
-
By whether parts were changed. Breakdown: the line stopped, maintenance came out, a part got replaced, the line restarted. Process Failure: the line stopped, maintenance came out, an adjustment or reset got it running, no parts changed. This distinction matters because it routes different work to different Orbits — Breakdowns lead to FMEA-review missions, Process Failures often lead to procedure-and-training missions. The platform enforces the discipline by requiring parts-consumption data on work order close.
-
The P-F interval is the time between when a Failure Mode becomes detectable (Potential failure) and when the asset actually fails (Functional failure). It governs how often a condition-based PM needs to run to catch the failure before it occurs. The platform observes actual P-F intervals as failures recur in your data and recommends task frequency adjustments accordingly. If a bearing is showing detectable wear 30 days before failure and your inspection interval is 60 days, the platform flags the gap and recommends tightening to 21 days for a margin of safety.
-
Yes — Reliability-Centered Maintenance is one of the two reliability views the platform supports. The function-down view (RCM) starts from what an asset is supposed to do, identifies how it can fail to do it, and works toward the maintenance tasks that prevent the failure. The component-up view (parts-and-spares) starts from the asset's components and works toward the spares each Failure Mode requires. Most platforms support one or the other. Rocket IGS supports both and lets the same Failure Mode appear in both views because in real plants, that's how reliability work actually gets done.
-
The Holistic Reliability Framework is ReliabilityX's canonical methodology — the assessment structure, the loss platform, and the discipline-spanning view (Maintenance, Operations, Engineering, Reliability) that has guided the consultancy's work for a decade. Rocket IGS implements the same framework in software. The Mission Planning assessment uses the same focus areas (Knowledge, Existence, Robustness, Discipline, Results). The Loss Analysis uses the same 30 Major Manufacturing Loss platform with the same 7 Big Losses categorization. The mission templates reflect the same engagement patterns. When you buy Rocket IGS, you're not buying a software vendor's interpretation of reliability methodology — you're buying the methodology itself, in software form.
The product and modules
-
Five operational modules plus Administration. Mission Planning (assessments, strategy, missions, orbits, loss analysis). Ground Control (CMMS — assets, work orders, PMs, failure modes, reliability library). Flight Operations (production scheduling, OEE, loss tracking — manufacturing only). Mission Control (comms, defect management, reporting). Arming (training). Administration (tenant admin — Crew Members, security, configuration; ships with every deployment).
-
The platform is mobile-responsive. Operators and technicians can use Rocket IGS on tablets and phones for the work that happens on the floor — downtime capture, work order execution, inspection completion, defect reporting. Native mobile apps for iOS and Android are on the roadmap; the web-responsive version covers the same workflows today.
-
Limited offline support today, expanding post-launch. The current state: if a tablet loses connectivity during a work order, the operator can complete the task offline and sync when connectivity returns. Full offline mode (long-duration disconnected operation) is on the roadmap. For most plant environments with WiFi coverage, this isn't a daily concern.
-
Standard reports across every module — work order throughput, PM compliance, OEE by line/product/shift, MTBF/MTTR by asset and Failure Mode, defect Pareto, EBITDA-ranked opportunities, Orbit progress against milestones, training compliance, audit trails. Reports are filterable by site, line, asset, time period, and Crew Member. Saved views and scheduled distribution are supported.
-
Yes, within boundaries. The platform includes a report builder that operates over the same data model the standard reports use. For deeper analytics — custom dashboards, ML models, cross-tenant benchmarking — most customers export to a BI tool. The platform supports CSV export today and direct database connection (read-only) on a per-tenant basis.
-
Yes — across multiple channels. Email notifications for work order assignments, PM due dates, defect escalations, orbit milestones, and approval requests. In-platform notifications for everything above plus comms threads. SMS notifications are available for high-priority alerts (breakdowns on critical assets, security events). Each Crew Member can configure their notification preferences per channel per event type.
-
English at launch. Spanish is the priority second language and is on the near-term roadmap, with the FMEA library content (Failure Modes, Causes, Tasks) being translated in parallel with the UI. This builds on ReliabilityX's existing Spanish-language training catalog. French, Portuguese, and German follow as customer demand warrants. For multinational customers, the platform supports tenant-level language preferences with future support for site-level overrides.
-
The current generation of Chromium-based browsers (Chrome, Edge), Firefox, and Safari — the most recent two major versions of each. Internet Explorer is not supported. Legacy browser support gets sunset as the underlying frameworks evolve; if a customer's plant IT requires a specific browser, raise it in the Mission Briefing.
-
Logo and limited color customization at the tenant level. Full white-label rebranding (your URL, your name on every screen) is not offered today and not on the near-term roadmap — Rocket IGS is a brand we're building deliberately, and white-labeling would dilute that for everyone.
Deployment and onboarding
-
The pre-launch phase — Countdown — typically runs 6–12 weeks for a single-module, single-site deployment and 12–24 weeks for a multi-module or multi-site full platform deployment. Faster is possible for assessment-only configurations; longer for complex multi-site rollouts with significant data migration. Countdown is structured so Launch (go-live) is not a leap into the unknown — by that point, your crews have been trained, your data is loaded, and the platform is configured for your operation.
-
Four phases. Configuration — your assets, your sites, your Crew Members, your reliability library tenant tier. Data migration — existing CMMS data, asset registers, PM histories, training records where available. Training — Arming module rollout to all tiers with role-specific curriculum, drawing on ReliabilityX's established training catalog. Pilot — a single line, asset class, or site running on the platform before full deployment. Launch happens when the pilot proves the platform fits the work.
-
Yes. Most multi-module deployments include a piloted phase as part of Countdown. The pilot scope depends on your operation — sometimes a single production line, sometimes a single critical asset class, sometimes a single site within a multi-site rollout. The pilot's job is to surface configuration mismatches before they propagate, not to be a separate sales artifact.
-
Asset hierarchy and criticality ratings, PM history (3–5 years if available), work order history (3+ years if available), spare parts inventory, Crew Member roster with roles, training records where available, and existing reliability program documentation (FMEAs, RCMs, criticality analyses) if any. We bring the master library, the platform configuration, and the mapping toolkit; you bring the operational reality. ReliabilityX has run this data exercise hundreds of times — the migration toolkit handles the standard messes.
-
Most of it is. Part of Countdown is cleaning and rationalizing the data as it migrates — asset hierarchy normalization, Failure Mode mapping from your existing codes to the standardized library, PM frequency review against the library defaults. Messy CMMS data is the rule, not the exception. The migration toolkit handles the standard messes; complex situations (failed prior deployments, multi-system histories, units in different languages) get manual review.
-
Yes — Mission Planning is sold as a standalone module exactly for this use case. Run the maturity assessment, see the gaps, get the report, design the roadmap, no operational modules required. If the assessment surfaces a strong case for deployment, you add Ground Control and Flight Operations (or take the full platform) with the Mission already named and the Orbit already designed. This mirrors how ReliabilityX has structured consulting engagements for a decade — assess first, deploy second.
-
Two paths. If "not ready" means "we don't have a reliability program," start with Mission Planning as a standalone — run the maturity assessment, see the gaps, design the roadmap before committing to operational modules. If "not ready" means "we have one but it's underused," pair Mission Planning with Ground Control for a guided rebuild of the maintenance program using the Reliability & Loss Library.
-
The recurring killers: configuration that doesn't match the work, data migration that introduces more errors than it preserves, training that's a one-hour walkthrough instead of curriculum, and a go-live that happens before the crews trust the platform. Rocket IGS counters each: configuration is collaborative, not template-pushed; data migration is rationalized with library defaults, not transferred 1:1; training lives in Arming and runs through Countdown, not just before Launch; and the pilot phase makes go-live the validation of a working system, not the bet on one. ReliabilityX has been on the cleanup side of those failed deployments for a decade — the platform's deployment discipline is what those lessons look like in software.
Architecture, integration, and security
-
Not in release 1, and that's deliberate. Rocket IGS is built as a complete platform — the reason the orbit closes is because every module shares the same data model, the same Failure Mode library, the same Crew Member records. Customers running SAP PM or Maximo today will use Rocket IGS instead of those systems, not alongside. Integration with adjacent enterprise systems — ERP, HRIS, identity providers — is on the roadmap. Integration with competing CMMS platforms is not.
-
SSO via SAML 2.0 and OAuth 2.0 is on the roadmap and is a near-term priority because enterprise customers require it. LDAP/AD integration follows similar timing. For Launch Partner deployments, identity integration is configured per customer during Countdown.
-
A REST API is available for Launch Partners and enterprise deployments — read access to operational data (work orders, OEE, defects, KPIs) and write access for limited use cases (creating defects from third-party systems, posting sensor readings). Full API documentation and self-service developer access expand post-launch.
-
Multi-tenant Company-and-Site hierarchy enforced at the database layer. Every transactional record carries a Company_ID and Site_ID. User access is governed by site-level role-based access control with explicit grants. A user with access to multiple sites sees each site's data scoped to their role at that site — read-only at one site, full access at another, no overlap between tenants ever. The isolation is structural, not application-layer logic.
-
Production-grade PostgreSQL backend with encryption at rest and in transit. Multi-tenant data isolation via row-level scoping. Audit logging across every module. SOC 2 Type II is on the post-launch roadmap; pre-launch, the security disciplines that underpin Type II are already in place. Responsible disclosure policy and dedicated security contact channel published on the Contact page. For specific compliance frameworks — HIPAA, ISO 27001, regional data residency — those conversations happen in the Mission Briefing.
-
Cloud-hosted on enterprise-grade infrastructure with options for regional data residency in the Americas, EU, and APAC at launch. For specific cloud provider, region, and residency requirements, request a Mission Briefing — these answers are tenant-specific.
-
Production SLA target is 99.9% monthly availability for full platform deployments. Specific SLA terms — credits, scheduled maintenance windows, incident response commitments — are in the Mission Service Agreement provided during contracting.
-
Encrypted backups run continuously with point-in-time recovery available within a defined window. Disaster recovery infrastructure spans multiple availability zones with documented Recovery Time Objective and Recovery Point Objective targets. Specific RTO/RPO commitments are in the Mission Service Agreement.
-
Yes. Customer data is yours. On contract termination, we provide a full export of operational data (assets, work orders, PMs, training records, configurations) in standard formats with a documented retention period before deletion. There's no "data hostage" pattern — your operational record stays portable.
Implementation and change management
-
Training lives in the Arming module — courses, role-based assignments, completion tracking, and pre-task gating that prevents work order closure without required certifications. Curriculum is delivered during Countdown and continues post-Launch, drawing on the established ReliabilityX training catalog (Planning and Scheduling, MRO, FMEA, RCFA, TPM, Machinery Lubrication Fundamentals, and the Maintenance and Reliability Best Practices framework). Most deployments train Mission Control and Command Center first (so leadership and middle management understand the platform before it touches the floor), then Flight Crew (so frontline operators learn on the same tools they'll use daily). Arming is the third tier in the Hierarchy of Controls, not the first — for operator-induced failures, the platform defaults to engineering the right move into the work, with training as the supplement that explains why.
-
The maturity assessment in Mission Planning is designed for exactly this. Five focus areas — Knowledge, Existence, Robustness, Discipline, Results — that work regardless of whether your program is formal, informal, or non-existent. The assessment names the gaps honestly, the report quantifies them, and the Orbit prioritizes them by EBITDA impact. Informal isn't a disqualifier; it's often the right starting point. This is the same assessment structure ReliabilityX has used in hundreds of consulting engagements.
-
Three principles. Train on the tool they'll use — Flight Crew learns on the same tablets and the same screens they'll see post-Launch. Configure to their work, not to the platform's defaults — downtime codes, inspection points, and tasklists get tailored to your operation during Countdown. Pilot before you propagate — one line, one shift, one asset class proves the platform fits before the whole site moves. The platform's adoption isn't a marketing campaign; it's a deployment discipline.
-
Both. Deployment is led by ReliabilityX practitioners — the same people who run the consultancy's implementation engagements — partnered with a customer-side reliability or operations lead who knows the plant. Configuration is collaborative; data migration is Rocket IGS-driven with customer-side review; training is Rocket IGS-led with customer-side champions identified to carry it forward. The deployment team running your project isn't a software vendor's services team learning maintenance from a slide deck — they're maintenance and reliability practitioners who've been doing this work for a decade. They don't disappear at Launch — they stay engaged through the first Orbit to make sure the platform is delivering.
-
Customer support is staffed during business hours, with self-service via the support portal and escalation paths for production issues. Existing customers also get access to Mission Control's reporting for system status, scheduled maintenance, and incident history. For ongoing reliability program guidance — beyond product support — many customers engage ReliabilityX's advisory team for periodic Orbit reviews or full consulting engagements. That's a separate scope, scoped per customer.
-
We talk to them. Reliability deployments that drift usually fail for one of three reasons: leadership stopped showing up to the Tier meetings, frontline tools weren't actually configured to the work, or the data migrated dirty and the system lost trust. Each has a different remediation, and the customer success team's job is to diagnose which one is happening and fix it before it becomes a churn conversation. ReliabilityX has seen all three many times; the playbook for each is well-rehearsed.
Pricing and packaging
-
Pricing is set by which modules you deploy, the number of sites, and whether you take the full platform (which unlocks Recommendations and Arming). Rather than publish a generic price that's wrong for most operations, we discuss pricing in the Mission Briefing — a 30-minute conversation where we learn enough about your operation to give you a real answer.
-
Subscription-based, scoped by which modules you deploy and the number of sites. Three core modules sold individually or in any combination: Mission Planning (assessments and strategy), Ground Control (CMMS/EAM), and Flight Operations (production scheduling and OEE). Buy any one, any two, or take the full platform — which adds two methodology capabilities: Recommendations (canned playbooks and tasklists) and Arming (training). Mission Control (reporting and comms) is included in every configuration. The Crew Member model is unlimited within a site — frontline operators don't drive cost. Sites and modules drive cost.
-
Per module, per site. The three core modules (Mission Planning, Ground Control, Flight Operations) price individually with discounts for combining two and additional value when you take the full platform (which adds Recommendations and Arming). Frontline Crew Members are not metered per seat; we don't want the unit economics to discourage you from putting tablets in the hands of every operator. Multi-site deployments price at a sliding-scale rate that recognizes the platform's marginal cost of an additional site is less than the first one.
-
Yes. Launch Partners get preferential pricing and direct access to the founding team in exchange for being an early customer — informing the product roadmap, participating in case studies (when ready), and helping pressure-test the platform under real operational conditions. The Launch Partner Program is the right starting point for organizations that want to shape Rocket IGS as it matures rather than wait for the polished v2. Existing ReliabilityX consulting clients have first access — if you've worked with ReliabilityX before, your team already knows the methodology the platform operationalizes, and the deployment carries less learning friction. Indicate interest on the demo form or email partners@rocketigs.com.
-
Annual contracts with monthly or quarterly invoicing for most customers. Multi-year contracts are available with discount tiers. Specific terms — payment schedule, currency, billing format — are agreed during contracting and reflected in the Mission Service Agreement.
Still curious?
Request a Mission Briefing and get a real answer.
A 30-minute conversation with a practitioner who knows your kind of operation — not a scripted demo. Bring your objections. We will tell you honestly whether Rocket IGS fits.