ITAP_Master_PWS_2June16_V3.pdf

PERFORMANCE WORK STATEMENT

For

Innovative Transformative Applications Program (ITAP)

Prepared by:

U.S. Army Research Laboratory

Advanced Prototype and Experimentation (APEx) Team Adelphi, MD

Table of Contents

1.0 Description of Project

1.1 Scope

2.0 Project Summary

2.1 Project Summary (PS)

2.2 Performance Plan

3.0 Government Furnished Property/Services

3.1 Government Furnished Information (GFI)

3.2 Government Furnished Materials (GFM)/Equipment (GFE) and Facilities

4.0 Specific Tasks

4.1 Categories of Work

4.1.1 Task Area 1 - Initial End User Organization Coordination and Collaboration .. 5

4.1.2 Task Area 2 - Software Application Development for Real-time Coordination 5

4.1.3 Task Area 3 - Web Client Applications for Real-time Coordination

4.1.4 Task Area 4 - Integration of Applications and Technology

4.1.5 Task Area 5 - Modeling and Analysis

4.1.6 Task Area 6 - Field Demonstration, Pilot Testing and Education

4.1.7 Task Area 7 - Technology Scouting for State-of-the-Art

4.1.8 Task Area 8 - Reference Architecture and Ecosystem

4.2 Contractor Requirements

4.3 Personnel Qualifications

4.4 Single Managers

4.5 Program Management

4.6 Team – Subcontractor Management

4.7 Delivery/Task Order Requirements

4.8 Field Representation

4.9 Access to Facilities and Property

4.10 D/TO Deliverables

4.11 D/TO Data Requirements

4.12 Release/Removal of Documentation

4.13 Safety and Environmental

4.14 Safety Plan

4.15 Safety Reporting

4.16 Quality Control

4.17 Software Engineering

4.18 Travel Requirements

4.19 Security (Installation and Personnel)

4.20 Non-Development Items (NDI)

4.21 Contractor Furnished Materials and Equipment

4.22 Commercial Processes and Technologies

4.23 Risk Management

4.24 Meetings and Reviews

4.25 Technical Interchange Meetings (TIMs)

4.26 Performance Reviews

4.27 Logistics Support Analyses

4.28 Packaging, Handling, Storage, Marking and Transportation

4.29 Reporting

4.30 Anti-Terrorism (AT)

4.31 Information Assurance (IA)

1.0 Description of Project

1.1 Scope

Innovative Transformative Applications Program (ITAP) will leverage and continue DARPA's Transformative Applications (TA) program which defined mobile platform technical standards for Department of Defense research and development programs. The TA program used an aggressive spiral research and development process through embedded personnel with military operational end users in real combat situations in Afghanistan and in training, exercise and VIP event situations stateside. This tightly coupled development effort provided an unprecedented understanding of Warfighter, first responder and law enforcement requirements and allowed real time assessment of applications utility to mission areas. DoD requires additional research and development, cross-agency interoperability, prototyping, hosting, systems engineering, security validation, and test and evaluation in this area to maintain a tactical/technical edge against our adversaries.

This contract will be awarded to GXM whom was down selected through the DARPA TA Broad Agency Announcement (BAA) that selected six Teams to compete on the TA Program.

Over a 4-Year Period GXM became the company selected by DARPA to lead TA Program through its final phases. The TA Ecosystem, Mobile Mapping Tools, 120 plus S/W Applications, Market Place and H/W Designs will continue to be maintained and optimized under this contract. ARL will use a framework similar to that of the DARPA TA program to identify new TA solutions and requirements for organizations that require cross-agency interoperability, innovation, prototyping and hosting expertise. ARL and the GXM TA Team will directly support Joint Service Explosive Ordnance Disposal (JSEOD) community, Joint Improvised-Threat Defeat Agency (JIDA), National Ground Intelligence Center (NGIC), and Geographic Combatant Commands (SOCOM, EUCOM, AFRICOM, SOUTHCOM, PACOM) and other government agencies to continue development and evaluation of the utility of Smart Phones, Tablets, S/W Applications, Wearable and Non-Wearable Sensors and ancillary equipment. Additionally, this effort will provide solutions for the DoD National Security Technology Accelerator (NSTA) to enhance innovation by providing a collaborative environment that will allow non-traditional companies the opportunity to better understand defense requirements and propose application solutions, as well as, aid in Transition of Technology to better serve the war-fighter and first responders

