Hervé Panetto. A framework for analysing product information traceability
-
Upload
milan-zdravkovic -
Category
Technology
-
view
1.145 -
download
7
description
Transcript of Hervé Panetto. A framework for analysing product information traceability
A framework for analysing product information
traceability
Dr. Hervé PanettoFull Professor of Enterprise Information Systems
Centre de Recherche en Automatique de Nancy (CRAN - UMR 7039),Nancy-University, CNRS,
F-54506 Vandoeuvre les Nancy, [email protected]
http://www.panetto.fr
Chair of the IFAC TC 5.3 « Enterprise Integration and Networking »http://www.ifac-tc53.org
School of Engineering in Information Technology
© Hervé Panetto (CRAN UMR 7039, Nancy-University, CNRS)
Where Am I from?
© Hervé Panetto (CRAN UMR 7039, Nancy-University, CNRS)
Nancy-University
Nancy-University (40 000 students)Federation of three universities in Nancy
University Henri Poincaré Nancy I (Sciences & Technology)
University Nancy II (Economics, Law, Arts, Literature, Foreign Languages)
Institut National Polytechnique de Lorraine (Engineering)
In 2012: University of Lorraine (60 000 students)
© Hervé Panetto (CRAN UMR 7039, Nancy-University, CNRS)
Université Henri Poincaré Nancy I
Since 1572Science and Technology17 000 students45 research laboratories: many
associated to the CNRS (French National Research Centre)
1000 researchers, 800 PhD students5 faculties
© Hervé Panetto (CRAN UMR 7039, Nancy-University, CNRS)
Research Centre for Automatic Control
JRU associate to Nancy-University and CNRS5 Scientific Research Groups
Automatic Control : Systems Control and observation (ACOS) Systems Identification and Signal Processing (IRIS) Ambient Manufacturing Systems (SYMPA) Dependability and System Diagnosis (SURFDIAG) Health Engineering (IPS)
200 persons (1st Jan. 2010) 30 Professors
42 Associate Professors
7 Researchers CAV
23 Engineers and TechAdminist
85 PhDstudents
13 Post-doct
http://www.cran.uhp-nancy.fr
© Hervé Panetto (CRAN UMR 7039, Nancy-University, CNRS)
Ambiant Manufacturing Systems
3 Research projectsInteroperating systemsProduct-Driven systemsNetworked-Driven systems
50 persons (1st Jan. 2010)
© Hervé Panetto (CRAN UMR 7039, Nancy-University, CNRS)
Agenda
The context: Enterprise ApplicationsProduct-Driven ParadigmTraceability uses and needsIEC 62264 standardsThe Zachman Framework… for Product information traceabilityConclusions
© Hervé Panetto (CRAN UMR 7039, Nancy-University, CNRS)
The enterprise applications « constellation »
CRM APS
SCE MES
ERP
Main Prod Stock Sales Trans
Conf EMA
SAV
GCO CTI
SFABI
SCM
SFC
© Hervé Panetto (CRAN UMR 7039, Nancy-University, CNRS)
The Product « views »
HRHuman
Resources
ERPLogistics
SCMSupplyChain
Management
MESManufacturing
ExecutionSystems
CRMCustomer
RelationshipManagement
ERPFinancials
PLMProduct Lifecycle
Management
The product
© Hervé Panetto (CRAN UMR 7039, Nancy-University, CNRS)
Product-Driven Paradigm
ERP
APS
CRMERP
APS
CRM
Business world
MESMES
SCESCE
MESMES
SCESCE
Product
Manufacturing world
PLM
Model-DrivenProduct/ProcessEngineering
ManufacturingExecution
Product LifecycleManagement
© Hervé Panetto (CRAN UMR 7039, Nancy-University, CNRS)
Product Lifecycle Management
Customer behaviour
Global markets
Global competition
Product complexity
Product Design
Process Design
Plant Design
PP&CAfter Sales
Logistics ……
(Globally Scaled) Product and Production Lifecycle
Integration between processes/tools/enviroments
Product Lifecycle Management
© Hervé Panetto (CRAN UMR 7039, Nancy-University, CNRS)
Traceability
Traceability is a PLM question:Organizational perspective (allocation of tracing task) Information perspective (coding and decoding) Infrastructure perspective (systems for traceability)
Traceability in literature:Traceability for Quality procedures (ISO 9000 – Chen
and Simmons 1994)Traceability is the abilitity to trace in a forward and
backward direction (Jansen-Vullers et al. 2003)Traceability deals with mantaining records (Karkkainen
et al. 2003)
© Hervé Panetto (CRAN UMR 7039, Nancy-University, CNRS)
Traceability
Industrial sectors: Traceability in Food industry (e.g. Moe 1998) Traceability in Construction (e.g. Finch 1996) Traceability in Software Development (e.g. Gothel 1994)
Industrial Applications: Traceability in SCM (e.g. Karkkainen et al. 2003) Traceability in After Sales (e.g. Sohal 1997) Traceability in Plant Management (e.g. Garner et al. 2003)
Tracing systems: Traceability with bar code (EAN/JAN consortium, 2D) Traceability with RFID (e.g. AutoID) Traceability with MEMS (e.g. RAND)
© Hervé Panetto (CRAN UMR 7039, Nancy-University, CNRS)
Traceability limits “Product” Traceability deals with coding and identification, for
mantaining records Then, information records are stored into (one or more) database,
accessed using product code or directly into tags such as RFID A merging activity between product and information is needed for
tracing (e.g. AutoID, Dialog efforts) This activity is not risk-free (Karkkainen et al. 2003):
Accessibility unavailable Timing and costing of accessibility
Info
Product
Info
ProductP
© Hervé Panetto (CRAN UMR 7039, Nancy-University, CNRS)
Needs
StandardsFor structuring the information related to a
product, independently to the applicationsFor bringing semantics to that information
FrameworksFor helping modellers to think about traceability
at the initial stage of the system design
© Hervé Panetto (CRAN UMR 7039, Nancy-University, CNRS)
IEC 62264 Standard (IEC 62264, 2002)
Based on the ISA95 « Enterprise-control systems integration »
ISO and IECDefines the interface between Business
and Manufacturing worlds in terms of information exchange and semantics
© Hervé Panetto (CRAN UMR 7039, Nancy-University, CNRS)
Business To Manufacturing Integration - What does it mean?Coordinating the functions and goals of
the business with the functions and goals of the business’s manufacturing operations
In simple terms make sure that manufacturing is building the
right products, at the right time, using the right materials to meet the business’s needs,
and make sure that the business has correct information on production and actual material, personnel, and equipment use
BusinessLogistics
ManufacturingOperations
© Hervé Panetto (CRAN UMR 7039, Nancy-University, CNRS)
Because …
In many cases business needs are not effectively made known to manufacturing operations
In many cases actual production is not effectively made known to business operations
Delays and errors are common, often expected, and very expensive
© Hervé Panetto (CRAN UMR 7039, Nancy-University, CNRS)
Functional hierarchy as defined in IEC 62264
Business Planning& Logistics Information
Plant Production Scheduling, Operational Management, etc
Manufacturing Operations& Control Information
Area Supervision, Production Planning, Reliability, Assurance, etc
ProductDefinition
Information(How to make
a product)
ProductionCapability
Information(What isavailablefor use)
ProductionSchedule
(What tomake and
use)
ProductionPerformance
(What wasmade and
used)
© Hervé Panetto (CRAN UMR 7039, Nancy-University, CNRS)
The IEC 62264 models hierarchy
ProductionCapability
CapabilityProperty
ResourceCapability
ProductionCapability
What resourcesare available
ProductionPerformance
ProductionResponse
SegmentResponse
ActualProperty
ResourceActual
ProductionInformation
What wasmade & used
ProductionRequest
SegmentRequirement
RequirementProperty
ResourceRequirement
ProductionSchedulingWhat is it to bemade & used
ProductionSchedule
ProductionRule
ProductSegment
SpecificationProperty
ResourceSpecification
ProductDefinition
What must be definedto make a product
ProcessSegment
SegmentProperty
ResourceSegmentCapability
ProcessSpecificationWhat can be donewith the resources
© Hervé Panetto (CRAN UMR 7039, Nancy-University, CNRS)
IEC 62264 Models
Material ModelEquipment ModelPersonel ModelProduct Definition ModelProcess Segment ModelProduction Schedule ModelProduction Capability ModelProduction Performance Model
© Hervé Panetto (CRAN UMR 7039, Nancy-University, CNRS)
The conceptualised IEC 62264 Material model
MaterialClass
+Description
MaterialDefinition
+Description:string
QAMaterialTestSpecification
+Description+Name+Version
MaterialLot
+Description+Status
MaterialSubLot
+Description+Status
MaterialClassProperty
+Description+Value
MaterialDefinitionProperty
+Description+Value:string
MaterialLotProperty
+Description+Value
*
1..*
Is tested By
*
1..*
Is tested by
*Defines a procedure for obtaining a
*
*1
Defined by *1
Made up of
*
1Has properties
of *
1Has properties
of*
1
Has values for
* *
Defines a grouping
Location
+Description
*
Location
0..1
MaterialCapability
+CapabilityType+Description+EndTime+MaterialUse+Quantity+Reason+StartTime
*
1
MaterialInformation
+Description+PublishedDate
0..1
Location
*
*
MaterialDefinition
*
MaterialClass
*MaterialLot
*
*
QAMaterialTestSpecification
*MaterialSubLot
*
0..1
*
Location
© Hervé Panetto (CRAN UMR 7039, Nancy-University, CNRS)
The Material Model
LotHCL-50-100019
pH7.0
Density1.32
ColorYellow
Purity.5%
Material
Definitio
n
Material DefinitionHCl 50%
Color PuritypH
Material ClassAcid
Material
Class
Density
SublotHCL-50-100019
Barrel 15
LocationQA TestSpecification
QA TestResults
Common material information
© Hervé Panetto (CRAN UMR 7039, Nancy-University, CNRS)
Needs
StandardsFor structuring the information part of a product,
independently to the applicationsFor bringing semantics to that information
FrameworksFor helping modellers to think about traceability
at the initial stage of the system design
© Hervé Panetto (CRAN UMR 7039, Nancy-University, CNRS)
The Zachman framework
John Zachman proposed the framework for Enterprise Architecture (Zachman, 1987) and extended it in 1992 (Sowa and Zachman, 1992)
He organized a lifecycle around the points of view taken by the various players in a system engineering project
© Hervé Panetto (CRAN UMR 7039, Nancy-University, CNRS)
Players’ points of view
Planner The one who has undertaken to do business in a particular
industry and runs the organizationOwner
the systems analyst who wants to represent the business in a disciplined form
Designer the designer, who applies specific technologies to solve the
problems of the businessBuilder
the builder of the system who specifies how it executesSub-contractor
The developer of the system
© Hervé Panetto (CRAN UMR 7039, Nancy-University, CNRS)
The categories of models
Data (What)Function (How)Network (Where)People (Who)Time (When)Motivation (Why)
© Hervé Panetto (CRAN UMR 7039, Nancy-University, CNRS)
The Zachman framework matrixBased on work by John A. Zachman
VA Enterprise Architecture
DATAWhat
FUNCTIONHow
NETWORKWhere
PEOPLEWho
TIMEWhen
MOTIVATIONWhy
DATAWhat
FUNCTIONHow
NETWORKWhere
PEOPLEWho
TIMEWhen
MOTIVATIONWhy
SCOPE(What is importantfor the enterprise)
Planner
ENTERPRISEMODEL(What is available)
Owner
SYSTEM MODEL(How to build products)
Designer
TECHNOLOGYMODEL(How to implement)
Builder
DETAILEDREPRESENTATIONS
Sub-Contractor
FUNCTIONINGENTERPRISE
SCOPE(What is importantfor the enterprise)
Planner
ENTERPRISEMODEL
(What is available)
Owner
SYSTEM MODEL(How to build products)
Designer
TECHNOLOGYMODEL
(How to implement)
Builder
DETAILEDREPRESENTATIONS
Sub-Contractor
FUNCTIONINGENTERPRISE
Things Important to the Business
Entity = Class of Business Thing
ProcessesPerformed
Function = Class of Business Process
Semantic Model
Ent = Business EntityRel = Business Relationship
Business ProcessModel
Proc = Business ProcessI/O = Business Resources
Business LogisticsSystem
Node = Business Location Link = Business Linkage
Work Flow Model
People = Organization Unit Work = Work Product
Master Schedule
Time = Business Event Cycle = Business Cycle
Business Plan
End = Business Objective Means = Business Strategy
ImportantOrganizations
People = Major Organizations
Business locations
Node = Major Business Locations
Events Significantto the Business
Time = MajorBusiness Event
Business Goalsand Strategy
Ends/Means =Major Business Goals
Logical DataModel
Ent = Data EntityRel = Data Relationship
Application Architecture
Proc = Application FunctionI/O = User Views
Distributed SystemArchitecture
Node = IS FunctionLink = Line Characteristics
Human InterfaceArchitecture
People = RoleWork = Deliverable
ProcessingStructure
Time = System Event Cycle = Processing Cycle
Business RuleModel
End = Structural Assertion Means = Action Assertion
Physical DataModel
Ent = Segment/Table Rel = Pointer/Key
SystemDesign
Proc = Computer FunctionI/O = Data Elements/Sets
TechnologyArchitecture
Node = Hardware/Software Link = Line Specifications
PresentationArchitecture
People = User Work = Screen Format
ControlStructure
Time = ExecuteCycle = Component Cycle
RuleDesign
End = Condition Means = Action
DataDefinition
Ent = Field Rel = Address
Program
Proc = Language StatementI/O = Control Block
NetworkArchitecture
Node = AddressesLink = Protocols
SecurityArchitecture
People = IdentityWork = Job
Timing Definition
Time = InterruptCycle = Machine Cycle
RuleDesign
End = Sub -Condition Means = Step
Data
Ent = Rel =
Function
Proc =I/O =
Network
Node = Link =
Organization
People = Work =
Schedule
Time = Cycle =
Strategy
End = Means =
ProcessingStructure
Time = System Event Cycle = Processing Cycle
Business RuleModel
End = Structural Assertion Means = Action Assertion
Physical DataModel
Ent = Segment/Table Rel = Pointer/Key
SystemDesign
Proc = Computer FunctionI/O = Data Elements/Sets
TechnologyArchitecture
Node = Hardware/Software Link = Line Specifications
PresentationArchitecture
People = User Work = Screen Format
ControlStructure
Time = ExecuteCycle = Component Cycle
RuleDesign
End = Condition Means = Action
DataDefinition
Ent = Field Rel = Address
Program
Proc = Language StatementI/O = Control Block
NetworkArchitecture
Node = AddressesLink = Protocols
SecurityArchitecture
People = IdentityWork = Job
Timing Definition
Time = InterruptCycle = Machine Cycle
RuleDesign
End = Sub -Condition Means = Step
Data
Ent = Rel =
Function
Proc =I/O =
Network
Node = Link =
Organization
People = Work =
Schedule
Time = Cycle =
Strategy
End = Means =
Based on work by John A. Zachman
VA Enterprise Architecture
DATAWhat
FUNCTIONHow
NETWORKWhere
PEOPLEWho
TIMEWhen
MOTIVATIONWhy
DATAWhat
FUNCTIONHow
NETWORKWhere
PEOPLEWho
TIMEWhen
Based on work by John A. Zachman
VA Enterprise Architecture
DATAWhat
FUNCTIONHow
NETWORKWhere
PEOPLEWho
TIMEWhen
MOTIVATIONWhy
DATAWhat
FUNCTIONHow
NETWORKWhere
PEOPLEWho
TIMEWhen
MOTIVATIONWhy
- -
Things Important to the Business
Entity = Class of Business Thing
ProcessesPerformed
Function = Class of Business Process
Semantic Model
Ent = Business EntityRel = Business Relationship
Business ProcessModel
Proc = Business ProcessI/O = Business Resources
Business LogisticsSystem
Node = Business Location Link = Business Linkage
Work Flow Model
People = Organization Unit Work = Work Product
Master Schedule
Time = Business Event Cycle = Business Cycle
Business Plan
End = Business Objective Means = Business Strategy
ImportantOrganizations
People = Major Organizations
Business locations
Node = Major Business Locations
Events Significantto the Business
Time = MajorBusiness Event
Business Goalsand Strategy
Ends/Means =Major Business Goals
Logical DataModel
Ent = Data EntityRel = Data Relationship
Application Architecture
Proc = Application FunctionI/O = User Views
Distributed SystemArchitecture
Node = IS FunctionLink = Line Characteristics
Human InterfaceArchitecture
People = RoleWork = Deliverable
ProcessingStructure
Time = System Event Cycle = Processing Cycle
Business RuleModel
End = Structural Assertion Means = Action Assertion
Physical DataModel
Ent = Segment/Table Rel = Pointer/Key
SystemDesign
Proc = Computer FunctionI/O = Data Elements/Sets
TechnologyArchitecture
Node = Hardware/Software Link = Line Specifications
PresentationArchitecture
People = User Work = Screen Format
ControlStructure
Time = ExecuteCycle = Component Cycle
RuleDesign
End = Condition Means = Action
DataDefinition
Ent = Field Rel = Address
Program
Proc = Language StatementI/O = Control Block
NetworkArchitecture
Node = AddressesLink = Protocols
SecurityArchitecture
People = IdentityWork = Job
Timing Definition
Time = InterruptCycle = Machine Cycle
RuleDesign
End = Sub -Condition Means = Step
Data
Ent = Rel =
Function
Proc =I/O =
Network
Node = Link =
Organization
People = Work =
Schedule
Time = Cycle =
Strategy
End = Means =
People = IdentityWork = Job
Timing Definition
Time = InterruptCycle = Machine Cycle
RuleDesign
End = Sub -Condition Means = Step
Data
Ent = Rel =
Function
Proc =I/O =
Network
Node = Link =
Organization
People = Work =
Schedule
Time = Cycle =
Strategy
End = Means =
© Hervé Panetto (CRAN UMR 7039, Nancy-University, CNRS)
Recursivity of the framework
At a first stage, the framework defines abstraction levels of the engineering processScopeEnterprise model MDA CIM LevelSystem model MDA PIM LevelTechnology model MDA PSM LevelDetailed implementation
© Hervé Panetto (CRAN UMR 7039, Nancy-University, CNRS)
IEC 62264 standards on the Zachman abstraction view
Based on work by John A. Zachman
VA Enterprise Architecture
DATAWhat
FUNCTIONHow
NETWORKWhere
PEOPLEWho
TIMEWhen
MOTIVATIONWhy
DATAWhat
FUNCTIONHow
NETWORKWhere
PEOPLEWho
TIMEWhen
MOTIVATIONWhy
SCOPE(CONTEXTUAL)
ENTERPRISEMODEL(CONCEPTUAL)
SYSTEM MODEL(LOGICAL)
TECHNOLOGY
MODEL(PHYSICAL)
DETAILEDREPRESENTATIONS
FUNCTIONINGENTERPRISE
SCOPE(CONTEXTUAL)
Planner
ENTERPRISEMODEL
(CONCEPTUAL)
Owner
SYSTEM MODEL(LOGICAL)
Designer
TECHNOLOGY
MODEL(PHYSICAL)
Builder
DETAILEDREPRESENTATIONS(OUT -OF -CONTEXT)
Sub -Contractor
FUNCTIONINGENTERPRISE
Master Schedule
Time = Business Event Cycle = Business Cycle
Business Plan
End = Business Objective Means = Business Strategy
Events Significantto the Business
Time = MajorBusiness Event
Business Goalsand Strategy
Ends /Means =Major Business Goals
Business RuleModel
End = Structural Assertion Means = Action Assertion
RuleDesign
End = Condition Means = Action
DataDefinition
Ent = Field Rel = Address
Program
Proc = Lang.StatementI/O = Control Block
NetworkArchitecture
Node = AddressesLink = Protocols
SecurityArchitecture
People = IdentityWork = Job
Timing Definition
Time = InterruptCycle = Machine Cycle
RuleDesign
End = Sub-Condition Means = Step
Data
Ent = Rel =
Function
Proc =I/O =
Network
Node = Link =
Organization
People = Work =
Schedule
Time = Cycle =
Strategy
End = Means =
IEC 62264Standards
Holonic ProcessModels
B2MMLXML Schemas
Goods &Services
Processes Sites Actors
© Hervé Panetto (CRAN UMR 7039, Nancy-University, CNRS)
IEC 62264 models mapped onto the players view
Based on work by John A. Zachman
VA Enterprise Architecture
DATAWhat
FUNCTIONHow
NETWORKWhere
PEOPLEWho
TIMEWhen
MOTIVATIONWhy
DATAWhat
FUNCTIONHow
NETWORKWhere
PEOPLEWho
TIMEWhen
MOTIVATIONWhy
SCOPE(What is importantfor the enterprise)
Planner
ENTERPRISEMODEL(What is available)
Owner
SYSTEM MODEL(How to build products)
Designer
TECHNOLOGYMODEL(How to implement)
Builder
DETAILEDREPRESENTATIONS
Sub-Contractor
FUNCTIONINGENTERPRISE
SCOPE(What is importantfor the enterprise)
Planner
ENTERPRISEMODEL
(What is available)
Owner
SYSTEM MODEL(How to build products)
Designer
TECHNOLOGYMODEL
(How to implement)
Builder
DETAILEDREPRESENTATIONS
Sub-Contractor
FUNCTIONINGENTERPRISE
Business Plan
End = Business Objective Means = Business Strategy
Business Goalsand Strategy
Ends/Means =Major Business Goals
Business RuleModel
End = Structural Assertion Means = Action Assertion
Physical DataModel
Ent = Segment/Table Rel = Pointer/Key
SystemDesign
Proc = Computer FunctionI/O = Data Elements/Sets
TechnologyArchitecture
Node = Hardware/Software Link = Line Specifications
PresentationArchitecture
People = User Work = Screen Format
ControlStructure
Time = ExecuteCycle = Component Cycle
RuleDesign
End = Condition Means = Action
DataDefinition
Ent = Field Rel = Address
Program
Proc = Language StatementI/O = Control Block
NetworkArchitecture
Node = AddressesLink = Protocols
SecurityArchitecture
People = IdentityWork = Job
Timing Definition
Time = InterruptCycle = Machine Cycle
RuleDesign
End = Sub -Condition Means = Step
Schedule Strategy
IEC 62264Material Model
IEC 62264Personnel
Model
IEC 62264Product Definition Model
IEC 62264Equipment
ModelIEC 62264
Production Schedule
Model
IEC 62264Production Capability Model
IEC 62264Process Segment Model
IEC 62264Production Performance Model
Based on work by John A. Zachman
VA Enterprise Architecture
DATAWhat
FUNCTIONHow
NETWORKWhere
PEOPLEWho
TIMEWhen
MOTIVATIONWhy
DATAWhat
FUNCTIONHow
NETWORKWhere
PEOPLEWho
TIMEWhen
MOTIVATIONWhy
SCOPE(CONTEXTUAL)
ENTERPRISEMODEL(CONCEPTUAL)
SYSTEM MODEL(LOGICAL)
TECHNOLOGYMODEL(PHYSICAL)
DETAILEDREPRESENTATIONS
FUNCTIONINGENTERPRISE
SCOPE(CONTEXTUAL)
Planner
ENTERPRISEMODEL
(CONCEPTUAL)
Owner
SYSTEM MODEL(LOGICAL)
Designer
TECHNOLOGYMODEL
(PHYSICAL)
Builder
DETAILEDREPRESENTATIONS(OUT-OF-CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
Master Schedule
Time = Business Event Cycle = Business Cycle
Business Plan
End = Business Objective Means = Business Strategy
Events Significantto the Business
Time = MajorBusiness Event
Business Goalsand Strategy
Ends/Means =Major Business Goals
Business RuleModel
End = Structural Assertion Means = Action Assertion
RuleDesign
End = Condition Means = Action
DataDefinition
Ent = Field Rel = Address
Program
Proc = Lang.StatementI/O = Control Block
NetworkArchitecture
Node = AddressesLink = Protocols
SecurityArchitecture
People = IdentityWork = Job
Timing Definition
Time = InterruptCycle = Machine Cycle
RuleDesign
End = Sub-Condition Means = Step
Data
Ent = Rel =
Function
Proc =I/O =
Network
Node = Link =
Organization
People = Work =
Schedule
Time = Cycle =
Strategy
End = Means =
IEC 62264Standards
Holonic ProcessModels
B2MMLXML Schemas
Goods &Servicesa
Processes Sites Actors
© Hervé Panetto (CRAN UMR 7039, Nancy-University, CNRS)
Products information traceability
Forward traceability
Backward traceability
Abstraction view Players view
The Zachman framework: filter for views definition of products information traceability models
© Hervé Panetto (CRAN UMR 7039, Nancy-University, CNRS)
The IEC 62264 modelling framework workflow
Use of the Functionning
Enterprise
DesignerOwnerPlannerProducts Business
- ERP
Products Manufacturing
- MESProducts specification
Product definitionMaterial specification
Equipment specificiation
Personnel specification
Material definition
Equipment definition
Personnel definition
Product segments specification Production schedule definition
Personnel capability
Equipment capability
Material capability
Process segments definition
Production capabilityMaterial availability
Equipment availability
Personnel availability
Production responses
Production information
Process segments
Production requests
Product information traceability
Forward traceability
Backward traceability
Application
Modelling Activity
External Application
Player
Service
Legend
Production performanceProduction information
© Hervé Panetto (CRAN UMR 7039, Nancy-University, CNRS)
System Engineering for Product Traceability
EnterprisePlanning
Manufacturing Execution
ProcessControl
EngineeringApplications
Incoplan
Factory Suite
Product DataManagement
FlexNet
ProductTraceability
Product Service-orientedInteroperability
Product information-orientedInteroperability
Models-orientedInteroperability
Exploitation/Application
Engineering
© Hervé Panetto (CRAN UMR 7039, Nancy-University, CNRS)
Conclusions
We define a specific perspective of the framework dealing with the players view as a guideline for better understanding the product informations for traceability
The IEC 62264 deals with products information at both Business and Manufacturing levels, thus it is a good candidate set of models for product traceability
However, the models are complex because they are generic to any kind of application domains.
The framework helps at defining product lifecycle information models for traceability
The result of this modelling approach is the emergence of all information objects that deal with product information along its life cycle
© Hervé Panetto (CRAN UMR 7039, Nancy-University, CNRS)
References Panetto H., Baïna, S., Morel G. (2006). Mapping the IEC 62264 models onto the Zachman framework for analysing products information traceability: a
case study. Journal of Intelligent Manufacturing, Springer Verlag, ISSN 0956-5515, to appear in 2007 Baïna S., Panetto H., and Morel G. (2005), Holon-oriented B2M process modelling approach for applications interoperability in manufacturing systems
environment, Proceedings of the IFAC World Congress, July 4-7, Prague, Czech Republic, ISBN: 0-08-045108-X Bézivin J. (2004). In search of a Basic Principle for Model Driven Engineering, Novatica/Upgrade, Vol. V, N°2, April, pp. 21-24, http://www.upgrade-
cepis.org/issues/2004/2/upgrade-vol-V-2.html Cheng M.L. and Simmons J. E. L. (1994). Traceability in manufacturing systems. International Journal of Operations and Production Management, 14,
4-16 C4ISR Architecture Framework Version 2.0 (1997). Office of the Assistant Secretary of Defense for Command, Control, Communications and
Intelligence, Washington D.C., November delaHostria E. (2005). Manufacturing Application Integration Scheme using ISO 15745 and IEC 62264. Proceedings of the IFAC World Congress, July
4-7, Prague, Czech Republic, ISBN: 0-08-045108-X IEC 62264 (2002). IEC 62264. Enterprise-control system integration, Part 1. Models and terminology, Part 2: Model object attributes. ISO/IEC, Geneva ISO IS 15704 (2000). ISO/IS 15704:2000 Industrial automation systems—Requirements for enterprise—reference architectures and methodologies,
ISO, Geneva, Switzerland ISO 15745-1, (2003) Industrial automation systems and integration – Open systems application integration framework - Part 1: Generic reference
description. ISO, Geneva, Switzerland Frankel D. S., et al. (2003). The Zachman Framework and the OMG's Model Driven Architecture. Business Process Trends Whitepaper, September,
http://www.bptrends.com Jansen-Vullers J., van Dorp A., and Beulens B. (2003). Managing traceability information in manufacture, International Journal of Information
Management, 23, 395-413 McFarlane D., Sarma J., Chirn G., Wong J., Ashton A. (2003). Auto-ID systems and intelligent manufacturing control, Journal of Engineering
Applications of Artificial Intelligence, 16, 365 – 376 Mellor S.J., Kendall S., Uhl A. and Weise D. (2004). Model Driven Architecture, Addison-Wesley Pub Co, March, ISBN: 0201788918. Morel G., Panetto H., Zaremba M.B. and Mayer F. (2003). Manufacturing Enterprise Control and Management System Engineering: paradigms and
open issues. IFAC Annual Reviews in Control. 27/2:199-209, December Noran O. (2003). An analysis of the Zachman framework for enterprise architecture from the GERAM perspective. IFAC Annual Reviews in Control.
27/2:163-183, December Osvalds G. (2003). Use of UML in Modeling Enterprise and Systems Architecture. INCOSE Chesapeake Chapter Meeting, Columbia, August O'Rourke C., Fishman N. and Selkow W. (2003). Enterprise Architecture Using the Zachman Framework,, Thomson Learning, Inc. Boston, MA. ISBN:
0-619-06446-3. April Sowa J. F. and Zachman J. A. (1992). Extending and Formalizing the Framework for Information Systems Architecture, IBM Systems Journal, 31/3,
590–616 Sowell P. K. (1999). Consolidated Mapping of C4ISR Framework Products to Federal Framework Models. The MITRE Corporation, McLean, Virginia. Terzi S. (2005). Elements of Product Lifecycle Management: Definitions, Open Issues and Reference Models, PhD dissertation, University Henri
Poincaré Nancy I and Politecnico di Milano, May 25th Terzi S., Cassina J., and Panetto H. (2005). Development of a metamodel to foster interoperability along the product lifecycle traceability. Proceedings
of the IFIP/ACM INTEROP-ESA conference, February 23-25, Geneva, Switzerland, Springer Science publisher, pp. 1-11, ISBN: 1-84628-151-2 UML (2005). Unified Modeling Language. UML 2.0 Superstructure, v2.0 formal 05/07/04. OMG Zachman J. A. (1987). A Framework for Information Systems Architecture, IBM Systems Journal, 26/3, 276–295
© Hervé Panetto (CRAN UMR 7039, Nancy-University, CNRS)
Subset of the planner view
Equipment Model
Product Definition
Flour Bag:ProductDefinitionType
PublishedDateVersionDescription
Fill a Bag:ProductSegmentType
DescriptionDurationParameter
Has associated
Prepare Flour:ProductSegmentType
DescriptionDurationParameter
PrepFull:ProductSegmentDependencyOtherValue:string=AfterEnd
Has an execution dependency on
Bag filler:EquipmentSpecificationTypeQuantity:Quantity={50, Kg}Description
Equipment specification
Mixer:EquipmentSpecificationType
DescriptionQuantity:Quantity
Equipment specification
Mixer 50:EquipmentDescription
Equipment
Bag filler:EquipmentDescription
Equipment
DATAWhat
NETWORKWhere
SCOPE(What is importantfor the enterprise)
Planner
FUNCTIONHow
Instance name:Classproperties:type=values
Association name
Legend
© Hervé Panetto (CRAN UMR 7039, Nancy-University, CNRS)
Subset of the owner view
Equipment Model
Material Model
Flour:MaterialDefinitionDescription:string
FlourBags:MaterialLotStatusDescription
Defined by
Composition type:MaterialDefinitionProperty
ValueDescription
Has properties of
Flour type:MaterialDefinitionPropertyValueDescription
Has properties of
Packing:MaterialLotProperty
DescriptionValue
Has values for
Flour type:MaterialLotProperty
DescriptionValue
Has values for
Palette:LocationDescription
EquipmentElementLevel
Location
Mixer 50:EquipmentDescription
Zone2:LocationDescription
Level:EquipmentElementLevelTypeOtherValue:string=ProductionLIne
EquipmentElementLevel
Location
Bag filler:EquipmentDescription
Location
Has Value for
Bag:MaterialDefinitionDescription:string
Level:EquipmentElementLevelType
OtherValue:string=StorageUnit
BagCapacity:EquipmentPropertyValue:Quantity={50, Kg}Description:string=Capacity of Bags to be filledTestResult
ENTERPRISEMODEL(What is available)
Owner
DATAWhat
NETWORKWhere
Instance name:Classproperties:type=values
Association name
Legend
© Hervé Panetto (CRAN UMR 7039, Nancy-University, CNRS)
Subset of the designer view
Material Model Equipment Model
Process Segment
Fill Bags:ProcessSegmentType
ParameterDescriptionPublishedDateDuration
Bag:MaterialSegmentSpecification
TypeMaterialUse:string=ConsumedQuantity:Quantity=1Description
Bag:MaterialDefinitionDescription:string
MaterialDefinition
Flour:MaterialSegmentSpecification
TypeMaterialUse:string=ConsumedQuantity:Quantity={50, Kg}Description
Flour:MaterialDefinitionDescription:string
MaterialDefinition
MaterialSegmentSpecification
MaterialSegmentSpecification
FlourBag:MaterialSegmentSpecification
TypeMaterialUse:string=ProducedQuantity:Quantity=1Description
MaterialSegmentSpecification
Bag filler:EquipmentSegmentSpecification
TypeDescriptionQuantity
EquipmentSegmentSpecification
Equipment
Corbeil:LocationDescription
Level:EquipmentElementLevel
TypeOtherValue:string=Site
EquipmentElementLevel
Location
Bag filler:EquipmentDescription
DATAWhat
NETWORKWhere
FUNCTIONHow
SYSTEM MODEL(How to build products)
Designer
Instance name:Classproperties:type=values
Association name
Legend