# Understanding complete assessment data requirements
<a name="understanding-complete-assessment-data-requirements"></a>

The following table describes the information required to obtain a complete portfolio view of the applications in the migration and their associated infrastructure.

The tables use the following abbreviations:
+ R, for required
+ O, for optional
+ N/A, for not applicable

**Applications**


| **Attribute name** | **Description** | **Inventory and prioritization** | **Detailed Business case** | **Recommended fidelity level (minimum)** | 
| --- | --- | --- | --- | --- | 
| Unique identifier | For example, application ID. Typically available on existent CMDBs or other internal inventories and control systems. Consider creating unique IDs whenever these are not defined in your organization. | R | R | High | 
| Application name | Name by which this application is known to your organization. Include commercial off-the-shelf (COTS) vendor and product name when applicable. | R | R | High | 
| Is COTS? | Yes or No. Whether this is a commercial application or internal development | R | R | High | 
| COTS product and version | Commercial software product name and version  | R | R | High | 
| Description | Primary application function and context | R | R | High | 
| Criticality | For example, strategic or revenue-generating application, or supporting a critical function | R | R | High | 
| Type | For example, database, customer relationship management (CRM), web application, multimedia, IT shared service | R | R | High | 
| Environment | For example, production, pre-production, development, test, sandbox | R | R | High | 
| Compliance and regulatory | Frameworks applicable to the workload (for example, HIPAA, SOX, PCI-DSS, ISO, SOC, FedRAMP) and regulatory requirements | R | R | High | 
| Dependencies | Upstream and downstream dependencies to internal and external applications or services. Non-technical dependencies such as operational elements (for example, maintenance cycles). | R | O | High | 
| Infrastructure mapping | Mapping to physical and/or virtual assets that make up the application | R | R | High | 
| License | Commodity software license type (for example, Microsoft SQL Server Enterprise) | R | R | Medium-high | 
| Cost | Costs for software license, software operations, and maintenance | N/A | R | Medium-high | 
| Business unit | For example, marketing, finance, sales | R | R | High | 
| Owner details | Contact information for application owner | R | R | High | 
| DR information | Disaster recovery components | R | R | High | 
| Migration strategy | For example, one of the 6 Rs for migration to AWS | R | R | High | 
| Support tickets | 12–24 months of data to help assess the productivity and financial impact of outages, slow downs, transaction throttling, and batch window overruns | O | R | Medium | 

**Infrastructure**


| **Attribute name** | **Description** | **Inventory and prioritization** | **Business case** | **Recommended fidelity level (minimum)** | 
| --- | --- | --- | --- | --- | 
| Unique identifier | For example, server ID. Typically available on existing CMDBs or other internal inventories and control systems. Consider creating unique IDs whenever these are not defined in your organization. | R | R | High | 
| Network name | Asset name in the network (e.g., hostname) | R | R | High | 
| DNS name (fully qualified domain name, or FQDN) | DNS name | R | O | High | 
| IP address and netmask | Internal and/or public IP addresses | R | R | High | 
| Asset type | For example, physical or virtual server, hypervisor, container, device, database instance | R | R | High | 
| Product name | Commercial vendor and product name (for example, VMware ESXi, IBM Power Systems, Exadata) | R | R | High | 
| Operating system | For example, REHL 8, Windows Server 2019, AIX 6.1 | R | R | High | 
| Configuration | Allocated CPU, number of cores, threads per core, total memory, storage, network cards | R | R | High | 
| Utilization | CPU, memory, and storage peak and average. Database instance throughput. | R | R | High | 
| License | Commodity license type (for example, RHEL Standard) | R | R | High | 
| Is shared infrastructure? | Yes or No to denote infrastructure services that provide shared services such as authentication provider, monitoring systems, backup services, and similar services | R | R | High | 
| Application mapping | Applications or application components that run in this infrastructure | R | R | High | 
| Cost | Fully loaded costs for bare-metal servers, including hardware, maintenance, operations, storage (SAN, NAS, Object), operating system license, share of rack space, and data center overheads | N/A | R | Medium-high | 
| Estimated volume of data transfer (in/out) | For example, per infrastructure asset over per day over a 30 days period  | O | R | Medium | 

**Networks**


| **Attribute name** | **Description** | **Inventory and prioritization** | **Business case** | **Recommended fidelity level (minimum)** | 
| --- | --- | --- | --- | --- | 
| Size of pipe (Mb/s), redundancy (Y/N) | Current WAN link specifications (for example, 1000 Mb/s redundant) | R | R | Medium-high | 
| Link utilization | Peak and average utilization, outbound data transfer (GB/month) | R | R | Medium-high | 
| Latency (ms) | Current latency between connected locations. | R | O | High | 
| Cost | Current cost per month | N/A | R | Medium-high | 

**Migration**

[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/prescriptive-guidance/latest/application-portfolio-assessment-guide/understanding-complete-assessment-data-requirements.html)