Kpi Ml v01

KPI-ML LogosSource

KPI ML

class KPI Object Model

KPI Definition

+ ID+ Name [0..1]+ Description [0..*]+ Scope [0..*]+ Formula [0..1]+ UnitOfMeasure [0..1]+ Trend [0..1]+ Timimg [0..1]+ Audience [0..*]+ ProductionMethodology [0..*]+ EffectModel [0..*]+ Notes [0..*]

KPI Value

+ ID+ Description [0..*]+ Name [0..1]+ Value [0..1]+ UnitOfMeasure [0..1]

KPI Definition Property

+ ID+ Description [0..*]+ Value

KPI Instance Property


KPI Value Property


Resource Reference

+ ID+ Description [0..*]+ ResourceType+ ResourceID

KPI Range

+ ID+ Description [0..*]+ LowerLimit+ UpperLimit

KPI Instance

+ ID+ Description [0..*]+ Name [0..1]+ Scope [0..*]+ Formula [0..1]+ UnitOfMeasure [0..1]+ Trend [0..1]+ Timimg [0..*]+ Audience [0..*]+ ProductionMethodology [0..*]+ EffectModel [0..*]+ Notes [0..*]

KPI Definition Time Range

+ StartTime [0..1]+ EndTime [0..1]+ Recurrence [0..1]+ Duration [0..1]

KPI Instance Time Range

+ StartTime [0..1]+ EndTime [0..1]+ Recurrence [0..1]+ Duration [0..1]

KPI Value Time Range

+ StartTime [0..1]+ EndTime+ Recurrence [0..1]+ Duration [0..1]

0..* 0..10..* 0..*0..* 0..*

1

+is defined in

0..*1

+is defined by

0..*

0..*

0..*

0..*

0..*0..*

0..*0..*

+may be used incalculation of 0..*

0..*

+may be used incalculation of 0..*

0..*

Indicates 1 instance only

Indicates 1 to many instances

Indicates contained elements or attributes

Indicates fixed order of elements

Name of an element or element type

Indicates elements

Indicates 0 or 1 instance only

Indicates 0 to many instances

Indicates no contained elements or attributes

Indicates selection of alternatives

Information Provider

InformationUser

GET

SHOW

Localprocessing

GET Equipment

Application Identification Area

Data Area

VERB = GET

Noun = EquipmentID= “A*”

SHOW Equipment

Application Identification Area

Data Area

VERB = SHOW

Noun = EquipmentID= “ABC”Description = “Simple equipment”Equipment Property ID = “Throughput” Value = “200” Value Unit of Measure = “PPM” Description = “Throughput as parts per minute” …

Noun = EquipmentID= “A11862”Description = “Complex equipment”Equipment Property ID = “Throughput” Value = “2000” Value Unit of Measure = “PPM” Description = “Throughput as parts per minute” …

InformationProvider

InformationRequestor GetKPIDefinition

ShowKPIDefinition

InformationReceiver

InformationSender ProcessKPIValue

AcknowledgeKPIValue

InformationReceiver

InformationSender ChangeKPIInstance

RespondKPIInstance

InformationReceiver

InformationSender

CancelKPIInstance

ConfirmBOD

Value of element determines what is returned



InformationSubscriber

InformationPublisher

SyncKPIInstance (Add)

ConfirmBOD



SyncKPIValue (Change)

ConfirmBOD



SyncKPIDefinition (Delete)

ConfirmBOD

<Verb><Object> <Verb>

<Object>

Verb Specific Area

Object Specific Area

Combined Verb and Object Element Name

ShowEquipmentClassType

ShowEquipmentClass

attributes

ApplicationArea

DataArea

TransShowType

Show

OriginalApplicationArea

TransResponseCriteriaType

ResponseCriteria

0 ¥..

ResponseExpression

ChangeStatus

EquipmentClass

1 ¥..

Contains required “actionCode” attribute of Accepted or Rejected

Contains optional addition reasons for return status

Contains optional “acknowledgeCode” attribute

