IA02_MFLEETS_PWS_09-16-19.docx

PERFORMANCE WORK STATEMENT (PWS)

Mobile Computing and Mobile Law Enforcement Video Services with Hardware Under the Program Name Mobile Federal Law Enforcement Enterprise Technical Service (MFLEETS)

PART 1

GENERAL INFORMATION

1. General: This is a non-personal services contract to provide a mobile first responder technical solution supported by a data center, which is commonly referred to by the program name, “Mobile Federal Law Enforcement Enterprise Technical Service (MFLEETS)”. This is only a program naming convention that describes a technical compilation of commercial off the shelf capabilities assembled into one program to support first responder vehicles. This is not a trademark name. The government shall not exercise any supervision or control over the contract service providers performing the services herein. Such contract service providers shall be accountable solely to the contractor who, in turn, is responsible to the government.

1.1 Description of Services/Introduction: The contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and non-personal services necessary to perform all of the following capabilities using available COTS products in one streamline service program: Mobile Computing, In-car video, vehicle hardware install, data storage, and data archive in a FEDRAMP accredited data center that also provides real time viewing of in-car cameras during critical incidents as defined in this performance work statement. The consolidated fusion of these commercial off-the-shelf (COTS) capabilities provided as a single service will be known throughout the remainder of this document and within the Army as the MFLEETS program. The contractor shall perform to all the standards within this contract.

1.2 Background: MFLEETS will implement a Federal Risk and Authorization Management Program (FEDRAMP) accredited cloud service IAW DFARS 239.7602 at the level 5 accridation standards.

Definitions.

for the secure collection, review, archival, and distribution of video evidence collected by mobile users at military installations. MFLEETS will provide capability to allow remote monitoring, viewing, and operation of devices mounted in patrol vehicles anywhere and anytime while within network connectivity. MFLEETS will provide a common accredited computing platform for integration and interoperability of law enforcement applications and mobile video devices.

MFLEETS will deploy mobile communications services for the secure transfer of data and controls between patrol vehicles, operations centers, and the MFLEETS services infrastructure. MFLEETS will provide tools and services to facilitate the collection, consolidation, organization, review, retrieval, search, and distribution of video and audio data using mobile networking and cloud computing technologies. MFLEETS will provide cost effective mechanisms for storing, managing, and retrieving large volumes of digital evidence data. MFLEETS will provide immutable storage solution able to protect digital evidentiary data from any alteration. MFLEETS will provide a storage solution able to preserve the quality and integrity of archived evidentiary data.

1.3 Objectives: Provide Contractor support services for United States Army, Headquarters, Installation Management Command (HQ IMCOM), Provost Marshal/ Protection Directorate, Mobile Federal Law Enforcement Enterprise Technical Service (MFLEETS) at IMCOM installations.

1.3.1. Implementation. The contractor shall provide an MFLEETS service that consists of installation of mobile equipment in addition to data center hosting with hardware and software as an accredited service. The contractor shall provide a full service solution that provides mobile computers, connectivity, in car video hardware and capabilities while also providing a turn-key data center that allows for the routine download of video data with real time viewing, and “optical drive” evidentiary archiving of all law enforcement video as required by Department of Justice standards. The contractor shall configure and accredit, the full system while also providing data hosting, system connectivity and monitoring for problem resolution on servers and mobile workstations, and verify peripheral equipment is interacting as required. This is a total solution provided by one contractor. The Contractor shall perform in accordance with (IAW) the terms and conditions of the contract, and in accordance with the established standards in this PWS and contract.

1.4 Scope: The Contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items necessary to provide an integrated in-vehicle law enforcement video solution, archival, and content management service for US Army Law Enforcement organizations as described herein. The service will meet Department of Defense (DoD) cyber accredidation requirements, and must integrate with existing law enforcement vehicles acquired through the Joint Services Law Enforcement Vehicle Equipment Standards (JSLEVES) contract.

1.5 Period of Performance: To be consistent with three year cyber accreditation cycles, the period of performance for this contract shall be twelve (12) months from the date of award with two (2), twelve (12) month option renewal periods. The period of performance reads as follows:

Base Year Option Year I Option Year II

1.6 General Information

1.6.1 Quality Control: Quality control is the responsibility of the contractor. The contractor is responsible for the delivery of quality services/supplies to the government (see FAR 52.246-1, Contractor Inspection Requirements).

