RE: RE: [provision] Business Case Paper: Subscription and IdentityManagement Intero perability

["DeSouza, Edwin" <edesouza@jamcracker.com>]

Excellent.  Having Internally and Externally sourced applications will
really get the point across.

The paper should communicate Provisioning for.....

Internal Applications:
-- Provisioning is ONLY for Users (Create/Update/Delete)

External Applications (all Multi-Tenant Apps like ADP, Salesforce.com,
401k Providers, etc):
-- First, Provisioning is for Company (Create/Update/Delete)
-- Second, Provisioning is for Users (Create/Update/Delete) at a Company

If you want to make it even more "real", assume that each External
Provider has multiple applcations.  And, we will be Provisioning the
Company+Users to only a *specific* one of those applications.

Hope this helps,
Edwin.


-----Original Message-----
From: gsodhi1@cox.net [mailto:gsodhi1@cox.net] 
Sent: Wednesday, December 18, 2002 10:34 AM
To: DeSouza, Edwin; Yoav Kirsch; Gavenraj Sodhi;
provision@lists.oasis-open.org
Subject: Re: RE: [provision] Business Case Paper: Subscription and
Identity Management Intero perability


I can agree on a scenario which includes internally and externally
sourced applications, systems, etc... but my opinion about presenting
names of the applications, systems, etc... should be vendor agnostic.
The greatest impact of this paper is for each of our organizations to
promote SPML, particulary the business case paper and discussing with
their partners, collegues, marketing channels, etc. and not necessarily
using actual vendor names.  The real scenario should suffice.

-Gavenraj


> 
> From: "DeSouza, Edwin" <edesouza@jamcracker.com>
> Date: 2002/12/18 Wed PM 01:27:24 EST
> To: Yoav Kirsch <Yoav.Kirsch@businesslayers.com>,
>  Gavenraj Sodhi <Gavenraj.Sodhi@businesslayers.com>, 
>  provision@lists.oasis-open.org
> Subject: RE: [provision] Business Case Paper:  Subscription and
Identity
>  Management Intero	perability
> 
> I think using real product names makes it better....  If you do go 
> with generic, it may still be good to give example product for each 
> generic.
> 
> More important is to show a scenario that many Corporate IT types can 
> identify with themselves.  Key is to include Internally+Externally 
> sourced applications.
> 
> Regards,
> Edwin
> 
> 
> 
> -----Original Message-----
> From: Yoav Kirsch [mailto:Yoav.Kirsch@businesslayers.com]
> Sent: Wednesday, December 18, 2002 9:48 AM
> To: DeSouza, Edwin; Gavenraj Sodhi; provision@lists.oasis-open.org
> Subject: RE: [provision] Business Case Paper: Subscription and
Identity
> Management Intero perability
> 
> 
> I would like to eliminate vendor name. We should use mail account , 
> Operating System account ,...
> 
> Yoav Kirsch
> Director, Applications Development
> Business Layers
> 
> 
> -----Original Message-----
> From: DeSouza, Edwin [mailto:edesouza@jamcracker.com]
> Sent: Wednesday, December 18, 2002 12:40 PM
> To: Gavenraj Sodhi; provision@lists.oasis-open.org
> Subject: RE: [provision] Business Case Paper: Subscription and
Identity
> Management Intero perability
> 
> Gavenraj,
> I think this paper should be targetd to folks who deal with 
> Provisioning issues, and who would "buy" a Provisioning/Security 
> product to solve this problem.  In my mind this would be Corporate IT.
> 
> Here is a scenario that I think would be right on.....  Every company 
> (with 500+ employees) has something like this.
> 
> Acme Corp's Corporate IT provides the following (internally hosted) 
> Services to its Employees:
> -- Novell eDirectory
> -- Microsoft Exchange
> -- Intranet
> -- Some other "fairly common applications"
> 
> Acme Corp's Corporate IT also provides the following Externally hosted
> (ASP) Services to it Employees:
> -- ADP Payroll
> -- Schwab 401K
> -- Salesforce.com
> 
> I would recommend using "real" products/applciations, rather than 
> trying to be politically correct.  It will have more impact.
> 
> Also, Supply Chain type examples are very "late 90s".  People want to 
> to solve real problems these days.
> 
> Regards,
> Edwin.
> 
> 
> -----Original Message-----
> From: Gavenraj Sodhi [mailto:Gavenraj.Sodhi@businesslayers.com]
> Sent: Tuesday, December 17, 2002 11:38 PM
> To: 'provision@lists.oasis-open.org '
> Subject: [provision] Business Case Paper: Subscription and Identity
> Management Intero perability
> 
> 
> 
> All,
>  
> As discussed, at the last SPML F2F meeting last month in Redmond, 
> Washington, I am currently in the process of updating this Business 
> Case Paper.  I am looking for comments, critiques, subject topic 
> changes, market diversification, etc... so I may mold this paper to 
> our message of advancement to the upcoming version 1 draft of the SPML

> specification.
> 
> I would like comments by folks before Christmas as I may work on it 
> during the holidays and provide a v2 draft after New Years.  Please, 
> if possible, place comments on a separate document and email them to 
> me at gsodhi@businesslayers.com and I will develop a document of 
> "tracked comments" for discussion and possible inclusion.
>  
> Thanks to everyone, in advance, for helping in the development of this

> version 2 Business Case Paper.
>  
> 
> Best regards,
> 
> 
> -Gavenraj
>  
>  
>  
> **************************************************
> Gavenraj Sodhi 
> Senior Technology Analyst 
> 
> Business Layers
> The eProvisioning Company(tm) 
> 
> P: (949) 388-0088
> M: (949) 350-8808
> F: (949) 767-5851
> 
> **************************************************
> 
> 
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>
> 
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>
>