Attachment 0006 EMS_Task 1 PWS.docx

PERFORMANCE WORK STATEMENT (PWS)

FOR

Emergency Management Sustainment

1. Background

2. Scope

3. Applicable Documents

4. Performance Requirements

5. Options

6. Deliverables

7. QASP

8. General Requirements and Information

9. Security

10. Environmental

11. Accounting for Contract Service

12. Other Requirements

13. Non-United States (U.S.) Citizen Employee Requirements

14. Point of Contact

1. Background

U.S. Army Armament Research, Development, and Engineering Center (CCDC - ARMAMENTS CENTER), in support of Tank-automotive and Armaments Command (TACOM) Life Cycle Management Command (LCMC) is tasked to sustain Emergency Management (EM) capabilities to multiple Installations by providing labor, materials, and equipment to perform life-cycle sustainment services for a Mass Warning Notification (MWN) solution, to include enterprise Network Alerting Systems (NAS), Telephonic Alerting System (TAS), and Giant Voice Integration (GVI), as well as Audio Visual Notification System (AVNS), and Enhanced 911 (E-911) to selected installations. The current NAS and TAS solution is provided by US Army Alert!. The MWN-integrated COTS AVNS and GVI solution is provided by Alertus. The current COTS E-911 solutions are provided by Airbus and Microautomation. Work includes preventive and corrective maintenance, repair and replacement, services calls, and systems/software upgrades, and system training. These technology areas were established as a result of emergency management gaps and requirements identified in the Directed Requirements for Emergency Management Modernization Program Capabilities in Response to the Fort Hood, Army Internal Review Team (Applicable Document 3.1). It was determined that emergency staff at installations were not able to inform and track their personnel during emergency situations.

2. Scope

The Scope of the task includes preventive and corrective maintenance, repair and replacement, services calls, and systems/software upgrades.

3. Applicable Documents

3.1. Directed Requirements for Emergency Management Modernization Program Capabilities in Response to the Fort Hood, Army Internal Review Team PWS Para 1, 4.15

3.2. Fielded System List (FSL) (possible work locations are not limited to the locations listed) PWS Para 4, 4.2.1, 4.9, 4.11, 4.16.1, 8.2.1, 8.4.1

3.3. DoDAF 2.02 PWS Para 4.2

3.4. Department of Defense (DoD) Instruction 8500.01, Cybersecurity, 14 March, 2014 PWS Para 4.10

3.5. DoD Instruction 8510.01, “Risk Management Framework (RMF) for DoD Information Technology (IT)”, 12 March 2014 PWS Para 4.10

3.6. DoD 8570.01-M – Information Assurance (IA) Workforce Improvement Program PWS Para 4.10

3.7. AR25-1 – Army Knowledge Management and Information Technology PWS Para 4.10

3.8. AR25-2 – Information Assurance PWS Para 4.10

4. Performance Requirements

The Contractor shall provide sustainment for the Army MWN, AVNS, and E-911 solution defined as, US Army Alert!, Alertus, Motorola AMCOM, Airbus Vesta 4, and Caliber Public Safety MicroAutomation and in the Fielded System List (FSL) (Applicable Document 3.2). US Army Alert! is the Army’s enterprise MWN tool requiring sustainment. The MWN locations on the FSL are the major Installations and Organizations currently using the system. The list of MWN locations/organizations in the FSL is subject to change, and not limited to Army organizations. MWN sustainment, specifically, does not require travel to the locations on the FSL.

4.1. At the conclusion of the task, the Contractor shall provide a System Test Plan (CDRL B001) for implementation following E-911 repairs and/or upgrades. The System Test Plan will also include test plans for AVNS and MWN. The plan must include system test descriptions, responsibilities, procedures, results templates, and non-conformance report templates. The format of the System Test Plan must be approved by the Government.

4.1.1. The Contractor shall make arrangements to perform diagnostics from remote locations to speed the response, prevent travel, or otherwise proves to be time and cost effective to do so. Remote connections are subject to Information Assurance (IA) Certification & Accreditation (C&A) requirements as described in the approved system Risk Management Framework (RMF) accreditation packages.

4.2. The Contractor shall document the Emergency Management Sustainment System Architecture (CDRL A001) in accordance with the DoDAF 2.02 (Applicable Document 3.3) (or latest approved version) standard. The document shall include all applicable variations of MWN, AVNS, and E-911 All Viewpoint (AV), Capability Viewpoint (CV), Data and Information Viewpoint (DI), Operational Viewpoint (OV), Project Viewpoint (PV), Services Viewpoint (SvcV), Standard Viewpoint (StdV), and Systems Viewpoint (SV). The format of the System Architecture must be approved by the Government. The Contractor shall manage the repeatable Systems Engineering (SE) process in support of engineering, design, and sustainment activities. The Contractor shall lead the overall system requirements decomposition, allocation, and traceability, shall document and manage the lifecycle processes, and shall maintain the SE artifacts and tools for both systems requirements and system architecture.

4.2.1. The Contractor shall maintain one (1) copy of each version of the FSL software applications in a Software Library Repository (CDRL A002) as backup in the same media as provided by the software vendor. Access to the repository will be made available to CCDC - ARMAMENTS CENTER supporting TACOM. Upon request of the Government, the Contractor shall provide any software, software source code, Glue Code, and any other software programming documentation or software developed by the Contractor in support of the above efforts. The contents of the Software Library Repository must be approved by the Government. At the conclusion of Contract, the Software Library Repository shall be provided to CCDC - ARMAMENTS CENTER supporting TACOM.

