China
Africa
Explore chapters and articles related to this topic
Defining System Architecture
Published in John P.T. Mo, Ronald C. Beckett, Engineering and Operations of System of Systems, 2018
Although PERA was developed for the steel and paper industries, Figure 2.4 shows that it is quite generic, in that there is little reference to the specific industries in which it was researched. Effectively, PERA is a time-based enterprise architecture representing the evolution of activities, resources, structures, and information in the life of the enterprise. The layering of tasks occurring within those regions is represented graphically as a top-down approach. Hence, the resulting architecture could apply to any enterprise regardless of the industry involved, and its applicability was far beyond what was originally intended.
Application of Reference Architectures for Enterprise Integration
Published in Cornelius Leondes, Computer-Aided Design, Engineering, and Manufacturing, 2019
The Purdue Enterprise Reference Architecture (PERA) and its accompanying Purdue Methodology were developed at Purdue University, (Nest Lafayette, IN). This university has also taken a leading role in the definition of reference models for computer integrated manufacturing.
Internet of things (IoT) and big data analytics (BDA) for digital manufacturing (DM)
Published in International Journal of Production Research, 2023
Zhuming Bi, Yan Jin, Paul Maropoulos, Wen-Jun Zhang, Lihui Wang
Popular EAs for manufacturing enterprises include Open System Architecture for Computer Integrated Manfuacturing (CIMOSA), Purdue Enterprise Reference Architecture (PERA), GRAI Integrated Methodology (GRAI-GIM), and National Institute of Standards and Technology (NIST) Enterprise Architecture (NIST-EA) (Williams 1994). Without losing generality, we used NIST-EA as an example to discuss the limitations of existing EAs.
Big data analytics capabilities: a novel integrated fitness framework based on a tool-based content analysis
Published in Enterprise Information Systems, 2023
Sunil Pathak, Venkataraghavan Krishnaswamy, Mayank Sharma
The definition of EA has evolved over several years. The eGovernment Act of 2002 (Public Law [PL] 107–347) states that EA means the following: (A) (i) a strategic information asset base, which defines the mission; (ii) the information necessary to perform the mission; (iii) the technologies necessary to perform the mission; and (iv) the transitional processes for implementing new technologies in response to changing needs; and (B) includes (i) a baseline architecture; (ii) a target architecture; and (iii) a sequencing plan (Hagan 2004). One can discern that EA constitutes a high-level model of the entire organisation (Lankhorst 2013; Ross, Weill, and Robertson 2006) and encompasses strategy, business processes, organisational structure, IS, applications and technology. EA can detect anomalies, and improvement opportunities for the organisation, thus supporting its transformation. In practice, EA is often organised using EA frameworks (EAFs) (Schekkerman 2004), and there are more than 90 EAFs that exist today in various domains (Kaisler and Armour 2017). EAF roots can be traced back to its development by two distinct communities: (a) Industrial Engineering – manufacturing, industrial engineering, and supply chain and (b) IS community concentrating on the development of software systems. The prominent examples in the industrial engineering domain include Purdue Enterprise Reference Architecture (Williams 1993), computer-integrated manufacturing open system architecture (European Commission 2008), and the GRAI-GIM method (Graphs with Results and Actions Inter-related – GRAI Integrated Methodology (GIM) (Chen and Doumeingts 1996). The focus of EAFs has been on addressing the complex design and implementation process of manufacturing, service, and supply-chain-related issues. On the IS front, following the pioneering work on the Zachman Framework (Zachman 1987), some notable EAFs include TOGAF (The Open Group 2018), the federal enterprise architecture (FEFA) framework, the department of defence architecture framework (DoDAF) (DoDAF 2010) and the treasury enterprise architecture framework (TEAF). Among the frameworks in the IS context, Zachman (1987) has been the most prominent framework and most referenced up until the year 2004. Another widely used framework is the ‘The Open Group Architecture Framework’ (TOGAF) developed by the Open Group – a technology-neutral international consortium (The Open Group 2018). TOGAF has become the most prominent EA framework in practice today (Buckl et al. 2009), and given its technology neutrality, it is used in the context of this paper. Moreover, TOGAF’s vision of boundaryless information flow (The Open Group 2018) suggests combining multiple sources of information to deliver the ubiquitous availability of information for business process improvements makes it a framework of choice for this study.