eBIS - PIPE Functional Specification

7/31/2019 eBIS - PIPE Functional Specification

1/51

Functional Specification Partner Integration & Productivity Environment(Code Name: PIPE 1.0)

Created from xBUIT SDLC Template: Functional Specification v1.2

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

Filename: e*BIS - PIPE Functional Specification.doc

Revision: V3.0Last Save Date: Wednesday, June 06, 2012Author(s): e*BIS TeamFile Location: PIPE SharepointRead Only (public)Link:

TBD
http://tksiebel/sites/PIPE_06/Shared%20Documents/3%20-%20Design/eBIS%20Design/Spec%20Docshttp://tksiebel/sites/PIPE_06/Shared%20Documents/3%20-%20Design/eBIS%20Design/Spec%20Docs


2/51

Table of Contents

1. Introduction......................................................................................................................................................4

2. Solution Overview.......................................................................................................................................... ..62.1. Scope.................................................................................................................................................. .....6

2.2. Out of Scope.............................................................................................................................................72.3. Assumptions, Constraints and Dependencies...................................................................................... .....82.4. Risks.........................................................................................................................................................9High Level Conceptual Design......................................................................................................................11

2.4.1. e*BIS Integration Framework.......................................................................................................... .....122.5. Checklist to Onboard a New Partner with PIPE...................................................................................... .13

3. System Overview..........................................................................................................................................143.1. System Context & Architecture................................................................................................. ..............143.2. Data Flow...............................................................................................................................................163.3. Application Navigation.............................................................................................................................173.4. Supported Platforms ........................................................................................................................... ...17

4. System Features............................................................................................................................................18

4.1. Functional Area Opportunity Assignment & Notification .......................................................................194.1.1. User Role..................................................................................................................................... ...194.1.2. Transaction Volumes.......................................................................................................................194.1.3. As-Is Solution..................................................................................................................................204.1.4. Business Scenario/Functional Process Flow....................................................................................204.1.5. Process Overview of Screens..........................................................................................................224.1.6. Business Rules................................................................................................................................224.1.7. Security and Privacy........................................................................................................................224.1.8. Regional Requirements...................................................................................................................224.1.9. Data Conversion..............................................................................................................................224.1.10. Reporting.......................................................................................................................................224.1.11. Error Handling....................................................................................................................... ........22

4.2. Functional Area Partner Status Notification..........................................................................................234.2.1. User Role..................................................................................................................................... ...234.2.2. Transaction Volumes.......................................................................................................................234.2.3. As-Is Solution..................................................................................................................................234.2.4. Business Scenario/Functional Process Flow....................................................................................234.2.5. Process Overview of Screens..........................................................................................................264.2.6. Business Rules................................................................................................................................264.2.7. Security and Privacy........................................................................................................................264.2.8. Regional Requirements...................................................................................................................264.2.9. Data Conversion..............................................................................................................................264.2.10. Reporting.......................................................................................................................................264.2.11. Error Handling....................................................................................................................... ........26

4.3. Functional Area Opportunity Updates................................................................................................ ...274.3.1. User Role..................................................................................................................................... ...274.3.2. Transaction Volumes.......................................................................................................................27

4.3.3. As-Is Solution..................................................................................................................................274.3.4. Business Scenario/Functional Process Flow....................................................................................274.3.5. Process Overview of Screens..........................................................................................................314.3.6. Business Rules................................................................................................................................314.3.7. Security and Privacy........................................................................................................................314.3.8. Regional Requirements...................................................................................................................314.3.9. Data Conversion..............................................................................................................................314.3.10. Reporting.......................................................................................................................................314.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 thismaterial is subject to the limits described in your non-disclosure agreement with Microsoft Corporation.


3/51

3 of 51

4.4. Functional Area Customer Error Messaging.........................................................................................324.5. Requirements Control ............................................................................................................................33

5. Security, Privacy, Accessibility, & Disaster Recovery.......................................................................... ...........445.1. Security...................................................................................................................................................445.2. Privacy....................................................................................................................................................455.3. Accessibility............................................................................................................................................45

5.4. Audit.................................................................................................................................................... ...465.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



4/51

4 of 51

1. IntroductionPartner Integration & Productivity Environment (PIPE) is an integration and collaboration solution built tofacilitate 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 shareopportunity information between MS Siebel and the Partners CRM systems, without having to re-enteropportunity 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 thepartner community. Each integrated partner then has the ability to adopt the public process, and map thepublic 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 BusinessRequirements 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 tosupport the overall design of the solution and underlying components.

Figure 1a Overview of the Business Perspective of the Solution

Customer

Partner Sales Reps

EPG

SMS&P

PIPE:

Partner Integration & Productivity Environment

Opportunit

y Opportunity

Microsoft Sales Reps

MS Siebel

4.2/4.3

Partner CRM

System

Business Process

Field Taxonomy

Data TransformationRouting

Core Services

Collaborative Opportunity Management of Microsoft InitiatedOpportunities between Microsoft and its Partner Community



5/51

5 of 51

Figure 1b Overview of the Business Perspective of the Solution


Integration ServerExecutes CreateOpportunity BIP

Send PartnerNotification

Partner Assigned

Partner

Assignment

Opportunity is

Created

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

OpportunityEntered into

Partner System

CRMCRM

Integration Server

Executes UpdateOpportunity BIP

Partner Accepts

Opportunity

Update Opportunity

Status to PartnerAccepted

Opportunity

Status Visibility


6/51

6 of 51

