RequestableOffering / RequestableOfferingBundle

Replies to This Discussion

Permalink Reply by Paul G. Huppertz on January 28, 2010 at 10:32pm

Any Requestable Service Offering in the Service Catalog, i.e. any business relevant ICT-based Business Support Service (ICTBSS) can be completely, consistently & concisely specified by means of the generic 12 standard service attributes, i.e.
01 Service Consumer Benefits
02 Service-specific Functional Parameters
03 Service Delivery Point
04 Service Consumer Count
05 Service Readiness Times
06 Service Support Times
07 Service Support Languages
08 Service Fulfillment Target
09 Maximum Impairment Duration per Incident
10 Service Delivering Duration
11 Service Delivery Unit
12 Service Delivering Price
s. http://en.wikipedia.org/wiki/Service_(economics)#Service_specification

When triggered by an authorized service consumer, each ICTBSS is aggregrated from particular service contributions which are specified with their particular 12 attributes and attribute values. Thus, each ICTEBSS is a kind of bundle of service contributions. Furthermore, several different ICTBSS's can be bundled in one combined Service Offering.

Conclusion:
By applying the service (contribution) specification with the 12 standard service attributes one can specify any service (contribution) up and down the service hierarchy with one consistent set of attributes. This method dramatically eases any service specification effort with simultaneous consideration of the service characteristics. Thus, the service specifications, the service catalog entries and the SLAs become pretty lean & handy.
s. http://en.wikipedia.org/wiki/Service_(economics)#Service_characteristics

• ▶ Reply

Permalink Reply by Toon Van Hauwermeiren on February 2, 2010 at 3:08pm

Paul,

Thank you for your reply.

I guess a bundle can be more than the sum of it's children, e.g. it could define successor/predecessor relationships among the children.

• ▶ Reply

Permalink Reply by Paul G. Huppertz on February 3, 2010 at 1:23am

Toon Van Hauwermeiren said:

Paul,

Thank you for your reply.

I guess a bundle can be more than the sum of it's children, e.g. it could define successor/predecessor relationships among the children.

Such a bundle of service contributions must be aggregated in the course of a real time transaction which is triggered by a service consumer, e.g. by hitting the 'Send' button in his e-mail client software. This service trigger must kick off the aggregation of a distinct set of service contributions which amount to rendering the bundle of e-mail service specific benefits explicitly to the triggering service consumer. In the case of an e-mail service the indispensable core and primary benefit is that one copy of the original e-mail content is delivered to each e-mailbox of the intended addressees. For effectuating this, several standard service contributions must be aggregated, e.g. one replication service for transferring the first copy of the e-mail content to the front-end e-mail server, storing services for filing the e-mail content, LDAP services for identifying the accounts related to the e-mail addresses, antivirus services for scanning the e-mail attachments, e-mail copying services, perhaps DNS services for getting valid IP addresses for required hosts and hostnames, respectively, e-mail routing services and, finally, e-mail delivering services.
All these standard service contribution can be specified once by means of the 12 standard service attributes, too. These standard specifications for standard service contributions can be reused for each & every such service contribution as the quality of these serivce contributions always must be the same independent of the service-relevant ICT system used, e.g. a DNS service must have the same qualities either being effectuated by UNIX- or Linux- or Windows-based DNS systems.

Conclusion:
There is a bundle of benefits which must be effectuated & aggregated by a sequence distinct serivce contributions or a bundle of service contributions, as you'd like to write. All services and service contributions can be clearly, completely & concisely specified by means of the 12 standard service attributes which significantly eases & reduces the efforts for specifying, conceiving, commissioning and delivering services.

• ▶ Reply

▶ Reply to Discussion