EIN 6133EIN 6133Enterprise EngineeringEnterprise Engineering

Chin-Sheng ChenChin-Sheng ChenFlorida International UniversityFlorida International University

T8: Enterprise Systems T8: Enterprise Systems Modeling and ModelsModeling and Models Systems modeling toolsSystems modeling tools Enterprise modelsEnterprise models

ReferenceReference

Object-oriented Modeling and Object-oriented Modeling and DesignDesign, by James Rumbaugh, et , by James Rumbaugh, et al., Prentice Hall, 1991, ISBN-0-al., Prentice Hall, 1991, ISBN-0-13-629841-9 13-629841-9

Chapters 2 and 3, Handbook of Chapters 2 and 3, Handbook of Enterprise ArchitectureEnterprise Architecture

The ESE Framework –The ESE Framework –Re-visitRe-visitEnterprise Enterprise elementelement

WorkWork DecisionDecision ResourcResourcee

InformationInformation

System System facetfacet

StrategyStrategy CompetenCompetency cy (capability(capability))

Capacity Capacity StructureStructure

EngineerinEngineering activityg activity

SpecificatioSpecificationn

AnalysisAnalysis DesignDesign implementatiimplementationon

PerformanPerformance ce measuremeasure

QualityQuality TimeTime CostCost Benefit Benefit (profit)(profit)

Traditional modeling Traditional modeling toolstools Physical simulatorsPhysical simulators

– Use of physical (or in combination with Use of physical (or in combination with virtual) devicesvirtual) devices

Math modeling toolsMath modeling tools– Math programming (system specifications)Math programming (system specifications)– Queuing networks (system performance)Queuing networks (system performance)

(Computer graphic) charting tools(Computer graphic) charting tools– ABC flow-charterABC flow-charter– VisioVisio

Computer-based Computer-based simulation modeling simulation modeling toolstools Computer languagesComputer languages

– Java, VB, C#Java, VB, C# Macro programsMacro programs

– GASP, GPSSGASP, GPSS– Simen, ARINA, SLAMSimen, ARINA, SLAM– AutoMod, QuestAutoMod, Quest

NetworkNetwork– Petri Net, Petri Net, – Neural networksNeural networks

Information systems Information systems modeling toolsmodeling tools IDEFIDEF

– IDEF0 (activities)IDEF0 (activities)– IDEF1x (information)IDEF1x (information)– IDEF2x (dynamics)IDEF2x (dynamics)

OMTOMT– Functional modelFunctional model– Object modelObject model– Dynamic modelDynamic model

OMT Concepts (1)OMT Concepts (1)

There are 4 system development stages: There are 4 system development stages: analysis, system design, implementation analysis, system design, implementation design, and implementation.design, and implementation.

OMT is to capture the concepts of a system, OMT is to capture the concepts of a system, rather than its implementationrather than its implementation

The three models are orthogonal parts of the The three models are orthogonal parts of the description of a complete system and are description of a complete system and are cross-linked. The object model is most cross-linked. The object model is most fundamental, because it describes fundamental, because it describes whatwhat changes (or transforms) before changes (or transforms) before whenwhen (dynamic model) or (dynamic model) or howhow (functional model) it (functional model) it changes.changes.

OMT concepts (2) OMT concepts (2) - common themes - common themes Abstraction, Abstraction, Encapsulation, Encapsulation, Combining data and behavior, Combining data and behavior, Sharing with emphasis on object Sharing with emphasis on object

structure (not procedure structure), structure (not procedure structure), and and

Synergy (consistence in terms of ID, Synergy (consistence in terms of ID, classification, polymorphism, and classification, polymorphism, and inheritance)inheritance)

OMT concepts (3) OMT concepts (3) - Functional model- Functional model It describes the data value It describes the data value

transformations within a system. transformations within a system. The functional model contains The functional model contains

data flow diagrams. data flow diagrams. – A data flow diagram is a graph A data flow diagram is a graph

whose nodes are processes and whose nodes are processes and whose arcs are data flows.whose arcs are data flows.

OMT concepts (4) OMT concepts (4) - object model- object model It describes the static structure of It describes the static structure of

