Purdue Enterprise Reference Architecture Research Articles

Risk-based safety scoping of adversary-centric security testing on Operational Technology

Due to the recent increase in cyber attacks targeting Critical National Infrastructure, governments and organisations alike have invested considerably into improving the security of their underlying infrastructure, commonly known as Operational Technology (OT). The use of adversary-centric security tests such as vulnerability assessments, penetration tests and red team engagements has gained significant traction due to these engagements’ goal to emulate threat actors in preparation for genuine cyber attacks. Challenges arise, however, when performing security tests on these as the nature of OT requires additional safety and operation risks to be considered. This paper proposes a framework for incorporating the assessment of safety and operational risks within an overall scoping methodology for adversary-centric security testing in OT environments. Within this framework, we also propose a hybrid testing model derived from the Purdue Enterprise Reference Architecture and the Defense in Depth model to identify and quantify safety and operational risk at a per-layer level, separating high and low-risk layers and being subsequently used for defining the rules of engagement. As a result, this framework can aid vendors and clients in appropriately scoping adversary-centric security tests so that depth-of-testing is maximised while minimising the risk to safety and to the operational process. The framework is then evaluated through a qualitative study involving industry experts, confirming the framework’s validity for implementation in practice.

Production System Modelling Methodologies of an Open Pit Mine

Open pit mines experience several challenges and constraints in the management of mining operations and processes. The heterogeneity of the infrastructures and the complexity of the physical and managerial systems highlight these various challenges. The creation of a generic system that can drive but at the same time models in a dynamic logic all these constraints and elements assume a major complexity. In addition, the modelling allows the implementation of real-time decision-making components and increases the responsiveness of the system. This paper presents six modelling methodologies of the production system, namely Open System Architecture for Computer Integrated Manufacturing, GRAI Integrated Methodology, Purdue Enterprise Reference Architecture, Generalized Enterprise Reference Architecture and Methodology, Zachman and Model Based System Engineering. Based on the multi-criteria analysis, we have shown that the Modelling Based System Engineering is the most adapted methodology in the case of open pit mines but this method knows a lack of agility in the system. Our system will use a methodology based on Model Based System Engineering and will consider the agility of the system.

Situation awareness framework for industrial control system based on cyber kill chain

Information and cyber security of Industrial Control Systems (ICS) has gained considerable importance. Situation Awareness (SA) is an exciting mechanism to achieve the perception, comprehension and projection of the ICS information security status. Based on the Purdue Enterprise Reference Architecture (PERA), a situation awareness framework for ICS is presented considering the ICS cyber kill chain. The proposed framework consists of IT SA Centre, OT SA Centre, and Comprehensive SA Centre. Comprehensive SA Centre is responsible for creating and maintaining an integrated and high level of security visibility into the whole environments. The introduced framework can be used to guide the development of the situation awareness infrastructure in organization with industrial control systems.

Life Cycle Engineering 4.0: A Proposal to Conceive Manufacturing Systems for Industry 4.0 Centred on the Human Factor (DfHFinI4.0)

Engineering 4.0 environments are characterised by the digitisation, virtualisation, and connectivity of products, processes, and facilities composed of reconfigurable and adaptive socio-technical cyber-physical manufacturing systems (SCMS), in which Operator 4.0 works in real time in VUCA (volatile, uncertain, complex and ambiguous) contexts and markets. This situation gives rise to the interest in developing a framework for the conception of SCMS that allows the integration of the human factor, management, training, and development of the competencies of Operator 4.0 as fundamental aspects of the aforementioned system. The present paper is focused on answering how to conceive the adaptive manufacturing systems of Industry 4.0 through the operation, growth, and development of human talent in VUCA contexts. With this objective, exploratory research is carried, out whose contribution is specified in a framework called Design for the Human Factor in Industry 4.0 (DfHFinI4.0). From among the conceptual frameworks employed therein, the connectivist paradigm, Ashby’s law of requisite variety and Vigotsky’s activity theory are taken into consideration, in order to enable the affective-cognitive and timeless integration of the human factor within the SCMS. DfHFinI4.0 can be integrated into the life cycle engineering of the enterprise reference architectures, thereby obtaining manufacturing systems for Industry 4.0 focused on the human factor. The suggested framework is illustrated as a case study for the Purdue Enterprise Reference Architecture (PERA) methodology, which transforms it into PERA 4.0.

