Sunteți pe pagina 1din 51

Functional Specification Partner Integration & Productivity Environment (Code Name: PIPE 1.

0)
Created from xBUIT SDLC Template: Functional Specification v1.2

Filename: Revision: Last Save Date: Author(s): File Location: Read Only (public) Link:

e*BIS - PIPE Functional Specification.doc V3.0 Wednesday, June 06, 2012 e*BIS Team PIPE Sharepoint TBD

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

Table of Contents
1. Introduction......................................................................................................................................................4 2. Solution Overview............................................................................................................................................6 2.1. Scope.......................................................................................................................................................6 2.2. Out of Scope.............................................................................................................................................7 2.3. Assumptions, Constraints and Dependencies...........................................................................................8 2.4. Risks.........................................................................................................................................................9 High Level Conceptual Design......................................................................................................................11 2.4.1. e*BIS Integration Framework...............................................................................................................12 2.5. Checklist to Onboard a New Partner with PIPE.......................................................................................13 3. System Overview..........................................................................................................................................14 3.1. System Context & Architecture...............................................................................................................14 3.2. Data Flow...............................................................................................................................................16 3.3. Application Navigation.............................................................................................................................17 3.4. Supported Platforms ..............................................................................................................................17 4. System Features............................................................................................................................................18 4.1. Functional Area Opportunity Assignment & Notification .......................................................................19 4.1.1. User Role........................................................................................................................................19 4.1.2. Transaction Volumes.......................................................................................................................19 4.1.3. As-Is Solution..................................................................................................................................20 4.1.4. Business Scenario/Functional Process Flow....................................................................................20 4.1.5. Process Overview of Screens..........................................................................................................22 4.1.6. Business Rules................................................................................................................................22 4.1.7. Security and Privacy........................................................................................................................22 4.1.8. Regional Requirements...................................................................................................................22 4.1.9. Data Conversion..............................................................................................................................22 4.1.10. Reporting.......................................................................................................................................22 4.1.11. Error Handling...............................................................................................................................22 4.2. Functional Area Partner Status Notification..........................................................................................23 4.2.1. User Role........................................................................................................................................23 4.2.2. Transaction Volumes.......................................................................................................................23 4.2.3. As-Is Solution..................................................................................................................................23 4.2.4. Business Scenario/Functional Process Flow....................................................................................23 4.2.5. Process Overview of Screens..........................................................................................................26 4.2.6. Business Rules................................................................................................................................26 4.2.7. Security and Privacy........................................................................................................................26 4.2.8. Regional Requirements...................................................................................................................26 4.2.9. Data Conversion..............................................................................................................................26 4.2.10. Reporting.......................................................................................................................................26 4.2.11. Error Handling...............................................................................................................................26 4.3. Functional Area Opportunity Updates...................................................................................................27 4.3.1. User Role........................................................................................................................................27 4.3.2. Transaction Volumes.......................................................................................................................27 4.3.3. As-Is Solution..................................................................................................................................27 4.3.4. Business Scenario/Functional Process Flow....................................................................................27 4.3.5. Process Overview of Screens..........................................................................................................31 4.3.6. Business Rules................................................................................................................................31 4.3.7. Security and Privacy........................................................................................................................31 4.3.8. Regional Requirements...................................................................................................................31 4.3.9. Data Conversion..............................................................................................................................31 4.3.10. Reporting.......................................................................................................................................31 4.3.11. Error Handling...............................................................................................................................31
Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

3 of 51 4.4. Functional Area Customer Error Messaging.........................................................................................32 4.5. Requirements Control ............................................................................................................................33 5. Security, Privacy, Accessibility, & Disaster Recovery.....................................................................................44 5.1. Security...................................................................................................................................................44 5.2. Privacy....................................................................................................................................................45 5.3. Accessibility............................................................................................................................................45 5.4. Audit.......................................................................................................................................................46 5.5. Disaster Recovery/Business Continuance...............................................................................................46 Appendix A: Document Change History.............................................................................................................47 Appendix B: Review and Sign-off.......................................................................................................................48 Appendix C: Glossary/ Definitions......................................................................................................................49 Appendix D: Related Documents/References.....................................................................................................51

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

4 of 51

1. Introduction
Partner Integration & Productivity Environment (PIPE) is an integration and collaboration solution built to facilitate opportunity sharing and synchronization between Microsoft and its Partner systems. The overall goals and objectives of this phase is to define and develop the approach to seamlessly share opportunity information between MS Siebel and the Partners CRM systems, without having to re-enter opportunity data. Business benefits of integrating directly with a Partners CRM system for opportunity sharing include: Increases productivity for PAMs and Partners by eliminating double entry and streamlining manual work efforts Increased Partner satisfaction as it is easier to collaborate with Microsoft Increases visibility to Partners pipeline as more partner-generated opportunities will be in MS Siebel More accurate forecasts and improved data quality as Partner provide more timely updates of MS initiated opportunities Increased revenue potential from enhanced opportunity collaborations and efficiencies gained through the integrated solution with Microsoft Microsoft will map opportunity information to a public process that can be widely adopted throughout the partner community. Each integrated partner then has the ability to adopt the public process, and map the public processes and information to their own internal CRM systems and private processes. NOTE: The scope of this document is restricted to the Integration Layer (managed by e*BIS group). For further details on project objectives and functional context, please refer to the PIPE 1.0 Business Requirements Document The projects design phase was delivered via working JAD sessions (Technical process discovery, dependant applications, schema design etc). The document aims to capture the output/decisions made to support the overall design of the solution and underlying components. Figure 1a Overview of the Business Perspective of the Solution

y rtunit O ppo

Customer

O ppo

rt unit y

SMS&P EPG Microsoft Sales Reps

PIPE: Partner Integration & Productivity Environment


Collaborative Opportunity Management of Microsoft Initiated Opportunities between Microsoft and its Partner Community Business Process Field Taxonomy Data Transformation Routing Core Services

Partner Sales Reps

MS Siebel 4.2/4.3

Partner CRM System

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

5 of 51 Figure 1b Overview of the Business Perspective of the Solution


Sales/AM/PAM AM/PAM MS Siebel Integration Framework Partner Applications

Opportunity is Created

Partner Assignment

Partner Assigned

Send Partner Notification

Integration Server Executes Create Opportunity BIP

Opportunity Entered into Partner System


CRM

Opportunity Status Visibility

Update Opportunity Status to Partner

Accepted

Integration Server Executes Update Opportunity BIP

Partner Accepts Opportunity

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

6 of 51

2. Solution Overview
PIPE is built upon a scalable hub and spoke model. The PIPE Hub provides the transport, replication and processing of opportunities between the PSM Siebel and partner CRM systems. PIPE is the solution for reducing the amount of overhead associated with sharing opportunities as part of the PSM offering to the partner community. PIPE uses an industry standard interface for all transactions that adhere to a set of Microsoft derived taxonomy values and processes, and complete a procedure as part of the onboard process to the PIPE Opportunity Exchange. BizTalk Integration Layer is referred to as the HUB.

2.1.

Scope

The high level items listed here are considered in scope for this solution: Exchange of Opportunity Summary with trading partners Exchange of Partner Opportunity Status with trading partners Exchange of Full Opportunity messages with associated contacts, products, notes among trading partners Exchange of Opportunity Updates with trading partners Error handling / exception reporting Ability to disassociate/remove a partner from an opportunity Provision for re-assignment of an opportunity to a new partner Provide capability for the partner to reject / disengage from an assigned opportunity Authenticating participating trading partners Ability to assign an opportunity at the partner company level Ability to identify PIPE enabled partners within the Siebel UI Automatic new opportunity notification to partner upon assignment Ability to send opportunity summary to assigned primary partner Compliance to LCA requirements for Customer Contact Preferences Automatic update of Partner Status field based on assignment accept, reject, or removal Ability for partners to accept or reject an opportunity Ability to send opportunity full detail to assigned primary partner after acceptance Ability to remove a partner from an opportunity Ability for Partners to update an opportunity and have the updates automatically feed to Siebel Ability for PAMs to update an opportunity and have the updated automatically feed to the Partners CRM system Ability to re-assign an opportunity to a different partner (after rejection or removal) All partner owned processes and functionality within MSCRM Ability for the Partner to close opportunities and have the closure reflected in MS Siebel Ability for MS Siebel to close opportunities and have the closure reflected in the partner CRM system Ability to track partner closed by and last updated by (at the partner company level) Ability to assign an opportunity at the partner individual level SLA tracking Automatic notifications Customer Contact Preferences (PAM) Rejected opportunity notification (PAM) Missed SLA notification (PAM) Ability for a Partner to disengage post acceptance Ability to track reason disengaged code when a partner disengages an opportunity Ability to track reason rejected code when a partner rejects an opportunity
Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

7 of 51

Ability to track a close reason code when a partner closes an opportunity Ability to synchronize updates to an opportunity (partner or PAM) after close Ability to track partner closed by and last updated by (at the contact level)

2.2.

Out of Scope

The Out of Scope section identifies the requirements that will not be met by this project or release. This primarily is the identification of requirements (business, user, system, operational, usage scenario) that cannot be met as a part of the current phase. The out of scope list includes but not limited to those items found in the business requirements document (see Table 1). For a complete list of Requirements please refer to PIPE BRD & Siebel Functional Specification documents. Table 1 Requirements marked out of scope # 1 2 3 4 Requirement Opportunity Replication Partner Generated Opportunities Partner Level Individual assignment Reporting on PIPE Reason This solution will not provide the ability to publish or route the same opportunity to multiple trading partnering CRM systems simultaneously This solution will not provide the functionality to receive/process new opportunity messages published by partners This solution will not provide ability to assign opportunities to Partner Individual level This solution will not have provision to generate reports for Opportunities exchanged via PIPE. Generating operational metrics & reports for both successful and failed messages is currently not supported in this integration solution. Building interfaces for providing these details is also not defined to be a part of this solution. Exchange of Activities, Attachments is not supported Creating operational support tools for PIPE is not a part of the scope of this project phase PIPE does not support business processes pertaining to requests/fulfillments of Missing or Lost opportunity records. PIPE would not support bulk opportunity record processing.

5 6 7 8