the objects in a system and their the objects in a system and their relationships.relationships.

The object model contains object The object model contains object diagrams. diagrams. – An object diagram is a graph whose An object diagram is a graph whose

nodes are object classes and whose nodes are object classes and whose arcs are relationships among classes.arcs are relationships among classes.

OMT concepts (5) OMT concepts (5) - Dynamic model- Dynamic model It describes the aspects of a system It describes the aspects of a system

that change over time and is used to that change over time and is used to specify and implement the control specify and implement the control aspects of a system. aspects of a system.

The dynamic model contains state The dynamic model contains state diagrams. diagrams. – A state diagram is a graph whose nodes A state diagram is a graph whose nodes

are states and whose arcs are are states and whose arcs are transitions between states caused by transitions between states caused by events.events.

Relationship among Relationship among the three modelsthe three models IDEF0/functional modelIDEF0/functional model

– The input to an activity is usually a user interface for data entryThe input to an activity is usually a user interface for data entry– The output to an activity is usually a user interface for a report, though The output to an activity is usually a user interface for a report, though

the output may be a write/update to a database.the output may be a write/update to a database.– ICOMICOM

Material is an input object. Material is an input object. Product/process data are output objects. Product/process data are output objects. Rules/regulations and SOPs are constraints. Rules/regulations and SOPs are constraints. Resources/tools and methods are mechanisms.Resources/tools and methods are mechanisms.

IDEF1/object modelIDEF1/object model– The collection of the ICOM of an IDEF activity model constitutes an The collection of the ICOM of an IDEF activity model constitutes an

inclusive foundation for the object model. inclusive foundation for the object model. IDEF2/dynamics modelIDEF2/dynamics model

– Each object requires a state diagram to define/govern its life-cycle Each object requires a state diagram to define/govern its life-cycle behavior. behavior.

– A triggering event is associated with each transition from one state to A triggering event is associated with each transition from one state to another. One state may transform to multiple states, depending on the another. One state may transform to multiple states, depending on the triggering event. triggering event.

Related enterprise Related enterprise architecturesarchitectures (1) (1) Purdue Enterprise Reference Architecture (PERA), Purdue Enterprise Reference Architecture (PERA),

– by Williams, at Purdue University in 1988.by Williams, at Purdue University in 1988. GRAI Integrated Methodology (GIM) GRAI Integrated Methodology (GIM)

– – – a flattened version of IMPACS (integrated manufacturing a flattened version of IMPACS (integrated manufacturing planning and control system), by the GRAI Lab at the University planning and control system), by the GRAI Lab at the University of Bordeaux in France, 1984of Bordeaux in France, 1984

Computer Integrated Manufacturing Open System Computer Integrated Manufacturing Open System Architecture (CIMOSA) Architecture (CIMOSA) – by the AMICE Consortium under ESPRIT, 1988 by the AMICE Consortium under ESPRIT, 1988

Zackman’s framework for information systems architecture, Zackman’s framework for information systems architecture, – by Zackman at IBM in 1987by Zackman at IBM in 1987

CC44ISR (Command, Control, Communications, Computers, ISR (Command, Control, Communications, Computers, Intelligence, Surveillance, and Reconnaissance), Intelligence, Surveillance, and Reconnaissance), – by Architecture Working Group (DOD) in 1997.by Architecture Working Group (DOD) in 1997.

ARIS (Architecture for Information Systems), ARIS (Architecture for Information Systems), – by Scheer in 1999by Scheer in 1999

Related enterprise Related enterprise architectures (2)architectures (2) Generic Enterprise Reference Generic Enterprise Reference

Architecture and Methodology (GERAM) Architecture and Methodology (GERAM) – by an IFIP-IFAC joint task force on by an IFIP-IFAC joint task force on

architecture for enterprise integration, 1992-architecture for enterprise integration, 1992-2002, consisting of:2002, consisting of: GERA (generic enterprise reference architecture)GERA (generic enterprise reference architecture) GEEM (generic enterprise engineering GEEM (generic enterprise engineering

methodology)methodology) GEMT&L (generic enterprise modeling tools and GEMT&L (generic enterprise modeling tools and

languages)languages)

