Describing Resource Architectures
*A resource architecture is the combination of physical and organizational assets configured to supply a capability.
To create a resource architecture from the Infrastructure navigation pane:
1. Select Resource Architecture and click Resource Architecture tab.
The list of resource architectures appears.
2. Click New.
The Creation of a Resource Architecture window opens.
3. Enter the Name of your architecture as well as its Owner and click OK.
The new resource architecture appears in the list.
Creating a Resource Architecture Assembly Diagram: 
To create a Resource Architecture Assembly Diagram:
1. Right-click the resource architecture that interests you and click Create Diagram.
2. Select Resource Architecture Assembly Diagram.
The diagram opens in the edit area. The frame of the described resource architecture map appears in the diagram.
Using a Resource Architecture Assembly Diagram
Adding a Resource Architecture 
To describe that a resource architecture, such as a “call center”, implements another resource architecture, such as a “customer management service”, for example, you will add the resource architecture used in the user resource architecture diagram.
To add a resource architecture to a Resource Architecture Assembly Diagram:
1. In the objects toolbar of the Resource Architecture Assembly Diagram, click Resource Architecture.
2. Click in the frame of the Resource Architecture Assembly Diagram.
An addition dialog box prompts you to select a resource architecture. You can select an existing resource architecture or create a new one.
*To create a new resource architecture, simply enter its name.
3. Click OK.
Adding an Org-Unit or a Position Type 
*An org-unit represents a person or a group of persons that intervenes in the enterprise business processes or information system. An org-unit can be internal or external to the enterprise. An internal org-unit is an organizational element of enterprise structure such as a management, department, or job function. It is defined at a level depending on the degree of detail to be provided on the organization (see org-unit type). Example: financial management, sales management, marketing department, account manager. An external org-unit is an external entity that exchanges flows with the enterprise. Example: customer, supplier, government office.
*A position type represents a status assigned to an individual or a group of individuals with the aim of defining an organization or a hierarchy.
To describe that a Resource Architecture such as a call center uses operators to take calls and handle requests, you will create a Position Type component.
To add a Position Type to a Resource Architecture Assembly Diagram:
1. In the objects toolbar of the Resource Architecture Assembly Diagram, click Position Type.
2. Click in the frame of the resource architecture described.
An addition window prompts you to choose the Position Type that you wish to use:
3. Select the Position Type concerned and click OK.
The Position Type appears in the diagram.
*To create a Position Type, simply enter its name.
*In the same way, you can add an org-unit in the Resource Architecture Assembly Diagram.
Adding an IT infrastructure
To describe that a resource architecture is based on IT resources such as a communication network, workstations housing applications, you will add IT Infrastructure type components to the Resource Architecture Assembly Diagram.
*An IT infrastructure is made up of different hardware components such as: IoT and IT devices, computers or IT networks.
To create an IT Infrastructure:
1. In the diagram objects toolbar, click IT Infrastructure.
2. Click in the diagram frame.
An addition dialog box prompts you to select the IT infrastructure to be deployed.
3. Select the IT infrastructure that interests you and click OK.
The IT infrastructure appears in the diagram.
*To create an IT infrastructure type, simply enter its name.
*In the same way, you can add another hardware resource in the Resource Architecture Assembly Diagram. For more details on hardware resources, see Describing IT Infrastructures.
Channels and communication ports
In a resource architecture, communication channels support the transfer of information from one hardware asset to another. For more details on creation of these channels and the associated communication protocols, see Communication channels.
Communication ports enable connection of resource architecture physical assets with external equipment elements.
Describing Interaction in a Resource Architecture Assembly Diagram 
In a resource architecture assembly diagram, Interactions enable representation of exchanges between organizational entities for services fulfillment.
*An interaction represents a contract established in a specific context between autonomous entities that are internal or external to an enterprise. These entities can be enterprise org-units, applications, activities or processes, as well as external org-units. The content of this contract is described by an exchange contract.
Exchange terms are defined by an Exchange contract assigned to the interaction.
*An exchange contract is a model of a contract between organizational entities. This contract is described by exchanges between an initiator role and one or several contributor roles.
You can define interactions between:
Two components of resource architecture type to represent exchanges between these entities,
A component of resource architecture type and an IT infrastructure to represent the terms of use of the equipment resource by the organizational resource. For example, you can represent that operator hardware use is arranged by booking.
two components of IT infrastructure type to represent the terms of use of one IT resource by another in the context of the modeled resource architecture.
a service point and one or more resource architecture type components to represent implementation of the service within the resource architecture,
A component of architecture use type and a request point to represent that the entity calls a resource of an external organization.
*For further details, see Interactions.
Describing the Services in a Resource Architecture Assembly Diagram 
A resource architecture is created to assure one or several services.
Expected and realized services are represented by:
service points
*A service point is a point of exchange by which an agent offers a service to potential customers.
request points
*A request point is a point of exchange by which an agent requests a service from potential suppliers.
*For more details, see Service points and Request points.