Jeopardy Management

Note the following considerations for Jeopardy management:

Note:
  • When starting the Orchestrator services, an error is seen on configuration automation for Oracle.

    As a workaround, navigate to OMS > Advanced > Persistence from the Configurator UI and set the value of thecom.tibco.af.oms.databaseType flag as Oracle.

  • On the Order Management System UI Rule Config tab, when you click activity log, a scripting error is seen.
  • On the Order Management System UI Rule Config tab, when you add a new rule and select the notification type as Service, the new rule does not show in the Service Parameters tab dropdowns.
  • On the Order Management System UI Rule Config tab, when you add a new rule by setting aProtocol value as file and URL value as folder path, the rule does not get saved on Docker.
  • Jeopardy notifications are not received when you created a rule.
  • On the Order Management System UI Jeopardy dashboard, pagination is missing for the orders in jeopardy gadget.
  • On the Order Management System UI Rule Config tab, an error is seen when you try to update a rule.
  • On the Order Management System UI Rule Config tab, when you configure the notification as email, the email notification does not work.

The jeopardy management process involves three main activities:

  1. Monitoring the quality of service
  2. Reporting the Quality of Service
  3. Predicting the quality of service

The objectives of Jeopardy Management are as follows:

  1. Continuous collection of performance data and status information of all execution plans
  2. Detect SLA violation
  3. Predict Jeopardy Conditions for execution plan
  4. Perform consequential actions
    1. Send notification
    2. Invoke web service

The Jeopardy Management System enables you to manage the risk associated with plan tasks falling behind schedule, and to prevent them from jeopardizing the timely fulfillment of an order. The Jeopardy Management System is a key component of Order Management. Jeopardy management is the process of monitoring the 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 is predicted to go outside the expected design of the schedule then the system notifies the stakeholders as early as possible to take the corrective steps.

A plan is composed of a series of plan items. Each plan item has at least two milestones:

  • START milestone
  • END milestone

Plan items might also have intermediate milestones that represent points of interest during the execution of that plan item. Service-level agreement of service provider that runs plan items are specified through the process component model or plan fragment model, which stipulates among other things - the provided services performance. SLAs have a typical duration and a maximum allowed duration to fulfill a plan item.

To manage the risk associated with plan tasks falling behind schedule, the jeopardy manager performs the following risk-management tasks:

  1. Managing Critical Paths: Jeopardy management computes and keeps an account of critical paths through an execution plan. Two of these critical paths correspond to the typical and maximum durations of process components. The third type of critical path is based on the actual duration to date, once the execution plan has started processing. The critical paths are used to predict the completion date and time of the execution plan.
  2. Monitoring jeopardy conditions at each of the following levels:

    a. Plan Task

    b. Execution Plan

  3. Perform consequential actions at each of the following levels:

    a. Plan Task

    b. Execution Plan

    c. Milestone

The Order Management UI shows a dashboard for jeopardy management containing the following elements along with Orders Summary, Amended Orders, Backlog Orders, Orders in Execution:

  1. Orders in Jeopardy.
  2. Jeopardy Live Alerts.
  3. Jeopardy Recorded Alerts.