2.0 Project Summary

2.1 Project Summary (PS)

No project summary will be required on the basic contract. Project summaries may be required for individual D/TOs.

2.2 Performance Plan

No performance plan will be required on the basic contract. Performance Plans may be required for individual D/TOs.

3.0 Government Furnished Property/Services

3.1 Government Furnished Information (GFI)

To the maximum practicable extent, the Government, via Integrated Digital Environment (IDE), will provide available information needed to support individual D/TO performance in digital format.

3.2 Government Furnished Materials (GFM)/Equipment (GFE) and Facilities

The TA Ecosystem that was developed under Contract XXXX will be provided as GFE on this effort. Additional GFE/GFM may be required to support individual D/TOs. In such cases, the GFM/GFE clauses of the contract will be supplemented by specific delivery and disposition instructions along with a list and value of the GFM/GFE being provided in each individual D/TO requiring GFM/GFE. In such cases, the contractor shall provide a GFM/GFE Property Control Plan. Upon completion of the contract, all GFM/GFE property will revert back to the government.

4.0 Specific Tasks

This research and development effort will focus on efficient and timely production of leading-edge mobile technology that focuses on the end user while identifying solutions for cross-agency interoperability, innovation and prototyping while overcoming existing communications and networking obstacles, consists of the following tasks:

NOTE: Level of effort and scope will be specified in detailed Task Orders for all Task Areas

4.1 Categories of Work

4.1.1 Task Area 1 - Initial End User Organization Coordination and Collaboration

The contractor shall identify end-user organizations (OCONUS and CONUS) to coordinate and collaborate with to better understand the role of innovative technology and software applications in existing and changing mission areas. The contractor will capture this information to establish new requirements and document understanding of the challenges of each organization to focus initial planning of future research and development activities.

4.1.2 Task Area 2 - Software Application Development for Real-time Coordination

4.1.2.1 Identify and Review Requirements for Applications

The contractor shall identify requirements for software applications from designated end user organizations feedback and approved requirements. Requirements will be vetted and validated in terms of practicality, operational impact, available funding, priority and technical capability/resources, through users and organizations designated by the Army Research Laboratory (ARL) Program Manager. Multiple related requirements shall be consolidated into single application suites for development through sprint cycles within an agile development framework.

Using the framework of agile development where appropriate, the contractor shall work with end users, customer and/or subject-matter-experts (SMEs) designated by the ARL Program Manager to identify requirements and capture these in a web-based electronic system such that they can be easily reviewed, prioritized and approved for development and execution.

4.1.2.2 Develop the Applications

The contractor shall develop applications for use on platforms that have been approved through the requirements review process. The contractor shall provide technology innovation capabilities that will enable rapid prototyping and technology evaluation as the basis for assessing the feasibility of developing a new or unfamiliar technology; assessing or mitigating technical risk; validating requirements; demonstrating critical features; verifying a product;

validating a product; determining enabling product readiness characterizing performance or product features; or discovering physical principles. This effort will allow transformation of proposed concepts and ideas into usable forms for field testing in operational settings. These prototypes will allow interactive development of emerging capabilities by providing users an opportunity to use and familiarize themselves with the prototype capability well before it is operationalized.

The contractor shall develop software applications for upload to designated networks, based on requirements identified by end users. When directed by the ARL Program Manager, the contractor will coordinate with commercial entities where existing proprietary software applications may be more appropriate to fulfill end user requirements.

