---
title: Test Study for a Network Information Management System Electric Utility (PostgreSQL)
description: Test study for a Network Information Management System electric utility in AWS on PostgreSQL
content_type: test-studies
source_url: "https://architecture.arcgis.com/en/architectures/network-information-management-electric-postgresql/physical-architecture.html"
md_url: "https://architecture.arcgis.com/en/architectures/network-information-management-electric-postgresql/physical-architecture.md"
---
# Physical architecture
This architecture was evaluated in January 2023 with:
- A small-medium electric utility in mind
- Support for [electric utility workflows](tested-workflows.md) with a target design load as described in the [test methods](test-results.md) section
- An enterprise geodatabase configured with PostgreSQL
- AWS cloud infrastructure

The system was designed for and [tested](tested-workflows.md) against the specified workflows, with adjustments to the machine types and sizes as needed based on test results.


![Physical architecture for a Network Information Management System: Electric Utility (PostgreSQL)](https://architecture.arcgis.com/assets/images/test-studies/nims-wl-electric-postgresql.png "Physical architecture for a Network Information Management System: Electric Utility (PostgreSQL)")

_Download a [Microsoft Visio file](/assets/diagrams/nims-wl-electric-postgresql.vsdx) of this architecture._ 
_Learn more about [diagramming resources](/en/framework/architecture-practices/architectural-foundations/diagramming-resources.md) for ArcGIS systems._

> [!NOTE]
> **Note**
> For more information on the software components and key interactions in this architecture, review the Network Information Management System [reference architecture](/en/architectures/network-management/logical-reference-architecture.md).
# Resourcing the architecture
 These are the machine sizes chosen and validated for this test study. It is still highly recommended that you go through a design process yourself to account for your business and technical requirements.

## Machine types and sizes
The following represent the machine sizes chosen and validated for the scope and purpose of this test study. However, it is highly recommended to follow a complete design process to account for your business and technical requirements.

Esri offers [system architecture design](https://www.esri.com/en-us/arcgis/services/consulting) services should you need help determining all of the different factors relating to your organization's physical design, such as networking, storage, system environments, and sizing. Minimum system requirements for each component are listed in [documentation available online](https://doc.arcgis.com/en/).

#### Desktop (ArcGIS Pro & web browser)

| Spec | Value |
|---|---|
| Machines | 3 |
| G4DN.2xlarge | |
| CPU | 4 CPU (8 vCPU) |
| RAM | 32 GB |
| GPU | 16 GB |
| Storage | 1 TB |


#### Portal for ArcGIS 

| Spec | Value |
|---|---|
| Machines | 2 |
| M6i.xlarge | |
| CPU | 2 CPU (4 vCPU) |
| RAM | 16 GB |
| Storage | 128 GB |


#### ArcGIS GIS Server 

| Spec | Value |
|---|---|
| Machines | 2 |
| M6i.2xlarge | |
| CPU | 4 CPU (8 vCPU) |
| RAM | 32 GB |
| Storage | 128 GB |


#### ArcGIS Server (hosting server) 

| Spec | Value |
|---|---|
| Machines | 2 |
| M6i.2xlarge | |
| CPU | 4 CPU (8 vCPU) |
| RAM | 32 GB |
| Storage | 128 GB |


#### ArcGIS Data Store (relational) 

| Spec | Value |
|---|---|
| Machines | 2 |
| M6i.xlarge | |
| CPU | 2 CPU (4 vCPU) |
| RAM | 16 GB |
| Storage | 128 GB |


#### ArcGIS Web Adaptor

| Spec | Value |
|---|---|
| Machines | 2 |
| M6i.large | |
| CPU | 1 CPU (2 vCPU) |
| RAM | 8 GB |
| Storage | 128 GB |


#### ArcGIS Monitor 

| Spec | Value |
|---|---|
| Machines | 1 |
| M6i.2xlarge | |
| CPU | 4 CPU (8 vCPU) |
| RAM | 32 GB |
| Storage | 128 GB |


#### File storage 

| Spec | Value |
|---|---|
| Machines | 1 |
| C6i.xlarge | |
| CPU | 2 CPU (4 vCPU) |
| RAM | 8 GB |
| Storage | 128 GB |


#### Database 

| Spec | Value |
|---|---|
| Machines | 1 |
| M6i.4xlarge | |
| CPU | 8 CPU (16 vCPU) |
| RAM | 64 GB |
| Storage | 1 TB |


#### Domain server

| Spec | Value |
|---|---|
| Machines | 1 |
| C6i.large | |
| CPU | 1 CPU (2 vCPU) |
| RAM | 4 GB |
| Storage | 128 GB |


# Additional infrastructure considerations
The following are additional areas of consideration when designing a Network Information Management System and an explanation of some infrastructure choices made for this test study.

### Application load balancer (ALB)
At least one third-party load balancer is required in a highly available ArcGIS Enterprise deployment to handle client traffic to portal and server sites as well as internal traffic between the software components. Although the ArcGIS Web Adaptor is considered a load balancer, it is insufficient on its own to serve as a load balancer in a [high availability](/en/framework/architecture-pillars/reliability/high-availability.md) configuration. Therefore, in this test study, an Amazon Web Services (AWS) Application Load Balancer was used.

### Shared storage
To successfully implement a highly available ArcGIS Enterprise deployment, the configuration stores must be stored in a highly available, shared location. This ensures this data remains accessible even if one server fails, providing uninterrupted service to end-users. Additionally, shared storage simplifies data management in a multi-machine deployment and improves scalability by centralizing data storage and allowing for expansion as needed.

### System components not included in the diagram
While antivirus software and AWS networking components are not illustrated in this diagram, they were present in the test study.