Before You Sign: The CMMS Due Diligence Checklist for Manufacturing Operations

Due Diligence Area 1: Pilot Validation

The most reliable signal of whether a CMMS will deliver its promised outcomes in your facility is a structured pilot on your actual assets with your actual technicians.

If you have completed a 30-day pilot, the following validation should already exist.

If you have not completed a pilot before reaching the contract stage — complete one before signing.

A vendor unwilling to support a 30-day pilot on a representative selection of your assets before contract commitment is communicating something important about their confidence in their platform's real-world performance.

Pilot Validation Checklist

☐ Machine connectivity was confirmed on at least one modern digitalized asset, one legacy asset, and one manual or hybrid station during the pilot.

☐ The connection was stable for the full pilot period — no unexplained data gaps, signal dropouts, or accuracy issues.

☐ At least one condition-based PM trigger fired automatically from a machine signal during the pilot — not a manually scheduled calendar PM.

☐ Technician adoption rate reached above 70% by day 30 of the pilot — measured by actual mobile app login frequency, not self-reported compliance.

☐ At least one compliance audit trail record was reviewed end-to-end — confirming it contains user attribution, timestamp, parts consumed, SOP version, and sign-off at the level your regulatory framework requires.

☐ OEE data from the pilot period was reviewed alongside maintenance records — confirming that both datasets exist in the same environment and that cross-referencing them does not require manual data export and reconciliation.

Due Diligence Area 2: Contract Terms

Manufacturing CMMS contracts contain terms that create ongoing obligations and constraints that are easy to overlook when the primary focus is on pricing.

These terms matter more than most buyers realize at the signing stage — particularly those governing data portability, contract renewal, and scope changes.

Contract Terms Checklist

☐ Data portability clause confirmed.

The contract explicitly states that all data — asset records, work order history, maintenance records, OEE data — is exportable in a standard machine-readable format (CSV, JSON, or XML) at any time and upon contract termination.

A vendor who resists a clear data portability clause is creating future switching costs that you should price into the total cost of ownership now.

☐ Notice period for termination is documented and reasonable.

Contracts requiring 6-12 months termination notice for annual subscriptions create significant lock-in.

30-90 days is a reasonable termination notice period for a manufacturing CMMS.

☐ Price escalation terms are defined.

Annual price increases above a defined cap — typically CPI plus 2-3% — should require your explicit consent rather than automatic application.

Confirm whether the contract includes a price escalation clause and what its terms are.

☐ Scope of included support is explicitly defined.

Implementation support, post-go-live account management, response time commitments for critical operational issues versus configuration questions, and the process for escalating unresolved issues are all defined in writing — not left to verbal assurances during the sales process.

☐ Connectivity scope is documented.

The specific assets included in the machine connectivity project are listed — with the connectivity path for each (PLC direct, IoT gateway, computer vision) and the party responsible for installation.

Connectivity surprises mid-implementation are one of the most common sources of timeline overrun and budget conflict.

☐ Uptime and data availability guarantees are stated.

Confirm whether SLA terms for platform availability — particularly relevant for cloud-hosted platforms — are included and what remedies exist if they are not met.

Due Diligence Area 3: Post-Go-Live Support

The quality of post-go-live support is the single most underestimated factor in CMMS implementation success.

The sales team and implementation team who were attentive and responsive during the evaluation process are not always the same people who support the operation after go-live.

Validating the post-go-live support model before signing is not skepticism — it is standard due diligence.

Post-Go-Live Support Checklist

☐ Named account manager confirmed.

The name of the account manager who will be responsible for the relationship post-go-live is documented.

Confirm whether this person was involved in the implementation process or is a new relationship that begins at go-live.

☐ Support response time commitments are in writing.

The contract distinguishes between response time commitments for critical operational issues (platform unavailability, data loss, system failures affecting production operations) and standard configuration or usage questions.

Critical issue response times of under 4 hours during business hours and a defined escalation path for out-of-hours critical issues are reasonable expectations for a manufacturing operations platform.

☐ Product update communication process is defined.

The vendor has a documented process for communicating platform updates before they are deployed — including changes that affect configured workflows, integrations, or compliance documentation structures.

Ask specifically how product updates have affected existing customer configurations in the last 12 months and how those customers were notified and supported through the changes.

☐ Reference customers in post-go-live operation have been contacted.

At least two reference customers who are 12-24 months post-go-live in a similar manufacturing environment have been contacted directly — not routed through vendor-curated reference calls.

The specific questions to ask references:

"How did the vendor's support quality change between the implementation phase and the post-go-live phase?"

"Were there any post-go-live surprises — connectivity issues, compliance documentation gaps, adoption problems — that were not identified during the evaluation?"

"Would you implement this platform again, knowing what you know now?"

Due Diligence Area 4: Integration and ERP Connectivity

For manufacturers with existing ERP infrastructure — SAP, Microsoft Dynamics, NetSuite — the integration between the CMMS and the ERP is a critical operational requirement that deserves specific pre-signature validation.

