CoST IDS mapping: Clarify mapping for completion elements

[duncandewhurst]

The completion section of the CoST IDS includes the projected or actual cost, date and scope at completion. These elements are mapped to the completion object in OC4IDS. However, according to its description, the completion object should only be populated with the actual final values, rather than the projected values.

CoST IDS element	CoST IDS draft definition	Mapping to OC4IDS
Project completion cost	State projected or actual completion cost (currency and amount)	Project Level: Publish in completion.finalValue
Completion date	State projected or actual completion date	Project Level: Publish in completion.endDate
Project Scope at completion (projected)	Indicate projected or actual scope of project. Aim is to show if the completed project scope differs from the original project scope. Specify main outputs (type, quantity, unit)	Project Level: Publish free text as completion.finalScope and/or include document with .documentType of projectScope and dates and descriptions that show this is final scope at completion

completion:

This information is provided at project completion, and reflects the final timing and values relating to the project. The reason for any variation (not already explained) between the anticipated project scope, period and value should be detailed.

It makes sense for the completion object to be restricted to the actual final values, otherwise its semantics would be conditional on the project's status.

We don't yet have a place to put projected completion costs and dates (see #322 and #140) but, in the meantime, we should update the mapping to make it clear that only the actual final values should be published in the completion object. Proposed changes in bold:

CoST IDS element	CoST IDS draft definition	Mapping to OC4IDS
Project completion cost	State projected or actual completion cost (currency and amount)	Project Level: Publish the actual completion cost in completion.finalValue. There's an open issue about how to publish the projected completion cost.
Completion date	State projected or actual completion date	Project Level: Publish the actual completion date in completion.endDate. There's an open issue about how to publish the projected completion date.
Project Scope at completion (projected)	Indicate projected or actual scope of project. Aim is to show if the completed project scope differs from the original project scope. Specify main outputs (type, quantity, unit)	Project Level: Publish the actual completion scope as free text as completion.finalScope and/or include a document with .documentType of 'projectScope' and dates and descriptions that show whether it is the projected or actual scope at completion.