Building a Hybrid Functional Reference Architecture – Part 5 – Service Fulfillment Design


In my last podcast, I talked about the Service Capability Design of Requirement to Deploy, let’s now focus on the Service Fulfillment Design, in other words the development of the automation required to make the service available to the end-user. Whether the service is developed internally, intermediated or aggregated, it requires some interaction with the Hybrid Management Platform to be provisioned, de-provisioned, changed etc. This is the automation we talk about here. Starting with the role of the service offer manager, we describe what is required at each of our three levels to enable the service to be accessible by the user.

FRA6

We also describe the data stores in the demand and the supply layer that are central to the architecture itself. By the end of this podcast we have a service that is referenced in the service catalog and available to specific users. The next podcast will focus on the user and how he/she requests a service. Have a great listening.

One Reply to “Building a Hybrid Functional Reference Architecture – Part 5 – Service Fulfillment Design”

Tell me what is going through your mind.

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

w

Connecting to %s