1.6.1.1. The contractor shall deploy, implement and maintain an effective quality control system that includes a written quality control plan (QCP). The QCP shall implement standardized procedure/methodology for monitoring and documenting contract performance to ensure all contract requirements are met. The contractors’ QCP must contain a systematic approach to monitor operations to ensure acceptable services/products are provided to the government. The QCP, as a minimum, shall address continuous process improvement; procedures for scheduling, conducting and documentation of inspection; discrepancy identification and correction; corrective action procedures to include procedures for addressing government discovered non-conformances; procedures for root cause analysis to identify the root cause and root cause corrective action to prevent re-occurrence of discrepancies; procedures for trend analysis; and procedures for collecting and addressing customer feedback/complaints. The contractor shall upon request provide to the government its quality control documentation. After acceptance of the quality control plan the contractor shall receive the contracting officer’s acceptance in writing of any proposed change to its QC system.

1.6.2 Quality Assurance: The government shall evaluate the contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan. This plan is a government only document primarily focused on what the government must do to assure that the contractor has performed in accordance with the requirements of the contract.

1.6.3 Federal Government Holidays:

1.6.4 Hours of Operation: The contractor is responsible for conducting business, between the hours of 7:30 A.M. to 4:30 P.M. Monday through Friday except federal holidays or when the government facility is closed due to local or national emergencies, administrative closings, or similar government directed facility closings. For other than firm fixed price contracts, the contractor will not be reimbursed when the government facility is closed for the above reasons. The contractor must at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS when the government facility is not closed for the above reasons. When hiring personnel, the contractor shall keep in mind that the stability and continuity of the workforce are essential.

1.6.5 Place of Performance: The work to be performed under this contract shall be accomplished at various IMCOM military installations located in the continental United States (CONUS), Hawaii and Alaska as required. The contractor shall provide the total video and mobile data solution to the ten following installations first, in this order of fielding: Bragg, Stewart, Hood, Benning, Gordon, Polk, Belvoir, Myer, Drum, and Jackson.

1.6.6 Type of Contract: The government will award a (Type of contract to be determined by the contracting office and resource adviser (RA)).

1.6.7 Post Award Conference/Required Progress Meetings: The contractor agrees to attend any post award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5, Post Award Orientation. The contracting officer, COR, and other government personnel, will meet with the contractor quartrerly as a minimum IAW AR 70-13 to review the contractor's performance. At these meetings the contracting officer will apprise the contractor of how the government views the contractor's performance and the contractor will apprise the government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the government.

1.6.8 Contracting Officer Representative (COR): The COR will be identified by separate letter. The COR monitors all technical aspects of the contract and assists in contract administration. The COR is authorized to perform the following functions: assure that the contractor performs the technical requirements of the contract; perform inspections necessary in connection with contract performance; maintain written and oral communications with the contractor concerning technical aspects of the contract; issue written interpretations of technical requirements, including government drawings and specifications; monitor contractor's performance and notify both the contracting officer and contractor of any deficiencies; coordinate availability of government furnished property; and facilitate site entry of contractor personnel. A letter of designation issued to the COR, a copy of which is sent to the contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost or price, estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting order.

1.6.9 Key Personnel: The follow personnel are considered key personnel by the government: Program Manager, Information Assurance Manager, and Database Architect or equivalent. The contractor shall provide a contract manager who shall be responsible for the performance of the work. The name of this person and an alternate who shall act for the contractor when the manager is absent shall be designated in writing to the contracting officer. The contract manager or alternate shall have full authority to act for the contractor on all contract matters relating to daily operation of this contract. The contract manager or alternate shall be available between 7:30 a.m. to 4:30p.m., Monday through Friday except federal holidays or when the government facility is closed for administrative reasons. Qualifications for all key personnel are listed below:

1.6.9.1 Information Assurance (Ia) Manager: The Contractor shall provide an Information Assurance (IA) Manager who shall ensure the enforcement and development of information system security procedures and plans. The IA Manager shall be involved in the plan development, ensuring system compliance, its auditing, investigation of security incidents, and preparation of reports related to security. The IA Manager shall be responsible for planning, implementing and maintaining the information assurance program, ensuring the security requirements have been incorporated appropriately in the system and that all the relevant documentation has been updated. The IA Manager shall have at least a Master’s Degree in a computer sciences, cyber security, or information security equivalent, or have at least 12-15 years’ experience.

1.6.9.2 Database Architect Or Equivalent: The Contractor shall provide a Database Architect who shall manage database configuration to meet MFLEETS requirements. The Database Architect shall ensure the database is secure, scalable and performs reliably. The Database Architect shall have at least a Master’s Degree in a relevant field such as database and network architecture, cloud computing sciences, cloud security, or networks management or have at least 8-10 years of database management experience.

