Create and Release Products through Siebel EAI

Siebel has provided some vanilla business services which can be used to either create or update existing products in Siebel.

1. There is a "product Import" web service which can be readily used.This is based on the Business service "SWI Product Import".We can create a simple or complex product with this Business service.
2. To create a simple product, we can use the business service "Siebel Simple Product".
3. You can also use the Integration Object "Internal Simple Product Interface" with the "EAI Siebel Adapter" business service to insert products.

Apart from these 3 vanilla options, I have found creating a custom Integration Object to be very easy to create simple products in Siebel.

Steps to:

1. create an Integration Object on the Business Object -- "Admin ISS Product Definition" and select the parent Integration Component on Business component-- "Internal Product - ISS Admin". (This is the same BO and BC on which the Administration - Product Screen>Product Definitions view is based on).
2. "Name" is the only required field to be populated and is the one available in the Integration Component Key also.
3. Use the "EAI Siebel Adapter" Business service -- "Insert" method to insert the record.
4. This will create the Product record in the S_PROD_INT table and also the related version records in S_VOD and S_VOD_VER. (Without records in the version Table, we cannot use the product (or) lock (or) release it.)
5. To "Release" the product, we can use the "ISS Authoring Import Export Service" Business service and "ReleaseSingleObject" method.

Below is an Example workflow, which takes input as the <ProductName> and then creates and releases a simple product:

1. Create an Integration Object based on Business Object -- "Admin ISS Product Definition" and select the parent Integration Component on Business component-- "Internal Product - ISS Admin".
   
2. Inactivate the Integration Component Keys, except for the one which just has the "Name" Integration Component Key Field.
   
3. Inactivate the Integration Component User Properties -- "NoDelete", "NoInsert" and "NoUpdate"
   
4. Add a new Integration Object user Property "AdminMode" & value = "Y" and compile.
   
5. Create a Workflow Process with 2 process properties. 
1. vName -- to pass the Product name as input
2. vSiebelMessage -- based on the Integration Object to create the hierarchy.
   
6. Add 4 Business Service steps.
   
7. Step 1 is to create empty hierarchy based on the Integration Object.
1. Business Service: "PRM ANI Utility" and Method:"Create Empty Hierarchy"
2. Inputs:
1.  Hierarchy Name =  <Name of Integration Object>
   
3. Outputs: save the SiebelMessage in the process property
   
8. Step 2 is to set Property and populate the Product name.
1. Business Service: "PRM ANI Utility" and Method:"Set Property"
2. Inputs:
1. Hierarchy Path: --- IO.IC path
2. Property Name -- <Name of the field to set>
3. Property Value --- <Value of the property to be set>
4. SiebelMessage -- <input the siebel message where the changes are to be made>
   
3. Outputs: Save the modified SiebelMessage into a process property
   
9. Step 3 is to insert the Product record.
1. Business Service: "EAI Siebel Adapter" and Method: "Insert"
2. Inputs: Pass the Siebel message as input
   
3. Outputs: Capture the ROW_ID of the created record.
   
10. Step 4 is to release the Product.
1. Business Service: "ISS Authoring Import Export Service" and Method: "ReleaseSingleObject". This method will not be visible in the dropdown and has to be typed in literally.
2. Inputs:
1. RootObjectType --- ISS_PROD_DEF
2. RootObjectId --- <ROW_ID of the product to be released>
   

Importing Products using EIM

Importing Products using EIM:

· When the Products are imported using EIM they are imported into the S_PROD_INT table.

· These Products will be visible only on the “Administration – Products” screen and not in the “Products” screen.

· In order to make these products visible in the “Products” screen these Products records must have an association on the S_VOD and S_VOD_VER Table.

· Products imported through EIM are not directly associated to the S_VOD and S_VOD_VER tables since there is no EIM Counterpart defined.

Some theory (Oracle Support Web)

Doc ID 485530.1

The below query is a modified spool generated after querying on the “Products” applet on ‘Internal Products List view’.

SELECT

T1.NAME as Product

,T1.CFG_MODEL_ID

,T2.ROW_ID as 'S_VOD ROW_ID'

,T2.OBJECT_NUM

,T3.VOD_ID as 'S_ISS_OBJ_DEF VOD_ID'

,T3.PAR_VOD_ID as 'S_ISS_OBJ_DEF PAR_VOD_ID'