Activities Support Tools Missing Opportunities Bulk Opportunities

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

8 of 51

2.3.

Assumptions, Constraints and Dependencies

Following are e*BIS specific list of assumptions, constraints and dependencies (Tables 2, 3 & 4). For a complete list of these please visit PIPE BRD & Siebel Functional Specification Documents. Table 2 Assumptions # 1 2 3 Assumption No dog-fooding allowed e*BIS personnel support Acknowledgements are generated only for fresh Opportunity Summary transactions Product Line and Product Validation Environment Support Publishing Opportunity Messages Administrative Co-ordination Description Only release product will be used in PIPE opportunity exchange Once PIPE is released to production it will be supported by e*BIS production support Business acknowledgement messages are generated only for fresh/new opportunity summary transactions. Similar acknowledgements for update transactions is deemed out of scope for this release Product Line Item and Product Family value validations are expected to happen only at MS Siebel and not in the integration layer Partners have completed PIPE / middleware tier development and testing to integrate with MS Siebel prior to the solution launch. Partners will allow Microsoft to push data into their respective system. Coordination between Siebel User Support and e*BIS Production Support will occur to determine at what point the Partner Account records need to be PIPE Enabled or Disabled. It will be necessary to mark all Partner Child Account Records for a given Partner Parent Organization with the PIPE Enabled flag as well as PIPE-ID. PIPE Enabling for a single backend gateway may even span across multiple Parent Organizations depending upon how Partner Accounts are grouped It is assumed that for PIPE to function, PIPE enabled partner seed data would be available in the integration layer database. No user interface for these activities on the integration layer, is assumed to be part of this project scope. Product, Account, Contact & Notes information is never manipulated in the integration layer. The snapshot received from Microsoft or Partner would be forwarded to the recipient system as is. It is assumed that all the three business flows, Opportunity Summary, Partner Status and Opportunity Updates would flow in the same sequence and that any other system hooked up to PIPE would not break or override this sequence The entries registered in the e*BIS integration server database would be cleared/deleted the moment a partner rejects or Disengages from the opportunity and likewise if Microsoft removes a partner from an opportunity. This would enable effective transaction management while processing re-assigned opportunities & preventing exchange of wrong opportunity update messages from the removed partners.

4 5 6 7

PIPE enabled Partner Seed Data Product, Account, Contact Notes Information in PIPE messages Message Flow

9 1 0 1 1

Data Cleansing

Table 3 Constraints # 1 Constraint Data Consistency Description Data consistency and data integrity issues exist across internal and externally integrated systems and shadow applications. Subsidiaries run the business from various systems with many silos between processes and systems

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

9 of 51

# 2 3 4

Constraint Solution Performance Solution Performance Software Technical Limitations

Description System performance may be degraded due to the additional volume of opportunities generated by the new user base. This may lead to decrease in user experience and lack of adoption Usage of digital certification process for authentication and encryption may degrade the overall transaction performance and through-put in association to the transaction volume Any and all of the PIPE software limitations have to be directed to the respective product team for resolutions or work-arounds e.g., BizTalk, BizTalk Accelerator etc.

Table 4 Dependencies # 1 2 3 4 Dependency Taxonomy Data Integrity Integration Platform Stability Validation of Product, Product Family, Contact, Account Description The PIPE integrated solution will depend on the existing integration between Siebel PSM application and the PSM Partner Portal for the taxonomy of Opportunity data and Partner information Data integration and integrity historically data integrity issues such-as partner originated data have prevented adoption and usage of standard systems Platform stability currently the platform to be used for the PIPE integrated solution requires a rigorous evaluation to analyze the stability and fit of Microsofts proprietary Integration Framework PIPE Integrated solution will depend on Siebel to validate Product, Product family, Account, Contact data. The current scope of the PIPE integration layer does not enable querying & validation of this data against Siebel.

2.4.

Risks

The following risks list includes but not limited to the following items found in the business requirements document (see Table 5).

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

10 of 51 Table 5 Risks # 1 Risk e*BIS Integration Framework Partner Requirements Performance Description The fact that the new concept e*BIS Integration Framework with its underlying Common Integration Data Model (CIDM) has not been completely evaluated. Unknown partner community requirements, in a broader perspective, is a concern. System performance may be degraded due to the additional volume of opportunities and activities generated by the new user base. This may lead to decrease in user experience and lack of adoption. PIPE enabled Partner who has access to view/modify the assigned Opportunities on PSM Portal would have conflicting impact on the overall solution. The message sequence (opportunity summary followed by Partner Status followed by Opportunity Update exchange) can be disrupted because of this overlap. The ongoing monthly Siebel Taxonomy changes, will disrupt PIPE solution by putting the Integration Layer and Partner System out of sync with the Siebel configuration. Risk Mitigation PIPE solution is standards based. Experience and the lessons learnt from the previous projects of using Siebel UAN product and other integration projects are put to use while designing this solution. The functional and technical teams from Microsoft and Partner are working closely to design this solution meet all the generic needs of the partner community. Fine-tuning software & hardware configuration to meet the performance requirements and evaluating performance of PIPE should minimize this impact. It is decided to prevent PIPE partners from accepting/declining/disengaging opportunities on PIPE Portal. (pending decision from the Siebel Technical team to determine the feasibility) For the enumerated fields maintained in the RosettaNet PIP schemas, the integration layer would have a provision to support two PIP versions while for the enumerated fields maintained as a part of the database, the changes would be absorbed once every six months and the same would be communicated to the partners. This work-around in addition to the efforts to prevent inflow of these changes would minimize the risk impact. The usage of document revision number and document generated date-time stamp will minimize this impact.

2 3

PSM PIPE overlap of functionality and its impact Siebel Taxonomy

Re-Queuing Failed Messages

Re-queuing failed-to-deliver messages, by respective PIPE administrators for Siebel or Partner or e*BIS, can cause old updates overwriting the newer data in the respective partner systems.

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

11 of 51

High Level Conceptual Design


The following diagram (Figure 2) highlights the various systems that can conceptually participate in this collaborative PIPE Opportunity Exchange System. MS Siebel is hosted on a customized version of Siebel acts as the master system. This is one of the many spoke systems that can communicate with the HUB hosted by a BizTalk server. The communication protocol between the hub and the various spoke systems is via secure and encrypted HTTP layer. The industry standard - RosettaNet Message Exchange Framework, is employed in exchanging messages with the trading partners. Next Section (section 2.5.1) provides an overview of the integration framework hosted by the Microsofts Hub. Figure 2 Conceptual Design
Partner CRM System

Partner CRM System

PSM Microsoft Siebel


Siebel Application

Outbound

Outbound

Hub
HTTP(s) EAI Transport Inbound BizTalk Server BTARN HTTP(s) RosettaNet Framework Inbound Internet Partner CRM System Partner CRM System

The backbone of the PIPE Opportunity Exchange solution is in the hub. Microsoft Integration Framework with CIDM components acts as the foundation layer which is extended and customized to develop this solution. The Hub receives or publishes messages to the trading partner CRM system, in PIP format a RosettaNet standard.

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

12 of 51

2.4.1.e*BIS Integration Framework


Figure 3 Overview of e*BIS Integration Framework
PSM / MS-Siebel INTEGRATION LAYER Microsoft e *BIS Integration Framework

Siebel Application Message

Source Adapter Flow Siebel Application Object Source Validation Flow Custom Error Message Object

Source Transformation Flow Microsoft CIDM Object Integration Flow RosettaNet PIP Object Target Transformation Flow

Target Adapter Flow

RosettaNet Message

Trading Partner Agreements

RosettaNet PIP Message Published to Trading Partner CRM System

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

13 of 51 The e*BIS Integration layer would host the Microsoft Integration Framework driven PIPE solution. This framework would utilize the Common Integration Data Model (CIDM) to generate message transformation and validation algorithms. As represented in the above diagram (Figure 3), hub - the Integration Server, hosts various components of the integration solution. These components are managed and administered by the BizTalk server software. Off these components, some of the important ones are the o adapter flows o transformation flows o validation flows o business flows Adapter flows enable exchange of application specific content with the trading partner systems (e.g., MSSiebel, Partner CRM Systems). Transformation flows enable translation of messages into various formats. This process would involve transformation of inbound application specific messages to an application agnostic CIDM message utilizing the Common Integration Data Model. These application agnostic common messages are massaged utilizing the various validation rules and business rules laid out in the business flows. Once these check-points are executed the target transformation flow would transform the CIDM message to the target application specific format which is then published out to the target system via the target adapter flow. As a part of this solution, the message exchange with the target trading partnering systems is enforced to be compliant with RosettaNet standards. To implement this, custom PIP schemas would be built and utilized as message templates. The hub would utilize the BizTalk Accelerator for RosettaNet to create Trading partner agreements and PIP configurations.

2.5.

Checklist to Onboard a New Partner with PIPE

The following check-list is concise, limited and specific to e*BIS integration layer. Following is the list of components needed for partner preparation to onboard PIPE. - Functional and, business requirements documents - Public process related RosettaNet PIP definitions and configuration details - List of enumerated fields and standard values to be used during message exchange - PSM, e*BIS inputs, guidelines and standards to be followed including the security standards Following is the list of activities that should happen, once the partner is technically ready to onboard PIPE. - Register the new partner and generate partner specific trading partner agreements using BTARN on Microsoft Integration server - Exchange security and communication related details like IP, URLs etc with the partner, once the partner is ready for message exchange - Execute smoke-tests and sample message exchange dry runs to ensure configuration integrity - Identify Partner administrator who would closely work on PIPE related technical issues - Identify Partner PAM and User support team to handle the business messages and calls and to closely work with Microsoft PAM and PIPE functional users - Ensure that Siebel PSM application has PIPE enabled the new partner - Populate the partner seed-data table on the Microsofts PIPE integration server database, with the new partner information to enable message exchange. The PIPE solution team will be responsible for compiling a Partner onboarding (configuration/deployment) document.
Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

14 of 51

