Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 24.7

Microsoft Power Business Intelligence (BI)

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:	Microsoft Power Business Intelligence (BI) is a business analytics software. This technology allows end users to create and share interactive visualizations with self-service business intelligence capabilities such as reports and dashboards via a drag-and-drop user interface. User generated data models are utilized to shape data imported from a range of sources and to perform analytics without the need for information technology staff or database administrator assistance. This technology is available in three editions; Power BI Desktop, Power BI Pro, and Power BI Premium. Power BI Desktop has no licensing fee associated with it and provides authoring functionalities to end users in order to analyze and build reports. Power BI Pro allows users to collaborate on shared data by creating a data culture in which users in multiple roles can build reports and share insights. Power BI Premium is configured for large scale deployments and allows users to allocate and manage dedicated server capacity and share data with users both inside and outside of an organization. The scope of this entry is for all three editions. Data collected by Microsoft Power BI is stored in a Microsoft Structured Query Language (SQL) Server database. Additionally, this technology has optional functionality to integrate with Microsoft Azure SQL Databases. This entry covers the Desktop Edition of this technology and not any mobile versions. Please note that the implementation of mobile technology applications that operate on Mobile Operating Systems must be reviewed and approved by the Mobile Technology and Endpoint Security Engineering Team: https://dvagov.sharepoint.com/sites/OITMT/SitePages/MTHome.aspx The TRM decisions in this entry only apply to technologies and versions owned, operated, managed, patched, and version-controlled by VA. This includes technologies deployed as software installations on VMs within VA-controlled cloud environments (e.g. VA Enterprise Cloud (VAEC)). Cloud services provided by the VAEC, which are listed in the VAEC Service Catalog, and those controlled and managed by an external Cloud Service Provider (i.e. SaaS) are not in the purview of the TRM. For more information on the use of cloud services and cloud-based products within VA, including VA private clouds, please see the Enterprise Cloud Solutions Office (ECSO) Portal at: https://dvagov.sharepoint.com/sites/OITECSO
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 v24.5
Decision Date:	05/20/2024 at 17:25:09 UTC
Aliases:	Microsoft Power BI Desktop, PowerBI, Power BI Desktop
Introduced By:	TRM Request
Vendor Name:	Microsoft

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.31.x	01/01/2016
2.32.x	02/01/2016
2.33.x	03/01/2016
2.34.x	05/06/2016
2.46.x	05/15/2017
2.49.x	08/14/2017
2.52.x	11/07/2017
2.55.x	02/01/2018
2.56.x	03/09/2018
2.58.x	05/08/2018
2.59.x	06/04/2018
2.61.x	08/05/2018
2.63.x	10/15/2018
2.64.x	11/20/2018
2.65.x	12/17/2018
2.68.x	04/01/2019
2.69.x	05/25/2019
2.70.x	06/18/2019
2.71.x	08/14/2019
2.72.x	08/19/2019
2.73.x	09/11/2019
2.74.x	10/24/2019
2.7x	11/01/2019
2.8x	04/01/2020
2.9x	03/08/2021
2.10x	12/21/2021
2.109.x	09/20/2022
2.110.x	11/03/2022
2.111.x
2.112.x	01/10/2023
2.113.x
2.114.x	02/21/2023
2.115.x	03/24/2023
2.116.x	04/19/2023
2.117.x	05/15/2023
2.118.x	06/22/2023
2.119.x	07/24/2023
2.120.x	08/29/2023
2.121.x	09/18/2023
2.122.x	11/01/2023
2.123.x	11/23/2023
2.124.x	01/20/2024
2.126.x	03/01/2024
2.127.x	03/28/2024
2.128.x	04/15/2024

