1. Menu Introduction High-Level Functionalities SOM and SCM Flow
Slides 1 - 4
Introduction
High-Level Functionalities
SOM and SCM Flow
MOP/MPO-In
SOM (Orchestration)
SCM
SOM (SF)
SOM and SCM Flow Summary
Check Yourself
Review
Slide 5, pages 1-3
Slide 6, pages 1-5
Slide 8, pages 1-3
Slide 10, pages 1-4
Slide 11, pages 1-8
Slide 12, pages 1-3
Slide 13, pages 1-4
Production guidelines:
This slide presents the slides to go from the storyboard menu
Please pay attention that the slide numbers that I use are the numbers written on the slides (not the numbers on the PowerPoint slides)
Slide 14, pages 1-5
Slide pages 1-5
Slide 18

2. Functional Products SOM and SCM
Slide 1
Functional Products SOM and SCM
Service Management Overview
Production guidelines:
See template for animation, duration etc.

3. Slide 1, page 1
Service Management Overview
second
Eight

4. Slide 1, page 2

5. Slide 1, page 3

6. Slide 1 / page 4

7. Slide 1, page 5 25

8. Slide 1, page 6
Let’s begin!

9. Recap Slide 2 In previous units, you learned to:
Explain OSS terms at a high level.
Describe the business needs requiring the Service Management product.
Describe a typical scenario where Service Management comes into play.
Production guidelines:
See template for animation, duration etc.
Animation alternate automatically
Bullets entrance animation: “Fly In”> from left, duration: 0.75

10. Slide 3 ID NOTE: Place a comma here.
Describe the high-level functionality of the two Service Management (SM) main modules – Service Order Manager (SOM) and Service Composition Manager (SCM).
Production guidelines:
See template for animation, duration etc.
Animation alternate automatically
Number of the objective entrance animation: “Fade”, duration: 0.75
Objective entrance animation: “Fly In”> from left, duration: 0.75

11. Unit Content This unit includes the following topics:
Slide 4
Unit Content This unit includes the following topics:
High-Level Functionalities
SOM and SCM Flow
MOP/MPO-In
SOM (Orchestration)
SCM
SOM (SF)
SOM and SCM Flow Summary
Check Yourself
Production guidelines:
See template for animation, duration etc.
Animation alternate automatically
Bullets entrance animation: “Fly In”> from left, duration: 0.75

12. High-Level Functionalities
Slide 5
High-Level Functionalities
In this lesson, we will focus on SCM and on SOM and its two modules: Orchestration and Service Fulfillment (SF). Please click each product or module to learn more:
SOM
Orchestration
Service Fulfillment (SF)
ID NOTE:
Place a period here, remove colon.
SCM
Production guidelines:

13. High-Level Functionalities
Slide 5, page 1
High-Level Functionalities
In this lesson we will focus on SCM and on SOM and its two modules: Orchestration and Service Fulfillment (SF). Please click each product or module to learn more:
SOM
Orchestration
Service Fulfillment (SF)
SCM
Receives the order from BSS and sends it to SCM.
Production guidelines:
Show text box on clicking SOM box. Animate arrow as shown.

14. High-Level Functionalities
Slide 5, page 2
High-Level Functionalities
In this lesson we will focus on SCM and on SOM and its two modules: Orchestration and Service Fulfillment (SF). Please click each product or module to learn more:
SOM
Orchestration
Service Fulfillment (SF)
SCM
Decomposes the order into service orders and sends the service orders back to SOM Orchestration.
Production guidelines:
Show text box on clicking SCM box, animate arrow as shown.

15. High-Level Functionalities
Slide 5, page 3
High-Level Functionalities
In this lesson we will focus on SCM and on SOM and its two modules: Orchestration and Service Fulfillment (SF). Please click each product or module to learn more:
SOM
Orchestration
Service Fulfillment (SF)
SCM
Production guidelines:
Show text box on clicking respective boxes, animate arrow as shown.
Sends the service orders one by one to the SOM Service Fulfillment component.
Interacts with various downstream systems to fulfill the service.

16. SOM and SCM Flow Slide 6 SOM
The flow starts when an order is entered into BSS.
SOM
BSS
SOM (Orchestration)
SCM
SOM (SF)
Production guidelines:
Show text
Show diagram
This slide will advance automatically (5 seconds per page) – showing diagram steps, arrows and info as shown in slide 6/page 1-5

17. SOM and SCM Flow Slide 6, page 1 SOM
The flow starts when an order is entered into BSS.
SOM
Order image
MOP\MOP-In
BSS
SOM (Orchestration)
SCM
SOM (SF)
Production guidelines:
Insert an Order image – the image will automaticity fades in to the “BSS” rectangle shape.
BSS sends the order to SOM Orchestration using either the Manage Order Placement (MOP) or Manage Product Order (MPO-In) capability.

18. SOM Orchestration passes the order details to SCM.
Slide 6, page 2
SOM and SCM Flow
The flow starts when an order is entered into BSS.
SOM
BSS
SOM (Orchestration)
SCM
SOM (SF)
Production guidelines:
SOM Orchestration passes the order details to SCM.

