Solicitation Attachment 4 - Solicitation PWS Reference 002-IPPS-A Technical Environment Designs-26 OCT 2023.pdf

UNCLASSIFIED//FOR OFFICIAL USE ONLY

Integrated Personnel and Pay System – Army (IPPS-A)

Environmental Designs (ED)

21 October 2019

IPPS-A Environmental Design v1.15 21 October 2019 i

REVISION HISTORY

ii

Table of Contents Contents 1 Introduction and Purpose

1.1 Introduction

1.2 Document Purpose

1.3 Document Overview

1.4 Reference Documents

2 Background

2.1 Legacy Systems and IPPS-A

2.2 Data Centers

3 Applications

4 IPPS-A Environmental Design and Data Center Architectural Overview

4.1 Hierarchical Framework

4.1.1 Sites

4.1.2 Zones

4.1.3 Enclaves

4.1.4 Application Stacks

4.1.5 Environments

4.2 Environmental Systems Management and Change Control

4.2.1 Service-Level Agreements (SLAs)

4.2.1.1 DISA

4.3 Site High-Level Design

4.3.1 IPPS-A Increment II SDC

4.3.1.1 DISA DATA CENTER 2 Enclaves/Environments

4.3.2 IPPS-A Increment II PDC

4.3.2.1 IPPS-A Increment II Production Data Center Enclaves/Environments

4.3.3 SuperCluster Capacity Planning

4.3.4 Hardware and Software inventory

5 IPPS-A Increment II Environment Prerequisites

5.1 Data Center Remote Access

5.2 Software Download Capability

Appendix A: Acronyms and Abbreviations ............................................................................. A-1

Appendix B: Consolidated Reference Documents ....................................................................B-1

Appendix C: Reference Terms ..................................................................................................C-1 iii

List of Figures

Figure 3-1 Software Architecture

Figure 4-1 Application Stack Example

Figure 4-2 Server to Environment Mapping Example

Figure 4-3 DISA Dev (Zone B) Environment Requirements

Figure 4-4 DISA Test (Zone A) Environment Requirements

Figure 4-5 DISA SDC/COOP Environment Requirements

Figure 4-6 DISA PDC Environment Requirements

Figure 4-7 Environments by Enclave

Figure 4-8 Zone B Development and Tools Enclaves/Environments

Figure 4-9 Zone A Test and Demonstration Enclave/Environments

Figure 4-10 Secondary Data Center/COOP Production/Training Enclave/Environments

Figure 4-11 R3 Secondary Production/COOP Enclaves/ Environments

Figure 4-12 Primary Data Center (PDC)Production/Reporting and Training Enclaves/ Environments

Figure 4-13 XXXX Capacity Planning

Figure 4-14 Test SuperCluster XXXX Capacity Planning

Figure 4-15 XXXX SuperCluster Capacity Planning

Figure 4-16 XXXX Capacity Planning

Figure 4-17 XXXX Capacity Planning

Figure 4-18 XXXX Capacity Planning

Figure 4-19 XXXX Capacity Planning

List of Tables

Table 1-1 Reference Documentation

1 INTRODUCTION AND PURPOSE

1.1 Introduction

The Army currently relies on more than 60 separate legacy information systems to provide personnel and pay management for all components (Active, Guard, and Reserve). These systems were designed at different times, reside on different hardware platforms, use a variety of in-house and commercial software, and vary widely in their functionality.

To consolidate these systems, the Army is developing and implementing the Integrated Personnel and Pay System – Army (IPPS-A), a Web-based tool, available 24 hours a day, accessible to Soldiers, Human Resources (HR) professionals, Combatant Commanders, personnel and pay managers, and other authorized users throughout the Army.

1.2 Document Purpose

The purpose of this document is to provide the design of the servers and environments, the functionality of the software components, and a list of hardware and software to support those capabilities for IPPS-A Increment II Prototype, Development, Test, Support Tools, and Primary/ Secondary Production enclaves. The document is intended to show the enterprise IPPS-A Increment II architecture in relation to software and hardware, as well as high-level processes critical to the program. It is not a detailed procedural guide. The hardware and software list is complete as of the delivery of this document, but changes to these configuration items are expected and this document is updated accordingly.

This document describes the environment within the Development/Test/Secondary Data Center (SDC) Hosting Center, and the Increment II Primary Data Center (PDC).

A detailed itemization of tasks to be performed to instantiate each environment is not included in this document; however, it is incorporated into the IPPS-A Increment II Integrated Master Schedule (IMS).

Although this document is a Quality Assurance Surveillance Plan (QASP) deliverable, it should be considered a living document that can be updated during post-analysis phase activities.

A Code Migration Plan is covered in the Configuration Management Plan.

1.3 Document Overview

This document contains a brief overview of the technical architecture for the IPPS-A Increment II system. This includes a high-level view of the environments hosted at the IPPS-A Increment II PDC at the Defense Information Systems Agency (DISA) Data Center in DATA CENTER 1; the IPPS-A Increment II SDCs at the DISA Data Center in DATA CENTER 1.

This document is designed for the following audiences:

• IPPS-A Stakeholders – Reference for technical components.

• Architects – Reference for the implementation of a specific architectural component covered in this document.

• Managers – Reference to gain an understanding of the technical approach.

• Administrators – Framework for the design approach and for knowledge transfer purposes.

This document defines and describes the IPPS-A Increment II Data Center’s infrastructure prerequisites and environments, which are implemented as part of IPPS-A Increment II activities to meet the requirements of the IPPS-A program. The infrastructure components discussed in this document may be used for future program releases as defined in technical architecture specifications of future releases. This document is revisited over the course of the project life cycle to confirm accuracy and reflect changes in design.

A high-level overview of the IPPS-A Increment II Data Center infrastructure is captured in this document and includes the following:

• Logical view of the environments

• Physical view of the servers, storage, and network

• Server and virtual machine (VM) specifications

• Environment prerequisites

• Application overviews to provide a basis of functionality within the environments

• Hardware and software inventory lists

• References to the applicable IPPS-A Functional Baseline

1.4 Reference Documents

Table 1-1 contains a list of cited references and supporting material used in the development of this document.

Table 1-1 Reference Documentation

Document Title Date

2 BACKGROUND

2.1 Legacy Systems and IPPS-A

Overall, Army legacy personnel and pay systems vary greatly in modernity, maintainability, and functionality, resulting in deficiencies that cause numerous processing errors, manual workarounds, and increasing processing costs. In addition, they are based on Component-unique business practices that manage Component-unique data. Some interfaces have been operating for decades on what is now obsolete hardware. The difficulty in integrating the Army’s Component-unique data elements into meaningful information presents problems in monitoring deployments, responding to needs of family members, and implementing personnel and pay policies.

The Army employs a hybrid solution for IPPS-A using Enterprise Resource Planning (ERP) software and Agile development to deliver integrated personnel and pay capabilities, building on the trusted database and PeopleSoft foundation delivered as IPPS-A Increment I (see Increment I Technical Architecture Specification Documentation). Increment II utilizes the current versions of PeopleSoft (version 9.2) and Oracle RDBMS (version 12c or higher) along with application technologies outside of the core ERP, to meet user requirements for the total system. IPPS-A is developed and deployed incrementally, delivering full integrated personnel and pay management functionality gradually in the form of multiple releases. As such, current versions are subject to change.

