CMMS for Manufacturing: What Your Operation Actually Needs

A machine is due for maintenance. The technician is available. The replacement part is on the shelf. The job plan is ready. But production needs the machine.

Now reverse the problem. Production can release the machine Thursday morning during a changeover. The technician is available. The required part will not arrive until Friday.

Putting a maintenance job on a calendar does not resolve either situation. The asset, maintenance resources and operational opportunity have to come together.

Manufacturing maintenance operates inside a production system. Production needs the asset available to make something. Maintenance needs access to keep it capable of making something. Both demands can be legitimate.

A CMMS should help the organization manage that reality. It needs enough production context to support maintenance decisions without trying to become the production system.

FUNCTION → CONSEQUENCE → TRIGGER → CONSTRAINT → OPPORTUNITY → EXECUTION → EVIDENCE → SYSTEM BOUNDARY

This is CMMSBuyersGuide’s practical framework for following a production requirement back to a software requirement. It is a synthesis of established manufacturing and maintenance concepts, not an industry-standard model.

The maintenance requirement starts with what production needs the asset to be capable of doing.

FUNCTION: What does production actually need this asset to do?

Start before software. Ask: What does the operation need this asset to be capable of doing?

• run when required
• produce at a required rate
• maintain dimensional tolerance
• maintain temperature or pressure
• move material
• position accurately
• provide consistent output
• support product quality
• satisfy relevant safety or environmental requirements

The answer depends on the operation and the asset. A machine shop, food processor, chemical plant, electronics assembler and packaging operation may define required performance differently.

NIST describes manufacturing monitoring, diagnostics and prognostics as ways to understand when and why production-performance thresholds are or will be exceeded. Its work connects equipment and process health with production performance, downtime and production quality.[1]

An asset can be running while losing the capability that production needs. A machine may continue cycling while dimensional accuracy drifts. A temperature-control asset may still operate while its control performance degrades.

Begin with the required production function, then determine what maintenance information and action support it.

If the organization has not yet translated operating needs into requirements, use How to Build Your CMMS Requirements before comparing products.

CONSEQUENCE: What happens when the asset cannot do it?

Equipment purchase price does not establish its operational criticality. Ask what happens next when the asset becomes unavailable or incapable.

• little immediate operational impact
• reduced capacity
• another machine takes over
• a production cell or line stops
• downstream operations are starved
• upstream work accumulates
• product quality deteriorates
• a shipment may be delayed
• safety risk increases
• an environmental or regulatory consequence occurs

These are prompts, not a universal scoring model. Each operation has different products, redundancy, buffers, hazards and obligations.

NASA’s equipment asset criticality method illustrates the principle by assessing several consequences, including safety, mission effect, downtime and replacement cost, rather than relying on equipment price alone.[2]

Asset value and production criticality answer different questions. Criticality comes from the asset’s role in the operation and the consequences of losing that role.

Choose several important assets and ask what actually happens if each becomes unavailable or unable to meet its required function. The answers reveal the maintenance priority, visibility and control the CMMS may need to support.

TRIGGER: What tells you maintenance is needed?

Manufacturing assets can live on several clocks. The useful trigger follows what actually ages, wears or degrades the asset.

• CALENDAR — every 30 days
• RUNTIME — every 500 operating hours
• CYCLES OR PRODUCTION COUNT — after a relevant quantity of cycles or units
• CONDITION — when a monitored condition crosses a defined threshold
• INSPECTION OR FINDING — when an inspection identifies work
• FAILURE — when the asset no longer performs its required function

Microsoft documents maintenance plans based on fixed time intervals and counter registrations. It also documents updating asset counters from production hours or production quantity.[3]

Calendar time is not the only clock a manufacturing asset lives on.

Ask what actually ages or degrades the asset, where that information originates, and how it becomes maintenance demand.

The full trigger-to-history test is covered in Preventive Maintenance Software: What It Does and What to Look For.

A trigger is not an opportunity

A maintenance trigger tells you why work is due. It does not necessarily tell you when the operation should stop to perform it.

Suppose a machine reaches a 500-hour maintenance threshold on Tuesday. Production needs it through Wednesday. A product changeover on Thursday creates a two-hour access window.

The organization now has two separate facts to manage: when the work becomes due and when it can reasonably be executed.

Production preference does not automatically justify deferral. Safety, regulatory requirements, failure risk, allowable tolerance and other constraints may require earlier action. The people responsible for the operation must make that decision using visible information.

A maintenance trigger tells you why work is due. It does not necessarily tell you when the operation should stop to perform it.

CONSTRAINT: What prevents the work from happening?

A work order can be justified and still be impossible to execute today.

• production demand
• labor availability
• technician skill
• spare parts
• tools
• contractor availability
• permits
• lockout or other safety requirements
• asset access
• prerequisite work
• a shutdown requirement

Three conditions for executable work

ASSET AVAILABILITY — Can the equipment actually be released?