GERAM (1)GERAM (1)- Background- Background Enterprise Integration (EI) historyEnterprise Integration (EI) history

– EI has evolved since 19EI has evolved since 19thth century, from the need of integrating information and century, from the need of integrating information and material flow throughout an enterprise.material flow throughout an enterprise.

Automation historyAutomation history– Since 1960’s, it was worked in two separate areas of manufacturing (design and Since 1960’s, it was worked in two separate areas of manufacturing (design and

production) and business support. production) and business support. – In the 80’s, efforts were started to integrate information and material flows with In the 80’s, efforts were started to integrate information and material flows with

human elements recognized as an integral part of enterprise operationhuman elements recognized as an integral part of enterprise operation Two approaches emerged to respond to this challenge.Two approaches emerged to respond to this challenge.

– Business approachBusiness approach Based on generic models or designs (architectures) that could subsequently Based on generic models or designs (architectures) that could subsequently

be implemented as information systems products, incorporating most or all be implemented as information systems products, incorporating most or all information processing tasks in the enterprise (especially its management). information processing tasks in the enterprise (especially its management). The resulting systems were called ERP systems. At the same time, the effort The resulting systems were called ERP systems. At the same time, the effort in the CIM reference models failed to achieve an industry-wide acceptance.in the CIM reference models failed to achieve an industry-wide acceptance.

– Engineering approach – enterprise engineeringEngineering approach – enterprise engineering Based on life-cycle approach. To create an integrated enterprise, the creation Based on life-cycle approach. To create an integrated enterprise, the creation

activities (thus methodologies) must extend to the whole of the life of the activities (thus methodologies) must extend to the whole of the life of the enterprise form its inception till its de-commission. enterprise form its inception till its de-commission.

GERAM historyGERAM history– IFIF and IFAC established a joint force in 1992 to review existing approaches to EI. IFIF and IFAC established a joint force in 1992 to review existing approaches to EI. – It was led by Professors Williams and then Bernus and lasted for 10 yearsIt was led by Professors Williams and then Bernus and lasted for 10 years

GERAM (2)GERAM (2)- Introduction- Introduction GERA + MethodologyGERA + Methodology It defines a tool-kit of concepts for designing and maintaining It defines a tool-kit of concepts for designing and maintaining

enterprises for their life history.enterprises for their life history. It is meant to organize existing enterprise integration It is meant to organize existing enterprise integration

knowledge.knowledge. It facilitates the unification of methods of several disciplines It facilitates the unification of methods of several disciplines

used in the change (of life cycle) process, including IE, used in the change (of life cycle) process, including IE, management science, control engineering, communication and management science, control engineering, communication and information technology, to allow their combined use.information technology, to allow their combined use.

It unifies the two distinct approaches to EI: those based on It unifies the two distinct approaches to EI: those based on product models and on business process design.product models and on business process design.

It also offers new insights into the project management of EI It also offers new insights into the project management of EI and the relationship of integration with other enterprise and the relationship of integration with other enterprise strategic activities.strategic activities.

It recognizes continuous improvement process of the It recognizes continuous improvement process of the enterprise operation with feedback loops based on mission enterprise operation with feedback loops based on mission and performance indicators, to adapt to changes in the and performance indicators, to adapt to changes in the market, technology, and society.market, technology, and society.

GERAM (3)GERAM (3)- It considers Life cycle- It considers Life cycle Life cycleLife cycle

– The cycle from life (inception) to The cycle from life (inception) to death (de-commission).death (de-commission).

Life historyLife history– History (instantiation) of a lifeHistory (instantiation) of a life

GERAM (4)GERAM (4)- It considers feedback- It considers feedback FeedbackFeedback

– It recognizes and identifies feedback loops on It recognizes and identifies feedback loops on various levels of enterprise performance as they various levels of enterprise performance as they relate to products, mission, and meaning. relate to products, mission, and meaning.

– To achieve such feedback, performance indicators To achieve such feedback, performance indicators and evaluation criteria of the change impact on and evaluation criteria of the change impact on process and organization are required. process and organization are required.