IPPS-A is a combination of Agile, Modular, and traditional engineering methodologies in its development with the SI. The IPPS-A Project Management Office (PMO) and SI determine which methodology is the best fit for each activity. For example Agile development lends itself to requirements and third-party applications development and design; Modular development methodology lends itself to PeopleSoft Fit/Gaps, data management, design, and traditional engineering can best be used for the network and system design.

2.2 Data Centers

The IPPS-A Increment II Primary and Secondary Data Centers and the Prototyping/ Demonstration Hosting Center are geographically segregated: the Increment II PDC is hosted at the DISA Data Center in DATA CENTER 1 and provides Primary Production, Reporting, and Training Environments; the Increment II SDC is hosted at the Data Center in DATA CENTER 2 and provides Development, Test, and Continuity of Operations Plan (COOP) environments.

3 APPLICATIONS

Applications necessary to support the IPPS-A Increment II solution including the commercial off-the-shelf (COTS) business software packages include, but are not limited to:

REMOVED See RFP for most current list of applications

Figure 3-1 provides a Software Architecture. The current version of this figure is accessible on SharePoint at Software Architecture.

Figure 3-1 Software Architecture

4 IPPS-A ENVIRONMENTAL DESIGN AND DATA CENTER ARCHITECTURAL

OVERVIEW

This section provides a brief overview of the technical architecture for the IPPS-A Increment II system and the high-level view of the components at the IPPS-A Increment II hosting centers.

The IPPS-A Increment II hosting data centers include the PDC at DISA’s Data Center in DATA CENTER 1; the IPPS-A Increment II SDC at DISA’s Data Center in DATA CENTER 2.

4.1 Hierarchical Framework

The organization of the IPPS-A system environmental design is identified in a tiered structure.

Within the structure are defined layers. These levels include sites, zones, enclaves, application stacks, and environments.

4.1.1 Sites

The first tier of the environmental design is the site level. The term sites refers to the hosting data center that fulfills specific requirements for phases of the Software Development Life Cycle (SDLC). The current sites include:

• DISA DATA CENTER 2 Data Centers The purpose of the infrastructure at DISA DATA CENTER 2 is to support enclaves and environments for Development, Demonstration, Test, and R2 COOP activities.

• DISA DATA CENTER 1 Data Center

− DISA DATA CENTER 1 infrastructure hosts enclaves and environments to support primary transactional, reporting, and training activities.

4.1.2 Zones

According to the DISA Test and Development Enclave STIG dated 22 January 2016, a zone breakdown has been developed to establish the security baselines, which must be in place for each test and development environment. DISA has identified zones for various types of activities. For IPPS-A Increment II, two of these zones are utilized to support the SDLC.

• Zone A. IPPS-A utilizes Zone A to support its Test enclave and the environments contained within that enclave. The following is an extract from the Enclave STIG. Acronyms are identified in Appendix A. According to the Enclave STIG:

− “The Zone A environment is typically configured as a mirrored operational network for final end stage testing. This environment will have connectivity to the live operational network for final data testing prior to the product or application deployment into the operational network.”

− “Since the Zone A environment mimics the operational network, the supporting infrastructure will comply with all applicable Department of Defense (DoD) policy and security requirements. Prior to being granted connectivity, it will go through a risk assessment for the Connection Approval Process. The environment is required to hold at minimum, an IATO for connectivity to the Defense Information Systems Networks (DISN) or other live operational network within the DoD. An Interim Authority to Test

(IATT) may be obtained where the test environment requires testing of live operational data that cannot be mirrored or make use of sanitized data. The Information Security System Manager (ISSM) will conduct a security risk assessment for the requested IATT approved by the Authorizing Official (AO).”

• Zone B. The IPPS-A Development enclave, Release 2 sustainment, Release 3 – 4, and dot development environments contained within that enclave, and a subset of support tools will be implemented within Zone B. The following is an extract from the Enclave STIG.

Acronyms are identified in Appendix A. According to the Enclave STIG:

− “Zone B follows and is similar to Zone A from a network connectivity perspective, but with much stricter control mechanisms in the infrastructure supporting the environment.”

− “The Zone B environment is the designated zone permitting connectivity for moving sanitized data for testing purposes along with development of applications destined for a live and operational DoD network. The environment will have an IA-compliant infrastructure where it is separated from other test and development zones through the use of a firewall. Network segmentation is important in the environment because there will be areas where development and testing of products will take place with systems that will not be IA compliant. Network segments where development systems need access to tools or information outside of the environment will need to transit through a test and development DMZ for both inbound and outbound traffic. Network segments with systems that are not IA compliant will have all traffic blocked at the T&D DMZ. Non-compliant designated network segments within the environment will not have access to any systems on network segments or other designated segments used in development since the network segments will have access to the Defense Information System Network (DISN) through the T&D DMZ. An Active Directory solution has been requested and is being implemented within Zone B to accommodate Windows Tools servers. Requirements for Zone B ESM and EBN services have been requested from DISA however solutions have not yet been approved for operation within Zone B.”

The SDC/COOP and Production enclaves and their associated environments are hosted in a network segmentation boundary not defined as a zone, but simply as Production. Like Zone A, the supporting infrastructure complies with all applicable DoD policy and security requirements.

Prior to being granted connectivity, it goes through a risk assessment for the Connection Approval Process. A Support Tools Enclave is implemented in COOP to support Production, COOP, and Zone A environments.

4.1.3 Enclaves

Enclaves are defined as a group of environments logically segmented to support a defined phase of the SDLC. These phases include Development, Testing, SDC/COOP, and PDC. Additional Tools enclaves have been identified within the various sites and zones that support the capabilities of one or more enclaves. These capabilities include but are not limited to program support tools, such as monitoring, performance testing, log aggregation, and remote access. The planned IPPS-A Increment II enclaves are as follows:

• Development (DISA DATA CENTER 2, Zone B.) – Enclave supports environments necessary to conduct releases 3, 4 and dot release development activities for the IPPS-A Increment II system (one enclave per release).

• Support Tools (DISA DATA CENTER 2, Zone B) – Enclave hosts remote access Operational Environments (OEs) necessary to support the Zone B Development enclave.

• Test (DISA DATA CENTER 2, Zone A) – Enclave supports environments necessary to provide Development that requires PII, Product Level Testing (PLT), Demonstrations, and Production Staging for releases 2, 3, 4 and dot releases of the IPPS-A Increment II system (one enclave per release).

• Support Tools (DISA DATA CENTER 2, COOP) – Enclave hosts remote access and program support tools OEs necessary to support the COOP/SDC, and Zone A enclaves. The enclave also provides the primary program support tools capabilities such as OEM, HP Performance Center, Cameo, HP ALM, Splunk, Stonebranch Universal Controller, Stat, Teamforge, and UCMDB.

• SDC/COOP (DISA DATA CENTER 2, Production) – Enclave supports Releases 2 and 4 SDC Transactional, Reporting, and Training environments necessary to provide SDC/COOP capabilities for the IPPS-A Increment II system.

• ITE2-C - Enclave supports R3 SDC Transactional, Reporting, and Training environments necessary to provide SDC/COOP capabilities for the IPPS-A Increment II system.

• PDC (DISA DATA CENTER 1, Production) – Enclave supports PDC and Training environments necessary to provide PDC production capabilities for the IPPS-A Increment II system.