2. Solution OverviewPIPE is built upon a scalable hub and spoke model. The PIPE Hub provides the transport, replication andprocessing of opportunities between the PSM Siebel and partner CRM systems. PIPE is the solution forreducing the amount of overhead associated with sharing opportunities as part of the PSM offering to thepartner community.

PIPE uses an industry standard interface for all transactions that adhere to a set of Microsoft derivedtaxonomy values and processes, and complete a procedure as part of the onboard process to the PIPEOpportunity Exchange.

BizTalk Integration Layer is referred to as the HUB.

2.1. ScopeThe 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



7/51

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 ScopeThe Out of Scope section identifies the requirements that will not be met by this project or release. Thisprimarily is the identification of requirements (business, user, system, operational, usage scenario) thatcannot be met as a part of the current phase. The out of scope list includes but not limited to those itemsfound in the business requirements document (see Table 1). For a complete list of Requirements please referto PIPE BRD & Siebel Functional Specification documents.

Table 1 Requirements marked out of scope

# Requirement Reason

1 Opportunity Replication This solution will not provide the ability to publish or route the sameopportunity to multiple trading partnering CRM systems simultaneously

2 Partner GeneratedOpportunities

This solution will not provide the functionality to receive/process newopportunity messages published by partners

3 Partner Level Individualassignment

This solution will not provide ability to assign opportunities to PartnerIndividual level

4 Reporting on PIPE 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 notsupported in this integration solution. Building interfaces for providingthese details is also not defined to be a part of this solution.

5 Activities Exchange of Activities, Attachments is not supported6 Support Tools Creating operational support tools for PIPE is not a part of the scope of

this project phase7 Missing Opportunities PIPE does not support business processes pertaining to

requests/fulfillments of Missing or Lost opportunity records.8 Bulk Opportunities PIPE would not support bulk opportunity record processing.



8/51

8 of 51

2.3. Assumptions, Constraints and DependenciesFollowing are e*BIS specific list of assumptions, constraints and dependencies (Tables 2, 3 & 4). For acomplete list of these please visit PIPE BRD & Siebel Functional Specification Documents.

Table 2 Assumptions

# Assumption Description

1 No dog-fooding allowed Only release product will be used in PIPE opportunity exchange2 e*BIS personnel support Once PIPE is released to production it will be supported by e*BIS

production support3 Acknowledgements are

generated only for freshOpportunity Summarytransactions

Business acknowledgement messages are generated only for fresh/newopportunity summary transactions. Similar acknowledgements forupdate transactions is deemed out of scope for this release

4 Product Line and ProductValidation

Product Line Item and Product Family value validations are expected tohappen only at MS Siebel and not in the integration layer

5 Environment Support Partners have completed PIPE / middleware tier development and

testing to integrate with MS Siebel prior to the solution launch.6 Publishing OpportunityMessages

Partners will allow Microsoft to push data into their respective system.

7 Administrative Co-ordination Coordination between Siebel User Support and e*BIS ProductionSupport will occur to determine at what point the Partner Accountrecords need to be PIPE Enabled or Disabled. It will be necessary tomark all Partner Child Account Records for a given Partner ParentOrganization with the PIPE Enabled flag as well as PIPE-ID. PIPEEnabling for a single backend gateway may even span across multipleParent Organizations depending upon how Partner Accounts aregrouped

8 PIPE enabled Partner SeedData

It is assumed that for PIPE to function, PIPE enabled partner seed datawould be available in the integration layer database. No user interface

for these activities on the integration layer, is assumed to be part of thisproject scope.9 Product, Account, Contact

Notes Information in PIPEmessages

Product, Account, Contact & Notes information is never manipulated inthe integration layer. The snapshot received from Microsoft or Partnerwould be forwarded to the recipient system as is.

10

Message Flow It is assumed that all the three business flows, Opportunity Summary,Partner Status and Opportunity Updates would flow in the samesequence and that any other system hooked up to PIPE would not breakor override this sequence

11

Data Cleansing The entries registered in the e*BIS integration server database would becleared/deleted the moment a partner rejects or Disengages from theopportunity and likewise if Microsoft removes a partner from anopportunity. This would enable effective transaction management whileprocessing re-assigned opportunities & preventing exchange of wrongopportunity update messages from the removed partners.

Table 3 Constraints

# Constraint Description

1 Data Consistency Data consistency and data integrity issues exist across internal andexternally integrated systems and shadow applications. Subsidiaries runthe business from various systems with many silos between processesand systems



9/51

9 of 51

# Constraint Description

2 Solution Performance System performance may be degraded due to the additional volume ofopportunities generated by the new user base. This may lead to decreasein user experience and lack of adoption

3 Solution Performance Usage of digital certification process for authentication and encryptionmay degrade the overall transaction performance and through-put in

association to the transaction volume4 Software Technical

LimitationsAny and all of the PIPE software limitations have to be directed to therespective product team for resolutions or work-arounds e.g., BizTalk,BizTalk Accelerator etc.

Table 4 Dependencies

# Dependency Description

1 Taxonomy The PIPE integrated solution will depend on the existing integrationbetween Siebel PSM application and the PSM Partner Portal for thetaxonomy of Opportunity data and Partner information

2 Data Integrity Data integration and integrity historically data integrity issues such-aspartner originated data have prevented adoption and usage of standardsystems

3 Integration Platform Stability Platform stability currently the platform to be used for the PIPEintegrated solution requires a rigorous evaluation to analyze the stabilityand fit of Microsofts proprietary Integration Framework