The contractor shall utilize a software revision control system to store source code of the developed software applications and subsequent revisions. Working in concert with the contractor Product Owner, Lead Developer, Test team and SMEs and with the ARL Program Manager, the Software Development team shall create software versions for the purpose of testing, releasing and distributing them to the end users. Both source code and binary formats shall be deliverables to the customer. The contractor shall maintain Software Configuration Control Management (SCCM) using best practices approved by the ARL Program Manager.

The source code for all applications created under contract shall be maintained with this SCCM.

4.1.2.3 Test the Applications

The contractor shall establish a rigorous and efficient testing protocol for all software applications in accordance with industry best practices and approved standards (Unit Testing, Integration Testing, Smoke Tests, etc.). This testing will occur initially within the development team, then the testing team and subsequently with ARL Program Manager designated testers.

After defects/bugs have been addressed, the software applications shall be provided to end users for field testing with program staff members. The contractor shall prepare necessary documentation required for certification and accreditation of applications on designated networks. The test results shall be available to end users designated by the ARL Program Manager.

4.1.3 Task Area 3 - Web Client Applications for Real-time Coordination

4.1.3.1 Identify and Review Requirements for Applications

The contractor shall identify requirements for web based client applications from designated end users/end user organizations and end user feedback. Requirements shall be vetted in terms of practicality, impact, available funding, priority and technical capability/resources, through users and organizations designated by the ARL Program Manager. Multiple but related requirements shall be consolidated into single application packages for development through sprint cycles within an agile methodology framework where appropriate.

4.1.3.2 Develop the Applications

The contractor shall develop the applications for use on platforms that have been approved through the requirements review process. The contractor shall provide technology innovation capabilities that will enable rapid prototyping and evaluation as the basis for assessing the feasibility of a new or unfamiliar technology; assessing or mitigating technical risk; validating requirements; demonstrating critical features; verifying a product; validating a product;

determining enabling product readiness characterizing performance or product features; or discovering physical principles. It will allow the transformation of proposed concepts and ideas into usable forms that can be taken into the field and tested in operational settings. These prototypes will serve as vehicles for interactive development of emerging capabilities by giving potential customers an opportunity to use and familiarize themselves with the prototype capability before it is operationalized.

The contractor shall develop software applications that are uploaded to the network and based on requirements documentation from end user requirements. The contractor shall also coordinate with commercial entities where existing proprietary applications may be more appropriate to meet end user requirements.

Web application source code shall be managed in a source code revision control system, independent from other source code. On a regular basis, working in concert with the Product Owner, Lead Developer, Test team SMEs and the Program Manager, the Software Development team shall generate software versions to support comprehensive integration testing, software delivery and deployment. Both the source code and subsequent software releases shall be deliverables to the customer.

4.1.3.3 Test the Applications

The contractor shall establish a rigorous yet efficient testing protocol for all of the applications in accordance with approved standards and prepare all of the documentation required for certification of the applications on the various networks. This testing will occur initially within the development team and subsequently with the CONUS-based test team as well as ARL Program Manager designated testers. After defects/bugs have been addressed the applications shall be provided to end users both stateside and overseas to be more thoroughly tested with program staff.

4.1.4 Task Area 4 - Integration of Applications and Technology

4.1.4.1 Identify Integration Targets

The contractor shall identify the various software systems and databases on each network that applications require integration with and develop an approved integration plan to enable either one-way or two-way communication with those systems. The contractor shall provide data management support identifying information needs, data requirements, data conversion, and data strategies. Data management activities include re-use of existing resources through discovery of available data services and data repositories in order to provide timely, accurate information and supporting protection. Data management will support end user organizations in identifying and determining what data is available; the quality of data; how data is used; how to incorporate data into resource management decision; and how data will be managed over time.

4.1.4.2 Develop the Integration Plan