• ITE2 - Enclave supports R3 PDC Transactional, Reporting, and Training environments necessary to provide Primary capabilities for the IPPS-A Increment II system.

• Support Tools (DISA DATA CENTER 1, Production) – Enclave hosts remote access and program support tools OEs necessary to support the PDC enclave.

4.1.4 Application Stacks

The term Application Stack represents a set of servers (OEs) and associated application(s) that provide the capabilities of the application(s) (i.e., HCM Web, Application, and Batch) to environments. In an application stack, multiple environments can be supported by configuring those servers to support multiple environments through the use of domains, instances, or projects and pointing each domain/project at separate databases. Application stacks are used to increase the efficiency of servers, while reducing maintenance and licensing costs.

Each enclave is designed with the number of application stacks necessary to support the number of environments.

Figure 4-1 provides an example of how application stacks are used. This figure is accessible on SharePoint at Application Stack Example.

Figure 4-1 Application Stack Example

Figure 4-2 provides an example of how servers support multiple environments. This spreadsheet associated with this figure is accessible on SharePoint at Server to Environment Mapping example

Figure 4-2 Server to Environment Mapping Example

4.1.5 Environments

An environment is supported by application stacks, databases, and configurations that meet a predefined requirement and/or deliver a predefined capability (i.e., Core, Data, Payroll, and Security). Each enclave has environments identified based on the requirements of the requester.

The document that captures the environment requirements by site/enclave is accessible on SharePoint at Environment Requirements. The purpose of the environments may change to satisfy the needs of IPPS-A development and deployment.

Figure 4-3 identifies the requirements for development (Zone B) environments hosted at DISA

DATA CENTER 2.

Figure 4-3 DISA Dev (Zone B) Environment Requirements

Figure 4-4 identifies the requirements for Test (Zone A) environments hosted at DISA DATA

CENTER 2.

Figure 4-4 DISA Test (Zone A) Environment Requirements

Figure 4-5 identifies the requirements for SDC/COOP environments hosted at DISA DATA

CENTER 2.

Figure 4-5 DISA SDC/COOP Environment Requirements

Figure 4-6 identifies the requirements for Production environments hosted at DISA DATA

CENTER 1.

Figure 4-6 DISA PDC Environment Requirements

Figure 4-7 identifies the environment build status by site and enclave. The current version of this figure is accessible on SharePoint at Environments by Enclave.

Figure 4-7 Environments by Enclave

Institutional (and Self- Development/

Qualif ication) Training

HCM

CRM

OBIEE

OBIA/ODI

OAM/OIM

OUD

OHS

Informatica Gradkell

HCM

CRM

ELM

OBIEE

OBIA/ODI

Ab Initio

OAM/OIM

OUD

ESB

OHS

Informatica Gradkell

Config Baseline

HCM

CRM

ELM

OBIEE

OBIA/ODI

Ab Initio

OAM/OIM

OUD

ESB

OHS

Informatica Gradkell

Integrated Test

(PLT) SSO/CAC

Data Configuration

HCM

Ab Initio

ESB

Data Test

HCM

Ab Initio

ESB

HCM

ELM

OBIEE

OBIA/ODI

OAM/OIM

OUD

OHS

Informatica Gradkell

Operational Training

DISA Data Center 2 PDC

KEY

DISA Data Center 1 Zone B Enclave DISA Data Center 1 Zone A Enclave

AMRDEC

Release 2 Development Enclave (App & OS STIG)

DISA Data Center 1 SDC/COOP

ALTESS

Release 2 Fit/Gap

Increment 2 Environments Build Status

UNCLASSIFIED

Last Updated: 09/24/2019

Support Tools

HP ALM

Cameo

Iris Intelligence SharePoint

PeopleTools TOAD/SQL Dev

Putty Ultra Edit/ Compare

Fit/Gap

HCM

Portal

CRM

ELM

OBIEE

Ab Initio

UPK

OPA

Release 2 AMRDEC Support Tools R2 SDC – Transactional

SDC – Reporting/Training

XXX02 IOE: 1/09/17

XXX06 IOE: 2/14/17

R2 PDC – Transactional

XXX03 IOE: 3/22/17

PDC – Reporting/Training

XXX04 IOE: 3/30/17

Primary Reporting

OBIEE

OBIA/ODI

R3 Reporting/Training (DIT/Prod)

R3 Transactional (DIT/Prod) XXX11 IOE: 10/15/18

XXX05 IOE: 10/21/16

XXX12 IOE: 8/10/17

HCM

Portal

CRM

ELM

OBIEE

OBIA/ODI

OPA

Training

Core Dev

HCM

Portal

CRM

ELM

Elastic Search

OBIEE

OBIA/ODI

OPA

GRC

OAM/OIM/OID

Ab Initio

ESB

Data

HCM

Ab Initio

ESB

Functional/Unit Testing (FUT)

HCM

Portal

CRM

ELM

OBIEE

OBIA/ODI

Ab Initio

GRC

OAM/OIM/OID

OPA

ESB

Security

HCM

Portal

CRM

ELM

OBIEE

OBIA/ODI

OPA

GRC

OIM/OUD

Development/ Admin Tools

Stat Jenkins

Subversion Cobol Compiler

PeopleTools TOAD/SQL Dev

Putty Ultra Edit/ Compare

UPK

Program Support Tools

Iris Intelligence HP Agile Mgr.

HP ALM

Cameo

HP BPT

HP UFT

C-Factory

HP UCMDB

Adobe Captivate

OEM

Payroll

HCM

OPA

GP RRE Test

Data

HCM

Ab Initio

XXX01 IOE: 12/13/16

Tools Sub-Enclave Supporting Zone B, Zone A and DISA Data Center 1 SDC (Located at DC1)

OEM

Elastic Search

Audit Vault Stonebranch

Splunk

GRC

Qlik

Production Support Tools

Development/ Admin Tools

IOE: 3/2/17

IOC: 8/31/17

FOC: 2/28/18

1 2 3 4 5 6 7 8 9

PeopleTools Stat

Jenkins Subversion

Cobol Compiler SoapUI

UPK

TOAD/SQL DEV

Putty Ultra Edit / Compare

Program Support Tools

HP Agile Mgr.

HP ALM

Cameo

HP UFT

HP BPT

C-Factory

HP UCMDB

HP PC

*IRIS

*Migration in progress

UNCLASSIFIED

Secondary Production

HCM

Portal

CRM

ELM

Ab Initio

OAM/OIM

OUD

OPA

ESB

OHS

HCM

Portal

CRM

ELM

OBIEE

OBIA/ODI

OAM/OIM

OUD

OPA

Operational Training

HCM

Portal

CRM

ELM

OBIEE

OBIA/ODI

OAM/OIM

OUD

OPA

IOE: O/S configured & hardened (DISA) IOC: Software Installed/Configured (IPPS-A) FOC: Environment Ready for Users

IOE dates for Zone B, Zone A, COOP, & PROD are per DISA plans.

IOC & FOC dates for Zone A, COOP, & PROD are per SI IMS and are tentative until final delivery.

Environment FOC Ready. CM and App Sec activities completed.

Release 2 Test Sub-Enclave (App & OS STIG)

Institutional (and Self-

Development/ Qualif ication)

Training

HCM

Portal

CRM

ELM

OBIEE

OBIA/ODI

OPA

OIM/OAM

OUD

OHS

Payroll (with Cobol) SSO/CAC

HCM

OPA