3. System Overview
PIPE is built upon a scalable hub and spoke model. The PIPE Hub provides the transport, replication and processing of opportunities between the PSM Siebel and partner CRM systems. PIPE is the solution for reducing the amount of overhead associated with sharing opportunities as part of the PSM offering to the partner community. PIPE uses an industry standard interface for all transactions that adhere to a set of Microsoft derived taxonomy values and processes, and complete a procedure as part of the onboard process to the PIPE Opportunity Exchange. BizTalk Integration Layer is referred to as the HUB.

3.1.

System Context & Architecture

PIPE Opportunity Exchange is built upon a scalable hub and spoke model. The Hub (PIPE hub) provides the transport, replication and processing of opportunities between the PSM Siebel and participating partner CRM systems. PIPE Opportunity Exchange (the PIPE hub and all spokes) utilizes a public message transport standard from the RosettaNet organization as the interface to enable message exchange. The RosettaNet organization (http://www.rosettanet.org) defines message exchange in the RosettaNet Implementation Framework (RNIF) specifications. RNIF defines how integration systems will transport message. The Hub runs on Microsoft BizTalk Server 2006 and Microsoft BizTalk Accelerator for RosettaNet. PIPE Opportunity exchange utilizes BizTalk to provide a standard interface to exchange messages. Additionally BizTalk also utilizes business rules that enable the various partnering systems to be updated in a proper manner when particular opportunity is created or updated. Functionality Provided The purpose of the PIPE Opportunity exchange system is to allow information to flow multi directionally between multiple partnering CRM systems without loss of pertinent information. The basic mechanics of the Opportunity Exchange process requires opportunity information to be sent to the hub whenever an event occurs at MS-Siebel.

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

15 of 51 Figure 4 Overview of the solution architecture

M I C R O S O F T

Siebel XML Payload Opportunity Summary

Partner Status

H T T P S A d a p t e r

Business Components Business Services Integration Objects Workflows

BizTalk Accelerator for Microsoft Integration Framework Rosettanet Standards Based Validation Maps Transformation Maps Business Orchestrations Custom Error Handling Application Objects Canonical Objects RosettaNet PIPs Custom Tables RNIF Trading Partner Agreements

Sonic File Utility RosettaNet PIP Message

- Authenticate - Virus Scan

EAI HTTP(s) Transport

Fully Opportunity / Opportunity Update

Custom Error Messages

Gateway Web Server

X-Ref
MS - Siebel Server

RosettaNet PIP Message

Microsoft Gateway

RosettaNet PIP Message

Microsoft Siebel

MS BizTalk Server MS SQL Server

Microsoft - BizTalk Server I


Partner CRM System Specific XML Payload Opportunity Summary

RosettaNet PIP Message S O A P A d a p t e r

P A R T N E R
MS CRM

Partner Status

BizTalk Accelerator for Rosettanet RNIF Trading Partner Agreements RosettaNet PIP Message

Fully Opportunity / Opportunity Updates Custom Error Messages

- Validation Maps - Transformation Maps - Business Orchestration

Gateway Web Server

Partner Gateway Partner CRM System


MS BizTalk Server MS SQL Server

Partner MS - BizTalk Server

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

16 of 51 Table 6 Sub-systems Involved

# Sub-systems
1 Table 7 Technologies Used 2 MS - Siebel 4.3 BizTalk Server (BTS) 2006

3 #BizTalk Accelerator for RosettaNet (BTARN)3.3 Technology 4 1 RNIF 2.0Technology XML 5 2 SQL Server 2005 Technology Microsoft .NET 6 3 Partner CRM Application Database Technology The PIPE Opportunity Exchange project can be viewed as three distinct subsystems that represent entire HUB- Spoke system MS-Siebel (PSM), Microsoft Integration Framework hosted on BizTalk Server (hub) and the participating partnering CRM System. Various aspects of the project are represented and include product used, transformations, message format, transports and project boundaries Figure 5 Logical components of the solution
e*BIS Integration Framework Product Siebel Siebel BTS Integration Object To/From Common Integration Object BTS

Transformation

Application Obj. To/From Integration Obj .

Common Integration Object To/From RosettaNet Public PIP RosettaNet Message Format

Format

Siebel Message Format HTTPS - FILE

Transport

Project

Spoke

HUB

3.2.

Data Flow

The following diagram depicts a logical topology of the systems involved in this information exchange. As depicted below, the Microsoft Corp Net domain would host the MS-Siebel and the BizTalk Integration servers which would be exposed to the partner world via a secure gateway server. Figure 6 Systems Involved and underlying Data Flow

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

17 of 51

Trading Partner

Trading Partner
ge sa es M et

Partnering System
Ro s Me ett a ss N e ag t e

MS CorpNet Domain

N ta et os R

Siebel Message

MS Siebel 4.3

HTTPs

BizTalk Database Server

Database Server

I Net Rose tta Partnering N Message System T Proxy/ Gateway with Ro E s FireWall Me ett a ss N e Trading Partner ag t R e Ro se tt aN et M es sa ge N E R os et ta Ne T tM
tta Net R os e ge Messa

es sa ge

Trading Partner

Partnering System

Partnering System

3.3. 3.4.

Application Navigation Supported Platforms


# Platform
1 2 3 Microsoft Windows Advanced Server 2003 Microsoft Windows 2000, XP Internet Explorer 6.0 and above

There are no associated Application Navigation features in the integration layer.

Table 8 Supported Platforms

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

18 of 51

4. System Features
PIPE involves the transfer and sharing of Opportunities across Microsoft & Partner CRM applications. As a part of this PIPE Integration solution about three distinct business processes have been identified. These process flows were defined based on the business process details included in the PIPE Business Requirements document. Reference to an Opportunity in the following business processes is specific to those opportunities that are generated using Microsoft Siebel and not those generated via the Partner Portal or other interfaces. Table 9 List of process flows identified as a part of this solution # 4. 1 4. 2 4. 3 Functional Area Partner Assignment & Opportunity Summary Notification Partner Status Notification Opportunity Updates

The following diagram presents an overview of the overall data flow of the PIPE solution. Figure 7 Message Flow Overview

HUB
(BizTalk & BTARN)
Business Rules Business Validations Custom Tables
Message

Message ORIGINATOR System

Message RECIPIENT System(s)

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

19 of 51 The following list (Table 10) are assumptions that generally apply for all the business processes. These are in addition to those listed in the assumptions section 2.3. As mentioned already, these lists are limited to those that specifically impact the integration layer. Please refer to PIPE BRD and Siebel PIPE functional specification document for the complete list. Table 10 Generic Assumptions identified for all Business Processes listed above # 1 2

Assumption
Reference to the Opportunity in all the business process is those generated using Microsoft Siebel and not those generated via the Partner Portal or other interfaces. Posting of the message from the Siebel system will be optimistic such that the PIPE Integration Detail fields will update to Transfer Successful and with a timestamp of today() if the HTTP post out of Siebel to the middleware was successful. Downstream business validation errors will be communicated back to Siebel, however, there could be potential for systematic errors when attempting to post the transaction to the Partners CRM system that would not be have the error details reflected in Siebel. Systematic errors occur at the time of transport in the backend (e.g. a communication failure) and could potentially leave Siebel thinking the Partner successfully received the latest Opportunity information, when in actuality they are still waiting for it. The October, 2006 PSM release will drive which fields will be presented to the Partners CRM system pre (Opportunity Summary) & post (Opportunity Full) Opportunity acceptance. As PSM makes updates to this list of fields, PIPE will attempt to align as closely as technically possible in the Siebel messaging. PIPE Enabled Partners who are also Portal Enabled will know to only accept their Opportunities in their own CRM system. The system will not be able to support an Opportunity acceptance made directly in Siebel for a PIPE integrated Opportunity. MS Siebel Users will know not to accept on behalf of their partner a PIPE Integrated Opportunity directly in Siebel. The system will not be able to support an Opportunity acceptance made directly in Siebel. Synchronization of backend error information will be a best effort approach in order to avoid trading back and forth of errors. This is to say, if an error is generated while attempting to synchronize Opportunity information between Siebel and the Partner, if another error in-turn is generated in Siebel while attempting to update the database with the backend error information, no further error will be generated from Siebel back to the Integration Layer.

3 4 5 7

4.1.

Functional Area Opportunity Assignment & Notification

The PIPE Opportunity Assignment & Notification business process is a critical part of the PIPE process as it defines the triggering point to when & where the Partner will receive the Opportunity Summary via PIPE. PAM creates an opportunity and assigns it to a PIPE enabled partner. Once this information is saved, the background processes within Microsoft Siebel, trigger this notification process which internally employ the custom integration components. The thus generated opportunity summary message is published to the integration layer. Microsoft PAMs can also re-assign an opportunity to a new PIPE enabled partner.

4.1.1. User Role


Any PSM PAM or PIPE PAM can generate new opportunities and assign PIPE enabled partners to them. Saving the data triggers the opportunity notification process to the respective PIPE enable partner.

4.1.2. Transaction Volumes


About 10% to 15% of the PSM opportunities to be shared with the PIPE enabled partner community.

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

20 of 51

4.1.3. As-Is Solution


Currently Partners log into Partner Portal hosted by the PSM environment to manage these opportunities.

4.1.4. Business Scenario/Functional Process Flow


The following figure presents an overview of this notification process. This business process would support the opportunity reassignment to a new partner (PIPE enabled). Figure 8 Opportunity Summary Notification Overview

Message Originator System

HUB
(BizTalk & BTARN )
Business Rules Business Validations Custom Tables

Message Recipient System

Siebel 4.3

Siebel

Message

RosettaNet

Partner CRM System

The following list (Table 11) are assumptions that apply for this business process. These are in addition to those listed in the assumptions section 2.3. As mentioned already, these lists are limited to those that specifically impact the integration layer. Please refer to PIPE BRD and Siebel PIPE functional specification document for the complete list. Table 11 Assumptions # 1 2 3 4

Assumption
PIPE assumes that Opportunity Summary message is always published for every time an opportunity is assigned newly to a PIPE enabled partner. Before the partner decides to accept or reject the published opportunity summary message, PIPE can continue to publish updates in the same message format. Partner cannot publish opportunity messages to another Partner Any errors encountered either in the Integration layer or at the Partner end, would yield a custom error message which would be published to Microsoft. This would result in an out-of-sync situation for that opportunity across Microsoft & the participating partner. It is assumed that Microsoft would take necessary steps to resolve such issues.

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

21 of 51 Figure 9 Opportunity Summary Notification High Level Flowchart

Opportunity Summary Notification


Transaction Originating System (s) HUB
BizTalk 2006 1

Transaction Recipient System(s)

Microsoft
START
SBL

Validation of other Business CRITICAL fields.

2b N

Critical Error Message

Partner
END

2a

2c Success ? Y 3 N Siebel Message Partner CRM System

MS Siebel 4.3

LOOP

Database

Validation of other Business Rules

8 Additional Massaging of the content

Success ? Y

N Using RosettaNet PIP Template Generate RosettaNet Message

Integration Server RosettaNet

Database

7 Generate MSCanonical Object 6 10 PIP Message Errors ?

LOOP

X-Ref Look -Up Does this Oppty Exist ? N

Generate Integration ID

11 RosettaNet Adapter Flow

Rosettanet Accelerator for BizTalk

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

22 of 51

4.1.5. Process Overview of Screens


Apparently there is no UI associated with these processes on the Integration layer.

4.1.6. Business Rules


Following is the list of business rules associated specifically to this functional process. Table 12 Business Rules # 1 2 3 4

Business Rule
Single Opportunity cannot be published to multiple partners simultaneously Only PIPE enabled primary partners should receive opportunity summary notification Re-assignment should not yield duplicate entries in the integration layer Only those opportunities that have a customer consent can be shared with partners

4.1.7. Security and Privacy


No Security and Privacy rules or requirements identified specific to this process flow.

4.1.8. Regional Requirements


No specific regional requirements identified for this process flow.

4.1.9. Data Conversion


No specific Data conversion requirements identified for this process flow.

4.1.10. Reporting
No specific Reporting requirements identified for this process flow.

4.1.11. Error Handling


Table 13 Error Conditions # 1 2 3 4

Error Condition
Missing Mandatory Field values Invalid values for enumerated fields Updates from Microsoft to those opportunities, for which partners have either opted to disengage or declined/rejected should not be honored Updates from Microsoft to those opportunities, for which Microsoft has already removed the partner association should not be honored

Severity
Critical Critical Critical Critical

For additional details on the custom error handling process to handle the above listed error conditions, please refer to the functional area Custom Error Handling (section 4.4)

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

23 of 51

4.2.

Functional Area Partner Status Notification

The Opportunity sharing process between Microsoft and its Partners facilitates both Microsoft and Partners to exchange or enforce the partners status on a shared opportunity. Various status values can be exchanged with this process flow. Partner can either choose to collaborate or decline to collaborate on an opportunity when the partner receives the opportunity summary notification from Microsoft. Accepting or rejecting/declining to collaborate on an opportunity can happen when the Partner has reviewed the summary information that was initiated by Microsoft within their CRM system and decides appropriately either to participate or decline to participate. As the Partner makes this determination (either to collaborate or not to collaborate, on the Opportunity), they must update their CRM system by changing the partner status value on the Opportunity record to indicate the decision. This in turn will trigger the Partner Status response back to Microsoft, via PIPE. Also Partners can initially accept to collaborate on an opportunity and this decision would publish a partner opportunity status message as accepted. This acceptance message would trigger the publication of a full opportunity message to the partner from Microsoft via PIPE. Partner after receiving the full opportunity message at a later point in time can choose to disengage themselves from that opportunity. As the Partner makes this determination, they must update their CRM system by changing the partner status value on the Opportunity record to indicate the decision. This in turn will trigger the Partner Status response back to Microsoft, via PIPE with the status value as Disengaged. Likewise, Microsoft PAMs can remove a partner from an already assigned opportunity at any stage of the opportunity collaboration with the partner. This occurs when the Microsoft PAM has reviewed the opportunity and decided to re-assign it to a new PIPE enabled partner. To re-assign this particular opportunity to a new partner, the PAM has to remove the currently assigned PIPE partner from that opportunity. Incorporating this change and saving the data would trigger a Partner Status response from Microsoft to the current partner via PIPE. Once these changes are saved by Microsoft PAM in the MS-Siebel application, PAM can re-assign this opportunity to a new PIPE enabled partner which would trigger the Opportunity Summary Notification process (section 4.1)

4.2.1. User Role


PAMs from both Microsoft and Partner community can initiate this transaction.

4.2.2. Transaction Volumes


About 10% to 15% of the opportunities can be shared with the PIPE enabled partner community.

4.2.3. As-Is Solution


Currently Partners log into Partner Portal hosted by the PSM environment to manage these opportunities.

4.2.4. Business Scenario/Functional Process Flow


The overview of the Opportunity Status Update (also referred to as the Acknowledgement Message and Partner Opportunity Status Update Message) flow designed as a part of this solution is shown in Figure 10. Also a high-level overview of this data flow is shown in Figure 11.

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

24 of 51 Figure 10 Partner Opportunity Status Overview

Microsoft

HUB
(BizTalk & BTARN )
Business Rules Business Validations Custom Tables

Partner

Siebel 4.3

Siebel

Message

RosettaNet

Partner CRM System

The following list (Table 14) are assumptions that apply for this business process. These are in addition to those listed in the assumptions section 2.3. As mentioned already, these lists are limited to those that specifically impact the integration layer. Please refer to PIPE BRD and Siebel PIPE functional specification document for the complete list. Table 14 Assumptions # 1

Assumption
Upon Opportunity updates in Siebel, the integration layer will receive a complete copy of the Opportunity information from Siebel to synchronize with. This is to say that the messaging from Siebel will not be a reflection of simply which specific data elements and/or child objects were changed as Siebel does not currently posses the concepts of action codes for the Opportunity child objects. Given the technical constraints imposed by designing a 15 minute wait state prior to posting an update message to the Partners CRM system after an initial update to a PIPE integrated field/object was made, if a Partner had initiated an update inbound transaction during that 15 minute period, updates made by the Siebel user will potentially be overwritten by the Partners transaction. End result is that the Siebel changes would be lost and the user would have to reenter at a later time to synch with the Partners system. Partner cannot change the opportunity sales stage to MS Win 100% Microsoft can re-assign an opportunity to a different partner (PIPE enabled) after removing the current partner-opportunity association. During such instances, Microsoft Siebel is expected to publish Opportunity Summary again to the newly assigned partner or after re-assigning it to the same partner

3 4

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

25 of 51 Figure 11 Opportunity Status Update High Level Flowchart

Opportunity Status Update


Status Publishing System
Microsoft
START
1 Missing or Invalid Integration ID ? MS Siebel 4.3 SBL Y

HUB
BizTalk 2006 3b Critical Error Message

Message Recipient System


Partner
END

4 N 2 Using RosettaNet PIP Template Generate RosettaNet Message 3a N Y Y 5 PIP Message 6 RosettaNet Adapter Flow Errors RN Integration Server RosettaNet

Partner CRM System

Validation of other Business CRITICAL fields.

Database

Database LOOP

Success ?

Rosettanet Accelerator for BizTalk

Partner
START
Y 3a Missing Or Invalid Integration ID ? N 4

BizTalk 2006 Critical Error Message

Microsoft
END

3b

Validation of other Business CRITICAL fields. Errors

Partner CRM System 2 Integration Server RosettaNet Database 1

MS Siebel 4.3

PIP Message

SBL Success ? Y N 6

RosettaNet Adapter Flow RN

LOOP

Generate Siebel Message

Database

Rosettanet Accelerator for BizTalk

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

26 of 51

4.2.5. Process Overview of Screens


No User-Interface is provided for these processes on the Integration layer.

4.2.6. Business Rules


Following is the list of business rules associated specifically to this functional process. Table 15 Business Rules # 1 2 3 4 5

Business Rule
Partner can only disengage from an opportunity but cannot reject an opportunity after accepting an opportunity summary notification Re-assignment should not yield duplicate entries in the integration layer All the entries pertaining to the opportunity message exchange have to be cleared off either after a partner rejects/disengages from an opportunity OR when Microsoft removes the partner. Full opportunity message has to be automatically published immediately after an acceptance message is received from a partner If a partner rejects an opportunity offer, it is necessary for the partner to provide, reasons for rejecting it as a part of the opportunity status update message

4.2.7. Security and Privacy


No Security and Privacy rules or requirements identified specific to this process flow.

4.2.8. Regional Requirements


No regional requirements identified for this process flow.

4.2.9. Data Conversion


No Data conversion requirements identified specifically for this process flow.

4.2.10. Reporting
No Reporting requirements identified specifically for this process flow.

4.2.11. Error Handling


Table 16 Error Conditions # 1 2 3

Error Condition

Severity

Missing standard or conditional Mandatory Field values Critical Invalid values for enumerated fields Critical Updates from Microsoft to those opportunities, for which partners have either Critical opted to disengage or declined/rejected should not be honored 4 Updates from Microsoft to those opportunities, for which Microsoft have Critical already been explicitly removed from that opportunity should not be honored 5 Multiple opportunity status messages for the same opportunity (for other than Critical acceptance) should not be honored For additional details on the custom error handling process to handle the above listed error conditions, please refer to the functional area Custom Error Handling (section 4.4)

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

27 of 51

4.3.

Functional Area Opportunity Updates

The PIPE integrated solution provides the ability for Partners to have visibility to updates and changes to the Opportunity information without having to double enter the data. The decision to accept and collaborate on the Opportunity also entitles Microsoft to receive the full details of the Opportunity in their MS Siebel system along with the ability to modify values and provide updates as well. When general updates to Opportunity data are made, both MS Siebel application and the Partner CRM System will be in sync with the changes.

4.3.1. User Role


Any PSM PAM or PIPE PAM can generate new opportunities and assign PIPE enabled partners to them. Saving the data triggers the opportunity notification process to the respective PIPE enable partner.

4.3.2. Transaction Volumes


About 10% to 15% of the PSM opportunities to be shared with the PIPE enabled partner community.

4.3.3. As-Is Solution


Currently Partners log into Partner Portal hosted by the PSM environment to manage these opportunities.

4.3.4. Business Scenario/Functional Process Flow


The overview of the Opportunity Updates (also referred to as the Full Opportunity Message and Partner Opportunity Updates) process designed as a part of this solution is shown in Figure 12. Also an overview of this flow is shown in Figures 13a & 13b. Figure 12 Opportunity Updates Overview

Microsoft

HUB
(BizTalk & BTARN )
Business Rules Business Validations Custom Tables

Partner

Siebel 4.3

Siebel

Message

RosettaNet

Partner CRM System

The following list (Table 17) of assumptions apply for this business process. These are in addition to those listed in the assumptions section 2.3. As mentioned already, these lists are limited to those that specifically impact the integration layer. Please refer to PIPE BRD and Siebel PIPE functional specification document for the complete list.

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

28 of 51 Table 17 Assumptions # 1

Assumption
Partners will not be able to update the MS Sales Stage to 100% - MS Win. Partners will only be able to take it to the Closed - 80% sales stage as aligned with PSM functionality. Partners will be able to set the Sales Stage to other closed Sales Stage values such as Support 100%, Loss 0% or Disengaged 0% Only Partners who currently have accepted an Opportunity may make general updates to an Opportunity. Partners who have declined or disengaged from the Opportunity may not make general updates to the Opportunity. Partners who chose to decline must supply a declined reason code. Partners who chose to close an Opportunity to Loss 0% or Disengaged 0% will be enforced to provide a closure reason code. PIPE Enabled Partners who are also Portal Enabled Partners will know to only accept, decline or disengage from their assigned Opportunities in their own CRM system. The PIPE platform will not be able to handle an Opportunity decline, accept or disengagement performed directly in Siebel.

2 3 4 5

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

29 of 51 Figure 13a Siebel Generated Opportunity Updates High Level Flowchart

Opportunity Updates Microsoft Generated Updates


Update Publishing System
Microsoft
1

HUB
BizTalk 2006 2b Construct Critical Error Message 2c Siebel Message

Update Recipient System


Partner
END

START

Validation of other Business CRITICAL fields. SBL 5 2a Success ? Y N X-Ref Look -Up Does this Oppty Exist ? 6 3 Y N

MS Siebel 4.3

Partner CRM System Integration Server RosettaNet Database Errors

LOOP

Database Validation of other Business Rules

Retreive Integration Entries 7 Generate MSCanonical Object

9 Using RosettaNet PIP Template Generate RosettaNet N Message 10 Y 11 RosettaNet Adapter Flow RN PIP Message

Success ? LOOP Y

8 Additional Massaging of the content

Rosettanet Accelerator for BizTalk

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

30 of 51 Figure 13b Partner Generated Opportunity Updates High Level Flowchart

Opportunity Updates Partner Generated Updates


Update Publishing System
Partner
START
Construct Critical Error Message

HUB

Update Recipient System


Microsoft
END

BizTalk 2006

4 Validation of other Business CRITICAL fields. 9 Generate MSCanonical Object MS Siebel 4.3

Partner CRM System PIP Message Integration Server RosettaNet Database Y 3a Missing N Or Invalid Integration ID ? 2 PIP Message 1 RosettaNet Adapter Flow RN

5 LOOP

Success ? Y

10 Additional Massaging of the content

6 Validation of other Business Rules

Database

7 LOOP 8

Success ?

11 Generate Siebel Message Errors

SBL

Retreive Integration Entries

Rosettanet Accelerator for BizTalk

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

31 of 51

4.3.5. Process Overview of Screens


Apparently there is no UI associated with these processes on the Integration layer.

4.3.6. Business Rules


Following is the list of business rules associated specifically to this functional process. Table 18 Business Rules # 1 2 3 4 5 6

Business Rule
Sales Stage edits are restricted by a Restriction flag (available as a part of all the full opportunity update messages from Microsoft Siebel) Only PIPE enabled primary partners should be exchanging opportunity updates with Microsoft and likewise Microsoft should be publishing updates through PIPE, only to PIPE enabled partners Microsoft Opportunity Update message would be full messages including all the child records for Products, Contacts, and Notes. Integration layer would publish the entire message to the target partner as is. Full opportunity message has to be automatically published immediately after an acceptance message is received from a partner Partners who have disengaged from a particular opportunity should not publish updates on that Opportunity Updates to a closed Opportunity are always honored/exchanged

4.3.7. Security and Privacy


No Security and Privacy rules or requirements identified specific to this process flow.

4.3.8. Regional Requirements


No regional requirements identified for this process flow.

4.3.9. Data Conversion


No Data conversion requirements identified specifically for this process flow.

4.3.10. Reporting
No Reporting requirements identified specifically for this process flow.

4.3.11. Error Handling


Table 19 Error Conditions # 1 2 3 4 5

Error Condition
Missing standard or conditional Mandatory Field values Invalid values for enumerated fields Updates for those opportunities, for which partners have either opted to disengage or declined/rejected should not be honored Updates for those opportunities, for which Microsoft has explicitly removed the partner association with an opportunity should not be honored Updates to the sales stage, for those opportunities with sales stage value already marked closed should not be honored

Severity
Critical Critical Critical Critical Critical

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

32 of 51

For additional details on the custom error handling process to handle the above listed error conditions, please refer to the functional area Custom Error Handling (section 4.4)

4.4.

Functional Area Customer Error Messaging

The PIPE integrated solution provides the ability for both Microsoft and Partners to have visibility to errors captured / generated while exchanging Opportunity information through PIPE. Exceptions are raised during the validation process and to convey a relevant and meaningful message, custom error handling process has been built. Following are two possible error capturing scenarios. Errors encountered in the Integration Layer: Messages received by integration layer would undergo a series of message structure validations, data validations and business rule validations. Any errors encountered during these validation cycles would kick-off the error handling process which would then construct a custom error message. This custom error message is published to the message originator system (figure 14). Figure 14 Error Generation & Error Handling at the Integration Layer

Message Originating System

HUB
(BizTalk & BTARN)
Business Rules Business Validations Custom Tables
Application Message

Siebel or RosettaNet Message

CRM System
ERROR MESSAGE In Siebel or RosettaNet format
Validations Errors

Errors encountered in the Destination System: Messages published by the source system (either Microsoft or partner) after getting into the Integration layer would undergo a series of validation tests before getting handed over to the destination system. The destination system, after receiving the message, can generate errors due to business validation failures. Errors encountered this way, would get published to the Integration layer with a custom error message, which then would get published to the destination system (figure 15). Figure 15 Error Handling at the Integration Layer (error generation @ the message recipient system)

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

33 of 51

Message Originator

HUB
(BizTalk & BTARN )
Business Rules Business Validations Custom Tables
Application Message

Message Recipient

CRM System

Siebel or RosettaNet Message

Siebel or RosettaNet Message

CRM System

ERROR MESSAGE In Siebel or RosettaNet format

Custom Error Message

ERROR MESSAGE In Siebel or RosettaNet format

Validations Errors

4.5.

Requirements Control

The following list of Business Requirements in essence is extracted from the PIPE 1.0 BRD. This scope of the list has been restricted to the integration layer. Please refer to the corresponding functional specification documents for the list of other business requirements related to functionality associated with participating MS-Siebel and PIPE Partner applications. Table 20 Solution Requirements # 1 Requirement # NEW-244 PIPE Requirement Disengaged Rejection reasons: The solution shall provide the ability to capture a partners disengaged reason code when a partner sets the status of an opportunity to disengaged. The solution will map these partner disengaged reason codes back to the corresponding value in MS Siebel. The solution shall provide the ability for a Partner to disengage from an Opportunity in which they previously accepted. The solution shall provide the ability to automatically update the MS Siebel Partner Status field when a Partner disengages the Opportunity. Status will move from Accepted to Disengaged The solution shall continue to allow a MS Rep to close opportunities within MS Siebel and have the closure details reflected in the partners CRM (if the partner has accepted the opportunity) The solution shall prevent the MS Siebel user from changing the Siebel opportunity status field from active to deleted for MS Opportunities that are assigned to a PIPE Partner. The partner solution will have the option to synch or do not synch customer account information in their Partner CRM system; Opportunity names/descriptions and contacts (End Customer Accounts and End Customer Contacts all will be partner-configurable) The solution shall provide the ability to report on the last successful synchronization of opportunity fields.

2 3

145 146

227

NEW-243

NEW-235

70

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

34 of 51

Requirement #

PIPE Requirement The solution shall provide rollback transaction-handling, which will write all the record details or rollback the entire transaction if any technical issues are encountered. This failed transaction will then be re-queued and re-processed (see Requirement #34 below). This solution applies to data written to the partner systems and data written to MS Siebel. The solution shall facilitate in determining the winning/losing edit when a Microsoft Sales Rep and Partner Sales Rep update or modify the same record at the same time. The solution shall provide opportunity summary; details; and updates to the partner within a 15 minute transactional window (after the update is saved/triggered by Siebel). If MS updates occur on the opportunity within that 15 minute window, then send them the most updated opportunity record (and not multiple records). The solution shall provide the ability to synchronize Opportunity updates made in MS Siebel to the assigned Partner CRM system The solution will provide the ability for a MS Rep to update an offered Opportunity that is in a 'Pending' state and these updates will be reflected in MS Siebel and the Partner's CRM System. This will allow Partners to view the most up-to-date opportunity information when making an accept/reject decision. MS Reps will be able to update the opportunity at any time in MS Siebel and those updates will be sent to the partners system The solution shall allow MS updates on End Customer Account information to be communicated to the Partners CRM system. The solution shall provide the ability for Microsoft not to forward any updates to a Partner that has rejected the Opportunity. Only the partner marked primary will be able to view/accept/reject the opportunity. The partner solution should allow two opportunity import options: 1) Staging area and 2) Automatically import into Partner CRM system (create new opportunity) A PIPE-enabled Partner will have a method to easily identify the Pending Opportunity offer within their system which has been sent to them by Microsoft. The solution shall provide the partner with the ability to accept or reject a MS opportunity within the MS provided Opportunity overview email notification (hyperlinks). The partner's accept/reject email decision will be reflected within MS Siebel. The solution shall provide the ability to automatically update the Partner Status field when a Partner rejects the Opportunity offer. Status will move from Pending to Rejected

33

56

10

NEW-232

11

104

12

113

13 14 15 16 17 18

168 NEW-240 148 213 NEW-236 126

19

219

20

164

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

35 of 51

# 21 22

Requirement # 165 170

PIPE Requirement The solution shall provide the ability to suppress any updates from Partners that have Rejected an Opportunity. Only updates to an opportunity accepted by the partner will be received by MS The solution shall record an audit trail of changes made to the Sales Stage field on the Opportunity by a Partner, and make this audit trail visible within MS Siebel (Opportunity audit trail sub-tab) The solution shall provide the ability to track the # of Days In Stage when a Partner updates or changes the sales stage on the opportunity. The solution needs to update the audit table allowing the velocity to be reported on and tracked. (Previously Requirement #98 combined into this requirement #55) The solution shall provide the ability to monitor and report on a Partners update frequency of their assigned and accepted Opportunities. Partner can add or update account or contact information on an opportunity, but the updated information will not flow back to Siebel. The solution shall provide the ability to allow a Partners to modify any Account Contacts they have created for their assigned opportunities. Updates will occur in Partners CRM system, but not MS Siebel (due to add contact formal manual process) The solution shall prevent a Partner from editing an existing Microsoft Account Contact that is associated to a Microsoft generated Opportunity that been previously accepted. Partner updates on Microsoft Account Contact fields will not be consumed in MS Siebel since these are MS-owned fields. Ability for a partner add, update (quantity & price) and remove products from an opportunity Post acceptance by the Partner, the solution shall provide the ability to synchronize any changes/updates made to Opportunity records in the Partner CRM system, and for these updates to be reflected in the MS Siebel application A Partner cannot update an Opportunity Name and Description for Opportunities generated by Microsoft The solution will prevent Microsoft from receiving any Opportunity updates by a Partner, other than an acceptance or rejection while the offer is in a 'Pending' state. The solution shall provide the ability to accept opportunity notes from a PIPEenabled partner system (on MS-assigned active opportunities). The solution shall allow a Partner to close MS-assigned opportunities within their CRM system and have the closure details reflected in MS Siebel (if the partner has accepted the opportunity) The solution shall support the existing partner selection process where a Partner organization is attached using the Opportunity | Partner sub-tab in MS Siebel.

23

55

24 25

26 10

26

105

27

156

28

222

29

30 31

115 134

32

NEW-234

33

NEW-237

34

35

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

36 of 51

# 35

Requirement # 152

PIPE Requirement The solution shall provide the ability to associate a Partner Company to the Opportunity that is to be offered during the attach process. Selecting a Partner Company for an Opportunity is required for assignment. Only the primary partner will be sent the opportunity via PIPE. PIPE will not distribute an opportunity to multiple partner companies. The solution shall provide the ability to automatically set the Primary flag as checked when the first Partner record is attached to the Opportunity via the Partner sub-tab. Ability for the PAM to associate a Partner Account to an Opportunity when the Primary Partner Contact is not on the Opportunity Sales Team The solution shall provide the ability to automatically update the 'Partner Status' field when an Opportunity is offered to a partner. Regardless of the original value, the status will be set to Pending. (i.e. new assignment or re-assignment). The MS sales rep has the ability to update the Primary flag (i.e. check or uncheck). The solution shall provide the ability to associate a Partner Contact to the Opportunity that is to be offered during the attach process. Selecting a Partner Contact for the Opportunity is optional for assignment. Partner accounts and partner contacts should be established (in Siebel) so that the opportunity assignment process and partner contact assignment process is universal for all three partner profiles (PIPE-enabled; Portal-enabled; both)

36

212

37

118

38

210

39

163

40 41

162 151

42

202

43

203

The ability to track the individual partner contact that is assigned to an opportunity, even if that partner contact is not a portal user. In a given company, it is expected that some of the sales reps could also be portal users, but not all of the sales reps in a company will be set up as portal users. Even if the partner sales rep is not a portal user, they should be allowed to be assigned to an opportunity. Partner Sales reps that are portal users could also be assigned an opportunity that is distributed via the pipe solution.

44

204

The PIPE opportunity assignment and partner contact assignment process should be similar to the non-PIPE (i.e. Partner Portal partners) opportunity assignment and partner contact assignment (i.e. same forms/sub-tabs in Siebel)

45

205

The solution shall allow Partner contacts to be filtered based on the partner company selected (during the Partner Contact Assignment process). A MS Rep should not be allowed to assign an opportunity one company and then to a partner contact from a different company. The Partner Contact must me a part of the selected Partner Company. The partner Company and the partner contacts assigned to an opportunity should always be in sync.

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

37 of 51

# 46 47 48 49 50

Requirement # 211 223 225 160 161

PIPE Requirement The Partner Individual assigned to the opportunity doesn't have to be an OM/PSM Partner Portal user to be assigned an opportunity via PIPE. Ability for the system to restrict deletion of a contact from an opportunity The partner Company and the partner contacts assigned to an opportunity should always be in sync. If a partner company rejects an opportunity, the partner contacts assigned to the opportunity should be removed The solution shall provide a flag in the MS Siebel UI that indicates if a Partner Contact is Partner-Portal enabled. If only a partner company is selected when assigning the opportunity, the partner companys primary contact will be automatically added to the opportunity sales team. The solution shall provide the ability to search by contact first/last name during the PIPE Partner Contact assignment process Ability for the system to automatically add the partner company's primary contact to the opportunity sales team - when only a partner company is selected when assigning the opportunity. Ability for the system (MS Siebel) to filter when selecting Partner Contact - based on the Company/Partner selected. When the MS Opportunity assignor assigns a partner to an opportunity, the solution will only display partner contacts associated to that selected partner company in the drop-down list. The (Siebel) solution shall support three partner profiles: 1) Partners that are PIPE-enabled 2) Partners that are Partner-Portal enabled and 3) Partners that are both PIPE-enabled and Partner Portal-enabled. Solution should address the discrepancy between the OM PSM partner contact assignment (Opportunity team) versus the PIPE partner contact assignment (partner attach) Change of primary partner contact on opportunity. The solution shall provide the ability to deactivate the PIPE Partner and suppress the sending and synchronizing of assigned opportunity information. The solution shall provide a flag in the MS Siebel UI that indicates if a Partner Company is PIPE-enabled. This PIPE-enabled flag will allow users to determine if a partner is PIPE-enabled at the time of partner assignment (i.e. in the partner pick list) The solution shall provide the ability to search and display PIPE-enabled partners The solution shall provide for MS production support to administer the PIPEenabled (yes/no) property for MS partners. The ability to change this indicator will only be available for production support and will not be available for normal Siebel users. This indicator needs to be added to the Siebel UI (i.e. Partner Profile) The solution shall provide reporting capabilities on all newly introduced PIPE fields (within existing Siebel Reports).