4.2.2. The Contractor shall maintain all current MWN, AVNS, and E-911 configurations that are currently fielded. Any changes shall be documented in a change report detailing the time, reason, and nature of the change.

4.3. The Contractor shall deliver a quarterly Contractor Roster (CDRL B002 - Tailored) to CCDC - ARMAMENTS CENTER supporting TACOM. In addition to the critical personnel, the report must identify all personnel directly supporting the TACOM contract. Those personnel requiring administrator access to the MWN hosting environment, and their progress in completing account requirements, shall be noted on the Roster. At a minimum, the report must identify the employee’s normal office location, phone number, e-mail address, security level, and functional area within the program. The format of the Contractor Roster must be approved by the Government.

4.4. The Contractor shall provide CCDC - ARMAMENTS CENTER supporting TACOM with an Integrated Master Schedule (IMS) (CDRL B003) that includes all on-going approved activities. The IMS shall be specific to sustainment efforts. The format of the IMS must be approved by the Government.

4.5. The Contractor, in collaboration with CCDC - ARMAMENTS CENTER supporting TACOM, shall conduct a biweekly Status Tracker telecon meeting for the duration of the task. The date and time of the meeting will be jointly decided by CCDC - ARMAMENTS CENTER supporting TACOM and Contractor.

4.6. The Contractor shall document the Configuration Management Plan (CMP) (CDRL B004). The format of the CMP must be approved by the Government. The Contractor shall follow, maintain, and update the Configuration Management (CM) capability necessary to support CCDC - ARMAMENTS CENTER supporting TACOM. The CM plan must contain plans and procedures for configuration management to identify, control, and define the status of the technical performance specifications of MWN, AVNS, and E-911 products and associated components. This includes maintaining CM plans, documenting physical characteristics of the hardware, versions of software, updating plans and procedures for record management. The Contractor shall document equipment repairs and manage Installation specific design configurations including Engineering drawing revisions and replacement MWN, AVNS, and E-911 Bill of Materials. The Contractor shall create an authoritative data source for MWN, AVNS, and E-911, as well as equipment warranty numbers and codes. The Contractor shall provide this information in a web based Configuration Management System (CMS) that will function as the authoritative data source for the items listed above. The Contractor shall provide to the Government twenty four/seven (24/7) web based access to this information within the CMS. The Contractor shall ensure that this information is integrated into or accessible through the Help Desk functionality

4.7. The Contractor shall deliver a single monthly MWN, AVNS, and E-911 Sustainment Technical Report (STR) (CDRL A003) covering each sustained installation. The format of the Sustainment Technical Report must be approved by the Government. The STR shall include the following:

4.7.1. Trend analysis which includes repair and replacement parts or equipment usage. The analysis information shall be based on historical data.

4.7.2. Data and analysis of that data to reveal support, material, training, or operator deficiencies that contribute to reduced operational availability (A0).

4.7.3. Deviations from the systems’ required functionality as per the DRD.

4.7.4. Equipment failures to include identifying warranty and non-warranty failures

4.7.5. Recommended changes to servicing procedures or intervals (Historical information)

4.7.6. Recommended cost savings (Historical information)

4.7.7. Time to repair and time to resolve expired or damaged equipment

4.8. The Contractor’s program management effort shall provide CCDC - ARMAMENTS CENTER supporting TACOM with a Monthly Cost, Schedule, and Performance Report (CDRL B005) for MWN, AVNS, and E-911 sustainment. The report shall include Contractor and Government owned risk, particularly Risk Identification (ID), category, probability, consequence, owner, impact, urgency, risk mitigation plan of action, and projected time for reducing the risk that will allow the Contractor to perform the non-risk loaded best case schedule. This report must be dynamic as report requirements will change depending on cost, schedule, and performance concerns of CCDC - ARMAMENTS CENTER supporting TACOM. Each Contractor functional area shall provide input to the report. The format of the Cost, Schedule, and Performance Report must be approved by the Government.

4.9. Contractor shall provide Supply Chain Management System (SCMS) for tracking of replacement parts as well as repair and calibration or re-imaging of sustained EM systems as defined by the FSL. The Contractor shall maintain the SCMS ensuring timely and efficient supply of all replacement/repair equipment/materials for sustainment efforts. Materiel management functions include all labor and material that are required to procure approved equipment. The Stock Status Report (CDRL B006), shall include characteristic data, as well as status of COTS and Government Off The Shelf (GOTS) equipment. Status of replacement/repair equipment shall include Nomenclature, Part Number, National Stock Number, item cost, unit of issue, document number, expected delivery date, total of units ordered, receipt date at Contractor facility, quantity on hand, warranty information, estimated lead time and amplifying remarks. The format of the Stock Status Report must be approved by the Government. All material procured by the Contractor must have U.S. Government Contracting Officer approved pricing prior to procurement.