4 Validation of Product,Product Family, Contact,

Account

PIPE Integrated solution will depend on Siebel to validate Product,Product family, Account, Contact data. The current scope of the PIPEintegration layer does not enable querying & validation of this dataagainst Siebel.

2.4. Risks

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



10/51


11/51

11 of 51

High Level Conceptual Design

The following diagram (Figure 2) highlights the various systems that can conceptually participate in thiscollaborative PIPE Opportunity Exchange System. MS Siebel is hosted on a customized version of Siebelacts 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 isvia secure and encrypted HTTP layer. The industry standard - RosettaNet Message Exchange Framework, isemployed in exchanging messages with the trading partners.

Next Section (section 2.5.1) provides an overview of the integration framework hosted by the MicrosoftsHub.

Figure 2 Conceptual Design

Partner

CRM

System

Partner

CRM

System

PSM

MicrosoftSiebel

Siebel A pplication

HTTP(s)

EAI Transport

Hub

BizTalk Server

BTARN

HTTP(s)

RosettaNet Framework

Partner

CRM

System

Internet

Partner

CRM

System

Inbound

OutboundOutbound

Inbound

The backbone of the PIPE Opportunity Exchange solution is in the hub. Microsoft Integration Framework withCIDM 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 RosettaNetstandard.



12/51

12 of 51

2.4.1.e*BIS Integration Framework

Figure 3 Overview of e*BIS Integration Framework

Source Adapter

Flow

Source

Transformation Flow

Integration Flow

Target

Transformation

Flow

Microsoft CIDM

Object

Siebel

Application

Message

Source Validation

Flow

RosettaNet PIP

Message Published

to

Trading Partner

CRM System

RosettaNet

Message

RosettaNet PIP

Object

Trading

Partner

Agreements

Siebel Application

Object

Target Adapter Flow

Custom Error

Message Object

PSM / MS-Siebel

INTEGRATION LAYER

Microsoft e*BIS Integration Framework



13/51


14/51

14 of 51

3. System OverviewPIPE is built upon a scalable hub and spoke model. The PIPE Hub provides the transport, replication andprocessing of opportunities between the PSM Siebel and partner CRM systems. PIPE is the solution forreducing the amount of overhead associated with sharing opportunities as part of the PSM offering to thepartner community.