Modelling a Global EPCM (Engineering, Procurement and Construction Management) Enterprise

This paper investigates the applicability of enterprise architectures in the context of current business environment by examining the application of Purdue Enterprise Reference Architecture to WorleyParsons, a global engineering, procurement and construction management enterprise, under the backdrop of a similar study carried out on Fluor Daniel during mid-nineties of the last century. The outcome of this study recommends the need for new enterprise architecture, the People-Centric Enterprise Architecture that not only focuses on human dimension in modern enterprises as the central thread, but also includes more business characteristics of the enterprise other than engineerings.

Interface design for the Purdue enterprise reference architecture (PERA) and methodology in e-Work

One of the primary concerns of enterprise integration is the establishment of the necessary interconnections or interfaces between the components and/or subsystems of the enterprise system. Such integration is considered a fundamental requirement for effective e-Work environment. As a Type 2 Enterprise Reference Architecture, PERA presents under its framework two major types of interfaces, the Internal System Interfaces and the Programme Interfaces. The former interface type provides the necessary interconnections between the components of the enterprise implementation or operational systems. The latter provides the necessary interconnections between the different phases of an enterprise development programme. The concepts of interfaces as illustrated in PERA indicate that the design of the system interfaces should be included in the design of the overall methodology together with the design of implementation architectures. A phased development programme for any enterprise integration project needs such well-designed communication interfaces between the project phases to assure that the desired information exchange occurs between the parties involved.

The interconnected chain of enterprises as presented by the Purdue Enterprise Reference Architecture

Enterprise integration programs need throughout their life cycles the many products and/or services that can be provided by other enterprises. At its operational stage, every enterprise can become such a provider of products or services to answer others' needs. This paper will show that such a product/service, provider–receiver relationship can be illustrated by using Purdue Enterprise Reference Architecture (PERA)'s own unique diagram as the basic unit to form an interconnected chain of the enterprises involved. According to the roles on this chain played by the different enterprises or enterprise programs, only four basic types of enterprises need to be defined to describe this chain. The PERA diagram can be used recursively to describe each of these basic types and the relations between them. Therefore, PERA is able to present a complete description of this evolving chain of enterprises regardless of the origin or field of application of the systems involved.

Enterprise Integration—Business Processes Integrated Management: a proposal for a methodology to develop Enterprise Integration Programs

An approach to develop Enterprise Integration Programs to assist enterprises in their migration path towards integration is proposed. It is called IE—GIP (Enterprise Integration—Business Processes Integrated Management, acronyms in Spanish). The topic is very important in industrial engineering nowadays because of the growing need to improve existing industrial systems and to organise such complex systems faster, better, and in a more systematic way. The contribution to the field of Enterprise Integration is mostly a methodological one. More specifically, it is based on the integration of Purdue Enterprise Reference Architecture (PERA) and Open System Architecture for Computer Integrated Manufacturing (CIMOSA) principles to propose an integration approach for industrial enterprises. Starting from existing leading proposals (CIMOSA, PERA, GERAM), a methodology has been defined and some extension to an architecture and supporting computer tools are discussed. The proposal covers the life cycle of an Enterprise Integration Program in a top-down approach. The approach is centred on the business process concept, but is based on a vision/process/people/technology view of the enterprise. The methodology divides the work into two major phases before system construction: master planning and CIM programme development. The method adapts the system life cycle of PERA but uses, whenever possible, the CIMOSA architecture with its business process approach. New CIMOSA-like constructs are introduced to be used in activities along with the methodology when necessary. To support the modelling phases of the proposal and to provide guidance to users of the methodology, computer supported tools have been developed in the course of this work.

