The addition of a plan item to a service plan can in some instances result in the creation of a product delivery. Cúram Service Planning includes a number of interfaces designed to support integration between a plan item and a product delivery. There are several attributes of a plan item that have either a corresponding product delivery attribute or are related in some manner to particular aspects of product delivery functionality. The following table outlines these relationships.
| Plan Item Attribute | Comment |
|---|---|
| Expected Start Date | The plan item expected start date is used to set the value of the case header startDate and expectedStartDate attributes. The expected start date of a plan item can not be set once the plan item has moved into a status of In Progress. The status of a plan item that is associated with a product delivery is set to In Progress when the product delivery is activated. Any change to the start date of the case prior to case activation will update the plan item expected start date to the same value. However, after the case has been activated, an update to the case start date will update the plan item actual start date and not the expected start date. Any update to the plan item expected start date prior to case activation will update the case header expectedStartdate and startDate attributes. |
| Expected End Date | The plan item expected end date is used to set the value of the case header expectedEndDate attribute. Any change to the expected end date of the case, prior to case activation, will update the plan item end date and vice versa. However, on case activation the expected end date of both the case and the plan item may not be modified. |
| Actual Start Date | The actual start date of the plan item is set to the start date of the product delivery at the time the product delivery is activated (setting the actual start date of the plan item will change its status to In Progress). The actual start date of the plan item should not be set until the case has been activated and this must be the only means by which this value can be set. The user should not be able to directly enter or update the value for the plan item actual start date. If the case start date changes after the case has been activated, then the plan item actual start date must also be updated. |
| Actual End Date | The actual end date of the plan item is set to the value of the case header endDate attribute when the case is closed. The user should not be able to directly enter or update the value for the plan item actual end date; it may only be set as a result of the case being closed. If the case is reactivated the plan end date is cleared. |
| Actual Cost | The actual cost for a plan item associated with a product delivery is derived from the payments made via the product delivery in respect of the benefit or service given to the client. The value of the actualCost attribute is cleared when a case is reactivated. The actual cost should not be entered by the user. Note, whilst the estimated cost is displayed during product delivery creation, it is not stored on the product delivery case and is used solely to help the case worker select the appropriate product provision. |
| Expected Outcome | The plan item expected outcome is used to set the value of the case header expectedOutcome attribute. Any change to the expected outcome of the plan item will update the product deliveries expected outcome until the time at which the product delivery is activated. From this point onwards the expected outcome may not be modified. |
| Outcome | The plan item outcome may only be entered upon completion of the plan item. A plan item may only be completed when an actual end date has been recorded. Therefore, in the case of a plan item with an associated product delivery, the product delivery must be closed before the outcome may be set. After the product delivery has been closed, the outcome may be set on the product delivery which will update the plan item outcome or vice versa. |