1.6.10 Identification of Contractor Employees: The contractor (to include subcontractors) shall provide each employee an identification (ID) badge, which includes at a minimum, the company name, employee name and a color photo of the employee. ID badges for key personnel shall also indicate their job title. ID badges shall be worn at all times during which the employee is performing work under this contract. Each contractor (to include subcontractors) employees shall wear the ID badge in a conspicuous place on the front of exterior clothing and above the waist except when safety or health reasons prohibit. The contractor (to include subcontractors) shall be responsible for collection of ID badges upon completion of the contract or termination of employee. A listing of issued identification cards shall be furnished to the contracting officer prior to the contract performance date and updated as needed to reflect contractor and subcontractor personnel changes. All contract personnel attending meetings, answering government telephones, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are government officials. They must also ensure that all documents or reports produced by contractors are suitably marked as contractor products or that contractor participation is appropriately disclosed.

1.6.11 Supervision of Contractor Employees: The government will not exercise any supervision or control over contractor or subcontractor employees while performing work under the contract. Such employees shall be accountable solely to the contractor, not the government. The contractor, in turn, shall be accountable to the government for contractor or subcontractor employees.

1.6.12 Contractor Travel: The contractor will be required to travel CONUS and within the National Capital Region (NCR) during the performance of this contract to attend meetings, conferences, and conduct training. The contractor may be required to travel to off-site training locations and to ship training aids to these locations in support of this PWS. The contractor will be authorized travel expenses consistent with the substantive provisions of the Joint Travel Regulation (JTR) and the limitation of funds specified in this contract. All travel requires government approval/authorization and notification to the COR.

1.6.13 Other Direct Costs: This category includes reproduction, shipping expenses and costs associated with training activities and visits to contractor facilities. It could also entail the renting of suitable training venues.

1.6.14 Data Rights: The government has unlimited rights to all documents/material produced under this contract. All documents and materials, to include the source codes of any software, produced under this contract shall be government owned and are the property of the government with all rights and privileges of ownership/copyright belonging exclusively to the government. These documents and materials may not be used or sold by the contractor without written permission from the contracting officer. All materials supplied to the government shall be the sole property of the government and may not be used for any other purpose. This right does not abrogate any other government rights. The contractor shall provide standardized, reliable processes and mechanism for transferring physical possession of archived data to the DoD services. Data shall be viewable using any Microsoft application (software). Contractor shall provide video archive of data using optical drive data storage solutions that do not require proprietary software to retrieve or view video data. All archived data and transferred data is the the property of the government.

1.6.15 Organizational Conflict of Interest:

a. Purpose. The primary purpose of this clause is to aid in ensuring that:

(1) The Contractor does not obtain an unfair competitive advantage by establishing the ground rules for a future competition;

(2) The Contractor's objectivity and judgment are not biased because of its present or future interests (financial, contractual, organizational, or otherwise) which relate to work performed under this contract; and

(3) The Contractor does not obtain an unfair competitive advantage by virtue of its access to non-public or proprietary information belonging to others.

b. Definitions.

(1) The term “Contractor” herein used means: (a) the organization (hereinafter referred to as "it" or "its") entering into this agreement with the Government; (b) all business organizations with which it may merge, join or affiliate now or in the future and in any manner whatsoever, or which hold or may obtain, by purchase or otherwise, direct or indirect control of it; (c) its parent organization if any and any of its present or future subsidiaries, associates, affiliates, or holding companies, and; (d) any organization or enterprise over which it has direct or indirect control now or in the future.

(2) The term "proprietary information" for purposes of this clause means any information considered so valuable by its owners that it is held secret by them and their licensees. Information furnished voluntarily by the owner without limitations on its use, or which is available without restrictions from other sources, is not considered proprietary.

c. Organizational Conflicts of Interest Examples. The following examples illustrate situations in which organizational conflicts of interest may arise. These examples are not all inclusive.

(1) Biased Ground Rules. This type of conflict may arise in situations where a company sets the ground rules for a future competition.

(2) Impaired Objectivity. This type of conflict may exist where a Contractor’s obligations under a contract require objectivity, but another role of the Contractor casts doubt on its ability to be truly objective. An example of this type of conflict is where a Contractor’s work under one contract entails evaluating itself, its affiliates, or its competitors under a separate contract.

(3) Unequal Access to Information. This type of conflict may arise when a Contractor has access to nonpublic or proprietary information as part of its performance under a contract that gives it an unfair advantage in a competition for a later contract.

