8 OSM Functional Overview

OSM Functional Diagram

Figure 8-1 shows a functional diagram of OSM.

Figure 8-1 shows the three primary stages in order management: create the order, generate and execute an orchestration plan, and run processes and tasks.

• To create an order, OSM receives an order as a web service operation from an order source system. When an order request is received, OSM performs order recognition to determine which type of order to create, based on the order specification. Transformation rules transform the order data into a format that can be used by OSM. See "How OSM Receives and Creates Orders."

  The order specification also defines the order lifecycle policy, which governs the states that the order can transition through. For more information, see "About the Order Lifecycle Policy."

• To generate and execute an orchestration plan, OSM derives order items from the order data, and decomposes the order items in order components, based on fulfillment patterns. See "How OSM Generates and Executes an Orchestration Plan" and "About Decomposition."

  The orchestration plan includes dependencies that determine the order in which processes can run. See "About Dependencies."

  When processing a customer order, OSM can use order item transformation to transform order items for products, bundles, and offers into order items for customer-facing services. See "About Order Item Transformation" and "About COM, SOM, and TOM."

• When running processes, OSM runs manual tasks and automated tasks. Manual tasks are managed by the Task web client. Automated tasks are run as plug-ins by the automation framework. Plug-ins use EXtensible Stylesheet Language Transformations (XSLT), XQuery scripts, and Java to communicate with external systems. See "About Tasks and Processes."

Figure 8-1 shows the areas in OSM that carry out functionality related to business processes such as changes to in-flight orders:

• Fulfillment states can manage states in orders and in order items.

• Predefined processing states can manage order item states. (Note that order item processing states do not go to the order level as fulfillment states do.)

• Order change management, such as using revision orders and compensation, is performed when processing tasks. Revising an order can also require a new orchestration plan.

• Internal order and task events throughout the order management process can create events that trigger notifications to order management personnel.

Figure 8-1 shows the interfaces used by the OSM functionality:

• CRM systems use JMS queues to send an order to OSM. HTML can be used in test and demonstration systems.

• You configure orchestration by using XQuery scripts to find, get, and transform data. You can also use XQuery scripts in processes.

• The Task web client and the Order Management web client communicate with the OSM server by using HTTP.

• The reporting interface uses SQL to retrieve data from the OSM database.

• OSM uses a variety of interfaces to connect to external systems, such as billing or shipping systems.