BACKGROUND - Veterans Affairs



PERFORMANCE WORK STATEMENT (PWS)DEPARTMENT OF VETERANS AFFAIRSOffice of Information & TechnologyData Architecture (DA)Data Management Architecture Service (DMAS)Date: October 18, 2011TAC-12-03311Task Order PWS Version Number: 0.1 Version HistoryTemplate Version #Version DescriptionRelease Date1.0Initial ReleaseContents TOC \o "1-3" \h \z \u 1.0BACKGROUND PAGEREF _Toc307812750 \h 52.0APPLICABLE DOCUMENTS PAGEREF _Toc307812751 \h 63.0SCOPE OF WORK PAGEREF _Toc307812752 \h 63.1APPLICABILITY PAGEREF _Toc307812753 \h 93.2ORDER TYPE PAGEREF _Toc307812754 \h 94.0PERFORMANCE DETAILS PAGEREF _Toc307812755 \h 94.1PERFORMANCE PERIOD PAGEREF _Toc307812756 \h 94.2PLACE OF PERFORMANCE PAGEREF _Toc307812757 \h 94.3TRAVEL OR SPECIAL REQUIREMENTS PAGEREF _Toc307812758 \h 104.4CONTRACT MANAGEMENT PAGEREF _Toc307812759 \h 114.5GOVERNMENT FURNISHED PROPERTY PAGEREF _Toc307812760 \h 114.6SECURITY PAGEREF _Toc307812761 \h 114.6.1POSITION SENSITIVITY PAGEREF _Toc307812762 \h 125.0SPECIFIC TASKS AND DELIVERABLES PAGEREF _Toc307812763 \h 135.1TASK PROJECT MANAGEMENT PAGEREF _Toc307812764 \h 145.1.1PROJECT MANAGEMENT PLAN PAGEREF _Toc307812765 \h 145.1.2project Kick-off meeting and Meeting support PAGEREF _Toc307812766 \h 145.1.3REPORTING REQUIREMENTS PAGEREF _Toc307812767 \h 155.2DMAS COMMON SERVICES DEVELOPMENT PAGEREF _Toc307812768 \h 165.3DMAS Ongoing Development and Maintenance of Existing Development Efforts PAGEREF _Toc307812769 \h 165.4DMAS UPDATES TO SERVER MODELS PAGEREF _Toc307812770 \h 175.5DMAS MAPPING OF DATA MODELS PAGEREF _Toc307812771 \h 175.6DMAS NEW DEVELOPMENT AND MAINTENANCE PAGEREF _Toc307812772 \h 185.7DMAS LOGICAL AND PHYSICAL DATA MODELS PAGEREF _Toc307812773 \h 195.8DMAS Enterprise Data Architecture PAGEREF _Toc307812774 \h 205.9DMAS Websites PAGEREF _Toc307812775 \h 215.10DMAS ARTIFACT ELECTRONIC RECORD PAGEREF _Toc307812776 \h 215.11DMAS REQUESTS FOR ARCHITECTURE CHANGE (RFAC) PAGEREF _Toc307812777 \h 225.12DMAS DATA MODEL PROJECT-LEVEL ACTIVITIES PAGEREF _Toc307812778 \h 245.13DMAS GRAPHICAL INTERFACE PORTALS PAGEREF _Toc307812779 \h 245.14DMAS TRAINING PAGEREF _Toc307812780 \h 255.15DMAS BACKUP/DISASTER RECOVERY PLAN PAGEREF _Toc307812782 \h 265.16Optional Task 1 - Office of the Secretary Requirement(s) (includes congress, omb, white house) PAGEREF _Toc307812783 \h 265.17Optional Task 2 - VA Business Line Requirement(s) PAGEREF _Toc307812784 \h 265.18Optional Task 3 - External Government Agency Requirement(s) PAGEREF _Toc307812785 \h 275.19<ADDITIONAL TASK(S)> PAGEREF _Toc307812786 \h 276.0GENERAL REQUIREMENTS PAGEREF _Toc307812787 \h 276.1PERFORMANCE METRICS PAGEREF _Toc307812788 \h 276.2ORGANIZATIONAL CONFLICT of INTEREST (Add For A&A Services) PAGEREF _Toc307812789 \h 28APPENDIX A PAGEREF _Toc307812790 \h 30 BACKGROUNDThe mission of the Department of Veterans Affairs (VA), Office of Information & Technology (OI&T), Data Architecture (DA) Division is to provide benefits and services to Veterans of the United States.? In meeting these goals, OI&T strives to provide high quality, effective, and efficient Information Technology (IT) services in support of the Veteran and family members related health care, veterans benefits to include services, such as, i.e., Compensation and Pension (C&P), Education, Work Study Management Programs, Loans, Death Benefits, etc. VA depends on Information Management/Information Technology (IM/IT) systems to meet mission goals. The Office of Architecture, Strategy and Design (ASD), Data Architecture (DA) Division is a Service within the OI&T Organization that supports the VA mission and goal. DA is responsible for the design, development, architecture and modeling of veteran related data that supports systems, applications and/or services program efforts for Veterans Benefits Administration (VBA), Veteran Health Administration (VHA), National Cemetery Administration (NCA), as well as all other VA Business Lines across VA to include Enterprise Architecture programs, and external VA sources; such as, Department of Defense (DOD), Health and Human Services (HHS), Social Security Administration (SSA), etc. The design and development of logical and physical data models are currently underway. The Data Modeling effort is an ever evolving and ongoing program effort. Throughout the life of the VA, systems, applications and/or services shall continue to be developed and data modeling efforts to capture and provide VA with access to information shall remain as a constant requirement without end. DA has and is accomplishing this effort by capturing data from several VA systems, applications and/or services, is developing and implementing architectural data models, based on VA requirements and is providing access to the data models across VA business lines. The data being captured for Data Architecture and Enterprise Architecture data modeling program efforts were and are being designed and developed to include data in motion, static or data at rest, data imports, interfaces, portals, etc. DA also provides support to VA programs by managing data imports from the requirements phase to the production phase throughout the Software Development Life Cycle (SDLC). This contract shall support new requirements planned for Data Management Architect Services (DMAS) and the information stored by DMAS efforts shall be shared and provided across VA business lines. The Data Architecture (DA) Division within the Office of Architecture, Strategy and Design (ASD) has been mandated to develop and implement programs to capture and store veteran related data. DA is currently developing DMAS program efforts, i.e., the Data Architecture Repository (DAR) and the VBA Corporate Database. These program efforts developed to date are the DAR and VBA Corporate Database and these DMAS program efforts support data from numerous VA applications, systems and/or services supported by Veterans Benefits Administration (VBA), Veterans Health Administration (VHA), National Cemetery Administration (NCA) and other VA business lines. The Data Architecture Repository (DAR) and the VBA Corporate Database are the start for DMAS program efforts, as there are an abundance of VA applications that may be supported by DMAS program efforts. Currently the DAR and the VBA Corporate Database capture veteran related metadata and data from several VA applications supported by VBA, VHA, NCA and other VA business lines. VA Business Lines have access to information on Veterans Health Care, Veterans Benefits, Veterans Death Benefits, etc.The effort to capture existing data, as well as developing logistical and physical data models, and enterprise data models for business lines across VA may reduce the number of new development efforts in the future. This Performance Work Statement (PWS) describes the Technical Support Services required to continue moving forward with the DMAS program efforts to provide essential and necessary information that may be captured from the many applications, systems and/or services in existence throughout VA. VA veteran related information is imperative to all business lines across VA and must be provided to support business needs, as well as VA goals and objectives. This Performance Work Statement (PWS) is critical as it supports the sixteen VA initiatives. DMAS program efforts are planned to support all sixteen initiatives.The DAR is currently captures some of the data necessary for business lines across VA to accomplish their business requirements for the VA initiatives. The DMAS program development efforts plan to continue capturing data from VA applications, systems, and/or services and provide business lines access to the data, as well as continue to support the VA sixteen initiatives. This contract shall also provide the necessary technical expertise to satisfy business needs, as well as new requirements in support of the sixteen VA initiatives.APPLICABLE DOCUMENTSDocuments referenced or germane to this Performance Work Statement (PWS) are listed below. In the performance of the tasks associated with this Performance Work Statement, the Contractor shall comply with the following:44 U.S.C. § 3541,?“Federal Information Security Management Act (FISMA) of 2002”Federal Information Processing Standards (FIPS) Publication 140-2, “Security Requirements For Cryptographic Modules”FIPS Pub 201, “Personal Identity Verification of Federal Employees and Contractors,” March 200610 U.S.C. § 2224, "Defense Information Assurance Program"Software Engineering Institute, Software Acquisition Capability Maturity Modeling (SA CMM) Level 2 procedures and processes5 U.S.C. § 552a, as amended, “The Privacy Act of 1974” 42 U.S.C. § 2000d “Title VI of the Civil Rights Act of 1964”Department of Veterans Affairs (VA) Directive 0710, “Personnel Suitability and Security Program,” September 10, 2004VA Directive 6102, “Internet/Intranet Services,” July 15, 200836 C.F.R. Part 1194 “Electronic and Information Technology Accessibility Standards,” July 1, 2003OMB Circular A-130, “Management of Federal Information Resources,” November 28, 200032 C.F.R. Part 199, “Civilian Health and Medical Program of the Uniformed Services (CHAMPUS)”An Introductory Resource Guide for Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule, March 2005Sections 504 and 508 of the Rehabilitation Act (29 U.S.C. § 794d), as amended by the Workforce Investment Act of 1998 (P.L. 105-220), August 7, 1998Homeland Security Presidential Directive (12) (HSPD-12)VA Directive 6500, “Information Security Program,” August 4, 2006VA Handbook 6500, “Information Security Program,” September 18, 2007VA Handbook, 6500.5, Include the Security and Privacy in System Development Life Cycle.VA Handbook 6500.6, “Contract Security,” March 12, 2010Program Management Accountability System (PMAS) portal (reference PWS References -Technical Library at )OED ProPath Process Methodology (reference PWS References -Technical Library and ProPath Library links at ) NOTE: In the event of a conflict, OED ProPath takes precedence over other processes or methodologies. Technical Reference Model (TRM) (reference at )National Institute Standards and Technology (NIST) Special PublicationsSCOPE OF WORKThe Contractor shall provide technical expertise to continue with developing and implementing DMAS program efforts based on VA business line requirements and needs. The contractor shall provide highly technical resources with the expertise and experience to develop DMAS program efforts. The contractor shall demonstrate their technical expertise, knowledge and program experience in designing and developing DMAS programs that capture many forms of data, such as, i.e., data in motion, static or data at rest, interfaces and portals to include data architecture logical and physical modeling efforts, Canonical models and implementing the data models at the enterprise level. VA experience and technical expertise and knowledge in the development of current DMAS program efforts, as well as with the applications supported for VBA, VHA and NCA are also essential due to the complexity and magnitude of this program effort. The contractor shall provide access to DMAS information based on VA business line requirements and needs. ORDER TYPEThe effort shall be proposed on a Firm Fixed Price (FFP) basis. PERFORMANCE DETAILSPERFORMANCE PERIODThe period of performance shall be One Base Period of twelve (12) Months and Four (4) twelve (12) Month Options for a total of Five (5) years (60 months). Any work at the government site shall not take place on Federal holidays or weekends unless directed by the Contracting Officer (CO). If required, the CO may designate the Contractor to work during holidays and weekends. There are ten (10) Federal holidays set by law (USC Title 5 Section 6103) that the VA follows:Under current definitions, four are set by date:New Year's DayJanuary 1Independence DayJuly 4Veterans DayNovember 11Christmas DayDecember 25If any of the above falls on a Saturday, then Friday shall be observed as a holiday. Similarly, if one falls on a Sunday, then Monday shall be observed as a holiday.The other six are set by a day of the week and month:Martin Luther King's BirthdayThird Monday in JanuaryWashington's BirthdayThird Monday in FebruaryMemorial DayLast Monday in MayLabor DayFirst Monday in SeptemberColumbus DaySecond Monday in OctoberThanksgivingFourth Thursday in November TRAVEL OR SPECIAL REQUIREMENTSThe Government anticipates travel under this effort to perform the tasks associated with the effort, as well as to attend program-related meetings or conferences through the period of performance.? Include all estimated travel costs in your firm-fixed price line items. These costs will not be directly reimbursed by the Government.Total estimated number of trips in support of this effort is eight (8). Anticipated locations shall be within the Continental United States (CONUS), include the following, estimated at four (4) days in duration:Non-government conference centers within the Continental U.S. (maximum of four (4) Contractors).Designated Government facilities, such as VISNS, to be determined, within the Continental U.S. (maximum of two (2) Contractors) per trip.SECURITyPOSITION SENSITIVITYPosition Sensitivity and Background Investigation - The position sensitivity and the level of background investigation commensurate with the required level of access is: FORMCHECKBOX Low/NACI FORMCHECKBOX Moderate/MBI FORMCHECKBOX High/BIPosition SensitivityBackground Investigation (in accordance with Department of Veterans Affairs 0710 Handbook, “”Personnel Security Suitability Program,” Appendix A)LowNational Agency Check with Written Inquiries (NACI) A NACI is conducted by OPM and covers a 5-year period. It consists of a review of records contained in the OPM Security Investigations Index (SII) and the DOD Defense Central Investigations Index (DCII), FBI name check, FBI fingerprint check, and written inquiries to previous employers and references listed on the application for employment. In VA it is used for Non-sensitive or Low Risk positions.ModerateMinimum Background Investigation (MBI) A MBI is conducted by OPM and covers a 5-year period. It consists of a review of National Agency Check (NAC) records [OPM Security Investigations Index (SII), DOD Defense Central Investigations Index (DCII), FBI name check, and a FBI fingerprint check], a credit report covering a period of 5 years, written inquiries to previous employers and references listed on the application for employment; an interview with the subject, law enforcement check; and a verification of the educational degree.High Background Investigation (BI) A BI is conducted by OPM and covers a 10-year period. It consists of a review of National Agency Check (NAC) records [OPM Security Investigations Index (SII), DOD Defense Central Investigations Index (DCII), FBI name check, and a FBI fingerprint check report], a credit report covering a period of 10 years, written inquiries to previous employers and references listed on the application for employment; an interview with the subject, spouse, neighbors, supervisor, co-workers; court records, law enforcement check, and a verification of the educational degree.SPECIFIC TASKS AND DELIVERABLESThe Contractor shall perform the following: TASK PROJECT MANAGEMENTPROJECT MANAGEMENT PLAN The Contractor shall draft a Project Management Plan (PMP) that lays out the Contractor’s approach, timeline and tools to be used in execution of the contract. ?The PMP should take the form of both a narrative and graphic format that displays the schedule, milestones, risks and resource support.??The PMP shall also include how the Contractor shall coordinate and execute planned, routine, and ad hoc data collection reporting requests, and deliverable as identified within the PWS to support current DMAS program development efforts, VBA Corporate Database and Data Architecture Repositry as well as new DMAS programs. The Contractor shall describe in detail the approach to be used for each aspect of each task in this PWS. The PMP shall also address the risk, quality and technical management, Change and Configuration Management and Communications Management approach, work breakdown structure and proposed personnel. The initial baseline PMP shall be concurred upon and updated monthly thereafter. The Contractor shall update and maintain the VA PM approved PMP throughout the period of performance. Deliverables: Project Management Planproject Kick-off meeting and Meeting supportThe Contractor shall brief the VA DMAS Project Team on the PMP and the approach to manage the scheduling and execution of Information Technology project in accordance with standard Information Technology processes, such as those detailed in Projecct Management Book of Knowledge (PMBOK).. The Contractor shall provide a kick-off briefing to the VA Project Team reviewing the Project Management template. The Contractor shall provide support to facilitate the logistics of Project Meetings to include scheduling and arrangement of meetings, providing meeting leader or coordinator, developing meeting materials and presentations, dissemination of meeting minutes, record and track status of actions items.The Contractor shall also attend PM hosted project meetings including the weekly update calls to discuss and review project status. Deliverables:Kick-Off MaterialsMeeting MaterialsMeeting MinutesProject Management Template for a Monthly Progress Report:Tasks required to accomplish workContractor’s methodology for completing the taskMilestone schedule Proposed draft and final deliverable due datesOutline of the proposed deliverables and a format for the required weekly, monthly, quarterly, and annual status reports, including business case justification analyses REPORTING REQUIREMENTSThe Contractor shall provide the Contracting Officer’s Representative (COR) with Monthly Progress Reports in electronic form in Microsoft Word and Project formats.? The report shall include detailed instructions/explanations for each required data element, to ensure that data is accurate and consistent. These reports shall reflect data as of the last day of the preceding Month? The Monthly Progress Reports shall cover all work completed during the reporting period and work planned for the subsequent reporting period.? The report shall also identify any problems that arose and a description of how the problems were resolved.? If problems have not been completely resolved, the Contractor shall provide an explanation including their plan and timeframe for resolving the issue. The Contractor shall monitor performance against the PMP and report any deviations. It is expected that the Contractor will keep in communication with the VA accordingly so that issues that arise are transparent to both parties to prevent escalation of outstanding issues.The Contractor shall notify the VA Program Manager (VA PM) and COTR in writing, immediately if problems arise adversely impacting the performance of the PWS.? Quarterly and Annual Status Reports shall be developed and shall be roll-ups and summary of the monthly reports.Deliverables:? Monthly Progress ReportDMAS COMMON SERVICES DEVELOPMENTThe Contractor shall develop common services for access to existing and new DMAS programs. The DMAS platforms currently being supported for development is the Java2 Platform Enterprise Edition (J2EE) and Application Software Architecture (ASA). VA has many diverse systems that share sufficient services/capabilities permitting the creation of common services for access. The Contractor shall with DMAS team, participation identify the requirements for these common services and identify the potential benefit of each candidate service. The VA Task Order Project Management (TOPM) shall select the services for the development effort based on the potential benefits, reusability and the ability to integrate into existing and future software. The Contractor shall develop and document the Software Development Life Cycle (SDLC) to be used in developing the common services. It shall follow a standard SDLC including requirements, development, testing, pre-certification, certification, testing, pre-production and then implementation into production. The VA PM shall approve the SDLC. As part of the development process, the Contractor shall create a document using Java 2 Platform Enterprise Edition (J2EE) Common Services Technical Specifications that document the list of services to be developed. This document shall include the technical specifications for each of the selected services. The Contractor shall also develop a J2EE Common Services Test Plan for testing and debugging these common services. The Test Plan shall include a detailed test plan, schedule and criterion for success. The Contractor shall execute the Test Plan and report the results in a documented J2EE Common Services Test Report.Deliverables:Contractor SDLC ProcessJ2EE Common Services Technical SpecificationsTest PlanTest ReportDMAS Ongoing Development and Maintenance of Existing Development EffortsThe Contractor shall perform all project-level activities needed to maintain current DMAS development efforts and new requirements to include: data modeling, data analysis, business analysis and research for the application development teams. The Contractor shall promote the effective use of existing DMAS program development efforts to support VBA, VHA, NCA, as well as other business lines across VAAll activities performed on this subtask shall be reported in the Monthly Progress ReportCommunications/Collaborative WebsiteDMAS UPDATES TO SERVER MODELSDMAS UPDATES TO SERVER MODELS TO SUPPORT DATA IMPORTS AND EXPORTS FROM THE REQUIREMENTS PHASE AND TO AND FROM THE PRODUCTION PHASE OF THE SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC)The Contractor shall identify and document processes to include the appropriate procedures, tools, methodologies and resources to uncover data problems before they adversely affect business application processing. The Contractor shall perform analyzes to identify short and long term solutions that can reduce the number of data errors and develop plans and schedules to implement these solutions. The processes and solution analyzes shall also consider risk analysis for new requirements. These solutions shall be approved by business project managers and coordinated with application development project managers to ensure they are not in conflict with other business requirements or any current software development.Deliverables:Data Problem Identification ProcessAnalysis Report on Short and Long Term Data Error solutionsDMAS MAPPING OF DATA MODELSDEVELOP AND DOCUMENT DMAS MAPPING OF PROJECT METADATA AND DATA TO FINAL DATA MODELSThe Contractor shall conduct data analyses of the DMAS data models to map current implementations to the Enterprise Logical Data Model (LDM), Enterprise Architecture and the Business Relationship Model (BRM). This includes documenting the mapping for each of the project’s metadata and data from databases to the final data models. The Contractor shall perform the mapping to appropriate database tables and database attributes to support Veteran related metadata/data. Progress, efforts, and updates should be input to the monthly progress report in a separate section.All activities performed on this subtask shall be reported in the Monthly Progress ReportDMAS NEW DEVELOPMENT AND MAINTENANCEDMAS DEVELOPMENT AND MAINTENANCE OF NEW AND EXISTING PROGRAM EFFORTSThe Contractor shall maintain and update existing DMAS in-house developed applications. The Contractor shall analyze and implement all Request for Architecture Change (RFAC’s) in support of development and implementation of business line applications, such as Compensation & Pension (C&P), Education (EDU), Loan Guaranty (LGY), Office of Resource Management (ORM), etc. The Contractor shall work closely with the Operations staff to implement changes to the preproduction and production DMAS environments. The changes shall be implemented in accordance with new software releases and the schedule established by the DMAS Operations staff. The new release shall be documented in application release notes. All activities performed on this subtask shall be reported in the Monthly Progress Report. Each application note and a brief summary shall be reported in a separate section of the “Monthly Progress Report.”Tasks:OngoingRequest for Architectural Change (RFAC)Participant Merge Create, Read, Update, Delete (CRUD)Program Schema Objects ReportGrant MeisterParticipant Data QueryParticipant FetchParticipant ExplorerDDL (Dynamic Data Language) GeneratorDMAS LOGICAL AND PHYSICAL DATA MODELSDMAS LOGICAL AND PHYSICAL DATA MODEL DEVELOPMENTThe Contractor shall support the development and implementation of DMAS Logical and Physical data Models by developing a Data Model Review, Implementation and Maintenance Plan to maintain existing and new DMAS program data models, as new data requirements are received. A few of the existing DMAS program efforts include applications, such as, i.e., Compensation and Pension (C&P); Education (EDU); Loan Guaranty (LGY); Vocational Rehabilitation and Employment (VR&E); Office of Resource Management (ORM), Veterans Affairs Department of Defense Identity Repository (VADIR), etc. This task shall ensure the proper development and maintenance of existing and new data models.The Contractor shall provide the Data Architecture Division support in the development of Logical and Physical Data Models for VA programs. The Contractor shall provide support for managing data imports and exports from the requirements phase to the production phase of the SDLC. The Contractor shall support and assist business lines across VA by managing data imports and exports from the requirements phase to the production phase. This includes developing a model that includes the list of common data elements to be standardized for VA consensus and approval. All activities performed on this subtask shall be reported in the Monthly (and Quarterly) Progress ReportTasks:OngoingData AnalysisBusiness Analysis Collation and documentation of Functional RequirementsConversion to Technical RequirementsResearch of Common Elements and Development of Plans to Ensure the Proper Validation of Data from other OrganizationsDocumentation of Updates to the Data Models, Monthly and Quarterly Release of the DMAS Data Models Following Receipt of VA PM ApprovalDevelop, Document and Implement Data Model Review ProcessDevelop, Document and Implement Data Model Maintenance PlanDevelop modeling artifacts using IDEF1X, Information Engineering (IE), Universal Modeling Language (UML), and/or other notations. The data models shall conform to the Federal Enterprise Architecture (FEA) Data Reference Model (DRM) guidanceDevelop physical and logical data models for new requirements received from business lines across VAPerform analysis on databases for business lines across VA, for example: Vista, VADIR, Maverick, and National Data Systems (NDS), to create the “As-Is” logical data models and also to identify and standardize the common data. This includes modeling, developing and standardizing database schemas. This includes documenting the “As-Is” Logical Data ModelSupport data cleansing and data standardization as a result of the on-going and ever-evolving evolution of the Enterprise Data Architecture initiative and any other Department level or Government-wide initiatives that require Information Architecture resources.Develop the “To-Be” Logical Data Model and document that in “To-Be” Enterprise Logical Data Model. This includes documenting the “To Be” Logical Data Model.Support the “As-Is” Enterprise Data Model, along with the Business Context Layer, Information Exchange Packages and Data Description Layer per FEA DRM to include a documented list of candidate data elements for standardization. Document in “As-Is” Enterprise Data ModelSupport the “To-Be” Enterprise Data Model, along with the Business Context Layer, Information Exchange Packages, and Data Description Layer per the FEA DRM to include the standardization of data elements to be identified in the “To Be” Enterprise Data Model. Document in “To-Be” Enterprise Logical Data Model and in the “To Be” Enterprise Physical Data Model.DMAS Enterprise Data ArchitectureDMAS Enterprise Data Architecture to maintain and update existing DMAS in-house developed applicationsThe VA PM shall approve any required changes. The Contractor shall then develop the code, develop a test plan and test the data models per the test plan. The Contractor shall ensure that changes have no adverse impact on business application processing. After receiving update approval from the VA PM the new DMAS release shall be documented in application release notes. All activities performed on this subtask shall be reported in the Monthly Progress Report. Each application note and a brief summary shall be reported in a separate section of the monthly report.Tasks:Request for Architectural Changes (RFAC)Participant Merge Create, Read, Update, Delete (CRUD)VBA Corporate Database Schema objects reportGrant MeisterParticipant Data QueryParticipant FetchParticipant ExplorerDDL (Dynamic Data Language) GeneratorDeliverables:Test PlanMonthly Report Referencing Application ReleasesDMAS WebsitesDMAS Website Development EffortsThe Contractor shall maintain and update existing DMAS websites. The Contractor shall also develop, implement, update and maintain web sites to support new DMAS requirements.Tasks:OngoingData DictionaryData ModelReference DataMaintenance of Software Supported Management ToolsDMAS ARTIFACT ELECTRONIC RECORDDMAS ARTIFACT ELECTRONIC RECORD KEEPING AND MAINTENANCEThe Contractor shall develop and maintain an electronic record to document the DMAS artifacts. The Contractor shall provide access the electronic artifact to business lines across VA. The DMAS artifact electronic records provides the VA user community to register data architecture artifact, establish data relationships, establish data accounts, a visual of the data architecture models, build workflows to guide data architecture activities, status reports, statistical data and reports, store data architecture artifacts and provides the capability to conduct data architecture analyses. This activity supports the data captured and stored from VA applications, systems and/or services.Tasks: Ongoinga)Update and Maintain Electronic Records for DMAS ArtifactArchitecture ArtifactData RelationshipsVA Business Line Data AccountsData Architecture ModelsWorkflowsReporting RequirementsStatistical Data RequirementsData QueriesDeliverables:Monthly Progress ReportActivityNew User AccountsNew RequirementsSpecial Reports ProvidedNumber of DMAS QueriesDMAS REQUESTS FOR ARCHITECTURE CHANGE (RFAC)DMAS RFAC UTILIZING THE DATA DEFINITION LANGUAGE (DDL) AND DATA MANIPULATION LANGUAGE (DML)The Contractor shall analyze and implement Requests for Architecture Change (RFAC) in support of development and implementation of business line applications. The business line applications, such as, Compensation and Pension, Education, Loan Guaranty, Office of Resource Management and Vocational Rehabilitation and Employment, etc. will initiate the RFAC. The Contractor shall follow the RFAC process, and track the Architecture Change Requests as outlined in the “Requests for Architecture Change (RFAC) User Guide.” This includes the implementation of the DMAS data scripts in existing DMAS development environments to implement the RFAC. It includes testing on the non-production databases, debugging of any identified issues, and final user acceptance by the appropriate VA business line management. The Contractor must ensure that testing the RFAC implementation on the non-production DMAS development environment does not adversely affect business application processing. The Contractor shall develop a Data Error Reduction Process to identify the appropriate procedures, tools, methodologies and resources to uncover and resolve data problems before they adversely affect business application processing. The process shall cover short-term and long-term solutions, that can reduce the number of data errors and develop plans and schedules to implement these solutions. The solutions shall be written as standard procedures for analyzing and detecting data errors and quantify the efficacy of each proposed solution. These solutions shall be included in the process documentation along with the Dynamic Data Language (DDL) and Data Manipulation Language (DML) scripts. These solutions shall be approved by business project managers and coordinated with application development project managers to ensure they are not in conflict with other business requirements or any current software development. Following acceptance testing the Contractor shall provide the DMAS data scripts (Dynamic Data Language (DDL) and Data Manipulation Language (DML) and documentation for submission to the Hines Operations Staff for their testing on the pre-production and implementation on the DMAS program development environment. Transfer of the Dynamic Data Language (DDL) and Data Manipulation Language (DML) and documentation shall be via ftp.Implementation into the DMAS production environment shall be coordinated with software releases according to RFAC schedules and the published schedule of the Hines System Implementation Office (SIO).The documentation shall include a description and version number of the Dynamic Data Language (DDL) and Data Manipulation Language (DML) and a description of the updated application server model diagram. This updated application server model includes the Entity Relationship diagrams for the applications affected by the “Request for Architecture Changes.”The Contractor shall provide an End of Month progress report identifying the Requests from Architecture Changes (RFAC). The report shall include the percentage of completion for each request, as well as, the type of action taken and what action remains to complete the RFAC. The Contractor shall maintain Section 508 compliance for DMAS Web services.Tasks: OngoingAnalyze and Implement Requests for Architecture Changes (RFAC)Track RFAC’s According to RFAC User GuideImplement RFAC Data Scripts in DMAS Development EnvironmentsPerform RFAC Pre-Production Testing to Include Debugging and User AcceptanceAnalyze and Recommend Appropriate Procedures, Tools, Methodologies and Resources to Resolve Data Problems Develop and Implement Solutions to Reduce Data ErrorsDevelop and Implement Test PlanCoordinate DMAS Data Transfer and Testing with the Hines Operations Staff Install and Release Software Updates According to the RFAC Schedule and the Hines System Implementation Office ScheduleEnd of Month Progress ReportDeliverables:Data Error Reduction ProcessDMAS data scripts DDL and DML with documentationsTest PlanEnd of Month Progress ReportDMAS DATA MODEL PROJECT-LEVEL ACTIVITIESDMAS DATA ANALYSIS, BUSINESS ANALYSIS AND DATA MODELING TO SUPPORT PROJECT-LEVEL ACTIVITIESThe Contractor shall perform project-level activities needed to maintain the DMAS environments. This includes data analysis to ensure business line requirements are met such as in developing the data models, complete the business analysis and research for the application development teams. The Contractor shall promote the effective use of existing DMAS environments that support VHA, VBA, NCA and other business lines across VA such as the Data Architecture Repository and the VBA Corporate Database. The Contractor shall support Operations, Maintenance and Enhancements of DMAS program efforts. The Contractor shall elicit and document requirements, develop process and maintain modeling artifacts, provide expertise in specification writing and provide technical support to application development teams in the interpretation of standards for Graphical User Interface (GUI) design, system design, diagramming and modeling. The Contractor shall provide review and maintenance of DMAS project data models that support VBA, VHA, NCA and other business lines across VA, to include external Government Offices such as Department of Defense, Health and Human Services, Social Security Administration, etc. The Contractor shall research and analyze data issues, as directed by the TOPMTasks:OngoingData Analysis and Research of RequirementsData Analysis and Research of Data IssuesBusiness Analysis and Research of RequirementsDocument New Requirements Develop Specification, Interpret and Document Standards for Graphical User Interface (GUI) Design, System Design, Diagramming and ModelingDeliverables:DMAS GRAPHICAL INTERFACE PORTALSDMAS DEVELOPMENT AND IMPROVEMENT OF GRAPHICAL INTERACE PORTALSThe Contractor shall provide technical support and technical assistance to the Data Architecture Team to ensure success for DMAS development and the improvement of graphical interface portals. The Contractor shall provide high-level technical support and assistance to manage the DMAS platforms to include hardware and software. This shall include customizing, maintaining, managing and enhacing the Oracle-APEX COTS tool that is used to develop portals and drill down functionality; install, configure and document configuration of Oracle Application Express (APEX) on existing hardware; develop a DMAS program User Guide; develop and document DMAS Configuration Management Procedures; develop a DMAS Test Plan and perform test on DMAS portals; deliver a test report of the DMAS portals testing; develop and document a DMAS Operations and Maintenance Plan.Deliverables:APEX Configuration GuideDMAS User GuideDMAS Configuration Management ProceduresDatabase Portals Test PlanDatabase Portals Test ReportDMAS Operations and Maintenanace PlanDMAS TRAININGDMAS GUIDANCE, UINDERSTANDING AND TRAINING FOR USERS AND DEVELOPERS ACROSS VA BUSINESS LINESThe Contractor shall provide DMAS training and guidance to business lines across VA to include both the user community, as well as VA developers. The Contractor shall develop, and implement a User Training Guide. The training sessions shall be customized to the needs of the VA clients in support of specific DMAS requirements.Tasks:DMAS User GuideDMAS User Specific Customized Training PlanDeliverables:DMAS User Training GuideCustomized Training Plan DMAS BACKUP/DISASTER RECOVERY PLANDEVELOP AND IMPLEMENT DMAS BACKUP/DISASTER RECOVERY PLANSThe Contractor shall develop a strategic plan to support Disaster Recovery for DMAS program efforts. The Contractor shall solicit and document requirements that the backup plan must meet. The Contractor shall develop, document and implement the plan to meet those requirements.The Contractor shall include a Disaster Recovery plan into the strategic plan that includes protection of data and recovery of applications in the event of a disaster that impacts the Data Architecture Service’s ability to provide services. The disaster recovery plan shall include recovery service with redundant processing capability at the alternate VA data center and utilizes electronic data vaulting for applications designated as mission critical or essential support. Continuity of Operations shall be included in the strategic Backup/Disaster Recovery Plan. The Contractor shall solicit and document requirements for the Continuity of Operations and develop a plan to meet those requirements.Tasks:Document VA Business Line DMAS RequirementsDevelop/Implement DMAS Strategic PlanDevelop/Implement Backup Disaster Recovery PlanDeliverables:DMAS Backup/Disaster Recovery PlanOptional Task 1 - Office of the Secretary Requirement(s) (includes congress, omb, white house)Estimate of $500,000.00 (per requirement) Based on the extent and complexity of developing and supporting a complex DMAS Information Management System program effort.Optional Task 2 - VA Business Line Requirement(s)Estimate of $500,000.00 (per requirement) Based on the extent and complexity of developing and supporting a complex DMAS Information Management System program effort.Optional Task 3 - External Government Agency Requirement(s)Estimate of $600,000.00 (per requirement) Development for External Government Agencies for the purpose of sharing, transfer and accessing VA veteran related data is extremely complex to include added security measures. Department of Defense (DOD)Social Security Administration (SSA)Health and Human Services (HHS)Other Government Agencies that require veteran related dataGENERAL REQUIREMENTS PERFORMANCE METRICSThe table below defines the Performance Metrics associated with this effort. Performance ObjectivePerformance StandardAcceptable Performance LevelsSurveillance MethodA. Technical NeedsShows understanding of requirementsEfficient and effective in meeting requirements Meets technical needs and mission requirementsOffers quality services/productsSatisfactory or higherPerformance Based Service AssessmentSurveyB. ManagementCurrency of expertise.Personnel possess necessary knowledge, skills and abilities to perform tasks.Sufficient number of personnel to accomplish the mission.Meeting subcontracting goals.Responsiveness to customer.Satisfactory or higherPerformance Based Service AssessmentSurveyC. Project Milestones & ScheduleQuick response capability.Products completed, reviewed, delivered in timely manner.Notifies customer in advance of potential problems.Satisfactory or higherPerformance Based Service AssessmentSurveyD. CostAbility to manage cost.Timely communications regarding cost changes.Timely submission of cost vouchers.Satisfactory or higherPerformance Based Service AssessmentSurveyThe Government will utilize a Quality Assurance Surveillance Plan (QASP) throughout the life of the contract to ensure that the Contractor is performing the services required by this PWS in an acceptable manner. The Government reserves the right to alter or change the QASP at its own discretion. A Performance Based Service Assessment Survey will be used in combination with the QASP to assist the Government in determining acceptable performance levels. The COTR will determine if the performance of the Contractor is below a metric standard and deem it unacceptable.? The COTR will then notify the Contracting Officer. ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download