The document summarizes the Supply Chain Operations Reference model (SCOR) which provides a process reference model for supply chain management. The SCOR model defines five core processes - plan, source, make, deliver, and return. It describes the scope of these processes to include all interactions from a supplier's supplier to a customer's customer. The model is intended to help companies describe their supply chain processes, benchmark performance, and identify best practices to improve performance.
Operations Management II- SCOR is he world’s leading supply chain framework, linking business processes, performance metrics, practices and people skills into a unified structure.
The presentation justifies this tool used in one of the leading furniture brands 'Ikea' and implemented into their process flow.
Operations Management II- SCOR is he world’s leading supply chain framework, linking business processes, performance metrics, practices and people skills into a unified structure.
The presentation justifies this tool used in one of the leading furniture brands 'Ikea' and implemented into their process flow.
An unofficial and unauthorized overview of the SCOR Model from the first CTO of the Supply Chain Council. Why and how the SCOR model was constructed for supply chain management and how it was applied.
For current and official documentation please visit - www.supply-chain.org
(i) Cycle View (ii) Push & Pull View of the Supply Chain, Supply Chain Responsiveness. Strategic Fit between Business Strategy and Supply Chain Strategy, Achievement of Strategic Fit through different steps, Obstacles to achieving Strategic Fit.
A presentation on the Supply Chain Management as per Production and Marketing are concerns, the highly relayed branch of any business house is to concentrate on this particular topic.
The Supply-Chain Operations Reference-model (SCOR) is a process reference model that has been developed and endorsed by the Supply-Chain Council (non-profit consortium) as the cross-industry standard diagnostic tool for supply chain management. It is a proven methodology and tool that has been successfully applied and implemented in Fortune 500 firms.
Accompanying presentation for the free SCE Ltd. webinar highlighting a best-practice application of SCOR®, and summarizing the key steps to effectively utilize SCOR® in your company’s supply chain improvement initiatives.
We strongly urge attending the webinar (http://www.scelimited.com/education/free-scor-best-practice-case-study/) in order to get the most out of the presentation.
It is appropriate for anyone who is thinking about using the SCOR® framework, or those who are doing so and want exposure to additional expertise.
Topics covered:
+Principles of SCOR Application
+Metrics, Performance, and the Business Case
+Process and System – Work and Information
+Organizational Learning Plan
+Next Steps
An unofficial and unauthorized overview of the SCOR Model from the first CTO of the Supply Chain Council. Why and how the SCOR model was constructed for supply chain management and how it was applied.
For current and official documentation please visit - www.supply-chain.org
(i) Cycle View (ii) Push & Pull View of the Supply Chain, Supply Chain Responsiveness. Strategic Fit between Business Strategy and Supply Chain Strategy, Achievement of Strategic Fit through different steps, Obstacles to achieving Strategic Fit.
A presentation on the Supply Chain Management as per Production and Marketing are concerns, the highly relayed branch of any business house is to concentrate on this particular topic.
The Supply-Chain Operations Reference-model (SCOR) is a process reference model that has been developed and endorsed by the Supply-Chain Council (non-profit consortium) as the cross-industry standard diagnostic tool for supply chain management. It is a proven methodology and tool that has been successfully applied and implemented in Fortune 500 firms.
Accompanying presentation for the free SCE Ltd. webinar highlighting a best-practice application of SCOR®, and summarizing the key steps to effectively utilize SCOR® in your company’s supply chain improvement initiatives.
We strongly urge attending the webinar (http://www.scelimited.com/education/free-scor-best-practice-case-study/) in order to get the most out of the presentation.
It is appropriate for anyone who is thinking about using the SCOR® framework, or those who are doing so and want exposure to additional expertise.
Topics covered:
+Principles of SCOR Application
+Metrics, Performance, and the Business Case
+Process and System – Work and Information
+Organizational Learning Plan
+Next Steps
For informative discussions on software testing please see. http://forum.360logica.com/
Please see description below
360logica is an independent software and application testing services company which provides wide range of testing solutions to our partners based on domain, technology and business solutions including software product testing, quality assurance of software, automation in testing, finance testing, mobile software and applications testing. 360logica offers full range of software testing which include Software Product Testing, Test Automation, Performance Test Engineering, Finance Application Testing, Healthcare App Testing and SaaS Product Testing. We work closely with our partners to tailor a program of support which meets their needs and ensures our systems achieve the quality levels demanded by our partners, especially in financial testing
SCOR uma realidade em Logística. O modelo de pratica de negócio mais atualizado produzido de forma colaborativa por grandes empresas do mercado internacioal e organizado pelo SCC Supply Chain Council.
Adaptive software development processes epitomized by Agile methodologies are based on continual improvement – incremental changes that emerge as teams iterate and learn about the product they are developing. This appears to conflict with the world of the program office, responsible for defining the software development lifecycle (SDLC), in which a stable and repeatable development process with well-defined ownership and controls is a common objective. Using recent examples in which agile methods have been successfully introduced into large organizations with existing SDLCs, we consider the difficulties of creating a verifiable process when the process itself is continually being modified, and look at how software development can be managed and controlled without stifling the benefits of adaptive software development processes.
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
• The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
• Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
• Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
• Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
Generating a custom Ruby SDK for your web service or Rails API using Smithyg2nightmarescribd
Have you ever wanted a Ruby client API to communicate with your web service? Smithy is a protocol-agnostic language for defining services and SDKs. Smithy Ruby is an implementation of Smithy that generates a Ruby SDK using a Smithy model. In this talk, we will explore Smithy and Smithy Ruby to learn how to generate custom feature-rich SDKs that can communicate with any web service, such as a Rails JSON API.
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
Elevating Tactical DDD Patterns Through Object CalisthenicsDorra BARTAGUIZ
After immersing yourself in the blue book and its red counterpart, attending DDD-focused conferences, and applying tactical patterns, you're left with a crucial question: How do I ensure my design is effective? Tactical patterns within Domain-Driven Design (DDD) serve as guiding principles for creating clear and manageable domain models. However, achieving success with these patterns requires additional guidance. Interestingly, we've observed that a set of constraints initially designed for training purposes remarkably aligns with effective pattern implementation, offering a more ‘mechanical’ approach. Let's explore together how Object Calisthenics can elevate the design of your tactical DDD patterns, offering concrete help for those venturing into DDD for the first time!
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
3. What Is a Process
Reference Model?
Process reference models integrate the well-known concepts of business process
reengineering, benchmarking, and process measurement into a cross-functional
framework.
Business
Process Best Practices Process
Reengineering Benchmarking Analysis Reference Model
Capture the “as-is” Capture the “as-is” state of a
state of a process process and derive the desired
and derive the “to-be” future state
desired “to-be”
future state
Quantify the
operational
performance of
similar companies Quantify the operational
and establish performance of similar companies
internal targets and establish internal targets
based on based on “best-in-class” results
“best-in-class”
results
Characterize the
management
practices and
software solutions Characterize the
that result in management practices
“best-in-class” and software solutions
performance that result in “best-in-class”
performance
1
4. A Process Reference Model Contains:
• Standard descriptions of management processes
• A framework of relationships among the standard processes
• Standard metrics to measure process performance
• Management practices that produce best-in-class performance
• Standard alignment to features and functionality
Once a Complex Management
Process is Captured in Standard Process
Reference Model Form, It can Be:
• Implemented purposefully to achieve competitive advantage
• Described unambiguously and communicated
• Measured, managed, and controlled
• Tuned and re-tuned to a specific purpose
A Process Reference Model
Becomes a Powerful Tool in the Hands
of Management
2
5. The Boundaries of Any
Model Must Be Carefully Defined
“From your supplier’s supplier to your customer’s customer”
SCOR spans:
• All customer interactions, from order entry through paid invoice
• All product (physical material and service) transactions, from your supplier’s supplier to your
customer’s customer, including equipment, supplies, spare parts, bulk product, software, etc.
• All market interactions, from the understanding of aggregate demand to the fulfillment of
each order
SCOR does not attempt to describe every business process or activity, including:
• Sales and marketing (demand generation)
• Research and technology development
• Product development
• Some elements of post-delivery customer support
Links can be made to processes not included within the model’s scope, such as product development,
and some are noted in SCOR.
SCOR assumes but does not explicitly address:
• Training
• Quality
• Information Technology (IT)
• Administration (non SCM)
SCOR is Based on Five Distinct Management Processes
Plan
Plan Plan
Deliver Source Make Deliver Source Make Deliver Source Make Deliver Source
Return Return Return Return Return Return
Return Return
Suppliers’ Supplier Customer Customer’s
Supplier Your Company Customer
Internal or External Internal or External
3
6. Scope of SCOR Processes
Demand/Supply Planning and Management
Balance resources with requirements and establish/communicate plans for the whole supply chain,
including Return, and the execution processes of Source, Make, and Deliver.
Plan Management of business rules, supply chain performance, data collection, inventory, capital assets,
transportation, planning configuration, and regulatory requirements and compliance.
Align the supply chain unit plan with the financial plan.
Sourcing Stocked, Make-to-Order, and
Engineer-to-Order Product
Schedule deliveries; receive, verify, and transfer product; and authorize supplier payments.
Identify and select supply sources when not predetermined, as for engineer-to-order product.
Source Manage business rules, assess supplier performance, and maintain data.
Manage inventory, capital assets, incoming product, supplier network, import/export
requirements, and supplier agreements.
Make-to-Stock, Make-to-Order, and Engineer-to-Order
Production Execution
Schedule production activities, issue product, produce and test, package, stage product, and release
product to deliver.
Make Finalize engineering for engineer-to-order product.
Manage rules, performance, data, in-process products (WIP), equipment and facilities,
transportation, production network, and regulatory compliance for production.
Order, Warehouse, Transportation, and Installation
Management for Stocked, Make-to-Order, and
Engineer-to-Order Product
All order management steps from processing customer inquiries and quotes to routing
Deliver shipments and selecting carriers.
Warehouse management from receiving and picking product to load and ship product.
Receive and verify product at customer site and install, if necessary.
Invoicing customer.
Manage Deliver business rules, performance, information, finished product inventories,
capital assets, transportation, product life cycle, and import/export requirements.
Return of Raw Materials (to Supplier) and Receipt of Returns
of Finished Goods (from Customer), including Defective
Products, MRO Products, and Excess Products
All return defective product steps from authorizing return; scheduling product return; receiving,
Return verifying, and disposition of defective product; and return replacement or credit.
Return MRO product steps from authorizing and scheduling return, determining product condition,
transferring product, verifying product condition, disposition, and request return authorization.
Return excess product steps including identifying excess inventory, scheduling shipment, receiving
returns, approving request authorization, receiving excess product return in Source, verifying excess,
and recover and disposition of excess product.
Manage Return business rules, performance, data collection, return inventory, capital assets,
transportation, network configuration, and regulatory requirements and compliance.
4
7. A Process Reference
Model Differs from Classic
Process Decomposition Models
SCOR is a process reference model that provides a language for
communicating among supply-chain partners
Process decomposition models are developed to address
one specific configuration of process elements
Level Contains: Provide a balanced
horizontal (cross-process)
1 Process
and vertical (hierarchi-
Process Element cal) view
Process Element Designed to be
2 (re)configurable
Task
Task
3 Used to represent many
Activities different configurations
of a similar process
Activities
4
Aggregate a series of
hierarchical process
models
5
8. SCOR Contains
Three Levels of Process Detail
Level
# Description Schematic Comments
Plan Level 1 defines the scope and content
1 Top Level for the Supply Chain Operations
(Process Types) Source Make Deliver Reference-model. Here basis of
competition performance targets are set.
Supply-Chain Operations Reference-model
Return Return
A company’s supply chain can be
2 Configuration “configured-to-order” at Level 2 from 30
Level (Process core “process categories.” Companies
Categories) implement their operations strategy
through the configuration they choose
for their supply chain.
Level 3 defines a company’s ability to
3 Process Element compete successfully in its chosen mar-
Level kets, and consists of:
(Decompose
• Process element definitions
Processes)
• Process element information
inputs, and outputs
P1.1
Identify, Prioritize, and • Process performance metrics
Aggregate Supply-Chain
Requirements P1.3 P1.4 • Best practices, where applicable
Balance Production Establish and
P1.2
Resources with Supply-
Chain Requirements
Communicate
Supply-Chain Plans
• System capabilities required to
Identify, Assess, and
Aggregate Supply-Chain
support best practices
Resources
• Systems/tools
Companies “fine tune” their Operations
Strategy at Level 3.
Companies implement specific
4 Implementation supply-chain management practices at
Not Level this level. Level 4 defines practices to
in (Decompose achieve competitive advantage and to
Scope Process adapt to changing business conditions.
Elements)
6
9. Process Categories
Defined by the Relationship Between a SCOR Process and a Process Type
“SCOR Configuration Toolkit”
SCOR Process
Plan Source Make Deliver Return
Planning P1 P2 P3 P4 P5
Process Process
Type Execution S1- S3 M1- M3 D1 - D3 R1-R3 Category
Enable EP ES EM ED ER
Practitioners select appropriate process categories from the SCOR configuration toolkit to represent their
supply-chain configuration(s).
Level 1 Process Definitions
SCOR Is Based on Five Core Management Processes
SCOR Process Definitions
Processes that balance aggregate demand and supply to develop a course of
Plan action which best meets sourcing, production and delivery requirements
Processes that procure goods and services to meet planned or
Source actual demand
Processes that transform product to a finished state to meet planned or
Make actual demand
Processes that provide finished goods and services to meet planned or actual
Deliver demand, typically including order management, transportation management, and
distribution management
Return Processes associated with returning or receiving returned products for any reason.
These processes extend into post-delivery customer support
7
10. Level 1 Performance Metrics
Customer-Facing Internal-Facing
Performance Attribute Reliabilty Responsiveness Flexibility Cost Assets
Delivery performance
Fill Rate
Perfect order fulfillment
Order fulfillment lead time
Supply-chain response time
Production flexibility
Supply chain management cost
Cost of goods sold
Value-added productivity
Warranty cost or returns processing cost
Cash-to-cash cycle time
Inventory days of supply
Asset turns
At Level 2, Each SCOR Process Can Be Further
Described by Process Type
SCOR
Process Type Characteristics
Planning A process that aligns expected resources to meet expected demand requirements.
Planning processes:
• Balance aggregated demand and supply
• Consider consistent planning horizon
• (Generally) occur at regular, periodic intervals
• Can contribute to supply-chain response time
A process triggered by planned or actual demand that changes the state of material
Execution goods. Execution processes:
• Generally involve -
1. Scheduling/sequencing
2. Transforming product, and/or
3. Moving product to the next process
• Can contribute to the order fulfillment cycle time
Enable A process that prepares, maintains, or manages information or
relationships on which planning and execution processes rely
8
12. SCOR Level 3
Presents Detailed Process Element Information for Each
Level 2 Process Category
Process flow
S1 Source Stocked Product Inputs and outputs
Source of inputs
Output destination
Level 3 Example — S1 Source Stocked Product
• (P2.4) Sourcing Plans • (Supplier)
Inputs • (ES.2) Source Execution Data Sourced
• (ES.6) Logistics Selection Products
• (M1.1, M2.1, M3.2) Production Schedule
• (M1.2, M2.2, M3.3, D1.3) Replenishment Signals
S1.1 S1.2 S1.3
Process Schedule Receive Verify
Product Product Product
Elements Deliveries
• Procurement Signal (Supplier) • Receipt Verification • Receipt Verification
• Sourced Product on Order (ES.1, ES.2, ES.6, ES.8) (ES.1, ES.2)
Outputs (P2.2), (ES.9)
• Scheduled Receipts (M1.1, • (M) (D) Product Pull Signals
M2.1, M3.2, D1.8) • (ES.4) Product Inventory Location
• Material on Order • (EM) WIP Inventory Location • (ES.9) Payment
• (ED) Finished Goods Inventory Location Terms
S1.4 S1.5
Transfer Authorize
Product Supplier
Payment
• Inventory Availability (P2.2, ES.4,
M1.2, M2.2, M3.3, D1.8)
Inputs, outputs, and basic logic flow of process elements
are captured.
An Example of SCOR Level 3 Process Element Logic Flow
10
13. Examples:
SCOR Level 3 Standard Process
Element Definition, Performance Attributes and Accompanying Metrics
Process Element: Schedule Product Deliveries Process Number: S1.1
Process Element Definition
Scheduling and managing the execution of the individual deliveries of product against an existing contract or purchase order.
The requirements for product releases are determined based on the detailed sourcing plan or other types of product pull signals.
Performance Attributes Metric
Reliability % Schedules Generated within Supplier’s Lead Time
% Schedules Changed within Supplier’s Lead Time
Responsiveness Average Release Cycle of Changes
Flexibilty Average Days per Schedule Change
Average Days per Engineering Change
Cost Product Management and Planning Costs as a % of Product
Acquisitions Costs
Assets None Identified
SCOR Level 3 Best Practices and Features
Process Element: Schedule Product Deliveries Process Number: S1.1
Best Practices Features
Utilize EDI transactions to reduce cycle time and EDI interface for 830, 850, 856, and 862 transactions
costs
VMI agreements allow suppliers to manage Supplier managed inventories with scheduling interfaces
(replenish) inventory to external supplier systems
Mechanical (Kanban) pull signals are used to notify Electronic Kanban support
suppliers of the need to deliver product
Consignment agreements are used to reduce assets Consignment inventory management
and cycle time while increasing the availability of
critical items
Advanced ship notices allow for tight synchroniza- Blanket order support with scheduling interfaces to
tion between SOURCE and MAKE processes external supplier systems
11
14. Implementation of Supply-Chain Management Practices
within the Company Occurs at Level 4 (and below)
D1.7 D1.6 D1.5 D1.4 D1.3 D1.2 D1.1
Select Route Plan & Consolidate Reserve Receive, Process
Carriers Shipments Build Orders Inventory & Enter & Inquiry &
& Rate Loads Determine Validate Quote
Shipments Delivery
Date
Order D1
Deliver
D1.8 D1.9 D1.10 D1.11 D1.12 D1.13 Stocked
From Make
or Source
Receive
Product at
Pick
Product
Load Vehicle,
Generate
Receive &
Verify
Install
Product
Invoice
Product
Warehouse Ship Docs, Product at
Verify Credit Customer
& Ship Site
Process Element - D1.2 Tasks
Level 4
Receive Enter Check Validate
Order Order Credit Price
Below Level 3, each
process element is
Task - D1.2.3
Activities described by classic
Level 5 Access Credit
Screen
Check Credit
Availability
Clear Order
hierarchical process
Communicate
Contact Results to
Accounting Customer
decomposition
1. Contact customer account rep.
2. Look up customer history
Level 6 3. If necessary, account rep. calls
sales manager to authorize
additional credit
4a. Account rep. clears credit issue
4b. Account rep. refuses credit request
12
15. The Concept
of “Configurability”
A supply-chain configuration is driven by:
Plan levels of aggregation and information sources
Source locations and products
Make production sites and methods
Deliver channels, inventory deployment and products
Return locations and methods
SCOR must accurately reflect how a supply-chain’s configuration impacts
management processes and practices.
Each Basic Supply-Chain is a “Chain” of
Source, Make, and Deliver Execution Processes
Configurability
Plan Plan Plan Plan
Source Make Deliver
Customer and Supplier Customer and Supplier Customer and Supplier
Each intersection of two execution processes (Source-Make-Deliver) is a “link” in the supply chain
Execution processes transform or transport materials and/or products
Each process is a customer of the previous process and a supplier to the next
Planning processes manage these customer-supplier links
Planning processes thus “balance” the supply chain
Every link requires an occurrence of a plan process category
13
16. How SCOR Logic Supports Horizontal Process Integration
Return Plan
Delivery Plan
Production Plan
Sourcing Plan
Planning
Process
Type Plan Source Plan Make Plan Deliver Plan Return
Source, Make, Deliver
Respond to Order or Plan Signal
Execution
Process
Type Transform and Move Product
14
17. How SCOR Describes One SCM Trade-off
Make-to-Stock Configuration
Common SCM objective — achieve “market-winning” fulfillment time with the least inventory risk. Example: “pure”
make-to-stock configuration. Plan Deliver and Deliver activities are taken upon receipt of Customer Order.
Plan Source Plan Make Plan Deliver
Customer Order
Signal
Source Make Deliver
Delivered
Product
Common SCM objective — achieve “market-winning” fulfillment time with the least inventory risk.
Example: replenish-to-order Deliver network. Plan Deliver activities are already in place and ready to be
executed when Customer Order Signal is received.
Plan Source Plan Make Plan Deliver
Customer Order
Signal
Source Make Deliver
Delivered
Product
15
18. How SCOR Describes One SCM Trade-off
Make-to-Order Configuration
Common SCM objective — achieve “market-winning” fulfillment time with the least inventory risk. Example: make-
to-order configuration. Plan Make and Plan Deliver activities are already in place and ready to be executed when
Customer Order Signal is received.
Plan Source Plan Make Plan Deliver
Customer Order
Signal
Source Make Deliver
Delivered
Product
Common SCM objective — achieve “market-winning” fulfillment time with the least inventory risk. Example: make-
to-order configuration that extends through the Source process. All inter-enterprise planning functions are already in
place and ready to be executed when Customer Order Signal is received. This scheme requires some degree of
intra-enterprise P1 Planning. See page 23.
Plan Source Plan Make Plan Deliver
Customer Order
Signal
Source Make Deliver
Delivered
Product
16
19. Configuring
Supply-Chain Threads
Configuring a supply-chain “thread” illustrates how SCOR configurations are
done. Each thread can be used to describe, measure, and evaluate supply-chain
configurations.
1. Select the business entity to be modeled (geography, product set, organization)
2. Illustrate the physical locations of:
• Production facilities (Make)
Distribution activities (Deliver)
• Sourcing activities (Source)
3. Illustrate primary point-to-point material flows using “solid line” arrows
4. Place the most appropriate Level 2 execution process categories to describe activities at each location
Source Make Deliver
S1 Source Stocked Product M1 Make-to-Stock D1 Deliver Stocked Product
S2 Source Make-to-Order M2 Make-to-Order D2 Deliver Make-to-Order
Product Product
S3 Souce Engineer-to- M3 Engineer-to-Order D3 Deliver Engineer-to-
Order Product Order Product
Source Return Deliver Return
R1 Return Defective Product R1 Return Defective Product
R2 Return MRO Product R2 Return MRO Product
R3 Return Excess Product R3 Return Excess Product
17
20. Supply Chain Threads are Developed from the
Geographic Product Flow
Manufacturing Warehouse
(S1, D1)
(SR1, DR1, DR3)
(S1, S2
(S1) M1, D1)
(SR1, SR3) (SR1, SR3, DR3)
Warehouse
(S1, D1) European Supplier (S1)
(SR1, DR1, DR3) Warehouse (SR1, SR3)
(D2)
Latin American (S1, D1)
(DR1)
Suppliers (SR1, DR3)
Other Suppliers
(D1)
(D1)
Warehouse (S1)
(S1, D1) (SR1, SR3)
(SR1, DR1, DR3) (S1)
(SR1, SR3)
Consumers Production Site
Suppliers Return
Warehouse Execution Process
18
21. SCOR Process Maps are Used as a Basis for
Evaluating/Understanding the Supply Chain
P1
P1 P1 P1
P2 P3
P4
P3 P2
P4 P4
P2
European RM
Suppliers S2 M2 D2
Key Other
S1 M1 D1 S2 M1 D1 S1 D1 S1
RM Suppliers
S1
DR1 SR1 DR3 SR1 DR1 SR1
SR3 DR3 SR3
Raw Materials (RM) Suppliers ALPHA Alpha Regional Consumer
Warehouses
5. Describe each distinct supply-chain “thread”
• A supply-chain thread ties together the set of Source-Make-Deliver supply-chain processes that a given product
family flows through
• Develop each thread separately to understand common, and distinct, execution and return process categories
• Consider end-to-end threads in the inter-company case
6. Place planning process categories, using dashed lines to show links with execution processes
7. Place P1, if appropriate
• P1 - Plan Supply Chain aggregates outputs from P2, P3, and P4
19
22. In a Classic Logistics World
A change in a supply chain often “ripples” through each linkage, affecting other areas.
Plan Plan
Plan Plan
Plan Entity 6 Plan Plan
Entity 5 Entity 7
Entity 4 Make Entity 8
Source Deliver Entity 9
Deliver Source
Make
Change in Supply
(e.g. machine line breakdown)
The impact of a change can be felt both up and down the supply chain
A change in supply caused by a “production planner” may impact a “materials planner” and an “inventory
planner”
Further, such a change may impact both your customer’s and supplier’s supply-chain planning
Effective Supply-Chain Management
Requires Balancing Multiple Links Concurrently
P1 Plan Supply Chain
Develop plan that aligns
supply resources to
meet demand
Aggregate all Aggregate all
sources of supply sources of demand
Entity A Entity B Entity C Entity D Entity E Entity F
Deliver Source Make Deliver Source Make
20
23. SCOR Overview:
Summary
SCOR is a process reference model designed for effective communication
among supply-chain partners.
• A standard language helps management to focus on management issues
• As an industry standard, SCOR helps management focus across inter-company supply chains
SCOR is used to describe, measure and evaluate
Supply-Chain configurations
• Describe: Standard SCOR process definitions allow virtually any supply-chain to be configured.
• Measure: Standard SCOR metrics enable measurement and benchmarking of supply-chain
performance.
• Evaluate: Supply-chain configurations may be evaluated to support continuous improvement and
strategic planning.