The General area is displayed at the top of the Summary tab. It includes a selection of important identifying and status information about the entity selected in the Order Info tree.

Table 4-1 describes the information displayed in the General area.

P[daysD][T[hoursH][minutesM][secondsS]]

order_id[total: number] 

The Order Items Processing State area is displayed below the General area. It contains information about each processing state for the order. Each row in the table in this area represents an order item state.

Table 4-2 describes the columns in the table in the Order Items Processing State area.

Table 4-3 describes the actual order item states that are indicated for each cell in the table. For more information about the meanings of the specific states, see the information about order item processing states in OSM Modeling Guide.

Some combinations of a state and Normal/Warning/Failure are not possible, and will never have values in the table in the Order Management web client.

The Dependencies area is displayed below the Order Items Processing State area. It contains information about entities on which the entities in the order depend.

More information about the dependencies for individual order components is available in the Order Component tab. See "Viewing Order Component Dependencies" for details.

Table 4-4 describes the information displayed in the Dependencies area.

You can search for specific characters or words in the data. For example, you could search for all occurrences of the text Broadband Modem. The search results are all of the data elements for the order that include the search text.

Search results are displayed in the Data tab. The total number of results is displayed near the Find field along with the sequential number of the data element you are currently viewing. Next and Previous buttons enable you to move between search results.

To search for data:

1. In the Data tab, enter text in the Find field.

2. Press the Enter key.

   The first matching data element is displayed. If the data element is a parent, the area displays all of its children. The area in the tab is renamed to correspond to this data. The total number of results is displayed near the Find field.

3. Click the Next button to see the next result.

   The next data element is displayed in the area.

Cartridge designers can create different data views to show or hide data based on business needs. These views determine what is displayed in the Data tab. If more than one view is available, you can switch between views.

To select a data view:

• In the Data tab, select a view from the View list.

  The data display changes to reflect the view you selected.

You can display the history of data elements in the Data tab. You can get history at any level in the data hierarchy. If you get the history for parent data, the history includes all children. If you get history for data with no children, you see information about only that data element.

Data history is shown in a dialog box that lists the activity for the selected data element and its children (if any). Information about each event (creation, update, or deletion) in the data's history is displayed.

To get data history:

• In the Data tab, click the Actions button for a line in the tree view and select Show Data History.

  The Data History dialog box is displayed.

Table 4-5 describes the information displayed in the Data History dialog box.

The Dependency Graph illustrates the dependencies among the order components in the order.

The graph shows all the executable order components (based on having passed through all orchestration stages) in the order. Arrows show dependencies between order components or order items. Each order component lists the order items it contains and colors differentiate order components based on the first orchestration stage. A legend illustrates the meaning of each color.

The order components with no dependencies are show on the left side of the graph. Execution of the orchestration plan starts with these order components. When these order components are completed, the dependencies on them are resolved. These resolutions allow the dependent order components, shown to the right of the first group, to be executed. The resolution of this next group of dependencies in turn frees other order components to be executed. This process continues until all order components are executed. The final order components to be executed are those on the right side of the graph.

Figure 4-2 shows a simple set of dependencies as displayed in the Dependency Graph. Order components are color coded based on the first orchestration stage. The component labels are based on the orchestration stages. In this case, there are three stages, so the labels have three parts. The first part of the label corresponds to the color coding: all order components of the same color share the same first label segment.

Order component labels have the following syntax:

DecompositionStage_1[DecompositionStage_2]...[DecompositionStage_n]

For example, if an order has three decomposition stages: function, system, and granularity, and an order component is labeled FulfillBillingFunction[BRM-REZDB][ServiceBundleGranularity], the function is FulfillBillingFunction, the fulfillment system is BRM-REZDB, and the granularity is ServiceBundleGranularity.

In Figure 4-2, there are three stages, so the labels have three parts. The first part of the label corresponds to the color coding: all order components of the same color share the same first label segment.

Figure 4-2 Dependency Graph

Description of "Figure 4-2 Dependency Graph"

An order component can be dependent on another order component both directly and indirectly (by being dependent on an order component that is itself dependent on another). For example, in Figure 4-2, order component E[1][y] is dependent on order component A[1][z] both directly and indirectly through order component D[2][z].

The Dependency Graph can display different detail levels:

• Component: At this level, the graph shows a single arrow for each dependency between one order component and another.

• Dependent Item: At this level, the graph shows arrows for each order item in an order component. The arrows point from dependent order item to the order item on which it depends.

To set the detail level:

• In the upper-left corner of a Dependency Graph, click the Component or Item button.

  The graph redisplays to show the detail level you selected.

The Decomposition Tree illustrates the orchestration stages into which an order is broken. Each order item in the order is shown in the order components into which it is grouped by the orchestration sequence.

The graph displays a series of areas for progressively more specific orchestration stages as you move from left to right in the image. The areas are labeled at the top with the name of the orchestration stage. The number of stages and their names depend on how the stages are defined for orders in Design Studio. See the Design Studio Help and OSM Concepts for more information about orchestration stages.

• On the left of the diagram, the first area displays a gray box listing all of the order items in the order. Above that box, a legend shows colors used to differentiate functions in the diagram.

• The next area to the right shows the results of the first orchestration stage. For example, if the first stage is DetermineFulfillmentFunctionStage, this area displays color-coded boxes into which order items are grouped into order components by function. The same order item is frequently included in more than one order component.

• The third area shows the next orchestration stage. For example, for a sequence where the next stage is DetermineFulfillmentSystemStage, this area shows order components with order items broken down by both function and fulfillment system. The color coding continues to differentiate functions.