51

208

52

209

53

218

54

201

55 56

NEW-241 28

57

36

58

206

59

228

60

NEW-246

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

38 of 51

# 61

Requirement # 150

PIPE Requirement SMS&P requires that a unique Partner identifier, other than the P-login or the Partner Name, be available in the solution providing backend-reporting capabilities of Opportunities that SMS&P is currently working on with a Partner. Any Partner CRM System that has had the PIPE integrated solution deactivated will not have the capability to receive data from Microsoft (and Microsoft will not have the capability to accept any transaction data from the Partner) Ability for the solution to automatically disable PIPE-enabled Partners when partner is removed from Program. The solution shall provide the ability for an Opportunity to be re-assigned to a Partner that has previously been removed or rejected. The integrated solution will allow a Partner to be removed from the Opportunity by a Microsoft sales rep (both before OR after partner acceptance) by manually changing the partner status to Removed The solution shall provide the ability for Microsoft not to forward any updates to a Partner that has been removed from the Opportunity. The solution shall provide the ability for Microsoft to inform the Partner that they have been removed from an Opportunity. If the opportunity is in the Partner CRM system, a flag or status field will indicate the removal. The solution shall translate all relevant transaction related fields into the MS OM system. The solution shall provide the ability for PIPE-enabled Partners to receive transaction data from Microsoft. The full opportunity detail information being sent to the partner, will override any updates that may have been made in the Partners CRM System once it is released through the solution. The solution shall submit the partner with full Opportunity Detail fields once the partner has accepted the opportunity overview. The solution shall provide MS Account/Opportunity notes to be communicated to the partner CRM system. The solution shall provide the ability to identify the opportunity record by a referential system key, regardless of changes made to other opportunity data fields within the transaction. The solution shall provide the ability for an Opportunity to be offered to a Partner when the Opportunity is at any sales stage (including those at < 20 %.) The Product information needs to be included in the Opportunity Summary when an Opportunity is Offered to a partner (i.e. concatenated in an Opportunity Summary field for the partner) so a Partner has visibility to the types of products the customer is interested in. Product Information will consist of Product Family and Product Quantity