Establishment of the place of the human in enterprise integration

The Purdue Enterprise Reference Architecture (PERA) has developed a unique methodology for determining the place of the Human in any particular enterprise. This methodology will be described in this paper. This same capability also applies to GERAM through its inheritance from PERA in the development process of GFRAM.

Some extensions to the Purdue Enterprise Reference Architecture (PERA): I. Explaining the Purdue architecture and the Purdue methodology using the axioms of engineering design

The initial development of the Purdue Enterprise Reference Architecture (PERA) and the Purdue Methodology (PM) was necessitated by the desires of the industry for guidance in the field of enterprise integration and the necessary application of modern information technology in that field. As such, the original version was written based on intuitive and engineering logic. This article verifies whether PERA and PM are good engineering design solutions on the basis of Suh's design axioms and a related set of Functional Requirements (FRs) and Design Parameters (DPs). This paper thus shows in this way that the structure of PERA, though developed intuitively, is inherently consistent and logical. In Suh's term, it is a good engineering design. The executability and simplicity of PERA are, therefore, further strengthened.

Manufacturing Enterprise Modeling with PERA and CIMOSA

Both CIMOSA and PERA are architectures developed for integrated manufacturing systems analysis, design and implementation. CIMOSA is an open systems architecture for Enterprise Integration which includes a powerful language for enterprise modeling and is aimed at model-based integration. The Purdue Enterprise Reference Architecture (PERA) is based on a detailed and pragmatic methodology covering the whole life cycle of an industrial project from inception to operation and even system disposal. This paper presents how the PERA methodology can be applied using the CIMOSA constructs to engineer a production planning and control system. PERA provides a clear indication of the role and place of humans in the architecture to be defined or specified while CIMOSA provides a consistent set of constructs to capture system details at all modeling levels.

Textile Enterprise Modeling

Textile companies are striving for an advantage using many different competitive strategies and are often employing more than one strategy at a time. To maximize the potential of incorporating new technologies that include process equipment and information systems, an increased level of understanding of the integrated enterprise is required. This paper reviews the current research efforts relating to enterprise modeling in the textile industry. Discussed are two generic enterprise reference architectures: the Purdue Enterprise Reference Architecture and the Open Systems Architecture for CIM (CIMOSA). Areas for research in enterprise modeling in textiles are presented.

Requirements of the generic enterprise reference architecture and methodology

The Generic Enterprise Reference Architecture and Methodology (GERAM) defines those methods, models and tools which are needed to identify and carry out change in enterprises. Enterprises need a life-cycle architecture that describes the progression of an enterprise from the point of realisation that change is necessary through setting up a project (or enterprise integration programme) and to implementing the change based on a thorough analysis and design. GERAM is a framework in which all necessary ingredients of this process are identified. GERAM allows one to characterise and compare all particular change methodologies and architectures, or helps in deciding how to combine ingredients of individual architectures and methods. GERAM is the result of generalisation, based on the three most complete enterprise reference architectures: CIM-OSA (Vernadat, 1992), the GRAI Integrated Methodology, GIM (Vallespir et al 1991), and the Purdue Enterprise Reference Architecture, PERA (Williams, 1992), but GERAM extends the scope of enterprise architecture to the life-cycle of Products, Enterprises, Enterprise Integration Projects, and Strategic Enterprise Management. It is also proposed which details of GERAM could be standardised.

The task force specification for GERAM and its fulfillment by PERA

The IFAC/IFIP Task Force on Architectures for Enterprise Integration has established a specification and set of requirements for a Generalized Enterprise Reference Architecture and Methodology (GERAM) as a class of complete enterprise architecture systems. These can be used to judge whether a specific enterprise reference architecture and methodology fulfills such requirements and can itself be classified as a GERAM. This paper describes the development of these requirements by the Task Force and shows how the Purdue Enterprise Reference Architecture and Methodology (PERA) fulfills them and can be labeled as a GERAM.

