For more information about DEAR, see the IEA Team's website.

Training courses on DEAR are available--contact the IEA Team:

• Colleen Coggins, Chief Architect
• Suzanne Acar, Data Architect
• Michael McGreer, Technology Architect
• Carl Huls, Indian Trust Architect

Deployments

Entering location and processing node information for deployments is a DEAR function; it is not part of the wizard. Instructions about deployments are included in this tutorial for convenience.

What's a deployment?

This tutorial explains how system owners can enter a server (or a cluster acting as one server), and information about where it is, into DEAR. The server's information, its location, and its relationship to a system component instance, are together called a "deployment".

Why enter deployment information?

Once this information is in DEAR, it can be analyzed in modernization blueprints to show where servers can be consolidated to save IT funds. Reports based on this information, showing where systems are and aren't related, will also help Interior show which parts of its network are not connected--so when one system has to be shut down, it doesn't affect the whole network.

Collecting deployment data

The easiest way to enter the data is to collect the inventory of locations and processing nodes in CSV files or spreadsheets, and import the files. You may be able to use existing CM data, or data from other inventories. If you don't have a CSV file, you will have to enter the data manually.

Enter all the physical locations where systems are deployed. If you share a facility with another organization, coordinate with that organization on the naming. Better yet, one organization can export the information and the other can import it.

How to enter

There are three steps:

1. Location Node: Enter the location, from a CSV file or manually.
2. Processing Node: Enter the server information, from a CSV file or manually.
3. Map to Instance: Map the server to a system component instance.