Contains required “actionCode” attribute

Contains optional “responseCode” attribute

Contains required “actionCode” attribute


Contains required “actionCode” attribute of Add, Change, or Delete


Contains additional information provided by the sender to assist in the handling of any error condition.

Not defined in B2MML

Production Planning & Scheduling Scenario

Level 4PLM

Level 3Product Definition

Management

Level 4Production Planning &

Capacity Analysis

Level 4Inventory Mgt

Level 3Production

Resource Mgt

Level 3Detailed

Scheduling

Level 3Production

Tracking

SH

OW

Pro

duct

Def

initi

on

GE

T P

rodu

ct D

efin

ition

PR

OC

ES

S P

rodu

ctio

n C

apab

ility

PR

OC

ES

S P

rodu

ctio

n S

ched

ule

Communication within Levels 3 or 4 are not shown since they are not in the scope of ISA-95 Parts 1 and 2

PR

OC

ES

S P

rodu

ctio

n P

erfo

rman

ce

PR

OC

ES

S M

ater

ialS

ubLo

t

Level 4Asset Mgt

SH

OW

Equ

ipm

ent

GE

T E

quip

men

t

ERPLevel 4Production Scheduling

MOMLevel 3PROCESS – Production Schedule

PROCESS – Production Performance

Scenario assumptions: 1. ERP send production schedule to MOM for processing2. MOM (Manufacturing Operations Management) sends production performance to ERP for processing

* Message contains a FINAL flag to indicate that the message is the final production performance for the associated production schedule.

PROCESS* – Production Performance

Business Process Scenario #1aPUSH MODEL – Production Schedule / Production Performance

Some workcomplete

All work finished

ERPLevel 4

MOMLevel 3

SHOW – Production Schedule

SHOW – Production Performance

Scenario assumptions: 1. MOM requests production schedule from ERP 2. ERP requests production performance from MOM ~ The GET production performance message contains an identification of a production schedule (Production Performance / Production Schedule ID)* The final SHOW production performance message contains a flag to indicate that the message is the final production performance for the associated production schedule.

SHOW* – Production Performance

Business Process Scenario #3aPULL MODEL – Production Schedule / Production Performance

GET – Production Schedule

GET – Production Performance~

GET – Production Performance~

Some workcomplete

All work finished


MOMLevel 3SYNC ADD – Production Schedule

SYNC ADD – Production Performance

Scenario assumptions: 1. MOM subscribes to production schedules.2. ERP subscribes to production performances.3. ERP publishes production schedule.4. MOM publishes initial production performance with a SYNC ADD message.5. MOM publishes subsequent production performances for the schedule with SYNC CHANGE messages.


SYNC CHANGE* – Production Performance

Business Process Scenario #1aPUBLISH MODEL – Production Schedule / Production Performance

Some workcomplete

All work finished


MOMLevel 3

PROCESS – Production Schedule


Scenario assumptions: 1. ERP sends production schedule to MOM for processing2. MOM sends production performance to ERP for processing 3. ERP makes change to schedule and sends to MOM for processing



Business Process Scenario #1bPUSH MODEL – Production Schedule Changes

CHANGE – Production Schedule


Some workcomplete

All work finished

Schedulechanges

Some morework complete


MOMLevel 3

SYNC ADD – Production Schedule


Scenario assumptions: 1. MOM subscribes to production schedules.2. ERP subscribes to production performances.3. ERP publishes production schedule.4. MOM publishes initial production performance with a SYNC ADD message.5. ERP changes the schedule based on initial work done and republished with a SYNC CHANGE6. MOM publishes subsequent production performances for the schedule with SYNC CHANGE messages.



Business Process Scenario #1bPUBLISH MODEL – Production Schedule Changes

SYNC CHANGE – Production Schedule

SYNC CHANGE – Production Performance

Some workcomplete

All work finished

Schedulechanges



MOMLevel 3



