The difference between capabilities and resources is something hard to discern, but that doesn’t mean it isn’t there. There are design implications because failures may be due to either aspect of the service asset. Capabilities are invisible assets and are exposed to customers only through a resource. The presence of the capability aspect may not be as obvious as that of the resource.

Air traffic management approves flights plans, tracks aircraft, and separates them from other traffic. Gates, runways, and radars are resources an airport provides for an airline to use. They are useless without the capability of traffic control, which itself is useless without the available resources. Some airports are too small to handle certain types of aircraft. Others are simply to congested or too expensive.

The scanning procedure with increasingly sophisticated software, might seem like it’s more important than the physical resource itself. But consider this, there every now and then there is a worldwide shortage of radioactive isotopes using in medical imaging. Therefore it is a scarce commodity and to perform the scanning, the hospital or clinic must also provide. There is no concept of BYOB or Bring Your Own Barium, or ride-sharing. As part of the service, patients and doctors depend on the service to have the isotope in stock, bear the costs and risks of supply not meeting demand.

Posted by:Majid Iqbal

TL;DR I bring clarity to the concept of a service.