– It is the prerequisite for the continuous It is the prerequisite for the continuous improvement process of the enterprise operation improvement process of the enterprise operation and its adaptation to the changes in the relevant and its adaptation to the changes in the relevant market, technology, and society.market, technology, and society.

GERAM views enterprise models as an GERAM views enterprise models as an essential component of EE/Iessential component of EE/I

GERAMGERAM- - Enterprise integration (EI) and enterprise engineering Enterprise integration (EI) and enterprise engineering

(EE)(EE) EI definition, by GERAMEI definition, by GERAM

– About breaking down organizational barriers and About breaking down organizational barriers and improving interoperability to create synergy within improving interoperability to create synergy within the enterprise to operate more efficiently and the enterprise to operate more efficiently and adaptively.adaptively.

EE Definition, by GERAMEE Definition, by GERAM– A discipline that organizes all knowledge that is A discipline that organizes all knowledge that is

needed to identify the need for change in enterprises needed to identify the need for change in enterprises and to carry out that change expediently and and to carry out that change expediently and professionally.professionally.

– A collection of tools and methods which one can use A collection of tools and methods which one can use to design and continually maintain an integrated to design and continually maintain an integrated state of an enterprise.state of an enterprise.

GERAM FrameworkGERAM Framework

GERA (generalized enterprise reference architecture) GERA (generalized enterprise reference architecture)

employsemploys -> EEM (enterprise engineering methodology) -> EEM (enterprise engineering methodology)

utilizes utilizes -> EML (enterprise modeling languages) -> EML (enterprise modeling languages)

implemented inimplemented in -> EET (enterprise engineering tools) -> EET (enterprise engineering tools)

along with support ofalong with support of

PEM (partial enterprise models)PEM (partial enterprise models)

GEMC (generic enterprise modeling GEMC (generic enterprise modeling concepts) concepts)

used to buildused to build -> EM (enterprise models) -> EM (enterprise models)

with EMO (enterprise modules) with EMO (enterprise modules)

used to implementused to implement -> EOS (enterprise operational systems) -> EOS (enterprise operational systems)

GERAM framework GERAM framework componentscomponents- GERA- GERA A set of enterprise related concepts for A set of enterprise related concepts for

use in EE/Iuse in EE/I– Human oriented conceptsHuman oriented concepts

To describe the role of humans an integral part To describe the role of humans an integral part of an enterprise org. and operationof an enterprise org. and operation

To support humans during enterprise design, To support humans during enterprise design, construction, and change.construction, and change.

– Process oriented conceptsProcess oriented concepts Describe the business process of the enterpriseDescribe the business process of the enterprise

– Technology oriented conceptsTechnology oriented concepts Describe the business-process-supporting Describe the business-process-supporting

technology in the EE or enterprise operation technology in the EE or enterprise operation efforts (i.e., modeling and model-use support)efforts (i.e., modeling and model-use support)

GERAM framework GERAM framework componentscomponents- - Enterprise engineering methodology Enterprise engineering methodology (EEM)(EEM) Describes the process of EE/IDescribes the process of EE/I

– May be expressed in the form of a process model or May be expressed in the form of a process model or structured procedure with detailed instructions for each EE/A structured procedure with detailed instructions for each EE/A activityactivity

An EEM emphasis:An EEM emphasis:

1.1. Human factorHuman factor Automat-ability, human-izability, and extent of automationAutomat-ability, human-izability, and extent of automation

2.2. Project managementProject management In three phases: start-up, control, and terminationIn three phases: start-up, control, and termination

3.3. Economic evaluation in three stepsEconomic evaluation in three steps Calculation of the cost of the solutionCalculation of the cost of the solution Comparison of the solution costs to the budget Comparison of the solution costs to the budget Performance measures of the solutionPerformance measures of the solution

GERAM framework GERAM framework componentscomponents- - Enterprise modeling languages Enterprise modeling languages (EMLs)(EMLs) Define the generic modeling Define the generic modeling

constructs for enterprise modeling constructs for enterprise modeling adapted to the needs of people adapted to the needs of people creating and using enterprise creating and using enterprise models.models.

