PWS.pdf

PWS for AISA Tool Development 23 October 2015

Introduction and Purpose A major PARCA initiative in support of Better Buying Power (BBP) 3.0 has been to improve agility in acquisition, intelligence and requirements processes to better serve warfighter needs. These processes are inherently slow and are not integrated to sustain core force capabilities. PARCA leadership is working within the Department and the Intelligence Community to move from this status quo to a fully agile integrated enterprise. A major initiative in this transition to acquisition agility is the use of a commercial practice, the service level agreement. PARCA is piloting and prototyping its construct called an Acquisition Intelligence Support Agreement (AISA) to define and clarify demand and timelines for intelligence support. AISA development would occur as early as possible in the life of a project to promote a collaborative dialogue in assessing the feasibility and cost of desired operational capabilities while also considering relevant threat technologies. A related construct is that of the AGORA or library card catalogue that would exist on a classified network as a secure database of AISA information.

PARCA requires an Acquisition Intelligence Support Agreement (AISA) analytic tool to fulfill its BBP 3.0 tasking and integrate information from the Intelligence Community into the acquisition process. This tool would enable the common understanding and exchange of threat information as it relates to lifecycle acquisition program requirements, development, milestones, schedules, and system performance, and it would enable reports to be generated which will inform stakeholders of intelligence transaction requirements, gaps, deliverables, timelines and potential trades. Because meeting the schedule for this AISA tool is critical, PARCA requires the technical services of a company having state-of-the-art technical know-how, in-depth knowledge and experience with the AT&L organization, infrastructure, security requirements and acquisition data business rules to implement the required solution.

Scope The contractor shall build upon the September, 2015, workshop proof of concept with the goal of producing a deployable Version 1. To accomplish this, the contractor shall complete a feature and capability gap review which defines remaining capabilities required for Version 1 and for closing those gaps. The contractor shall additionally work with government hosting and infrastructure teams to complete and execute information assurance steps and to execute a plan to deploy and maintain software. The contractor shall develop authentication and authorization strategies for AISA users on the SIPR network, and it shall finalize integration strategies for DAMIR, threat library integration and other integration points highlighted during the feature and capability gap review. The contractor shall set up, host and maintain a secure development and test environment in support of the AISA tool.

Data Rights: The Government has unlimited rights to all documents/material produced under this contract. All documents and materials 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. OUSD(AT&L)/PARCA Earned Value Management Division data must be stored on the network drives to ensure consistency and review capability for both government and contractor authorized persons.

Information made available to the Contractor by the Government for the performance or administration of this effort shall be used only for those purposes and shall not be used in any other way without the written consent of the Contracting Officer (CO). Contractor and contractor personnel will not divulge or release data or information developed or obtained in performance of this effort, until made public by the Government, except to authorize Government personnel or upon written approval of the COR. The contractor will not use, disclose, or reproduce proprietary data that bears a restrictive legend, other than as required in the performance of this effort. Nothing herein will preclude the use of any data independently acquired by the contractor without such limitations or prohibit an agreement at no cost to the Government between the contractor and the data owner which provides for greater rights to the contractor.

The Contractor agrees to assume responsibility for protecting the confidentiality of Government records, which is not considered public information. Each Contractor or employee of the Contractor to whom information may be made available or disclosed shall be notified in writing by the COR or other Government representative that such information may be disclosed only for purposes and to the extent authorized herein. The Contractor shall not release any information related to this contract to the public, media or other unauthorized persons or organizations unless the Government has conducted the appropriate security review and granted written approval (e.g. posting information to a public website).

Performance of this effort may require the contractor to access and use data and information proprietary to a Government agency or Government contractor which is of such a nature that its dissemination or use, other than in performance of this effort, would be adverse to the interests of the Government and/or others.

Security Clearance Requirements

The contractor shall possess and maintain a SECRET facility clearance from the Defense Security Service (DSS). The Contractor’s employees, performing work in support of this contract shall have been granted a SECRET security clearance from DSS.

Special Qualifications: Contractor personnel shall sign a Non-Disclosure Agreement

Period of Performance The period of performance shall be for six months from date of award.

Deliverables Deliverable Type Due Deliver To Monthly report Word/PDF document 10th working day of following month Task monitor via e-mail

Product roadmap based on requirements gap review

Word/PDF document 30 days post contract award

Task monitor via e-mail

Information Assurance (IA) support documents as defined by government IA team during project execution

Word/PDF document 60 days post contract award -- subject to government IA team task dependencies

Task monitor

AISA software

Source code and executable files

150 days post contract award

Task monitor

User Reference Guide

Word/PDF document 180 days post contract

Task monitor via e-mail

Operations and Maintenance Guide

Word/PDF document 180 days post contract

Task monitor via e-mail

Task Monitor Susan E. Shekmar, CDFM Deputy Director for Operations Performance Assessments and Root Cause Analyses OUSD(AT&L) Pentagon Room 3C889A 571-256-1685