The Purdue enterprise reference architecture

Williams, Theodore J.

doi:10.1016/0166-3615(94)90017-5

Cited by 372 publications

(141 citation statements)

References 5 publications

Supporting

Mentioning

135

Contrasting

Unclassified

Order By: Relevance

“…From the enterprise modelling point of view, any visionary manufacturing system development should be implemented with a coherent set of three architectures: physical, information, human/organization [5]. In a similar argument, Didic et al [6] outlined an open engineering architecture with functional, information, resources and organizational views.…”

Section: Introductionmentioning

confidence: 98%

The role of lean in the application of information technology to manufacturing

2009

Computers in Industry

View full text Add to dashboard Cite

Section: Introductionmentioning

confidence: 98%

The role of lean in the application of information technology to manufacturing

2009

Computers in Industry

View full text Add to dashboard Cite

“…Enterprise architecture is model based, in the sense that diagrammatic descriptions of the systems and their environment constitute the core of the approach. A number of enterprise architecture initiatives have been proposed, including The Open Group Architecture Framework (TOGAF) (The Open Group 2005), the Zachman Framework (Zachman 1987), GERAM (IFAC-IFIP 1999), CIMOSA (Kosanke 1995), PERA (Williams 1994), DoDAF (Department of Defense 2004), Intelligrid (Hughes 2004) and more.…”

Section: Introductionmentioning

confidence: 99%

Enterprise architecture analysis with extended influence diagrams

et al. 2007

View full text Add to dashboard Cite

The discipline of enterprise architecture advocates the use of models to support decision-making on enterprise-wide information system issues. In order to provide such support, enterprise architecture models should be amenable to analyses of various properties, as e.g. the level of enterprise information security. This paper proposes the use of a formal language to support such analysis. Such a language needs to be able to represent causal relations between, and definitions of, various concepts as well as uncertainty with respect to both concepts and relations. To support decision making properly, the language must also allow the representation of goals and decision alternatives. This paper evaluates a number of languages with respect to these requirements, and selects influence diagrams for further consideration. The influence diagrams are then extended to fully satisfy the requirements. The syntax and semantics of the extended influence diagrams are detailed in the paper, and their use is demonstrated in an example.

show abstract

“…Among them the most known are: the Computer Integrated Manufacturing Open System Architecture (CIMOSA) [20] that coined the term enterprise architecture, the Purdue EnterpriseReference Architecture (PERA) [21], the GIM architecture [22] and ARIS [23]. These Type 2 architectures are mainly elaborated along the system life cycle to show what has to be done to model, design and implement an integrated enterprise system.…”

Section: Early Initiatives On Enterprise Architecturesmentioning

confidence: 99%

“…GERAM identifies, in its most important component called GERA (Generalized Enterprise Reference Architecture), the basic concepts to be used in enterprise engineering and integration. GERAM has been developed with the significant contributions from CIMOSA [20], the GRAI Integrated Methodology (GRAI/GIM) [22] and the Purdue Enterprise-Reference Architecture (PERA) [21]. Today GERAM has been moved to the standardization process (CEN and ISO).…”

Section: Ifac-ifip Task Force On Enterprise Integrationmentioning

confidence: 99%