The contractor shall design and develop an Integration Plan to enable applications to read/write into identified software systems and databases. The Integration Plan shall define the required software development and certification/accreditation efforts necessary to integrate the applications into the targeted software systems and databases. The contractor shall provide systems engineering services to support end user organizations in integrating the applications.

Support for integration will include solutions engineering, systems planning, requirements, design, development, integration and test, implementation, operations and maintenance, and disposal activities.

The systems engineering will include execution of activities such as, systems engineering subject matter expertise (SME) support, requirements identification, enterprise architecture support, application and systems design and development, information assurance, application and systems testing, help desk support, and training. The contractor shall support creation of documentation artifacts required by end user organizations as well as other system related diagrams, gate and decision event review packages, program assessments, certification and accreditation (C&A) artifacts, models, etc. as required.

4.1.4.3 Execute the Integration Plan

The contractor shall execute the integration plan to integrate the applications into the targeted software systems and databases on identified networks.

4.1.5 Task Area 5 - Modeling and Analysis

The contractor shall develop data models and conduct risk analysis to support identification and inter dependencies against multiple characterizing attributes and data sources. Support will include, but not be limited to, modeling to risk methodology analysis, uncertainty analysis, sensitivity analysis, and risk assessment tool analysis across various scenarios, hazards, threats, vulnerabilities, and consequences in support of requirements.

The contractor shall provide support for Geospatial Information System (GIS) analysis and development services to facilitate identification of critical assets and vulnerabilities using an inter-agency geographic framework. The contractor shall provide support required for designing inter-agency services for manipulating various information resources. These analyses will include geospatial production and situational awareness support using geospatial tools and geographic information systems.

4.1.6 Task Area 6 - Field Demonstration, Pilot Testing and Education

4.1.6.1 Field Demonstrations/Exercises

The contractor shall work with end users as designated by the ARL Program Manager to identify how developed applications on the platforms and web clients effectively support the intended missions. Based on the outcomes of these exercises and research, the contractor shall develop after action reports and feedback to be spiraled into ongoing development process for enhancements, defect corrections, device upgrades/corrections and the development of new concepts.

4.1.6.2 Pilot Testing

The contractor shall conduct events that involve pilot testing programs with government end users. The intent is to aggressively gather feedback and requirements and to spiral these requirements back into the development processes with program development staff.

4.1.6.3 Education and Training Programs

The contractor will also establish training/education programs as necessary to inform new government end users on identified technologies/processes/programs so that appropriate metrics and measures of success can be gathered from innovative prototype activities. These educational programs may involve collaboration with academic institutions for subject matter expertise as identified by the ARL Program Manager.

4.1.7 Task Area 7 - Technology Scouting for State-of-the-Art

The contractor shall provide ARL with periodic reports on the State-of-the-Art innovative technologies. These analyses will support identification of disruptive, game-changing and force multiplying capabilities and allow prioritization for investigation and provide a basis for applying resources for rapid adoption of highest value capabilities. This approach will support the goal to develop, maintain and increase technical dominance. The contractor shall stay abreast of new capabilities/developments in the commercial and government spheres and serve as subject matter experts to ARL in this critical area.

4.1.7.1 Report Format

The report shall highlight new capabilities in the following areas and provide references/links so that ARL can provide this information to other researchers. The report is intended to be a survey of the current state-of-the-art. As such, it should highlight new capabilities, explain why they are significant and pinpoint potential benefits to warfighters and end users. The areas currently identified are as follows, however ARL may change, expand or contract this list during the contract so that the research best serves the needs of the US Government. The reports should include such recommendations to assist ARL to best focus efforts in this dynamic field.

• Hardware Capabilities

• Power Capabilities and Limitations

• Operating System Capabilities

• Networking Capabilities

• Peripheral Capabilities

• Security Improvements and Limitations

4.1.7.2 Report Engineering