GP RRE Test

HCM

Portal

CRM

ELM

OBIEE

OBIA/ODI

Ab Initio

OAM/OIM

OUD

OPA

ESB

Integrated Test

(PLT) SSO/CAC

HCM

Ab Initio

ESB

Data Test

Release 4 Test Sub-Enclave (App & OS STIG)

Production Staging

HCM

CRM

ELM

OBIEE

OBIA/ODI

Ab Initio

OAM/OIM

OUD

ESB

OHS

Informatica Gradkell

Primary Production

HCM

Portal

CRM

ELM

Ab Initio

OAM/OIM

OUD

OPA

ESB

OHS

HCM

CRM

ELM

OBIEE

OBIA/ODI

Gradkell

Informatica

OAM/OIM

OUD

ESB

Ab Initio

OHS

Primary Production

HCM

ELM

OBIEE

OBIA/ODI

OAM/OIM

OUD

OHS

Gradkell

Operational Training

HCM

CRM

OBIEE

OBIA/ODI

OAM/OIM

OUD

OHS

Gradkell

Institutional Training

Institutional Training

Release 3 Test Sub-Enclave (App & OS STIG)

HCM

CRM

ELM

OBIEE

OBIA/ODI

Gradkell

Informatica

OAM/OIM

OUD

ESB

Ab Initio

OHS

Integrated Test

(PLT) SSO/CAC

HCM

CRM

ELM

OBIEE

OBIA/ODI

Gradkell

Informatica

OAM/OIM

OUD

ESB

Ab Initio

OHS

HCM

Portal

ELM

OBIEE

OBIA/ODI

OAM/OIM

OUD

OPA

OHS

Operational Training

HCM

Portal

CRM

OBIEE

OBIA/ODI

OAM/OIM

OUD

OPA

OHS

Institutional Training Production

Reporting

OBIEE

OBIA/ODI

Secondary Reporting

OBIEE

OBIA/ODI

Release 2-4 Development (Bug Fixes/Sustainment) Sub-Enclave

HCM

Portal

CRM

OBIEE

OBIA/ODI

OPA

Institutional (and Self- Development/

Qualif ication) Training

HCM

Portal

CRM

ELM

OBIEE

OBIA/ODI

Ab Initio

OIM

OUD

OPA

ESB

FUT

HCM

Portal

CRM

ELM

OBIEE

OBIA/ODI

Ab Initio

OIM

OUD

OPA

ESB

Sustainment

Dot Release Test Sub-Enclave

ITE

DOT Releases

HCM

Portal

CRM

ELM

OBIEE

OBIA/ODI

Ab Initio

OAM/OIM

OUD

OPA

Production Staging

HCM

Portal

CRM

ELM

OBIEE

OBIA/ODI

Ab Initio

OAM/OIM

OUD

OPA

OHS

GRC

HCM

Portal

CRM

ELM

OBIEE

OBIA/ODI

AB Initio

GRC

OAM/OIM

OUD

OPA

ESB

Config Baseline

* NonPS Files Only

CM BASELINE

(ECR req.)

CM BASELINE

(ECR req.)

CM BASELINE

(ECR req.)

CM BASELINE

(ECR req.)

CM BASELINE

(ECR req.)

UPKs/Data

Release 3 /4 Prototype/Demonstration Enclave (App & OS No STIG)

Release 2 Training UPK Development Environment

Prototype

HCM

Portal

CRM

ELM

*FSCM

OBIEE

OBIA/ODI

Ab Initio

GRC

OAM/OIM/OID

OPA

HCM

Portal

CRM

ELM

OBIEE

OBIA/ODI

Ab Initio

GRC

OAM/OIM

OID

OPA

Demonstration

(STIG) SSO/CAC

HCM

Portal

CRM

ELM

OBIEE

OBIA/ODI

OPA

UPK Dev

CM BASELINE

(ECR req.)

PDC Support Tools Enclave

PeopleTools Cobol Compiler

TOAD/SQL DEV

Putty Ultra Edit/Compare

Admin Tools

Release 3 ITE2C – SDC Reporting/Training

(DIT/COOP)

XXX06 IOE: 2/01/20

R3 SDC Transactional

(DIT/COOP) XXX05 IOE: 2/01/20

HCM

CRM

ELM

Ab Initio

OAM/OIM

OUD

ESB

Gradkell Informatica

COOP

Production

HCM

ELM

OBIEE

OBIA/ODI

OAM/OIM

OUD

OHS

Gradkell

Operational Training

HCM

CRM

OBIEE

OBIA/ODI

OAM/OIM

OUD

OHS

Gradkell

Institutional Training

Production Reporting

OBIEE

OBIA/ODI

Config Baseline

CM BASELINE

(ECR req.)

CM BASELINE

(ECR req.)

XXX12 IOE: 10/15/18

Dot Release Development Sub-Enclave

Dot Release

FUT

HCM

Portal

CRM

ELM

OBIEE

OBIA/ODI

OPA

Release 3 Development Sub-Enclave (App & OS STIG)

CRM

ELM

OBIEE

OBIA/ODI

Gradkell

Informatica

OAM/OIM

OUD

ESB

Ab Initio

OHS

FUT/QA

*Data Dev

HCM

Ab Initio

ESB

R2 to R3 Migration

Staging (Database only no front end)

HCM

Portal

CRM

ELM

HCM

CRM

ELM

OBIEE

Gradkell

Institutional Training Dev (data and web pages only)

Unified Baseline Development Sub-Enclave (App & OS STIG)

Portal

CRM

ELM

UBL Core Dev (PUM retrofits)

HCM

CRM

ELM

OBIEE

OBIA/ODI

Gradkell

Informatica

OAM/OIM

OUD

ESB

Ab Initio

OHS

Core Dev

Dev0

Roles and Permissions

*Security Dev

HCM

CRM

ELM

OIM

OUD

Dot Release

DEV

HCM

Portal

CRM

ELM

OBIEE

OBIA/ODI

OPA

HCM

CRM

Gradkell

OAM/OIM

OUD

ESB

Ab Initio

OHS

Release 4 Development Sub-Enclave (App & OS STIG)

Data

HCM

Ab Initio

ESB

HCM

CRM

ELM

OBIEE

OBIA/ODI

OAM/OIM

OUD

Institutional (and Self- Development/

Qualif ication) Training

Dev0

HCM

CRM

ELM

Ab Initio

OAM/OIM

OUD

ESB

Gradkell Informatica

Security

HCM

CRM

ELM

OAM/OIM

OUD

HCM

CRM

ELM

OBIEE

OBIA/ODI

Ab Initio

OAM/OIM

OUD

ESB

Gradkell Informatica

FUT/QA

HCM

CRM

ELM

OBIEE

OBIA/ODI

Ab Initio

OAM/OIM

OUD

ESB

Gradkell Informatica

Core Dev

Conversions/Data Only

Data Configuration

HCM

Ab Initio

ESB

Institutional Training Test

Payroll (with Cobol) SSO/CAC

HCM

GP RRE Test HCM

ELM

OBIEE

OBIA/ODI

OAM/OIM

OUD

OHS

Gradkell

Operational Training

Production Staging

HCM

CRM

ELM

OBIEE

OBIA/ODI

Gradkell

Informatica

OAM/OIM

OUD

ESB

Ab Initio

OHS

Performance Testing

HCM

Portal

CRM

ELM

OIM

OUD