d. General Constraints. The provisions of FAR Subpart 9.5, Organizational and Consultant Conflicts of Interest, concerning organizational conflicts of interest govern this contract. Potential conflicts may exist in accordance with FAR 9.505-1, Providing Systems Engineering and Technical Direction, through 9.505-

4, Obtaining Access to Proprietary Information. In this regard, the Contractor is responsible for identifying any actual or potential organizational conflicts of interest to the Contracting Officer that arise as the result of performance under this contract. To avoid or mitigate a potential conflict related to performance under this contract, the Contracting Officer will impose appropriate constraints such as the constraints discussed below. Since it is impossible to foresee all of the circumstances that might give rise to organizational conflicts of interest, the constraints discussed below are not all inclusive and the Contracting Officer may impose constraints other than, or in addition to, the constraints listed below.

(1) The Contractor agrees that if it provides, under a contract or task order or delivery order, systems engineering and technical guidance for systems and programs, but does not have overall contractual responsibility, it will not be allowed to be awarded a contract or task or delivery order to supply the system or any of its major components or be a Subcontractor or consultant to a supplier of the system or any of its major components

(2) The Contractor agrees that if it prepares complete specifications for non-developmental items or assists in the preparation of work statements for a system or services under a contract or task order or delivery order, it shall not be allowed to furnish these items, either as a prime Contractor, a Subcontractor or as a consultant.

(3) The Contractor agrees that it shall neither evaluate nor advise the Government with regard to its own products or activities. The Contractor shall objectively evaluate or advise the Government concerning products or activities of any prospective competitors.

(4) The Contractor agrees that if it gains access to proprietary information of other companies, it shall exercise diligent effort to protect such proprietary information from unauthorized use or disclosure. In addition, the Contractor agrees to protect the proprietary information of other organizations disclosed to the Contractor during performance of this contract with the same caution that a reasonably prudent Contractor would use to safeguard highly valuable property. The Contractor also agrees that if it gains access to the proprietary information of other companies it shall enter into written agreements with the other companies to protect their information from unauthorized use or disclosure for as long as it remains proprietary and to refrain from using the information for any purpose other than that for which it was furnished. The Contractor shall provide copies of such agreements to the Contracting Officer.

(5) If the Contractor, in the performance of this contract, obtains access to plans, policies, reports, studies, financial plans, data or other information of any nature which has not been released or otherwise made available to the public, the Contractor agrees that without prior written approval of the Contracting Officer, it shall not: (a) use such information for any private purpose unless the information has been released or otherwise made available to the public, or (b) release such information unless release is otherwise authorized under the contract or such information has previously been released or otherwise made available to the public by the Government.

e. Non-Disclosure Agreements. The Contractor shall obtain from each employee who has access to proprietary information under this contract, a written agreement which shall in substance provide that such employee shall not, during his/her employment by the Contractor or thereafter, disclose to others or use for their benefit, proprietary information received in connection with the work under this contract. The Contractor shall educate its employees regarding the restrictions so that they shall not use or disclose proprietary information or data generated or acquired in the performance of this contract except as provided herein.

f. Training. The Contractor shall effectively educate its employees, through formal training, company policy, information directives and procedures, in an awareness of the legal issues so that each employee shall know and understand the bsolute necessity of safeguarding information from anyone other than the Contractor's employees who have a need to know, and the U.S. Government.

g. Subcontracts. The Contractor agrees that it shall include the provisions in paragraphs d., e., and f. above and this paragraph in consulting agreements, teaming agreements, and subcontracts of all tiers which involve access to information or the performance of services described in paragraph d. above. The use of this clause in such agreements shall be read by substituting the word "consultant" or "Subcontractor" for the word "Contractor" whenever the latter appears.

h. Additional Constraints. If this contract provides for the issuance of task or delivery orders, such orders may impose additional requirements and restrictions relating to this clause to include the requirement for the Contractor and its Subcontractors and employees to furnish the Government with written non-disclosure agreements or statements of no conflict of interest. With regard to any proposal submitted by the Contractor in response to a Request for Task or Delivery Order Proposal, by submitting its proposal the Contractor represents that it has disclosed to the Contracting Officer, prior to the issuance of the task or delivery order, all facts relevant to the existence or potential existence of organizational conflict of interest.

i. Conflicts Involving Future Procurements. The award of this contract, task or delivery orders issued under this contract, Government taskings, or acquiescence in the Contractor’s performance of services hereunder shall not constitute or be interpreted as a determination that the Contractor is eligible to participate in future procurements, developmental efforts, implementation efforts, or related activities. Only the Contracting Officers for such efforts, applying the rules, principles, and procedures have the authority to determine whether a conflict exists in connection with such procurements.