MAINTENANCE READINESS — Are the required labor, skills, parts, tools, procedures and other resources ready?

OPERATIONAL OPPORTUNITY — Is there an appropriate time to perform the work with an acceptable operational consequence?

These three terms are CMMSBuyersGuide’s practical synthesis. A job becomes realistically executable when the necessary conditions line up.

Buyer question: Can we see when the asset, the maintenance resources and the operational opportunity come together?

For the detailed flow from request through planning, execution and history, see Maintenance Work Order Software: What to Look For.

Maintenance and production share the asset

Production may ask, “When can maintenance return this equipment?” Maintenance may ask, “When can production release it?” Both are legitimate operational questions.

The CMMS does not necessarily make the tradeoff. It should provide or exchange enough information for responsible people to make it.

Production may need from maintenance

• planned downtime
• expected duration
• work status
• estimated return to service
• actual return to service
• unresolved equipment condition

Maintenance may need from production

• operating schedule
• machine state
• runtime
• cycle or production counts
• changeovers
• planned downtime
• production windows
• relevant process or quality context

These records do not all have to live in the CMMS. Their ownership and movement are system-boundary questions.

SCHEDULING: A calendar is not enough

A manufacturing maintenance schedule may need to coordinate priority, production requirements, equipment release, labor, skills, parts, tools, contractors and shutdown or changeover windows.

A peer-reviewed manufacturing case study specified that a CMMS should support scheduling maintenance activities while considering available resources and planned production. The same study included preventive maintenance, spare-parts management and failure-data analysis among company-specific requirements.[4]

That does not mean software should optimize every tradeoff automatically. It means the buyer should inspect whether the information needed for the scheduling decision is visible and usable.

Ask whether the software supports the decisions behind the schedule, rather than whether it has a scheduling screen.

Planned shutdowns and maintenance windows

Some manufacturing work cannot reasonably occur while production is running. A shutdown or planned outage creates a scarce maintenance opportunity.

Before the window opens, the work may need defined scope, a completed plan, available parts, identified labor, coordinated contractors, prepared permits and safety requirements, and understood dependencies.

The CMMS may identify, prepare, schedule, execute or document some of that work. It does not necessarily need to replace project-management or specialist shutdown-planning systems. Define the role it must play in your operation.

Spare parts: inventory is about executable work

A low-cost bearing available tomorrow creates one kind of maintenance risk. The same bearing with a long lead time, required by the only machine capable of a critical production step, creates a different operational exposure.

The useful relationship joins asset criticality, likely maintenance need, required part, current availability, lead time and the ability to execute the work.

Buyer question: Can maintenance understand which unavailable parts can prevent important work from being executed?

Detailed stocking and purchasing rules belong in a separate inventory analysis. Here, the requirement is visibility from maintenance need to work readiness.

Asset hierarchy: choose useful detail

Loading thousands of equipment records into a CMMS does not by itself create useful asset management.

Plant → Area → Line → Cell → Machine → Assembly → Component

That is one possible structure, not a universal manufacturing hierarchy. A process plant, batch operation and discrete assembly site may need different relationships.

At what level do we need to plan work, capture failures, consume parts, record cost and make decisions?

A hierarchy that is too shallow hides useful distinctions. A hierarchy with more detail than the organization can maintain creates burden and unreliable records. The decisions the organization needs to make should determine the useful level of detail.

EXECUTION: What happens at the machine?

At the asset, the technician may need the exact location, work instructions, safety information, drawings or manuals, asset history, parts, measurements, related work, attachments and a way to record findings.

Mobile access matters when work happens away from a desk. Offline access matters where the operating environment has unreliable connectivity. Neither is a universal requirement.

Evaluate the technician experience with the complete execution test in Maintenance Work Order Software: What to Look For.

EVIDENCE: Can today’s maintenance become tomorrow’s knowledge?

Completed manufacturing work orders can become evidence about recurring failures, problem equipment, labor-intensive activities, parts consumption, maintenance cost, downtime, failure modes and asset condition.

NIST notes that much of the available knowledge about a maintenance workflow may exist in historical maintenance work orders, while inconsistent data collection, cleaning and analysis make that knowledge difficult to use.[5]

A NIST manufacturing example makes the problem concrete. Researchers manually reviewed a manufacturer’s maintenance records and found that hydraulic leaks had occurred more than 40 times in three months. The pattern was difficult to recognize because technicians used different wording, abbreviations and a misspelling for similar events.

The NIST account gives examples including “hyd leak,” “hydraulics were leaking” and “hydaurlic burst and leak.” The lesson is about the records and their structure, not a criticism of the technicians who created them.[6]

The data-entry tension

Free text preserves nuance but can make repeated patterns difficult to identify. Rigid categories can improve consistency while making it harder to describe what actually happened.

NIST has separately studied categorization errors when people enter maintenance information into controlled-vocabulary fields, showing that structured entry can introduce its own human-error modes.[7]

There is no universal balance. Decide which future questions the history must answer, then test whether technicians can capture the required evidence accurately during real work.