4.10. The Contractor shall provide system-level support in accordance with provisions of DoD Instruction 8500.01 (Applicable Document 3.4), Cybersecurity, 14 March, 2014 and DoD Instruction 8510.01, “Risk Management Framework (RMF) for DoD Information Technology (IT)” (Applicable Document 3.5), 12 March 2014, DoD 8570.01-M “Information Assurance Workforce Improvement Program” (Applicable Document 3.6), AR25-1 “Army Knowledge Management and Information Technology” (Applicable Document 3.7), and AR25-2 “Information Assurance” (Applicable Document 3.8). The Contractor shall perform Information Assurance (IA) and Cybersecurity activities in accordance with Federal Information Security Management Act of 2002, 44 U.S.C. § 3541. This adherence to Federal Information Security Management Act (FISMA) and DoD issuances includes all information systems operated on the behalf of CCDC - ARMAMENTS CENTER supporting TACOM that receives, processes, stores, displays, communicates, or transmits DoD information regardless of classification or sensitivity.

4.10.1. There will be two (2) IT systems which will require IA support in accordance with this PWS.

4.10.2. The Contractor shall plan, initiate, and perform RMF activities to minimize impacts on fielded systems, work with CCDC - ARMAMENTS CENTER supporting TACOM and its stakeholders to secure and maintain certification & accreditation (C&A) at the Army level for all supported AVNS and E-911 systems. The Contractor shall perform analysis of the IT systems and confirm the accreditation boundaries and inherited DoD IA controls. The Contractor shall validate the IA posture of each sustainable system by performing certification, testing and evaluation (CT&E) of sustained systems.

4.10.3. The Contractor shall ensure all vendors maintain documents and credentials necessary to participate in the accreditation efforts (i.e. Common Access (CAC) card) and fully comply with all military requirements.

4.10.4. The Contractor shall review existing AVNS and E-911 RMF Packages; analyze DoD IA Scorecard, C&A status, and identified vulnerabilities. The Contractor shall work with CCDC - ARMAMENTS CENTER supporting TACOM to resolve identified vulnerabilities and provide mitigation strategies in the form of a Plan of Action and Milestones (POA&M) for outstanding issues. Upon accreditations renewals, The Contractor shall assist CCDC - ARMAMENTS CENTER supporting TACOM with reviewing and updating all necessary RMF documents.

4.10.5. Once the accreditation is granted by the Authorization Official (AO), the Contractor shall maintain the sustainable systems Authorization to Operate (ATO), for the specified period of performance and to perform annual certification and FISMA reviews. Additionally, the Contractor shall support CCDC - ARMAMENTS CENTER supporting TACOM in attainment and maintenance of Service level certifications and accreditations.

4.10.6. The Contractor shall upload all Information Assurance documentation and deliverables to Enterprise Mission Assurance Support Service (eMASS) and other tracking databases.

4.10.7. The Contractor shall update and execute processes to identify, verify, and distribute the AVNS and E-911 system Information Assurance Vulnerability Management (IAVM) in accordance with Defense Information Security Agency (DISA) and DISA policies. The Contractor shall support CCDC - ARMAMENTS CENTER supporting TACOM in identifying reaccreditation requirements, confidentiality, integrity, and availability levels, DoD IA controls, to include inherited IA controls as relevant requirements affecting the security posture of fielded systems change and evolve. The accreditation letters shall be delivered to CCDC - ARMAMENTS CENTER supporting TACOM upon request.

4.10.7.1. The Contractor shall, through the IAVM and configuration management processes, develop, document and execute a process to apply security patches to software/operating systems for sustainable systems as applicable.

4.10.7.2. The Contractor shall conduct monthly Information Assurance Vulnerability Assessment (IAVA) Compliance scans for AVNS and E-911 systems utilizing approved DoD and Army scanning tools. The Contractor shall provide the results to the CCDC - ARMAMENTS CENTER supporting TACOM at their request

4.10.7.3. The Contractor shall utilize the latest Assured Compliance Assessment Solution (ACAS) and the latest plugins prior to each scan conducted. Raw Scan Results shall be provided to CCDC - ARMAMENTS CENTER supporting TACOM upon request. The Contractor shall always use the latest scanning tools required by the accrediting authorities. The Contractor shall utilize and fill out the DISA created instructions for successfully running ACAS prior to each scan conducted.

4.10.7.4. The Contractor shall update the Plan of Action and Milestones (POA&M) with the scan results in accordance with the latest guidance per the accrediting authority.

4.10.7.5. The Contractor shall create and maintain an Army accreditation checklist.

4.10.7.6. The Contractor shall obtain all latest versions of templates/forms relevant to the Army accreditation process.

4.10.8. The Contractor shall perform Life Cycle implementation of IAVA Compliance Requirements for sustained AVNS and E-911 systems.

4.11. The Contractor shall follow the existing formal Configuration Control Board (CCB) process, as found in the CMP, to control the technical baseline for the sustained systems as defined in the FSL. The Contractor shall contribute and participate in an IA Working Group (IAWG) meeting consisting of (but not limited to) CCDC - ARMAMENTS CENTER supporting TACOM and Contractor team members. The Contractor and CCDC - ARMAMENTS CENTER supporting TACOM shall agree on the frequency and dates of these meetings. The Contractor shall propose recommended improvements to the existing CCB process. The purpose of this meeting shall be to discuss specific installation service requests, IAVAs, Operating System (OS) patches, software patches, vendor updates, and other hardware/software implications, of the changing baseline of fielded MWN, AVNS, and E-911 configurations. AVNS and MWN IA issues will also be covered during this meeting. The Contractor shall assemble the weekly IAWG meeting. The Government and the Contractor shall determine agendas, and regularly scheduled meeting times and location as is deemed sufficient to address the IA requirements. Included in the meeting will be an overview of the open Help Desk tickets.

