A conceptual model includes the following entities:
Customer facing services, which represent your services from a customer perspective. See "About Customer Facing Services" for more information.
Resource facing services, which represent a technical view of a service. See "About Resource Facing Services" for more information.
Resources, which represent the entities that are required to configure the service. See "About Resources" for more information.
Products, which represent your commercial products. See "About Products" for more information.
Locations, which represent physical locations. For example, in a Broadband service, the DSL RFS for a DSL service can be associated with a location to represent the address of the customer.
Actions, which are requests to perform work. Actions describe how conceptual model entities change, cause change, or retrieve information. Actions are associated with customer facing services, resource facing services, and resources. See "About Conceptual Model Actions" for more information.
Domains, which are groups of entities and actions that you can use to organize and filter conceptual models. See "About Domains" for more information.
Functional areas, which are the logical layers of an installation and can be commercial, service, and technical layers. These layers are supported by an Order and Service Management order type or by an external order management system. See "About Functional Areas" for more information.
Provider functions, which are processing components that perform a defined set of tasks based on their role in a solution. Design Studio Modeling Basics includes the configuration for some provider functions, such as Calculate Service Order, Design and Assign, Calculate Technical Order, and Activation. See "About Provider Functions" for more information.
Fulfillment patterns, which determine the high-level functions that are required (and in what order) to process an action or conceptual model entities. See "About Fulfillment Patterns" for more information.