Provide constructs to describe and Provide constructs to describe and model human roles, operational model human roles, operational processes and their functional processes and their functional contents.contents.

GERAM framework GERAM framework componentscomponents- - Generic enterprise modeling concepts (GEMCs)Generic enterprise modeling concepts (GEMCs)

Define and formalize the most generic concepts Define and formalize the most generic concepts of enterprise modeling. of enterprise modeling.

May be defined in various ways:May be defined in various ways:– Natural language Natural language

explaining the meaning of modeling concepts explaining the meaning of modeling concepts (glossaries)(glossaries)

– Some form of meta model (E/R meta schema)Some form of meta model (E/R meta schema) describing the relationship among modeling concepts describing the relationship among modeling concepts

available in enterprise modeling languages.available in enterprise modeling languages.– Ontological theories Ontological theories

defining the meaning (semantics) of enterprise defining the meaning (semantics) of enterprise modeling languagesmodeling languages

To improve the analytic capability of engineering tools, To improve the analytic capability of engineering tools, and through them the usefulness of enterprise models.and through them the usefulness of enterprise models.

These theories are usually built inside the engineering These theories are usually built inside the engineering toolstools

GERAM framework GERAM framework componentscomponents- - Partial enterprise models Partial enterprise models (PEMs)(PEMs) Are re-usable modelsAre re-usable models Capture characteristics common to many enterprise in Capture characteristics common to many enterprise in

one or more industriesone or more industries Common ones are Common ones are

– Partial human role models (skills and competencies in Partial human role models (skills and competencies in enterprise operation and management)enterprise operation and management)

