RE: [provision] SPML: Multi-Tenant ASPs/MSPs

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

Title: Message

Here is another twist.

 

Lets take the previous Mutual Funds example. 

 

1)  Lets assume that Schwab manages Exxon's 401K business, and Fidelity manages Boeing's 401K business.

2)  Lets assume that Schwab and Fidelity include Janus and Vanguard as Providers.

3)  Lets assume that Janus has 15 different funds and Vanguard has 50 different funds.

 

Requirements:

1)  Schwab and Fidelity do not allow Janus to talk to their customers.

2)  Schwab and Fidelity are the "Single Source" for Administration, Reporting, Billing, Support.

3)  Schwab and Fidleity are the "Single Source" from where Updates percolate into the ecosystem.

 

 

Issue:

1)  How do the Providers (Janus, Vanguard, etc) know the difference between Shops (Schwab, Fidelity, etc) and Company (Exxon, Bowing, etc) and CompanyEmployees.

2)  How do the Shops know the various Funds at each Provider?

 

 

regards,

Edwin.

 

 

-----Original Message-----
From: DeSouza, Edwin
Sent: Friday, November 15, 2002 6:56 PM
To: provision@lists.oasis-open.org
Subject: [provision] SPML: Multi-Tenant ASPs/MSPs

Hi,

One of the things that ASPs/MSPs deliver is an ability to "leverage" skills, hosting, operations, etc across a large set of customers+users.

 

The most efficient way of doing this, is to run a Multi-Tenant model, where you run a SingleInstance+MultipleCustomers

(login requires CompanyName+UserName+Password) 

 

The least efficient way would be to run a SingleInstance+SingleCustomer model (login would be UserName+Password).

 

SPML needs to be able to deal with the SingleInstance+MultipleCustomers  model.

 

regards,

Edwin.