Scenario assumptions: 1. MOM subscribes to production schedules.2. ERP subscribes to production performances.3. ERP publishes production schedule.4. MOM publishes initial production performance with a SYNC ADD message.5. ERP changes schedule and republishes with SYNC CHANGE6. MOM publishes subsequent production performances for the schedule with SYNC CHANGE messages.



Business Process Scenario #1bPUBLISH MODEL – Production Schedule Changes



Some workcomplete

All work finished

Schedulechanges



MOMLevel 3


Scenario assumptions: 1. ERP sends production schedule to MOM for processing2. ERP cancels schedule before actual production starts, and sends CANCEL of schedule to MOM

Business Process Scenario #1cPUSH MODEL – Production Schedule Canceled

CANCEL – Production ScheduleSchedule invalidated


MOMLevel 3

Scenario assumptions: 1. MOM requests production schedule from ERP.2. ERP cancels schedule before actual production starts, and sends CANCEL of schedule to MOM.

Business Process Scenario #1cPULL and PUSH MODEL – Production Schedule Canceled

CANCEL – Production ScheduleSchedule invalidated



Business Process Scenario #1dPUSH MODEL – Daily Production Performance

ERPLevel 4

MOMLevel 3

Production TrackingPROCESS – Production Performance (May 24, 2005)

Scenario assumptions: 1. MES sends daily production performance to ERP2. Scope of production performance (which production lines, etc…) and timing of the publication (daily, weekly, time published) is not defined in a transaction message but is determined to in an out-of-band agreement.

PROCESS – Production Performance (May 25, 2005)

Business Process Scenario #2dPUBLISH/SUBSCRIBE MODEL – Daily Production Performance

ERPLevel 4

MOMLevel 3

SYNC ADD – Production Performance (May 24, 2005)

Scenario assumptions: 1. ERP subscribes to daily production performance from MOM 2. MOM publishes daily production performance3. Scope of production performance (which production lines, etc…) and timing of the publication (daily, weekly, time published) is not defined in a transaction message but is determined to in an out-of-band agreement.

SYNC ADD – Production Performance (May 25, 2005)

ERPLevel 4

MOMLevel 3

SHOW – Production Performance (May 24, 2005)

Scenario assumptions: 1. ERP requests production performance from MOM on a daily schedule

SHOW – Production Performance (May 25, 2005)

Business Process Scenario #3dPULL MODEL – Daily Production Performance

GET – Production Performance (May 24, 2005)

GET – Production Performance (May 25, 2005)


MOMLevel 3Execution



Scenario assumptions: 1. ERP requests production capability for the planning period2. MOM sends production capability to ERP3. ERP sends production schedule to MOM for processing4. MOM sends production performance to ERP reflecting partial order completion5. MOM sends production performance to ERP reflecting partial order completion6. MOM sends production performance to ERP reflecting completion of order


Business Process Scenario #1hPUSH/PULL MODEL – Production Schedule based on Production Capability


Some workcomplete

All work finished


GET – Production Capability

SHOW – Production Capability


MOMLevel 3Execution



Scenario assumptions: 1. ERP subscribes to production capability.2. MOM subscribes to production schedules. 3. MOM publishes production capability on a regular schedule, e.g. every 2 days,4. ERP generates a production schedule and publishes it. 5. MOM sends production performance to ERP reflecting partial order completion.6. MOM sends production performance to ERP reflecting partial order completion.7. MOM sends production performance to ERP reflecting completion of order.



Business Process Scenario #1hPUBLISH and PUSH MODEL – Production Schedule based on Production Capability


Some workcomplete

All work finished


SYNC ADD – Production Capability

ERPLevel 4

MOMLevel 3

Production Resource Management


PROCESS – Production Capability

Scenario assumptions: 1. ERP send production schedule to MOM for processing2. MOM sends updated production capability to ERP for processing 3. Scope of production capability (which production lines, etc…) and timing of the publication (daily, weekly, time published) is not defined in a transaction message but is determined to in an out-of-band agreement. 4. ERP changes schedule based on new capability and sends CHANGE to MOM