,T13.VOD_ID as 'S_VOD_VER VOD_ID'

,T13.RELEASED_FLG

FROM

dbo.S_PROD_INT T1

LEFT OUTER JOIN dbo.S_VOD T2 ON T1.CFG_MODEL_ID = T2.OBJECT_NUM

LEFT OUTER JOIN dbo.S_ISS_OBJ_DEF T3 ON T2.ROW_ID = T3.VOD_ID AND T3.LAST_VERS is notnull

LEFT OUTER JOIN dbo.S_VOD T4 ON T3.PAR_VOD_ID = T4.OBJECT_NUM AND T4.VOD_TYPE_CD ='ISS_CLASS_DEF'

LEFT OUTER JOIN dbo.S_VOD_VER T13 ON T2.ROW_ID = T13.VOD_ID AND T13.RELEASED_FLG = 'Y'

Result

· As you ca see in the above picture the Product ‘RG Product’ has RELEASED_FLG as NULL, this Product was created from the UI “Administration – Products” screen.

· Any Product created from the screen has to be released by that owner of the product, this can be done by clicking the “Release” button on the “Administration – Products” screen.(Usually Products information is added only by company administrators)

· Currently I am logged in as ‘SADMIN’ .You can see that the Release button is not active.

· When logged in with ‘GRYAN’ only then will the Release button be enabled.(as below)

      

· Once the Lock has been released an association is created on the S_VOD_VER table and the RELEASE_FLG is updated to ‘Y’.

Queries to check associations on the Siebel Data base:

1) Query to get all Products that are associated/ not associated to the S_VOD table.

select T1.NAME , T1.CFG_MODEL_ID, T2.OBJECT_NUM from S_PROD_INT T1

LEFT OUTER JOIN dbo.S_VOD T2 ON T1.CFG_MODEL_ID = T2.OBJECT_NUM

Result

For records that are not associated to the S_VOD table will have CFG_MODEL_ID and OBJECT_NUM asNULL

1) Query to get only those Products that are associated to the S_VOD table.

select T1.NAME , T1.CFG_MODEL_ID, T2.OBJECT_NUM from S_PROD_INT T1

LEFT OUTER JOIN dbo.S_VOD T2 ON T1.CFG_MODEL_ID = T2.OBJECT_NUM

where OBJECT_NUM is not null

After Importing Products using EIM:

· After Products are successfully imported using EIM the next step is to execute the Business Service

“ISS Authoring Import Export Service”, “Post_EIM_Upgrade” Method.

· You can execute the Business service using the Administration – Business Serviceà Simulator in the Site Map.

· Enter the following Input Arguments.

· Click the Run button.

· All the Products that had a broken association or no association with the S_VOD or S_VOD_VER table will not be associated.

· You can now see that all the Imported Products will be available on the “ProductsàInternal Products” screen.

· You can execute the above SQL’s to check the association made on the S_VOD and S_VOD_VER tables

Assignment Manager – An Overview

source from siebeloracle.com


Introduction of Assignment Manager :  Siebel Assignment Manager routes business entities and work items to the most appropriate candidates by enforcing business rules set by sales, service, and marketing organizations. Assignment Manager does this by matching candidates (that is, employees, positions, and organizations) to predefined and user-configurable assignment objects. To assign the most qualified candidate to each object, Assignment Manager applies assignment rules that you define to each candidate.
 Three major terms used in Assignment manager

1. Assignment Objects
2. Candidates
3. Criteria

Assignment Objects—the data that need to be assigned. Identify the types of data being assigned, such as accounts, opportunities, and service requests. An assignment rule may be used to assign one or more assignment objects
Candidates—the people, positions or organizations that will be assigned to that data. Assignment Manager assigns data to: Employee candidates, Position candidates, Organization candidates. An assignment rule may

• Contain a list of candidates who are assigned if the rule passes
• Match data to candidates based on their skills

Criteria—define which data will be assigned to which candidates. There can be multiple criteria per rule. Examples of criteria:

• Does the Position Type = Sales Person?
• Does the candidate have a skill with the product associated with this service request?

Below figure shows the entities in Siebel that are used in Assignment Rules

To define assignment rules, we need the following:

1. Objects to which each assignment rule applies
2. Rule groups to which each assignment rule belongs
3. Candidates.person (employee or position), organization, or both.for each assignment rule
4. Criteria for each assignment rule
5. (Optional) Values for assignment criteria 

