- This line was added.
- This line was removed.
- Formatting was changed.
|UI Text Box|
Each time a maintainer interacts with equipment, a work order record captures in linguistic text their observations of the asset and a record of what was done, when, and how. These records contain unstructured text containing jargon, abbreviations, and incomplete data. Of primary interest are the needs to establish the as-found condition, the causality of failure regarding the failure mechanism and cause, and what maintenance work was done. This data is often in the work order texts but is not stored in a machine-readable way. These shortcomings lead to inadequate information about the asset condition, the failure cause and what work was actioned. As a result maintenance staff rely heavily on word-of-mouth and ad-hoc data exchange. The absence of standard schema for maintenance data representation hinders the ability to convert semantic meanings in the maintenance work orders into axiom based reasoning and useful information. We need to enable maintainers and the staff that support them to efficiently capture, retrieve, absorb, process and exchange knowledge about equipment and maintenance work.
Initial project areas for Theme 1 include: