Incremental Repository Merge (IRM)

Siebel CRM 8.1.1.10/8.2.2.3 introduces a new tool, Incremental Repository Merge (IRM).

The incremental repository merge process streamlines previous processes such as the ACR import process and repository changes to provide a simple and highly effective way to import and reconcile repository changes.  Only changes since the last installed patch are imported, reducing the impact on customers of adopting both new repository fixes and features.  IRM allows easy identification and resolution of any merge conflicts in workflows and tasks which in turn can help reduce the risk of regressions being introduced.

IRM provides the following capabilities and benefits:

1. IRM simplifies the installation and deployment features of Oracle patches that provide new features in Siebel CRM; a Siebel Innovation Pack consists of products features (formerly known as ACRs). IRM provides an aggregated process of importing all new ACR’s at once 

a. Removes the need to individually import Siebel features released since the base release. 

b. Accelerates availability of Siebel features by removing the need for any additional repository changes one a patch has been put into place

c. Reduces the impact of integration and testing midstream in a deployed Siebel instance by collating and combining manual steps previously required into the core IRM process. 

d. Reduces the number of steps required to complete deployment, the amount of documentation needed to support these steps and the associated learning curve by combing all steps needed to update the repository into a single process.

2. IRM provides repository fixes in Siebel patches that improve quality improvements related to quick fixes that are provided as part of the patch or release.

a. Reduces testing overhead caused by needing to conservatively apply patches that may not apply to the deployed functionality.

b. Increases confidence that all patches related to specific deployed functionality are present.

3. IRM provides a new and formalized approach to generating and consuming specific repository archives; it is now possible to generate an archive of specific targeted object content into Siebel Delta Files (SDF).

a. Promotes Parallel Development of customer solutions, simplifying the integration of work from different sources

       Generated files contain only the changes are smaller and will merge into the target repository faster.Example: archiving a particular Business Component field property change as opposed to archiving the complete object.

b. Reduces integration testing load by highlighting areas of conflict and recommending actions.

4. IRM provides aggregated product features together that are already tested in the same consolidated format by Oracle

a. Removes the task of acceptance testing ACR combinations

b. Allows the testing of customer specific changes related to configuration to take priority, shortening overall time to deploy.

The mandatory IRM process concentrates more on incremental changes, simplifies the adoption of fixes and features, and allows customers to make more agile business decisions based on function rather than being driven by the technical demands of the legacy, more complex, patching effort.