For the Assignment rules we can also mention the below
Scores for each assignment rule, criteria, and value and a personal score for each individual candidate For example: In a sales organization, you can create an assignment rule that scores positions (candidates) based on territory definitions (criteria) for an opportunity (object).
We can also customize the way Assignment Manager makes assignments by:
1. Defining how attributes are matched by:

• Using different comparison methods
• Making criteria required (compulsory) or optional
• Using inclusion and exclusion methods
• Using workload distribution rules 

2. Defining how assignment rules are matched by using:

• Assignment rule groups
• Assignment rule sequencing 

3. Defining how candidates are assigned based on person and organization relationships using multitiered assignment.
4. Creating and configuring your own entities, including:

• Assignment objects
• Assignment criteria
• Assignment attributes
• Dynamic candidates and candidate teams that are assigned dynamically            depending on the object row assigned

5. Running Assignment Manager in different operating modes to process assignments:

• Interactively in real time
• Dynamically when object rows are created or attributes on object rows are changed by connected or mobile users for example as soon as a Service Request is created it gets assigned to a resource depending on the skills or workload etc.
• Periodically assigning objects in batches(Manually running the batch assignment to assign objects for example Accounts )

6. Checking availability before assigning employees to objects

EIM Load Sequence

The following is the sequence while loading data through EIM in Siebel CRM

1) Administrative data – LOV’s
 2) Responsibilities
3) Views
4) Organization
5) Position
6) Employee
 7) Address
 8) Account
9) Contacts
10) And now other related entities depending on the dependency of the entity but here also we load all the parent entities or reference entities for any child or referring entity.

Create Simple Products

The following steps covers Simple product creation:

Creating a Product Record 
You enter products into the Siebel system by creating product records. The product record contains the product name and important information about the product, such as its product line name or part number.
Once a product record is created, it cannot be deleted. To prevent a product record from being displayed in pick lists and dialog boxes, edit the product record to deselect the Orderable, Sales Product, and Service Product check boxes. You can also control display of the product by setting Effective Start and Effective End dates.
You add a new product record by clicking the new button. This creates the new product without releasing it, and locks the workspace.
 To create a product record 

• Navigate to the Administration – Product screen, then the Products view.
• In the Products list, add a new record and complete the necessary fields.

 Associating a Product with Price Lists

 Products are not visible to customers unless they are associated with price lists that are assigned to the customers.
To associate a product with a price list

• Navigate to the Administration – Product screen, then the Products view.
• In the Products list, select the desired product.
• Click the Pricing view tab.
• In the Price Lists list, add a new record and select the desired price list.
• Complete the remaining fields as needed.  

Setting Up User Access To a Product 

You must set up user access to allow the user to select a product for a quote or to see the product in a catalog.
The catalog administrator creates product catalogs, which contain product categories. The catalog administrator sets up access controls by assigning access groups to the catalog and to the categories.
The product administrator assigns products to catalogs and categories. You can assign a product to more than one category, and thus more than one catalog.
Until you assign a product to at least one category, the product does not display in the following places:

• On eSales Web pages. When customers buy your products through the Web, they cannot see the product.
• While browsing catalogs. When salespeople click the Browse Catalog button to view products in catalogs, they cannot see the product.

NOTE:  For products with components, you must give users access to the product with components and all its components. To accomplish this, first assign the product with components and its components to the same product category or to categories that have the same access groups. Then assign users who will configure the product to these access groups. If the users in the access groups differ across components, these users will not be able to configure the product with components correctly.
The recommended method for assigning users to access groups is to assign the users to organizations and then assign the organizations to the access groups.
To set up user access

• Navigate to the Administration – Product screen, then the Products view.
• In the Products list, select the desired product.
• Click the Category view tab.
• Add a new record to the Category list.

A dialog box appears that lists all the currently defined categories.

• Select a category from the dialog box.
• Add all the categories needed to give users visibility to this product.  

Releasing a Simple Product 

Though simple products do not have a Versions list, they are versioned objects. A new version was created when you created the product, and you must release this version to make the product visible to users.
To release a simple product

• Navigate to the Administration – Product screen, then the Products view.
• In the Products list, select the simple product.
• Click Release.

Create VBC Steps

