Managed Entity and Task Resource Models
Here is the state machine diagram for a product order. Each order states are described in the tab below.
The order item states are the same as the order ones. Note that the order and order item states are tightly linked and need to be consistent, for example :
- Order, state : InProgress
- Order item 1, state : InProgress (Valid)
- Order item 2, state : Pending (Valid)
- Order item 3, state : Held (Valid)
- Order item 4, state : Completed (Valid until there is another order item which is NOT completed)
- Order item 5, state : Cancelled (Not valid : if an order item is cancelled, maybe the whole order should be cancelled too)
The Acknowledged state is where an order has been received and has passed message and basic business validations.
The In Progress state is where an order has passed the Order Feasibility check successfully and service delivery has started.
The Cancelled state is where an In-Flight Order has been successfully cancelled.
The Completed state is where an order has complete provision and the service is now active.
The Rejected state is where:
The Pending state is used when an order is currently in a waiting stage for an action/activity to be completed before the order can progress further, pending order amend or cancel assessment. In situations where Access Seeker action is required, an "information required" notification will be issued on transition into this state.
The Held state is used when an order cannot be progressed due to an issue. SP has temporarily delayed completing an order to resolve an infrastructure shortfall to facilitate supply of order. Upon resolution of the issue, the order will continue to progress.
All Order items have failed which results in the entire Order has Failed.
Some Order items have failed and some have succeeded so the entire Order is in a Partial state. This provides support for partial Failure of an Order
Here under a product order composed of 4 order lines (orderItems) :
- Line "1" : Purchasing of a new simple product that needs a physical delivery place and an appointment to be delivered
- Line "2" : Modification of a characteristic value of an already owned product, and change the user associated to this Product
- Line "3" : Purchasing of a new simple product that needs (is supported by) another already owned product (in this case for example a new product that relies on the owned mobile access product to be installed)
- Line "4" : Purchasing of a bundled product composed of two atomic products
Field Descriptions :
BillingAccount: is the billingAccount to use to bill the ordered products
Unique identifier of the billing account
Reference of the billing account
Note: Extra-information about the order (e.g. useful to add extra delivery information that could be useful for a human process : a digicode access to a building, …).
Date of the note
Author of the note
Text of the note
Product Order: is a type of order which can be used to place an order between a customer and a service provider or between a service provider and a partner and vice versa.
Used to categorize the order from a business perspective that can be useful for the OM system (e.g. "enterprise", "residential", ...)
Date when the order was completed
Description of the product order
Expected delivery date amended by the provider
ID given by the consumer and only understandable by him (to facilitate his searches afterwards)
Hyperlink to access the order
ID created on repository side (OM system)
Contact attached to the order to send back information regarding this order
Date when the order was created
A way that can be used by consumers to prioritize orders in OM system (from 0 to 4 : 0 is the highest priority, and 4 the lowest)
Requested delivery date from the requestor perspective
Order start date wished by the requestor
State of the order : described in the state-machine diagram above
OrderItem: Order items that have to be treated
Identifier of the line item (generally it is a sequence number 01, 02, 03, …)
Can be "add" / "modify" / "no_change"/ "delete"
State of the order item : described in the state machine diagram
Used to precise that an appointment was set up with a related party for this order item
Place: Used to defined a place useful for the product (for example a delivery geographical place)
Reference of a place (for instance in google map)
Role of the place (for instance delivery geographical place)
Product: Configure the product characteristics (only configurable characteristics and necessary only if a non-default value is selected) and/or identify the product that needs to be modified/deleted.
May be a bundle product instantiation, in this case, it will contain the list of bundled product to instantiate
Nota: Each product to instantiate corresponds to a purchased productOffering. In case of bundles, the order of the list in the productOffering bundle must match the order of the list in the product instance bundle to deliver.
Identifier of the owned product (useful for delete or modify command)
Reference to the owned product (useful for delete or modify command)
ProductCharacteristic: Characteristics of the product to instantiate or to modify
Name of the characteristic
Value of the characteristic
ProductOffering: Ordered offering (pricing, default values, etc. are fetched by the OM directly from the catalogue). May be a bundle ProductOffering, in this case, it will contain the list of bundled offers that are ordered
Unique identifier of the product offering
Reference of the product offering
ProductRelationship: Linked products to the one instantiate.
Type of the product relationship. It can be :
RelatedParty: Defines parties which are involved in the order and the role they are playing. At product order level, it may be the customer and at the product level, it may be the user.
Unique identifier of related party
Reference of the relatedParty, could be a party reference or a partyRole reference
Role of the related party
Name of the related party
Notification Resource Models
Five notification types are defined :
Order Creation Notification
Used to notify that a new order has just been created.
Order Remove Notification
Used to notify that an order was deleted.
Order State change Notification
Used to notify that an order state is evolving.
Order Value Notification
Used to notify that any data in an order has just changed.
Order Information Required Notification
Used to notify that some data in the order needs to be filled / is missing.
- "resourcePath" allows to precise if it is a data at order level or at orderItem level (and which one of them) that is missing
- "fieldPath" details which field is missing, its structure is quite similar to GET filter criteria
- "missing=" points at the missing field
- "&<criteria>" can be used to identify a specific element in lists
Simple example : notification contact is missing
Complex example : in the order item "1", the IMEI characteristic value is missing to instantiate the product "465665"
© TM Forum 2015. All Rights Reserved.