EA - IT Architecture V2 > Introduction TO HOPEX IT Architecture > Before starting with HOPEX IT Architecture > Importing components with HOPEX IT Architecture
Importing components with HOPEX IT Architecture
HOPEX IT Architecture uses Excel data exchange wizards to export import and export existing architecture components.
* 
*For more information on Excel exchange tools, see Data Exchange with Excel.
Two Excel templates are proposed:
• Hardware_Functionalities_Template.xlsx for infrastructure elements import/export : computing devices connected to the breakdown of hardware functionalities they implement.
• Technical_Functionalities_Template.xlsx for technology elements import/export : technologies connected on one side to vendors, and on the other side to the breakdown of technical functionalities they implement.
Structure of the import/export Excel templates of HOPEX IT Architecture 
HOPEX IT Architecture Exel templates that enable import of harware or technical elements are dentically presented.
• At the level hardware, the elements are as follows: Hardware, IoT Device, Server and It Device.
*An IoT device is both a hardware device and a computing device which provides cvombined hardware and information services to the users using it directly. As a hardware device, it embeds sensors - e.g. accelerometer - which provide data to the embedded computing device. As a computing device, it can host data stores or run applications. Examples: smartwatch with GPS tracker, on-line surveillance video camera with live IP video feed, connected weighting scale with weight history management
*For more details on hardware elements, see Describing a Computing Device.
• At the level of technologies, the elements are as follows: Vendor (Org-Unit) andSoftware technology.
*A software technology is a basic component necessary for operation of business applications. Software technologies include all basic software such as: application server, electronic mail server, software components for presentation, data entry, storage, business information sharing, operating systems, middleware, navigators, etc.
*For more details on technologies, see Describing a Software Technology.
• At the level of hardware of technical Capabilities, the elements are as follows:
• Hardware or technical Capabilities
*A hardware capability is the ability to deliver a physical outcome which is required by an organizational resource in order to perform its work. This hardware capability is generally necessary within a computing process in order to execute a specific operation.
• Hardware or Technical Capabilities maps,
*A technology capability map is a set of technology capabilities and their dependencies that, together, defines the scope of a hardware or software architecture.
• Sub-functionalities, which define the link between a functionality and the functionality map (or the functionality) in which it is referenced.
*For more details on functionalities, see Using Functionalities with HOPEX IT Architecture.
• Functionality fulfillments, which define the link between a functionality and the hardware or technical object that implements it.
The list of information provided for in the Excel template delivered with  HOPEX IT Architecture is presented in the following order:
• For elements of type: Hardware or technical Capability map, Computing device (IoT device, Server, It device):
• Short Name : name of the object concerned.
• Comment : object comment.
• For elements of type Technology:
• Short Name : name of the object concerned.
• Technology Code.
• Comment : object comment.
• Vendor.
• For elements of type Org Unit :
• Short Name : name of the object concerned.
• Internal/External.
• Org-Unit Type.
• Comment : object comment.
• For each element of Functionality Composition type:
• Name of the composite object: functionality map or functionality,
• Name of the owned functionality.
• For each element of Functionality Implementation type:
• Fulfilled Hardware/Technical Functionality: name of the implemented functionality.
• Name of the object (computing device or technology) that implements the functionality.
Importing computing devices or technologies with Excel 
*For more information on the structure of the Excel template, see Importing components with HOPEX IT Architecture.
If you want to export computing devices or technologies or functionality maps that exist in another repository than your current one, for example, you can use the Excel template of HOPEX IT Architecture.
Several steps must be followed in order for the Excel import of a business capability breakdown to be performed correctly:
4. Import your new file into your repository.
* 
*For more information on Excel import steps, see Importing data via Excel.
Specifying the current library 
This optional stage enables to connect imported objects to the current library.
A library and an enterprise are used to represent a unique work context.
*Libraries are collections of objects used to split repository content into several independent parts. They allow creation of virtual partitions of the repository. In particular, two objects owned by different libraries can have the same name.
In order for the data you import with Excel to be linked to a specific container, you must specify the current library.
*For more details, see Defining the Work Environment.
Exporting data from your repository with HOPEX IT Architecture 
If you want to export technical or hardware functionality maps that exist in another repository than your current one, for example, you can use the Excel template of HOPEX IT Architecture.
* 
*For more information on Excel import steps, see Exporting Data via Excel.
When the Excel file is filled with the names of the objects you want to import, you must complete the necessary information for import into HOPEX IT Architecture.
Completing the import file for HOPEX IT Architecture 
To get a correct import/export file, you must have specified the following elements:
• For each element of type hardware or technical capability map, hardware or technical functionality map, Vendor, Technology, (IT, Server, connected device) Computing device, you must enter the name of each object.
• For each breakdown (Technical Function_Composion or Functionality Composition Excel sheet), you must indicate:
• The name of the composite object: functionality map or functionality,
• The name of the owned functionality.
• To specify that a technology implements a functionality for example, you must indicate in the Technical Function_Fulfillment sheet:
• the name of the functionality implemented in the Fulfilled Hardware/Technical Functionality column.
• Name of the object (computing device or technology) that implements the functionality.
*The first two lines of each Excel worksheet are reserved for file configuration; ensure that the first two lines of the imported file remain identical to those obtained after an export.
*For more information on the structure of the Excel template, see Structure of the import/export Excel templates of HOPEX IT Architecture.