OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

saf message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: SAF meeting today - symptoms/prescription


Here are the results of my brainstorm (in table below), so far.

Will hopefully have more on the call today.

 

From: Vaught, Jeffrey A
Sent: Thursday, April 29, 2010 9:26 AM
To: saf@lists.oasis-open.org
Subject: SAF meeting today - proposed Agenda

 

Proposed Agenda:

-          Outreach review

-          Cloud Profile – potential prescriptions & symptoms across different business functions

 

Most of the meeting will focus on the latter (Cloud Profile).

Please be prepared to discuss candidate symptoms (and prescriptions) emitted from different business functions.  Pick your favorite business function and “have at it”!

Below is a list of business functions (stolen from a McDonald’s website).  I’ve organized into two columns – Cloud Consumer & Cloud Provider.

 

Function

Consumer symptoms/prescriptions

Provider symptoms/prescriptions

Accounting-Payables

 

Symptom: Invoice for XXXX service

Elements needed in Symptoms are:

-          Service identifier

-          Service description

-          Duration of service being billed

-          Amount

-          Unit (dollars, etc)

-          Due date

Accounting-Receivables

Symptom: Paid Invoice for XXXX service

Elements needed in Symptoms are:

-          Same as Invoice above

-          Amount Paid

 

 

Accounting-Pricing/Estimating

 

Symptom: Estimate of XXXX service

Elements needed:

-          Same as Invoice

Accounting-Costing

 

Internal Symptom: Cost of XXXX service

Elements needed:

-          List of items in the service

-          Materials cost per item

-          Labor cost per item

-          Overhead cost per item

Communications-Corporate

 

Symptom: Our support staff will be ‘on leave’ for the Holidays, Dec 24 & 25.

Elements:

-          Message

-          Category (hours-of-operation, safety, new-service-announcement, etc)

-          Date of applicability

Communications-Customer

 

Symptom: Release 11 of service XYZ is now available.

Elements:

-          Message

-          Category (hours-of-operation, safety, new-service-announcement, etc)

-          Date of applicability

Communications-Partner

 

 

Corporate Tax

 

 

Customer Satisfaction

Symptom: Interfaces are difficult to use in Service XYZ release 11

Elements:

-          Service identifier

-          Service description

-          Message

-          Satisfaction (excellent, good, fair, poor)

I’m thinking of this as different from SLAs.  Almost like a quality survey card.

 

 

Product Engineering/Development

 

 

Environmental Affairs

 

Internal symptom: Disposing of Server Rack 123

Elements:

-          Hardware identifier

-          Hazardous chemicals reference

 

Energy

 

symptom: Service XYZ consuming 100 KW/H of energy

-          Service identifier

-          Consumption rate

-          Consumption total

-          Energy blend

 

Facilities

 

 

Government Relations

 

 

Human Resources

 

 

Information Services (might be the same as Engineering for Cloud Provider?)

 

 

Insurance

 

 

Legal

 

 

Marketing

 

 

Purchasing

 

 

Quality Assurance

 

 

Operations/Infrastructure

 

 

 

 

 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]