4.12. The Contractor shall provide multi-tiered MWN, AVNS, and E-911 Help Desk support which will include twenty four/seven (24/7) operations for troubleshooting.

4.12.1. The Contractor shall implement and use an incident ticket system to be approved and accessible to CCDC - ARMAMENTS CENTER supporting TACOM staff. The incident ticket system shall be capable of providing automated metrics, be able to assign product numbers to line items on the sustainable systems, be capable of doing queue management, be able to track status changes of tickets with date/time/and name stamps, and be capable of being configurable to CCDC - ARMAMENTS CENTER supporting TACOM requirements. The incident ticket system shall maintain a log of CI and updates, customer interaction, metrics data, work flow management, and installation mission capable readiness.

4.12.2. The Contractor shall manage a Help Desk on behalf of CCDC - ARMAMENTS CENTER supporting TACOM. The Help Desk shall provide a Help Desk Metrics Report (CDRL B007). The report must include Case IDs (CI), System, Installation, Date Opened, Initial Response Time, Tier, Status, Priority, Assignee, Issue, and Comments. A visual chart of ticket types by installation must also be included. The format of the Help Desk Metrics Report must be approved by the Government. The function of the Help Desk is to provide tiered support for all MWN, AVNS, and E-911 equipment to include software. The Help Desk first tier shall be manned and operational 24/7 to support all installations with MWN, AVNS, and/or E-911 systems CONUS and OCONUS. The Contractor shall not deny any request for assistance from the customer.

4.12.3. The Help Desk phone number shall be the same for MWN, AVNS, and E-911 system support. That phone number shall be toll-free for all customers at Installations with sustained systems.

4.12.4. The Contractor shall implement a database of Configuration Management (CM) data of each installation with sustainable systems. This data will be used to determine operational status of the provided MWN, AVNS, and E-911 capability for the installation that is calling into the Help Desk. This shall be performed by assessing the operational capability (event or emergency, down, degraded, no impact etc.) of the equipment the installation is calling in reference to. The Contractor shall have the capability to provide all CM data in Microsoft Excel format to CCDC - ARMAMENTS CENTER supporting TACOM upon request.

4.12.5. The Help Desk shall create and maintain a Help Desk Frequently Asked Questions (FAQ) Log (CDRL A004) of all known issues regarding MWN, AVNS, and E-911 equipment. The FAQ’s shall be compiled by collecting lessons learned data from each of the closed CIs, SME lead inputs, and other sources (i.e. service requests, surveys, etc.) . The Contractor shall analyze closed CIs for development of lessons learned and equipment trends analysis. The lessons learned shall then be recorded in the FAQ log for review, analysis, and incorporation into the technology insertion process. The format of the FAQ Log must be approved by the Government.

4.12.6. Reports and survey results shall be available to CCDC - ARMAMENTS CENTER supporting TACOM within twenty four (24) hours of being requested. A review of open Help Desk tickets will be conducted during the weekly IA Working Group (IAWG) meeting. All helpdesk tickets will have follow-up for closure on all tickets. Any tickets open for thirty (30) days or more, the Contractor shall contact CCDC - ARMAMENTS CENTER supporting TACOM to determine a remediation plan

4.12.7. The Contractor shall notify CCDC - ARMAMENTS CENTER supporting TACOM, and provide an immediate Status Report in the event of irregular or high number of Help Desk tickets opened in one day.

4.13. The contractor shall provide a MWN, AVNS, and E-911 Help Desk capability following a tiered approach. The tiers are defined as:

4.13.1. Twenty Four/Seven (24/7) Support

4.13.1.1. The first tier twenty four/seven (24/7) Help Desk shall be operated by dedicated Systems Engineering Help Desk Analysts (HDA) with strong technical sets of skills to analyze, troubleshoot, and conduct customer relationship management (CRM). The HDA shall be responsible for opening CIs and logging them into the incident ticket system, qualify support calls based on the Installation’s capability of being able to perform their mission, and on the operational readiness of the equipment, collect customer data. The HDA shall ensure highly detailed updates (detailed information of all communications with customers, in depth descriptions of work done since last update, decisions made regarding the CI, and in depth descriptions of any and all activities associated with the CI) of all open CIs are inputted into the incident ticket system within their required time frame. The HDA shall ensure CIs are worked and resolved within their associated time-to-resolve metric, and provide twenty four/seven (24/7) support. The HDA shall inform CCDC - ARMAMENTS CENTER supporting TACOM of any and all CIs that will not meet the deadline in advance of not meeting its time to resolve metric.

4.13.1.2. The HDA shall utilize the FAQ Log to provide support and/or determine if the request is related to a known issue. The Analysts shall elevate any CI that no knowledge entry or resolution can be immediately found to a higher tiered support Subject Matter Expert (SME). The Analysts shall connect the customer with an available SME for immediate support. The Analysts shall be responsible for obtaining updates for all open CIs assigned to Level-2 SMEs within a required timeframe. For e-mail and voicemail requests, the Analysts shall provide an immediate call back, upon receipt, to address the customer’s concerns.

4.13.1.3. The Analysts shall conduct site status end-user surveys for all closed CIs each week. The questions shall be reviewed by CCDC - ARMAMENTS CENTER supporting TACOM via an CCDC - ARMAMENTS CENTER supporting TACOM approved method.