The contractor shall conduct sufficient engineering and testing of new commercial capabilities to determine the maturity of new capabilities. ARL will assess and prioritize proposed testing to ensure best use of limited resources.

4.1.8 Task Area 8 - Reference Architecture and Ecosystem

The contractor shall develop a lightweight framework that shall provide a reusable reference architecture for software application development to create and sustain software applications quickly and economically. The purpose of this architecture is to standardize common capabilities that may readily be reused in other applications. This will speed capability development, provide a means for multiple solution providers to reuse core capabilities when building lightweight software applications and create an ecosystem of applications around a common core framework.

4.1.8.1 Architecture Design

The design of the Reference Architecture shall be created using agile development methodologies. The reference architecture will be developed with due consideration for practical use to avoid significant rework for end-user applications. The contractor shall develop and use the reference architectural when performing all development activities. This will ensure the reference architectural is designed at the correct abstraction level to provide a reusable framework that minimizes problems faced by solution providers.

4.1.8.2 Architecture Development

The reference architecture development shall be done in an agile and interactive/incremental fashion. It shall use an evolutionary approach and be part of other development activities. It will be an evolving architecture that will grow and mature through the lifetime of the contract. It should incorporate best agile practices in the development, to ensure sufficient maturity to allow reuse by other solution providers.

4.1.8.3 Architecture Testing

As the architecture is developed, unit tests and system tests shall be developed in parallel. A Continuous Integration and Test process shall be implemented to allow for errors to be detected and corrected rapidly. This will increase robustness, use and acceptance of the architectural throughout the development community.

4.1.8.4 Architecture Dissemination

The contractor will make recommendations for best methods to make the reference architecture available to other solution providers. Any flaws, limitations and suggested improvements will be referred by ARL to the vendor for incorporation into the next release of the architecture for the duration of this contract. ARL may require adoption of a Government Open Source Software model so that multiple solution providers may contribute to the reference architecture.

4.2 Contractor Requirements

The contractor shall provide the services and supplies specified herein in accordance with this PWS and the applicable individual D/TOs.

4.3 Personnel Qualifications

General and unique personnel qualifications will be specified in the D/TO.

4.4 Single Managers

The contractor shall establish a single manager Point of Contact (POC) for program management, and one POC for contracting, having authority and responsibility for the overall effort for all D/TOs. The intent of each single manager is to give the Government agencies one point of contact for each management area to avoid possible duplication of effort from multiple D/TOs.

4.5 Program Management

The contractor shall be responsible for managing all aspects of the contract and awarded D/TOs, to include cost, schedule, performance and contract management. The contractor shall act as the task integrator, assuring that all technical and program elements of a D/TO provide a fully integrated approach. The contractor shall also participate (as directed) in Program Management Reviews where performance requirements and D/TO accomplishment will be discussed.

4.6 Team – Subcontractor Management

The contractor may disseminate portions of D/TOs to team members (subcontractors) based upon areas of expertise. The contractor may subcontract with other companies to establish a strong technical capability to meet diverse D/TO requirements. The prime contractor shall be held fully responsible for all aspects of each D/TO performance and oversight, regardless of any arrangement between its subcontractors and vendors.

4.7 Delivery/Task Order Requirements

The contractor shall perform tasks as specified by individual D/TOs.

4.8 Field Representation

In some cases, the complexity of system problems will warrant extended contractor representation at operational bases and repair depots. In such instances the contractor may be required to physically observe and evaluate system performance, collect data, provide on-the-spot assistance for operational problems, and perform as a liaison between Government, contractor, and/or subcontractor representatives.

Requirements for field representation may be presented to the contractor and required as an integral part of problem resolution and/or task assignment. Contractor personnel assigned to field activities shall be fully qualified individuals who have knowledge of the systems related to a specific D/TO.

4.9 Access to Facilities and Property

Access to Government facilities and sites is limited. Therefore, the contractor shall coordinate the need, time, and personnel requiring access with the Task Order Initiator (TOI) prior to need.

