
Maintenance is where many factories still run on paper registers, WhatsApp messages and the memory of one senior technician. A CMMS (computerised maintenance management system) replaces that with a single record of every machine, every breakdown, every preventive maintenance task and every spare part used. Ready-made CMMS products exist and suit many plants well. But a growing number of manufacturers choose custom CMMS software development — a maintenance system built around their own plants, assets and processes.
This guide is written for plant heads, maintenance managers and owners who are considering that route. It explains when custom development makes sense, what a factory CMMS should contain, how a development project runs, and what drives the cost — so you can brief a development company clearly and judge the proposals you receive.
Ready-made CMMS or custom development?
Start with an honest question: does a packaged CMMS already do what you need? For a single plant with standard equipment and a small team, it often does. Custom development is worth considering when several of the following are true:
- Maintenance must connect to other systems. Breakdowns should stop a production order, spares issues should update stores, and a failed calibration should block a quality release. Packaged tools usually treat maintenance as an island.
- Your asset structure is unusual. Multi-plant groups, machines with many sub-assemblies, moulds and dies that move between machines, or customer-owned tooling rarely fit a fixed template.
- Approval and escalation rules are specific. Who can close a breakdown, who approves outside contractors, when a stoppage escalates to the plant head — these differ from plant to plant.
- Licence costs grow with the team. Per-user, per-asset or per-site pricing becomes significant once every operator, technician and supervisor needs access.
- You need to own the system. Some manufacturers want their maintenance history and software in their own hands, hosted where they choose.
If none of these applies, a packaged product may be the better choice. If several do, a custom CMMS built in phases is usually the more practical long-term option. Our article on custom software versus off-the-shelf covers the general trade-offs.
What a factory CMMS should contain
A CMMS does not need to be large to be useful. These are the building blocks most manufacturers need, roughly in the order they are usually built.
1. Asset register and hierarchy
Every maintainable item — machines, utilities, panels, compressors, cranes, moulds, dies, fixtures — with a unique code, location, make, model, serial number, criticality and documents such as manuals and drawings. Assets sit in a hierarchy: plant, area or line, machine, sub-assembly. A QR code tag on each asset lets a technician open its history by scanning it.
2. Breakdown requests
Operators or supervisors raise a breakdown from a phone or shop-floor tablet: which machine, what happened, a photo, and whether production has stopped. The request notifies the maintenance team immediately, and the clock starts for response and repair time.
3. Work orders
Each job — breakdown, preventive, corrective or improvement — becomes a work order with assigned technician, status, labour time, spares used, root cause and closing remarks. Supervisors see open work by priority, age and machine. Our guide to work order prioritisation explains how to rank them.
4. Preventive maintenance schedules
Schedules by calendar (weekly, monthly, yearly), by usage (running hours, strokes, shots, cycles) or by condition. The system generates work orders when tasks fall due, with the checklist for each task. Missed and overdue tasks are visible, not hidden in a register. See our preventive maintenance checklist for CNC machines for an example of what a task checklist contains.
5. Spare parts and stores
Spares linked to the assets they fit, with stock by location, minimum levels and reorder alerts. Issuing a spare against a work order records its cost against the machine. Read more about linking maintenance and inventory and spare parts criticality.
6. Technician mobile app
Technicians see their assigned jobs, scan the asset, follow the checklist, record readings, attach photos, log spares and close the job — on an Android phone, often offline. Without a usable mobile app, data entry falls back on supervisors at the end of the shift, and the records lose accuracy.
7. Reports and KPIs
Downtime by machine and cause, MTTR and MTBF (see how to calculate MTTR and MTBF), preventive maintenance compliance, backlog, maintenance cost by asset and spares consumption. The point is not more reports but a few numbers the maintenance manager reviews every week.
8. Later phases
- Contractors and AMCs — outside service providers, contracts, visits and costs.
- Calibration — instruments and gauges with due dates and certificates, linked to calibration management.
- Permits and safety — permit-to-work and lockout/tagout steps before risky jobs.
- Machine data — running hours or alarms read from machines or sensors to trigger maintenance automatically, the start of predictive maintenance.
- Energy — consumption by machine or utility, where meters are available.
Integrations that make a CMMS worth more
A maintenance system becomes far more useful when it shares data with the rest of the factory:
- Production / MES — a breakdown appears as downtime on the production board, and planners know a machine is unavailable. Planned maintenance windows are visible in the production plan.
- Stores and purchase — spares issues reduce stock; reorders become purchase requests.
- Accounts / ERP / Tally — spares and contractor costs flow to accounts where the accounting system offers an import or API.
- Quality — a maintenance job on a critical machine can trigger a first-piece inspection before production resumes.
Discuss integrations early. They often account for a significant share of the effort, and they depend on what the other systems allow.
How a CMMS development project runs
Discovery
The development team walks the plant, meets maintenance, production and stores, and reviews your current registers, checklists and reports. The output is a written scope: modules, users and roles, screens, reports, integrations and phases, with the assumptions behind the estimate.
Design
Screen designs and workflows are agreed before coding: how a breakdown is raised, who is notified, how a job is closed. Technicians and supervisors should see the mobile screens at this stage — they are the people who must use them every day.
Build in phases
The first phase is usually the asset register, breakdowns, work orders, preventive maintenance and the technician app for one plant or one area. Each phase is demonstrated and tested before the next begins.
Data migration
Asset lists, PM schedules and spares masters are cleaned and imported from Excel. This is often the most underestimated task: duplicate machine names and incomplete spares lists need decisions from the plant team, not just the developers.
Pilot, training and rollout
A pilot on one line or plant, training for each role, then rollout. A good partner stays close for the first weeks, fixing small issues quickly so trust in the system builds. Afterwards, a support and maintenance arrangement keeps it running and improving.
What drives CMMS development cost
Every factory is different, so a responsible development company will estimate from a scope rather than quote a fixed price for "a CMMS". The main cost drivers are:
- Number of modules in the first phase — asset register and work orders are smaller than a scope that includes spares, contractors, calibration and permits.
- Mobile app requirements — an Android app with offline sync costs more than a mobile-friendly web screen, but is often worth it on the shop floor.
- Number of plants and the complexity of roles and approvals.
- Integrations with ERP, Tally, MES or machine data.
- Data migration — volume and cleanliness of existing data.
- Reports and dashboards — standard KPIs versus many custom reports.
- Hosting and support — cloud hosting, backups and ongoing improvements after launch.
Our article on what drives custom software development cost explains these factors in more depth, and manufacturing software development cost covers factory projects specifically.
Choosing a CMMS development company
Look for a team that has built maintenance and shop-floor software before, asks to see your plant, writes a clear scope, shows working software every few weeks, and transfers the code to you. Ask how they handle offline mobile use, how they migrate asset data, and what support looks like after launch. Our guide to choosing a manufacturing software development company lists the questions to ask.
Designing the data model: the decisions that matter later
A few early design decisions determine whether a CMMS stays useful for years or becomes hard to extend. A good development company will raise them with you during discovery:
- What counts as an asset? Decide whether moulds, dies, fixtures, gauges, forklifts, panels and utilities are assets in the same register, and whether components such as motors, gearboxes and pumps are tracked separately so their history follows them when they move between machines.
- How deep is the hierarchy? Plant, area, line, machine and sub-assembly is common. Too shallow and reports become vague; too deep and technicians struggle to find the right item.
- Failure codes. A short, agreed list of problem, cause and action codes — for example "hydraulic leak / seal worn / seal replaced" — is what makes breakdown analysis possible. Free text alone cannot be analysed.
- Meter readings. Running hours, strokes or shot counts drive usage-based maintenance. Decide where they come from: manual entry, the MES, or the machine itself.
- Cost capture. Labour hours, internal rates, spares and contractor charges per work order make maintenance cost by asset visible, which supports repair-or-replace decisions.
Designing the technician app for real conditions
Maintenance technicians work with oily hands, in noisy areas, often with weak mobile signal, and usually under pressure to get a line running again. A CMMS app that works for them has:
- Scan-first navigation — scan the asset's QR tag to see its open jobs, history and checklist, instead of searching menus.
- Large buttons and minimal typing — pick lists for causes and actions, with voice notes or photos for detail.
- Offline working — jobs, checklists and asset data cached on the phone, synchronised when connected.
- Language options — checklists in the language technicians read most comfortably.
- Clear status — "waiting for spares", "waiting for contractor" and "under trial" as separate states, so supervisors know why a job is still open.
Test the app with two or three technicians during design. Their feedback in the first week will save months of low adoption later.
Rolling out a new CMMS without disrupting maintenance
- Start with breakdowns. Everyone sees immediate value when breakdowns are reported and tracked properly. It also builds the habit of using the app.
- Add preventive maintenance for critical machines first. Load PM schedules for the 20 percent of assets that cause most stoppages, then extend.
- Bring in spares once work orders are stable. Issuing spares against work orders only works when work orders are consistently used.
- Review KPIs monthly. Breakdown count, MTTR, PM compliance and top downtime causes, reviewed in a monthly meeting, keep the system relevant.
- Retire the paper register on a fixed date. Running paper and software in parallel for too long splits the data.
Signs a CMMS project is on track
- Breakdowns are raised in the app by production staff, not entered later by maintenance.
- Most work orders close with a cause code and spares recorded.
- PM compliance is reported weekly and rising.
- The maintenance manager uses the dashboard in production meetings.
- Requests for improvements come from users — a sign they rely on it.
Where Corposol fits
Corposol is a custom software development company based in Bengaluru, India, with a US company (Corposol LLC) in Montana. We build maintenance management software and other manufacturing software as cloud web applications with Android and iOS apps where they help, in phases, and we transfer all custom code to the client on final payment. If you are planning a CMMS, we are happy to review your current maintenance process and suggest a sensible first phase.
Frequently asked questions
When does a factory need a custom CMMS instead of a ready-made one?
When maintenance has to follow the plant's own way of working — its asset hierarchy, approval rules, shift pattern, spares stores and production systems — and a packaged CMMS would force workarounds or per-user fees that grow with every technician. Many small plants are well served by a ready-made CMMS; custom development pays off when maintenance needs to connect tightly with production, stores and quality.
How long does it take to build a CMMS?
A first phase covering the asset register, breakdown requests, work orders and a preventive maintenance calendar with a technician app is usually live in weeks to a few months, depending on the number of plants, integrations and approval rules. Spares, analytics and machine connectivity are added in later phases.
Can the CMMS work offline in areas with poor network?
Yes. A mobile app can store assigned work orders and checklists on the phone, let technicians complete them without a connection, and sync when the network returns. This matters in basements, utility areas and remote plants.
Who owns the CMMS code?
With Corposol, all custom code built for a project is transferred to the client on final payment, so the plant is not tied to per-user licences for its own maintenance system.
