Функциональный компонент «Исполнение заявки» Fulfillment Execution Functional Component

Простыми словами

Оркестратор доставки в потоке Request to Fulfill: он выбирает механизмы исполнения, координирует их и порождает сразу два объекта данных — заявку на исполнение и желаемую услугу. Отличие от компонента «Request Rationalization»: тот разбирает заказ и ведёт подписки, а этот привлекает исполнителей и делает работу. Стандарт описывает две парадигмы использования: потребительскую, где всё начинается со связанной записи каталога, и прямой доступ, где компонент вызывает «Release Composition» потока Requirement to Deploy напрямую, минуя каталог. Именно этот компонент создаёт фактическую услугу как копию желаемой внутри «Configuration Management» и может отправить определения мониторов в поток Detect to Correct.

Определение из первоисточника

Основные параметры

Атрибуты этой сущности по справочнику источника.

• Функциональные критерии стандарта: Shall orchestrate the delivery of the various Requests amongst (one or more) fulfillment engines in order to deliver the IT service. May engage fulfillment systems that perform actions directly, or engage other systems in order to perform actions. May engage external providers in order to fulfill Subscriptions. May manage a registry of the available fulfillers to include what each fulfiller does (capabilities) and how to engage each fulfiller (where they are located and how to invoke them). May take the bound Service Catalog Entry and generate both the relevant Fulfillment Requests in order to realize/fulfill the originating consumer request and the Desired Service data object which represents the Service Model in its pre-configured or consumer-configured state. May update the IT asset inventory as they are ordered. May request standard changes and update the Configuration Management functional component (if needed) on delivery of components. Shall maintain visibility into supplier capacity levels and raise alerts if capacity appears to be insufficient for immediate demand. Shall select the appropriate fulfillment mechanism. Shall coordinate if multiple fulfillment mechanisms are needed and manage the dependencies required to fulfill the IT service Request. Shall create one or more Desired Services based on the Service Release Blueprint and associated Subscription for new service deployment Requests. Should create an associated Desired Service for all consumer Subscriptions to the service. Shall provide the Subscription status to the Request Rationalization functional component. Shall create the Actual Services as a copy of the Desired Service within the Configuration Management functional component. May create an RFC associated with the service instantiation that is created within the Change Control functional component (D2C Value Stream). The RFC type, standard or normal, is determined within the Change Control functional component. Can create a new service monitor or modify an existing one for the service provided in the Request as part of fulfillment. Can create/route a Request to an external service provider to fulfill part or all of the service. Can request IT assets necessary for fulfillment (such as licenses). This also enables the tracking of assets being requested or procured and links them with the services that require them. Can trigger deployment engines to enable fulfillment of the service. Объекты данных компонента: Fulfillment Request, Desired Service.

Связанные понятия