W15QKN20R0007-0001.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. Contract ID Code Page Of

2. Amendment/Modification No.

3. Effective Date

4. Requisition/Purchase Req No.

5. Project No. (If applicable)

6. Issued By Code 7. Administered By (If other than Item 6) Code

8. Name And Address Of Contractor (No., Street, City, County, State and Zip Code)

9A. Amendment Of Solicitation No.

9B. Dated (See Item 11)

10A. Modification Of Contract/Order No.

10B. Dated (See Item 13) Code Facility Code

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

The above numbered solicitation is amended as set forth in item 14. The hour and date specified for receipt of Offers is extended, is not extended.

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing items 8 and 15, and returning ____________ copies of the amendments: (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. Accounting And Appropriation Data (If required)

13. THIS ITEM ONLY APPLIES TO MODIFICATIONS OF CONTRACTS/ORDERS

It Modifies The Contract/Order No. As Described In Item 14.

A. This Change Order is Issued Pursuant To: The Changes Set Forth In Item 14 Are Made In

The Contract/Order No. In Item 10A.

B. The Above Numbered Contract/Order Is Modified To Reflect The Administrative Changes (such as changes in paying office, appropriation data, etc.) Set

Forth In Item 14, Pursuant To The Authority of FAR 43.103(b).

C. This Supplemental Agreement Is Entered Into Pursuant To Authority Of:

D. Other (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return _______________ copies to the Issuing Office.

14. Description Of Amendment/Modification (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

Except as provided herein, all terms and conditions of the document referenced in item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. Name And Title Of Signer (Type or print)

16A. Name And Title Of Contracting Officer (Type or print)

15B. Contractor/Offeror 15C. Date Signed 16B. United States Of America 16C. Date Signed

By (Signature of person authorized to sign) (Signature of Contracting Officer)

NSN 7540-01-152-8070

PREVIOUS EDITIONS UNUSABLE

30-105-02 STANDARD FORM 30 (REV. 10-83)

Prescribed by GSA FAR (48 CFR) 53.243

SEE SCHEDULE

X

Firm Fixed Price

0001 2020JUN15

W15QKN

ARMY CONTRACTING COMMAND - NJ

PICATINNY ARSENAL, NJ 07806-5000

NICHOLAS R GLAZEWSKI

EMAIL: NICHOLAS.R.GLAZEWSKI.CIV@MAIL.MIL

W15QKN-20-R-0007

2020JUN02

X

X

/SIGNED/

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 26

CONTINUATION SHEET

Reference No. of Document Being Continued Page of

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION A - SUPPLEMENTAL INFORMATION

Buyer Name: NICHOLAS R GLAZEWSKI

Buyer Office Symbol/Telephone Number: CCNJ-JA/(973)724-8874

Type of Contract 1: Firm Fixed Price

Type of Contract 2: Time and Materials

Kind of Contract: Service Contracts

*** End of Narrative A0000 ***

The purpose of this amendment, 0001, is to answer questions and make associated updates based upon the questions received from industry:

1. Would the Government please consider increasing the page limitation for the Past Performance Volume to 15 pages? As the Government states offerors must list all relevant contracts within a three (3) year period, ten (10) pages can pose a severe limitation on an

Offeror's ability to accurately and completely address all relevant citations.

Answer: Yes, this amendment shall increase the page limitation from 10 to 15.

Update: Section L.2.1 has been updated to reflect this.

2. What is the Government's estimated date of award?

Answer: Estimated date of contract start is DEC 2020.

Update: No change required.

3. This section [4.3.4.5] is in reference to replacing/upgrading E9-1-1 systems. However, the last statement in this item is referencing replacing "other MWN" systems. Is there an expectation to provide pricing on a separate CLIN for upgrading an MWN system?

Answer: If done, this would be done on a future task order and has no bearing in submission of the current proposal.

Update: No change required.

4. [The] PWS section is currently numbered 1.3.7. Should this be numbered 4.3.7?

Answer: Yes, this amendment shall renumber 1.3.7 to 4.3.7.

Update: PWS paragraph 1.3.7 renumbered to 4.3.7.

5. Will the Government accept Contractor Performance Assessment Reports (CPARS) instead of PPQS, if they are available?

Answer:Every effort should be made to have PPQs filled out and submitted. The SST will do its due diligence and search other databases as stated in L.3.2.2.

Update: No change required.

6. Please confirm there is no page limitations for Volume IV: Solicitations, Offer and Award Documents and

Certifications/Representations.

Answer: Confirmed.

Update: No change required.

7. Will the Government please allow 9 pt font for graphics?

Answer: 9 point font for graphics is acceptable if the graphic remains legible.

2 26

W15QKN-20-R-0007

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Update: L.2.3.1 has been updated to include a statement saying that " 9 point font is acceptable for graphics".

8. Section M.2.2 states that there are three subfactors for the Technical Factor, however it lists 5 subfactors within the section. Can the Government please confirm that there are only 3 evalutated subfactors - Subfactor 1: Sustainment Plan, Subfactor 2: Sample Task

Proposal, and Subfactor 3: Management Plan?

Answer: Subfactor 4: Understanding of Requirements & Subfactor 5: Feasibility of Approach are not subfactors and have been removed from the solicitation.

Update: M.2.2 has been updated to remove Subfactors 4 & 5.

9. Item 9(b) states that the offeror shall provide a written plan with its offer describing how it will continue essential contractor services during periods of crisis. Section L provides no instructions or page allocation for this plan. Please confirm that no plan is required with proposal submission.

Answer: This plan is required as part of the clause it is referenced in. The plan shall be submitted in Contractor Format as part of

Volume IV, with no page limitations. The plan can be general in nature and will be incorporated as part of the awarded contract (this is

NOT part of the evaluation factors for selection).

Update: L.3.4.1 has been updated to include 252.237-7024 Essential Contractor Services Emergency Plan.

10. Will the government allow the PWS reference to be placed in the header of the paragraph to maintain linkage between the PWS references and the proposal document?

Answer: Yes. However, an index is still required.

Update: No change needed.

11. Will the government please provide the final deadline for questions to be submitted?

Answer: Deadline for submission of questions is 25 JUN 2020 @ 1500 EST.

*** END OF NARRATIVE A0002 ***

3 26

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION C - DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

Performance Work Statement (PWS) for

Mass Warning and Notification (MWN) and Enhanced 911 (E911) Sustainment

1. Objective

2. Scope

3. Applicable Documents

4. Performance Requirements

5. General Information

6. Accounting for Contract Service

7. Security

8. Non U.S. Citizens Requirements

9. Combating Trafficking in Persons

10. Environmental

1. OBJECTIVE

1.1 This Performance Work Statement (PWS) establishes and defines the requirements for Contractor support associated with the sustainment of the Mass Warning and Notification (MWN), Enhanced 911 (E911), Audio Visual Notification (AVN), and Giant

Voice Integration (GVI) Systems to the fielded Department of Defense (DoD) installations. The systems were fielded as part of the

Emergency Management Modernization Program (EM2P). The capability of the DoD installations to reach personnel during times of high criticality must be maintained and enhanced.

1.2 The MWN System supports fully integrated Short Message Service (SMS) text messaging to cell phones, e-mail notifications, and phone call notifications to users. It is capable of tracking users responses / acknowledgements to the notifications in real-time so that the installation can have situational awareness of the event. It integrates with Giant Voice towers with the ability to target specific towers or tower groups with text-to speech capability where applicable.

1.3 The E911 System provides both Automatic Number Identification (ANI) and Automatic Location Information (ALI) data to the emergency operators, which allows for tracking of the caller recording, storing, and playback of all 911 calls placed through the system; and management of all E911 activities through a suite of software applications running at dispatch or emergency operation centers.

1.4 The AVN System provides notifications through various alternative means where traditional MWN capabilities are inadequate due to high noise or lack of technology. The various means shall include scrolling marquees, beacons, strobes, sirens, speakers, and paging systems.

2. SCOPE

2.1 The Weapons and Software Engineering Center (WSEC) within Combat Capabilities Development Command Armaments Center (CCDC-AC) in support of the Tank Automotive Command (TACOM) Life Cycle Management Command (LCMC) is tasked to sustain current Emergency Management

(EM) capabilities to multiple installations by providing labor, materials, and equipment to perform lifecycle sustainment services.

This includes enterprise Network Alerting Systems (NAS), Telephonic Alerting System (TAS), Giant Voice Integration (GVI), Audio Visual

Notification System (AVNS), and Enhanced 911 (E911) to selected Installations. Other EM systems, over the life of the contract, could be included in the same type of overall sustainment effort.

2.2 US Army Alert! provides the current Army NAS, TAS, and GVI solutions.

2.3 Alertus provides the current Army MWN-integrated AVNS and GVI solutions.

2.4 Microautomation, VESTA Solutions, and Spok provide the current Army E911 solutions.

2.5 Scope includes preventive and corrective maintenance, repair and replacement, service calls, as well as systems / software upgrades, system trainings, and tech refreshes as necessary. These technology areas were established as a result of emergency management gaps identified in the Fort Hood Army Internal Review Team: Final Report (Applicable Document 3.2). It was determined that emergency staffs at installations were not able to inform and track their personnel during emergency situations.

3. APPLICABLE DOCUMENTS

1. Defense Information Systems Network (DISN) Secret Internet Protocol Routing Network (SIPRNet) Security Classification Guide

2. Fort Hood Army Internal Review Team: Final Report

3. 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.

4 26

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

4. PERFORMANCE REQUIREMENTS

4.1. Mass Warning and Notification (MWN) Systems

4.1.1. Configuring MWN Systems:

4.1.1.1. Configuring client applications to communicate with cloud based MWN Systems.

4.1.1.2. Configuring cloud based systems to fit the needs and requirements of individual unique locations.

4.1.1.3. Configuring MWN Systems to integrate with other MWN Systems including but not limited to: Facebook, Twitter, Federal Emergency

Management Agency (FEMA) Integrated Public Alert & Warning System (IPAWS), Giant Voice systems, and Audio Visual Notification Systems

(AVNS).

4.1.1.4. Configuring routine backups to minimize downtime in the event of an issue/failure.

4.1.1.5. Configuring enterprise based MWN systems to trigger locally hosted MWN, AVNS, and GVI Systems to send out messages.

4.1.1.6. Restoring systems back to the last stable version or from backups.

4.1.2. Patching MWN Systems to include:

4.1.2.1. Routine vendor and operating System patches.

4.1.2.2. DoD Information Assurance Vulnerability Management (IAVM) patches.

4.1.2.3.Client and Server version upgrades and patches.

4.1.2.4. Developing and implementing a patching and testing plan to ensure all patches do not impact the operations of the system.

4.1.2.5. Distributing patching instructions to local Network Enterprise Center (NEC) and Signal commands to ensure systems are kept up to date and secure.

4.1.3. Performing Help Desk responsibilities and tasks both remotely and in person:

4.1.3.1. Routine day to day operational issues which shall include: password resets, system performance issues, and remotely assisting users operating the system.

4.1.3.2. Assisting super users in routine tasks including the following: drafting messages, sending messages, developing templates, maintaining the user database, and troubleshooting operational concerns.

4.1.3.3. Developing lessons learned documentation to share across the user base intended to prevent users from making the same mistakes others have, share best business practices, best optimize the use of the system.

4.1.3.4. Emergency onsite troubleshooting provide a technician on site within forty eight (48) hours of a problem being identified as unable to be corrected remotely.

4.1.3.5. Coordinate troubleshooting activities between product vendors, NECs, system administrators, and the end user.

4.1.3.6. Operate a twenty four/seven (24/7) help desk supporting users around the globe.

4.1.4. Upgrading MWN Systems:

4.1.4.1. Coordinate software, hardware, and full systems upgrades with various NECs and hosting organizations.

4.1.4.2. Upgrading system components such as the operating system, hardware, and peripherals.

4.1.4.3. Rolling systems over to a cold, warm, or hot backup during a maintenance window or upon a failure.

4.1.5. Documenting and obtaining approvals for the MWN systems:

4.1.5.1. Obtaining and maintaining accreditation packages for MWN systems such as: Certificate of Networthiness (CoN), Authority to

Operate, Joint Interoperability Test Command (JITC) certifications, and all necessary local approvals.

4.1.5.2. Documenting test procedures, deployment strategies, maintenance plans, troubleshooting guides, user guides, administrator guides, and lessons learned documents.

4.1.5.3. Experience working with outside organizations and higher headquarters such as United States (US) Army Network Enterprise

Technology Command (NETCOM), Signal Commands, local NECs, installation Garrison staff, Flag Officers, and the general user base.

4.1.6. Analyzing system performance, design, and architecture and making cost saving and performance enhancing suggestions to help obtain best value.

4.1.7. Provide periodic MWN refresher training to personnel at fielded system locations. 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 shall 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 (Applicable Document 3.3) as guidance.

4.2. Audio Visual and Notification (AVN) Systems

4.2.1. Configuring AVN Systems:

4.2.1.1. Configuring locally deployed AVN systems servers to communicate with cloud based MWN systems for centralized alert publishing.

5 26

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

4.2.1.2. Configuring beacons, strobes, marquees, and other audio visual tools to communicate with a locally hosted centralized server.

4.2.1.3. Configuring servers and other AVN systems technologies to reside on a local NEC controlled DoD network in compliance with all

DoD policies and procedures.

4.2.1.4. Configuring routine backups to minimize downtime in the event of an issue/failure.

4.2.1.5. Restoring systems back to the last stable version or from backups

4.2.2. Patching AVN Systems to include:

4.2.2.1. Routine vendor and Operating System patches.

4.2.2.2. DoD IAVM patches.

4.2.2.3. Client and Server version upgrades and patches.

4.2.2.4. Developing and implementing a patching and testing plan to ensure all patches do not impact the operations of the system.

4.2.2.5. Distributing patching instructions to local NECs and Signal Commands to ensure systems are kept up to date and secure.

4.2.3. Performing Help Desk responsibilities and tasks both remotely and in person:

4.2.3.1. Routine day-to-day operational issues which shall include: password resets, system performance issues, and remotely assisting users operate the system.

4.2.3.2. Assisting super users in routine tasks including the following: drafting messages, sending messages, developing templates, maintaining the user database, and troubleshooting operational concerns.

4.2.3.3. Developing lessons learned documentation to share across the user base intended to prevent users from making the same mistakes others have, share best business practices, best optimize the use of the system.

4.2.3.4. Emergency onsite troubleshooting: Provide a technician on site within forty eight (48) hours of a problem being identified as unable to be corrected remotely.

4.2.3.5. Coordinating troubleshooting activities between product vendors, NECs, system administrators, and the end user.

4.2.3.6. Operate a twenty four/seven (24/7) help desk supporting users around the globe.

4.2.4. Upgrading AVN Systems:

4.2.4.1. Coordinating software, hardware, and full systems upgrades with various NECs and hosting organizations.

4.2.4.2. Upgrading system components such as the operating system, hardware, and peripherals.

4.2.4.3. Developing and executing upgrade plans to minimize system down time.

4.2.5. Documenting and obtaining approvals for AVN Systems:

4.2.5.1. Obtaining and maintaining accreditation packages for AVN Systems which shall include: CoN, Authority to Operate, JITC certifications, and all necessary local approvals.

4.2.5.2. Documenting test procedures, deployment strategies, maintenance plans, troubleshooting guides, user guides, administrator guides, and lessons learned documents.

4.2.5.3. Experience working with outside organizations and higher headquarters such as NETCOM, Signal Commands, local NECs, Installation

Garrison staff, Flag Officers, and the general user base.

4.2.6. Analyzing system performance, design, and architecture and making cost saving and performance enhancing suggestions to help obtain best value.

4.2.7. Provide periodic AVNS refresher training to personnel at fielded system locations. 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 shall 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 (Applicable Document 3.3) as guidance.

4.3. Enhanced 911 (E911) Systems

4.3.1. Configuring E911 Systems:

4.3.1.1. Configuring client applications / desktops to communicate with a centralized server E911 System.

4.3.1.2. Configuring E911 systems to fit the needs and requirements of individual unique locations.

4.3.1.3. Configuring Automatic Number Identification (ANI) and Automatic Location Identification (ALI) circuits to communicate with E911

Systems.

4.3.1.4. Configuring E911 Systems to integrate with other systems including ALI databases, phone switches, and surrounding communities

911 technologies.

4.3.1.5. Configuring digital voice recorders to capture all calls coming into the 911 facility.

4.3.1.6. Restoring or rebuilding systems in the event of a failure.

4.3.2. Patching E911 Systems to include:

6 26

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

4.3.2.1. Routine vendor and Operating System patches.

4.3.2.2. DoD IAVM patches.

4.3.2.3. Client and Server version upgrades and patches.

4.3.2.4. Developing and implementing a patching and testing plan to ensure all patches do not impact the operations of the system.

4.3.2.5. Distributing patching instructions to local NECs and Signal Commands to ensure systems are kept up to date and secure.

4.3.3. Performing Help Desk responsibilities and tasks both remotely and in person:

4.3.3.1. Routine day-to-day operational issues which shall include: assisting with account management, system performance issues, customizing system settings, and remotely assisting users operate the system.

4.3.3.2. Assisting super users in routine tasks including the following: retrieving audio logs, troubleshooting hardware failures, investigating rollover failures, and providing step by step directions to accomplish a task.

4.3.3.3. Developing lessons learned documentation to share across the user base intended to prevent users from making the same mistakes others have, share best business practices, and best optimize the use of the system.

4.3.3.4. Emergency onsite troubleshooting provide a technician on site within forty eight (48) hours of a problem being identified as unable to be corrected remotely.

4.3.3.5. Coordinating troubleshooting activities between product vendors, NECs, system administrators, and the end user.

4.3.3.6. Operate a twenty four/seven (24/7) help desk supporting users around the globe.

4.3.4. Upgrading E911 Systems

4.3.4.1. Coordinating software, hardware, and full systems upgrades with various NECs and hosting organizations.

4.3.4.2. Upgrading system components such as the operating system, hardware, and peripherals.

4.3.4.3. Developing and executing upgrade plans to minimize system down time.

4.3.4.4. Providing expertise in new E911 system features among leading vendors in the industry.

4.3.4.5. The replacement of an existing 911/E911 system with a new E911 system shall be an optional Contract Line Item Number

(CLIN)/requirement within the task order PWS. Options for replacement of other MWN systems may be included on a task order basis.

4.3.5. Documenting and obtaining approvals for E911 Systems

4.3.5.1. Obtaining and maintaining accreditation packages for E911 Systems which shall include: CoN, Authority to Operate, JITC certifications, and all necessary local approvals.

4.3.5.2. Documenting test procedures, deployment strategies, maintenance plans, troubleshooting guides, user guides, administrator guides, and lessons learned documents.

4.3.5.3. Experience working with outside organizations and higher headquarter such as NETCOM, Signal Commands, local NECs, Installation

Garrison staff, Flag Officers, and the general user base.

4.3.6. Analyzing system performance, design, and architecture and making cost saving and performance enhancing suggestions to help obtain best value.

4.3.7. Provide periodic E911 refresher training to personnel at fielded system locations. 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 shall 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 (Applicable Document 3.3) as guidance.

4.4. The Contractor shall adhere to all applicable safety and security precautions during the site preparation, configuration, and repair of sustainable systems. The Contractor shall maintain environmental compliance (EC), health and safety program (HS), to include reviewing EC and HS plans and monitoring health and safety performance and ensuring effective actions are taken for continuous improvement per 29 CFR 1926 Occupational Safety and Health Administration (OSHA).

5. GENERAL INFORMATION

5.1 Travel

5.1.1 Travel shall be established for each individual task order. Travel shall be in accordance with the Joint Travel Regulations

(JTR) as practicable.

5.1.2 Costs for transportation shall be based upon mileage rates, actual costs incurred, or a combination thereof, provided the method used results in a reasonable charge. Travel costs shall be considered reasonable and allowable only to the extent that they do not exceed on a daily basis, the maximum per diem rates in effect at the time of the travel. The JTR shall provide the basis for the determination as to whether travel is reasonable and allowable. Maximum use is to be made of the lowest available customary standard coach or equivalent airfare accommodations available during normal business hours.

7 26

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

5.2 Contract Data Requirements List (CDRL), DD Form 1423, shall be specified for each individual task order.

5.3 Period of Performance - The period of performance for this contract shall be five (5) years. Each task order shall have its own defined period of performance.

5.4 Incidental Government Furnished Property (GFP) - GFP shall be identified for each individual task order.

5.5 Place of Performance - The place of performance shall primarily be Contractor facilities. In addition, the Contractor shall be required to perform system maintenance and repair at government facilities. Contractor shall maintain secret clearance to access

Government facilities.

5.6 Data Rights. 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 contract.

5.7 Information Disclosure. A Non-Disclosure Agreement (NDA) (CDRL B001, DI-MGMT-82241, TAILORED) 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.

5.8 Accidents and Incidents. The Contractor shall immediately report with 24 hours any major accident or incident, including fire, which results in any of the following: one (1) or more disabling injuries, damage to Government property exceeding $10,000, disruption of program plans or production schedules, degradation of the safety of equipment under contract such that personal injury or property damage shall be involved, or identifies a potential hazard which requires correction action. The Contractor shall prepare an

Accident/Incident Report (CDRL B002, DI-SAFT-81563) for each incident.

The Contractor employees, including subContractor employees, shall comply with all building, installation, facility and security policies and procedures such as all fire drills and building evacuations. The Contractor shall report their evacuation immediately to their COR to confirm compliance.

5.9 Materials. Any material purchase by the Contractor must be approved by the Government prior to purchasing.

5.10 Non-Personal Services. The Government shall neither supervise Contractor employees nor control the method by which the Contractor performs the required tasks. Such Contractor employees shall be accountable solely to the Contractor who, in turn is responsible to the

Government.

Under no circumstances shall the Government assign tasks to, or prepare work schedules for, individual Contractor employees. It shall be the responsibility of the Contractor to manage its employees and to guard against any actions that are of the nature of personal services, or give the perception of personal services. If the Contractor believes that any actions constitute, or are perceived to constitute personal services, it shall be the Contractor's responsibility to notify the Procuring Contracting Officer (PCO) immediately.

5.11 Government - Contractor Relationships. The Government and the Contractor understand and agree that the services to be delivered under this contract by the Contractor to the Government are non-personal services and the parties recognize and agree that no employer-employee or master-servant relationships exist or shall exist under the Contract between the Government and the Contractor and/or between the Government and the Contractor's employees. It is therefore in the best interest of the Government to afford the parties a full and complete understanding of their respective obligations.

Contractor personnel under this contract shall not:

(1) be placed in a position where they are appointed or employed by a Federal Officer, or are under the supervision, direction, or evaluation of a Federal Officer, Military or Civilian.

(2) be placed in a staff or policy making position.

(3) be placed in a position of command, supervision, administration or control over DA Military or Civilian personnel, or personnel of other Contractors, or become a part of the Government organization.

(4) be used for the purpose of avoiding manpower ceilings or other personnel rules and regulations of DA or the Civil Service

Commission.

(5) be used in administration or supervision of military procurement activities.

b. Employee Relationships

Rules, regulations, directions, and requirements which are issued by command authorities under their responsibility for good order, administration, and security are applicable to all personnel who enter any Government installation, or who travel on Government transportation. This is not to be construed or interpreted to establish any degree of Government control which is inconsistent with a non-personal services contract.

5.12 Identification of Contractor Employees:

a. All Contractor employees shall be identified as such by wearing badges at all times while performing work at Government facilities and when performing work for the Government under the scope of specific contract at other installations or nongovernment sites to include attendance at meetings, seminars, etc. The badges shall be either affixed to clothing or be displayed from a chain or other mechanism worn around the neck. Badges must include Contractor's company name and employee's name. No other items shall be placed on the badge.

b. Contractor workspace shall ensure that Federal employees and the public know that they are not Federal employees.

8 26

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

c. Contractor employees shall initially identify themselves by name and company affiliation when answering the telephone, presenting briefings, conducting or attending meetings/seminars or any other situations where their Contractor status is not obvious.

d. Official Contractor correspondence (written, facsimile, and email display) shall include their company name and any other documents or reports produced by Contractors are identified as Contractor products or Contractor participation is disclosed.

5.13 Inherently Governmental Functions. The Contractor shall not provide inherently governmental functions as defined in FAR 2.101 under this contract.

6. ACCOUNTING FOR CONTRACT SERVICE

6.2.1. The Office of the Assistant Secretary of the Army (Manpower & Reserve Affairs) operates and maintains a secure Army data collection site where the Contractor shall report ALL Contractor manpower (including subContractor manpower) required for performance of this contract.

6.2.2. The Contractor is required to completely fill in all the information in the format using the following web address https://Contractormanpower.army.pentagon.mil . The required information includes:

6.2.2.1. Contracting Office, Contracting Officer, Contracting Officers Technical Representative;

6.2.2.2. Contract number, including task and delivery order number;

6.2.2.3. Beginning and ending dates covered by reporting period;

6.2.2.4. Contractor name, address, phone number, e-mail address, identity of Contractor employee entering data;

6.2.2.5. Estimated direct labor hours (including sub-Contractors);

6.2.2.6. Estimated direct labor dollars paid this reporting period (including subContractors);

6.2.2.7. Total payments (including sub-Contractors);

6.2.2.8. Predominant Federal Service Code (FSC) reflecting services provided by Contractor (and separate predominant FSC for each sub-

Contractor if different);

6.2.2.9. Estimated data collection cost;

6.2.2.10. Organizational title Associated with the Unit Identification Code (UIC) for the Army Requiring Activity (the Army Requiring

Activity is responsible for providing the Contractor with its UIC for the purposes of reporting this information).

6.2.2.11. Locations where Contractor and subContractors perform the work (specified by zip code in the United States and nearest city, country, when in an overseas location, using standardized nomenclature provided on website);

6.2.2.12. Presence of deployment or contingency contract language; and

6.2.2.13. Number of Contractor and sub-Contractor employees deployed in theater this reporting period (by country).

6.2.3. As part of its submission, the Contractor shall also provide the estimated total cost (if any) incurred to comply with this reporting requirement. Reporting period shall be the period of performance not to exceed twelve (12) months ending September 30 of each government fiscal year and must be reported by 31 October of each calendar year.

6.2.4. Contractors shall use a direct Extensible Markup Language (XML) data transfer to the database server or fill in the fields on the website. The XML direct transfer is a format for transferring files from a Contractors systems to the secure web site without the need for separate data entries for each required data element at the web site. The specific formats for the XML direct transfer shall be downloaded from the web site.

7. SECURITY

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

7.2 DFARS Clause 252.225-7043 applies to this contract.

7.3 The Contractor shall 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 shall only receive classified material at the actual performance location(s) as identified in block 8a of the DD254.

7.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 of the DD254.

7.5 Information Disclosure: _______________________

7.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 shall also have to sign a non-disclosure agreement provided by the requiring activity for the protection of unclassified, sensitive and/or proprietary information.

7.6 Personnel: __________

7.6.1 Contractor personnel shall have the appropriate level of investigation and/or security clearance for each site of performance of

9 26

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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 shall 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 shall notify the AOR the same day as an employee receives notice that they shall be released, have been fired, or have had their security clearance revoked or suspended.

7.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 a Certification Data Report / Mandatory

Training (CDRL B003, DI-MISC-80678) 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/ .

7.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.

7.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. The Contractor shall also provide all information required for background checks to meet installation access requirements to be accomplished by the installation Provost Marshal Office, Director of Emergency Services, or

Security Office. Contractor workforce must comply with all personal identity verification requirements (CFR clause 52.204-9, Personal

Identity Verification of Contract Personnel) 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 shall require changes in Contractor security matters or processes. During FPCONs Charlie and Delta, services/installation access shall be discontinued/postponed due to higher threat. Services shall resume when FPCON level and or threat is reduced to an acceptable level as determined by the Installation Commander. Contractor personnel working on an installation are required to participate in the Installation Random Antiterrorism Measures Program as directed. Contractors shall be subject to and must comply with vehicle searches, wearing of ID badges, etc. Failure to comply with policies and procedures could result in barred access onto the installation.

7.10 iWATCH (See Something, Say Something) Training: All Contractor employees, including subContractor employees, shall receive training and participate in the local iWATCH program (training standards provided by the requiring activity ATO). This locally developed training shall be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR. This training shall be completed within 45 calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever applies, and then annually thereafter. The Contractor shall submit a Certification Data Report

/ Mandatory Training (CDRL B003, DI-MISC-80678) 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. Slides available to COR at https://www.milsuite.mil/book/docs/DOC-284984 .

7.11 Before CAC issuance, the Contractor employee requires, at a minimum, a favorably adjudicated National Agency Check with Inquiries

(NACI) or an equivalent or higher investigation in accordance with Army Directive 2014-05. The Contractor employee shall be issued a CAC only if duties involve one of the following: (1) both physical access to a DoD facility and access, via logon, to DoD networks on-site or remotely; (2) remote access, via logon, to a DoD network using DoD-approved remote access procedures; or (3) physical access to multiple DoD facilities or multiple non-DoD federally controlled facilities on behalf of the DoD on a recurring basis for a period of 6 months or more. At the discretion of the sponsoring activity, an initial CAC shall be issued based on a favorable review of the FBI fingerprint check and a successfully scheduled National Awareness Check With Inquiries (NACI) at the Office of Personnel Management.

7.12 Contractor and all associated subContractor employees shall comply with adjudication standards and procedures using the National

Crime Information Center Interstate Identification Index (NCIC-III) and Terrorist Screening Database (Army Directive 2014-05/AR 190-13);

applicable installation, facility and area commander installation and 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.

7.13 DFARS Clause 252.225-7043, AT/Force Protection (FP) Policy for defense Contractors outside of the US applies to this contract. The key AT requirement is for Contractor personnel to comply with theater clearance requirements and COCOM policies and directives.

7.14 Threat Awareness Reporting Program: Per AR 381-12, Threat Awareness and Reporting Program (TARP), Contractor employees must receive annual TARP training by a counterintelligence (CI) agent or other trainer as specified in 2-4b. This training shall be completed within 12 months after contract start date or effective date of incorporation of this requirement into the contract, whichever applies, and then annually thereafter. The Contractor shall submit a Certification Data Report / Mandatory Training (CDRL B003, DI-MISC-80678) for each affected Contractor employee and subContractor employee to the COR (or to the contracting officer, if a COR is not assigned)

10 26

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

within 14 calendar days after completion of training by all employees and subContractor personnel. Training can be executed by a local

CI agent, online via the Army Learning Management System at https://www.lms.army.mil (and search for TARP), or by contacting the 308th Military Intelligence Battalion at usarmy.pica.902-mi-grp.list.308th-picatinnyfo@mail.mil and 973-724-5446.

7.15 All Contractor employees, including subContractor employees, with access to a government information system must be registered in the Army Training Certification Tracking System (ATCTS) at commencement of services and must successfully complete the DoD Cyber

Awareness training prior to access to the information system and then annually thereafter. The Contractor shall submit a Certification

Data Report / Mandatory Training (CDRL B003, DI-MISC-80678) 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.

7.16 IA/Information Technology (IT) Training: All Contractor employees, including subContractor employees, employees must complete the

DoD Cyber awareness training before issuance of network access and annually thereafter. The Contractor shall submit a Certification Data

Report / Mandatory Training (CDRL B003, DI-MISC-80678) 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. All Contractor employees working IA/IT functions must comply with DoD and Army training requirements in DoDD

8570.01, DoD 8570.01-M, and AR 25-2 within six months of employment.

7.17 IA/Information Technology (IT) certification: Per IA best business practices, DFARS 252.239-7001, Information Assurance Contractor

Training and Certification and AR 25-2, All Contractor employees, including subContractor employees, supporting IA/IT functions shall be appropriately certified upon contract award. The Contractor shall submit a Certification Data Report / Mandatory Training (CDRL B003, DI-

MISC-80678) 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. The baseline certification as stipulated in DoD 8570.01-M must be completed upon contract award.

7.18 Government Furnished Items: All Contractor employees, including subContractor employees, shall return all issued U.S. Government owned equipment which includes travel laptops, mobile devices, Common Access Cards, installation badges, and/or access passes to the COR when the contract is completed or when a Contractor employee no longer requires access to the installation or facility.

7.19 Information Management Army Information Technology /IA: The Contractor shall be capable of accessing, handling, receiving, and storing UNCLASSIFIED documents, equipment, hardware, and test items, using the applicable standards of FOUO information. Controlled

Unclassified Information (documents designated as FOR OFFICIAL USE ONLY and/or LIMITED DISTRIBUTION) shall be submitted by a controlled means using USPS mail, Safe Access File Exchange (SAFE) website and/or DoD Army approved encryption software as per AR 25-1.

7.20 The Contractor shall comply with FAR 52.204-2, Security Requirements. This clause involves access to information classified

Confidential, Secret, or Top Secret and requires Contractors to comply with (1) the Security Agreement (DD Form 441), including the

National Industrial Security Program Operating Manual (DoD 5220.22-M), and (2) any revisions to DoD 5220.22-M, notice of which has been furnished to the Contractor.

7.21 Export Control Laws/International Traffic in Arms Regulation: DFARS Clause 252.225-7048, Export-Controlled Items applies to this effort. All documents determined to contain export controlled technical data shall be marked with the following notice: WARNING: - This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., App. 2401 et seq.

Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive

5230.25.

7.22 All Contractor employees, including subContractor employees, shall comply with the applicable Interim Program Protection Plan

(IPPP)/ Program Protection Plan (PPP)/ or Technology Protection Plan (TPP). The Contractor shall comply with DOD, DA, and AMC technology protection requirements in DODI 5200.39, AR 70-1, DA PAM 70-3, and AMC-R-380-13.

7.23 For Official Use Only Information (FOUO) and Controlled Unclassified Information (CUI): Contract personnel shall be capable of accessing, handling, receiving, and storing UNCLASSIFIED documents, equipment, hardware, and test items, using the applicable standards of FOUO and CUI. DFARS Clause 252.204-7012, Safeguarding Covered Defense Information and Cyber Incident Reporting applies to this effort.

7.24 The Contractor shall develop an Operations Security (OPSEC) Plan (B004, DI-MGMT-80934C), within 90 calendar days of contract award, to be reviewed and approved by the responsible Government OPSEC officer, per AR 530-1, Operations Security. This SOP/Plan shall specify the projects critical information, why it needs to be protected, where it is located, who is responsible for it, and how to protect it.

In addition, the Contractor shall identify an individual who shall be an OPSEC Coordinator. The Contractor shall ensure that this individual becomes OPSEC Level II certified per AR 530-1. CCDC Armaments Center OPSEC POC e-mail: usarmy.pica.rdecom-ardec.mbx.ardec-opsec@mail.mil.

7.25 Per AR 530-1 (or DoDM 5205.02-M), new Contractor employees, including subContractor employees, must complete initial (Level I)

OPSEC training within 30 calendar days of reporting for duty and must also complete annual OPSEC awareness training as provided by the appropriately designated OPSEC level II trained OPSEC Officer/Coordinator. The Contractor shall submit a Certification Data Report /

Mandatory Training (CDRL B003, DI-MISC-80678) for each affected Contractor employee and subContractor employee to the COR (or to the

11 26

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

contracting officer, if a COR is not assigned) within 14 calendar days after completion of training by all employees and subContractor personnel. The Contracting Officer Representative (COR) or Agreements Officer Representative (AOR) can request CCDC Armaments Center

OPSEC training from CCDC Armaments Center OPSEC POC e-mail: "mailto:usarmy.pica.rdecomardec.mbx.ardec-opsec@mail.mil " .