Plan Room Va Pdf Sheets Veteran Project Drawings

Attention A T users. To access the menus on this page please perform the following steps. one. Delight switch car forms fashion to off. ii. Hit enter to aggrandize a main menu option (Wellness, Benefits, etc). 3. To enter and actuate the submenu links, hit the down arrow. You lot will now be able to tab or pointer up or downward through the submenu options to admission/activate the submenu links.

VA Technical Reference Model v 22.4

Space and Equipment Planning System (SEPS)

1. General
2. Conclusion
3. Reference
4. Component
5. Category
6. Analysis

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

Website:	Go to site
Description:	Space and Equipment Planning System (SEPS) is a spider web-based health system monitoring software jointly adult past the Departments of Defense (DoD) and Veterans Affairs (VA). This technology develops detailed programs for design, based on established space planning criteria, room design requirements, and established room guide plates. This technology also produces detailed room contents reports, which includes all logistical categories of associated equipment, medical equipment, and article of furniture needs to support the functional requirements of the room. This technology stores information in a Microsoft Structured Query Language (SQL) Server database.
Engineering science/Standard Usage Requirements:	Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, simply non express to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Plant 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 utilise of this technology, users should check with their supervisor, Information Security Officeholder (ISO), Facility Chief Data Officeholder (CIO), or local Office of Information and Engineering (OI&T) representative to ensure that all deportment are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:	This technology has non been assessed past the Section 508 Office. The Implementer of this technology has the responsibleness to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed past the Section 508 Office and appropriate remedial action required if necessary. For additional information or aid regarding Department 508, please contact the Section 508 Office at Section508@va.gov.
Decision:	View Decisions
Decision Source:	TRM Mgmt Group
Determination Process:	One-VA TRM v20.3
Decision Appointment:	03/10/2020
Introduced By:	TRM Request
Vendor Name:	Military Health System

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

