Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 26.1

Living Systems Process Suite (LSPS)

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:	Living Systems Process Suite (LSPS) is a Java-based Business Process Management Suite (BPMS) used for modeling, execution, and analytic optimization of goal-oriented business processes, based on the Business Process Modeling Notation (BPMN) standard. This software directly executes process models without requiring any coding. This technology does not contain a database. However, LSPS has the capability to import and export data from different types of databases, including Oracle Database, Microsoft Structured Query Language (SQL) Server, and DB2. This technology is offered in either Enterprise Edition or Cloud Edition. This entry only covers the Enterprise Edition which is locally installed. 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 System Security Officer (ISSO), 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 v25.11
Decision Date:	11/25/2025 at 20:35:28 UTC
Introduced By:	TRM Request
Vendor Name:	Whitestein
Cage Code:	N/A

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.

Major versions and minor versions of that Major released on or after 09/14/2022 are NOT EXEMPT. Major Versions released before 09/14/2022 are EXEMPT as well as minor versions of that Major regardless of release date.

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
2.0	06/10/2010
2.5	11/30/2011
2.5.1	01/27/2012
2.6	07/10/2012
2.7	10/01/2013
3.0	06/08/2015
3.1	11/02/2015
3.2	02/20/2017
3.3.x	05/31/2018
3.6.x	03/11/2021

Current Decision Matrix (11/18/2025)

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 System Security Officer (ISSO), 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	Unauthorized, Conditions Required^[a] : 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	Unauthorized, Conditions Required^[b] : 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	Unauthorized, Conditions Required^[c] : 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 Unauthorized, Conditions Required ^[a] .

Release	Q1	Q2	Q3	Q4	Q1	Q2	Q3	Q4	Q1	Q2	Q3	Q4
<Past	CY2026				CY2027				CY2028				Future>
2.0	Unauthorized, Conditions Required (POA&M Required)	Unauthorized, Conditions Required (POA&M Required)	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]
2.5	Unauthorized, Conditions Required (POA&M Required)	Unauthorized, Conditions Required (POA&M Required)	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]
2.5.1	Unauthorized, Conditions Required (POA&M Required)	Unauthorized, Conditions Required (POA&M Required)	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]
2.6	Unauthorized, Conditions Required (POA&M Required)	Unauthorized, Conditions Required (POA&M Required)	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]
2.7	Unauthorized, Conditions Required (POA&M Required)	Unauthorized, Conditions Required (POA&M Required)	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]
3.0	Unauthorized, Conditions Required (POA&M Required)	Unauthorized, Conditions Required (POA&M Required)	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]
3.1	Unauthorized, Conditions Required (POA&M Required)	Unauthorized, Conditions Required (POA&M Required)	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]
3.2	Unauthorized, Conditions Required (POA&M Required)	Unauthorized, Conditions Required (POA&M Required)	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]
3.3.x	Unauthorized, Conditions Required (POA&M Required)	Unauthorized, Conditions Required (POA&M Required)	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]
3.6.x	Unauthorized, Conditions Required (POA&M Required)	Unauthorized, Conditions Required (POA&M Required)	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]
Note:	At the time of writing, version 3.6.1014 is the most current version, released 03/11/2021.

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
Living Systems Process Design Suite	This package provides an Eclipse-based environment to create, edit, execute, test, and monitor business processes defined in the Goal Oriented Business Process Model and Notation (BPMN) modeling language.
Living Systems Process Runtime Suite	This package provides all the necessary artifacts to set up the LSPS on various application and database servers. It is intended for system integrators and administrators.
Living Systems Process Software Development Kit (SDK)	This package contains all the necessary artifacts to set up a development environment to create, customize, extend and build enterprise applications based on the LSPS product. This module is intended for the IT specialists creating applications using the Process Suite.


Application Technology Development Tools	Process Management Tools

General Analysis

Adoption Benefits

This technology may improve productivity for specific staff whose responsibilities include Business Processing Reengineering (BPR).
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.
This is a well-documented 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.
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 technology relies on Java Development Kit (JDK) - Oracle, which has a rapid release and update schedule.
This technology is available as freeware. As such this technology may be without clearly defined support options which may result in suboptimal enterprise level support.
There are other authorized solutions that provide similar functionality available on the TRM. The use of several similar solutions may increase organization requirements for support and maintenance.
System scans indicate that this technology is no longer in use within the VA network.

Architectural Benefits

This technology can use a VA-preferred database.
This technology is portable as it runs on multiple TRM-authorized operating systems.
This technology is compatible with multiple other Technical Reference Model (TRM) technologies and standards used by the organization.

Architectural Risks

This technology includes cloud-based functionality which has potential information security risks.

- The information contained on this page is accurate as of the Decision Date (11/25/2025 at 20:35:28 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 26.1

General Information

Vendor Release Information

Current Decision Matrix (11/18/2025)

References

Technology Components

VA Categories

View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Optional 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 26.1

General Information

Vendor Release Information

Current Decision Matrix (11/18/2025)

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Optional Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES

VA Categories

View the VA Categorization Framework