The proposed VEMS solution is comprised of commercial off-the-shelf (COTS) software with selected modifications to accommodate current VA standards. The documentation of these standards is referenced in Appendix A of this document.
This solution incorporates elements of COTS software to provide the following functionality:
Beneficiary Identification Records Locator Subsystem (BIRLS)
Correspondence Tracking System (CTS)
Dun & Bradstreet (D&B)
WestLaw Legal Research
Table : Scope Exclusions
The VEMS solution uses a service-oriented architecture (SOA) to accommodate the integration of data via standards-based data communications. At this time, the VEMS solution does not include integration with the following external data systems (but the service integration framework is designed to accommodate these data suppliers once the transmission protocols, data payloads, frequency of exchange, and service level agreements with these data providers have been defined and approved for integration by the government):
Federal Procurement Data System (FPDS),
Electronic Contract Management System (eCMS)
Contractor Performance Assessment Reporting System (CPARS),
Past Performance Information Retrieval System (PPIRS),
Small Business Administration (SBA),
Dynamic Small Business Search system (DSBS),
Defense Manpower Data Center (DMDC),
Disability Evaluation System (DES),
The National Cemetery Administration’s Veteran Death Notification System (VDNS)
The system does not include enhanced modeling and simulation (M&S) capabilities as part of the initial releases including the project’s base period. All of the excluded integrations listed above and additional/expanded functionality are to be implemented (as available) as components of the project’s Option Period, if approved by the VA. Also, while this solution includes the design and forethought necessary to provide VEMS-based information via a mobile platform, the deployment of those capabilities has also been defined as an optional task to occur in the project’s later stages.
Further, for the COTS components of the solution architecture, consideration will be given to design decisions to ensure the future enhancements that would come from implementing items currently in the exclusions list. The COTS products listed throughout this document have been selected due to their ability to meet all requirements as defined within the constraints requirements.
1.4.Relationship to Other Plans
As an enterprise solution, VEMS has and must accommodate inter-system dependencies. These dependencies are managed through the requirements process, IPT meetings, alignment with the VA Technical Reference Model, and alignment with the VA Enterprise Architecture. This project will have key dependencies with the following independent programs:
VA Identity Access Management (IAM)-This project will be dependent upon services available from the IAM group at the time of implementation, with focus on Active Directory Federated Services and future support for HSPD12 PIV authentication. The project will also be dependent on the availability to leverage existing authentication services for external users developed by other VA projects such as My HealthEVet.
Benefits Gateway System (BGS)-The project will look to leverage services provided by BGS for Veteran Identity and Veteran Disability information. Alignment with the latest systems such as the Master Veteran Index (MVI) will ensure the project leverages the most authoritative data source. Based upon the project schedules for BGS will determine whether integration with BIRLS will be required for disability information.