4.13.1.4. On a quarterly basis, the Analysts shall conduct an audit of all CIs opened in the previous three (3) months. The audit will be used to develop lessons learned for the FAQ, process improvement, and vendor performance via an CCDC - ARMAMENTS CENTER supporting TACOM approved web enabled metrics portal.

4.13.2. Normal Business Hours Support (7am-9pm EST. and available on-call outside of normal business hours to address critical items)

4.13.2.1. When CIs are elevated to a higher tiered Subject Matter Expert (SME), the SME shall respond back to the customer within twenty four (24) hours, during normal business hours, of the CI being assigned. SMEs shall input highly detailed updates (detailed information of all communications with customers, in depth descriptions of work done since last update, decisions made regarding the CI, and in depth descriptions of any and all activities associated with the CI) of all open CIs that are assigned to them into the incident ticket system within the required time line stated above. The SME shall provide resolution within the CIs time to resolve metric, time frames to be established and documented by the Government. SMEs shall be available to support and answer questions from the Level-1 Analysts.

4.13.3. Vendor Support

4.13.3.1. When CIs are not able to be resolved by a higher tier SME, the SME shall escalate the CI to the Vendor Support within twenty four (24) hours, during normal business hours. The higher tier SME shall be responsible for obtaining updates from the Vendor and inputting them into the incident ticket system within the required update time frame outlined above. The higher tier SME shall be responsible for managing the Vendor in getting CIs escalated to the Vendor resolved in the proper time-to-resolve metric.

4.14. The Contractor shall update all fielded MWN, AVNS, and E-911 hardware and software components with the necessary spins, patches, and IAVMs. All software must be maintained to comply with all Army IA policies.

4.14.1. The Contractor shall create a monthly Information Assurance Patch Installation Notice (SPIN) (CDRL A005). The document must include vendor security patch ID, IAVM information, and applicable system(s). The format of the Information Assurance SPIN Report must be approved by the Government.

4.15. The Contractor shall repair/replace all critical MWN, AVNS, and E-911 system/component failures within 48 hours of Help Desk incident reporting. A critical component is defined as a component that stops the entire MWN, AVNS, or E-911 system from functioning as defined in the Directed Requirements for Emergency Management Modernization Program (DRD) and this PWS.

4.16. Whenever it is learned that the MWN, AVNS, or E-911 systems suffers from a deficiency that degrades its intended functionality, the Contractor shall perform diagnostics and repair services to restore system operation to its full capability as per its original performance specifications, the DRD, and this PWS. This includes working with the appropriate local installation organizations to provide restoration and repair services to systems impacted by environmental conditions such as regional weather conditions and/or seasonal conditions to include, but not limited to, snow, wind, lightning strikes and sand storms.

4.16.1. The Contractor shall be responsible for the repair or replacement of all sustained systems identified in the FSL, including any subcomponents of those systems.

4.16.2. The Contractor shall repair and/or replace any malfunctioning sustained systems, including hardware as well as reprogramming, replacing, or updating associated firmware and software. If repair is not possible the systems shall be replaced by the Contractor.

4.16.3. When the same component (same asset tag or serial number) has a third service call following two previous repairs within a two (2) year period, the Contractor shall replace the component with new equipment. The Contractor can request a waiver to this requirement through CCDC - ARMAMENTS CENTER supporting TACOM

4.16.4. The Contractor shall provide all support equipment, tools, test equipment, and supplies to perform Corrective Maintenance of the sustained systems

4.16.5. The Contractor shall have the customer sign-off on each resolved Service Call, and provide the documentation to CCDC - ARMAMENTS CENTER supporting TACOM

4.17. The Contractor shall support remote online weekly Alert! User Training for Installation personnel, using Defense Information Systems Agency (DISA) Defense Collaboration Services (DCS). The training will consist of the necessary steps to manage Alert! Client personnel, initiate notifications and alerts, and overall Alert! System management. The contractor may use MIL-HDBK-29612-2A - Department of Defense Handbook, Instructional Systems Development/Systems Approach to Training and Education (Part 2 of 5 Parts), 31 August 2001 as guidance. All training materials will be provided to the Contractor by the Government. The schedule for online training will be determined by the Government. Personnel attendance for each training session shall be provided to the Government via e-mail no later than 24 hours following the session.

4.18. The Contractor shall sustain US Army Alert! software development support. This includes:

4.18.1. Provide technical engineering skills for all phases of the software development life-cycle including requirements and design analysis, software design, documentation, implementation and testing support of the US Army Alert! Program.

4.18.2. Identify, analyze, and correct all system bugs.

4.18.3. Develop a software development schedule outlining each software release and the features to be included in that release.

4.18.4. Support all Alert! technical refresh activities, as required, to include Site Verification Visits, deployment, and training.

4.18.5. Provide networking, hardware, software and internet support for all phases of the Alert! system development life-cycle including requirements and design analysis, software design, implementation and testing support for projects.

4.18.6. Provide software and systems support in analyzing, troubleshooting, testing and making recommendations related to systems environment.

4.18.7. Perform configuration, installation and other system administration functions as necessary.

4.18.8. Provide central authentication and authorization services for the Alert! application.

4.18.9. Troubleshoot, diagnose, and resolve outages and other problems with web servers, data processing servers, and database servers.

4.18.10. Determine the root cause of system problems resulting in operational performance degradation or system outages, and provide corrective actions and/or interim workarounds.