j. Representations and Disclosures.

(1) The Contractor represents that it has disclosed to the Contracting Officer, prior to award of this contract, all facts relevant to the existence or potential existence of organizational conflict of interest.

(2) The Contractor represents that if it discovers an organizational conflict of interest or potential conflict of interest after award of this contract, a prompt and full disclosure shall be made in writing to the Contracting Officer. This disclosure shall include a description of the action the Contractor has taken or proposes to take in order to avoid or mitigate such conflict.

k. Remedies and Waiver.

(1) For breach of any of the above restrictions or for non-disclosure or misrepresentation of any relevant facts required to be disclosed concerning this contract, the Government may terminate this contract for default, disqualify the Contractor for subsequent related contractual efforts, and pursue such other remedies as may be permitted by law or this contract. If, however, in compliance with this clause, the Contractor discovers and promptly reports an organizational conflict of interest (or the potential thereof) subsequent to contract award, the Contracting Officer may terminate this Contract or any task or delivery order issued under this Contract for convenience if such termination is deemed to be in the best interest of the Government.

(2) The parties recognize that this clause has potential effects which will survive the performance of this contract and that it is impossible to foresee each circumstance to which it might be applied in the future. Accordingly, the Contractor may at any time seek a waiver from the cognizant Contracting Officer by submitting a full written description of the requested waiver and the reasons.

1.6.16 Combat Trafficking In Person.

IAW FAR 52-222-50. Contractor Requirements.

The Contractor shall –

(1) Notify its employees of

(i) The U.S. Government's zero tolerance policy.

(ii) Actions that will be taken against employees for violations of this policy.

(2) Take appropriate action.

Part II, Trafficking in Persons (TIP)

1. The Contractor has a procedure for notifying employees of TIP and proof of such notification on file via: Training records or Employee signature

2. Has documented actions on file citing appropriate action to TIP violations.

3. Record of documented violations to date (if any).

4. The Contractor has a procedure for notifying the Contracting Officer if information is received or actions related to TIP are observed.

1.6.17. Access And General Protection/Security Policy and Procedures: All Contractor personnel performing work under this contract shall comply with applicable installation, facility and area commander installation/facility access, local security policies and security procedures provided by the Security Manager Government representative.

1.6.17.1. Contractor personnel shall comply with all personal identity verification requirements as directed by Department of Defense (DoD), HQ Department of Army (DA), HQ IMCOM or local policies. In addition to the changes otherwise authorized by this contract, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in Contractor and subcontractor security matters or processes.

1.6.19 Anti-Terrorism And Operations Security Requirements.

1.6.19.1. At Level I Training. All Contractor employees, to include subcontractor employees, shall submit certificates of completion for each affected Contractor employee and subcontractor employee, within 05 days after completion of training by all employees and subcontractor personnel. AT level I awareness training is available at the following website:

http://jko.jten.mil, Course # JS-US007.

1.6.19.2. Access And General Protection/Security Policy And Procedures: Contractor and all associated sub-Contractors employees shall comply with applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by Government representative). The Contractor shall also provide all information required for background checks to meet installation access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security Office. Contractor workforce must comply with all personal identity verification requirements as directed by DOD, HQDA and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in Contractor security matters or processes. For contractors that do not require CAC, but require access to a DoD facility or installation.

Contractor and all associated sub-contractors employees shall comply with adjudication standards and procedures using the National Crime Information Center Interstate Identification Index (NCIC-III) and Terrorist Screening Database (TSDB) (Army Directive 2014-05/AR 190-13), applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by government representative), or, at OCONUS locations, in accordance with status of forces agreements and other theater regulations.

1.6.19.3. iWATCH Training: The Contractor and all associated sub-Contractors shall brief all employees on the local iWATCH program (training standards provided by the requiring activity ATO). This training shall be completed within 30 days of contract award and within 05 days of new employees commencing performance with the results reported to the COR NLT 30 days after contract award."

http://www.myarmyonesource.com/familyprogramsandservices/iwatchprogram/default.aspx

1.6.19.4. Contractor Employees Who Require Access To Government Information Systems: All Contractor employees with access to a Government info system shall be registered in the ATCTS (Army Training Certification Tracking System) at commencement of services, and shall successfully complete the DOD Information Assurance Awareness prior to access to the IS and then annually thereafter.

