The current corpus of scientific literature when considering the subject of interoperability, presents wide and varied attention to the research, development and application of ontologies to develop new approaches and technologies to problem domains. A large amount of this research reports upon ontologies that are built to support specific contexts with exact aims, each of these having been built wholly within their respective contexts from the ground up, thereby meaning they are domain specific and cannot profit from exposure to different viewpoints by being able to represent more than just one. The issue with this is that when considering interoperability and communication between different systems, contexts and domains, the seamless transfer of data, information and knowledge is unachievable, due to the fact that the very premise of understanding different viewpoints and domains and how they interrelate is the cornerstone to achieving interoperability (Borgo and Leitão
2004). This can be addressed by the development and application of a reference ontology (core ontology) so as to construct a common basis for the sharing of information and knowledge between multiple domains to therefore enable interoperability. Figure
1 presents a view upon the classification of the different types of ontologies. Foundation ontologies are high level ontologies (sometimes called upper ontologies or top-level ontologies) that comprise generic (domain independent) concepts, relationships and axioms that are able to represent and relate to any context dependent concept. As such, they are context independent and have very few constraining axioms. Examples of foundation ontologies are: the Standard Upper Ontology (SUO) (Neches et al.
1991), the Suggested Upper Merged Ontology (SUMO) (Niles and Pease
2001), Descriptive Ontology for Linguistic and Cognitive Engineering (DOLCE) (Gangemi et al.
2002) and Cyc-Ontology (Matuszek et al.
2006). Core ontologies are ontologies that have been specialised to some extent and are therefore broadly context dependent, but represent a number of different domains (Nardi et al.
2015). They are based upon and utilise concepts and relationships that exist within foundation ontologies. These ontologies still contain a minimal set of generalised concepts. These can be used as reference ontologies to be employed as building blocks to promote interoperability for much more domain specific and contextually dependant ontologies, yet enable communication between them due to the shared ‘common’ core concepts used to build them. Examples of core ontologies are: the Core Product Model (CPM) from the National Institution of Standards and Technology (NIST) (Foufou et al.
2005), the Manufacturing Core Ontology (MCO) (Chungoora and Young
2011a; Chungoora et al.
2012,
2013), the Manufacturing Core Concepts Ontology (MCCO) (Usman et al.
2011), the Manufacturing Information Systems (MIS) ontology (Hastilow
2013) and the UFO-S ontology (Nardi et al.
2015). Domain ontologies (Guarino
1998a,
b) are ontologies that are wholly context dependant and are thus very specialised for their intended representation and purpose, these apply to specific activities.
Collaboration, enterprise and supply chain management ontologies
There are a number of widely available ontologies that centre upon collaboration, enterprise and supply chain management. Table
1 portrays an assessment of accepted and notable ontological approaches, it sets out the ontologies considered, their context, the level of formalisation, their key concepts and their approach. The aim of this is to illustrate both the commonalities and differences between the approaches.
Table 1
Assessment of ontologies relating to collaboration, enterprise and supply chain management
| No reference of industry sector | Knowledge Interchange Format (KIF) | Activity, state, time. Organisation, goal, agent, role, constraint, resource, use consume release, produce, skill, authority | To support the Enterprise model development so as to answer queries in industrial environments |
Enterprise Ontology (Uschold et al. 1998) | No reference of industry sector | Ontolingua (based upon Knowledge Interchange Format (KIF) | Entity, role, activity, person, time | Enhancing human Communication and support interoperability |
| No reference industry sector | Knowledge Interchange Format (KIF) and Unified Modeling Language (UML) | Enterprise, organisation, process resource, product. Goal, strategy, objective, process, person. Plan, activity. Product, information product, material product | To provide foundation for designing, reinventing, managing and Controlling collaborative and distributed enterprises |
Virtual Enterprise ontology (Soares et al. 2000) | Electronics: Semiconductors | Natural language statements for concepts | (founded upon the Enterprise Ontology) Organisation, order, plan, resource, product, activity, customer, supplier | To improve production planning and control system to support a virtual enterprises |
Supply Chain Ontology (Ye et al. 2008) | Electronics: PCB Printing | Web Ontology Language (OWL) and Semantic Web Rule Language (SWRL) | Supply chain, supply chain structure, role, purpose, activity, resource, performance, performance metric and transfer object | Enabling semantic integration between heterogeneous systems in a supply chain |
SCOR-FULL (Zdravković et al. 2011) | Product engineering—snow making facility | Web Ontology Language (OWL) | Agent, resource item information item, physical item, configured item and communicable, item, function, course, setting | Ontological framework for semantic interoperability between enterprise information systems for supply chain networks |
Business-OWL (Ko et al. 2012) | Construction and manufacturing examples applied | Web Ontology Language (OWL) | Task, method, actor, product type, resource pattern, collaboration mode, business goal, thing, preconditions, sourcing type, collaboration mode, process type | Provides an ontology that can decompose high levels business goals to lower level operational tasks |
Global Supply Chain ontology (Wang et al. 2013) | Iron and steel production sectors | Web Ontology Language (OWL) and Semantic Web Rule Language (SWRL) | Company, product, location, policy, supplier, customer, product type | Ontology to provide decision support for the management of supply chains |
EAGLET Ontology (Geerts and O’Leary 2014) | Soup caning production process | Unified Modeling Language (UML) | Thing, event, agent, location, equipment | Ontology to represent a supply chain of things |
Each of the ontologies represented in Table
1 seek to enable and enhance interoperability, be it for business, enterprise (virtual and distributed) or supply chain management. The enterprise and business ontologies are pertinent in that they represent aspects of organisations and can be applied to supply chain management and are therefore relative to context of the research within this paper. For interoperability to be successful, the semantic definition of concepts must be absolutely precise. For without this, discordancy in meaning can exist between concepts, thus hindering interoperability.
The TOronto Virtual Enterprise (TOVE) project (Gruninger and Fox
1996; Fox et al.
1996,
1997) sought to develop an enterprise ontology that could represent precise enterprise structures to then be used to model process integration within an enterprise. The purpose of this was to enable ontologies to be developed to answer queries within industrial environments to support the needs of organisations. It is comprised of a set of ontologies, those being: resource, organisational, product design, product requirements, manufacturing activity, manufacturing resource, order, transportation, quality, inventory and cost. The activity-state-time ontology can be considered to be an upper or top level ontology for the set of ontologies. The Enterprise Ontology (Uschold et al.
1998) was developed from the research conducted within the Enterprise Project. It consists of five main sections, which are: (i) activities and processes, (ii) organisation, (iii) strategy, (iv) marketing and (v) time. The premise of the ontology is to represent and model an enterprise utilising Ontolingua (Gruber
1993) and sets out a number of core concepts and relationships for just this purpose and is consistent with the TOVE ontologies. Madni et al. (
1998, (
2001) put forward the IST Distributed Enterprise Ontology (IDEON). This ontology was developed in an effort to unify the concepts and relationships of enterprise modelling and process/workflow management with respect to the domain of systems engineering. It has been developed so that it is compliant with the Process Specification Language (PSL) (ISO 18629). The IDEON ontology consists four of perspectives, these being (i) the Enterprise Context View, (ii) the Enterprise Organisation view, (iii) the Process view and (iv) the Resource/Product view.
Bjeladinovic and Marjanovic (
2014) discuss the lexical commonalities and differences for TOVE (Gruninger and Fox
1996; Fox et al.
1996,
1997), EO (Uschold et al.
1998) and IDEON (Madni et al.
1998,
2001). They show there are differences in the way concepts are grouped. There are similarities too, an example of this is the concept for resource, it is shared between the three ontologies, albeit with slightly different naming conventions. This is an important concept relating to supply chains, resources are consumed to produce, manufacture and deliver products and services. Additionally time and location are present, they, again are useful for the representation of supply chains and the management thereof. The Virtual Enterprise Ontology (VEO) (Soares et al.
2000) is built upon EO, thus utilising many of its concepts and relationships. Whilst focused upon planning and control, examples of key concepts are organisation unit, resource, product and activity. However, Grubic and Fan (
2010) state that EO has perhaps focused too much upon enterprise knowledge and not enterprise ontology, this observation is levelled at TOVE and parallels could be drawn against VEO too.
The Supply Chain Ontology (SCO) (Ye et al.
2008) sets out a number of generalist concepts and relationships that represent Supply Chain Management (SCM), examples being: supply chain, supply chain structure, performance, objective, activity and resource to highlight a few. SCO applies the Supply Chain Operations Reference model (SCOR) (Supply Chain Council
2014) to help describe the performance aspects. Zdravković et al. (
2011) state that reference models ‘often lack semantic precision’, to which they present the SCOR-Full ontology. This was developed by firstly modelling the SCOR concepts and relationships to semantically define them in a more rigorous manner, from this the SCOR-Full domain ontology was developed to represent supply chain operational knowledge. It utilises the SCOR definitions so as to counter the ‘semantic inconsistencies of a SCOR reference model’. The main concepts are: agent, course, resource item, function, quality and setting, which, are mapped to the SCOR input/output elements. Sadly, the ontology does not define in detail supply chain activities. What can be gleaned from these two ontologies is that they both represent resource as an important concept. The SCO concept of resource relates closely to the TOVE, EO and VEO definitions, but the SCOR-Full terminology and representation is slightly different, where a resource item can be an information item or physical item. Additionally, in difference to the other ontologies, SCOR-Full models a course (i.e., an activity, process, method, procedure, strategy or plan) as having a setting (a description of the environment), which, can be considered a viewpoint or context.
Business-OWL (BOWL) (Ko et al.
2012) is an ontology that employs the Web Ontology Language (OWL) to represent collaborative business processes as a ‘hierarchical ontology of decomposable business tasks’ at a high level. The tasks represented by BOWL are those of: sales and marketing, inventory management, procurement and order management together with logistics and payment. Whilst not strictly representing supply chains, it exhibits many businesses activities that could be utilised within such a domain, those of business to business information systems. As the authors state, the tasks within BOWL can be decomposed and specialised by way of differing requirement sets, thereby representing different activities. Ko et al. (
2012) cite the SCOR and MIT Process handbook (Malone et al.
2003) in relation to their work, but do not explicitly state whether or not they apply. Many of the BOWL concepts would need to be interpreted and specialised to map them to the aforementioned ontologies. A difficult concept to relate is task, this could be mapped to activity in TOVE, EO, VEO and SCO. EO states that activity means ‘something to be done’, but task within BOWL stems from the Hierarchical Task Network and breaks down into compound and primitive tasks, to which actions are called primitive tasks. Thus the semantics are somewhat difficult to align.
A Global Supply Chain (GSC) ontology is expounded by Wang et al. (
2013) who seek to develop an ontology that goes beyond what is perceived as the traditional scope for a supply chain. Not only do they consider internal factors, but, external factors that an affect organisations and suppliers within a network on a global scale. It is comprised two ontologies: the core ontology consisting of five main classes, those being company, product, primary market, policy and financial status; the competitor ontology consisting of eleven main classes, which are corporation, financial status, supplier, customer, product, product type, price, price strategy, inventory and location. It must be noted, that whilst the ontology considers market environments, it does not consider wider factors that are part of GPN approaches, for example, those of the natural environment, political factors, social factors and technological factors. The GSC ontology does share some concepts with the other ontologies in Table
1. For example product can be mapped to IDEON and VEO, then to SCOR-Full and BOWL, although, for these, the names and classification structures are slightly different.
Geerts and O’Leary (
2014) set out the Event, AGent, Location, Equipment, and Thing (EAGLET) ontology to represent a supply chain of things. The purpose of this is to enable interoperability throughout and along a supply chain relative to any one partner within it. Moreover, it supports multiple viewpoints for a standard set of economic phenomena relative to ‘an individual thing’s (object) identification information’. Those viewpoints are physical flow, chain of custody (i.e. who owns something at any point in time) and chain of ownership. As per the EAGLET ontology’s name sake, it is composed of five primitives, those of: event, agent, location, equipment, and thing, along with sets of relationships, modelled using Unified Modeling Language (UML) (Object Management Group
2012). It therefore needs to be more rigidly semantically defined for it to be used computationally to promote interoperability. Nonetheless, location is present within IDEON and agent is represented within SCOR-Full.
What can be derived from the ontologies represented within Table
1, is that there are many numerous concepts that exist for all of them. Some of these concepts are represented between a number of the ontologies, sometimes necessitating that concept names be interpreted, but, their semantic meaning is not always the same. When relating these ontologies to the context of risk and GPN, it can be said that none of them contain concepts to represent risk and it is only the GSC ontology (Wang et al.
2013) that represents market environments that relates to GPN. All of the ontologies do not represent GPN factors such as social, political, environmental or technological that can impinge upon and influence GPN.
Manufacturing reference ontologies
There are approaches that have been reported, showing efforts to devise tools, techniques and methods to address the issue of cross-domain interoperability. Borgo and Leitão (
2007) set out a view upon the role of foundation ontologies and apply them to the domain of manufacturing control, showing that they can enhance and support interoperability between different applications. Panetto and Molina (
2008) and Panetto et al. (
2012) reinforce this view of the need to enable enterprise integration and interoperability within the wider the manufacturing enterprise to share information and knowledge between systems to support the development of technological solutions. Further aspects are put forward by Young et al. (
2007), showing that heavy-weight logical approaches can be used to share manufacturing process information. Young et al. (
2007), point towards the need to share such information and knowledge between different domains and show the value of linking both foundation ontologies and domain ontologies to enable a multi-domain sharing approach. Table
2 puts forward an assessment of current literature that focuses on the development of reference ontologies for various manufacturing contexts.
Table 2
Assessment of developed ontologies relating to manufacturing reference ontologies
Core Product Model for Product Lifecycle Management (Foufou et al. 2005) | Planetary gear system | Unified Modeling Language (UML), eXtensible Markup Language (XML) | Artifact, feature, function, flow, form, geometry, material, behaviour, requirement, specification, common core relationship, common core object core product model | CPM to supports information needs of product lifecycle management (PLM) |
Athena Interoperability Framework (AIF) (Athena 2006; Chen et al. 2009) | No reference of industry sector | Web Ontology Language (OWL) | Task, process, activity, location, gateway, capability, material object, information object, time, time point, duration, state, behaviour, rule, parameter, condition, event, role, flow, input, output, control, resource | Provides ways in which to view and address interoperability issues |
| Aerospace: design for manufacturing | Common Logic based Process Specific Language (ISO 18629) | Process, resource, manufacturing process, manufacturing resource, view | Value of linking foundation and ontologies to enable multi-context knowledge sharing. Ontology for manufacturing information sharing applied to PSL (ISO 18629) |
Feature Oriented Design and Manufacture ontology (Chungoora and Young 2011a, b) | Aerospace: design for manufacturing | Knowledge Framework Language (KFL)—Common logic based first order logic | Object, activity, activity occurrence, function, feature, hole, material, dimension, tolerance shape, measure item, geometry item, assembly, location, part, part family | Reference ontology for feature-orientated design and manufacture concepts |
Product-Service Systems Ontology (Annamalai et al. 2011) | No context given | Unified Modeling Language (UML) | Need/requirement, product-service, PSS design, PSS life cycle, business model, support system (supply network, infrastructure), PSS outcome (environmental, economic, social), stakeholder (supplier) | Reference Ontology to represent the growing domain of Product-Service Systems |
Manufacturing Core Concepts Ontology (Chungoora et al. 2012) | Aerospace: design for manufacturing | Knowledge Framework Language (KFL)—Common logic based first order logic | Feature, design feature, manufacturing feature, standard feature, realised part, manufactured part, service part, part family, hole, activity, function, manufacturing facility, manufacturing process, manufacturing resource, process plan, manufacturing method | Product Lifecycle reference ontology to improve Product Lifecycle Management (PLM) configuration for manufacturing knowledge sharing between domains |
| Aerospace: design for manufacturing | Knowledge Framework Language (KFL)—Common logic based first order logic, Web Ontology Language Description Logics (OWL-DL) | Resource, capability, process, enterprise, behaviour | Exploration of heavyweight ontological approaches to support the consolidation of product-centric standards |
Assembly Reference Ontology (Imran 2013) | Aerospace: design for assembly | Knowledge Framework Language (KFL)—Common logic based first order logic | Build upon the Manufacturing Core Ontology and adds the following concepts relative to assembly: process, material, operation, spatial location, shape attribute, product version, product feature, BOM, component, auxiliary material | Assembly reference ontology to support the sharing of knowledge between assembly design and assembly process planning domains |
Manufacturing Intelligence Systems ontology (Hastilow 2013) | Aerospace: design for manufacturing Systems | Knowledge Framework Language (KFL)—Common logic based first order logic | Input, output, constraint, resource, system, target, knowledge, data, feedback, response, decision, timescale, manufacturing method, collaboration, prediction, person, delivery, metric, performance, risk, | Manufacturing intelligence System Reference Ontology to promote interoperability between manufacturing systems |
Sustainability manufacturing ontology (Borsato 2014) | Bicycles | Unified Modeling Language (UML), Protocol and RDF Query Language (SPARQL) and OWL2Query | Activity, data, organization, place, process, product, property and resource | Sustainability manufacturing ontology to promote interoperability between products and processes |
It has been acknowledged that undertaking research into the issue of sharing information and knowledge between different domains can be an arduous task. The crossing of boundaries between contexts and disciplines can encounter difficulties due to need to relate differing points of view and derive a common and accepted understanding, this often requires inordinate amounts of time and effort to accomplish this (Pisanelli et al.
2002). Nonetheless, there are other applicable research efforts that have focused upon interoperable heavyweight ontological approaches (Chungoora and Young
2011a,
b; Chungoora et al.
2012,
2013; Imran
2013; Hastilow
2013), which seek to further the push towards formal, computable, semantic interoperability, specifically Common Logic based approaches (ISO/IEC 24707). Each of these approaches has applied an augmented version of Common Logic to the issue of interoperability to develop sets of concepts to form reference ontologies.
CPM is put forward by Foufou et al. (
2005), developed by the NIST. It uses the now well accepted form, function and behavior views for the representation of product information to support the needs of product lifecycle management systems. Other concepts within the model are artifact, feature, flow, geometry, material, behavior, requirement and specification. CPM applies UML to represent the model and expressed in XML for computational purposes. As such, this too product centric to be of use relative to risk and GPN domains. Additionally, it is not semantically defined rigorously enough to be directly of use. Nonetheless, flow is an important concept in the reference ontology. The European Framework Programme 6 (FP6) Athena project produced a methodology called POP* (Process, Organisation, Product and others), which, is focused upon developing ways to capture design and management issues which occur during enterprise collaboration. Its motivation is to enable interoperability between collaborating enterprises using different modelling languages. A number of the concepts listed in Table
2 are important to the needs of the FLEXINET reference ontology, such as activity, location, gateway, event and state. POP* also has the concept flow represented within with maps directly the CPM flow concept. Both CPM and POP* do not represent concepts related to risk or GPN.
Annamalai et al. (
2011) set out a PSS ontology. This seeks to represent the current servitisation efforts that ae happening in industry as orgainsations try to sell a combination of products and services to boost profitability and grow. The PPS ontology focuses upon top levels concepts. A number of these are of interest to the FLEXINET reference ontology, concepts such as supply network and infrastructure. Once again concepts relating to risk and GPN are not represented. The concepts of economic, environment and social are modelled, but the relate directly to the out of a PSS and have nothing to do with GPN.
The Interoperable Manufacturing Knowledge System (IMKS) project (Chungoora and Young
2011a,
b; Chungoora et al.
2012,
2013) set out to formally model and define through-life engineering knowledge for manufacturing knowledge sharing across different domains. The project firstly developed lightweight UML models and then a heavyweight ontology that consisted of a design domain, a manufacturing domain and a set of core concepts which these two domain models related to. These were developed utilising the Common logic based Knowledge Frame Language (KFL) (Huber
2014). Mappings were built between the design and manufacturing ontology entities thus enabling cross domain knowledge sharing and hence support interoperability. One of the main outcomes of this was a set of generic manufacturing core concepts or reference ontology called the ‘Manufacturing Core Concepts Ontology’. In addition to this, two further approaches have taken the IMKS approach and built upon it. The first is that of Imran (
2013) who focused upon the domain of assembly. This was been done by applying Common Logic-based ontologies and subsequently developing a set of key specialised reference concepts for the assembly domain utilising the IMKS work and the generic concepts within it. The aim of this was to support interoperability and thus enable the creation of specific application ontologies. The second approach is that of Hastilow (
2013), who, again applied Common Logic-based ontologies for the domain of manufacturing information systems interoperability. The work from the IMKS approach was expanded to included product lifecycles and was specifically focused upon interoperation between defined systems. The Hastilow ontological work is currently being applied within the FLEXINET reference ontology.
A sustainable manufacturing ontology is presented by Borsato (
2014). This focuses upon green manufacturing and the concepts that relate to Product Lifecycle Management (PLM), drawn from multiple standards, existing research work and various other sources. Concepts relating to environmental impact, environmental policy and environmental performance exist which ultimately relate to the concept of product. Hence environmental aspects are considered, but in the wrong context, i.e. not that of a GPN context, moreover risk is not represented.
The ontological approaches detailed in Table
2 have focused upon ameliorating the interchange of information and knowledge between multiple contexts and describe the organisation of relationships between concepts for products, manufacturing, assembly and design activities, PLM and sustainability. What is conclusive is that risk is only represent within one of the ontologies, the Manufacturing Intelligence Systems ontology (Hastilow
2013). Additionally, whilst some environmental and social concepts are represented, they do not relate to a GPN context. Nonetheless, the concepts needed to represent the factors that influence a GPN do not exist in enough quantity, or the correct context.
Overview of the literature review
Three main points can be deduced from the literature articles presented herein: (i) most of the ontologies do not address the aspects relative to GPN, i.e., aspects relating to political, social, technological, economic and environmental factors, (ii) the ontologies in sections “Collaboration, enterprise and supply chain management ontologies” and “Manufacturing reference ontologies” (except for Hastilow
2013) do not consider risk within the ontologies, and (iii) the majority of the ontologies have developed their ontologies utilising OWL due to its popularity and accessibility.
Against point (i) and point (ii) it is fundamentally important that all concepts of relevance to the problem domains are included in an ontology if the ontology is to be of real value. It is due to the complexity of meeting this challenge that FLEXINET is committed to pursuing a reference ontology for manufacture and that this paper contributes to this especially in relationship to risk concepts and risk analysis.
Against point (iii) it is clear that while useful progress is being made in the definition of formal ontologies using OWL that solutions based on this are limited to the expressiveness of Description Logic (Scheuermann and Leukel
2014). We take the view, given the complexity of the manufacturing area, that modelling methods that support higher levels of expressiveness should be consideration. To that end we follow the view expressed by Chungoora and Young (
2011b), that Common Logic (ISO/IEC 24707
2007) based approaches, that are more aligned with full first order logic, should be exploited.
Overall, it can be seen from the literature assessed, that there are active ontological approaches being developed to address either interoperability or risk for a number of domains. But, there are few approaches focusing on the development of a reference ontology to enable interoperability for multi-contextual GPN that consider risk and support risk analysis.