On the data interoperability issues in SCOR-based supply chains

On the data interoperability issues in SCOR-based supply

chains

Milan Zdravković, Miroslav TrajanovićLaboratory for Intelligent Production Systems

Faculty of Mechanical Engineering in Niš, University of Niš

7th International Workshop on Enterprise Integration, Interoperability and Networking (EI2N'2012), September 12-13, 2012, Rome, Italy

2

Objective

• Highlight data interoperability issues of SCOR and

• make these explicit,

• so two independent systems may communicate and interpret this information (interoperate).


3

What is a Supply Chain

SCOR Benchmarking - Presentation 3

Su

pplie

r pro

cess

es

Product Design

Custo

mer p

roce

sses

Supply Chain Management

Sales & Support

Product Management


4

Why is Supply Chain Management important for enterprises


5

What is expensive in Supply Chain Management


6

How the costs of Supply Chain Management are reduced


7

Supply Chain Operations Reference Model (SCOR) : Basic Management

ProcessesPlan-Source-Make-Deliver-Return

Supplier’sSupplier

Make DeliverSource Make DeliverMakeSourceDeliver SourceDeliverSource

Customer’s Customer

Plan

Supplier (Internal or External)

Your Company

Customer (Internal or External)

ReturnReturn ReturnReturn

ReturnReturn


8

..plus:

• Each of the processes has its own activities, metrics and best practices

• Each of the activities has inputs&outputs, metrics and best practices

• Each of the metrics has performance attributes• Each of the best practices is implemented by the

system


Plan


ReturnReturn


9

Why systems are good in communication


10

Why systems are bad in communication


11


12

SCOR-OWL Model


13

Why is interoperability important for Supply Chain Management

Supplier’sSupplier


Customer’s Customer

Plan

Supplier (Internal or External)

Your Company

Customer (Internal or External)


ReturnReturn

Interoperability issues


14

Assets flows between process elements for engineered-to-order

production type


15

Interoperability issues highlighted by using SCOR-OWL

• (isOutputFrom some (isProcessElementOf value S3_Source_Engineer-to-Order_Product)) and (isInputFor some (isProcessElementOf value M3_Engineer-to-Order)) or (isOutputFrom some (isProcessElementOf value S3_Source_Engineer-to-Order_Product)) and (isInputFor some (isProcessElementOf value D3_Deliver_Engineered-to-Order_Product))


16

Systems do not “speak” SCOR

business-rule(?x) return-process(?y) has-rule(?y, ?x) SameAs(?x, ∧ ∧ ⇒Business_Rules_For_Return_Processes)available-to-promise(?x) time-range(?y) has-quality(?x, ?y) SameAs (?∧ ∧ ⇒y, Available_to_Promise_Date)capability(?x) return-process(?y) has-quality(?y, ?x) SameAs (?x, ∧ ∧ ⇒Capabilities_of_the_Return_Processes)production-schedule(?x) SameAs (?x, ⇒ Production_Schedule)

SCOR-Full


18

Interoperability issues explicated by using SCOR-Full

• production-schedule– Superclasses

• function-schedule• schedules some production

– Inherited anonymous classes• has-realization some production-schedule-item• schedules some function

• production-schedule-item– Superclasses

• has-product-information exactly 1 product-information• has-production-end-date exactly 1 dateTime• has-production-start-date exactly 1 dateTime• information-item

On the data interoperability issues in SCOR-based supply chains

Milan Zdravković, Miroslav TrajanovićLaboratory for Intelligent Production Systems

Faculty of Mechanical Engineering in Niš, University of Niš

Thank you for your attentionQ&A

On the data interoperability issues in SCOR-based supply chains

Documents

Transcript of On the data interoperability issues in SCOR-based supply chains