1.6.19.5. Contracts That Require Opsec Training: Per AR 530-1, Operations Security, new Contractor employees shall complete Level I OPSEC training within 30 days of their reporting for duty. All Contractor employees shall complete annual OPSEC awareness training and adhere to organization’s security program. http://cdsetrain.dtic.mil/opsec/

1.6.19.6. Information Assurance (Ia)/Information Technology (It) Training: All Contractor employees and associated sub-contractor employees shall complete the DoD IA awareness training before issuance of network access and annually thereafter. All Contractor employees working IA/IT functions shall comply with DoD and Army training requirements in DoDD 8570.01, DoD 8570.01-M and AR 25-2 within six months of employment.

1.6.19.7. Threat Awareness Reporting Program: For all contractors with security clearances. Per AR 381-12 Threat Awareness and Reporting Program (TARP), contractor employees must receive annual TARP training by a CI agent or other trainer as specified in 2-4b of AR 381-12.

PART 2

DEFINITIONS & ACRONYMS

2. DEFINITIONS AND ACRONYMS:

2.1. DEFINITIONS:

2.1.1. CONTRACT ADMINISTRATOR. The official government representative delegated authority by the contracting officer to administer a contract.

This individual is normally a member of the appropriate contracting/procurement career field and advises on all technical contractual matters.

2.1.2. CONTRACTOR. A supplier or vendor awarded a contract to provide specific supplies or services to the government. The term used in this contract refers to the prime.

2.1.3. CONTRACTING OFFICER. A person with authority to enter into, administer, and/or terminate contracts, and make related determinations and findings on behalf of the government. Note: The only individual who can legally bind the government.

2.1.4. CONTRACTING OFFICER'S REPRESENTATIVE (COR). An employee of the U.S. government appointed by the contracting officer to administer the contract. Such appointment shall be in writing and shall state the scope of authority and limitations. This individual has authority to provide technical direction to the contractor as long as that direction is within the scope of the contract, does not constitute a change, and has no funding implications. This individual does not have authority to change the terms and conditions of the contract.

2.1.5. DEFECTIVE SERVICE. A service output that does not meet the standard of performance associated with the performance work statement.

2.1.6. DELIVERABLE. Anything that can be physically delivered, but may include non-manufactured things such as meeting minutes or reports.

2.1.7. GOVERNMENT-FURNISHED PROPERTY (GFP) OR GOVERNMENT PROPERTY (GP). Property in the possession of, or directly acquired by, the government and subsequently made available to the contractor.

2.1.8. KEY PERSONNEL. Contractor personnel that are evaluated in a source selection process and that may be required to be used in the performance of a contract by the key personnel listed in the PWS. When key personnel are used as an evaluation factor in best value procurement, an offer can be rejected if it does not have a firm commitment from the persons that are listed in the proposal.

2.1.9. PHYSICAL SECURITY. Actions that prevent the loss or damage of government property.

2.1.10. QUALITY ASSURANCE. The government procedures to verify that services being performed by the contractor are acceptable in accordance with established standards and requirements of this contract.

2.1.11. QUALITY ASSURANCE SPECIALIST. An official government representative concerned with matters pertaining to the contract administration process and quality assurance/quality control. Acts as technical advisor to the contracting officer in these areas.

2.1.12. QUALITY ASSURANCE SURVEILLANCE PLAN (QASP). An organized written document specifying the surveillance methodology to be used for surveillance of contractor performance.

2.1.13. QUALITY CONTROL. All necessary measures taken by the contractor to assure that the quality of an end product or service shall meet contract requirements.

2.1.14. SUBCONTRACTOR. One that enters into a contract with a prime contractor. The government does not have privity of contract with the subcontractor.

2.1.15. WORK DAY. The number of hours per day the contractor provides services in accordance with the contract.

2.1.16. WORK WEEK. Monday through Friday, except for federal holidays unless specified otherwise.

2.2. ACRONYMS:

PART 3

GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, AND SERVICES

3.1. Services: The Government will provide functional FirstNet connections at installation site and limited network support is available. The government will only provide commercial wireless connections as needed to suppprt each first responder vehicle equipped with MFLEETS capabilities.

3.2. Facilities: The Government will provide a single point of contact for coordination with the Contractor Project Manager and provide access to the GFE system and software. Government will provide access to first responder facilities and work areas as required with pre-authorization (eight hour notice).

3.3. Materials/Information: The Government will provide information and information transfer between CAD and JSLEVES vendors as required.

PART 4

CONTRACTOR FURNISHED ITEMS AND SERVICES

4. CONTRACTOR FURNISHED ITEMS AND RESPONSIBILITIES:

