Avaya Pod Orchestration Suite

General Information

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	Avaya Pod Orchestration Suite (POS) provides the visualization and management applications required to configure, orchestrate, manage, and monitor Avaya Collaboration Pods. Various management components and applications required for a Collaboration Pod are bundled as part of the Pod Orchestration Suite: Pod Visualization Manager (PVM), Visualization Performance and Fault Manager (VPFM), IP Flow Manager (IPFM), Configuration and Orchestration Manager (COM), Virtualization Provisioning Service (VPS), Management Server Console (MSC), and Pod Utility Module (PUM).
Technology/Standard Usage Requirements:	Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:	This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v23.12
Decision Date:	12/21/2023 at 21:23:25 UTC
Aliases:	VCL, POD, POS, PVM, VPFM, IPFM, COM, VPS, MSC, PUM
Introduced By:	TRM Request
Vendor Name:	Avaya

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
2.1.1	10/05/2015
3.0.x	07/28/2016
3.1.x	09/01/2018
4.x	03/01/2019

Current Decision Matrix (12/19/2023)

Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.

The VA Decision Matrix displays the current and future VA IT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported. Any major.minor version that is not listed in the VA Decision Matrix is considered unapproved for use.

Legend:

White	Approved: The technology/standard has been approved for use.
Yellow	Approved w/Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Unapproved: This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Divest: VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unapproved may be found on the Decision tab for the specific entry.
Black	Prohibited: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Planning/Evaluation Constraint:The period of time this technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology approved with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology approved with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

<Past

CY2023

CY2024

CY2025

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

2.1.1

Unapproved

3.0.x

Unapproved

3.1.x

Unapproved

4.x

Approved w/Constraints
[1, 5]

Approved w/Constraints
[1, 6, 7, 8]

Decision Constraints


[1]	Technology must remain patched and operated in accordance with Federal and Department security policies and guidelines in order to mitigate known and future security vulnerabilities.

[2]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[3]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[4]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[5]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500.

[6]	Users must not utilize Avaya Aura call Center Elite Multi Channel, as it is at the time of writing, unapproved in the TRM. Users must not utilize Avaya Aura System Platform, as it is at the time of writing, unapproved in the TRM. Users must not utilize Avaya Diagnostic Server, as it is at the time of writing, unapproved in the TRM.

[7]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500.

[8]	The Federal Information Processing standards (FIPS) 140-2 certification status of this technology was not able to be verified. This technology will require a 3rd party FIPS 140-2 or 140-3 certified solution for any data containing PHI/PII or VA sensitive information, where applicable. More information regarding the Cryptographic Module Validation Program (CMVP) can be found on the NIST website.

Note:

At the time of writing, version 4.1 is the most current version released.

References

The following reference(s) are associated with this entry:
Type	Name	Source	Description
There are no references identified for this entry.

Technology Components

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.
Name	Description
Configuration and Orchestration Manager (COM)	Configuration and Orchestration Manager (COM) is one of the POD configuration and provisioning applications that provides configuration, provisioning, and troubleshooting for Avaya network devices and technologies.
IP Flow Manager (IPFM)	IP Flow Manager (IPFM) is a network management software application that analyzes IP Flow traffic collected by Ethernet Routing Switches in order to provide enterprises with full views of network usage. IPFM provides the ability to monitor network usage and investigate and resolve network issues.
Management Server Console (MSC)	Management Server Console (MSC) is the management and utility software required to manage, configure and upgrade Avaya proprietary and third-party POD components.
Pod Utility Module (PUM)	Pod Utility Module (PUM) is specialized utility software required to configure and maintain POD configurations, virtual server and storage settings, etc., for Avaya 2400 and 4200 model hardware.
Pod Visualization Manager (PVM)	Pod Visualization Manager (PVM) is the Graphical User Interface (GUI) application that provides dashboards, monitoring, performance, and analytics for the Avaya Collaboration Pod.
Virtualization Provisioning Service (VPS)	Virtualization Provisioning Service (VPS) is the management technology utilized for the configuration and provisioning of POD network device inventory and topology, device configuration features (VLAN, ACL and port setting features) and for setting device credentials, roles and permissions.
Visualization Performance and Fault Manager (VPFM)	Visualization Performance and Fault Manager (VPFM) is a network management application that discovers and manages network attached devices and provides discovery of IP/SNMP devices, including network switches and routers, file and storage servers, applications and server operating systems, and IP phones, PCs and other end nodes.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Collaboration and Electronic Workplace Collaboration Software	Unified Messaging
Systems Management Systems Management Tools	IT Service Desk
Platforms and Storage Cloud Services/Server Virtualization	Virtualization Software

Operating Systems Supported by the Technology

Red Hat Enterprise Linux (RHEL) - Approved w/Constraints
Windows Server - Approved w/Constraints

Technologies/Standards Relationships

Runtime Dependencies:

No runtime dependencies have been identified.

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

This technology may improve productivity by providing a unified communication and contact center solution which includes pre-integrated networking, servers and storage which support unified communications and collaboration.
This technology integrates with other TRM approved Avaya technologies and provides enhanced functionality.
At the time of writing, no National Institute of Standards and Technology (NIST) vulnerabilities had been reported and no VA Cyber Security Operations Center (CSOC) bulletins had been issued for the latest versions of this technology.

Adoption Risks

Due to the rapid release schedule of this technology, the VA may be unable to update to the most recent patch and may require a deployment model requiring the use of specific versions.
There is limited publicly available technical documentation for this technology.
The technology requires the purchase of licenses from vendor, which could potentially lead to vendor lock-in.
This technology can potentially use Avaya Aura call Center Elite Multi Channel, an unapproved technology.
This technology can potentially use Avaya Aura System Platform, an unapproved technology.
This technology can potentially use Avaya Diagnostic Server, an unapproved technology.
The potential exists to store Personally Identifiable Information (PII), Protected Health Information (PHI) and/or VA Sensitive data and proper security standards must be followed in these cases.
This technologies calls that are captured and stored by the product components may contain sensitive information. Although this product is Federal Information Processing Standards (FIPS) 140-2 certified, care should be taken in the storage, management and use of recorded information.

Architectural Benefits

This technology is portable as it runs on multiple TRM-approved operating systems.
This technology is compatible with virtual machines, therefore consistent with the enterprise Server Virtualize First Policy (VAIQ 7266972 08-27-2012).
This technology utilizes Datagram Transport Layer Security/Secure Real-time Transport Protocol (DTLS/SRTP) encryption for recorded (ACR) calls in transit, during replay, and at rest.

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (12/19/2023)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (12/19/2023)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

EMAIL UPDATES