Architecture

TIBCO Fulfillment Order Management is made of several components. Each component has a particular role.

The major components of TIBCO Fulfillment Order Management include:

  • Order Manager Server (OMS): OMS exposes SOAP Web services that can be used by external systems to submit orders to the Fulfillment Order Management.
  • Orchestrator: Orchestrator takes the order plan from AOPD and executes those tasks till completion. It invokes micro-level process plan fragments to initiate tasks within the operator's operations ecosystem, enabling appropriate actions in a variety of back-end systems (for example, billing systems, network systems, scheduling systems, and so on). Orchestrator keeps track of status and manages exceptions.
  • Automatic Order Plan Development (AOPD): Valid orders accepted by the OMS system are decomposed into their individual products, services, and resources. An optimized order plan workflow process is then generated based on those basic building blocks to ensure an accurate order fulfillment. Optimization can take into account both product rules, as well as customer inventory and other data to arrive at the final order plan.
  • Jeopardy Manager System (JeoMS) : The Jeopardy Management System is a key component of Fulfillment Order Management. Jeopardy management is the process of monitoring execution of a set of tasks in a plan to fulfill a customer order. In this application, execution plans are generated by decomposing orders based on the product model. Plans are orchestrated based on a schedule, and when a plan goes or predicted to go outside the expected design of the schedule, the system notifies the stakeholders as early as possible to take corrective steps.
  • Order Capture System (OCS): The Order Capture System is a web application component with a UI to create, manage, and submit TIBCO® Fulfillment Orchestration Suite (FOS) orders based on what a subscriber already has. With Order Capture System, you can select subscribers and browse validated products, services, or bundles from the TIBCO® Fulfillment Catalog (FC). OCS interacts with the runtime model server, which handles data, synchronizes it with all systems, and monitors the life cycle of the shopping cart.
  • Order and Pricing Engine (OPE): Offer and Price Engine is a part of the TIBCO Fulfillment Order Management engine that replaces the existing Offer Configuration and Validation (OCV) engine. The Order and Price Engine evaluates eligibility for products, validates the orders, and provides prices.

There are additional components, that are explained in more detail in TIBCO Fulfillment Order Management User's Guide. Here are few of those additional components:

  • Fulfillment Order Management User Interface (OMSUI): Provides operators a GUI to manage and track orders. Order Management System (OMS) persists order data and allows operators to search, view, track, and trace orders, as well as allows users to take actions on order/order lines.
  • Router: Orders from OMS may optionally be routed to an alternate Orchestration engine. In this case, Fulfillment Order Management Router can read inbound orders and, based on rules, may route to an external orchestration engine.
  • Common Logging: All Fulfillment Order Management components report to a common logging component for the ease of maintenance and operations management of the system.
Fulfillment Order Management Architecture