1. Create a new BC based on the Class CSSBCVExtern.
2. Do not associate any tables to this BC since VBC are not based on an underlying table but rather is based on a Business Service.
3. Create the fields associated with VBC.
4. The field names must exactly match the name of the columns of the table that this VBC will reference.
5. Do not specify column or type for the fields.
6. Under the Business Component / Business Component User Property, create a new entry:
  a. Name: Service Name
  b. Value: AAA Test Business Service
  c. The Value can be any name that will use to create your new Business Service.
  d. "Name" must be "Service "Name".
7. Create a new Business Service with the same name that you used in the Business Component User Property above.
8. Create the various methods for your Business Service.
Some examples are:
  a. Delete, Init, Insert, Preinsert, Query, Update
  b. The minimum that you should have is Init and Query.
  c. Sample codes are given below.
9. Now define the Business Service Method Arg that goes with each of the Methods.
10. Associate your new VBC to a Business Object.
11. Create a new applet based on your VBC.
12. The example here is a list applet.
13. Add the VBC columns to the list applet.
14. Create a new view based on your new applet that is based on your VBC.
15. Associate the new View to a screen.
16. Don't forget to add the view to Application / Views in the application.
17. Also, add the view to an appropriate responsibility.

Siebel Implementation Process

Siebel Implementation Process example.  Please suggest any modifications if any.

1. Stage SPA00 - Plan and Activate
2. Stage SRP00 - Release Planning
3. Stage SRQ00 - Requirements Definition
4. Stage SFA00 - Functional Analysis & Design
5. Stage STA00 - Technical Analysis & Design
6. Stage SCF00 - Configuration
7. Stage SDM00 - Data Migration
8. Stage STS00 - Testing
9. Stage SDP00 - Deployment
10. Stage SUT00 - User Training
11. Stage SCE00 - Control and End

Stage SRQ00 - Requirements Definition

Step
Tasks
Output

Step 0100 - Acquaint Project Team with Business


Task 010 - Prepare Siebel Application Demo
Task 020 - Demo Siebel to Business Community
Siebel Business Requirements Document
Step 0200 -
Conduct Siebel
Awareness Sessions



Step 0300 -
Identify Siebel Business
and Reporting Requirements

Task 010 - Capture Business Requirements
Task 020 - Capture Reporting Requirements
Siebel Business Requirements Document
Step 0400 -
Define Organizational
Structures & Positions /Responsibilities


Step 0500 - Prioritize and Establish Baseline Requirements





Stage SFA00 - Functional Analysis & Design

Step
Tasks
Output

Step 0100 -
Create Business Object
Model
Task M00 - Milestone SFA M00 –
Functional Analysis & Design Started
Task 010 - Define Business Processes
Task 020 - Map Business Processes to Business Objects
Task 030 - Create Business Object Model
Task 040 - Validate Business Object Model
Task M01 - Milestone SFA M01-Business Object Model Complete
Siebel Business Object Model
Step 0200 -
Develop High Level
Screen Design
Task 010 - Define Business Transactions
Task 020 - Identify Screens
Task 030 - Map Business Transactions to Screens
Task 040 - Create Transaction Groups
High Level Screen Design
Step 0300 -
Identify Required Views,
Applets and Reports
Task 010 - Identify Views
Task 020 - Identify Applets
Task 030 - Identify Reports
Task 040 - Consolidate Gap Analyses
Task 050 - Create Views/Applets/Reports Reusability
Matrix
Task 060 - Define Navigation Between Views
Task 070 - Assign Siebel Visibility Classes
High Level Screen Design
Siebel Screen Visibility Checklist
Siebel Screen Design Checklist
Siebel Screen Data Elements
Views/Applets/Reports Cross Reference Matrix
Step 0400 -
Create Business
Component Model
Task 010 - Extract Business Components from Views and Applets
Task 020 - Extract Business Components from Business Objects
Siebel Business Component Model
Step 0500 -
Refine Business
Component Model
Task 010 - Map Conceptual Business Components to Standard Siebel Business Components
Task 020 - Specify Changes to Standard Siebel Business Components
Task 030 - Map Data Elements to Business Components
Siebel Business Component Model
Step 0600 -
Design Views,
Applets and
Reports
Task 010 - Design Screen Layouts (Applets and Views)
Task 020 - Design Report Layouts
Siebel Screen Visibility Checklist
Siebel Screen Design Checklist
Siebel Screen Data Elements
Applet Design Specification
Report Design Specification
Step 0700 - Create and Review Functional Specification
Task 010 - Document Changes to Tables, Business Components, UI
Task 020 - Document Functional Specification
Task 030 - Conduct Functional Design Review (Internal)
Task M02 - Milestone SFA M02 -Functional Analysis & Design Finished
Functional Specification