4.1 General: The contractor shall furnish all supplies, equipment, facilities and services required to perform work under this contract that are not listed under part 3 of this PWS.

4.2. The Contractor shall be reposnsible for all services (other than local mobile wireless cellular subscriptions - see conceptual diagram attached to this document), facilities, utilities, equipment, and materials/information required for the performance of this contract.

//area intentionally left blank//

PART 5

SPECIFIC TASKS

5. Specific Tasks:

5.1. Basic Services. The contractor, as an independent contractor and not as an agent of the Government, shall provide the necessary resources (except those furnished by the Government) to accomplish tasks of the type set forth within this PWS.

5.1.1. Contractor employees performing services under this contract shall be controlled, directed and supervised at all times by management personnel of the contractor. The contractor’s management shall ensure that employees properly comply with the performance standards outlined in this PWS. Contractor employees shall perform independent of and without the supervision of any Government official..

5.2. EXISTING MFLEETS COMPLIANT HARDWARE/CAPABILITIES

5.2.1. The contractor shall provide evidence capture and archival service to collect, store, retrieve, and manage electronic data captured through mobile technology platforms installed in law enforcement patrol vehicles. This capability will then be integrated to the mobile computer and the data center by the contractor using a COT commercial wireless solution. Existing evidence or video data prior to contract award will not be integrated to the data center provided by this contract.

5.2.2. Contractor shall activate connection of existing compliant hardware to the data center within 15 days of notification from the COR that the data center is approved and accredited (with interim, conditional or full authority to operate). Notification will occur using official email.

5.3. CLOUD COMPUTING. Contractor shall ensure that the Cloud Hosting solution will be a approved by the Defense Information System Agency (DISA) and accredited under FedRAMP level 5 accreditation standards immediately upon contract award. The Contractor shall ensure that the Cloud Computing solution functions IAW the DoD Cloud Computing Security Requirements Guide (current version at the time of operation) in all aspects of cloud computing. The Contractor will seek government permission before performing any work that would result in major upgrades increasing the performance envelope of existing systems. The contractor will also seek government permission before purchasing or executing any additional test articles, before conducting developmental testing and/or initial operational testing or evaluation, in order to meet the objectives of this contract.

5.3.1. Deliver a Federal Risk and Authorization Management Program (FedRAMP) Level 5 (level 5/High) accredited cloud service IAW the DoD Cloud Computing SRG (must use the most current version in effect) DISA Risk Management, Cybersecurity Standards Guide for the secure collection, review, archival, and distribution of video evidence collected by mobile users at Army and DoD installations. The FedRAMP Level 5 accreditation shall also include the systems used to collect evidence, networks used to transmit evidence, and devices used to store evidence at the data center.

5.4. COMMAND AND CONTROL ON THE MOVE (C2OTM)

5.4.1. Provide capability to allow remote monitoring, viewing, and operation of MFLEETS hardware mounted inside patrol vehicles while within network connectivity.

5.5. COMMON COMPUTING ENVIRONMENT

5.5.1. Deploy service to meet interoperability, installation, and interface requirements of the Joint Services Law Enforcement Vehicle Equipment Standards (JSLEVES) for integration of service components into Army and DoD service standardized law enforcement vehicles.

Provide a common accredited computing platform for integration and interoperability of law enforcement applications and mobile video devices.

5.6. COMMUNICATIONS ACTIVATION

5.6.1. Deploy mobile communications services for the secure transfer of data and controls between patrol vehicles, operations centers, and the MFLEETS services infrastructure. The contractor shall ensure end to end encryption from the vehicle to the data center using FIPS 140-2 compliant mechanisms.

5.7. CYBER SECURITY AND INFORMATION ASSURANCE

5.7.1. Contractor shall provide all Enterprise Mission Assurance Support Service (eMASS) artifacts, to include security controls, topology diagrams, hardware and software inventories for program security accreditation at the FEDRAM “Level 5 or high” level for law enforcement operations.

5.7.2. Contractor is responsible for all security controls listed in column “Q” of the attached “Security Control Template”. This template is based on an overall system categorization impact level of High with the following primary security control set from NIST SP 800-53 version 4:

Confidentiallity Moderate Integrity: High Availability: High

5.8. DATA MANAGEMENT