Business Process Scenario #1ePUSH MODEL – Production Schedule / Capability Changes

CHANGE – Production ScheduleSchedulechanges

ERPLevel 4

MOMLevel 3

Scenario assumptions: 1. Consumable material arrives at the facility and is entered into the ERP2. ERP send material lot information to MOM for processing3. MOM sends quantity changes in material lot to ERP as material is consumed4. ERP sends CANCEL when material lot is no longer available

Business Process Scenario #1fPUSH MODEL – Material Lot added, material lot quantity changed

New material lotis available

PROCESS – Material Lot (quantity = 400)

CHANGE – Material Lot (quantity = 300) Material lotquantity changed


CANCEL – Material Lot


Material lot nolonger available

ERPLevel 4

MOMLevel 3

Scenario assumptions: 1. ERP publishes material lot information, MOM subscribes2. MOM sends quantity changes in material lot to ERP 3. ERP send SYNC DELETE when material lot is no longer available

Business Process Scenario #1gMixed MODEL – Material Lot added, material lot quantity changed


SYNC ADD – Material Lot (quantity = 400)



SYNC DELETE – Material Lot


Material lot nolonger available


MOMLevel 3PROCESS – Production Schedule


Scenario assumptions: 1. ERP sends production schedule to MOM for processing2. MOM sends production performance to ERP for processing 3. ERP requests production capability from MOM4. MOM sends production capability to ERP5. ERP makes change to schedule and sends to MOM for processing6. MOM sends production performance to ERP reflecting partial order completion7. MOM sends production performance to ERP reflecting completion of order


New Business Process Scenario #1jPUSH/PULL MODEL – Production Schedule Changes using Production Capability as input

CHANGE – Production Schedule


Some workcomplete

All work finished

Schedulechanges


GET – Production Capability

SHOW – Production Capability

ERPLevel 4

MESLevel 3



Scenario assumptions: 1. ERP publishes production schedules, MES subscribes to changes2. MES publishes production responses, ERP subscribes to changes3. MES publishes SYNC ADD on first response and SYNC CHANGE on subsequent responses



Business Process Scenario #2aPUBLISH/SUBSCRIBE MODEL – Production Schedule / Production Performance


Some workcomplete

All work finished

More workcomplete

Scenario assumptions: 1. ERP publishes production schedules, MES subscribes to changes2. MES publishes production responses, ERP subscribes to changes3. ERP changes production schedule and sends changed production schedule using SYNC CHANGE to MES


Business Process Scenario #2bPUBLISH/SUBSCRIBE MODEL – Production Schedule Changes

ERPLevel 4

MESLevel 3






Some workcomplete

All work finished

Schedulechanges


Scenario assumptions: 1. ERP publishes production schedules, MES subscribes to changes2. ERP cancels the schedule before production starts and sends SYNC DELETE to MES

Business Process Scenario #2cPUBLISH/SUBSCRIBE MODEL – Production Schedule Canceled

ERPLevel 4

MESLevel 3


SYNC DELETE – Production ScheduleSchedulecanceled

ERPLevel 4

MESLevel 3


Scenario assumptions: 1. MES requests production schedule from ERP 2. ERP requests production performance from MES 3. ERP changes production schedule and returns changed schedule on next request

* Message would contain a flag to indicate that the message is the final production performance for the associated production schedule.

SHOW* – Production Performance

Business Process Scenario #3bGET/SHOW MODEL – Production Schedule Changes


GET – Production Performance

Some workcomplete

All work finished

Schedulechanges



ERPLevel 4

MOMLevel 3

Scenario assumptions: 1. MOM requests material lot information from ERP2. ERP sends information on new material lots (lots with no changes)3. MOM pushes quantity changes in material lot to ERP

Business Process Scenario #1gPUSH and PULL MODEL – Material Lot added, material lot quantity changed


SHOW – Material Lot (quantity = 400)




GET – Material Lot (ReceiptStatus = “New”)

Documents

Kpi Ml v01