PIPE uses an industry standard interface for all transactions that adhere to a set of Microsoft derivedtaxonomy values and processes, and complete a procedure as part of the onboard process to the PIPEOpportunity 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 thetransport, 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 transportstandard from the RosettaNet organization as the interface to enable message exchange. The RosettaNetorganization (http://www.rosettanet.org) defines message exchange in the RosettaNet ImplementationFramework (RNIF) specifications. RNIF defines how integration systems will transport message. The Hubruns 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 aproper manner when particular opportunity is created or updated.

Functionality Provided The purpose of the PIPE Opportunity exchange system is to allow information toflow multi directionally between multiple partnering CRM systems without loss of pertinent information. Thebasic mechanics of the Opportunity Exchange process requires opportunity information to be sent to the hub

whenever an event occurs at MS-Siebel.

http://www.rosettanet.org/http://www.rosettanet.org/http://www.rosettanet.org/


15/51

15 of 51

Figure 4 Overview of the solution architecture

Partner CRM SystemSpecific XML Payload

MS - Siebel Server

Business

ComponentsBusiness Services

Integration ObjectsWorkflows

MS SQL Server

X-Ref

HTTPS

Ada

pter

BizTalkAccelerator

forRosettanet

MS BizTalk Server

Microsoft Integration Framework

Standards Based- Validation Maps- Transformation Maps- Business Orchestrations

- Custom Error Handling- Application Objects- Canonical Objects- RosettaNet PIPs- Custom Tables

OpportunitySummary

Partner Status

Fully Opportunity /Opportunity Update

Custom ErrorMessages

EAI HTTP(s)

Transport

Gateway WebServer

I N T E R N E T

Gateway WebServer

Partner CRM System

Partner GatewayMS CRM

Microsoft Gateway

Microsoft Siebel

MS SQL Server

SOAP

Adapter

Partner MS - BizTalk Server

OpportunitySummary

Partner Status

Custom ErrorMessages

Fully Opportunity /Opportunity Updates

MS BizTalk Server

- Validation Maps- Transformation Maps- Business Orchestration

MIC

R

O

SO

FT

PA

RTN

ER

Microsoft - BizTalk Server

Siebel XML Payload

Sonic File Utility

RosettaNetPIP

Message

RosettaNetPIP

Message

RNIF

TradingPartner

Agreements

BizTalkAccelerator

forRosettanet

RNIF

TradingPartner

Agreements

RosettaPIP

Messag

RosettaPIP

Messa

RosettaNet

PIPMessage

- Authenticate- Virus Scan

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


16/51

16 of 51

Table 6 Sub-systems Involved

Table 7 Technologies Used

# Technology

1 XML Technology

2 Microsoft .NET Technology

3 Database Technology

The PIPE Opportunity Exchange project can be viewed as three distinct subsystems that represent entireHUB- 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

Siebel BTS

e*BIS IntegrationFramework

Siebel BTS

Application Obj. To/From Integration Obj.Common Integration Object

To/FromRosettaNet Public PIP

Product

Transformation

IntegrationObject

To/From

CommonIntegration

Object

HUBSpoke

Siebel Message Format

RosettaNet

MessageFormat

Format

Project

Transport HTTPS - FILE

3.2. Data FlowThe 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 Integrationservers which would be exposed to the partner world via a secure gateway server.

Figure 6 Systems Involved and underlying Data Flow


# Sub-systems

1 MS - Siebel 4.3

2 BizTalk Server (BTS) 2006

3 BizTalk Accelerator for RosettaNet (BTARN)3.3

4 RNIF 2.0

5 SQL Server 2005

6 Partner CRM Application


17/51

17 of 51

I

N

T

E

R

NE

T

MS Siebel 4.3

Database Server

MS CorpNet

Domain

BizTalk

Database Server

Trading Partner

Partnering

System

Trading Partner

Trading Partner

Trading Partner

Proxy/Gateway with

FireWall

Partnering

System

PartneringSystem

Partnering

System

SiebelMessage

Rosetta

NetM

essage

RosettaNetMessage

RosettaNetM

essage

RosettaNet

Message

RosettaN

et

Messag

e

RosettaNet

Message

RosettaNet

Messag

e

HTTPs

3.3. Application NavigationThere are no associated Application Navigation features in the integration layer.

3.4. Supported PlatformsTable 8 Supported Platforms


# Platform

1 Microsoft Windows Advanced Server 2003

2 Microsoft Windows 2000, XP

3 Internet Explorer 6.0 and above


18/51

18 of 51

4. System FeaturesPIPE 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 BusinessRequirements document.

Reference to an Opportunity in the following business processes is specific to those opportunitiesthat are generated using Microsoft Siebel and not those generated via the Partner Portal or otherinterfaces.

Table 9 List of process flows identified as a part of this solution

# Functional Area

4.1

Partner Assignment & Opportunity Summary Notification

4.2 Partner Status Notification

4.3

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

MessageORIGINATOR

System

MessageRECIPIENT

System(s)



19/51

19 of 51

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

# Assumption1 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.2 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 Siebelto the middleware was successful. Downstream business validation errors will be communicated backto Siebel, however, there could be potential for systematic errors when attempting to post thetransaction 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 couldpotentially leave Siebel thinking the Partner successfully received the latest Opportunity information,when in actuality they are still waiting for it.

3 The October, 2006 PSM release will drive which fields will be presented to the Partners CRM systempre (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.4 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 inSiebel for a PIPE integrated Opportunity.

5 MS Siebel Users will know not to accept on behalf of their partner a PIPE Integrated Opportunitydirectly in Siebel. The system will not be able to support an Opportunity acceptance made directly inSiebel.

7 Synchronization of backend error information will be a best effort approach in order to avoid tradingback and forth of errors. This is to say, if an error is generated while attempting to synchronizeOpportunity information between Siebel and the Partner, if another error in-turn is generated in Siebelwhile attempting to update the database with the backend error information, no further error will begenerated from Siebel back to the Integration Layer.

4.1. Functional Area Opportunity Assignment & NotificationThe PIPE Opportunity Assignment & Notification business process is a critical part of the PIPE process as itdefines 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, thebackground processes within Microsoft Siebel, trigger this notification process which internally employ thecustom integration components. The thus generated opportunity summary message is published to theintegration 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 VolumesAbout 10% to 15% of the PSM opportunities to be shared with the PIPE enabled partner community.



20/51

20 of 51

4.1.3. As-Is SolutionCurrently Partners log into Partner Portal hosted by the PSM environment to manage theseopportunities.

4.1.4. Business Scenario/Functional Process Flow

The following figure presents an overview of this notification process. This business process wouldsupport the opportunity reassignment to a new partner (PIPE enabled).

Figure 8 Opportunity Summary Notification Overview


Business RulesBusiness Validations

Custom Tables

MessageSiebel 4.3

Partner CRMSystem

Message

Originator System

Message

Recipient System

Siebel RosettaNet

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

Table 11 Assumptions

# Assumption

1 PIPE assumes that Opportunity Summary message is always published for every time an opportunity isassigned newly to a PIPE enabled partner.

2 Before the partner decides to accept or reject the published opportunity summary message, PIPE cancontinue to publish updates in the same message format.

3 Partner cannot publish opportunity messages to another Partner4 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 thatopportunity across Microsoft & the participating partner. It is assumed that Microsoft would takenecessary steps to resolve such issues.



21/51

21 of 51

Figure 9 Opportunity Summary Notification High Level Flowchart

Opportunity Summary Notification

HUB

BizTalk 2006

Transaction Recipient

System(s)

Transaction Originating

System(s)

Success?

NCriticalError

Message

LOOP

Validation of otherBusiness

CRITICAL fields.

N

N

Y

Rosettanet Accelerator for BizTalk

RosettaNetAdapter Flow

RosettaNet

IntegrationServer

Microsoft

MS Siebel 4.3

START

Database

Partner

Database

END

Partner CRM

System

Validation of oth erBusiness Rules

Success?

PIPMessage

GenerateIntegration ID

Generate MS-Canonical Object

N

Y

1

SiebelMessage

2b

56

8 9

10

2c

SBL

X-Ref Look-Up

Does this OpptyExist ?

LOOPY

3

4

Y

N

7

Additional

Massaging of thecontent

Using RosettaNetPIP Template

GenerateRosettaNetMessage

2a

Errors ?

11



22/51

22 of 51

4.1.5. Process Overview of ScreensApparently 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

# Business Rule

1 Single Opportunity cannot be published to multiple partners simultaneously2 Only PIPE enabled primary partners should receive opportunity summary notification3 Re-assignment should not yield duplicate entries in the integration layer4 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 RequirementsNo specific regional requirements identified for this process flow.

4.1.9. Data ConversionNo specific Data conversion requirements identified for this process flow.

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

4.1.11. Error Handling

Table 13 Error Conditions

# Error Condition Severity

1 Missing Mandatory Field values Critical2 Invalid values for enumerated fields Critical3 Updates from Microsoft to those opportunities, for which partners have either

opted to disengage or declined/rejected should not be honoredCritical

4 Updates from Microsoft to those opportunities, for which Microsoft has alreadyremoved the partner association should not be honored

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)



23/51

23 of 51

4.2. Functional Area Partner Status Notification

The Opportunity sharing process between Microsoft and its Partners facilitates both Microsoft and Partners toexchange or enforce the partners status on a shared opportunity. Various status values can be exchangedwith this process flow.

Partner can either choose to collaborate or decline to collaborate on an opportunity when the partnerreceives the opportunity summary notification from Microsoft. Accepting or rejecting/declining to collaborateon an opportunity can happen when the Partner has reviewed the summary information that was initiated byMicrosoft within their CRM system and decides appropriately either to participate or decline to participate. Asthe Partner makes this determination (either to collaborate or not to collaborate, on the Opportunity), theymust update their CRM system by changing the partner status value on the Opportunity record to indicate thedecision. 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 partneropportunity status message as accepted. This acceptance message would trigger the publication of a fullopportunity message to the partner from Microsoft via PIPE. Partner after receiving the full opportunitymessage 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 theOpportunity record to indicate the decision. This in turn will trigger the Partner Status response back toMicrosoft, via PIPE with the status value as Disengaged.

Likewise, Microsoft PAMs can remove a partner from an already assigned opportunity at any stage of theopportunity collaboration with the partner. This occurs when the Microsoft PAM has reviewed the opportunityand decided to re-assign it to a new PIPE enabled partner. To re-assign this particular opportunity to a newpartner, the PAM has to remove the currently assigned PIPE partner from that opportunity. Incorporating thischange and saving the data would trigger a Partner Status response from Microsoft to the current partner viaPIPE. Once these changes are saved by Microsoft PAM in the MS-Siebel application, PAM can re-assign thisopportunity to a new PIPE enabled partner which would trigger the Opportunity Summary Notificationprocess (section 4.1)

4.2.1. User RolePAMs from both Microsoft and Partner community can initiate this transaction.

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

4.2.3. As-Is SolutionCurrently Partners log into Partner Portal hosted by the PSM environment to manage theseopportunities.

4.2.4. Business Scenario/Functional Process FlowThe overview of the Opportunity Status Update (also referred to as the Acknowledgement Message andPartner Opportunity Status Update Message) flow designed as a part of this solution is shown in Figure10. Also a high-level overview of this data flow is shown in Figure 11.



24/51

24 of 51

Figure 10 Partner Opportunity Status Overview



Custom Tables

MessageSiebel 4.3

Partner CRMSystem

Microsoft Partner

Siebel RosettaNet

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


# Assumption

1 Upon Opportunity updates in Siebel, the integration layer will receive a complete copy of theOpportunity information from Siebel to synchronize with. This is to say that the messaging from Siebelwill not be a reflection of simply which specific data elements and/or child objects were changed asSiebel does not currently posses the concepts of action codes for the Opportunity child objects.

2 Given the technical constraints imposed by designing a 15 minute wait state prior to posting an updatemessage to the Partners CRM system after an initial update to a PIPE integrated field/object wasmade, if a Partner had initiated an update inbound transaction during that 15 minute period, updatesmade 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 thePartners system.3 Partner cannot change the opportunity sales stage to MS Win 100%4 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 publishOpportunity Summary again to the newly assigned partner or after re-assigning it to the same partner



25/51

25 of 51

Figure 11 Opportunity Status Update High Level Flowchart

Opportunity Status Update

HUB

BizTalk 2006

Message Recipient

SystemStatus Publishing System

N

Partner CRMSystem

YSTART

N

Database

Database


Microsoft

ENDCriticalError

Message

MS Siebel 4.3

Partner

Y

Y

SBL

Missing or InvalidIntegration ID ?

Success?


CRITICAL fields.

LOOP


RN

PIP

Message

Using RosettaNetPIP Template

GenerateRosettaNetMessage

IntegrationServer

RosettaNet

Errors

1

2

3a

3b

4

5

6

BizTalk 2006

N

MS Siebel 4.3

START

DatabaseDatabase


Partner

END

CriticalError

Message

Partner CRMSystem

Microsoft

Y

SBL

MissingOr InvalidIntegration

ID ?

Success?

Validation of other

BusinessCRITICAL fields.

LOOPGenerate Siebel

Message

Errors

5

3b4

6

RN

IntegrationServer

RosettaNet


PIPMessage

2

1

N

Y

3a



26/51

26 of 51

4.2.5. Process Overview of ScreensNo User-Interface is provided for these processes on the Integration layer.




# Business Rule

1 Partner can only disengage from an opportunity but cannot reject an opportunity afteraccepting an opportunity summary notification

2 Re-assignment should not yield duplicate entries in the integration layer3 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 thepartner.

4 Full opportunity message has to be automatically published immediately after an acceptancemessage is received from a partner

5 If a partner rejects an opportunity offer, it is necessary for the partner to provide, reasons forrejecting it as a part of the opportunity status update message

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

4.2.8. Regional RequirementsNo regional requirements identified for this process flow.

4.2.9. Data ConversionNo Data conversion requirements identified specifically for this process flow.

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




1 Missing standard or conditional Mandatory Field values Critical2 Invalid values for enumerated fields Critical3 Updates from Microsoft to those opportunities, for which partners have either

opted to disengage or declined/rejected should not be honoredCritical

4 Updates from Microsoft to those opportunities, for which Microsoft havealready been explicitly removed from that opportunity should not be honored

Critical

5 Multiple opportunity status messages for the same opportunity (for other thanacceptance) should not be honored

Critical




27/51

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 theOpportunity information without having to double enter the data. The decision to accept and collaborate onthe 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 Opportunitydata are made, both MS Siebel application and the Partner CRM System will be in sync with the changes.

4.3.1. User RoleAny 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 VolumesAbout 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 theseopportunities.

4.3.4. Business Scenario/Functional Process Flow

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

Figure 12 Opportunity Updates Overview



Custom Tables

MessageSiebel 4.3

Partner CRMSystem

Microsoft Partner

Siebel RosettaNet

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



28/51

28 of 51


# Assumption

1 Partners will not be able to update the MS Sales Stage to 100% - MS Win. Partners will only be able totake it to the Closed - 80% sales stage as aligned with PSM functionality. Partners will be able to setthe Sales Stage to other closed Sales Stage values such as Support 100%, Loss 0% or

Disengaged 0%2 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 generalupdates to the Opportunity.

3 Partners who chose to decline must supply a declined reason code.4 Partners who chose to close an Opportunity to Loss 0% or Disengaged 0% will be enforced to

provide a closure reason code.5 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 beable to handle an Opportunity decline, accept or disengagement performed directly in Siebel.



29/51

29 of 51

Figure 13a Siebel Generated Opportunity Updates High Level Flowchart

Opportunity Updates Microsoft Generated Updates

HUB Update Recipient SystemUpdate Publishing System

Partner CRMSystem

START

Database

Database

Microsoft

END

MS Siebel 4.3

Partner

SBL

IntegrationServer

RosettaNet

Errors

BizTalk 2006

Success?

ConstructCritical Error

Message

LOOP


CRITICAL fields.

N

N

Y

Rosettanet Accelerator for B izTalk


Validation of otherBusiness Rules

Success

?

PIPMessage

RetreiveIntegration Entries

Generate MS-

Canonical Object

N

Y

1

Siebel

Message

2b

5

6

8

9

10

2cX-Ref Look-UpDoes this Oppty

Exist ?

LOOPY

3

4

N

Y

7

AdditionalMassaging of the

content

Using RosettaNet

PIP TemplateGenerate

RosettaNetMessage

2a

11

RN



30/51

30 of 51

Figure 13b Partner Generated Opportunity Updates High Level Flowchart

Opportunity Updates Partner Generated Updates

HUB Update Recipient SystemUpdate Publishing System

BizTalk 2006

N

MS Siebel 4.3

START

Database Database


Partner

END

ConstructCritical Error

Message

Partner CRM

System

Microsoft

Y

SBL

MissingOr Invalid

IntegrationID ?

Success?


CRITICAL fields.

LOOP

Generate SiebelMessage

Errors

5

10

4

RN

IntegrationServer

RosettaNet


PIPMessage

2

1

N

Y

3a

PIPMessage

LOOP

N

Validation of other

Business Rules

Success?

7

Retreive

Integration Entries

Generate MS-Canonical Object

6

9

AdditionalMassaging of the

content

8

11



31/51

31 of 51

4.3.5. Process Overview of ScreensApparently there is no UI associated with these processes on the Integration layer.




# Business Rule

1 Sales Stage edits are restricted by a Restriction flag (available as a part of all the fullopportunity update messages from Microsoft Siebel)

2 Only PIPE enabled primary partners should be exchanging opportunity updates with Microsoftand likewise Microsoft should be publishing updates through PIPE, only to PIPE enabledpartners

3 Microsoft Opportunity Update message would be full messages including all the child recordsfor Products, Contacts, and Notes. Integration layer would publish the entire message to thetarget partner as is.

4 Full opportunity message has to be automatically published immediately after an acceptancemessage is received from a partner

5 Partners who have disengaged from a particular opportunity should not publish updates onthat Opportunity

6 Updates to a closed Opportunity are always honored/exchanged

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

4.3.8. Regional RequirementsNo regional requirements identified for this process flow.

4.3.9. Data ConversionNo Data conversion requirements identified specifically for this process flow.

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




1 Missing standard or conditional Mandatory Field values Critical2 Invalid values for enumerated fields Critical3 Updates for those opportunities, for which partners have either opted to

disengage or declined/rejected should not be honoredCritical

4 Updates for those opportunities, for which Microsoft has explicitly removed thepartner association with an opportunity should not be honored

Critical

5 Updates to the sales stage, for those opportunities with sales stage valuealready marked closed should not be honored

Critical



32/51

32 of 51


4.4. Functional Area Customer Error Messaging

The PIPE integrated solution provides the ability for both Microsoft and Partners to have visibility to errorscaptured / generated while exchanging Opportunity information through PIPE. Exceptions are raised duringthe validation process and to convey a relevant and meaningful message, custom error handling process hasbeen built.

Following are two possible error capturing scenarios.

Errors encountered in the Integration Layer: Messages received by integration layer would undergo aseries of message structure validations, data validations and business rule validations. Any errorsencountered during these validation cycles would kick-off the error handling process which would thenconstruct a custom error message. This custom error message is published to the message originatorsystem (figure 14).

Figure 14 Error Generation & Error Handling at the Integration Layer


Business Rules

Business Validations

Custom Tables

Application

Message

CRM System

Message

Originating System

Siebel or

RosettaNet

Message

ERROR

MESSAGE

In Siebel or

RosettaNet

format

Errors

Validations

Errors encountered in the Destination System: Messages published by the source system (eitherMicrosoft or partner) after getting into the Integration layer would undergo a series of validation tests beforegetting handed over to the destination system. The destination system, after receiving the message, cangenerate errors due to business validation failures. Errors encountered this way, would get published to theIntegration 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)