Capture enough structure to make the history useful without turning technicians into data-entry clerks.

Running does not always mean capable

Failure is not always binary. An asset may continue running while vibration increases, dimensional accuracy deteriorates, temperature control worsens, cycle performance changes, tool wear increases or product quality is affected.

NIST’s manufacturing monitoring research focuses on equipment and process health, production-performance thresholds, diagnostics, prognostics and production quality. That work reflects the difference between simple operation and acceptable production performance.[1]

“Is the asset running?” and “Is the asset capable of producing acceptable output?” can be different maintenance questions.

The CMMS should not replace quality, process-control or condition-monitoring systems. Determine what condition or quality context maintenance needs to receive, reference or send so it can act and preserve relevant history.

SYSTEM BOUNDARIES: CMMS, MES, ERP and other systems

Manufacturing information may live across several systems. Exact boundaries vary by organization and software stack.

Typical responsibilities to test

• CMMS or EAM — maintenance assets, work, preventive maintenance, labor, parts, failure history and maintenance-related costs
• MES — production execution, shop-floor activity, machine or production state, production quantities and production context
• ERP — purchasing, financial transactions, enterprise inventory or materials, and broader business records
• Other systems — controls, SCADA, condition monitoring, quality, historians and specialized production applications

Treat those as broad starting points, not rules. Some products combine roles; some organizations divide them differently.

Microsoft documents near-real-time exchanges between its supply-chain platform and third-party manufacturing execution systems, including messages about production and material consumption. Its asset-management documentation separately shows asset counters updated from production hours or quantities.[8]

SAP’s current asset-management materials likewise describe maintenance integrated with production planning and technical asset structures. These vendor documents demonstrate possible exchanges and boundaries; they do not establish one architecture for every manufacturer.[9]

Map each important information handoff

1. Who creates the information?
2. Which system owns it?
3. Who needs it?
4. Does the CMMS need to store it, receive it, reference it or send it?
5. How current does it need to be?

Integration should move context across systems without confusing their responsibilities.

If the maintenance decision extends into wider lifecycle, risk or investment decisions, CMMS vs EAM: What’s the Difference? provides a practical boundary test.

Production work order and maintenance work order

PRODUCTION ORDER: Make 5,000 units of Product A.

MAINTENANCE WORK ORDER: Inspect or repair the conveyor used to produce Product A.

The records can be related. The conveyor may fail during a particular production run. They still serve different purposes.

Determine which production context needs to cross into maintenance and which maintenance status needs to cross back. Do not assume that the CMMS should manage production execution.

Start the vendor demo with your manufacturing scenario

Ask the vendor to follow this situation rather than opening with a tour of a “manufacturing module.”

Machine 12 is approaching its runtime-based maintenance threshold. Production needs it through Wednesday. A Thursday-morning changeover creates a potential two-hour maintenance window. The job requires a replacement component and a technician with the appropriate skill. During the work, the technician discovers abnormal wear that requires corrective action.

Ask the vendor to demonstrate:

1. Where does runtime or usage information come from?
2. How does the maintenance requirement become due?
3. How can production context be considered?
4. How can maintenance identify the potential work window?
5. How are required parts checked?
6. How are labor and skills considered?
7. What does the technician receive?
8. What does the technician record?
9. What happens to the abnormal finding?
10. Can follow-on work be created and linked?
11. How is equipment downtime represented?
12. What becomes asset history?
13. What information can flow to or from other systems?

A product may support some functions internally and depend on integration for others. The exercise reveals its actual boundary and fit.

Use The CMMS Demo Checklist to structure the session and How to Compare CMMS Solutions to record the evidence.

FOLLOW THE PRODUCTION REQUIREMENT

Take several important assets from the actual operation and work through the same sequence.

1. FUNCTION — What does production need this asset to be capable of doing?
2. CONSEQUENCE — What happens when it cannot?
3. TRIGGER — What tells us maintenance is required?
4. CONSTRAINT — What prevents the work from happening?
5. OPPORTUNITY — When can the work reasonably happen?
6. EXECUTION — What does maintenance need to perform it correctly?
7. EVIDENCE — What should the organization know afterward?
8. SYSTEM BOUNDARY — Where does the necessary information live and what must cross between systems?

Do not choose only the most expensive equipment. Include assets whose failure or degradation creates different consequences: lost capacity, quality risk, safety exposure, material flow disruption or a manageable inconvenience.

The differences begin to reveal the organization’s actual CMMS, data and integration requirements.

Bring it back to the operation

Manufacturing does not produce one universal CMMS requirements list. Requirements depend on what the operation needs its assets to do, what happens when they cannot, how maintenance becomes necessary, what constrains the work and what information must move between maintenance and production.

Start there. Follow the production requirement back through the maintenance process. Then determine what the software has to support.

That operational definition should also shape implementation. What to Expect During CMMS Implementation explains how to carry those decisions into configuration and adoption.

The requirements are already in the operation.