– Partial (operational) process models (functionality and Partial (operational) process models (functionality and behaviorbehavior

– Partial technology models (e.g., process plan for Partial technology models (e.g., process plan for manufacturing)manufacturing)

Partial IT/infrastructure models (e.g., IT, energy, services, Partial IT/infrastructure models (e.g., IT, energy, services, etc.)etc.)

Also known as reference models, or type I reference Also known as reference models, or type I reference architectures architectures – Note: Life-cycle architectures such as GERA is referred to Note: Life-cycle architectures such as GERA is referred to

as type II reference architectureas type II reference architecture

GERAM framework GERAM framework componentscomponents- Generic enterprise modeling concepts - Generic enterprise modeling concepts (GEMC)(GEMC) Most generically used concepts and definition of Most generically used concepts and definition of

enterprise integration and modelingenterprise integration and modeling Three forms of concepts definition:Three forms of concepts definition:

– GlossariesGlossaries– Meta-modelsMeta-models– Ontological theoriesOntological theories

GuidelinesGuidelines– Concepts defined in more than one form of the Concepts defined in more than one form of the

above must be defined in a mutually consistent wayabove must be defined in a mutually consistent way– Those concepts that are used in an enterprise Those concepts that are used in an enterprise

modeling languages must also have at least a modeling languages must also have at least a definition in the metal model form, but preferably definition in the metal model form, but preferably the definition should appear in an ontological theory.the definition should appear in an ontological theory.

GERAM framework GERAM framework componentscomponents- - Enterprise engineering tools Enterprise engineering tools (EETs)(EETs) Support the processes of EE/I by Support the processes of EE/I by

– Implementing an EE methodologyImplementing an EE methodology– Supporting modeling languagesSupporting modeling languages

Should provide for analysis, Should provide for analysis, design and use of enterprise design and use of enterprise modelsmodels

GERAM framework GERAM framework componentscomponents- - (Particular) enterprise models (EMs) (1)(Particular) enterprise models (EMs) (1)

Represent a particular enterprise entityRepresent a particular enterprise entity Can be expressed using enterprise Can be expressed using enterprise

modeling languagesmodeling languages Include various designs, models for Include various designs, models for

analysis, and executable models to analysis, and executable models to support the enterprise operation support the enterprise operation

May include several models describing May include several models describing various aspects (or views) of the various aspects (or views) of the enterprise.enterprise.

GERAM framework GERAM framework componentscomponents- (Particular) enterprise models (EMs) (2)- (Particular) enterprise models (EMs) (2) Notes on EMsNotes on EMs

– The goal of enterprise modeling is to create and continuously The goal of enterprise modeling is to create and continuously maintain a model of a particular enterprise entity. maintain a model of a particular enterprise entity.

– An enterprise model should represent the reality of the An enterprise model should represent the reality of the enterprise operation according to the requirements of the user enterprise operation according to the requirements of the user and his applicationand his application

– It includes all description, design, and formal models of the It includes all description, design, and formal models of the enterprise that are prepared in the course of the enterprise’s life enterprise that are prepared in the course of the enterprise’s life historyhistory

Some uses of enterprise modelsSome uses of enterprise models– Decision support for evaluating operational alternatives in the Decision support for evaluating operational alternatives in the

EE process, enabling operation analysis and synthesisEE process, enabling operation analysis and synthesis– Communication tool that enables the mutual understanding of Communication tool that enables the mutual understanding of

issues.issues.– Model-driven operation control and monitoring for efficient Model-driven operation control and monitoring for efficient

business process executionbusiness process execution– Training of new personnel.Training of new personnel.

GERAM framework GERAM framework componentscomponents- - Enterprise modules (EMOs)Enterprise modules (EMOs)

Are implementation of partial Are implementation of partial modelsmodels

Are building blocks that are utilized Are building blocks that are utilized as common resources in EE/A.as common resources in EE/A.

Are reusable and could be available Are reusable and could be available in the market placein the market place

Common ones are resource Common ones are resource modules for humans, machines, modules for humans, machines, equipment, and IT infrastructureequipment, and IT infrastructure

GERAM framework GERAM framework componentscomponents- - (Particular) enterprise operational system (EOS)(Particular) enterprise operational system (EOS)

Supports the operation of a Supports the operation of a particular enterpriseparticular enterprise

Its implementation is guided by the Its implementation is guided by the particular enterprise model whichparticular enterprise model which– provides the system specifications provides the system specifications

andand– identifies the enterprise modules used identifies the enterprise modules used

in the implementation of the in the implementation of the particular enterprise system.particular enterprise system.

Three major enterprise Three major enterprise information reference information reference architecturesarchitectures

Generalized enterprise reference Generalized enterprise reference architecture (GERA)architecture (GERA)

Purdue enterprise reference Purdue enterprise reference architecture (PERA)architecture (PERA)

Enterprise architecture Enterprise architecture frameworkframework– By John ZackmanBy John Zackman

GERA GERA - - Three scoping/modeling dimensionsThree scoping/modeling dimensions

Life-cycle dimensionLife-cycle dimension– Provides for the controlled modeling Provides for the controlled modeling

process of enterprise entities according to process of enterprise entities according to its life cycleits life cycle

Generic-ity dimensionGeneric-ity dimension– Provides for the controlled Provides for the controlled

particularization (instantiation) process particularization (instantiation) process from generic and partial to particular.from generic and partial to particular.

View dimensionView dimension– Provides for the controlled visualization of Provides for the controlled visualization of

specific views of the enterprise entityspecific views of the enterprise entity

GERA GERA - - Enterprise life-cycle phases (1)Enterprise life-cycle phases (1)

IdentificationIdentification– A set of activities that identifies the contents of the A set of activities that identifies the contents of the

enterprise in terms of the nature of its existence, its enterprise in terms of the nature of its existence, its need and the need for changes. need and the need for changes.

ConceptConcept– A set of activities for developing the concepts of the A set of activities for developing the concepts of the

underlying enterprise, including the definition of its underlying enterprise, including the definition of its mission, vision, values, strategies, objectives, mission, vision, values, strategies, objectives, operational concepts, policies, and business plans.operational concepts, policies, and business plans.

RequirementsRequirements– A set of activities for developing descriptions of A set of activities for developing descriptions of

operational requirements of the enterprise, its relevant operational requirements of the enterprise, its relevant processes, and the collection of all their functional, processes, and the collection of all their functional, behaviroural, information and capacity needs for both behaviroural, information and capacity needs for both production and mgt, whether by humans or machinery. production and mgt, whether by humans or machinery.

GERA GERA - - Enterprise life-cycle phases (2)Enterprise life-cycle phases (2)

DesignDesign– A set of activities that support the specification of the enterprise with A set of activities that support the specification of the enterprise with

all of its components that satisfy the enterprise requirements. They all of its components that satisfy the enterprise requirements. They include the design of all human tasks, all machine tasks, and include the design of all human tasks, all machine tasks, and operational processes (including identification of necessary operational processes (including identification of necessary information and resources for mfg. information, communication, information and resources for mfg. information, communication, control and other processing technology)control and other processing technology)

– Sub-phases: preliminary (architectural) design and detailed designSub-phases: preliminary (architectural) design and detailed design ImplementationImplementation

– A set of activities that define all tasks that must be carried out to A set of activities that define all tasks that must be carried out to build or re-build (manifest) the enterprise. This comprises build or re-build (manifest) the enterprise. This comprises implementation in the broadest sense, coveringimplementation in the broadest sense, covering Commissioning, purchasing, re-configuring, or developing all Commissioning, purchasing, re-configuring, or developing all

software and hardware resources for services, mfg. and control.software and hardware resources for services, mfg. and control. Hiring and training personnel, and developing or changing the Hiring and training personnel, and developing or changing the

human organization.human organization. Component testing and validation, system integration, validation, Component testing and validation, system integration, validation,

and testing, and and testing, and releasing into operationreleasing into operation

GERA GERA - - Enterprise life-cycle phases (3)Enterprise life-cycle phases (3)

OperationOperation– The activities of the enterprise that are needed during its operation The activities of the enterprise that are needed during its operation

for producing the customers products and service which is its for producing the customers products and service which is its special mission , along with all those tasks needed for monitoring, special mission , along with all those tasks needed for monitoring, controlling, and evaluating the operation.controlling, and evaluating the operation.

– Thus the resources of the enterprise are managed and controlled so Thus the resources of the enterprise are managed and controlled so as to carry out the processes necessary for the entity to fulfill its as to carry out the processes necessary for the entity to fulfill its missionmission

– Deviations from goals and objectives or any feedback from the Deviations from goals and objectives or any feedback from the environment may lead to requests for change, which includes environment may lead to requests for change, which includes enterprise re-engineering, continuous improvements of its human enterprise re-engineering, continuous improvements of its human and technology resources, its business process, and its organization.and technology resources, its business process, and its organization.

DecommissionDecommission– The activities needed for disbanding, re-missioning, re-training, The activities needed for disbanding, re-missioning, re-training,

redesign, recycling, preservation, transfer, disassembly, or disposal redesign, recycling, preservation, transfer, disassembly, or disposal of all or part of the entity at the end of its useful life in operation. of all or part of the entity at the end of its useful life in operation.

GERA GERA - - Enterprise’s entity types (4)Enterprise’s entity types (4)

Type A – strategic management entityType A – strategic management entity– such as an (enterprise) engineering projectsuch as an (enterprise) engineering project– Very short life cycleVery short life cycle

Type B – engineering implementation entityType B – engineering implementation entity– Entity that creates other enterprise entitiesEntity that creates other enterprise entities

Type C – enterprise entityType C – enterprise entity– Entity that produces customers goods and servicesEntity that produces customers goods and services

Type D – product entityType D – product entity– All products and customers services of enterprise type All products and customers services of enterprise type

CC Type E – methodology entityType E – methodology entity

– Entity that establishes tasks to support other entities.Entity that establishes tasks to support other entities.

GERA GERA - - views (1)views (1)

Entity model contents viewsEntity model contents views– Function (model of functions and behaviors of business processes)Function (model of functions and behaviors of business processes)– Information (model)Information (model)– Organization (of responsibilities and authorizations on entities)Organization (of responsibilities and authorizations on entities)– Resource (model)Resource (model)

Entity purpose viewsEntity purpose views– (Customer) service and product views (contents relevant to operation (Customer) service and product views (contents relevant to operation

and its resultsand its results– Management and control views (contents relevant to mgt.)Management and control views (contents relevant to mgt.)

Entity implementation viewsEntity implementation views– Human activities view (of information related to human tasks)Human activities view (of information related to human tasks)– Automated activities view (of information related to machine tasks)Automated activities view (of information related to machine tasks)

Entity physical manifestation viewsEntity physical manifestation views– Software view (information resources capable of perform a task set) Software view (information resources capable of perform a task set) – Hardware view (physical resources capable to perform a set of tasks)Hardware view (physical resources capable to perform a set of tasks)

PERA Layers (life cycle PERA Layers (life cycle phases)phases) IdentificationIdentification

– of the CIM business entityof the CIM business entity Concept layer Concept layer

– mission, vision, and valuesmission, vision, and values Definition layer Definition layer

– functional requirementfunctional requirement Specification layersSpecification layers

– architectural designarchitectural design Detailed design layerDetailed design layer Manifestation layerManifestation layer

– ImplementationImplementation Operations layer Operations layer

Row Perspective Constraint Model

1 Planner Financial/external Scope (an executive summary of system scope, cost, and how it would perform)

2 Owner Usage/policy Enterprise (business) model (business entities, processes and how they interact)

3 Designer (analyst) Structure/operation System model (data elements and functions that represent business entities and processes)

4 Builder Technology Technology model (adapting information model to the details of programming languages, tools, I/O devices, and others)

5 Subcontractor Implementation Out of context models (detailed specifications given to programmers who code modules)

  Data (with entity and relation)

Function (with function and parameter)

Network (with node and link)

Scope (planner) List of things important to the business (entity: class of business thing)

List of processes the business performs (function: class of business processes)

List of location in which the business operates (node: major business location)

Enterprise model (owner) ENT/REL diagram (business entity, business constraint)

Process flow diagram (business process and resources)

Logistics network (business location, business linkage)

System model (designer) Data model (data entity and data relationship)

Data flow diagram (application function and user view)

Distributed system architecture (I/S function, and line characteristics)

Technology model (builder) Data design (segment/row; pointers/key)

Structure chart (computer function and screen/device format)

System architecture (hardware/system software, line specifications)

Components (subcontractor)

Data definition description (field and address)

Program (language statement and control block)

Network architecture (address, protocol)

  People (agent, work) Time (time, cycle) Motivation (ends, means)

Scope List of organizations/agents important to the business (major org. unit)

List of events significant to the business (major business event)

List of business goal/strategy (major bus. goal and critical success factor)

Enterprise model Organization chart (org. unit, work product)

Master schedule (business event and bus. cycle)

Business plan (business objective and bus. strategy)

System model Human interface architecture (role, deliverable)

Processing structure (system event and processing cycle)

Knowledge architecture (criterion, option)

Technology model Human/technology interface (user, job)

Control structure (execute, component cycle)

Knowledge design (condition and action)

Components Security architecture (identity, transaction)

Timing definition (interrupt and machine cycle)

Knowledge definition (sub condition, step)

Notes:Notes:

Of an information system, the 3 columns Of an information system, the 3 columns represent data (entities involved), represent data (entities involved), functions (to be performed) and network functions (to be performed) and network (locations and interconnections)(locations and interconnections)

The rows of the framework represent The rows of the framework represent different abstractions from or different different abstractions from or different ways to describe the real world.ways to describe the real world.

For physical processes in engineering, For physical processes in engineering, the 3 columns represent the material, the 3 columns represent the material, the functions, and the geometry.the functions, and the geometry.

T8: Home workT8: Home work

Develop a state diagram for a Develop a state diagram for a typical machine tool (class) for its typical machine tool (class) for its life cycle. It should have:life cycle. It should have:– A graphic presentation of the diagramA graphic presentation of the diagram– Definition for each stateDefinition for each state– Definition for each event that triggers Definition for each event that triggers

the transition from one state to the transition from one state to another.another.

Due date: next weekDue date: next week

Comments on T8 HWComments on T8 HW

It is for a class of machine It is for a class of machine equipment, NOT for a particular equipment, NOT for a particular machine such as a vending machine such as a vending machine.machine.

Don’t forget it’s for its life cycle Don’t forget it’s for its life cycle from birth to death. from birth to death.