33/51


34/51

34 of 51

# Requirement # PIPE Requirement

8 33

The solution shall provide rollback transaction-handling, which will write all therecord details or rollback the entire transaction if any technical issues areencountered. 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.

9 56The solution shall facilitate in determining the winning/losing edit when aMicrosoft Sales Rep and Partner Sales Rep update or modify the same record atthe same time.

10 NEW-232

The solution shall provide opportunity summary; details; and updates to thepartner within a 15 minute transactional window (after the update issaved/triggered by Siebel). If MS updates occur on the opportunity within that 15minute window, then send them the most updated opportunity record (and notmultiple records).

11 104The solution shall provide the ability to synchronize Opportunity updates made inMS Siebel to the assigned Partner CRM system

12 113

The solution will provide the ability for a MS Rep to update an offeredOpportunity that is in a 'Pending' state and these updates will be reflected in MSSiebel and the Partner's CRM System. This will allow Partners to view the mostup-to-date opportunity information when making an accept/reject decision.

13 168MS Reps will be able to update the opportunity at any time in MS Siebel andthose updates will be sent to the partners system

14 NEW-240The solution shall allow MS updates on End Customer Account information to becommunicated to the Partners CRM system.

15 148The solution shall provide the ability for Microsoft not to forward any updates to aPartner that has rejected the Opportunity.

