Abstract
Ontologies have emerged as an important tool in the Enterprise architecture discipline to provide the theoretical foundations for designing and representing the enterprise as a whole or a specific area or domain, in a scientific fashion. This paper examines the domain of maintenance, repair, and overhaul (MRO) of the Sikorsky UH-60 helicopter involving multiple enterprises, and represents it through an ontology using the OWL Language and Protégé tool. The resulting ontology gives a formal and unambiguous model/representation of the MRO domain that can be used by multiple parties to arrive at a common shared conceptualization of the MRO domain. The ontology is designed to be conformant to ISO 13030 or the Product Life Cycle Support Standard (PLCS) standard, hence representing the state of being as per this standard especially at the interfaces between enterprises while incorporating existing reality to the greatest possible extent within the enterprises. As a result the ontology can be used to design Information Systems (IS) and their interfaces in all enterprises engaged in MRO to alleviate some of the issues present in the MRO area and to support business intelligence efforts.
Highlights
This template, Enterprise Architecture is a comprehensive blueprint for the automated enterprise that is developed from different views and perspectives [1]
This paper examines the domain of maintenance, repair, and overhaul (MRO) of the Sikorsky UH-60 helicopter involving multiple enterprises, and represents it through an ontology using the OWL Language and Protégé tool
The development of the aircraft ontology starts with the identification of the aircraft we identified for the case
Summary
This template, Enterprise Architecture is a comprehensive blueprint for the automated enterprise that is developed from different views and perspectives [1]. The ontology can be used to design information systems (for of data exchange and process standardization) across various partners involved in the Sikorsky UH-60 MRO to resolve the issues faced. The following assumptions are made: 1) We have to assume that all the involved entities would be willing to use common models as a medium for data exchange that is applicable to most defense enterprise integration problems centered on exchanging information based on rigid standards and interfaces. We have to assume that we have 100% knowledge about the exact scope, product information, usage characteristics, and minimum requirements of the entire aircraft industries, which appropriately comply with the standards defined by the H60 Helicopter Program and Aviation Maintenance, the Federal Aviation Administration (FAA), and the Joint Aviation Authorities (JAA). This is needed for ensuring that the ontology is still useful and can be adapted to at least other similar aircrafts
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
