Maintenance guide
CMMS setup for a new manufacturing facility — go live before the chaos sets in
New manufacturing facilities should stand up a CMMS before tribal workarounds harden: import critical assets, invite the crew under facility pricing, open work orders on day-one faults, and schedule light PM on the riskiest equipment. Typical CMMS rollouts take multiple weeks of workshops and data projects. Corivo’s guided first-facility setup is designed so a focused go-live can happen in under a day.
Why new facilities uniquely need CMMS early
A new manufacturing facility forms habits in weeks, not quarters.
If day-one faults live in group chats and commissioning notes live in personal sheets, that pattern hardens by the time volume ramps. History debt compounds: the same commissioning issues get re-diagnosed, spare-parts tribal knowledge never becomes a list, and “we’ll implement a CMMS after things settle” becomes a year of undocumented restores.
Greenfield and transfer plants share the same constraint: no spare time for a six-week software program, and no desire to rebuild spreadsheet chaos in a brand-new building. The CMMS should arrive with the equipment — light, focused, and live — not as a post-ramp project.
Day-0 vs day-30 mistake patterns
Day-0 mistakes
- Waiting for a perfect asset register before any work orders
- Buying enterprise EAM scope when the gap is floor execution
- Training nobody except the maintenance manager
- Letting commissioning punch lists stay outside the system of record
Day-30 mistakes
- Parallel chat remains the real workflow; the CMMS is “for later”
- PM library is huge and unfinished while critical stops still lack history
- Integration workshops block basic claim/start/complete on the line
- Second shift was never invited, so handoffs still fail
The antidote is the same in both windows: critical assets + live work orders + full crew invited, then enrich.
New-facility CMMS setup checklist
Use this as a go-live checklist for a first facility:
- Name the facility and confirm who admins it
- Import or create critical assets (the machines that stop production if they fail)
- Invite the full maintenance crew (and key operators who report faults) under facility pricing
- Agree the work-order minimum fields — asset, fault, impact, owner, start/complete
- Open work orders on day-one faults — including commissioning issues you still own
- Schedule light PM on the riskiest assets only (short checklists, real windows)
- Stage critical spares for those same assets — even a short list beats none
- Run a 15-minute daily stand-up for the first week: open work, overdue PM, parts blocks
- Defer full catalog imports, deep integrations, and plant-wide PM libraries until the loop sticks
For broader timeline expectations, see the [CMMS implementation timeline](/guides/cmms-implementation-timeline).
Under-a-day guided go-live with Corivo
Most traditional CMMS implementations take 2–6 weeks (sometimes longer) once workshops, data cleansing, and role debates expand. That cadence mismatches a new facility that is commissioning equipment this week.
Corivo’s guided setup is designed for a focused first-facility go-live in under a day:
- Morning: create the facility, import critical assets, invite users
- Midday: open the first live work orders on real faults; walk claim/start/complete on the floor
- Afternoon: add light PM on the top risk assets; confirm parts visibility for those machines
- End of day: you have a system of record for open work — not a perfect digital twin
That is intentionally narrower than a multi-week rollout. You trade exhaustive configuration for durable history before tribal workarounds win. Expand line by line after the first week of real use.
What to configure later (integrations, full PM library)
Defer without guilt:
- Full spare-parts catalog beyond critical kits
- ERP / MES deep integrations
- Every OEM PM procedure for every asset
- Advanced reporting packs and custom fields nobody uses yet
- Multi-site process standardization workshops
Day-one value is owned work on the machines that can stop the plant. Everything else is enrichment. If an integration is required for purchasing later, schedule it as a phase-two project — do not block go-live on it.
Multi-plant: second facility pattern
When the second facility opens (or a sister plant adopts the same stack):
- Clone the first facility’s working pattern — fields, PM sizing rules, review cadence
- Import that site’s critical assets first; do not restart from a blank spreadsheet culture
- Invite the local crew under facility pricing so coverage does not become seat math
- Keep a short playbook: “how we go live in under a day here”
Solar and battery plants often ramp capacity across sites — see [solar manufacturing](/for/solar-manufacturing) and [battery manufacturing](/for/battery-manufacturing). The second facility should inherit discipline, not reinvent chat-based maintenance.
FAQ for greenfield and transfer plants
Greenfield: Stand the CMMS up as equipment is commissioned. Treat commissioning faults as work orders so early failure modes become history, not folklore.
Transfer / relocation: Bring critical asset identity and known failure notes with the move. Do not wait until the new building “settles” — the settling period is when undocumented fixes multiply.
Partial production: Even a soft start needs owned work. Pilot on the lines that are live; expand the register as more equipment comes online.
Perfect data myth: You will never have perfect data on day one. Critical assets and live work orders beat a pristine empty register.
New facilities do not need a months-long CMMS program to avoid spreadsheet debt. They need a guided first go-live measured in hours, then steady expansion — which is the constraint Corivo is built around.
Frequently asked questions
Open the new facility in Corivo on day one
Import critical assets, invite unlimited users, and make work orders the system of record before spreadsheets win.
Get started