16 213Only the partner marked primary will be able to view/accept/reject theopportunity.

17 NEW-236The partner solution should allow two opportunity import options: 1) Stagingarea and 2) Automatically import into Partner CRM system (create newopportunity)

18 126A PIPE-enabled Partner will have a method to easily identify the PendingOpportunity offer within their system which has been sent to them by Microsoft.

19 219

The solution shall provide the partner with the ability to accept or reject a MSopportunity within the MS provided Opportunity overview email notification(hyperlinks). The partner's accept/reject email decision will be reflected withinMS Siebel.

20 164The solution shall provide the ability to automatically update the Partner Statusfield when a Partner rejects the Opportunity offer. Status will move from Pendingto Rejected



35/51

35 of 51


21 165The solution shall provide the ability to suppress any updates from Partners thathave Rejected an Opportunity.

22 170 Only updates to an opportunity accepted by the partner will be received by MS

23 55

The solution shall record an audit trail of changes made to the Sales Stage fieldon 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 theopportunity. The solution needs to update the audit table allowing the velocity tobe reported on and tracked. (Previously Requirement #98 combined into thisrequirement #55)

24 26The solution shall provide the ability to monitor and report on a Partners updatefrequency of their assigned and accepted Opportunities.

25 10Partner can add or update account or contact information on an opportunity, butthe updated information will not flow back to Siebel.

26 105

The solution shall provide the ability to allow a Partners to modify any AccountContacts they have created for their assigned opportunities. Updates will occur inPartners CRM system, but not MS Siebel (due to add contact formal manualprocess)

27 156

The solution shall prevent a Partner from editing an existing Microsoft AccountContact that is associated to a Microsoft generated Opportunity that beenpreviously accepted. Partner updates on Microsoft Account Contact fields willnot be consumed in MS Siebel since these are MS-owned fields.

28 222Ability for a partner add, update (quantity & price) and remove products from anopportunity

29 5Post acceptance by the Partner, the solution shall provide the ability tosynchronize any changes/updates made to Opportunity records in the PartnerCRM system, and for these updates to be reflected in the MS Siebel application

30 115A Partner cannot update an Opportunity Name and Description for Opportunitiesgenerated by Microsoft

31 134The solution will prevent Microsoft from receiving any Opportunity updates by aPartner, other than an acceptance or rejection while the offer is in a 'Pending'state.

32 NEW-234The solution shall provide the ability to accept opportunity notes from a PIPE-enabled partner system (on MS-assigned active opportunities).

33 NEW-237The solution shall allow a Partner to close MS-assigned opportunities within theirCRM system and have the closure details reflected in MS Siebel (if the partnerhas accepted the opportunity)

34 35The solution shall support the existing partner selection process where a Partnerorganization is attached using the Opportunity | Partner sub-tab in MS Siebel.



36/51


37/51

37 of 51


46 211The Partner Individual assigned to the opportunity doesn't have to be anOM/PSM Partner Portal user to be assigned an opportunity via PIPE.

47 223 Ability for the system to restrict deletion of a contact from an opportunity

48 225The partner Company and the partner contacts assigned to an opportunityshould always be in sync. If a partner company rejects an opportunity, thepartner contacts assigned to the opportunity should be removed

49 160The solution shall provide a flag in the MS Siebel UI that indicates if a PartnerContact is Partner-Portal enabled.

50 161If only a partner company is selected when assigning the opportunity, the partnercompanys primary contact will be automatically added to the opportunity salesteam.

51 208The solution shall provide the ability to search by contact first/last name duringthe PIPE Partner Contact assignment process

52 209Ability for the system to automatically add the partner company's primary contactto the opportunity sales team - when only a partner company is selected whenassigning the opportunity.

53 218

Ability for the system (MS Siebel) to filter when selecting Partner Contact - basedon the Company/Partner selected. When the MS Opportunity assignor assigns apartner to an opportunity, the solution will only display partner contactsassociated to that selected partner company in the drop-down list.

54 201

The (Siebel) solution shall support three partner profiles: 1) Partners that arePIPE-enabled 2) Partners that are Partner-Portal enabled and 3) Partners thatare both PIPE-enabled and Partner Portal-enabled. Solution should address thediscrepancy between the OM PSM partner contact assignment (Opportunityteam) versus the PIPE partner contact assignment (partner attach)