4.18.11. Implement and comply with:

4.18.11.1. Security Technical Implementation Guides (STIG's).

4.18.11.2. Security Requirements Guides (SRG's).

4.18.11.3. All system specific IA documentation.

4.18.12. Conduct Alert! system unit testing, integration testing, and Formal Qualification Testing (FQT), verifying the application software functionality against the system requirements. The personnel will participate in the Data Review Board to resolve any outstanding defects with government software developers.

4.18.13. The personnel shall comply with all data interoperability standards (e.g. Common Altering Protocol (CAP) and Emergency Data Exchange Language (EDXL)).

4.18.14. Review, analyze, and update existing software code as well as develop new code to meet program requirements. All new code shall follow the project’s coding and documentation standards. Code shall be peer reviewed to detect errors prior to deployment. Code shall be stored in the governments’ configuration management repository and in accordance with the system’s documentation.

5. Options

5.1. Complete E911 System Replacement (May be exercised more than once for various locations.)

5.1.1. When the determination has been made that a location’s E911 System needs to be completely replaced during the duration of the contract, an option will be awarded and the Contractor shall perform a complete E911 system replacement at a specified DoD Installation. All costs involved in this requirement, to include labor, travel, and Other Direct Costs (ODC), will be combined into a single Contract Line Item Number (as a LOT). The E911 system chosen for replacement deployment must have an Authority to Operate (ATO) and be NG9-1-1 compliant equipment. The complete E911 package will consist of two (2) call-taker positions. The option must be completed within twelve (12) months of award of the option.

5.1.2. The Contractor shall provide an E911 Integrated Master Schedule (IMS) (CDRL B008) for approval no later than the fifth (5th) day of the month following option award. The IMS shall be updated monthly.

5.1.3. The Government will provide all necessary documentation, including existing 911/E911 drawings for the E911 system replacement at the designated Installation to the Contractor within thirty (30) calendar days of option award.

5.1.4. The Contractor shall participate in a Site Coordination Visit (SCV) at the designated Installation, within ninety (90) calendar days of option award.

5.1.5. The Contractor shall provide the appropriate staff to conduct the visit and gather additional data as necessary to complete the E911 Design & Deployment Plan (E911 DDP) (CDRL A006) at the designated Installation.

5.1.6. The Contractor shall coordinate with the appropriate Installation POCs, and conduct data gathering activities for:

5.1.6.1. Verification of network, telephony, space, power, infrastructure and connectivity information

5.1.6.2. Verification of Installation telephone subscriber data

5.1.6.3. Verification of call centers, PSAP, and dispatch capabilities

5.1.7. The Contractor’s E911 DDP will consist of, at a minimum, an executive summary, site description, E911 system description, implementation methodology, deployment schedule, system schematics, construction specifications, testing plan, and as-required engineering drawings that would include schematics, block diagrams, bills of materials, and assembly drawings. The E911 DDP shall also include a listing of required agreements, permits, and associated POCs on the Installation for performance of work, access, and coordination of schedules. The list of POCs shall include organizations responsible for initiation, processing, and approvals.

5.1.8. The E911 DDP shall include:

5.1.8.1. Transition plan avoiding gap in 911 service.

5.1.8.2. Where possible investigate the potential integration of existing capabilities to include Computer-aided Dispatch (CAD) and Land Mobile Radio (LMR).

5.1.9. The Contractor shall submit the E911 DDP within twenty (20) calendar days of SCV completion.

5.1.10. The Contractor shall not begin deployment activities until the final E911 DDP is approved by the Government.

5.1.11. Within ninety (90) calendar days of approval of the E911 DDP, the Contractor shall provide complete, fully configured & functioning E911 systems at the designated Installation. The Contractor shall be responsible for all aspects of deployment, site preparation, configuration, integration, transition, and interfacing with existing systems. The Contractor shall also obtain and oversee construction subcontractors, coordinate with the Installation POC’s Engineering and Facilities Maintenance offices. The Contractor is responsible for acquiring all permits, to include environmental, required for the light construction and install of the E911 system. Any building modifications, flooring, heat dissipation, grounding, lighting, etc… changes that are required for implementation will be coordinated by the Contractor and executed by the Installation.

5.1.12. The Contractor shall provide the services to deploy the approved package with minimal impact on the day-to-day operations of the Installation.

5.1.13. The Contractor, with CCDC - ARMAMENTS CENTER support, shall provide necessary process for ownership transfer of equipment to the designated Installation.

5.1.14. The Contractor shall adhere to all applicable safety and security precautions during the site preparation and deployment phases of the project. The Contractor, with CCDC - ARMAMENTS CENTER and the designated Installation POC will coordinate equipment receipt and temporary storage location on the Installation prior to system installation. The Contractor shall prepare site maps and asbuilt drawings as part of an E911 As-Built Package (ABP) (CDRL A007) for the designated Installation upon completion of the system implementation. A list of hardware (make, model, and serial #) delivered to the designated Installation will also be included in the ABP.

5.1.15. As required by the E911 DDP, the Contractor shall conduct a full system test and validation of the final equipment configuration under CCDC - ARMAMENTS CENTER oversight to ensure proper integration of components and functionality of the installed system. The specific acceptance test procedures and full system validation shall be Installation-specific and in accordance with the Contractor’s E911 DDP. Upon successful test and validation an E911 Delivery Acceptance Memo (CDRL B009) for the designated Installation, stating positive system delivery, testing, and acceptance will be signed by the Contractor, CCDC - ARMAMENTS CENTER, and Installation-designated POC. The Delivery Acceptance Memo will include information as to whether each system test, as defined in the E911 DDP, passed or failed.

5.1.16. Immediately following successful system test and validation, the Contractor shall conduct E911 New Equipment Training (NET) at the designated Installation. DoD personnel attendance will be taken at the designated Installation, and provided to CCDC - ARMAMENTS CENTER via e-mail. The NET must provide 911 operators/dispatchers with the required knowledge to complete their day-to-day 911 tasks. Standard E911 vendor training is applicable for NET.

5.1.17. The Contractor shall develop an E911 Training Materials Package (TMP) (CDRL B010) to be used for the designated Installation. The TMP must provide information, guides, workflows, diagrams, and other data supplementary to the NET. Any slides presented during the NET shall be included in the TMP. The TMP shall also include any pertinent COTS vendor manuals. The contractor shall employ training instruction (e.g., manuals), training criteria (e.g., desired learning outcomes and performance goals), and evaluation methods and metrics to verify training effectiveness in accordance with criteria (e.g., performance measurements such as number of tasks correctly completed within a prescribed time). The contractor may use MIL-HDBK-29612-2A - Department of Defense Handbook, Instructional Systems Development/Systems Approach to Training and Education (Part 2 of 5 Parts), 31 August 2001 as guidance. The Training Materials will be provided to the 911 operators/dispatchers during the NET, in addition to CCDC - ARMAMENTS CENTER. At the conclusion of the NET, an attendance roster will be provided to CCDC - ARMAMENTS CENTER via e-mail.

5.1.18. The Contractor shall provide a E911 drill at the designated Installation, following the NET and E911 system cutover, and will provide an E911 Drill Materials Package (DMP) (CDRL B011) at the designated Installation, utilizing an exercise scenario. The DMP shall include the plan for conducting the drill at the designated Installation and the Master Scenario Events List (MSEL). The E911 Drill shall be employed to test the capability of E911 system operators to respond to a simulated All-Hazards incident utilizing their E911 system. The E911 Drill shall ensure operators’ knowledge of system functionality for production operations. At the conclusion of the drill, an attendance roster will be provided to CCDC - ARMAMENTS CENTER via e-mail.

5.2. E911 Call-Taker Position Deployment (May be exercised more than once for various locations)

5.2.1. When the determination has been made that a location’s E911 System needs an additional call-taker position, an option will be awarded and the Contractor shall perform a call-taker position configuration and deployment at a specified DoD Installation. All costs involved in this requirement, to include labor, travel, and Other Direct Costs (ODC), will be combined into a single Contract Line Item Number (as a LOT). The call-taker position must be compatible with the Installation’s E911 system. The option must be completed within six (6) months of award of the option.

5.2.2. The Contractor shall conduct a full system test and validation of the final equipment configuration under CCDC - ARMAMENTS CENTER oversight to ensure proper integration of components and functionality of the installed system. Upon successful test and validation an E911 Delivery Acceptance Memo (CDRL B009) for the designated Installation, stating positive system delivery, testing, and acceptance will be signed by the Contractor, CCDC - ARMAMENTS CENTER, and Installation-designated POC. The Delivery Acceptance Memo will include information as to whether each system test, passed or failed.

5.3. Additional E911 Call-Taker Position Add-On (May be exercised more than once for various locations; must be exercised in conjunction with Option 5.1 or 5.2)

5.3.1. When the determination has been made that a location’s E911 System needs an additional call-taker position, an option will be awarded and the Contractor shall perform a call-taker position configuration and deployment at a specified DoD Installation. This option does not include travel, as travel is included in Options 5.1 and 5.2. All costs involved in this requirement, to include labor and Other Direct Costs (ODC), will be combined into a single Contract Line Item Number (as a LOT). The call-taker position must be compatible with the Installation’s E911 system. The option must be completed within six (6) months of award of the option.

5.3.2. The Contractor shall conduct a full system test and validation of the final equipment configuration under CCDC - ARMAMENTS CENTER oversight to ensure proper integration of components and functionality of the installed system. Upon successful test and validation an E911 Delivery Acceptance Memo (CDRL B009) for the designated Installation, stating positive system delivery, testing, and acceptance will be signed by the Contractor, CCDC - ARMAMENTS CENTER, and Installation-designated POC. The Delivery Acceptance Memo will include information as to whether each system test, passed or failed.

6. Deliverables

6.1. CDRL B001, System Test Plan PWS Para 4.1

6.2. CDRL A001, System Architecture PWS Para 4.2

6.3. CDRL A002, Software Library Repository PWS Para 4.2.1

6.4. CDRL B002 - Tailored, Contractor Roster PWS Para 4.3

6.5. CDRL B003, Integrated Master Schedule PWS Para 4.4

6.6. CDRL B004, Configuration Management Plan PWS Para 4.6

6.7. CDRL A003, Sustainment Technical Report PWS Para 4.7

6.8. CDRL B005, Cost, Schedule, and Performance Report PWS Para 4.8

6.9. CDRL B006, Stock Status Report PWS Para 4.9

6.10. CDRL B007, Help Desk Metrics Report PWS Para 4.12.2

6.11. CDRL A004, Help Desk Frequently Asked Questions Log PWS Para 4.12.5

6.12. CDRL A005 Information Assurance Patch Installation Notice (SPIN) PWS Para 4.14.1

6.13. CDRL B008, E911 Integrated Master Schedule, PWS Para 5.1.2

6.14. CDRL A006, E911 Design & Deployment Plan (E911 DDP), PWS Para 5.1.5

6.15. CDRL A007, E911 As-Built Package (ABP), PWS Para 5.1.14

6.16. CDRL B009, E911 Delivery Acceptance Memo, PWS Para 5.1.15

6.17. CDRL B010, E911 Training Materials Package (TMP), PWS Para 5.1.17

6.18. CDRL B011, E911 Drill Materials Package (DMP), PWS Para 5.1.18

6.19. CDRL B012, Operations Security (OPSEC) Plan PWS Para 9.24

6.20. CDRL B013, Certification Data Report/ Mandatory Training Certification PWS Paras 9.7, 9.10, 9.14, 9.15, 9.16, 9.17, 9.25

7. QASP: Incorporated by reference in Section J

8. General Requirements and Information

8.1. Period of Performance

8.1.1. The period of performance for this effort is 12 months with an option to extend services in accordance with FAR 52.217-8 for up to 6 months.

8.2. Place of Performane

8.2.1. The place of performance will primarily be Contractor facilities. Other places of performance include, but are not limited to, locations in the FSL. Access to these facilities may require a secret clearance.

8.3. Data and Equipment Rights

8.3.1. All reference material, documents, training support material, and other information obtained, produced, or developed by the contractor in support of this effort shall become the property of the Government, and shall be delivered to the Technical Point of Contact (TPOC). The Government shall have the unrestricted rights to use, modify, reproduce, release, perform, display, or disclose technical data, software, and products for all work products developed and modified under this Task Order.

8.4. Travel

8.4.1. The Contractor shall anticipate travel to DoD facilities indicated but not limited to the FSL.

8.4.2. Travel shall be in accordance with the Joint Travel Regulation (JTR).

8.5. Incidental Government Furnished Items (GFI).

8.5.1. GFI will be provided in the form of CAC cards. Government Furnished Property (GFP) will be provided to Contractor in the form of lab equipment and computers.

8.5.2. GFP from contract W15QKN-19-C-0045 is being transferred to this contract. The GFP listing is attached.

8.6. Information Disclosure

8.6.1. A Certificate of Non-Disclosure shall be signed by all contractor employees working under this effort and returned to the COR prior to award. The Contractor shall not release any information or data without the approval of the Government.

8.7. Invoices

8.7.1. Any invoice for material must be approved by the Government prior to purchasing.

9. Security

9.1. The highest security classification level for this effort is SECRET.

9.2. DFARS Clause 252.225-7043 applies to this contract.

9.3. The contractor will be required to obtain and maintain a Facility Clearance with safeguarding from the Defense Counterintelligence and Security Agency for the life of the contract. The contractor will only receive classified material at the actual performance location(s) as identified in block 8a of the DD254.

9.4. The Contractor shall not perform on CLASSIFIED requirements without an authorized DD254 provided by the US Army CCDC-AC Intelligence and Technology Protection Office (I&TPO). The prime contractor's Facility Security Officer (FSO) shall provide a signed copy of all subcontract DD254s issued under this agreement to the officials listed in blocks 16d and 17a below.

9.5. Information Disclosure:

9.5.1. A Classified Information Nondisclosure Agreement Standard Form (SF 312) shall be signed by all contractor employees working under this effort and returned to the COR prior to their being granted access to classified information. The contractor employees will also have to sign a non-disclosure agreement provided by the requiring activity for the protection of unclassified, sensitive and/or proprietary information.

9.6. Personnel:

9.6.1. Contractor personnel shall have the appropriate level of investigation and/or security clearance for each site of performance of work. The Contractor shall observe and comply with all security provisions in effect at each selected site. Only U.S. Citizens are authorized to work on this contract. All contractor personnel that require access to classified information and/or material will be required to have a Secret clearance under this contract and must maintain the level of security clearance for the life of this CONTRACT. The contractor will notify the AOR the same day as an employee receives notice that they will be released, have been fired, or have had their security clearance revoked or suspended.

9.7. AT Level I Training: All contractor employees, including subcontractor employees, requiring access to Department of Defense installations, facilities, or controlled access areas shall complete AT Level I awareness training within 45 calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever applies and within 12 months prior to travel outside of the US, then annually thereafter. The contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee to the COR (or to the contracting officer, if a COR is not assigned) within 14 calendar days after completion of training by all employees and subcontractor personnel. AT Level I awareness training is available at http://jkodirect.jten.mil/ .

9.8. AT Awareness Training for Contractor Personnel Traveling Overseas: This standard language requires U.S.-based contractor employees and associated subcontractor employees to make available and to receive Government-provided area of responsibility (AOR)–specific AT awareness training within 3 months prior to OCONUS travel as directed by AR 525-13. Government provided awareness training specific to an AOR traveled is provided to contract personnel upon request by contacting the CCDC Armaments Center AT Officer at usarmy.pica.rdecom-ardec.mbx.pica-ardec-at-training@mail.mil or 973-724-3005.

9.9. Access and General Protection/Security Policy and Procedures: All contractor employees, including subcontractor employees, shall comply with all installation and facility access and local security policies and procedures (provided by the Government representative), and security/emergency management exercises.