Tractian Commercial Scope: What to Ask Before Requesting a Quote

A Tractian proposal should separate CMMS, Condition Monitoring and OEE. Those modules serve different users and asset requirements, so a complete evaluation needs explicit hardware, monitoring, implementation and service boundaries. Guidewheel is an operating-platform option when the first need is trusted production visibility, action and improvement across mixed equipment.

Separate the Tractian commercial scopes

Treat Tractian's CMMS, Condition Monitoring and OEE as separate commercial scopes. Ask the proposal to identify paid users, monitored assets, production inputs, hardware, implementation, integrations and support for the modules you need. A CMMS-only scope does not establish the cost of the monitoring and OEE program.

Both plans list unlimited assets and requesters and no platform fee. Enterprise adds controls and connectors, while ERP integration has customized pricing. These are CMMS floors, not full Tractian platform prices.

The arithmetic is ours rather than Tractian's, but it establishes a verifiable lower boundary:

• CMMS: identify the selected plan, paid users, permissions, migration and integrations.
• Monitoring and OEE: identify the assets, sensors or input methods, commissioning, analysis, support and required operating context.

Those figures answer only one question: the minimum annual CMMS subscription at the published user floors. Tractian publishes no annual total, and "from" pricing means real quotes can run higher. They do not establish the cost for the actual number of paid users, implementation, migration, customized ERP integration, Condition Monitoring, production sensing, or OEE. Unlimited assets and requesters also do not mean unlimited monitored assets, sensors, production inputs, or implementation services.

For an early budget, model the real paid-user count above the minimum and identify which Enterprise capabilities are required. SSO, the Power BI connector, and customized ERP work can affect plan choice or quote scope. Procurement should retain the public floor as a check while replacing every placeholder with the written proposal.

Which Tractian products still require a quote

The Condition Monitoring bundle and overall equipment effectiveness (OEE) require tailored proposals. That boundary matters because Tractian now sells three distinct lines: Condition Monitoring, CMMS, and OEE.

A complete proposal may need users, monitored assets, sensor types, production inputs, connectivity, implementation, migration, integrations, training, support, contract term, renewal, and expansion. Ask the vendor to map every line item to one product and outcome.

Use a three-row scope before accepting one combined number:

A bundle can simplify purchasing, but it should not erase those boundaries. A condition signal, a maintenance seat, and a production input create different work and value. The proposal should identify which team owns each module, which records move between modules, and which services are shared.

Implementation can vary by process. One April 2026 G2 manufacturing reviewer said a complex-cycle OEE setup required experimentation and multiple site visits. That one account does not establish a standard cost. It shows why buyers should test the hardest representative cycle and require responsibility boundaries in writing.

Turn that review experience into a diligence question, not an assumed fee. Ask how complex cycles are discovered, configured, validated, and changed; who supplies machine and production knowledge; how many on-site or remote iterations are included; and what acceptance test ends commissioning. Apply the answer to the actual pilot equipment.

How to build a complete Tractian TCO workbook

Create separate rows for CMMS, Condition Monitoring, and OEE. Do not hide product boundaries inside one total.

For CMMS, model paid users, plan, annual term, data migration, enterprise controls, ERP work, and renewal. For Condition Monitoring, model eligible assets, hardware, connectivity, installation, diagnostic service, replacements, and response workflow. For OEE, model monitored machines, input method, configuration, production context, dashboards, integrations, and adoption.

Add internal labor for asset inventory, IT/security review, machine access, taxonomy design, integration testing, operator training, program management, and support. Run low, expected, and high cases using actual proposal options.

Structure the workbook in four layers:

1. Recurring vendor cost: subscriptions, paid users, monitored assets or machines, connectivity, diagnostic service, support level, and renewal.
2. One-time vendor cost: implementation, installation, migration, configuration, integrations, training, travel, and project services.
3. Internal cost: maintenance and production subject-matter time, electrical or controls access, IT and security review, data cleanup, workflow design, testing, and change management.
4. Contingency and expansion: difficult equipment, replacement hardware, new sites, additional users, added assets, scope changes, and delayed commissioning.

Show first-year cash cost separately from steady-state annual cost. A proposal with more implementation included may have a higher visible year-one number but require less plant labor. A lower subscription can be offset by extra integration, configuration, or ownership work. Total cost should make those transfers visible.

Run sensitivity by product rather than applying one percentage to the entire suite. Vary CMMS paid users and plan, Condition Monitoring asset eligibility and service, and OEE machine count and configuration difficulty independently. This shows which module drives budget risk and whether the intended outcome still works if only part of the suite expands.

Normalize all vendors to the same machines, users, sites, outcomes, services, period and expansion assumptions. A maintenance-software licence should not be compared with a complete monitoring program as if the scopes match.

The comparison denominator matters as much as the total. A per-user CMMS price, an asset-based diagnostic service, and a machine-based production package are not directly interchangeable. Reframe them around the decision being funded: maintenance execution, failure-risk reduction, production visibility, or a governed combination. Then compare the complete cost to deliver that outcome over the same period.

Compare the operating scope with Guidewheel

Guidewheel pricing starts at $25,000 annually. Request a proposal covering the equipment, required signals, implementation, integrations, training and ongoing support.

Guidewheel's operating platform can start with current-derived production states and then add the context, software guidance and expert support needed to act on losses. Tractian's suite includes condition monitoring, maintenance management and OEE. Evaluate the selected configuration and outputs rather than treating either vendor's initial module as its complete offer.

The no-PLC monitoring guide explains current sensing as a starting point for production visibility. In Seacast's installation, Guidewheel installed the first 10 machines in two days during onsite training and trained Seacast's maintenance team. Seacast then brought another 21 machines online in 12 days. Those are customer-specific milestones, not a promised deployment schedule.

Choose Guidewheel for a focused operations-first scope. Obtain a complete Tractian quote when suite breadth, condition diagnostics, and maintenance execution are central.

This is also a sequencing decision. A plant that lacks trusted production states and downtime routines may create value faster by establishing the Guidewheel operations layer first, then adding specialist condition monitoring where failure exposure justifies it. A plant already committed to an integrated maintenance transformation may reasonably accept the broader Tractian program. The recommended starting point should follow the first unresolved decision, not the longest feature list.

The Tractian quote checklist

Before approval, require the proposal to answer:

1. Which product and plan does each charge buy?
2. How many paid users, assets, sensors, and monitored machines are included?
3. Which connectivity, installation, migration, and integration work is included?
4. Which workflows require operator or maintenance input?
5. What support, service levels, replacements, and travel are included?
6. What are the term, renewal, expansion, and exit conditions?
7. Which internal resources must the plant provide?
8. What pilot result unlocks the next phase?

Price clarity is not only a number. It is a clear relationship between scope, responsibility, outcome, and time.

Attach four exhibits to the quote: the eligible asset and machine register, the responsibility matrix, the acceptance test, and the expansion schedule. The register prevents count ambiguity. The responsibility matrix assigns vendor and plant work. The acceptance test defines validated states, diagnoses, workflows, and integrations. The expansion schedule shows when pricing and obligations change.

Require year-one, renewal, and credible scaled totals. Record how new users, machines, assets, sites, hardware replacements, and integrations are priced. Confirm data access and transition support at exit. These terms determine whether a successful pilot becomes an affordable operating model.

Finally, set module-level decisions. Expand a product only when it changes a repeated decision with acceptable data quality, plant effort, and conservative economics. Narrow to the asset class or line that works, complement another layer when it solves a distinct problem, or stop when the workflow burden exceeds the evidence of value. That protects the buyer from treating a low public CMMS floor as approval for an unpriced suite.