Contractor clearances shall be confirmed prior to access to any restricted areas. Access to appropriate and affected data systems will be provided as authorized by the Government. All contractor personnel shall comply with facility requirements for vehicle entry and personnel identification badges before being allowed access to facilities to accomplish the tasks as specified by individual D/TOs. Any local requirements and procedures for access to Government facilities and property will be specified by the Government requirements POC for each D/TO.

4.10 D/TO Deliverables

The Quality Assurance Personnel (QAP) assigned at the D/TO level will identify the point of contact, normally the Contracting Officer’s Representative (COR), responsible to reject or require correction of any deficiencies found in deliverables unless otherwise defined in individual D/TOs. In the event of rejection of any deliverable, the contractor may be notified in writing by the contracting officer of the specific reasons why the deliverable was rejected.

4.11 D/TO Data Requirements

The contractor shall provide data as required on DD Forms 1423 as specified by the basic contract and individual D/TOs.

4.12 Release/Removal of Documentation

The contractor shall not release or remove system documentation, data, or reports generated by or through the use of any Government systems. All requests for information shall be forwarded to the contracting officer who will request approval from the designated government official.

4.13 Safety and Environmental

Individual D/TOs may require the contractor to comply with safety provisions, e.g., technical specifications, technical publications, MIL-Standards, Federal Occupational Safety and Health Standards (Title 29 CFR Part 1910) or other applicable nationally recognized or local sources of safety, health, and fire prevention standards. Safety shall be conducted in accordance with approved procedures and as specified by individual D/TOs.

The contractor shall comply with all applicable federal, state and local safety, health and environmental regulations, including the National Environmental Policy Act (NEPA), as appropriate with D/TOs. The contractor shall immediately inform the Contracting Officer’s Representative (COR) of any violation issued by any Federal, State or Local agency responsible for managing safety and environmental regulations and also identify the measures taken to resolve the issue.

4.14 Safety Plan

No safety plan will be required on the basic contract. Safety plans may be required for individual D/TOs. If required by an individual D/TO, the contractor shall submit a Safety Plan for approval.

4.15 Safety Reporting

The contractor shall comply with the instructions in this section. The prime contractor shall report class A, B, and C mishaps for itself and all subcontractors. Further prime and subcontractors will meet the below.

Contractor Compliance. Contractors shall comply with Occupational Safety and Health Act (OSHA) (Public Law 91-596) and the resulting standards. OSHA Standard 29 CFR 1910, 1926, and the protection of their employees.

Environmental, Safety, and Occupational Health (ESOH). The contractor is solely responsible for compliance with the Occupational, Safety and Health Act (OSHA) (Public Law 91-596) and the resulting standards, OSHA Standard 29 CFR 1910 and 29 CFR 1926, as applicable and the protection of their employees. It is the contractor’s sole responsibility to make certain that all safety requirements are met. Additionally, the prime contractor is responsible for the safety and health of all subcontractor employees.

Contractor Safety Program. For each individual D/TO the contractor shall establish and maintain an acceptable safety program. As directed, the contractor shall submit a safety plan which must be approved by the Government. All changes to the plan must also be submitted in writing and approved by the Government.

Contract Safety Manager. As part of the Contractor Safety Program, the contractor shall assign in their safety plan at the D/TO level, by name and phone number, a person who will be the primary point of contact for safety and health issues. The contractor will keep the contract safety manager information current by notifying the contracting officer of any change in personnel or contact information.

4.16 Quality Control

The contractor shall be responsible for the performance of quality control activities, ensuring the performance of products, subcontractors, and vendors. Specific quality requirements will be specified by individual D/TOs.

4.17 Software Engineering

The contractor shall apply effective software engineering processes to all software requirements.

4.18 Travel Requirements

