Live in weeks, not quarters
Most CMMS projects stall because someone decided the whole estate had to be perfect before anyone could raise a work order. Start with what matters, run real jobs immediately, and refine from there.
Getting live
Four weeksProgress
2 of 4 weeks
W1
Import assets and sites
NeoGen + your data
A spreadsheet of what you own is enough to start. Codes, locations, categories.
W2
Set up your critical PMs
Your maintenance lead
The twenty schedules that matter most, not all two hundred.
W3
NowTechnicians on the app
Your team
One session, then real jobs. Adoption comes from using it, not from training slides.
W4
Reporting and handover
NeoGen
Your scheduled reports configured, and the team running it without us.
You are running real work orders in week one. The rest is refinement.
Bring what you have
A spreadsheet of your assets is enough to start. We map your columns rather than asking you to rekey anything.
One site first
Prove it on one building. Every site after that is faster because the naming and the categories are settled.
Training that fits the role
Thirty minutes for technicians, an hour for managers. Not one long session nobody remembers.
Your spreadsheet, mapped
The import is where these projects usually get stuck. It should take an afternoon.
- Your column names mapped to fields, with a preview
- Duplicates, bad dates and missing values flagged before anything is written
- Nothing is imported until you have looked at it and said go
Your spreadsheet, mapped
assets.csvAsset CodeAsset ID
218 unique values, no duplicates
DescriptionName
Trimmed and title-cased on import
Bldg / FlrLocation
Split into building and level
Install DtInstalled
Parsed as DD/MM/YYYY
Notes—
Free text kept, not mapped to a field
Pilot, then spread
The first building is where you learn how you want to name things. Everywhere else inherits that.
- One site live in week one, running real work orders
- Later sites reuse the categories and priorities already agreed
- Sites with a different rhythm get their own setup pass
One site first
2 of 4 live- Live
Block B
96 assets · Week 1
The pilot. Where the asset naming got settled.
- Live
Block A
74 assets · Week 3
Took two days, using Block B’s categories.
- Importing
External works
48 assets · Week 5
Grounds and car parks — different asset classes.
- Planned
Pune plant
268 assets · Week 9
Runtime-based schedules, so a separate setup pass.
Prove it on one building. Every site after that is faster, because the decisions are already made.
Getting people to actually use it
Adoption is not a training problem. It is a design problem, and then a first-week problem.
- Short sessions aimed at the three things each role does daily
- Real jobs from day one rather than a sandbox nobody takes seriously
- A go-live checklist, so nothing is assumed to be done
Training, by role
Not one long sessionTechnicians30 min
Open a job, tick the checklist, attach a photo, close it.
Maintenance managers60 min
Raise and assign work, build a PM schedule, read the backlog.
Directors20 min
Find the three reports you will actually look at.
Go-live checklist
Explore the rest of the platform
Ready to simplify your maintenance operations?
Book a personalized demo and see how NeoGen CMMS fits the way your team already works.
Implementation questions
How long does it really take?
For one site with a clean asset list, a few weeks to being genuinely useful. What extends it is almost never the software — it is deciding how you want to name and categorise your assets, which is worth doing properly once.
What do you need from us?
A list of your assets in any tabular form, someone who knows how your maintenance actually runs, and access to your technicians for one short session. That is the honest minimum.
Can we import our maintenance history?
Yes. Past work orders can come across with the assets, so you keep the record you already have instead of starting from zero or running two systems in parallel.
What if the pilot does not go well?
Then we would rather find out in week three on one building than in month nine across seven sites. That is the whole reason for piloting rather than a big-bang rollout.