About Conceptual Model Actions

Design Studio includes the definitions for two action families, service and technical:

Service actions represent requests to change a customer facing service in the technical inventory. These actions are used during product-to-service mapping and during run-time design and assign activities. Service actions include a group of action codes, each of which can be performed against the associated entity.
Technical actions represent the information sent to delivery systems. Technical actions usually include a single action code.

You can create your own action families by creating additional functional areas. See "About Functional Areas" for more information.

Conceptual model entities are the targets, or subjects, of actions. You associate actions with entities to indicate that the action or group of actions can be performed against the associated entity.

You can create your own actions, or your can configure Design Studio to create actions automatically when you create new conceptual model entities. Actions that Design Studio create automatically are considered mandatory.

Customer facing services are associated with service actions only. By default, when you create customer facing services, Design Studio automatically creates a mandatory service action and associates the service action with the CFS. You can associate resource facing services and resources with one service action or with multiple technical actions.

Conceptual model service actions are realized in Design Studio for Inventory projects as rulesets. Conceptual model technical actions are realized in Design Studio for ASAP project as service actions (CSDLs) or in Design Studio for Network Integrity projects as scan actions.

See Design Studio Concepts for more information about actions.