Travel requirements will be specified by individual D/TOs. Airfare for travel and per diem shall be billed IAW Joint Travel Regulations (JTR). The contractor shall be responsible for making their own travel and lodging arrangements as necessary to support the requirements of each D/TO.

4.19 Security (Installation and Personnel)

The contractor shall comply with the instructions in this section. For the purpose of these instructions, the Servicing Security Activity (SSA) is the local military security organization that provides security support for all Government and contractor personnel performing on the installation.

a. Facility Clearance, Personnel Security Clearances, and Background Investigations: The contractor must possess a facility clearance at the classification level indicated on the associated DD Form 254, Department of Defense (DoD) Contract Security Classification Specification. It is anticipated that some Requests for Proposals (RFPs) and resultant D/TOs will be classified acquisitions up to and including Top Secret. Contractors that do not possess the required clearance and safeguarding capability at time of RFP release will not be eligible to receive that RFOP and resultant D/TO. DD Forms 254 will be attached to the RFPs and resultant D/TOs as required. Each contractor requiring access to unclassified Government automated information systems will only require a National Agency Check (NAC), as a minimum, in accordance with DoD 5200.2-R, Personnel Security Program. The SSA will process the necessary documentation for the contractor to obtain the necessary background investigation as specified by DoD 5200.2-R for the level of access required. Each employee requiring a background investigation for this purpose will comply with instructions furnished by the cognizant security manager and the SSA.

Security clearance requirements for contractor personnel, up to and including Top Secret/Sensitive Compartmented Information (SCI), will be specified in individual D/TOs.

b. Long-term Visitor Group Security Agreement: The contractor shall comply with the provisions of the National Industrial Security Program Operating Manual (NISPOM), the security procedures of the host military installation where D/TO performance will occur, and the requirements specified in the applicable DD Form 254. Where classified contract performance will occur on a military installation for 90 days or longer, the contractor shall enter into a long-term visitor group security agreement. This agreement, provided by the Government program manager in concert with the SSA, shall be tailored to specific mission and performance requirements and will include NISPOM and local military security procedures as applicable. As a visitor group operation, contractor access is controlled by the Government. Visitor group security agreements suffice in lieu of Standard Practice Procedures (SPPs). See Notification of Government Security Activity and Visitor Group Security Agreements Clause (AFFARS 5352.204-9000) in the basic contracts.

c. Notification of Government Security Activity: Thirty (30) days before the date contractor operations will begin on the military installation, the contractor shall furnish the SSA at the performance location all information required by the clause, Notification of Government Security Activity and visitor group security agreements (AFFARS 5352.204-9000). Contact the SSA identified in Item 13 of the DD Form 254 for assistance in obtaining the address of the applicable SSA for the performance location.

d. Contractor Credentials and Vehicle Entry: For contract performance on a military installation, contractor will comply with local procedures provided by the SSA to obtain contractor credentials and vehicle entry.

e. Unescorted Entry Authorizations: To obtain unescorted entry authorizations into controlled or restricted areas, contractor will comply with local procedures provided by the SSA.

Forms accomplished to obtain such entry must be certified by the SSA to ensure the individual requiring unescorted entrance has a personnel security clearance or a favorable background investigation.

f. Counterintelligence Awareness Briefing: The contractor shall comply with the military installation's Counterintelligence Awareness Program. Contractor personnel shall report to an appropriate authority any information or circumstances of which they are aware may pose a threat to the security of DoD personnel, contractor personnel, resources, and classified or unclassified defense information. Contractor employees shall be briefed on this requirement by their immediate supervisor upon initial on-base assignment.

4.20 Non-Development Items (NDI)

NDI and commercial products shall be used in accordance with individual D/TOs.

4.21 Contractor Furnished Materials and Equipment

The contractor shall acquire any additional hardware and software not provided by the Government as required to accomplish individual D/TOs. Ownership will be established in accordance with terms and conditions specified within individual D/TOs. The contractor is required to maintain software integrity in accordance with the licensing agreement of the vendor.

