Key facts
- Client
- Santos
- Assets
- Rotating and flow-control equipment
- Coverage
- Five asset classes and 44 asset class types
- System/CMMS
- SAP
- Focus
- Asset classification, FMEA data and asset-specific failure codes
- Delivery
- Eight weeks
Summary of the project
How Nexaan helped Santos replace generic SAP failure codes with a governed, reusable library covering 44 asset class types, delivered at less than 10% of traditional cost.
Related platform modules
- Eight-week delivery
- 44 asset class types
- Standardised, reusable SAP failure codes
The challenge: generic codes limited failure analysis
The client’s SAP failure codes were broad and insufficiently specific to the assets being maintained.
The project needed to establish consistent asset classifications and failure information across the rotating and flow-control fleet, giving reliability teams a more useful basis for recording and analysing failures.
The objective was a governed, reusable library that connected engineering failure information to SAP failure coding conventions.
Asset-specific codes across 44 asset class types
Nexaan delivered asset-specific code groups, object parts, damage and cause codes across five asset classes and 44 asset class types.
The library established a consistent reference for coding failures against the relevant asset class type. Its governed structure supported reuse, allowing the business to retain and extend the failure information as its teams and asset population changed.
Validated FMEA data connected to SAP
A validated FMEA library documented the dominant failure modes and mapped them to SAP catalog-profile conventions.
This connected the engineering description of asset failures to the structure required for recording them in SAP. Reliability teams received a consistent failure reference, while the SAP team received outputs aligned with its data requirements.
The result was a reusable foundation for asset-specific failure reporting and analysis.
SAP-aligned loadsheets ready for deployment
The failure-code library was delivered through SAP-aligned loadsheets, validated in a sandbox environment and ready to load without re-keying.
This provided a direct path from the validated engineering information to SAP, reducing the manual handling required to transfer the outputs.
The structured data also established a foundation for predictive maintenance and AI initiatives.
The results
The project delivered:
- Asset-specific code groups, object parts, damage and cause codes across five asset classes and 44 asset class types.
- A validated FMEA library covering the dominant failure modes.
- SAP catalog-profile mapping connecting engineering failure information to SAP conventions.
- Sandbox-validated loadsheets, ready to load with zero re-keying.
- A governed, reusable library designed to remain useful as teams and assets changed.
The scope was delivered in eight weeks, compared with an illustrative traditional approach of 12–18 months, at less than 10% of traditional cost.
Client feedback rated the engagement 5.0 out of 5.0 across 11 assessment dimensions, with a recommendation score of 10 out of 10.
The traditional duration and cost comparisons are illustrative estimates for equivalent scope.
Client feedback
The framework and technical depth were exactly what this work needed. The standardised output was the cleanest we have handed to SAP, and the failure-code library will hold up as our team and assets change.
Principal Reliability Engineer - Santos
Key questions
What was wrong with the existing SAP failure codes?
The client’s SAP failure codes were broad and insufficiently specific to the assets being maintained.
How were the FMEA failure modes connected to SAP catalog profiles?
A validated FMEA library documented the dominant failure modes and mapped them to SAP catalog-profile conventions.
How were the failure codes loaded into SAP?
The failure-code library was delivered through SAP-aligned loadsheets, validated in a sandbox environment and ready to load without re-keying.
How do failure codes for each asset type stay useful as teams and assets change?
The library established a consistent reference for coding failures against the relevant asset class type. Its governed structure supported reuse, allowing the business to retain and extend the failure information as its teams and asset population changed.
