Expected Outcome:

. Immediate Need: Copy IRS content from Dover URF ITT to Dover

. Feature Outcome: Ability to migrate full IRS set of content (including comments, attachments, status) from one project IRS to another project IRS.

Current Process:

During the life of a project "Issue Resolution Service" is used and issue records are created to manage various kinds of

information, including issues, clarifications and other [contractor] communications.

Shell wants these records to continue to exist in a cloned, as well as branched and subsequently merged project.

Use Cases:

a) General project branched to sub-contractor should retain the communications created in the general.

Problems:

a) There is no process or software capability for cloning IRS issues from one project/asset to another today.

b) IRS was not designed as a contractor communication tool

c) Even if there were, such an operation will automatically sever any links between the Issues and the iModel elements that they may reference.

Considerations:

The mechanism for cloning including B&M implies that the target context for the B&M operation already exist (was previously created). The clone, B&M process only forks the iModel. Other databases like IRS etc., are not automatically cloned today.

for more details, reference feature SDP4-54 & SR CS0377743

(attached PDF file & image snapshot for SDP4-54 image)