This White Paper outlines the data structure that HighStone applies in holding Asset Maintenance data records. These definitions include the class of Defect or Damage that can be recorded against Asset Records, Classification of a recorded Defect in terms of criticality and risk, application of required Correction or Fix Times against a Defect Classification.
Routine Maintenance checks or inspections / surveys are a common regime in industry and the recording of Asset Condition may also be recorded and managed through the same data recording mechanisms. This enables HighStone to record ‘OK’ or ‘Satisfactory’ status against Asset Records as a positive record of assessment, and not rely on a default status of satisfactory unless a defect has been recorded.
This White Paper outlines the data requirements and functional definitions and actions that are required to undertake an import of Asset Records in to HighStone from an external source. Typically such data is sourced from flat spreadsheet files with multiple columns defining the attributes associated with the source asset records.
HighStone Asset Records are held in a single definition accommodating all Asset Types required in the contract database. Attribute definitions are defined and held as child records to the main assets records, with different classes of asset attributes defined for each class of asset.
This White Paper outlines the data structure that HighStone applies in holding Asset Survey and Routine Maintenance data records. These definitions include the type of Asset Survey that can be raised against Asset Records and record details of Asset Condition and Cyclic Maintenance Activities.
HighStone is designed to build up and hold a complete history of the maintenance and checking of all assets held within the contract database. Additional maintenance records can be created to monitor specific aspects of an asset type and provide a complete history log from within the same data framework.