19. SOM and SCM Flow Slide 6, page 3 SOM
The flow starts when an order is entered into BSS.
SOM
BSS
SOM (Orchestration)
SCM
SOM (SF)
Production guidelines:
SCM decomposes the products in the order to create a Service Plan, which includes service orders, and returns it to SOM Orchestration.

20. SOM and SCM Flow Slide 6, page 4 SOM
The flow starts when an order is entered into BSS.
SOM
BSS
SOM (Orchestration)
SCM
SOM (SF)
Production guidelines:
SOM Orchestration sends a message to SOM Service Fulfillment (SF) for each service order in the plan.

21. SOM (SF) fulfils the service orders by calling external OSS systems.
Slide 6, page 5
SOM and SCM Flow
The flow starts when an order is entered into BSS.
SOM
BSS
SOM (Orchestration)
SCM
SOM (SF)
Production guidelines:
SOM (SF) fulfils the service orders by calling external OSS systems.

22. What Have We Discussed So Far?
Slide 7
What Have We Discussed So Far?
High-Level Functionalities
SOM and SCM Flow
MOP/MPO-In
SOM (Orchestration)
SCM
SOM (SF)
SOM and SCM Flow Summary
Check Yourself
Production guidelines:
See template for animation, duration etc.
Animation alternate automatically
All topics appear on screen when user enter the screen
Topics that were covered are grayed out gradually

23. Manage Order Placement (MOP) / Manage Product Order (MPO-In)
Slide 8
MOP and MPO-In
The fulfillment flow starts when SOM Orchestration receives the MOP or MPO-In message from BSS.
Manage Order Placement (MOP) / Manage Product Order (MPO-In)
MOP and MPO-In define the functionality to place and manage a complex order.
MOP is a capability which is provided by the Service Management Orchestration module and used for backward compatibility.
MPO-In is used to place the order in the current version of Service Management.
Production guidelines:
In slide 9 we have 3 “sub-screen” appearing as radio-buttons – showing user‘s progress: Button no.1 – show slide 9
Button no.2 – show slide 9/page 1
Button no.3 – show slide 9/page 2
Clicking Next – go to slide 10. 1 2 3

24. P1, Cellular (Root Product)
Slide 8, page 1
MOP and MPO-In
An order can contain many requests; each request has one root product and an unlimited number of products in a hierarchy (see example below).
Please click the request to view the relevant information.
P1, Cellular (Root Product)
P3, DSL (Root Product)
P2, Internet (Product 1 )
P4, Broadband (Product 1 )
Request 1
Request 2
Request 1 contains a root product whose ID is P1 and type is Cellular. P1 has one child product whose ID is P2 and type is Internet.
Request 2 contains root product P3 whose type is DSL. P3 contains a child product whose ID is P4 and type is Broadband.
Production guidelines: show text and example (diagram in blue and green) shoe two buttons :
Clicking on “Request 1 ” – open text box “Request one contains a root ….”
Clicking on “Request 2 ” – open the text “Request two contains root product P3….”
Clicking Next – go to slide 10. 1 2 3

25. Click to learn about In-Flight orders
Slide 8, page 2
MOP and MPO-In
Portfolio Information Model (PIM)
PIM is a standard model that is used to represent a Product Order (PO) placed by a customer, and is integrated across Amdocs BSS and OSS systems. The PO hierarchy is governed by the product definitions in the Master Enterprise Catalog (MEC). Each PO must contain at least one Product Order Item (POI). Each POI must contain at least one Product Order Line (POL).
Please click the i button for additional information.
Order (PO)
Request (POI)
Root Product (POL)
Production guidelines:
Show text, example and button
Rolling over each “I” button will reveal text: PO “I” – “The order is known as the Product Order (PO), and each PO must have at least one Product Order Item (POI)”
POI “I” – “Each PO can contain one or more Product Order Items (POI), and each POI must have at least one Product Order Line (POL)”
POL Root Product “I” – “each POI can contain one or more Product Order Lines (POL), at least one of which should be a Root POL”
Clicking button “Click to learn about In-Flight orders” – open slide 9 / page 3 as pop-up.
Clicking Next – go to slide 10. 1 2 3
Click to learn about In-Flight orders

26. MOP and MPO-In Portfolio Information Model (PIM)
Slide 8, page 3
MOP and MPO-In Portfolio Information Model (PIM) X
In-Flight Orders
In-flight orders are changes made to the original order after it has been placed by the customer. (The new order and original order must have the same Order ID to be treated as an in-flight order.) Changes are allowed until the original order reaches its Point of No Return (PoNR), which is configurable in SOM. SOM Orchestration and SF share a sophisticated platform that deals with the incoming in-flight messages, and replaces the original order with the in-flight order for fulfillment.
PIM is a standard model that is integrated across Amdocs BSS and OSS systems. The model is used to represent a Product order (PO) placed by a customer. This hierarchy is governed by the Product definitions as available in the Master Enterprise Catalog (MEC). Each PO must have minimum one POI. Each POI must have minimum 1 POL.
Please roll over the i button. For additional information.
each POI can contains one or many Product Order Lines (POL) in which at least one should be Root Product Order Line.
each PO can contain one or many Product Order Items (POI). PO
POI
POL Root Product
Receive CREATE
Request
The Order is known as the Product Order (PO)
Production guidelines:
Closing pop-up – return to slide 9/page 2.
Receive AMEND
Request
Click to learn about In-Flight orders
Receive AMEND
Request