Technical Analysis & Design

Step
Tasks
Output

Step 0100 -
Define Technical Architecture



Step 0200 -
Perform Capacity
Planning
Task 010 - Assess Network Bandwidth Requirements
Task 020 - Determine Database
Sizing and Tuning Requirements
Capacity Planning Documentation
Step 0300 -
Conduct Siebel Technical
Reviews
Task 010 - Conduct CapacityPlanning Review
Task 020 - Conduct InfrastructureStrategy Review
Task 030 - Conduct Data MappingReview
Siebel Review Results
Step 0400 -
Document Design
Specification and Procure
Components
Task 010 - Document DesignSpecification
Task 020 - Initiate Procurement
Task M01 - Milestone STA M01 -
Technical Analysis & Design Finished
Design Specification



Stage SCF00 - Configuration

Step
Tasks
Output

Step 0100 -
Set Up Development Environment

Task M00 - Milestone SCFM00 -Configuration Started
Task 010 - Set up Network Connectivity
Task 020 - Set Up Siebel File System
Task 030 - Install Siebel GatewayServer
Task 040 - Install Siebel Servers and Enterprise Server
Task 050 - Install Siebel Database Server
Task 060 - Install Web Server
Task 070 - Install Third Party Software
Task 080 - Install Siebel Client
Task 090 - Install Siebel Tools
Task 100 - Set Up Configurators
Task 110 - Create Database Extract for Configurators
Task 120 - Initialize Local Database
Environment Setup
Step 0200 -
Initiate Configuration
Task 010 - Assign Functional Areas to Configurators
Task 020 - Analyze and Refine Projects
Configuration Guidelines
Step 0300 - Implement Database Extensions
Task 010 - Implement Extensions
Task 020 - Test Extensions
Task 030 - Apply Changes to Master Database
Task 040 - Create Local Database Extract
Task 050 - Reinitialize Local Databases
Physical Database Schema
Step 0400 - Set Up Static Data
Task 010 - Set Up Positions and Responsibilities
Task 020 - Set Up LOV's
List of Values
User Settings
Step 0500 - Customize Siebel Business Objects
Task 010 - Create/Modify Business Objects and Components
Task 020 - Validate Siebel Configuration
Siebel Local Database
Step 0600 - Customize Siebel Presentation Objects
Task 010 - Configure Presentation Objects
Task 020 - Unit Test Configuration Objects
Siebel Local Database
Step 0700 - Create Siebel VisualBasic Scripts
Task 010 - Create Siebel Visual Basic Scripts
Task 020 - Unit Test Siebel VB Scripts
Siebel Local database
Siebel Repository File
Step 0800 - Conduct Quality Review
Task 010 - Conduct Quality Review and Fix Problems
Task 010 - Conduct Configuration Review (Siebel)
Configured Application
Step 900 - Evaluate Release
Modification Requests
Task 010 - Capture User Feedback
Task 020 - Prepare Estimates for Changes
Task 030 - Review and Prioritize Changes
Task M01 - Milestone SCF M01-Release is Complete

Project Management Plan
Step 1000 - Prepare for Deployment
Task 010 - Develop Operations Manual
Task 020 - Prepare Rollout Plan
Task 030 - Conduct Production Readiness Review
Task M02 - Milestone SCF M02 –
Release is Production-Ready
Approved Deployment Package



Data Migration

Step
Tasks
Output

Step 0100 –
Determine Data Migration Strategy

Task M00 - Milestone SDM M00 -
Data Migration Started
Task 010 - Inventory Data Sources
Task 020 - Acquire External Data
Task 030 - Assess Data Integrity
Task 040 - Determine Automated vs.Manual Migration Approach
Task 050 - Determine TransitionApproach
Task 060 - Determine Migration
Backup and Recovery Strategy
Task 070 - Develop Migration Tests
Task 080 - Finalize Data Migration Plan
Data Migration Plan
Step 0200 –
Design Migration Process
Task 010 - Design Data MigrationRoutines
Task 020 - Verify Siebel InterfaceData Mapping
Task 030 - Design Manual Processes
Siebel Data Migration Script Manual Entry Procedures
Step 0300 –
Construct Migration Process