OPA

OHS

HCM

CRM

ELM

OIM

OUD

ESB

Gradkell

Performance Testing

Performance Testing

OBIEE

OBIA/ODI

Performance Testing

OBIEE

OBIA/ODI

BI Dev

OBIEE

OBIA

HCM

CRM

ELM

Qlik Data Test

HCM

Ab Initio

ESB

HCM

CRM

OBIEE

OBIA/ODI

OAM/OIM

OUD

OHS

Gradkell

4.2 Environmental Systems Management and Change Control

Coordination for Systems Management activities are executed according to the Service-Level Agreements (SLAs) with each data center. Changes to all enclaves/environments are made in accordance with established SLAs and the Configuration Management Plan.

4.2.1 Service-Level Agreements (SLAs)

Effective management of IPPS-A resources is dependent on the SLAs negotiated between IPPS-A and hosting data centers. This section outlines the SLAs established with each data center.

4.2.1.1 DISA

An SLA covering IPPS-A assets hosted in DISA data centers is accessible on SharePoint at

DISA SLA.

4.3 Site High-Level Design

Each site is designed to meet requirements and deliver capabilities for specific phases of the SDLC. This section provides a high-level design for each site along with a logical view of the enclaves, application stacks, and environments required to deliver those capabilities.

4.3.1 IPPS-A Increment II SDC

The DISA Defense Enterprise Computing Center (DECC) located at DATA CENTER 2, hosts the infrastructure supporting IPPS-A Increment II Test, Development, and SDC enclaves. These enclaves are supported by five Oracle SuperClusters and one Oracle ZFS storage appliance. Two additional Infiniband-connected SuperClusters are being procured to provide DIT/Release 3 production capabilities.

SuperCluster XXXX, in Zone B, supports development environments and is configured with two 4-node Oracle Real Application Clusters (RAC) supporting Increment II development and administrative Oracle 12c or higher databases. XXXX is configured with four electrically isolated Physical Domains (PDOMs). Each PDOM contains one database and three general purpose Logical Domains (LDOMs) for a total of four database LDOMs and 12 general purpose LDOMs.

SuperCluster XXXX and XXXX, in Zone A, are two Infiniband-connected SuperClusters that support Test enclave environments. XXXX supports Releases 2 and 3 test, BI Dev, Data Config, and Demonstration environments and is configured with one, 4-node Oracle RAC supporting test enclave 12c or higher databases. XXXX supports Release 4 test environments and is also configured with one, 4-node Oracle RAC supporting test enclave 12c or higher databases.

XXXX and XXXX are each configured with four electrically isolated Physical Domains (PDOMs). Each PDOM contains one database and two general purpose Logical Domains (LDOMs) for a total of four database LDOMs and eight general purpose LDOMs.

Two SuperClusters, XXXX and XXXX, support SDC/COOP transactional and reporting/training environments respectively. Both SuperClusters also support a Performance Test environment that provides the same performance characteristics as Production. SuperCluster XXXX is configured with one 4-node RAC and supports the SDC transactional environment. XXXX is configured with two 4-node RACs and supports the SDC reporting and training environments within the SDC enclave.

For Release 4 SDC capabilities, XXXX and XXXX will be replaced by two tech refreshed Infiniband-connected SuperClusters. SuperClusters XXXX and XXXX are being procured in order to support Release 3 DIT and SDC capabilities. XXXX will be configured with one 4-node RAC and support the R3 SDC transactional environment. XXXX will be configured with two 4-node RACs and support the SDC reporting and training environments within the SDC enclave.

For tools and other applications that cannot be hosted on the SuperCluster’s Scalable Processor Architecture (SPARC) platform, x86 capabilities are supported on DISA capacity services.

4.3.1.1 DISA DATA CENTER 2 Enclaves/Environments

DISA DATA CENTER 2 supports five IPPS-A enclaves located within two zones and “Production.” These enclaves include:

• Development (Zone B)

• Support Tools (Zone B)

• Test and Demonstration (Zone A)

• Support Tools (COOP)

• COOP/SDC (Secondary/COOP Production/Training) The Development, Test, and SDC Enclaves contain Application Stacks that support one or more environments.

Figure 4-8 identifies the application stacks and OEs that support the Development environments.

Due to the size of this drawing, the figure is representative of the current full version. Select the icon or access the figure on SharePoint at Zone B Development and Tools Enclaves/Environments.

Figure 4-8 Zone B Development and Tools Enclaves/Environments

UNCLASSIFIED

DISA DC1 Zone B Development and Tools Enclaves/Environments

UNCLASSIFIED

GR

C

1XXXXXHPAG0

GRC-App1

GR

C

2XXXXXHPAG1

GRC-App2

R2 Dev Sust

R2 FUT

Sust

In fo rm at ica

XXXXXHPAGS

Informatica-App1

R3 Dev R3 Dev0 R3 FUT/QA

R3 Inst Train Dev

R3 Oper Train Dev

In fo rm at ica

XXXXXHPAGT

Informatica-App2

El as tic

XXXXXHPAI8

ELAST-App1

R2 Dev Sust

R2 Data Dev Sust

R2 Inst Train Sust

R3 FUT

Sust

El as tic

2XXXXXHPAI9

ELAST-App2

R3 Inst Train DevR3 FUT/QA R3 Data Dev

R3 Dev R3 Dev0

El as tic

3XXXXXHPAJA

ELAST-App3

XXXXXXSHUA8

TOOLS1-Support

File Server-1

XXXXXXSHUA9

TOOLS1-Support

PeopleTools-1

XXXXXXSHPAA7

TOOLS1-App

PUM-1

W W W

XXXXXXSHUA2

TOOLS1-Support Remote Desktop-1

XXXXXXSHUA3

TOOLS1-Support Remote Desktop-2

XXXXXXSHUA4

TOOLS1-Support Remote Desktop-3

W W W

XXXXXXSHUA5

TOOLS1-Support Remote Desktop-4

XXXXXXSHUA6

TOOLS1-Support Remote Desktop-5

XXXXXXSHUA7

TOOLS1-Support Remote Desktop-6

W W W

X8

Su pp or t T oo ls

Sp lu nk

XXXXXHPAJB

Splunk-App1

R2 Dev Sust R2 Data Dev Sust

R2 Inst Train Sust

R2 Security Dev Sust

R2 FUT

Sust

R2-R3 Staging

R3 Dev R3 Dev0 R3 Data Dev

R3 FUT/QA R3 Security Dev

R3 Inst.

Train Dev

St on eb ra nc h

XXXXXHPAI0

Stonebranch-App1

R2 Dev Sust

R2 Inst Train Sust

R2 FUT

Sust

St on eb ra nc h

XXXXXHPAI1

Stonebranch-App2

R3 Dev R3 Dev0 R3 FUT/QA

R3 Data Dev

R3 Sec Dev

R3 Inst Train Dev

De ve lo pm en t S up er

Cl us te r X

XX

X

XXXXXAD003

GRC-App1

XXXXXAD307

CTRLM-App1

XXXXXAD209

LDAP-App1

XXXXXWD208

OBIEE-Web2

XXXXXWB204

OBIEE-Web1

XXXXXWD219

Mail-Web1

O Es fo r D ec om m iss io n

XXXXXDD201

DB-RAC1-Node1

XXXXXDD202

DB-RAC1-Node2

XXXXXDD203

DB-RAC1-Node3