62

154

63 64

229 142

65

112

66

140

67 68 69 70

141 59 81 159

71 72 73

220 NEW-233 58

74

147

75

116

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

39 of 51

# 76

Requirement # 1

PIPE Requirement The solution shall automatically send an initial overview of Opportunity information to the attached Partners' CRM system in real-time. The solution shall provide for the ability for an Opportunity to be updateable by Microsoft and the attached primary Partner for up to 90 business days after it has been closed. When a partner closes an opportunity, by selecting a closed Sales Stage, the partner will also need to select a Closure Reason Code. The solution shall allow opportunity close details to be captured. Closing an Opportunity: win/loss/engage, Closure Reason Codes: available information/deal value/duplicate/geographic coverage/qualification level/sales capacity/skill set constraint The solution shall capture the identity of the Partner Rep who Accepts the Opportunity. Note: The Last Updated By and the Last Updated Date fields may be needed in the Partner update transaction to facilitate this requirement. The solution shall capture the identity of the Partner Rep who Rejects the Opportunity. (Note: The Last Updated By and the Last Updated Date fields may be needed in the Partner rejection transaction to facilitate this requirement.) The solution shall provide the ability to automatically record the Last Updated Date and the Partner Company that has updated the Opportunity. Note: Applies to all transactions involving a Partner update/change The solution shall capture the identity of the Partner Company name who Accepts the Opportunity. Note: The Last Updated By and the Last Updated Date fields may be needed in the Partner update transaction to facilitate this requirement. The solution shall capture the identity of the Partner Company Name who Rejects the Opportunity. Note: The Last Updated By and the Last Updated Date fields may be needed in the Partner rejection transaction to facilitate this requirement. The solution shall provide the ability to report on the Last Updated Date/Time on the Opportunity record Ability for the system to not show the rejection reason of a rejected opportunity to the next assigned partner (via PIPE or Partner Portal) Partner Opportunity rejection data will be available to generate reports (MS Internal only)