55 NEW-241 Change of primary partner contact on opportunity.

56 28The solution shall provide the ability to deactivate the PIPE Partner and suppressthe sending and synchronizing of assigned opportunity information.

57 36

The solution shall provide a flag in the MS Siebel UI that indicates if a PartnerCompany is PIPE-enabled. This PIPE-enabled flag will allow users to determineif a partner is PIPE-enabled at the time of partner assignment (i.e. in the partnerpick list)

58 206 The solution shall provide the ability to search and display PIPE-enabled partners

59 228

The solution shall provide for MS production support to administer the PIPE-

enabled (yes/no) property for MS partners. The ability to change this indicatorwill only be available for production support and will not be available for normalSiebel users. This indicator needs to be added to the Siebel UI (i.e. PartnerProfile)

60 NEW-246The solution shall provide reporting capabilities on all newly introduced PIPEfields (within existing Siebel Reports).



38/51

38 of 51


61 150SMS&P requires that a unique Partner identifier, other than the P-login or thePartner Name, be available in the solution providing backend-reportingcapabilities of Opportunities that SMS&P is currently working on with a Partner.

62 154Any Partner CRM System that has had the PIPE integrated solution deactivatedwill not have the capability to receive data from Microsoft (and Microsoft will nothave the capability to accept any transaction data from the Partner)