XXXXXDD204

DB-RAC1-Node4

De v

Da ta ba se

R

AC

ES

B

XXXXXWD001

P-ESB-Web1

XXXXXWD306

P-ESB-Web1

R3 Dev R3 Dev0 R3 FUT/QA

ES

B

XXXXXWD207

P-ESB-Web2

XXXXXWD307

P-ESB-Web2

R2 FUT

Sust

Ab In iti o

XXXXXAD230

AbInitio-Web3

XXXXXAD212

AbInitio-App3

R2 Dev Sust R2 Data Dev Sust

R2 FUT

Sust

O

BI

EE

XXXXXAD330

OBIEE-App10

R3 Dev0

O

BI

EE

XXXXXAD329

OBIEE-App9

O

BI

EE

XXXXXAD328

OBIEE-App8

R3 Inst Train Dev

O

BI

EE

XXXXXAD327

OBIEE-App7

R3 FUT/QA

O

BI

EE

XXXXXAD326

OBIEE-App6

R2 FUT Sust

O

BI

EE

XXXXXAD325

OBIEE-App5

R3 Dev

O

BI

EE

XXXXXAD229

OBIEE-App4

O

BI

EE

XXXXXAD228

OBIEE-App3

R2 Dev Sust

O

BI

EE

XXXXXAD213

OBIEE-App2

O

BI

EE

XXXXXAD204

OBIEE-App1

R2 Inst Train Sust

Ab In iti o

XXXXXWD300

AbInitio-Web3

XXXXXAD300

AbInitio-App3

Ab In iti o

XXXXXWD004

AbInitio-Web1

XXXXXAD006

AbInitio-App1

R3 Dev R3 Dev0 R3 FUT/QA

R3 Data Dev

R3 Data Conv. Dev

Gr ad ke ll

XXXXXAD312

Grad-App1

R3 Dev R3 Dev0 R3 FUT/QA

R3 Inst Train Dev

Gr ad ke ll

XXXXXAD313

Grad-App2

XXXXXAA204

HCM-App1

XXXXXAA005

HCM-Batch1

XXXXXWB203

HCM-Web1

HC

M

R3 Dev R3 Dev0 R3 FUT/QA

XXXXXAD201

HCM-App2

XXXXXAD202

HCM-Batch2

XXXXXWD205

HCM-Web2

HC

M

R3 Data Dev

XXXXXAD210

HCM-App3

XXXXXAD211

HCM-Batch3

XXXXXWD206

HCM-Web3

HC

M

R3 Inst Train Dev

XXXXXAD220

HCM-App4

XXXXXAD221

HCM-Batch4

XXXXXWD215

HCM-Web4

HC

M

R2-R3 Staging

R3 Sec Dev

XXXXXAD316

HCM-App5

XXXXXAD320

HCM-Batch5

XXXXXWD308

HCM-Web5

HC

M

R2 Dev Sust

XXXXXAD317

HCM-App6

XXXXXAD320

HCM-Batch5

XXXXXWD309

HCM-Web6

HC

M

R2 FUT

Sust

XXXXXAD318

HCM-App7

XXXXXAD321

HCM-Batch7

XXXXXWD310

HCM-Web7

HC

M

R2 Inst Train Sust

XXXXXAD319

HCM-App8

XXXXXAD321

HCM-Batch7

XXXXXWD311

HCM-Web8

HC

M

XXXXXAS001

Portal-App1

XXXXXAS002

Portal-Batch1

XXXXXWS001

Portal-Web1

Po rt al

R3 Dev R3 Dev0

XXXXXAD001

Portal-App2

XXXXXAD002

Portal-Batch2

XXXXXWD212

Portal-Web2

Po rt al

R3 FUT/QA

XXXXXAD218

Portal-App3

XXXXXAD219

Portal-Batch3

XXXXXWD214

Portal-Web3

Po rt al

R3 Inst Train Dev

R3 Oper Train Dev

XXXXXAD222

Portal-App4

XXXXXAD223

Portal-Batch4

XXXXXWD216

Portal-Web4

Po rt al

R2-R3 Staging

XXXXXAD336

Portal-App5

XXXXXAD340

Portal-Batch5

XXXXXWD316

Portal-Web5

Po rt al

R2 Dev Sust

XXXXXAD337

Portal-App6

XXXXXAD341

Portal-Batch6

XXXXXWD317

Portal-Web6

Po rt al

R2 Security Dev Sust R4 Dev0

XXXXXAD338

Portal-App7

XXXXXAD342

Portal-Batch7

XXXXXWD312

Portal-Web7

Po rt al

R2 Fut Sust R4 FUT/QA

XXXXXAD339

Portal-App8

XXXXXAD343

Portal-Batch8

XXXXXWD319

Portal-Web8

Po rt al

R2 Inst Train Sust

R4 Oper Train Dev

R4 Inst Train Dev

XXXXXAA001

CRM-App1

XXXXXAD203

CRM-Batch1

XXXXXWD201

CRM-Web1

CR

M

R3 Dev R3 Dev0

XXXXXAD301

CRM-App4

XXXXXAD304

CRM-Batch4

XXXXXWD301

CRM-Web4

CR

M

R2 Dev Sust

XXXXXAD205

CRM-App2

XXXXXAD206

CRM-Batch2

XXXXXWD213

CRM-Web2

CR

M

R3 FUT/QA R3 Sec Dev

XXXXXAD224

CRM-App3

XXXXXAD225

CRM-Batch3

XXXXXWD217

CRM-Web3

CR

M

R3 Inst Train Dev

XXXXXAD302

CRM-App5

XXXXXAD305

CRM-Batch5

XXXXXWD302

CRM-Web5

CR

M

R2 Fut Sust

XXXXXAD303

CRM-App6

XXXXXAD306

CRM-Batch6

XXXXXWD303

CRM-Web6

CR

M

R2 Inst Train Sust

XXXXXAD309

ELM-App5

XXXXXAD311

ELM-Batch5

XXXXXWD305

ELM-Web5

EL

M

R2 Inst Train Sust

R2 FUT

Sust

XXXXXAD207

ELM-App1

XXXXXAD208

ELM-Batch1

XXXXXWD202

ELM-Web1

EL

M

R3 Dev R3 Dev0

XXXXXAA002

ELM-App2

XXXXXAA003

ELM-Batch2

XXXXXWD209

ELM-Web2

EL

M

R3 FUT/QA R3 Sec Dev

XXXXXAD226

ELM-App3

XXXXXAD227

ELM-Batch3

XXXXXWD218

ELM-Web3

EL

M

R3 Inst Train Dev

XXXXXAD308

ELM-App4

XXXXXAD310

ELM-Batch4

XXXXXWD304

ELM-Web4

EL

M

R2 Dev Sust

O

PA

XXXXXAD005

OPA-App1

R3 FUT/QA R3 Inst Train Dev

R3 Oper Train Dev

R3 Dev R3 Dev0

O

PA

XXXXXAD231

OPA-App2

R2 Dev Sust

R2 Inst Train Sust

R2 FUT

Sust

O

PA

XXXXXAD231

OPA-App2

R4 FUT/QA R4 Inst Train Dev

R4 Oper Train Dev

R4 Dev R4 Dev0

O

AM

XXXXXAD322

OAM-App5

R2 Dev Sust R4 Dev R4 Dev0

O

AM

XXXXXAD323