77

157

78

62

79

80

135

81

31

82

NEW-247

83

NEW-248

84 85 86

68 224 132

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

40 of 51

Requirement #

PIPE Requirement The solution shall provide the ability to capture a partners rejection reason when a partner sets the status of an opportunity to rejected. The solution will map these partner rejection reasons back to the corresponding value in MS Siebel. Reject Reason codes: Duplicate Out of territory Value too low Skill Constraint Customer issue Capacity Insufficient Information Lead Qualification Level Closed Other (require a free form description and mandatory completion) The solution shall allow the results of the Rejected Opportunity by the Partner to be recorded and reflected within MS Siebel For Microsoft initiated Opportunities, the integrated solution will automatically generate a daily summary for all of the new opportunities assigned to the partner company that day. The email will be sent to the partner company's primary contact(s) (or partner company administrator). Each Partner Rep that a MS Rep would assign an opportunity to directly will have a Partner Contact record in MS Siebel. The integrated solution will utilize the email addresses from the Partner Contact record when sending automatic emails. For Microsoft initiated Opportunities, the integrated solution will automatically generate a daily summary for all of the new opportunities assigned to a Partner Rep that day. The email will be sent to the Partner Rep that is assigned to the opportunity by the MS Rep. An auto-generated email will be sent to the Opportunity Owner that indicates the Partner contact and the specific Opportunity ID within the Rejection Notification email. Only the partner marked primary will receive notifications for the opportunity. The solution shall provide the ability for the Opportunity Owner to be notified by email when a Partner chooses to reject a MS-assigned Opportunity. The integrated solution will automatically generate a daily summary for all of the new opportunities rejected by the partner company that day. The email will be sent to the MS opportunity owner. The solution shall automatically send an email notification to the Microsoft Opportunity Owner if the Opportunity offer has passed the stale expiration period and the Opportunity has not been accepted or rejected by the Partner