63 229Ability for the solution to automatically disable PIPE-enabled Partners whenpartner is removed from Program.

64 142The solution shall provide the ability for an Opportunity to be re-assigned to aPartner that has previously been removed or rejected.

65 112The integrated solution will allow a Partner to be removed from the Opportunityby a Microsoft sales rep (both before OR after partner acceptance) by manuallychanging the partner status to Removed

66 140The solution shall provide the ability for Microsoft not to forward any updates to aPartner that has been removed from the Opportunity.

67 141The solution shall provide the ability for Microsoft to inform the Partner that theyhave been removed from an Opportunity. If the opportunity is in the PartnerCRM system, a flag or status field will indicate the removal.

68 59The solution shall translate all relevant transaction related fields into the MS OMsystem.

69 81The solution shall provide the ability for PIPE-enabled Partners to receivetransaction data from Microsoft.

70 159

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 isreleased through the solution.

71 220The solution shall submit the partner with full Opportunity Detail fields once thepartner has accepted the opportunity overview.

72 NEW-233The solution shall provide MS Account/Opportunity notes to be communicated tothe partner CRM system.

73 58The solution shall provide the ability to identify the opportunity record by areferential system key, regardless of changes made to other opportunity datafields within the transaction.

74 147The 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 %.)

75 116

The Product information needs to be included in the Opportunity Summary whenan Opportunity is Offered to a partner (i.e. concatenated in an OpportunitySummary field for the partner) so a Partner has visibility to the types of productsthe customer is interested in. Product Information will consist of Product Familyand Product Quantity



39/51

39 of 51


76 1The solution shall automatically send an initial overview of Opportunityinformation to the attached Partners' CRM system in real-time.

77 157The solution shall provide for the ability for an Opportunity to be updateable byMicrosoft and the attached primary Partner for up to 90 business days after it has

been closed.

78 62

When a partner closes an opportunity, by selecting a closed Sales Stage, thepartner will also need to select a Closure Reason Code. The solution shall allowopportunity close details to be captured. Closing an Opportunity:win/loss/engage, Closure Reason Codes: available information/dealvalue/duplicate/geographic coverage/qualification level/sales capacity/skill setconstraint

79 3The solution shall capture the identity of the Partner Rep who Accepts theOpportunity. Note: The Last Updated By and the Last Updated Date fields maybe needed in the Partner update transaction to facilitate this requirement.

80 135The solution shall capture the identity of the Partner Rep who Rejects theOpportunity. (Note: The Last Updated By and the Last Updated Date fields maybe needed in the Partner rejection transaction to facilitate this requirement.)

81 31The solution shall provide the ability to automatically record the Last UpdatedDate and the Partner Company that has updated the Opportunity. Note: Appliesto all transactions involving a Partner update/change

82 NEW-247

The solution shall capture the identity of the Partner Company name whoAccepts the Opportunity. Note: The Last Updated By and the Last Updated Datefields may be needed in the Partner update transaction to facilitate this

requirement.

83 NEW-248

The solution shall capture the identity of the Partner Company Name whoRejects the Opportunity. Note: The Last Updated By and the Last Updated Datefields may be needed in the Partner rejection transaction to facilitate thisrequirement.

84 68The solution shall provide the ability to report on the Last Updated Date/Time onthe Opportunity record

85 224Ability for the system to not show the rejection reason of a rejected opportunity tothe next assigned partner (via PIPE or Partner Portal)

86 132Partner Opportunity rejection data wil