A framework to define a generic enterprise reference architecture and methodology

The generic enterprise reference architecture and methodology is about those methods, models and tools which are needed to build the integrated enterprise. The architecture is generic because it applies to most, potentially all types of enterprise. The coverage of the framework spans products, enterprises, enterprise integration and strategic enterprise management. The proposal for the architecture follows the architecture itself improving the quality of the presentation and of the outcome. Definitions of generic enterprise reference architecture, enterprise engineering/integration methodology, enterprise modelling languages, enterprise models, and enterprise modules are given. It is proposed how the above could be developed on the basis of previously analysed architectures (and other results too), such as the purdue enterprise reference architecture (PERA) 1, the GRAI integrated methodology 2, CIM-OSA 3, and TOVE 4. GERAM is meant to unify existing architectures rather than intending to replace them. This is achieved by ensuring that the scope of GERAM spans all areas of consideration in an enterprise.

Requirements of the Generic Enterprise Reference Architecture and Methodology

The Generic Enterprise Reference Architecture and Methodology (GERAM) defines those methods, models and tools which are needed to identify and carry out change in enterprises. Enterprises need a life-cycle architecture that describes the progression of an enterprise from the point of realisation that change is necessary through setting up a project (or enterprise integration programme) and to implementing the change based on a thorough analysis and design. GERAM is a framework in which all necessary ingredients of this process are identified. GERAM allows one to characterise and compare all particular change methodologies and architectures, or helps in deciding how to combine ingredients of individual architectures and methods. GERAM is the result of generalisation, based on the three most complete enterprise reference architectures: CIM-OSA (Vernadat, 1992), the GRAI Integrated Methodology, GIM (Vallespir et al 1991), and the Purdue Enterprise Reference Architecture, PERA (Williams, 1992), but GERAM extends the scope of enterprise architecture to the life-cycle of Products, Enterprises, Enterprise Integration Projects, and Strategic Enterprise Management. It is also proposed which details of GERAM could be standardised.

The Task Force Specification for GERAM and its Fulfillment by PERA

The IFAC/IFIP Task Force on Architectures for Enterprise Integration has established a specification and set of requirements for a Generalized Enterprise Reference Architecture and Methodology (GERAM) as a class of complete enterprise architecture systems. These can be used to judge whether a specific enterprise reference architecture and methodology fulfills such requirements and can itself be classified as a GERAM. This paper describes the development of these requirements by the Task Force and shows how the Purdue Enterprise Reference Architecture and Methodology (PERA) fulfills them and can be labeled as a GERAM.

The Purdue enterprise reference architecture

This paper presents the basic concepts which comprise the Purdue Enterprise Reference Architecture along with a description of its development and use. This architecture provides the capability for modelling the human component as well as the manufacturing or customer service component of anyenterprise in addition to the information and control system component. This latter component is the major focus of most reference architectures and models available today for computer integrated manufacturing or complete enterprise study. This paper particularly points out those areas where this architecture differs from others available. In doing this it describes a new and unique method for defining the place of the human in the computer integrated plant or enterprise. It also develops the concept of customer service, which allowed the architecture, which was originally developed for computer integrated manufacturing, to be extended to define the development and operation of any enterprise regardless of the industry or field of endeavor involved.

The Purdue Enterprise Reference Architecture

This paper presents the basic concepts which comprise the Purdue Enterprise Reference Architecture along with a description of its development and use. This architecture provides the capability for modelling the human component as well as the manufacturing or customer service component of any enterprise in addition to the information and control system component. this latter component is the major focus of most reference architectures and models available today for computer integrated manufacturing or complete enterprise study.The paper describes a new and unique method for defining the place of the human in the computer integrated plant or enterprise. It also develops the concept of customer service which allow the architecture, which was originally developed for computer integrated manufacturing, to be extended to define the development and operation of any enterprise regardless of the industry or field of endeavor involved.A review of important future work needed in this field is also presented.