Task 010 - Build Data ExtractionRoutines
Task 020 - Write Data Load Scripts
Task 030 - Create Batch Processes
Data Extraction Routines
Data Load Scripts
Batch Processes
Step 0400 –
Test Migration Routines
Task 010 - Unit Test MigrationRoutines
Task 020 - IntegrateTest FullMigration Process
Tested Data Migration Process
Step 0500 –
Perform and Verify Data Load
Task 010 - Execute Data ExtractionRoutines
Task 020 - Execute Data LoadRoutines
Task 030 - Verify Data Load
Task 040 - Reconcile Automatic DataMigration Routines
Task 050 - Conduct Manual DataConversion
Task M01 - Milestone SDM M01 -Data Migration Finished
Data Load



Testing

Step
Tasks
Output

Step 0100 -
Set up Testing Environment
Task M00 - Milestone STS M00 -Testing Started
Task 010 - Set up Network Connectivity
Task 020 - Set Up Siebel File System
Task 030 - Install Siebel Gateway Server
Task 040 - Install Siebel Servers and
Enterprise Server
Task 050 - Install Siebel Database Server
Task 060 - Install Web Server
Task 070 - Install Third Party Software
Task 080 - Install Siebel Client
Task 090 - Set up Dialup Connectivity
Task 100 - Set up Internet Access

Step 0200 -
Prepare Testing Server
Task 010 - Build Testing Database
Task 020 - Confirm Data Migration
Task 030 - Set Up Users
Task 040 - Create Predefined Queries
Task 050 - Verify Positions and
Responsibilities
Task 060 - Verify LOV's
Task 070 - Define and Test Translations
Task 080 - Set Up Correspondence Templates
Task 090 - Establish Call Center Administration
Task 100 - Set Up Siebel Marketing
Encyclopedia
Task 110 - Create Database Extract for Remote Users

Step 0300 -
Develop Test Plans
Task 010 - Create User Acceptance
Test Plan & Cases
Task 020 - Create System Test Plan
Task 030 - Select and Procure Automated Testing Tool

Step 0400 -
Conduct Testing
Task 010 - Conduct User Acceptance Testing
Task 020 - Conduct System Performance Testing
Task M01 - Milestone STS M01-Testing Finished




Deployment

Step
Tasks
Output

Step 0100 -
Set Up Production Environment

Task M00 - Milestone SDP M00 -
Deployment Started
Task 010 - Set up NetworkConnectivity
Task 020 - Set Up Siebel File System
Task 030 - Install Siebel GatewayServer
Task 040 - Install Siebel Servers and Enterprise Server
Task 050 - Install Siebel DatabaseServer
Task 060 - Install Web Server
Task 070 - Install Third PartySoftware
Task 080 - Install Siebel Client
Task 090 - Set up Dialup Connectivity
Task 100 - Set up Internet Access
Environment Setup
Step 0200 -
Prepare Production Server

Task 010 - Build Database
Task 020 - Confirm Data Migration
Task 030 - Set Up Users
Task 040 - Create Predefined Queries
Task 050 - Verify Positions and Responsibilities
Task 060 - Verify LOV's
Task 070 - Define and TestTranslations
Task 080 - Set Up CorrespondenceTemplates
Task 090 - Establish Call Center Administration
Task 100 - Set Up Siebel Marketing
Encyclopedia
Task 110 - Create Database Extractfor Remote Users
Local Database Extract
Physical Database Schema
List of Values
User Settings
Queries
Translations
Correspondence Templates
Call Center Parameters
Populated Marketing Encyclopedia
Step 0300 -
Roll Out Release

Task 010 - Establish/Test ProductionSupport Infrastructure
Task 020 - Implement BackupProcedures
Task 030 - Deploy Application
Task 040 - Verify Connectivity toDatabase
Task M01 - Milestone SDP M01-Release Accepted
Deployed Release
Step 0400 -
Prepare for Next Release
Task 010 - Review Results of ReleaseRollout
Task 020 - Refine Release Strategy
Task M02 - Milestone SDP M02 -Next Release Go-Ahead
Project Management Plan