OAM-App6

R2 FUT

Sust R4 FUT/QA R4 Sec

Dev

O

AM

XXXXXAD324

OAM-App7

R2 Inst Train Sust

R4 Inst Train Dev

R4 Oper Train Dev

O

AM

XXXXXAD008

OAM-App5

R3 Dev

O

AM

XXXXXAD009

OAM-App2

O

AM

XXXXXAD214

OAM-App3

R3 FUT/QA R3 Sec Dev

O

AM

XXXXXAD215

OAM-App4

R3 Inst Train Dev

R3 Oper Train Dev

O

IM

XXXXXAD007

OIM-App1

R3 Dev R3 Dev0 R3 FUT/QA

O

IM

XXXXXAD217

OIM-App2

R3 Sec Dev

R3 Inst Train Dev

O

IM

XXXXXAD333

OIM-App3

R2 Dev Sust

R2 FUT

Sust

O

IM

XXXXXAD334

OIM-App4

R2 Inst Train Sust

O

UD

XXXXXAD004

OUD-App1

R3 Dev R3 Dev0 R3 FUT/QA

O

UD

XXXXXAD216

OUD-App2

R3 Sec Dev

R3 Inst Train Dev

R3 Oper Train Dev

O

UD

XXXXXAD331

OUD-App3

R2 Dev Sust

R2 FUT

Sust

O

UD

XXXXXAD332

OUD-App4

R2 Inst Train Sust

O

HS

R2 Dev Sust

XXXXXWD312

OHS-Web5

O

HS

XXXXXWD313

OHS-Web6

O

HS

XXXXXWD314

OHS-Web7

R2 FUT

Sust

O

HS

R2 Inst Train Sust

XXXXXWD315

OHS-Web8

O

HS

XXXXXWD002

OHS-Web1

R3 Dev

O

HS

XXXXXWD003

OHS-Web2

R3 Dev0

O

HS

R3 FUT/QA R3 Sec Dev

XXXXXWD210

OHS-Web3

O

HS

R3 Inst Train Dev

R3 Oper Train Dev

XXXXXWD211

OHS-Web4

XXXXXAD344

SES-App1

XXXXXAD314

GRC-App2

XXXXXAD345

SES-App2

XXXXXAD315

GRC-App3

XXXXXWD321

PSRPT-Web1

Co nv er ge d / Ca pa ci ty S er vi ce s x

O

Es

TBD

TBD

TBD

TBD

R2-R3 Staging

TBD

TBD

TBD TBD

TBD

TBD

R2 Dev Sust

Last Modified 09/24/2019

Figure 4-9 identifies the application stacks and OEs that support the Test environments. Due to the size of this drawing, the figure is representative of the current full version, accessible on SharePoint at DISA Zone A Test and Demonstration Enclave/Environments.

Figure 4-9 Zone A Test and Demonstration Enclave/Environments

REMOVED

Figure 4-10 identifies the application stacks and OEs that support the Secondary Standby/COOP production and training environments. The latest version of this drawing is located on SharePoint at Secondary Data Center/COOP Production/Training Enclave/Environments.

Figure 4-10 Secondary Data Center/COOP Production/Training Enclave/Environments

REMOVED

Figure 4-11 is a representation that identifies the application stacks and OEs that support the Release 3 Secondary Standby/ COOP production and training environments to be built in DATA CENTER 2. The latest version of this drawing is located on SharePoint at R3 SDC COOP Enclaves/ Environments.

Figure 4-11 R3 Secondary Production/COOP Enclaves/ Environments

4.3.2 IPPS-A Increment II PDC

The DISA DECC located in DATA CENTER 1 hosts the production infrastructure supporting IPPS-A for Increment II production capabilities. SuperCluster XXXX supports the Release 2 primary production transactional environment. SuperCluster XXXX supports Release 2 primary reporting and training environments. Each SuperCluster is configured with four electrically isolated PDOMs. Each PDOM contains one database and three general purpose LDOMs for a total of four database LDOMs and 12 general purpose LDOMs per SuperCluster. XXXX is configured with one 4-node RAC-supporting Oracle 12c or higher PDC databases. XXXX is configured with two, 4-node RAC-supporting Oracle 12c or higher PDC databases. One RAC is dedicated for reporting databases and the second is dedicated for training databases.

For Release 3, SuperCluster XXXX will support the primary production transactional environment. SuperCluster XXXX will support Release 3 primary reporting and training environments.

4.3.2.1 IPPS-A Increment II Production Data Center Enclaves/Environments DISA DATA CENTER 1 supports the following two enclaves within one zone and Production:

• PDC (Primary Production/Reporting and Training)

• Remote Desktop and Support Tools Tools requirements for providing remote access capabilities and managing applications and databases hosted on the Oracle SuperClusters are accomplished via capacity services OEs.

Figure 4 identifies the application stacks and OEs that support the Release 2 primary production transactional. The latest version of this drawing is located on SharePoint at PDC Production/Reporting and Training Enclave/Environments.

Figure 4-12 Primary Data Center (PDC)Production/Reporting and Training Enclaves/ Environments

Due to finalization of decommission decisions impacting R3 PDC footprint, drawings representing Release 3 PDC will be completed and added to SharePoint in a future version of this document.

4.3.3 SuperCluster Capacity Planning

Capacity planning tracks the projected utilization of resources required by OEs. Virtual central processing unit (vCPU) and Capacity Planning are referenced in the Oracle PeopleSoft HRMS

9.1 FP2 Self-Service Using Oracle Database (DB) for Oracle Solaris (Unicode) on Oracle SPARC M6-32 Servers whitepaper located under Infrastructure/Requirements on SharePoint at SPARC M6-32 Planning Whitepaper. All NIPR planning capacity worksheets are located on SharePoint at SuperCluster Capacity Planning Worksheets.

Figure 4-13 identifies the OEs hosted on the Zone B XXXX SuperCluster and their projected utilization.

Figure 4-13 XXXX Capacity Planning Figure 4-14 identifies the OEs hosted on the XXXX SuperCluster and their projected utilization.

Figure 4-14 Test SuperCluster XXXX Capacity Planning

REMOVED

Figure 4-15 identifies the OEs hosted on the XXXX SuperCluster and their projected utilization.

Figure 4-15 XXXX SuperCluster Capacity Planning

REMOVED

Figure 4-16 provides the OEs hosted on the XXXX SuperCluster and their projected utilization.

Figure 4-16 XXXX Capacity Planning

Figure 4-17 provides the template to be used to identify the OEs hosted on the XXXX SuperCluster and their projected utilization.

Figure 4-17 XXXX Capacity Planning

Figure 4-18 provides the OEs hosted on the XXXX SuperCluster and their projected utilization.

Figure 4-18 XXXX Capacity Planning

Figure 4-19 provides the OEs hosted on the XXXX SuperCluster and their projected utilization.

Figure 4-19 XXXX Capacity Planning

REMOVED

Figure 4-19 provides the OEs hosted on the XXXX SuperCluster and their projected utilization.

Figure 4-20 XXXX Capacity Planning

Figure 4-19 provides the OEs hosted on the XXXX SuperCluster and their projected utilization.

Figure 4-21 XXXX Capacity Planning

Figure 4-19 provides the OEs hosted on the XXXX SuperCluster and their projected utilization.

Figure 4-22 XXXX Capacity Planning

