Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 24.7

TreeAge Pro

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:	TreeAge Pro is a visual modeling application used to build decision trees for analyzing various problems to calculate the expected value of different strategies and choose the optimal path. Analytical features include multi-way sensitivity analysis, decision tree functionality, tornado diagrams, threshold analysis, single and comparative probability distribution graphs, Bayes` revision, Monte Carlo simulation, and multi-attribute analysis. Data from this software can be stored on the user`s local drive and includes the option to link tables to an existing database or other data source using an Open Database Connectivity (ODBC) driver. TreeAge Pro can access Microsoft Structured Query Language (SQL) Server, Microsoft Access, Excel, or other databases via the ODBC driver. Linking a table to a database ensures that data are updated automatically. The vendor does not specify if these data are encrypted. Note: There are two editions of this product: Healthcare and Core. Healthcare has all the features of Core, but includes a healthcare module used to create trees that are evaluated based on cost-effectiveness. This entry covers both editions.
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 been assessed by the Section 508 Office and found non-conformant. 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. Please see reference tab for more information concerning product versions.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v23.11
Decision Date:	11/22/2023 at 20:45:36 UTC
Introduced By:	TRM Request
Vendor Name:	TreeAge Software Inc.

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
TP 2009
TP 2010
TP 2011 R1	01/12/2011
TP 2012 R1	01/30/2012
TP 2012 R2	07/13/2012
TP 2013 R1	01/16/2013
TP 2013 R2	07/01/2013
TP 2013 R2.1	09/11/2013
TP 2014 R1	01/13/2014
TP 2014 R1.1	03/18/2014
TP 2014 R1.2	04/23/2014
TP 2014 R2	07/07/2014
TP 2015 R1	01/12/2015
TP 2015 R2	11/30/2015
TP 2017 R1	01/09/2017
TP 2018	01/22/2018
TP 2019 R1	01/01/2019
TP 2020 R1	01/01/2020
TP 2020 R2	06/23/2020
TP 2021 R1	11/30/2020
TP 2021 R2	06/24/2021
TP 2022 R1	10/29/2021
TP 2022 R2	07/06/2022
TP 2023 R1	01/17/2023
TP 2023 R2	06/19/2023
TP 2024 R1	11/15/2023

Current Decision Matrix (11/21/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

CY2021

CY2022

CY2023

Future>

Release

TP 2009

Unapproved

TP 2010

Unapproved

TP 2011 R1

Unapproved

TP 2012 R1

Unapproved

TP 2012 R2

Unapproved

TP 2013 R1

Unapproved

TP 2013 R2

Unapproved

TP 2013 R2.1

Unapproved

TP 2014 R1

Unapproved

TP 2014 R1.1

Unapproved

TP 2014 R1.2

Unapproved

TP 2014 R2

Unapproved

TP 2015 R1

Unapproved

TP 2015 R2

Unapproved

TP 2017 R1

Unapproved

TP 2018

Divest
[8, 9, 10, 11]

Unapproved

TP 2019 R1

Divest
[8, 9, 10, 11]

Unapproved

TP 2020 R1

Approved w/Constraints
[8, 9, 10, 11]

Approved w/Constraints
[8, 9, 12, 13]

Divest
[9, 13, 14, 15, 16]

TP 2020 R2

Unapproved

Divest
[9, 13, 14, 15, 16]

TP 2021 R1

Unapproved

Divest
[9, 13, 14, 15, 16]

TP 2021 R2

Unapproved

Divest
[9, 13, 14, 15, 16]

TP 2022 R1

Unapproved

Divest
[9, 13, 14, 15, 16]

TP 2022 R2

Unapproved

Divest
[9, 13, 14, 15, 16]

TP 2023 R1

Unapproved

Divest
[9, 13, 14, 15, 16]

TP 2023 R2

Unapproved

Divest
[9, 13, 14, 15, 16]

TP 2024 R1

Unapproved

Approved w/Constraints
[9, 13, 14, 15, 16]

Decision Constraints


[1]	Veterans Affairs (VA) users must ensure VA sensitive data is protected properly in accordance with VA Handbook 6500 and the Federal Information Security Management Act (FISMA). Per VA Handbook 6500, FIPS 140-2 certified encryption must be used to protect and encrypt data in transit and at rest if Personally Identifiable Information/Protected Health Information/VA (PII/PHI/VA) sensitive information is involved. If FIPS 140-2 certified encryption in not used, additional mitigating controls must be documented in an approved System Security Plan (SSP). In addition, the technology must be implemented within the VA production network (not in a Demilitarized Zone (DMZ)), unless the specific uses and instances of the technology are approved by the Enterprise Security Change Control Board (ESCCB). All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. In cases where the technology is used for external connections, a full ESCCB review is required in accordance VA Directive 6004, VA Directive 6517 and VA Directive 6513.

[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]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

[4]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[5]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[6]	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.

[7]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. This product can be configured with Microsoft Access, which currently has TRM constraints for VA sensitive data. If Microsoft Access is selected for use with this product, these factors must be considered. (Refer to Microsoft Access TRM entry for more details.)

[8]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Users must ensure that Microsoft Access, Microsoft Excel and Microsoft Structured Query Language (SQL) Server are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) This technology must use the latest TRM-approved version of Java Runtime Environment (JRE) - Oracle.

[9]	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.

[10]	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.

[11]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[12]	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.

[13]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[14]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Users must ensure that Microsoft Access, Microsoft Excel and Microsoft Structured Query Language (SQL) Server are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)

[15]	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.

[16]	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 TP 2024 R1 is the most current version, released 11/15/2023.

The following reference(s) are associated with this entry:
Type	Name	Source	Description
Vendor Provided*	Release Info	Publicly Available	This page has information for the releases of this technology.
Vendor Provided*	System Requirements	Publicly Available	These are the system requirements for the technology.
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

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
Excel Module	The Excel Module allows the user to export graphical and numerical output to Excel, which allows the user to examine and analyze results outside of TreeAge Pro.
Healthcare Module	The Healthcare Module enables users to create decision trees that are evaluated on the basis of cost-effectiveness, as well as either cost or effectiveness as a single measure.


Information Management Technologies Business Intelligence and Data Warehouse Platforms	Data Analytics (Statistical Analysis, Prediction, and Modeling)

- The information contained on this page is accurate as of the Decision Date (11/22/2023 at 20:45:36 UTC).

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 (11/21/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 (11/21/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