87

111

88

123

89

108

90

109

91

119

92 93

149 214

94

NEW-242

95

47

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

41 of 51

# 96

Requirement # 107

PIPE Requirement If the Partner is enabled for the expiration SLA, an auto-generated email will be sent to the MS Primary Contact on the Opportunity if the Opportunity offer has passed the stale expiration period and the Opportunity has not been accepted or rejected by the Partner. Ability for the system to alert the user when ownership of the opportunity has been modified A Partner Company can have one or multiple partner companys primary contact(s) that will receive any auto-generated emails. The partner companys primary contact(s) need to be editable as resourcing and staffing changes at the partner company over time. It is preferred that this is administered centrally (i.e.. user support). There may be an impact to process for this requirement since no Parenting solution currently exists in the process.

97

217

98

121

99

122

The solution shall provide the ability for automatically generated emails to be prepopulated with data relating to the notification that is being sent to a Partner. The daily summary email will contain the following: - Assigned (pending) Opportunities - Summary of accepted/rejected/disengaged /removed/closed opportunities The solution shall provide the ability for the Opportunity Owner to be notified by email when a Partner chooses to disengage from an Opportunity in which they previously accepted. The solution shall provide the ability to support the routing of email notifications to different partner company's primary contacts based on the different regions/site of the Partner Company (i.e. Parented partner accounts/branch offices) Each Partner COMPANY that a MS Rep would assign an opportunity to directly will have a Partner record and email address in MS Siebel. The integrated solution will utilize the email addresses from the Partner Company-level record when sending automatic emails (to the partner opportunity assignor/administrator) The solution shall provide the ability for automatically generated opportunity UPDATE emails to be communicated to the partner. The update notification email will contain any MS updates on the partner-assigned opportunity. The daily summary email will contain the following: Microsoft-updated opportunities When MS disables pipe from partner notification to Partner Ability for the solution to notify the Partner CRM system or Partner Administrator via email/notification when partner is removed from PIPE program. The solution shall provide the ability to include the Opportunity ID and Opportunity Name within the email notification when a stale expiration period has been reached.

10 0

144

10 1

153

10 2

NEW-231

10 3

NEW-238

10 4

NEW-245

10 5

155

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

42 of 51

Requirement #

PIPE Requirement Ability for system to redirect notifications when the Primary Partner Contact reassigns an opportunity to a contact within the Partner Sales Organization. Partner reassigns the opportunity to a contact within the Partner Sales Organization (which may occur pre or post Acceptance). The notifications associated to the opportunity should be addressed to the new partner contact on the opportunity Ability for the system to notify the PAM (or Opportunity Assigner) when the Primary Partner Contact reassigns an opportunity within the Partner Sales Organization. Ability for the system to alert the PAM when updates have been made to key fields on the Opportunity Record The solution shall allow the results of the Accepted Opportunity by the Partner to be recorded and reflected within MS Siebel The solution shall provide the ability to suppress any updates from Partners that have been Removed or Disengaged from an Opportunity. The solution shall provide the ability to automatically update the Partner Status field when a Partner accepts the Opportunity offer. Status will move from Pending to Accepted The solution should provide the ability to send the opportunity summary information to the partner assigned to an opportunity, when communication preferences are verified and updated in MS Siebel (flags are checked) The solution is compliant with ASAP security requirements The solution shall prevent the opportunity summary information from being sent to the Partner system if the customer communication preferences (Allow Partner Call, Allow Partner Email) are unchecked. The solution shall display a message to the MS end-user informing them of the non-consent. Due to privacy constraints for the transfer of data, opportunity summary information can only be sent if the customer contact preferences indicate its ok to share data with partners (3rd party) When a PIPE-enabled partner is assigned to an opportunity and the solution determines the MS Siebel consent flags are "no", the solution will wait until the MS user modifies the flag to "yes". When the Microsoft end user sets the consent flags = Yes, the solution is triggered to automatically forward the Opportunity summary information to the assigned partner. The solution shall provide the ability for the for MS sales reps to view and edit the customer communication preference flags. I.e. Allow Partner Calls, Allow Partner Email. The solution shall allow MS updates on End Customer Contact information to be communicated to the Partners CRM system.

10 6

215

10 7 10 8 10 9 11 0 11 1

216 221 2 114

124

11 2 11 3

103

230

11 4

102

11 5

158

11 6 11 7

117

NEW-239

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

43 of 51

# 11 8 11 9 12 0 12 1

Requirement # 137 226 166 167

PIPE Requirement The business requires that only one standard business Service Level Agreement (SLA) be available and enabled for Partners within the Subsidiary (GLOBALLY) The ability for a PAM to revoke an opportunity from a partner based on SLA constraints (before partner acceptance). All pending opportunities will be automatically monitored against the SLA to determine stale opportunities. The solution shall provide the ability to generate a report that provides information on all stale opportunities that are pending Partner acceptance or rejection.

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

44 of 51

5. Security, Privacy, Accessibility, & Disaster Recovery


5.1. Security
Communication between e*BIS integration layer and partners would be secured by HTTP(s) protocol. Client certificate authentication would be the additional layer enforcing the security. Currently e*BIS team does not have the infrastructure to support the usage of encryption using digital certificates and providing certifying authority domains for these digital certificates. BTARN provides the RosettaNet Implementation framework (RNIF) for PIPE. The two RNIF ASPX pages for receive and send are ASP.Net web applications with no user interface, and use web security to ensure secure connection with external parties. They also provide facility for fault tolerance and scalability. BTARN also implements, Non-repudiation, archiving the sent and received messages. Please refer to BTARN documentation for details on registering PIP schemas, Partners and generating Trading Partner Agreements. The application must confirm to the Application Software Assurance Program (ASAP) security conditions. Please review the ASAP Security guidelines at the ASAP website. The reader can also reference the ACE Security checklist for a list of Security items to adhere to. However, the following summarizes the high level integration layer impacts to the guidelines extracted from Security checklist for the PIPE Project. Further technical details surrounding these areas will be addressed during the implementation phase. Authentication & Authorization - For PIPE, MS BizTalk serves as the middle layer residing within the MS Enterprise network between the Partners own systems and MS Siebel. The inbound & outbound Siebel application interfaces designed for the PIPE program do not transmit HBI information such as credit card numbers, personal addresses or SSNs. End Customer Account elements such as Company Name, Company Address are transmitted as well as End Customer Contact information such as First/Last Name, Business Phone Numbers, Email addresses, etc. are transmitted to the Partners CRM system. Communication between e*BIS integration layer and partners would be secured by HTTP(s) protocol. Client certificate authentication would be the additional layer enforcing the security. Currently e*BIS team does not offer the infrastructure to support the usage of encryption using digital certificates and providing certifying authority domains for these digital certificates. However, the MS BizTalk instance for PIPE will be set up with Siebel login access to the application in order to post PIPE transactions to Siebel. In turn, Siebel will be granted login access to the MS BizTalk application in order to post PIPE transactions from Siebel. Code Review N/A. No custom code is being added in the integration layer of PIPE. BizTalk 2006 software hosting this integration layer offers all the features to define and design the integration solution. The design environment has user interface which would enable the developers utilize the native out of the box features of BizTalk. Configuration File Settings N/A at this point of the design process and TBD during the implementation phase. All Servers (Web, Application & SQL) - N/A at this point of the design process and TBD during the implementation phase. SQL Specific - N/A Web Service PIPE will not be utilizing web service technology as a means to interface with Siebel. XML Transactions will be posted/received via a standard Siebel & RosettaNet Messaging payload formats over secure HTTP transport Protocols.
Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

45 of 51 Logging - N/A Cryptography - N/A Other Miscellaneous Checks - N/A

5.2.

Privacy