27. What Have We Discussed So Far?
Slide 9
What Have We Discussed So Far?
High-Level Functionalities
SOM and SCM Flow
MOP/MPO-In
SOM (Orchestration)
SCM
SOM (SF)
SOM and SCM Flow Summary
Check Yourself
Production guidelines:
See template for animation, duration etc.
Animation alternate automatically
All topics appear on screen when user enter the screen
Topics that were covered are grayed out gradually

28. SOM – Orchestration Internal and External Products Slide 10 1 2
Orchestration can handle orders for both internal and external products.
Internal products – Can be contained in MOP or MPO-In and decomposed into services by SCM.
External products – Can be contained only in MPO-In, and are defined in an external catalog and decomposed into services by an external SCM.
Production guidelines:
Show text and “SOM V9.2” button
Clicking “SOM V.9.2 Innovations ” open slide 10/ page 1 as pop-up.
Clicking Next – go to slide 11.
SOM V.9.2 Innovations 1 2

29. SOM – Orchestration Process Flows Slide 10, page 1 X Shared Equipment
SOM V.9.2 is enhanced in the following areas to support fulfillment and activation for multi- play services.
Process Flows
Orchestration supports two process flows:
Please click the flow to view the relevant information.
Shared Equipment
Outbound MSO/MRO (MxO)
OSS/J-based Activation
Solicited Flow –
includes MPO-In
Unsolicited Flow – does not include MPO-In
Data flow from USM
Supports transferring data directly from USM when SO from associated services is not physically created
Payload bundling
Supports transfer of data from subservice root service
Modify flow
BSS sends Modify order containing equipment with relevant referenced products
SOM is now able to call USM to fetch associated subservices
USM Compare in Orchestration
Business Rule Editor box added in MEC for USM Compare
Checks whether value of specific attribute from source or target service has changed
Product reference in BSS order
SOM is now able to use product references received in BSS orders
Production guidelines:
Shared Equipment “I” – show “Mainly required by residential customers, allowing one device at home serving multiple lines of business (for example, a single enhanced multimedia terminal adapter (eMTA) box that supports Internet and VoIP.”
Outbound MSO/MRO (MxO) “I” – show “Provides functionality for identifying, activating, or modifying relevant equipment for supporting:
•Ordered and installed services
•At a specific installation address”
OSS/J-based Activation “I” – show “Allows service providers to support equipment that can enable more than one line of business.”
When user closes the pop-up show a visited state to the buttons and return to slide 10
Clicking Next – go to slide 11. 1 2 3

30. Unsolicited Flow – does not include MPO-In
Slide 10, page 2
SOM – Orchestration
Process Flows
Orchestration supports two process flows:
Please click the flow below to view the relevant information.
Solicited Flow –
includes MPO-In
Unsolicited Flow – does not include MPO-In
Production guidelines:
Clicking “Solicited Flow” open slide 10/ page 3 as pop-up.
Clicking “Unsolicited Flow” open slide 10/ page 4 as pop-up.
Clicking Next – go to slide 11. 1 2

31. Unsolicited Flow – does not include MPO-In
Slide 10, page 3
SOM – Orchestration X
Process Flows
Orchestration supports two process flows:
Please click the flow to view the relevant information.
MxO request in response to MPO-In.
Solicited Flow –
includes MPO-In
Unsolicited Flow – does not include MPO-In
Production guidelines:
When user closes the pop-up show a visited state to the buttons and return to slide 10/page2
Clicking Next – go to slide 11. 1 2 3

32. Unsolicited Flow – does not include MPO-In
Slide 10, page 4
SOM – Orchestration X
Process Flows
Orchestration supports two process flows:
Please click the flow to view the relevant information.
No MPO-In. MxO request is sent independently.
Solicited Flow –
includes MPO-In
Unsolicited Flow – does not include MPO-In
Production guidelines:
When user closes the pop-up show a visited state to the buttons and return to slide 10/page2
Clicking Next – go to slide 11. 1 2 3

33. What Have We Discussed So Far?
High-Level Functionalities
SOM and SCM Flow
MOP/MPO-In
SOM (Orchestration)
SCM
SOM (SF)
SOM and SCM Flow Summary
Check Yourself
Production guidelines:
See template for animation, duration etc.
Animation alternate automatically
All topics appear on screen when user enter the screen
Topics that were covered are grayed out gradually

34. SCM SCM Functionality Slide 11 1 2 3 4
Service Composition Manager (SCM) encapsulates the product decomposition functionality. SCM translates a customer order into an optimized set of services to be fulfilled. The generated service plan is executed by Service Order Manager (SOM).
SCM’s metadata specifications and rules are stored in the Service Catalog.
CM Service Catalog (also known as the Service Modelling Catalog) is populated by the distribution process initiated from MEC. (The MEC course provides more details).
Production guidelines:
In slide 11 we have 4 “sub-screen” appearing as radio-buttons – showing user‘s progress: Button no.1 – show slide 11
Button no.2 – show slide 11/page 1
Button no.3 – show slide 11/page 2
Button no.3 – show slide 11/page 3
Show text
Clicking Next – go to slide 12. 1 2 3 4

35. SCM Process Flows Slide 11, page 1 1 2 3 4
SCM supports two process flows:
Run-Time Composition Engine – SCM receives an order from SOM and decomposes it into a set of service orders. This process is performed in three phases.
Design-Time Service Catalog – Definitions of products, services, and product-to-service decomposition, among others defined in MEC, are distributed to Service Modeling Catalog and used by the SCM Run-Time Composition Engine.
Production guidelines:
In slide 11 we have 4 “sub-screen” appearing as radio-buttons – showing user‘s progress:
Button no.1 – show slide 11
Button no.2 – show slide 11/page 1
Button no.3 – show slide 11/page 2
Button no.4 – show Slide 11, page 8
Show text
Clicking Next – go to slide 12. 1 2 3 4

36. Decomposition and Mapping
Slide 11, page 2
SCM
Run-Time Composition Engine Please click each phase to view the relevant information.
Order image
SCM
Decomposition and Mapping
USM Compare
NRM Compare
BSS
SOM (Orchestration)
add a pulsing glow around each phase to indicate to the learner which boxes are clickable
Production guidelines:
In slide 11 we have 4 “sub-screen” appearing as radio-buttons – showing user‘s progress:
Button no.1 – show slide 11
Button no.2 – show slide 11/page 1
Button no.3 – show slide 11/page 2
Button no.4 – show Slide 11, page 8
Show text
Clicking Next – go to slide 12.
clicking on “Decomposition and Mapping “ – show Slide 11, page 3
Clicking on “USM Compare” – show Slide 11, page 4
Clicking on “NRM Compare” – show Slide 11, page 6 1 2 3 4

37. Decomposition and Mapping
Slide 11, page 3
SCM
Run-Time Composition Engine Please click each phase to view the relevant information.
SCM
Decomposition and Mapping
USM Compare
NRM Compare
BSS
SOM (Orchestration)
Decomposition
Associations
Attribute Mapping
Decomposition to RFS
Production guidelines:
In slide 11 we have 4 “sub-screen” appearing as radio-buttons – showing user‘s progress: Button no.1 – show slide 11
Button no.2 – show slide 11/page 1
Button no.3 – show slide 11/page 2
Button no.3 – show slide 11/page 3
Show 4 boxes.
Rolling over Decomposition “I” – show text “Services out of the products in the MOP message.”
Rolling over Associations “I” – show text “Auto-instantiate service associations according to Service Catalog specifications.”
Rolling over Attribute Mapping “I” – Map attributes from the given MOP’s attributes to the decomposed services.”
Rolling over Decomposition to RFS “I” – show text “Decompose the order until end of resource-facing service (RFS) level.”
Clicking Next – go to slide 12. 1 2 3 4

38. Slide 11, page 4
SCM
Run-Time Composition Engine Please click each phase to view the relevant information.
SCM
Decomposition and Mapping
USM Compare
NRM Compare
BSS
SOM (Orchestration)
Compare against USM
Determine final service action
Production guidelines:
In slide 11 we have 4 “sub-screen” appearing as radio-buttons – showing user‘s progress: Button no.1 – show slide 11
Button no.2 – show slide 11/page 1
Button no.3 – show slide 11/page 2
Button no.3 – show slide 11/page 3
Show 2 boxes and button.
Rolling over Compare against USM “I” – show text “Compare the services on the service plan with USM to check their existence and configuration details.”
Rolling over Determine final service action “I” – show text “Determine service actions based on comparison rules defined in the Service Catalog.”
Clicking “V.9.2 Innovations ” – open a PDF
Clicking Next – go to slide 12.
USM Compare V.9.2 Innovations 1 2 3 4

39. Unsolicited Flow – does not include MPO-In
Slide 11, page 5
SOM – Orchestration X
SCM creates child phantom
Child phantom is part of USM query
Match from USM is found for a subservice and its parent, subservice action is changed
Child phantom is moved to be under its USM product
V.9
Process Flows
Orchestration supports two process flows:
Please click the flow to view the relevant information.
Child phantom is not created for subservice not decomposed from the order
Non-decomposed subservice is NOT a part of the USM query
Active USM subservice is merged in the service plan only if it has same product instance ID as its parent service
Match from USM is found for a subservice and its parent, subservice action is changed
If subservice is child phantom, it is removed from service plan
V.9.2
Solicited Flow –
includes MPO-In
Unsolicited Flow – does not include MPO-In
Production guidelines:
When user closes the pop-up show a visited state to the buttons and return to slide 10/page2
Clicking Next – go to slide 11. 1 2 3

40. Slide 11, page 6
SCM
Run-Time Composition Engine Please click each phase to view the relevant information.
SCM
Decomposition and Mapping
USM Compare
NRM Compare
BSS
SOM (Orchestration)
Check feasibility of RFS
Select TSS
Production guidelines:
In slide 11 we have 4 “sub-screen” appearing as radio-buttons – showing user‘s progress: Button no.1 – show slide 11
Button no.2 – show slide 11/page 1
Button no.3 – show slide 11/page 2
Button no.3 – show slide 11/page 3
Show 2 boxes and button.
Rolling over Check feasibility of RFS “I” – show text “Checking the services feasibility against a network resource management (NRM) system, such as Amdocs OSS Resource Manager.”
Rolling over Select TSS “I” – show text “Selecting the appropriate technology-specific service (TSS) based on selection rules defined in the Service Catalog.”
Clicking Next – go to slide 12.
Click to see an example 1 2 3 4

41. Slide 11, page 7 X
Every Product Order Line (POL) generates one or more Service Orders (SOs), every SO contains a Root Service Order Item (Root SOI), and in every Root SOI there can be a child Service Order Item (SOI).
Run Time Composition Engine Please click each phase to view the relevant information.
SCM decomposes each POL from the PO into one or more SOs. Each SO has one or more SOIs (per the Service Catalog definition), with at least one Root SOI.
SCM
PO received and passed from Orchestration to SCM.
Order image
Decomposition and Mapping
USM Compare
NRM Compare
BSS
SOM (Orchestration)
Product Order Line (POL1)
Service Order (SO1)
Root SOI– S1
Service Order (SO2)
Root SOI – S2
Service Order (SO3)
Root SOI - S3
Product Order Line (POL2)
Service Order (SO4)
Root SOI – S4
Service Order (SO5)
Root SOI – S5
SOI6
SOI7
1. Check feasibility of RFS – Checking the services feasibility against the Network Resource Management (NRM ) system, like the Amdocs OSS Resource Manager. 2. Select TSS – Selecting the appropriate Technology Specific Service (TSS) based on selection rules defined in the service catalog.
Production guidelines:
In slide 11 we have 4 “sub-screen” appearing as radio-buttons – showing user‘s progress: Button no.1 – show slide 11
Button no.2 – show slide 11/page 1
Button no.3 – show slide 11/page 2
Button no.3 – show slide 11/page 3
Show text, diagram and “I” buttons. Rolling over “I” show relevant text (in slide).
Clicking Next – go to slide 12.
Click to see an example 1 2 3 4

42. SCM Design-Time Service Catalog Slide 11, page 8 1 2 3 4
Key functions performed by SCM using the Service Catalog to predefine various rules and other metadata which are later used by the run-time three-phase flow:
Information in Service Catalog is created in and distributed from the Master Enterprise Catalog (MEC).
Service specification
Product specification (decomposition rules)
Attribute mapping rules
Service association rules
USM comparison rules
Technology selection rules
SID-aligned entities
Production guidelines:
In slide 11 we have 4 “sub-screen” appearing as radio-buttons – showing user‘s progress: Button no.1 – show slide 11
Button no.2 – show slide 11/page 1
Button no.3 – show slide 11/page 2
Button no.3 – show slide 11/page 3
Show text
Clicking Next – go to slide 12. 1 2 3 4

43. What Have We Discussed So Far?
High-Level Functionalities
SOM and SCM Flow
MOP/MPO-In
SOM (Orchestration)
SCM
SOM (SF)
SOM and SCM Flow Summary
Check Yourself
Review
Production guidelines:
See template for animation, duration etc.
Animation alternate automatically
All topics appear on screen when user enter the screen
Topics that were covered are grayed out gradually

44. Calculates Dependencies
Slide 12
SOM Orchestration
Process Flow Please click each phase to view the relevant information.
SOM Orchestration
Calculates Dependencies
Stores in DB
APM Process
SCM
add a pulsing glow around each phase to indicate to the learner which boxes are clickable
Production guidelines:
Show headers
Show diagram in this order: show the first blue box “SCM” – show arrow – show second blue box “SOM Orchestration” show three green boxes – one by one – in this order: 1. Calculates Dependencies
2. Stores in DB
3. APM Process
After the diagram – show instruction note “Please click each phase to view the relevant information.”
Clicking “Calculates Dependencies” – open Slide 12\page 1
Clicking “Stores in DB” – open Slide 12\page 2
Clicking “APM Process” – open 12\page 3
Clicking Next – go to slide 13.

45. Calculates Dependencies
Slide 12, page 1
SOM Orchestration
Process Flow Please click each phase to view the relevant information.
SOM Orchestration
Calculates Dependencies
Stores in DB
APM Process
SCM
Orchestration calls SCM to receive a service plan, then calculates dependencies between services in the service plan.
Production guidelines:
Clicking “Calculates Dependencies” – open Slide 12\page 1
Clicking “Stores in DB” – open Slide 12\page 2
Clicking “APM Process” – open 12\page 3
Clicking Next – go to slide 13.

46. Calculates Dependencies
Slide 12, page 2
SOM Orchestration
Process Flow Please click each phase to view the relevant information.
SOM Orchestration
Calculates Dependencies
Stores in DB
APM Process
SCM
Orchestration stores the MOP, service plan, and dependency details in the database.
Production guidelines:
Clicking “Calculates Dependencies” – open Slide 12\page 1
Clicking “Stores in DB” – open Slide 12\page 2
Clicking “APM Process” – open 12\page 3
Clicking Next – go to slide 13.

47. Calculates Dependencies
Slide 12, page 3
SOM Orchestration
Process Flow Please click each phase to view the relevant information.
SOM Orchestration
Calculates Dependencies
Stores in DB
APM Process
SCM
The Amdocs Process Manager (APM) is in charge of:
Sending MFOs to SF.
Sending KSU notifications to BSS.
Managing dependencies, customer project orders (CPOs), and in-flight orders.
Production guidelines:
Clicking “Calculates Dependencies” – open Slide 12\page 1
Clicking “Stores in DB” – open Slide 12\page 2
Clicking “APM Process” – open 12\page 3
Clicking Next – go to slide 13.

48. What Have We Discussed So Far?
High-Level Functionalities
SOM and SCM Flow
MOP/MPO-In
SOM (Orchestration)
SCM
SOM (SF)
SOM and SCM Flow Summary
Check Yourself
Production guidelines:
See template for animation, duration etc.
Animation alternate automatically
All topics appear on screen when user enter the screen
Topics that were covered are grayed out gradually

49. SOM Service Fulfillment
Slide 13
SOM Service Fulfillment
Process Flow Please click each phase to view the relevant information.
SOM Service Fulfillment (SF)
SOM Orchestration
Receives service order (MFO)
Calculates subservice dependencies
Stores subservice in DB
SF process
add a pulsing glow around each phase to indicate to the learner which boxes are clickable
Production guidelines:
Show text
Clicking Next – go to slide 11.

50. SOM Service Fulfillment
Slide 13, page 1
SOM Service Fulfillment
Process Flow Please click each phase to view the relevant information.
SOM Service Fulfillment (SF)
SOM Orchestration
Receives Service order (MFO)
Calculates subservice dependencies
Stores subservice in DB
SF process
The MFO capability defines the mechanism for creating and managing fulfillment orders in SM.
The process type is selected according to the SCM and Service Catalog specifications.
Production guidelines:
Show text
Clicking Next – go to slide 11.

51. SOM Service Fulfillment
Slide 13, page 2
SOM Service Fulfillment
Process Flow Please click each phase to view the relevant information.
SOM Service Fulfillment (SF)
SOM Orchestration
Receives service order (MFO)
Calculates subservice dependencies
Stores subservice in DB
SF process
SOM Service Fulfillment receive a service order, then calculates dependencies between subservices on the service order.
Production guidelines:
Show text
Clicking Next – go to slide 11.

52. SOM Service Fulfillment
Slide 13, page 3
SOM Service Fulfillment
Process Flow Please click each phase to view the relevant information.
SOM Service Fulfillment (SF)
SOM Orchestration
Receives service order (MFO)
Calculates subservice dependencies
Stores subservice in DB
SF process
SOM Service Fulfillment Stores subservice information in the database.
Production guidelines:
Show text
Clicking Next – go to slide 11.

53. SOM Service Fulfillment
Slide 13, page 4
SOM Service Fulfillment
Process Flow Please click each phase to view the relevant information.
SOM Service Fulfillment (SF)
SOM Orchestration
Receives service order (MFO)
Calculates subservice dependencies
Stores subservice in DB
SF process
Production guidelines:
Show text
Clicking Next – go to slide 14.

54. What Have We Discussed So Far?
High-Level Functionalities
SOM and SCM Flow
MOP/MPO-In
SOM (Orchestration)
SCM
SOM (SF)
SOM and SCM Flow Summary
Check Yourself
Production guidelines:
See template for animation, duration etc.
Animation alternate automatically
All topics appear on screen when user enter the screen
Topics that were covered are grayed out gradually

55. SOM and SCM Flow Summary
Slide 14, page 1
Instruction added
Please slide the slider to see the SOM and SCM flow.
MOP/MFO-In
SOM Orchestration
Order
BSS
SCM
Decomposition and Mapping
USM Compare
NRM Compare
Calculates dependencies
Stores in DB
APM Process
KUI DB
MFO
SOM Service Fulfillment (SF)
Production guidelines:
This is a slider slide with 5 stops.
Start slide at stop 1
Stop 1 – slide 14\page 1
Stop 2 – slide 14\page 2
Stop 3 – slide 14\page 3
Stop 4 – slide 14\page 4
Stop 5 – slide 14\page 5
Receives service order
Calculates subservice dependencies
Stores subservice in DB
SF process
KSU
BSS

56. SOM and SCM Flow Summary
Slide 14, page 2
MOP/MFO-IN
SOM Orchestration
Order
BSS
SCM
Decomposition and Mapping
USM Compare
NRM Compare
Calculates dependencies
Stores in DB
APM Process
KUI DB
MFO
SOM Service Fulfillment (SF)
Production guidelines:
This is a slider slide with 5 stops.
Start slide at stop 1
Stop 1 – slide 14\page 1
Stop 2 – slide 14\page 2
Stop 3 – slide 14\page 3
Stop 4 – slide 14\page 4
Stop 5 – slide 14\page 5
Receives service order
Calculates subservice dependencies
Stores subservice in DB
SF process
KSU
SOM (Orchestration)

57. SOM and SCM Flow Summary
Slide 14, page 3
MOP/MFO-IN
SOM Orchestration
Order
BSS
SCM
Decomposition and Mapping
USM Compare
NRM Compare
Calculates dependencies
Stores in DB
APM Process
KUI DB
MFO
SOM Service Fulfillment (SF)
Production guidelines:
This is a slider slide with 5 stops.
Start slide at stop 1
Stop 1 – slide 14\page 1
Stop 2 – slide 14\page 2
Stop 3 – slide 14\page 3
Stop 4 – slide 14\page 4
Stop 5 – slide 14\page 5
Receives service order
Calculates subservice dependencies
Stores subservice in DB
SF process
KSU
SCM

58. SOM and SCM Flow Summary
Slide 14, page 4
MOP/MFO-IN
SOM Orchestration
Order
BSS
SCM
Decomposition and Mapping
USM Compare
NRM Compare
Calculates dependencies
Stores in DB
APM Process
KUI DB
MFO
SOM Service Fulfillment (SF)
Production guidelines:
This is a slider slide with 5 stops.
Start slide at stop 1
Stop 1 – slide 14\page 1
Stop 2 – slide 14\page 2
Stop 3 – slide 14\page 3
Stop 4 – slide 14\page 4
Stop 5 – slide 14\page 5
Receives service order
Calculates subservice dependencies
Stores subservice in DB
SF process
KSU
SOM (Orchestration)

59. SOM and SCM Flow Summary
Slide 14, page 5
MOP/MFO-IN
SOM Orchestration
Order
BSS
SCM
Decomposition and Mapping
USM Compare
NRM Compare
Calculates dependencies
Stores in DB
APM Process
KUI DB
MFO
SOM Service Fulfillment (SF)
Production guidelines:
This is a slider slide with 5 stops.
Start slide at stop 1
Stop 1 – slide 14\page 1
Stop 2 – slide 14\page 2
Stop 3 – slide 14\page 3
Stop 4 – slide 14\page 4
Stop 5 – slide 14\page 5
Receives service order
Calculates subservice dependencies
Stores subservice in DB
SF process
KSU
SOM (SF)

60. What Have We Discussed So Far?
High-Level Functionalities
SOM and SCM Flow
MOP/MPO-In
SOM (Orchestration)
SCM
SOM (SF)
SOM and SCM Flow Summary
Check Yourself
Production guidelines:
See template for animation, duration etc.
Animation alternate automatically
All topics appear on screen when user enter the screen
Topics that were covered are grayed out gradually

61. Check Yourself | Question 1
Slide 15
Check Yourself | Question 1
What is the Service Management (SM) main two modules (SOM and SCM) flow?
Please arrange the steps of the SOM and SCM flow in the correct order.
BSS
SOM (Orchestration)
SCM
Production guidelines: Re-order
See template for animation, duration etc.
Allow 2 attempts in each question
Generic feedbacks:
Very Good
Try Again
Incorrect, note the correct answer
Reset to initial state when revisiting
SOM (Orchestration)
SOM (SF)

62. Check Yourself |Question 2
Slide 16
Check Yourself |Question 2
A customer project order starts when an order is received from BSS then sent to SOM and SCM, which creates a project order.
Please drag each entity to its correct box.
Customer Project Order 1
Project Order1
POI1
POL1
SO1
SOI1
POI1’
POL1’
SO1’
SOI1’
Project Order2
POI2
POL2
SO2
SOI2
POI2’
POL2’
SO2’
SOI2’
Received from MOP/MPO-In
Production guidelines: D&D
See template for animation, duration etc.
Allow 2 attempts in each question
Generic feedbacks:
Very Good
Try Again
Incorrect, note the correct answer
Reset to initial state when revisiting
Right answer in the next slid
Received from SCM

63. Customer Project Order 1
Slide 16, page 1
Customer Project Order 1
Project Order1
POI1
POL1
SO1
SOI1
POI1’
POL1’
SO1’
SOI1’
Project Order2
POI2
POL2
SO2
SOI2
POI2’
POL2’
SO2’
SOI2’

64. Check Yourself | Question 3
Slide 17
Check Yourself | Question 3
What are the SOM Orchestration stages? Please drag each stage to its correct place.
APM Process
Calculates Dependencies
Stores in DB
Template – slide with extension (please don't show as pop-up – show as extension)
Insert relevant icons for “Functionality” and “SOM and ”
Clicking “Functionality” – open Slide 15/page 1
Clicking “SOM and Router ” – open Slide 15/page 2-3
Show text and “I” icon – add relevant text.
Show question (this is a D&D question) – right answer in the next slide (Slide 15\page 3)
Allow 2 attempts in each question
user cant move forward – there is only a “submit” button.
Generic feedbacks:
Very Good!
Try Again
Incorrect
Reset to initial state when revisiting
When user click “next” show slide 16
SOM Orchestration

65. Check Yourself | Question 3
Slide 17, page 1
Check Yourself | Question 3
What are the SOM Orchestration stages? Please drag each stage to its correct place.
Template – slide with extension (please don't show as pop-up – show as extension)
Insert relevant icons for “Functionality” and “SOM and ”
Clicking “Functionality” – open Slide 15/page 1
Clicking “SOM and Router ” – open Slide 15/page 2-3
Show text and “I” icon – add relevant text.
Show question (this is a D&D question) – right answer in the next slide (Slide 15\page 3)
Allow 2 attempts in each question
user cant move forward – there is only a “submit” button.
Generic feedbacks:
Very Good!
Try Again
Incorrect
Reset to initial state when revisiting
When user click “next” show slide 16
SOM Orchestration
Calculates Dependencies
Stores in DB
APM Process

66. Check Yourself | Question 4
Slide 17, page 2
Check Yourself | Question 4
What are the SCM stages? Please drag each stage to its correct place.
Decomposition and Mapping
NRM Compare
USM Compare
Template – slide with extension (please don't show as pop-up – show as extension)
Insert relevant icons for “Functionality” and “SOM and ”
Clicking “Functionality” – open Slide 15/page 1
Clicking “SOM and Router ” – open Slide 15/page 2-3
Show text and “I” icon – add relevant text.
Show question (this is a D&D question) – right answer in the next slide (Slide 15\page 3)
Allow 2 attempts in each question
user cant move forward – there is only a “submit” button.
Generic feedbacks:
Very Good!
Try Again
Incorrect
Reset to initial state when revisiting
When user click “next” show slide 16
SCM

67. Check Yourself | Question 4
Slide 17, page 3
Check Yourself | Question 4
What are the SCM stages? Please drag each stage to its correct place.
Template – slide with extension (please don't show as pop-up – show as extension)
Insert relevant icons for “Functionality” and “SOM and ”
Clicking “Functionality” – open Slide 15/page 1
Clicking “SOM and Router ” – open Slide 15/page 2-3
Show text and “I” icon – add relevant text.
Show question (this is a D&D question) – right answer in the next slide (Slide 15\page 3)
Allow 2 attempts in each question
user cant move forward – there is only a “submit” button.
Generic feedbacks:
Very Good!
Try Again
Incorrect
Reset to initial state when revisiting
When user click “next” show slide 16
SCM
Decomposition and Mapping
USM Compare
NRM Compare

68. Check Yourself | Question 5
Slide 17, page 4
Check Yourself | Question 5
What are the SOM Service Fulfillment (SF) stages? Please drag each stage to its correct place.
Calculates subservice dependencies
Receives service order (MFO)
SF process
Stores subservice in DB
Template – slide with extension (please don't show as pop-up – show as extension)
Insert relevant icons for “Functionality” and “SOM and ”
Clicking “Functionality” – open Slide 15/page 1
Clicking “SOM and Router ” – open Slide 15/page 2-3
Show text and “I” icon – add relevant text.
Show question (this is a D&D question) – right answer in the next slide (Slide 15\page 3)
Allow 2 attempts in each question
user cant move forward – there is only a “submit” button.
Generic feedbacks:
Very Good!
Try Again
Incorrect
Reset to initial state when revisiting
When user click “next” show slide 16
SOM Service Fulfillment (SF)

69. Check Yourself | Question 5
Slide 17, page 5
Check Yourself | Question 5
What are the SOM Service Fulfillment (SF) stages? Please drag each stage to its correct place.
Template – slide with extension (please don't show as pop-up – show as extension)
Insert relevant icons for “Functionality” and “SOM and ”
Clicking “Functionality” – open Slide 15/page 1
Clicking “SOM and Router ” – open Slide 15/page 2-3
Show text and “I” icon – add relevant text.
Show question (this is a D&D question) – right answer in the next slide (Slide 15\page 3)
Allow 2 attempts in each question
user cant move forward – there is only a “submit” button.
Generic feedbacks:
Very Good!
Try Again
Incorrect
Reset to initial state when revisiting
When user click “next” show slide 16
SOM Service Fulfillment (SF)
Receives service order (MFO)
Calculates subservice dependencies
Stores subservice in DB
SF process

70. Review Slide 18 In this unit, you have learned to:
Describe the high-level functionality of the Service Management (SM) main two modules – Service Order Manager (SOM) and Service Composition Manager (SCM).
Production guidelines:
See template for animation, duration etc.
Animation alternate automatically
All objective appear on screen when user enter the screen
Objectives are greyed out gradually