Asset Management Center

Asset engineers and maintenance planners decide where limited crew time goes. Asset Management Center changes what that decision is based on.

One order of priority for the whole portfolio

Assets across the network are held in a single ranked view rather than assessed site by site. Teams see the portfolio in one order instead of reconstructing it from separate records.

Attention follows measured condition

Crew time is directed by the condition recorded against each asset rather than by a fixed round. Effort concentrates where the portfolio shows it is warranted.

Work sequenced into a programme

The order of work is held across the whole portfolio, so maintenance is planned as a programme rather than assembled outage by outage.

Decisions about which assets are maintained and which are replaced have to be defensible. Asset Management Center is built so the order of work can be examined.

Records that pass validation before they count

Validation checkpoints hold incomplete, duplicate, and inconsistent records out of the portfolio view, so the order of work rests on records that have been checked.

Every position traces back to its record

Condition, evidence, and work history stay linked to the asset they belong to, so any place in the order can be traced to the record it came from.

Ownership is never ambiguous

Each asset carries its owner and its review history, so responsibility for a decision is clear at the time it is taken and afterwards.

Anchored to the standards you already work to

Quality processes are aligned to ISO 9001. Records and review history are kept in a form that supports the reporting a network operator already produces.

Prepared for NIS2 obligations

Asset Management Center is designed for the obligations placed on critical infrastructure operators, and for the asset and evidence records those obligations rest on.

Records stay under your control

Operators who require it can run Asset Management Center inside their own infrastructure, so asset records, evidence, and review history remain in their own environment.

Maintenance and replacement are the two largest lines an asset owner controls. Both are decided from the same portfolio view.

Replacement planned as a programme

Replacement is planned across the portfolio rather than asset by asset, so the programme follows recorded condition and capital is committed in that order.

A budget case that survives review

Spend is tied to a ranked portfolio, so a maintenance or replacement budget is presented as an ordered list with the records behind it rather than as an aggregate estimate.

Interruptions that never reach the numbers

Work that follows recorded condition reaches assets while the condition is still developing. Interruptions that do not occur never count toward SAIFI, and their minutes never reach SAIDI.

Three ways of deciding what to work on next are common across network operators today. Each of them leaves the portfolio unordered.

Asset registers that record but do not rank

A conventional register holds what an asset is, where it sits, and what has been done to it. It does not place the portfolio in an order, so the question of what to attend to first is answered outside the system. REDXGRID returns the portfolio already ordered by recorded condition.

Priority rebuilt by hand each planning round

Ranking is often reassembled for every budget cycle from records held in separate places. The result depends on who assembled it and is difficult to review afterwards. REDXGRID holds one portfolio view that stays current between planning rounds.

Programmes driven by age and interval

Time-based planning replaces equipment because it has reached an age, not because its condition warrants it. Sound assets are retired early while deteriorating ones wait their turn. REDXGRID orders the programme on recorded condition.

An order of work is only useful if the reasoning behind it can be examined. This is what a position in the Asset Management Center portfolio rests on.

One record per asset, not several

Condition, inspection evidence, work history, and ownership are held against the same asset record. The order of the portfolio is derived from that record rather than from a copy of it.

Intake is checked before it counts

Incoming records and evidence pass validation before they reach the portfolio view. Incomplete and duplicate entries are surfaced rather than ranked, so the order is not distorted by data that was never verified.

The order can be reproduced

Ranking is produced by explicit, repeatable criteria applied to the same records. A position in the portfolio can be re-derived and reviewed rather than accepted as an opaque output.