Version	Release Date	Vendor End of Life Engagement	Vendor Desupport Appointment
one.0	10/01/2005
2.five
2.6	01/31/2011
iii.0	05/17/2013
iii.x.x	10/08/2015

Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not express to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Engineering science (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to utilize of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Master Information Officer (CIO), or local Part of Information and Technology (OI&T) representative to ensure that all deportment 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 apply.

Legend:

White Approved: The applied science/standard has been approved for utilize. Yellow Approved w/Constraints: The technology/standard can be used inside the specified constraints located below the conclusion matrix in the footnote[1] and on the General tab. Grayness Unapproved: This technology or standard tin can be used only if a POA&Grand 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&One thousand Compliance Enforcement, has been granted to the projection squad or organization that wishes to use the technology. Orange Divest: VA has decided to divest itself on the employ of the technology/standard. Equally a result, all projects currently utilizing the engineering/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to get 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 menses of fourth dimension this engineering is currently being evaluated, reviewed, and tested in controlled environments. Apply of this technology is strictly controlled and not bachelor for use within the general population. If a customer would like to use this technology, delight piece of work with your local or Regional OI&T office and contact the appropriate evaluation part displayed in the notes below the determination matrix. The Local or Regional OI&T function should submit an research to the TRM if they crave further assistance or if the evaluating office is not listed in the notes below.

Release/Version Data:

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

For case, a technology canonical with a decision for 7.ten would cover any version of 7.(Anything) - 7.(Anything). Yet, a seven.4.x determination would embrace any version of 7.four.(Anything), simply would non cover any version of seven.5.10 or 7.6.10 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 only is non to exceed or bear upon previous decimal places.

For example, a technology approved with a determination for 12.6.4+ would embrace any version that is greater than 12.half-dozen.iv, but would not exceed the .six 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.

<By	CY2021				CY2022				CY2023				Future>
Release	Q1	Q2	Q3	Q4	Q1	Q2	Q3	Q4	Q1	Q2	Q3	Q4
3.0	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved
3.x.x	Approved westward/Constraints [3, four, 6]	Approved west/Constraints [3, 4, half dozen]	Approved west/Constraints [3, 4, 6]	Approved west/Constraints [3, 4, six]	Canonical due west/Constraints [iii, 4, vi]	Approved w/Constraints [iii, 4, 6]	Approved w/Constraints [3, 4, 6]	Canonical west/Constraints [3, 4, 6]	Approved due west/Constraints [iii, iv, 6]	Approved w/Constraints [iii, four, 6]	Canonical w/Constraints [3, 4, 6]	Canonical west/Constraints [3, 4, 6]
	Decision Constraints [1] Per the May fifth, 2015 memorandum from the VA Chief Information Security Officeholder (CISO) FIPS 140-2 Validate Full Deejay Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database direction must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at balance at the application level. If FIPS 140-2 encryption at the application level is non technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Advisable access enforcement and concrete security control must also be implemented. All instances of deployment using this engineering science should exist reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the organisation owner to piece of work with the local CIO (or designee) and Data Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in identify and documented in a Organization Security Program (SSP). [2] Per the May fifth, 2015 memorandum from the VA Chief Information Security Officeholder (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Residuum in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must utilise Federal Data Processing Standards (FIPS) 140-two 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 non technically possible, FIPS 140-2 compliant full disk encryption (FOE) must exist implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also exist 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 Officeholder (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in identify and documented in a System Security Program (SSP). [iii] Engineering science must remain patched and operated in accord with Federal and Department security policies and guidelines in order to mitigate known and future security vulnerabilities. [4] Users must ensure that Microsoft .NET Framework, Microsoft Internet Information Services (IIS), Microsoft Structured Query Language (SQL) Server and Microsoft Internet Explorer are implemented with VA-approved baselines. (refer to the 'Category' tab under 'Runtime Dependencies') [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 exist reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. [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 applied science should exist reviewed by the local ISO (Data Security Officer) to ensure compliance with VA Handbook 6500.
Annotation:	At the time of writing, version 3.0.35 is the most current version and was released 02/24/2020. 3.0 is unapproved because information technology is covered nether 3.x.x.

The following reference(s) are associated with this entry:

Type	Name	Source	Description
There are no references identified for this entry.

Note: This list may not exist complete. No component, listed or unlisted, may be used outside of the technology in which information technology is released. The usage decision for a component is plant in the Determination and Conclusion Constraints.

Name	Description
No components have been identified for this entry.

Domain Surface area	Category	Customer Guidance	Category Locked By ELT Appointment
Health Care Administrative	Health Administration

• Windows Client - Approved w/Constraints
• Windows Server - Approved w/Constraints

Comparable Technologies:

• No comparable entries have been identified.

Adoption Benefits

• This technology has a comprehensive prepare of documentation.

• At the time of writing, no National Institute of Standards and Technology (NIST) vulnerabilities had been reported and no VA Network Security Operations Center (NSOC) bulletins had been issued for the latest versions of this applied science.

• This technology may improve productivity for specific staff whose responsibilities include health system monitoring.

• There are minimal other TRM-approved technologies that provide the aforementioned functionality.

Adoption Risks

• The potential exists to shop Personally Identifiable Information (PII), Protected Wellness Information (PHI) and/or VA Sensitive data and proper security standards must be followed in these cases.

• Due to the rapid release schedule of this technology, the VA may exist unable to update to the near recent patch and may crave a deployment model requiring the use of specific versions.

Architectural Benefits

• This technology is compatible with multiple other Technical Reference Model (TRM) technologies and standards used by the organisation.

• This technology can use a VA-preferred database.

Architectural Risks

• This technology is not portable every bit it runs only on Windows platforms.

- The data contained on this folio is accurate equally of the Determination Date (03/10/2020).

floresdialt1936.blogspot.com

Source: https://www.oit.va.gov/Services/TRM/ToolPage.aspx?tid=7204

Share this post