Please reference the ASAP website for further information about adhering to the privacy guidelines. The reader can also reference the ASAP privacy checklist for a list of privacy conditions to adhere to. However, the following summarizes the e*BIS impacts to guidelines extracted from the Privacy checklist for the PIPE project. Further technical details surrounding these areas will be addressed during the technical design & implementation phases: Privacy Statement N/A : PIPE functionality is focused on backend integration processes and the existing Privacy Statements are not impacted. All PIPE Partners will also be forced to sign a Trading Partner Agreement at the time of enrolling their CRM systems in the PIPE platform. P3P Encoding N/A (see above) Compact Cookie Policies - N/A: PIPE Integration functionality is focused on backend integration processes and does not utilize cookies. Third Party Links N/A : PIPE Integration functionality is focused on backend integration processes and does not utilize links to third party sites. Consent - N/A: PIPE integration functionality is focused on backend integration processes and does not utilize links to third party sites. Access Message exchange via the Integration Layer of PIPE, does not include any sensitive PII information about end-customer contacts like Social Security Number, Credit Card information, Date of Birth details etc.. The data in transfer is not hosted on the integration layer and its impact on accessibility of that information is not applicable. End users from Siebel and Partner community would not be able to access any of this information exchange happening on the integration layer. Security The inbound & outbound Siebel application interfaces designed for the PIPE program do not transmit HBI information such as credit card numbers, personal addresses or SSNs. End Customer Account elements such as Company Name, Company Address are transmitted as well as End Customer Contact information such as First/Last Name, Business Phone Numbers, Email addresses, etc. are transmitted to the Partners CRM system. Communication between e*BIS integration layer and partners would be secured by HTTP(s) protocol. Client certificate authentication would be the additional layer enforcing the security. Currently e*BIS team does not offer the infrastructure to support the usage of encryption using digital certificates and providing certifying authority domains for these digital certificates. Data Integrity N/A: PIPE integration functionality does not have any functional components and it does not have any application data to store or retrieve against BizTalk database. Enforcement N/A: PIPE integration functionality does not add any functionality to neither the existing MS Siebel application nor the existing Partner Applications.

5.3.

Accessibility

PIPE does not have any user-interface or web-access interface. All the transaction handling is real-time and is dealt as a back-ground process. Accessibility to this runtime data is not possible.

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

46 of 51

5.4. 5.5.

Audit Disaster Recovery/Business Continuance

No specific SOX audit requirements have been identified for PIPE.

PIPE integration layer does not host any business data hence the impact during disaster is minimal on the business. Please find the below link which provides details on existing e*BIS procedures for Disaster Recovery and Business Continuance. http://sts/ebis/Operations/Business%20Continuance/Forms/All%20Documents.aspx

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

47 of 51

Appendix A: Document Change History


Version No. 1.0 2.0 3.0 Date Mar 10, 2006 Mar 31 2006 Apr 03, 2006 Name (Alias) Diwakar Tadepalii (v-dtadep) Diwakar Tadepalli (v-dtadep) Diwakar Tadepalli (v-dtadep) Draft 1 Draft 2 Draft 3 Description of Change

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

48 of 51

Appendix B: Review and Sign-off


Below is a list of the project team members and required reviewers
Person Role Contact Reviewed Date

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

49 of 51

Appendix C: Glossary/ Definitions


Below is a list of common terms and their definitions that are used throughout PIPE:
Term Account ASAP Definition A Siebel entity used to represent a relationship between Microsoft and a partner organization. An account is created for each partner organization. Accounts are used to track opportunities, activities and contacts for the partner. Application Software Assurance Program ASAP aims to ensure all Microsoft line of business applications are secure and meet or exceed Microsofts security and privacy standards. The ASAP program is a joint effort between the Business Unit IT Groups (BUITs) and Microsoft IT which have developed a process to help ensure the security and privacy of new application releases as well as existing in-production applications. Business Requirements Documents - Structured documents detailing the specific requirements of a business process. Business requirements documents contain statements of work, requirements definitions, process and data decomposition information, business rule definitions, training plans, and final budgets. Common Integration Data Model A Siebel entity used to collect information about individuals who may be useful professionally by providing a connection to a professional field or organization. Customer Relationship Management. Provides the ability to manage and track interactions between Customers and Microsoft. Go-to-Markets - Integrated campaigns that address a common customer need and align the sales, marketing, and services teams of Microsoft and its partners with Microsoft and partner products and solutions. High Business Impact - A classification applied to information or assets whose disclosure would cause significant material loss to the company, owners, or relying parties. Integration objects are Siebel metadata structures that represent hierarchical objects using components and fields. Siebel Integration Objects are key development components in defining a Siebel application interface. Microsoft Accessibility Guide Microsoft guidelines and resources providing product groups with the information and tools they need to integrate accessibility into design specifications, develop accessible technology solutions, and understand how to prioritize accessibility. A family of Microsoft server products that supports large scale implementation management of enterprise application integration processes. Microsoft Integration Framework Microsoft Organizations - A data store of organizations and individuals that provides an integrated and standardized view of customer and business information to internal Microsoft business units. Microsoft Solution Provider Programs. A program that defines the criteria and benefits for partnering with Microsoft Opportunity Management. Tracking of potential revenue generating opportunities between Microsoft and a Microsoft lead or customer. Used for forecasting sales and product demand. Opportunities may be driven by either Microsoft or a Microsoft Partner. MSSP sales stage is 20%+ (after the lead is qualified) Partner Account Manager - A Microsoft job title for individuals who are responsible for business planning, recruiting, developing, and managing a diverse set of Microsoft Small and Medium Business partners. Partner Development Manager Partner Group Manager - A Microsoft job title for individuals driving revenue and maintaining relationships with partners in a designated geographical or business area by making sure that partners are technically enabled, driving joint demand activities, supporting partners in selling solutions, and managing opportunity pipelines. Personally Identifiable Information - Any information relating to an identified or identifiable individual. Such information may include name, country, street address, e-mail address, credit card number, social security number, government ID number, IP address, or any unique identifier that is associated with PII in another system. Partner Interface Process - RosettaNet Partner Interface Processes (PIPs) are specialized system-to-system XMLbased dialogs that define business processes between trading partners. Each PIP specification includes a business document with the vocabulary, and a business process with the choreography of the message dialog. Partner Integration & Productivity Environment - It is the intent of the PIPE project to develop an integrated solution that allows for the creation of an Opportunity record in Siebel PSM and having that record reflected automatically in a Channel Partners own CRM system Partner Relationship Management. Provides the ability to manage and track interactions between Partners and Microsoft. RosettaNet is an organization set up by leading information technology companies to define and implement a common set of standards for e-business. RosettaNet is defining a common parts dictionary so that different companies can define the same product the same way. It is also defining up to 100 e-business transaction processes and standardizing them. Because RosettaNet is supported by all or most of the major companies in the IT industry, its standards are expected to be widely adopted. User Interface - In information technology, the user interface (UI) is everything designed into an information device with which a human being may interact -- including display screen, keyboard, mouse, light pen, the appearance of a desktop, illuminated characters, help messages, and how an application program or a Web site invites interaction and responds to it. US Partner Central - A partner relationship management tool used by Microsoft and its Partners to jointly manage

BRD CIDM Contact CRM GTM HBI Integration Object MAG Microsoft BizTalk Server MIF MSO MSPP (UPP) OM Opportunity PAM PDM PGM PII PIP PIPE PRM/PSM

RosettaNet

UI USPC

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

50 of 51

Term

Definition account profiles, create and manage business opportunities, manage funds requested by and distributed to Microsoft Partners, and identify Partner solution offerings.

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

51 of 51

Appendix D: Related Documents/References


Document Vision and Scope Scope Matrix PIPE Workflow Assignment Matrix PIPE Program Management Website PSM Siebel Analysis Website ASAP Website ASAP Privacy Checklist ACE Security Checklist MAG Website MAG Checklist PIPE DI Functional Specification documents PIPE UI Functional Specification documents PSM DI Functional Specification documents PSM UI Functional Specification documents PIPE Design Issues List PIPE Questions List PSM Questions List PSM Dev-Test Question List RosettaNet Public Website Document Location \\tksiebel\SD_SHADOW\Siebel\Release4_5\Envisioning\BRDs\BRD - PIPE Business Requirements_Gold_1.doc \\tksiebel\SD_SHADOW\Siebel\Release4_5\Envisioning\Scope Matrix\ OM_PRM - Analysis ROMs_Consolidated_Scope Matrix.xls \\tksiebel\SD_SHADOW\Siebel\Release4_5\Design\FuncSpec\PIPE Workflow Assignment Matrix.xls http://tksiebel/sites/PIPE_06/default.aspx http://tksiebel/sites/analysis/default.aspx http://team/sites/asap/default.aspx http://team/sites/asap/PrivacyRelated%20Documentation/Privacy%20Comprehensive %20Assessment%20Checklist%203.3.xls http://team/sites/asap/SecurityRelated%20Documentation/ACE%20Security%20Checklist.doc http://enable/guide/ \\enableweb\intranet$\Guidelines\Overview\MAGV2HighImpactCheckpointsFull.doc \\tksiebel\SD_SHADOW\Siebel\Release4_5\Design\FuncSpec\DI\ \\tksiebel\SD_SHADOW\Siebel\Release4_5\Design\FuncSpec\UI\ \\tksiebel\SD_SHADOW\Siebel\Release4_5\Design\FuncSpec\DI\ \\tksiebel\SD_SHADOW\Siebel\Release4_5\Design\FuncSpec\UI\ http://tksiebel/sites/PIPE_06/Lists/PIPE%20Design%20Issues/active.aspx http://tksiebel/sites/PIPE_06/Lists/PIPE%20Question%20List/active.aspx http://tksiebel/sites/analysis/Lists/PSM%20Question%20List/Active%20Items.aspx http://tksiebel/sites/analysis/Lists/DevTest%20Questions/Open.aspx http://www.rosettanet.org/Rosettanet/Public/PublicHomePage

Microsoft Confidential: This document is considered confidential to and is maintained as a trade secret by Microsoft Corporation. Information in this document is restricted to Microsoft authorized recipients only and any reproduction, distribution, or public discussion of this material is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.

S-ar putea să vă placă și