Current Decision Matrix (05/16/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 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

CY2019

CY2020

CY2021

Future>

Release

2.31.x

Unapproved

2.32.x

Unapproved

2.33.x

Unapproved

2.34.x

Unapproved

2.46.x

Unapproved

2.49.x

Unapproved

2.52.x

Unapproved

2.55.x

Unapproved

2.56.x

Unapproved

2.58.x

Unapproved

2.59.x

Unapproved

2.61.x

Divest
[2, 4, 7, 8, 10, 14]

Divest
[4, 7, 8, 10, 15]

Unapproved

2.63.x

Approved w/Constraints
[2, 4, 7, 8, 10, 14]

Divest
[4, 7, 8, 10, 15]

Divest
[2, 4, 7, 8, 10, 16]

Unapproved

2.64.x

Unapproved

2.65.x

Approved w/Constraints
[2, 4, 7, 8, 10, 14]

Divest
[4, 7, 8, 10, 15]

Divest
[2, 4, 7, 8, 10, 16]

Unapproved

2.68.x

Unapproved

Approved w/Constraints
[4, 7, 8, 10, 15]

Divest
[2, 4, 7, 8, 10, 16]

Divest
[2, 4, 7, 8, 10, 17]

Divest
[2, 4, 7, 8, 17, 18]

Divest
[2, 7, 8, 17, 18, 19]

Unapproved

2.69.x

Unapproved

Approved w/Constraints
[4, 7, 8, 10, 15]

Divest
[2, 4, 7, 8, 10, 16]

Divest
[2, 4, 7, 8, 10, 17]

Divest
[2, 4, 7, 8, 17, 18]

Divest
[2, 7, 8, 17, 18, 19]

Unapproved

2.70.x

Unapproved

Approved w/Constraints
[1, 4, 7, 8, 10, 15]

Approved w/Constraints
[2, 4, 7, 8, 10, 16]

Unapproved

2.71.x

Unapproved

Approved w/Constraints
[1, 2, 4, 7, 8, 10, 16]

Unapproved

2.72.x

Unapproved

Approved w/Constraints
[2, 4, 7, 8, 10, 16]

Unapproved

2.73.x

Unapproved

2.74.x

Unapproved

2.7x

Unapproved

Approved w/Constraints
[2, 4, 7, 8, 10, 17]

Approved w/Constraints
[2, 4, 7, 8, 17, 18]

Divest
[2, 7, 8, 17, 18, 19]

Divest
[2, 7, 8, 18, 19, 20]

Divest
[2, 19, 20, 21, 22, 23]

Unapproved

2.8x

Unapproved

Approved w/Constraints
[2, 7, 8, 17, 18, 19]

Approved w/Constraints
[2, 7, 8, 18, 19, 20]

Approved w/Constraints
[2, 19, 20, 21, 22, 23]

Approved w/Constraints
[2, 19, 20, 21, 23, 24]

Approved w/Constraints
[2, 19, 21, 23, 24, 25, 26]

2.9x

Unapproved

Approved w/Constraints
[2, 19, 20, 21, 23, 24]

Approved w/Constraints
[2, 19, 21, 23, 24, 25, 26]

2.10x

Unapproved

2.109.x

Unapproved

2.110.x

Unapproved

2.111.x

Unapproved

2.112.x

Unapproved

2.113.x

Unapproved

2.114.x

Unapproved

2.115.x

Unapproved

2.116.x

Unapproved

2.117.x

Unapproved

2.118.x

Unapproved

2.119.x

Unapproved

2.120.x

Unapproved

2.121.x

Unapproved

2.122.x

Unapproved

2.123.x

Unapproved

2.124.x

Unapproved

2.126.x

Unapproved

2.127.x

Unapproved

2.128.x

Unapproved

Decision Constraints


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

[2]	Users should check with their supervisor, Information Security Office (ISO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not approved and the user should take the proper steps to decline those installations.

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

[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]	Due to potential information security risks, cloud based technologies may not be used without the approval of the VA Enterprise Cloud Services (ECS) Group. This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[8]	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).

[9]	In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISO can advise on the ESCCB review process.

[10]	Due to potential information security risks, cloud based technologies may not be used without the approval of the Enterprise Cloud Solution Office (ECSO). This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[11]	In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISO can advise on the ESCCB review process.

[12]	To ensure compliance, please check exact patched version on our standards portal here: https://vaww.eie.va.gov/SysDesign/CS/_layouts/15/listform.aspx?PageType=4&ListId=%7B51EBCCFA%2D0603%2D483D%2DBCD3%2D5F437760568A%7D&ID=336&ContentTypeID=0x01003A454BC85F6A22408D35BB29C7C53469.

[13]	To ensure compliance, please check exact patched version on our standards portal here: https://vaww.eie.va.gov/SysDesign/CS/_layouts/15/listform.aspx?PageType=4&ListId=%7B51EBCCFA%2D0603%2D483D%2DBCD3%2D5F437760568A%7D&ID=336&ContentTypeID=0x01003A454BC85F6A22408D35BB29C7C53469. If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

[14]	To ensure compliance, please check exact patched version on our standards portal here. If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

[15]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

[16]	To ensure compliance, please check exact patched version on our standards portal here. If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

[17]	To ensure compliance, please check exact patched version on the TRM standards portal here. If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Users must ensure that Microsoft Structured Query Language (SQL) Server, Microsoft .NET Framework and Microsoft Internet Explorer (IE) are implemented with VA-approved baselines.

[18]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (SPF) team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[19]	Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISO can provide assistance in reviewing the NIST vulnerabilities.

[20]	To ensure compliance, please check exact patched version on the TRM standards portal here. If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Users must ensure that Microsoft Structured Query Language (SQL) Server, Microsoft .NET Framework and Microsoft Internet Explorer (IE) are implemented with VA-approved baselines. Per the Initial Product Review, users must abide by the following constraints: Ensure use of a FIPS 140-2 validated cryptographic module to secure VA sensitive data in workstations that use Microsoft Power BI Desktop where applicable. Ensure that Microsoft Power BI Desktop Cloud Services version is obtained through Software Center and the Report Server version through authentic Microsoft webstore with verifiable web certificate. Due to potential information security risks, SaaS/PaaS solutions must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Project Special Forces (PSF), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS/Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by PSF. The visuals store should not have open access and content should be moderated and/or vetted by a central group before being used. The VA OIT Business Intelligence Service Line (BISL) supports Power BI for the VA enterprise. The BISL team can be contacted at the following email address: BISLPBISUPPORT@VA.GOV for support.

[21]	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).