The contractor is responsible to assure the completeness and correctness of the data before performance and completion of individual D/TOs. Required data types, formats, and transmission media will be specified by individual D/TOs.

4.22 Commercial Processes and Technologies

The contractor shall apply commercially acceptable processes and technologies, as appropriate, in accordance with individual D/TOs.

4.23 Risk Management

The procuring contracting officer (PCO) reserves the right to request a risk mitigation plan for mitigating major risks identified in accordance with individual D/TOs. The plan shall outline the major risks to executing the proposed program concept and the contractor’s proposed mitigation strategies.

4.24 Meetings and Reviews

The contractor shall be required to provide kickoff meetings, interim project reviews, project closeout meetings and other meeting as required in the execution of each D/TOs. The meeting and review schedule will be identified in accordance with individual D/TOs.

4.25 Technical Interchange Meetings (TIMs)

The contractor shall participate in TIMs as required by the manager for the individual D/TO.

The Government D/TO Manager will specify agenda and attendance requirements, with specific dates and locations, at least 10 calendar days prior to the meeting.

4.26 Performance Reviews

The contractor shall attend Contract Performance Reviews as required by the basic contract.

These meetings will focus on overall contract performance. Specific dates, locations, agenda and attendance requirements will be specified by the COR at least 30 days prior to each meeting. Individual D/TOs may also require Contract Performance Reviews.

4.27 Logistics Support Analyses

The contractor shall perform or assist in the performance of Logistics Support Analyses (LSA) as required by individual D/TOs. The contractor shall review any existing Integrated Logistics Support (ILS) Plan and/or LSA Plan for subsystems that are the target of redesign.

After this review, modifications and changes shall be identified and the contractor shall prepare an LSA Plan in accordance with dictated standards. Prior to approval of the LSA Plan, the contractor may be required to host an LSA Guidance Conference to review and further define LSA requirements. Delineation of tailored LSA task deliverables shall be accomplished at the LSA Guidance Conference for each D/TO.

4.28 Packaging, Handling, Storage, Marking and Transportation

Packaging will be accomplished in accordance with individual D/TOs, as applicable.

4.29 Reporting

Specific Reporting Requirements will be outlined in each D/TO.

4.30 Anti-Terrorism (AT)

Contractors and all associated sub-contractors who will handle or have access to Classified Information are directed to analyze 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); any revisions to DOD 5220.22-M, notice of which has been provided by the COR as Government Furnished Information {GFI} at contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable. Handling of and Access to Classified Information requirements as stated above are addressed in the PWS or be in the technical requirement in paragraph: 4.0

4.31 Information Assurance (IA)

Contractor Employees and associated sub-contractor employees who require access to Government Information Systems must successfully complete the DOD Information Assurance Awareness training, other mandatory IA training (ArmyG3 security, Cyber Security Tip, Home Computer Security, Personally Identifiable Information Handling, Phishing, and Portable Electronic Devices) and complete an ARL Acceptable Use Policy (AUP) form prior to access to the information systems. The DOD Information Assurance Awareness training must be completed annually thereafter, and the ARL AUP will need to be re-signed after any major change. This information is provided by the COR as Government Furnished Information {GFI} at contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable. The ARL Acceptable Use Policy (AUP) is at:

https://arlinside.arl.army.mil/inside/pubsforms/ARLFormsinPureEdge/AUP%20- %20Acceptable%20Use%20Policy.xfdl

After an ARL host clicks the URL above they will log into ARL Inside and then assist the contractor employee to complete the form.

After completion of the AUP it must be forwarded to the ARL Corporate Information Office (CIO) Information Assurance Management (IAM) office at:

usarmy.adelphi.arl.mbx.arl-iam@mail.mil

ARL Information Systems Access requirements as stated above are addressed in the PWS or be in the technical requirement in paragraph: 4.0