Our client required a centralised database that is 100% suitable and compatible with each of their site’s requirements. This included placeholders for any variation of asset types, components and the best suitable/applicable maintenance tactics.  On Key provided the perfect match.

Client Background

Our client is one of the leading role players in the South African diamond mining environment with various operations locally and internationally. Our client produces rough diamonds mainly for the export market all over the world. They are renowned for producing some of the largest, most expensive and most valuable diamonds in the world.

Key Challenges

• Development of a centralised and standardised group DB that is 100% suitable and compatible with each site’s requirements.
• The centralised, group DB must comply with AM best practices and good EAMS configuration standards and principles.
• Although the DB is generic, the configuration must be done in such a way that it could be used for any variation of Asset Types, components and best suitable/applicable maintenance tactic selection.
• The list of applicable maintenance tasks should accommodate the four main categories of maintenance tactics namely Usage Based Maintenance, Condition Based Maintenance, RTF and Design Improvement.
• The DB must be capable of generating all required AM related reports.
• The DB must be clean, streamlined, easily maintainable and user friendly for all levels of users

Quote

“The development of a new, centralised, group On Key database will greatly improve our ability to standardise on AM standards, reporting and general EAMS configuration. Sharing of a centralised DB will establish effective and streamlined asset and maintenance tactics configuration considering best available information within the group and good practices.” Client – Asset Manager

Pragma Intervention

• Analysed current needs and requirements for EAMS (On Key) functionality for the group.
• Analysed the current DB’s in order to compare the configuration structures and mater data currently being used.
• Proposed a new centralised DB for the group by developing a generic Asset Type Tree to be used by the different sites. By using On Key’s placeholder functionality, different maintenance tactics could be developed that will be suitable for any configuration of a certain Asset Type with corresponding components.
• Pragma used an existing ACP library (On Key DB) as a basis for the development of the new DB for the client since the library was developed on the same development principles containing many of the required basic Asset Types.

Value Add

•  The development and implementation of a centralised and standardised group DB will achieve the following:
• Reduction in On Key licencing fees since there will be one On Key DB instead of separate licences per site
• A new On Key DB that looks and works the same for all sites. Standardisation of data, Asset and Asset Type tree structures, processes, coding conventions, configuration and On Key functionality.
• The sharing of knowledge, learnings and best practice amongst the different sites for continuous improvement. The improvements are updated on the centralised DB to benefit all sites.
• Less development work since all Asset Types are developed once. Complete built-in flexibility to accommodate special requirements for each site including analysis and reporting requirements
• Endless possibilities for variations on Asset Types, components and tasks to standardise on generic Asset Type ACP’s (Asset Care Plans) allowing for best possible maintenance tactics.
• Simplified and easy to use interface for the standard users to manage assets and maintenance requirements from the Asset Tree.

Tools and Technology

• On Key 5 with:
  • Placeholder functionality
  • ACP developer module
  • BRR (Business Rules Reference) document
  • Used to consolidate the different site’s On Key configuration data to establish standardisation.