• Additional areas correspond to additional orchestration stages. For example, for an orchestration sequence that includes a third and last stage called DetermineProcessingGranularityStage, the last area on the right displays executable order components that include function, fulfillment system, and granularity. This final column reflects the order components that you see in other areas of the Order Management web client, such as the tree view in the Order Items area and the Dependency Graph.

Because order components are generated for order items based on fulfillment patterns, the graph can show separate order components for order items that have the same orchestration stages. For example, there could be separate order components for order items that share the same function, fulfillment system, and processing granularity if the order items are mapped to different fulfillment patterns.

The following greatly simplified example illustrates how the decomposition tree displays the orchestration sequence for a particular order item in an order-to-activate solution.

In this example, the On Top of the World Broadband VoIP order item progresses through three orchestration stages: DetermineFulfillmentFunctionStage, DetermineFulfillmentSystemStage, and DetermineProcessingGranularityStage.

In the first stage, illustrated in Figure 4-3, the order item is decomposed into three functions.

Figure 4-3 Orchestration Stage 1

Description of "Figure 4-3 Orchestration Stage 1"

In the next stage, illustrated in Figure 4-4, each of these three functions is decomposed based on the fulfillment system. In this case, InitiateBillingFunction requires two fulfillment systems, while the other two functions require only one fulfillment system each.

Figure 4-4 Orchestration Stage 2

Description of "Figure 4-4 Orchestration Stage 2"

In the final stage, illustrated in Figure 4-5, each of the function-fulfillment system order components is decomposed into one fully qualified order component that includes the function, fulfillment system, and granularity level. In this case, each function-fulfillment system order component corresponds to a single executable order component.

Figure 4-5 Orchestration Stage 3

Description of "Figure 4-5 Orchestration Stage 3"

Both the Dependency Graph and Decomposition Tree include tools that enable you to view the information you need. You can see an enlarged version of each diagram, zoom in and out, and pan.

Most orders are complex, so their dependency graphs and decomposition trees must be reduced in size to fit in their areas on the Orchestration Plan tab. For greater legibility, you can open enlarged versions of the diagrams in separate windows that you can move and resize. You can also zoom and pan in these windows. See "Zooming In and Out" and "Panning" for more information.

• In the Dependency Graph or Decomposition Tree area of the Orchestration Plan tab, click the Enlarge button.

  A new window displaying the diagram is displayed.

Because of the complexity of orders, you often need to zoom in to see the detail you need. You can zoom using three methods:

• By using the Zoom In and Zoom Out buttons to zoom in or out on the center of the current view of the diagram.

• By using the Zoom button to zoom in on an area that you select.

To zoom in and out of the center of diagram:

• In a Dependency Graph or Decomposition Tree window, click the Zoom In or Zoom Out button in the toolbar.

  You zoom into or out of the center of the current view of the diagram.

To zoom into a particular area:

1. In a Dependency Graph or Decomposition Tree window, click the Zoom button in the toolbar.

   The cursor turns into a plus sign.

2. Drag out the area into which you want to zoom.

   The diagram zooms to the area you designated.

When you are zoomed into the diagram, not all areas are visible. You can pan to move to other areas.

To pan:

1. In a Dependency Graph or Decomposition Tree window, click the Pan button in the toolbar.

   The cursor turns into a hand symbol.

2. Click in the diagram, then drag it to move to the area you want to see.

To access the activity area, show it using the Restore Pane arrow button on the right side of the page. For more information, see "Collapsing, Expanding, and Resizing Areas with Collapse Pane and Restore Pane Buttons."

The Activity tab contains a table that displays a list of all activity events. Table 4-7 describes the information displayed.

You can see additional event details by expanding rows. See "About the Activity Event Details."

You can view additional information about an event by clicking the Expand button next to the row for the event. See "Getting More Information About Rows" for instructions on expanding rows.

The information displayed for a row depends on the event type. Table 4-8, Table 4-9, Table 4-10, Table 4-11, Table 4-12, and Table 4-13 describe the information displayed for the different types of events.

If a source order item is selected, this tab contains a table with information about order items to which the selected order item has been transformed.

Table 4-16 describes the information displayed in the Transformed Order Items area.

If a source order item is selected, this tab contains a table with information about order items from which the selected order item has been transformed.

Table 4-17 describes the information displayed in the Source Order Items area.

The Predecessors of This Order Item area lists entities on which the order item depends.

Table 4-18 describes the information displayed in the Predecessors of This Order Item area.

The Successors of This Order Item area lists entities that depend on order components on the selected order item.

Table 4-19 describes the information displayed in the Successors of This Order Item area.

Dependencies are relationships in which a condition related to one order component must be satisfied before the other order component can be completed. For example, a piece of equipment must be shipped to a location before it can be installed.

Dependencies are managed by OSM at the level of order components. All order items in one order component that are dependent on order items in another order component are grouped together into a single dependency. Only when the required conditions for all the order items involved in a dependency are satisfied is the dependency resolved.

Dependencies can be between order components in the same order (intra-order dependencies) or between order components in different orders (inter-order dependencies). Inter-order dependencies are particularly common in situations that involve amendments or follow-on orders.

Dependencies are configured in Design Studio and determined for an order when OSM generates its orchestration plan. See OSM Concepts and the Design Studio Help for more information about dependencies.

The Predecessors of this order component area lists entities on which the order component depends. (This is the same information that is displayed in the Dependencies area of the Summary tab.)

Table 4-22 describes the information displayed in the Predecessors of this order component area.

The Successors of this order component area lists entities that depend on the selected order component.

Table 4-23 describes the information displayed in the Successors of this order component area.