VA Technical Reference Model v 24.11

OpenText Dimensions Change Management (CM)

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:	Dimensions Change Management (CM) is a process-based software change and configuration management solution. This technology is designed to streamline and automate Agile development practices, supporting a choice of industry standard databases, network compression, and library-cache technology. Dimensions CM has an n-tier cross-platform architecture consisting of the following layers: Presentation tier, Business logic tier, Database tier, and File/Storage tier. The Presentation tier consists of the clients that end-users will make use of to access the functionality of Dimensions CM. There are many different clients to allow support for different platforms and access methods. Components within the Business logic tier are server components responsible for carrying out Dimensions operations on behalf of the clients (for example, authenticating users, checking privilege/authorization, enforcing process rules, maintaining metadata about products, projects, baselines, requests, and items under control). These server components are supported on a wide variety of platforms. Dimensions CM uses relational database technology, requiring either Microsoft Structured Query Language (SQL) Server, PostgreSQL, or Oracle Database, to store and query this metadata. In addition to managing the metadata about assets under control, the software also needs to securely manage the content of the assets themselves (such as documents and versions of the user`s source code). These file storage/retrieval tasks are carried out by the File/Storage tier in the architecture. When communicating between tiers (across the network), Dimensions CM employs various encryption technologies to ensure data is transmitted securely. All data sent over the wire is Secure Sockets Layer (SSL) encrypted. If Dimensions network traffic travels over a public network link, the vendor recommends that users configure Dimensions to use the Secure Standard Dimensions Protocol (SSDP). Encryption is also provided using Transport Layer Security (TLS) and HyperText Transfer Protocol Secure (HTTPS) protocol. All stored passwords are encrypted. Note: This technology was sold to OpenText by Microfocus in 2023. This technology can integrate with Microsoft Structured Query Language (SQL) Server, PostgreSQL, and Oracle Database.
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 v24.4
Decision Date:	04/18/2024 at 18:19:36 UTC
Aliases:	Serena Dimensions Change Management (CM)
Introduced By:	Benefits ASA
Vendor Name:	Open Text

Vendor Release Information

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

You must be logged into the RSAA website prior to clicking the Attestation URLs or the URLs won't open.

Version	Release Date	Vendor Desupport Date
9.1.x	11/05/2004	09/01/2009
10.1	09/15/2006	01/31/2011
2009
10.1.x	04/07/2010
12.0.x	11/19/2011
14.0	06/10/2014
14.3.x	05/26/2016
14.4.x	01/10/2018
14.5.x	04/08/2019
14.6.x
14.7.x

Current Decision Matrix (04/15/2024)

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 VAIT 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.

Legend:

White	Authorized: The technology/standard has been authorized for use.
Yellow	Authorized 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	Authorized w/ Constraints (POA&M): 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	Authorized w/ Constraints (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 unauthorized may be found on the Decision tab for the specific entry.
Black	Unauthorized: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Authorized w/ Constraints (PLANNING/EVALUATION): 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 authorized 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 authorized 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.

Any major.minor version that is not listed in the VA Decision Matrix is considered Authorized w/ Constraints (POA&M).

<Past

CY2025

CY2026

CY2027

Future>

Release

9.1.x