Service lifecycle
Six stages. The same team.
Every product UBM supplies is wrapped in the same six stages, from the plan on the drawings to the certificate that says the disk was wiped. They are not six departments handing work to each other: the engineer who surveyed the site is on the call when it breaks.
Service lifecycle
Six stages, one team
-
01
Planning
Assess the environment, agree the outcome, sequence the work.
We start with the environment you have, not the one described in the last proposal. Most of the value in planning is finding the constraint nobody wrote down: a procurement window, a contract with fourteen months left, a comms room that cannot take another two kilowatts.
What happens
- A working session with the people who will live with the result, not only the people who sign for it.
- Site survey and current-state assessment: what is installed, how old it is, what is under warranty and what is quietly out of support.
- Constraint mapping: budget cycle, procurement route, downtime windows, existing agreements, power and cooling headroom.
- Options with the trade-offs stated plainly, including the option of doing less than you asked for.
- A phased plan with the sequence, the dependencies and dates the organisation can actually absorb.
What you are left holding
- A current-state assessment document
- An option comparison with indicative cost and effort
- A recommended architecture with the reasoning attached
- A phased plan with dependencies and target dates
- Success measures agreed in writing before anything is ordered
-
02
Procurement
Specify, source and supply against a committed delivery date.
A design is only as good as what actually arrives. Procurement is where a specification quietly gets substituted and a programme quietly slips, so the bill of materials, the lead times and the delivery date are held in one place and you hear early when one of them moves.
What happens
- Bill of materials priced against the approved design, with our authorisation level for each vendor confirmed in writing.
- Lead times checked before the quotation goes out, so a delivery date is a commitment rather than an estimate.
- Constrained parts flagged with an alternative and the technical difference stated. Nothing is substituted quietly.
- Purchase, import, logistics and short-term storage handled by us, including the case where the site is not ready yet.
- Goods received and checked, serial numbers recorded, warranties registered in your name and assets tagged before delivery.
What you are left holding
- A priced bill of materials tied to the approved design
- Confirmed lead times and a committed delivery date
- Warranty registration and serial-number records in your name
- An asset register populated on day one, not after go-live
-
03
Deployment
Install, configure, test and hand over with the documentation.
Deployment is where discipline shows or does not. Anything that can be built and tested off site is built and tested off site, so the hours spent on your floor are the hours that could only happen there.
What happens
- Detailed design signed off and a method statement agreed before anyone opens a ceiling.
- Staging and pre-configuration in our workshop: imaging, firmware baselines, switch configs, rack builds.
- Installation to the agreed method statement, with permits, inductions and access arranged in advance.
- Commissioning and testing against the acceptance criteria written at planning.
- Handover: documentation, credentials transfer, and a working session with the team who inherits it.
What you are left holding
- As-built drawings, rack elevations and port schedules
- Certified test and commissioning results
- Configuration backups and a firmware baseline record
- An administrator handover session, and a snag list closed in writing
-
04
Operation
Run it day to day, resolve faults, protect user productivity.
Once it is live it is judged on two numbers: how fast somebody answers, and how fast the user gets back to work. Everything else, the portal, the reporting, the reviews, exists to protect those two.
What happens
- One place to log a fault: phone, email or portal, all landing in the same queue.
- Severity classified against agreed response and restoration targets, so priority is a rule rather than a negotiation.
- Remote diagnosis first; on site when remote will not fix it, with the right part already in the van.
- Vendor escalation, warranty claims and RMAs handled by us. You should never be on hold to a manufacturer.
- A root-cause note on anything that recurs, and a change to stop it recurring again.
What you are left holding
- A ticket history you can audit
- Response and restoration performance measured against target
- A recurring-fault register with owners and dates
- Spares and RMA status visible rather than assumed
-
05
Maintenance
Patch, monitor, verify backups, keep the estate current.
Maintenance is the difference between an estate that decays quietly and one that gets better. The work is unglamorous, patching, firmware, backup verification, capacity, and it is the reason year three is calmer than year one.
What happens
- Proactive monitoring on the things that fail first: uplinks, controllers, power, storage capacity, backup jobs.
- Patch, firmware and signature cycles run in an agreed window rather than in an emergency.
- Configuration and backup verification, including a restore actually performed on a schedule.
- Asset and warranty tracking, so an expiry is a planned event and a refresh has a budget line before it has an outage.
- Scheduled service reviews with the roadmap revised against what the business is now doing.
What you are left holding
- A monthly service report written to be read, not filed
- An asset and warranty register that stays true
- Risk and capacity flags raised before they become incidents
- An improvement roadmap reviewed every quarter
-
06
Disposal
Retire assets safely: data wiped, records closed, hardware recycled.
Every asset eventually leaves. Done badly, a decommissioned server becomes a data-protection question nobody can answer and a store room fills with equipment nobody is allowed to throw away. The exit gets the same documentation as the install.
What happens
- Retirement planned against warranty expiry and the refresh it belongs to, so the replacement is live before the old kit goes.
- Decommissioning to a written sequence: dependencies checked, configurations archived, licences and links released.
- Data sanitised to a documented standard, with a wipe or destruction certificate against each serial number.
- Equipment collected on the same visit as the installation, then passed to a licensed recycler rather than to a corridor.
- The asset register closed off, so what left the estate is recorded as carefully as what entered it.
What you are left holding
- A decommissioning plan with dependencies checked before anything is powered down
- Wipe or destruction certificates against serial numbers
- Archived configurations and released licences
- Recycling documentation from a licensed handler
- An asset register closed and reconciled
Delivery model
How the work actually runs
Four phases one engagement moves through, in order, with governance applied at every one of them. Each phase carries the lifecycle stages named under it.
Governance across every stage
- Scope
- Documentation
- Safety
- Security
- Quality
- Service performance
Governance
Six things checked at every stage
Governance is not a document produced at the end. These six are reviewed at each stage gate, and a stage does not close until they are answered.
-
Scope
What is in, what is explicitly out, and who signs a change. Scope creep is a documentation failure before it is a commercial one.
-
Documentation
As-built, not as-designed. Drawings, port schedules, configurations and credentials handed over in a form the next engineer can use.
-
Safety
Method statements, permits, inductions and PPE agreed before anyone opens a ceiling or a riser. Work stops when the safety case does.
-
Security
Least privilege on our own access, named accounts rather than shared ones, and every credential we were given rotated at handover.
-
Quality
Acceptance criteria written before the work and tested after it. A snag is closed when the client agrees it is closed.
-
Service performance
Measured against the target in the agreement and reported monthly, including the months it was missed.
How engagements are structured
From transactions to relationships
Most of our work still starts as a project: a floor to cable, a fleet to refresh, a firewall to replace. It should not end as one. A cabling job that leaves site with no support agreement becomes somebody else’s problem in eighteen months, and the organisation pays twice: once to find out what was installed, and again to fix it.
So the commercial model is deliberately moving from one-off supply toward continuing relationships: support agreements attached to what we install, managed service contracts with response targets written into them, and lifecycle agreements that treat a warranty expiry as a planned event rather than an incident.
That is better for the client because the cost becomes predictable and the accountability becomes continuous. It is better for us because we inherit the environment we built, documented the way we documented it. Nobody spends the first four hours of an incident working out what is actually in the rack.
- Project Defined scope, fixed deliverables, formal handover with documentation.
- Support agreement Attached to what we installed. Agreed response and restoration targets, vendor escalation included.
- Managed service Monitoring, patching, backup verification and monthly reporting under one recurring agreement.
- Lifecycle Asset register, warranty and refresh planning, and a roadmap reviewed each quarter.
Start with the assessment.
The current-state document is yours whether or not the next stage is ours.