Figure 4-19 provides the OEs hosted on the XXXX SuperCluster and their projected utilization.

Figure 4-23 XXXX Capacity Planning

4.3.4 Hardware and Software inventory

The Hardware inventory for IPPS-A is captured in several Infrastructure artifacts including the DISA Master Server List (MSL), Monthly SuperCluster Inventory, and Consolidated Hardware Inventory Spreadsheet.

Once an SRF has been submitted, and the list of required infrastructure resource names are identified, the OEs are added to the DISA IPPS-A MSL. The MSL identifies the following:

• DISA Project under which the OEs were implemented

• Requested or assigned server name

• Server role

• LDOM placement

• Tier

• Operating System

• Cores/ RAM

• Storage requirements The latest version of the MSL is available on SharePoint at DISA Master Server List

DISA provides a monthly SuperCluster Inventory Spreadsheet that identifies the current status/utilization of all NIPR SuperClusters including:

• OE LDOM placement

• LDOM cores, VCPU, and RAM allocations

• Storage utilization The latest available version of the monthly inventory is located on SharePoint at DISA Monthly SuperCluster Inventory.

The new Consolidated Hardware Inventory consolidates the information from the MSL and Monthly SuperCluster Inventory to deliver the following in a single spreadsheet:

• Server name (CSHIP)

• Server Role

• SuperCluster or Capacity Services designation

• LDOM (if applicable)

• Cores

• VCPUs

• RAM

• Whether the server has been submitted for decommissioning

The Consolidated Hardware Inventory spreadsheet is available on SharePoint at Consolidated Hardware Inventory.

The R2 Production Hardware/Software Baseline is available on SharePoint at R2 Hardware/Software Baseline.

5 IPPS-A INCREMENT II ENVIRONMENT PREREQUISITES

Installation, implementation, development, testing, and sustainment of environments in the DISA hosting data centers require tools and services to access IPPS-A hosted infrastructure. The required tools and services are based on the role of the user.

5.1 Data Center Remote Access

In order to provide developers, application administrators, testers, and program support personnel the access to backend servers, a remote access solution must be implemented. The remote access solution must be sufficiently sized to support the number of concurrent users per role. The solution must also support the installation of the toolsets required by personnel based on their identified role. The VDI application requirements are accessible on SharePoint at VDI Requirements.

5.2 Software Download Capability

Application Administrators must have the ability to download the software required to install, configure, and maintain applications in all enclaves and environments. This capability must support the requirement to download large files (i.e., 20+ Gigabytes) without interruption. The speed of the download must be sufficient to accommodate individual downloads within a reasonable timeframe (i.e., an eight-hour work day for a large file).

A-1

Appendix A: Acronyms and Abbreviations Acronym Definition

AKO-S Army Knowledge Online-Secret Internet Protocol Router Network (SIPRNet)

ALM Application Lifecycle Management

AO Authorizing Official

BI Business Intelligence

BPT Business Process Testing

CDRL Contract Data Requirement List

CSHIP DISA term for a server name

CM Configuration Management

CAC Common Access Card

COOP Continuity of Operations Plan

COTS Commercial Off-The-Shelf

CR Change Request

CRM Customer Relationship Management

DECC Defense Enterprise Computing Center

DISA Defense Information Systems Agency

DISN Defense Information Systems Networks

DIT Developer Integration Testing

DMZ Demilitarized Zone

DoD Department of Defense

EBN Enterprise Backup Network

ECB Engineering Control Board

ECN Engineering Change Notification

ECR Engineering Change Request

ELM Enterprise Learning Management

ERP Enterprise Resource Planning System

ESB Enterprise Service Bus

ESM Enterprise Systems Management

FOC Full Operating Capability

FUT Functional User Test(ing)

GP Global Payroll

A-2

Acronym Definition

GRC Governance Risk and Compliance

HCM Human Capital Management

HP Hewlett Packard

HR Human Resources

HW Hardware

IA Information Assurance

IATO Interim Authority To Operate

IATT Interim Authority to Test

IdM Identity Manager

IMS Integrated Master Schedule

IRIS Integrated Risk Information System

IOC Initial Operating Capability

IOE Initial Operating Environment

IPPS-A Integrated Personnel and Pay System – Army

IRM Integrated Road Map

ISSM Information Security System Manager

ITE Integrated Testing Environment

LDOM Logical Domain

MFT Managed File Transfer

MOA Memorandum of Agreement

MSL Master Server List

NIPR Nonsecure Internet Protocol Router

OAM Oracle Access Manager

OBIA Oracle Business Intelligence Analytics

OBIEE Oracle Business Intelligence Enterprise Edition

ODI Oracle Data Integration

OE Operational Environments

OEM Oracle Enterprise Manager

OHS Oracle HTTP Server

OID Oracle Internet Directory

OIM Oracle Identity Manager

A-3

Acronym Definition

OOB Out of Band

OPA Oracle Policy Automation

OPM Oracle Policy Modeling

OS Operating System

OSC Oracle SuperCluster

OUD Oracle Unified Directory

PDC Primary Data Center

PDOM Physical Domain

PLT Product Level Testing

PMBOK Project Management Body of Knowledge

PMO Project Management Office

PMP Project Management Plan

PROD Production

PS PeopleSoft

QASP Quality Assurance Surveillance Plan

QC Quality Control

RAC Real Application Clusters

RAM Random Access Memory

RDBMS Relational Database Management System

RDP Remote Desktop Protocol

REQ Request or Requirements

RFAAP Radford Army Ammunition Plant

RRE Risk Reduction Exercise

SDC Secondary Data Center

SDLC Software Development Lifecycle

SED Software Engineering Directorate

SI System Integrator

SIPRNet Secret Internet Protocol Router Network

SLA Service-Level Agreement

SLM Service-Level Manager

A-4

Acronym Definition

SOA Service-Oriented Architecture

SP Sensitive Products

SPARC Scalable Processor Architecture

SRF Service Request Form

SQL Structured Query Language

SRB Soldier Record Brief

SSO Single Sign On

STIG Security Technical Implementation Guide

SW Software

T&D Test and Development

TOAD Tool for Oracle Application Developers

TRN Training

UCMDB Universal Configuration Management Database

UFT Unified Functional Testing

UPK User Productivity Kit

VCE Virtual Computing Environment vCPU Virtual Central Processing Unit

VDI Virtual Desktop Infrastructure

VIP Virtual Internet Protocol

VM Virtual Machine

XML Extensible Markup Language

B-1

Appendix B: Consolidated Reference Documents This appendix lists other documents that are referenced, which are provided to complement required items.

Document # PWS Reference Document Title

4.1.4 Project Management Plan (PMP)

4.13.4 Configuration Management Plan

C-1

Appendix C: Reference Terms

Term Definition

Application Stack A set of servers (or OEs) and application(s) that provide the capabilities of the application(s) (i.e. HCM Web, Application, and Batch) to environments.

Converged System

A portfolio of system-based products from Hewlett-Packard (HP) that integrates preconfigured IT components into systems for virtualization, cloud computing, big data, collaboration, converged management, and client virtualization.

Enclave An environment or group of environments that support one or more phases of the SDLC (i.e., Development, Test, Support Tools, SDC, and PDC).

Environment A set of application stacks, databases, and configurations that meet a pre-defined requirement, and/or delivers a pre-defined capability (i.e. Core, Data Payroll, and Fit/Gap).

Site Hosting Data Center.