Integration and ERP Connectivity Checklist

☐ Integration architecture is documented in writing.

The specific data flows between the CMMS and the ERP — production orders from ERP to CMMS, maintenance costs from CMMS to ERP, spare parts purchasing workflows — are documented with the technical integration method specified.

"We integrate with SAP" is not sufficient documentation.

"We connect to SAP via a bi-directional REST API, synchronizing production orders every 15 minutes and pushing maintenance cost data to SAP PM upon work order closure" is.

☐ Integration responsibility is assigned.

Who is responsible for building, testing, and maintaining the integration — the vendor, your IT team, or a third-party integrator — is explicitly defined in the contract.

☐ Integration testing is included in the implementation scope.

The implementation timeline includes a specific phase for integration testing before go-live — with defined acceptance criteria that the integration must meet before the platform is declared live.

☐ Integration maintenance responsibility is defined post-go-live.

When the ERP or the CMMS platform updates and the integration breaks — which it will, at some point — who is responsible for fixing it, within what timeframe, and at what cost is documented.

Due Diligence Area 5: Implementation Team and Timeline

The implementation team that will actually configure and deploy the platform is not always the same people who presented during the evaluation.

Validating who will be on the ground during your implementation — and what the realistic timeline looks like based on comparable customer implementations — is final-stage due diligence that most buyers skip.

Implementation Team and Timeline Checklist

☐ Named implementation team members are confirmed.

The automation engineer and account manager who will be assigned to the implementation are identified by name before the contract is signed.

If the vendor cannot name the specific implementation team members at contract stage, ask when they will be assigned and make the contract contingent on team assignment confirmation before implementation begins.

☐ Implementation timeline is based on comparable customer data.

The vendor can provide documented implementation timelines from at least three comparable customer implementations — similar facility size, similar equipment types, similar connectivity complexity.

If the quoted timeline is significantly faster than comparable customer implementations, ask what will be deferred or excluded to achieve it.

☐ Go-live criteria are defined in the contract.

The specific conditions that must be met for the implementation to be declared complete — machine connectivity percentage, technician adoption rate, compliance documentation configuration — are stated in the contract rather than left to the vendor's discretion.

☐ Connectivity feasibility for legacy assets is confirmed.

If the facility includes legacy equipment that will require IoT gateway deployment or computer vision coverage, the connectivity approach for those specific assets has been validated during the pilot or through a documented pre-implementation assessment.

Connectivity surprises on legacy assets are the most common cause of implementation timeline overrun.

The Final Question Before Signing

After completing every section of this checklist, one final question is worth asking directly to the vendor's sales representative — not their implementation team or their account manager.

"If this implementation underdelivers on the outcomes we discussed during the evaluation, what recourse do we have?"

The answer reveals more about the vendor's confidence in their platform than any demo or feature comparison.

A vendor who responds with specific, documented mechanisms — performance guarantees, defined remediation processes, exit clauses tied to measurable outcome failures — is a vendor who stands behind their implementation.

A vendor who responds with reassurances, deflection, or a shift to discussing why underdelivery is unlikely — rather than what happens if it occurs — is communicating something worth noting before signing.

Summary: The Pre-Signature Checklist

Sign when every box is checked.

Not before.

Frequently Asked Questions

Is it reasonable to ask a vendor for a pilot before signing?

Yes — and a vendor's willingness to support a structured pilot before contract commitment is itself a meaningful signal of their confidence in the platform's real-world performance.

A 30-day pilot on a representative selection of assets — covering the connectivity validation, adoption rate measurement, and compliance audit trail confirmation described in Due Diligence Area 1 — is a reasonable pre-signature requirement for a significant technology investment.

What if the vendor resists including go-live criteria in the contract?

Resistance to defined go-live criteria is a flag worth taking seriously.

Go-live criteria protect both parties — they give the vendor a clear definition of what success looks like and give the buyer an objective basis for declaring the implementation complete.

A vendor who resists defined go-live criteria is typically concerned that the criteria will expose a gap between their projected timeline and their realistic delivery capability.

How important is data portability for a cloud-hosted CMMS?

Critically important.

Your maintenance history, asset records, and compliance documentation are operational assets that your organization owns — regardless of which platform stores them.

A CMFS contract that does not explicitly guarantee your ability to export this data in a standard format at any time — including upon termination — creates a dependency that significantly increases switching costs if the platform underdelivers.

Should we negotiate the contract terms or accept standard terms?

Negotiate.

Specifically: data portability clauses, termination notice periods, price escalation caps, go-live criteria, and post-go-live support response time commitments.

These terms are negotiable for most vendors — and vendors who refuse to negotiate them on any point are communicating a vendor-buyer power dynamic that will affect the relationship throughout the contract period.

If every item on this checklist is confirmed and the final question has been answered satisfactorily — the contract is ready to sign. If any item remains unresolved — resolve it first. The implementation has not started yet. This is the last moment when outstanding issues cost nothing to address.