5.8.1. Contractor shall provide tools and services to facilitate the collection, consolidation, organization, review, retrieval, search, and distribution of video and audio data using mobile networking and cloud computing technologies. All data is the property of the government and will be stored on an optical disc archive solution that does not require proprietary software from the contractor to view hosted video data. The contractor shall provide a video solution that is viewable with any Microsoft viewing software. The contractor shall ensure that the government data is transferable to any data hosting solution (non-proprietary). The Contractor shall host a fully accredited data center the the required accreditation level. Provide cost effective mechanisms for storing, managing, and retrieving digital evidence data. Provide immutable storage solution able to protect digital evidentiary data from any alteration. Provide a storage solution able to preserve the quality and integrity of archived evidentiary data for a minimum of three (3) years. For the purposes of verifying compliance, storage solution should be designed to store government data up to 150 petabytes of data. Provide standardized, reliable processes and mechanism for transferring physical possession of archive data to the DoD services.

5.9. DOCUMENT PREPERATION AND REVIEW

5.9.1. Prepare all required technical, procedural, and process documentation required to meet FISMA FedRAMP “Level 5” accreditation requirements.

5.10. HUMAN FACTOR ENGINEERING

5.10.1. MFLEETS shall be ready for immediate use and require minimal task knowledge or input from the mobile user to operate. The Contractor shall provide a solution that prevents unauthorized users from accessing or altering video data and related meta data at any point during its life cycle from its collection through archival or disposal. Solution must be fully automated and video functions must be enabled by programmable triggers defined to meet policy requirements. Data will not be archived, stored, or retrieved in the datacenter by any personally identifiable information (PII). Provide audio/visual alarms when tampering is detected with mobile video devices. MFLEETS must provide high availability (i.e. elimination of single points of failure, reliable crossover, and detection of failures as they occur) for mobile video devices to ensure evidence capture is not subject to human intervention, control, or error.

5.11. COMMERCIAL “OFF-THE-SHELF” (COTS) INTEGRATION

5.11.1. MFLEETS must integrate with other IMCOM technical programs such as CAD, E911, JSLEVES, and First Responder Network Authority (FIRSTNET).

5.12. COMMERCIAL “OFF-THE-SHELF” (COTS) INTEROPERABILITY

5.12.1. The contractor must implement a solution that is designed to operate with standard Army and DoD systems, networks, and platforms, including but not limited to: CAD, E911, JSLEVES, and FIRSTNET.

5.13. NETWORK CONFIGURATION

5.13.1. Contractor shall implement communications network to enable MFLEETS hardware to operate using the mobile communications infrastructure available at each garrison location. Provide ability to securely transfer MFLEETS data from the field to the data center using FIRSTNET and commercial wide area network providers.

5.14. OPERATION AND MAINTENANCE OR DIRECT SUPPORT

5.14.1. Contractor shall provide Help Desk support for MFLEETS users during duty days and duty hours as outlined in this PWS. The Contractor shall also provide twenty-four (24) hours a day, seven (7) days a week on-call support for MFLEETS users. Provide twelve (12) months of maintenance for the full spectrum of MFLEETS services. Monitor continuous connectivity and operations of mobile platforms, data transfer and storage, and database and archive operations. Provide continuous monitoring of service for security events, vulnerabilities, network connectivity issues, data retrieval support, security patches and system scanning.

5.15. COTS INSTALLATION AND INTEGRATION

5.15.1. Contractor shall deploy an integrated platform to provide upload, consolidation, review, archival, and management of electronic video and audio data.

5.15.2. Hardware installation at local installations: When new vehicle delivery (does not apply to existing vehicles) by a marshalling yard is not available, contractor shall deliver, install and activate all required hardware and software within 30 days of notification to the help desk email by the COR or designated representative. Government will ensure vehicles are available as required to meet the obligations of this contract. A successful function test demonstrating data center connectivity and data upload implies acceptance at the local level.

5.15.3. Hardware installation at regional marshalling yards: When new vehicle delivery (does not apply to existing vehicles) to a marshalling yard is possible, the contractor shall deliver and install all required hardware and software within 14 days of notification to the help desk email by the COR or designated representative. Contractor shall activate all required hardware and software within 14 days of delivery to the local installation. Government will ensure vehicles are available as required to meet the obligations of this contract. A successful function test demonstrating data center connectivity and data upload implies acceptance at the local level.

5.15.4. System Deactivation. When the MFLEETS equipped vehicle is identified for turn-in, the Government will remove the in-car digital video hard drive, and will remove the hard drive from the mobile data terminal. These hard drives will be preserved as evidence by the government, while remaining hardware is turned in with the vehicle, at which point the contractor, in compliance with GSA, is responsible for the final disposition of the equipment.

5.16. Software Infrustructure and Applications Integration

5.16.1.…