Every Company is a Service-Oriented Company
Service Orientation has been a buzzword for ages and has led to the fact that it is common for everyone to use the word. However, that does not mean defining and designing the right service for an organization as an enterprise architect has become easy. Questions that often arise are: What are services? May they contain technical words? Does it provide external or internal business services to the business?
The benefit of working with or providing services to your customers is making their lives easier. Services are much simpler or less complex than products to use. So, the main reason for documenting your current and future services is to make your customers' lives easier, to show your added value more, and to make yourself more distinctive from competitors.
If you want an example, I can give one. Suppose you can buy a super deluxe coffee machine that can produce the best coffee ever. You only need to operate the machine in a certain way, or else the coffee is like sewage water. What if the suppliers of the coffee machine offer a 'coffee service'? Instead of making the coffee yourself, you can choose someone to make it for you on your premises. Or coffee cans with the best coffee are delivered to your house. Well, I think now you get why services make your life easier as a consumer, client or customer.
What is ArchiMate?
ArchiMate is an enterprise modelling language to model easily across layers in an enterprise. ArchiMate recognizes three layers: business, application, and technology. Several common entity classes are recognized in these layers: product, service, object, process, application, system software, and node.
What is a Service?
ArchiMate has its definition of service, and every architect has its definition of service. Here, I will provide the ArchiMate definition of service. Before you read this, you may write down your definition of service or certain types of services. So you can see how you comply with or differ with ArchiMate.
ArchiMate defines the word 'service' on its own: A service is defined as a unit of functionality that a system exposes to its environment. A service hides internal operations. A service provides a certain value (monetary or otherwise).
ArchiMate recognizes three types of business services: application services and infrastructure services.
-
A business service is a coherent piece of functionality offering value to the environment. It is independent of the way functionality is realized internally. A distinction can be made between external business services offered to customers and internal business services, which offer supporting functionality to processes within the organization.
- An application service is an externally visible unit of functionality provided by components, meaningful to the environment, and exposed via interfaces.
- An infrastructure service is defined as an externally visible unit of the functionality provided by nodes, meaningful to the environment, and exposed through interfaces.
Examples provided by ArchiMate of services are travel insurance selling, customer info processing, and messaging.
What is strange to me is how the definition of service contains elements that have to do with a type of service implementation, i.e., loosely coupled services. Infrastructure services, for instance, do not always have to be exposed through interfaces to be an infrastructure service. Networking, for instance, is an infrastructure service that is not exposed through interfaces.
Opportunities are Waiting there for You
Services allow making life easier for your external customers and your internal clients or stakeholders. It does not matter if we are talking about business, application, or infrastructure services. It applies to all types of services.
For instance, the infrastructure service of Home Computing makes the life of employees easier. Looking a bit further into your employees, you might recognize the need for dealing with certain Home Computing situations like 'Off the Grid Home Computing' or 'Abroad Home Computing'.
Suppose you live in a distant area with no phone lines (off the grid), or if you are in Europe or Australia (abroad), you still may want to do your work in your Mobile Home or on Holiday Camp. One could say these are different service levels, but the focus is on making life easier for customers and clients.
IT services are often focused on mitigating continuity risks, increasing the performance of employees, and reducing costs for the organization (which also comes down to making life easier). Examples of these kinds of services within the field of IT Service Management are Server Monitoring, Application Testing, Backup of Data, Intruder Detection Lockout, Service Desk, Follow Me Printing, and Single Sign-On. All these services increase the performance of employees using the IT Infrastructure and Information Systems.
I hope I have given you a different mindset about new services for your company.
Design Criteria for Services
If you want to design services using ArchiMate, you must write design criteria and naming conventions. Otherwise, working as a team toward a coherent set of services is hardly impossible. Also, if a reference model is available in your industry for your type of organization, it would be strange not to reuse that knowledge (wisely).
An example naming convention for service could be: A service always consists of one, two, three, or four words: a noun and a verb, a link to markets or clients, and one of the words must be a unique denominator. For example, Delivery Services, Food Delivery, Consumer Food Delivery, 24-hour Consumer Food Delivery and Marketing Services, B2B Marketing and Outbound B2B Marketing and Non-Stop Outbound B2B Marketing.
Some design criteria I suggest are:
- Make sure that the boundaries of service are defined explicitly.
- Make sure that the services are autonomous. They work independently of each other.
- Look at the units in your organization that deliver or should deliver services in your organization and create a hierarchy diagram of that.
- Look at the concerns the various units in your organization have and create a hierarchy diagram of concerns. Concerns are essential subjects, topics, or information for an entity to use or deal with, such as pain and trauma in a hospital or citizens and legislation in a municipality. Often fitting concerns for your organization can be found when considering Markets and Clients and looking at the mission, vision, and strategy.
- Now, per concern, try to define a service.
- Group the services on common aspects and then create a service hierarchy of three layers.
- Draw a rectangle and two competitors/substitutes for your organization. Write down the mission, vision, and strategy above the rectangle. Next, you place the services with unique denominators that define you in the market in your rectangle and do that exercise for your competitor. Now step back and look if service defines YOU. And if it does not, change some things: recognize other services or move services around.
- Make sure every service is documented: unique ID, author, owner, unit, concern, service level, costs, and benefits.
- In addition to the ArchiMate implementation definition of service, think of a service as the work done for or help given to someone or something: a person, animal, organization, or thing.
This set of design criteria or rules helps to know what services fit your organization. Although it is still you who has to think. As an enterprise architect, you are a designer of total concepts, so you are fit for this job by definition.
An alternative definition for Service
The Dragon1 open EA Method provides you with an alternative definition for service that does not focus on how to implement a service but is a definition that focuses on the identity and function of a service.
The Dragon1 definition for service is: Doing work for someone or something or the action of helping someone or something to make life easier, increasing focus on a core activity for someone or something.
This definition does not say how the service is implemented. This is because it does not matter how it is implemented for something to be a service. It does matter if you want loosely coupled services. However, loosely coupling is a concept that is different from services.
ArchiMate has tied the concept of 'loosely coupling' (hiding and abstraction) to the concept of service, limiting the notion of what services are.
Example Business Services in Health Care
Now let us define some common business services for a Hospital using the ArchiMate way of thinking (and a little bit of the Dragon1 Way of Thinking).
A list of external business services for the hospital would be:
- Billing Services
- Patient Billing Services
- Digital Patient Billing Services
- Automated Digital Patient Billing
- Intake Services
- Patient Intake
- Online Patient Intake
- 24/7 Online Patient Intake
- In-House Restaurant / Dining Service
- Birthday Party Service
- Parking Assistance
For some people, these services make their life easier. And that is just the meaning of service orientation.
Archimate Modelling
Here on Dragon1, you can model any ArchiMate diagram you like. And also in a unique, interactive, and animated way. We have provided a channel for you with some examples of ArchiMate Diagrams. It shows you what and how you can model ArchiMate on Dragon1.
ArchiMate Modelling Channel.
Conclusions and Recommendations
ArchiMate is an enterprise modelling language that is fit for the modelling and visualizing business services in health care.
ArchiMate provides an understandable definition for services and recognizes three usable types of services.
You need to put work into your design of services to make them show the uniqueness of your organization.
Make use of documented design criteria to support you in defining, modelling, and designing interoperable services as an individual and as a team.