[22]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (SPF) team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

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

[24]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (PSF) team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[25]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Users must ensure that Microsoft Structured Query Language (SQL) Server, Microsoft .NET Framework, Firefox, Google Chrome and Microsoft Internet Explorer (IE) are implemented with VA-approved baselines. Users must Divest the use of Internet Explorer with this technology. Other approved internet browsers are available. See Category Tab for details. Per the Initial Product Review, users must abide by the following constraints: Ensure use of a FIPS 140-2 validated cryptographic module to secure VA sensitive data in workstations that use Microsoft Power BI Desktop where applicable. Ensure that Microsoft Power BI Desktop Cloud Services version is obtained through Software Center and the Report Server version through authentic Microsoft webstore with verifiable web certificate. Due to potential information security risks, SaaS/PaaS solutions must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Project Special Forces (PSF), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS/Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by PSF. The visuals store should not have open access and content should be moderated and/or vetted by a central group before being used. The VA OIT Business Intelligence Service Line (BISL) supports Power BI for the VA enterprise. The BISL team can be contacted at the following email address: BISLPBISUPPORT@VA.GOV for support.

[26]	This technology has received one or more VA security bulletins that provide specific guidance on vulnerability patching and mitigation. It is the responsibility of VA system owners to ensure that the appropriate mitigations are taken to address all known and future discovered vulnerabilities with this product. See the Reference tab for more information on security bulletins related to this product.

Note:

At the time of writing, version 2.128.952.0 is the most current version, released 04/15/2024.

A standard configuration of this technology was developed by the DDE team. At the time of writing, the standard version is 2.122.746.0, and versions 2.126.927.0 and 2.128.952.0 is under testing and development for six weeks from 04/25/2024.

The following reference(s) are associated with this entry:
Type	Name	Source	Description
*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
No components have been identified for this entry.


Information Management Technologies Business Intelligence and Data Warehouse Platforms	Business Intelligence Platforms

- The information contained on this page is accurate as of the Decision Date (05/20/2024 at 17:25:09 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 (05/16/2024)

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

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (05/16/2024)

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

Architectural Risks

EMAIL UPDATES