Attachment 8 - SOO 2 AFSOC SUASMAN _23 Mar 11_.pdf

PDF 80 KB Posted

Attached to
SITEC Application Management Services
Solicitation number
H92222-10-R-0046
Issued by

About this file

Atch 8 - SOO 2 AFSOC SUASMAN

View the file

Other files

File Type Posted
Attachment 1 - App Mgt PWS - 25 Mar 2011.pdf PDF
H92222-10-R-0046_Questions_and_Answers 25 Mar 2011.pdf PDF
Attachment 9 - SOO 3 INTEL Trng _23 Mar 11_.pdf PDF
Attachment 13 - App Mgt Q and A _22 Mar 11_.pdf PDF
Attachment 11 - SOO 5 PKI Mgt _23 Mar 11_.pdf PDF
Attachment 10 - SOO 4 NSWC Development _23 Mar11_.pdf PDF
Attachment 7 - SOO 1 160 SOAR App Dev _23 Mar 11_.pdf PDF
H92222-10-R-0046 AMD 0002 Conformed Copy SITEC APP MGT.pdf PDF
Attachment 12 - Application Management SLAs _20110323_.pdf PDF
Attachment 1 - App Mgt PWS - 23 Mar 2011.pdf PDF
H92222-10-R-0046 AMD 0002 Modification SITEC APP MGT.pdf PDF
H92222-10-R-0046 P0001.pdf PDF
Attachment 3 - Value Engineering Program _29 Sep 10_.pdf PDF
Attachment 5 - DD254 Contract Security Classification Spec _24 Feb 11_.pdf PDF
H92222-10-R-0046 App Mgt RFP of 23 Feb 11.pdf PDF
Attachment 4 - Exit Plan _29 Sep 10_.pdf PDF
Attachment 7 - SOO 1 160 SOAR App Dev _24 Feb 11_.pdf PDF
Attachment 6 - Contract Data Requirements List - App Mgt _23 Feb 11_.pdf PDF
Attachment 1 Section C App Mgt PWS _15 Feb 2011_.pdf PDF
Attachment 13 App Mgt Q and A _15 Feb 11_.pdf PDF
Attachment 12 - Application Management SLAs _20110215_.pdf PDF
Attachment 8 - SOO 2 AFSOC SUASMAN _24 Feb 11_.pdf PDF
Attachment 10 - SOO 4 NSWC Development _24 Feb11_.pdf PDF
Attachment 2 - Policy References and Guidance _29 Sep 10_.pdf PDF
Attachment 9 - SOO 3 INTEL Trng _24 Feb 11_.pdf PDF
Attachment 11 - SOO 5 PKI Mgt _24 Feb 11_.pdf PDF
Attachment 2 - Policy References and Guidance _29 Sep 10.pdf PDF
Draft RFP H92222-10-R-0046 App Mgt 29 Sep 10.pdf PDF
Attachment 10 - App Mgt TO 1 SLAs.pdf PDF
Attachment 1 - App Mgt draft SOW - 29 Sep 2010.pdf PDF
Attachment 3 - Value Engineering Program _29 Sep 10_.pdf PDF
Attachment 7 - App Mgt TO 1 SOO.pdf PDF
Attachment 4 - Exit Plan _29 Sep 10.pdf PDF
Attachment 11 - Questions and Answer Format 29 Sep 10.pdf PDF
Show all 34

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

H92222-10-R-0046, 0002 Attachment 8

STATEMENT OF OBJECTIVES FOR EVALUATION

HQ AFSOC/A3OU

1.0 DESCRIPTION OF SERVICES: This task order provides configuration and consultation services for the Air Force Special Operations Command (AFSOC) SOF Unmanned Aircraft Systems (SUAS) mission critical web applications and database operations for Small Unmanned Aircraft Systems Manager (SUASMAN).

2.0 PURPOSE: The SUASMAN web application is designed to provide units that operate Small Unmanned Aircraft Systems (SUAS) the tools required to track systems and related equipment, track operator training requirements and status, track and report usage of SUAS. SUASMAN is essential for USSOCOM and its components to fulfill USSOCOM Directives 350-9 Unmanned Aircraft System (UAS) Training and Standards. The website shall also assist AFSOC with its responsibilities as UAS and UAS airspace lead component tasked by USSOCOM D10-1, AFPD 10-9, and AF approved interim guidance for Small Unmanned Aircraft System (SUAS).

3.0 SPECIFIC REQUIREMENTS. The AFSOC vision is meet all SUAS operator flight hour, training, and currency requirements through a web based application that is accessible worldwide. The application is also intended to support the logistics support requirements of the actual systems through vehicle flight hour tracking, material damage reporting and replacement part ordering. Applications developed under this task will be made available for use by other SOF components. Specifically, the contractor shall:

3.1 Provide software development services for the Air Force Special Operations Command (AFSOC) SUAS Web Application Module. Requirements for these services include development, design, test, maintenance and any related duties of the SUASMAN web application.

3.1.1 Support the sustainment and life cycle upgrade of AFSOC’s SUAS Web Application Module.

3.2 SOF UAS Web Application Module. In support of the development of the SUAS Web Application Module, the Contractor shall continue spiral development of the application and its associated database. The application is intended to support the logging of operational and training flight data; track individual qualifications, currency and produce associated reports; track vehicle flight times, mission status, material status and produce associated reports.

The application shall be used by all Special Operation Forces (all USSOCOM components and Sub Unified Commands) and the U.S. Air Force to support both training and logistics requirements. The application shall be capable of interfacing with current and future UAS ground control stations to facilitate the uploading of flight data.

Additionally, the application shall be capable of future development to interface with a wireless/portable barcode solution to ease inventory control tasks.

3.3 The Contractor shall ensure comprehensive software documentation. At a minimum the Contractor shall develop and maintain a Software Requirements Specification (SRS), Software Design Document (SDD), an Interface Control Document (ICD), and User Documentation. The Contractor shall act as Configuration Control Board (CCB) Secretary during CCB meetings; providing meeting minutes and documenting software change recommendations for government approval.

3.3.1 The Contractor shall provide each of the following deliverables:

3.3.1.1 Operations Module

3.3.1.2 Training Module

3.3.1.3 COA Module

3.3.1.4 Reports Module

3.3.1.5 Logistics Module

3.3.1.6 Other Modules and tasks as approved through the CCB process

3.3.1.7 Software Requirements Specification (SRS)

3.3.1.8 Software Design Document (SDD)

3.3.1.9 Interface Control Document (ICD) as required

3.3.1.10 Deployment Plan

3.3.1.11 Backup and Recovery Plan

3.3.1.12 User’s Guide

3.3.1.13 CCB meeting minutes

3.3.1.14 Summaries of Software Change Requests (SCRs) and documentation of government approved changes

3.3.1.15 Individual training as requested on the operation of the web application

3.3.1.16 Monthly reports document work accomplished and work forecasted for the next month. Monthly reports shall be provided to both AFSOC A3OU and USSOCOM SOKF-J7-T.

3.4 Software Design Document (SSD). The Contractor shall provide a SDD for each spiral of the project development cycle. The SDD shall include the architectures and identify a schedule for each spiral of the project as well as the solution scope, user roles, high level component definition, and logical/physical design.

3.5 Build Solution. The Contractor shall build the solutions designed and specified in the SDD for each spiral as specified in the deployment plan.

4.0 SECURITY REQUIREMENTS.

4.1 Security shall be in accordance with the attached DD254. Contractor team individual(s) supporting this task shall be cleared at the Secret level at the start of this task. Contractors shall require access to NIPRNET/SIPRNET.

At the discretion of the government, selected individuals supporting this Task Order shall require TS/SCI access to Special Access Program (SAP) information. Access to SAP information requires the requisite security clearance based on a security investigation with a date less than 5 years old and requires employees to undergo additional personnel security screening meeting the DoD SAP-accessing directives and policies. Contractor personnel supporting this Task Order may require access to Sensitive Compartmented Information, NATO and Focal Point material in performance of this effort. Contractor shall be authorized to courier classified information up to the “Secret” level in performance of official duties upon approval of and designation by the COR.

4.2 The Contractor shall insure requirements for safeguarding classified information and classified materials, for obtaining and verifying personnel security clearances, for verifying security clearances and indoctrination of visitors, for controlling access to restricted areas, for protecting government property, and for the security of automated and non-automated management information systems and data are fulfilled. The contractor’s management system shall prevent unauthorized disclosure of classified and sensitive unclassified information. The government shall be immediately notified if any security incident or any indication of a potential unauthorized disclosure or compromise of classified or sensitive unclassified information.

4.3 The Contractor shall provide security management support. Typical efforts include, but are not limited to, performing classified document control functions, classified materials inventories, program access requests, preparing and monitoring personnel indoctrination and debriefing agreements, and maintaining and using security-related databases.

5.0 REPORTS. CDRLs 1 – 21 will apply to this task order.

6.0 SERVICE LEVEL AGREEMENTS. SLAs F1 – F4 will apply to this task order.

7.0 MATERIAL. The Government will provide necessary materials to complete this Task Order. The government shall provide necessary office space, for a maximum of four contractor personnel, and facilities for storage.

8.0 PACKAGING, HANDLING, STORAGE, AND TRANSPORT ATION. N/A

9.0 HOURS OF WORK. Normal working hours for on-site coverage shall be 0800-1700, Monday-Friday (excluding holidays).

INSTRUCTIONS TO OFFERORS (ITO)

HQ AFSOC/A3OU

Background: This instruction to offerors gives specific guidance to assist the contractors in the preparation of a proposal against the Statement of Objectives (SOO) for HQ AFSOC/A3OU Task Order under the Special Operations Command Information Technology (SITEC) Application Management contract.

Provided as Attachments to the ITO: SOO, DD 254, SCI (if applicable) and FOUO Addendums

General Information:

Period and Place of Performance: 1 June 2011 – 31 May 2012, with 1, 1-year base option period and 1, 1-year option period. Place of Performance is onsite. The Government anticipates this work to be performed on site at Hurlburt FLD, Florida.

Travel: CONUS travel is anticipated. Based on historical information, annual travel expenditures will be approximately $15K.

Historical Labor Requirements: This requirement was currently being accomplished via EITC Task Orders #895 & 931.

Instructions: All offerors are to submit their task order proposals IAW Section H clause entitled “Ordering Procedures” and section L of the RFP. The following information is provided to assist with this submission:

Proposal: Contract Type: CPFF

Evaluation Statement: The proposal will be evaluated in accordance with the following paragraph and section H6 of the RFP.

Best Value Determination: The Government will evaluate the Task Order Management Plan, Performance Work Statement (PWS), and Task Order Price proposed. Task Order Management and PWS are significantly more important than Task Order Price.

DEPARTMENT OF DEFENSE

CONTRACT SECURITY CLASSIFICATION SPECIFICATION

1. CLEARANCE AND SAFEGUARDING

(The requirements of the DoD Industrial Security Manual apply to all security aspects of this effort.)

a. FACILITY CLEARANCE REQUIRES

SECRET

b. LEVEL OF SAFEGUARDING REQUIRED

None

2. THIS SPECIFICATION IS FOR: (X and complete as applicable)

3. THIS SPECIFICATION IS: (X and complete as applicable)

a. PRIME CONTRACT NUMBER

a. ORIGINAL (Complete date in all cases) Date (YYYYMMDD)

20110701

b. SUBCONTRACT NUMBER

b. REVISED (Supersedes all previous specs)

Revision No. Date (YYYYMMDD)

c. SOLICITATION NUMBER H92222-10-R-0046

DUE DATE (YYYYMMDD)

20110404 c. FINAL (Complete Item 5 in all cases) Date (YYYYMMDD)

4. IS THIS A FOLLOW -ON CONTRACT? YES NO If YES, complete the following

Classified material received or generated under (Preceding Contract Number) is transferred to this follow-on contract

5. IS THIS A FINAL DD FORM 254? YES NO If Yes, complete the following:

In response to the contractor’s request dated , retention of the classified material is authorized for the period of

6. CONTRACTOR (Include Commercial and Government Entity (CAGE) Code)

a. NAME, ADDRESS, AND ZIP CODE

TBD

b. CAGE

CODE

TBD

c. COGNIZANT SECURITY OFFICE (Name, Address, and Zip Code)

TBD

7. SUBCONTRACTOR

a. NAME, ADDRESS, AND ZIP CODE

b. CAGE

CODE

c. COGNIZANT SECURITY OFFICE (Name, Address, and Zip Code)

8. ACTUAL PERFORMANCE

a. LOCATION

HQ AFSOC/A7

427 Cody Ave, Ste 303 Bldg 90332 Hurlburt Field, FL 32544 **Multiple Locations, See Block 13**

b. CAGE

CODE

N/A

c. COGNIZANT SECURITY OFFICE (Name, Address, and Zip Code)

See Block/Item 15 of this form.

9. GENERAL IDENTIFICATION OF THIS PROCUREMENT

Provide App Mgt/Data Management support services to AFSOC A3OU.

Period of Performance: 1 July 2011 to 30 June 2012

10. THIS CONTRACT WILL REQUIRE

ACCESS TO:

YE

S

NO 11. IN PERFORMING THIS CONTRACT, THE

CONTRACTOR WILL:

YES NO

a. COMMUNICATIONS SECURITY (COMSEC)

INFORMATION

a. HAVE ACCESS TO CLASSIFIED INFORMATION ONLY AT ANOTHER

CONTRACTOR’S FACILITY OR A GOVERNMENT ACTIVITY

b. RESTRICTED DATA

b. RECEIVE CLASSIFIED DOCUMENTS ONLY

c. CRITICAL NUCLEAR WEAPON DESIGN

INFORMATION

c. RECEIVE AND GENERATE CLASSIFIED MATERIAL

d. FORMERLY RESTRICTED DATA

d. FABRICATE, MODIFY, OR STORE CLASSIFIED HARDWARE

e. INTELLIGENCE INFORMATION e. PERFORM SERVICES ONLY

(1) Sensitive Compartmented Information (SCI)

f. HAVE ACCESS TO U.S. CLASSIFIED INFORMATION OUT SIDE THE U.S., PUERTO RICO, U.S. POSSESSIONS AND TRUST TERRITORIES

(2) Non-SCI

g. BE AUTHORIZED TO USE THE SERVICES OF DEFENSE TECHNICAL

INFORMATION CENTER (DTIC) OR OTHER SECONDARY

DISTRIBUTION CENTER

f. SPECIAL ACCESS INFORMATION

h. REQUIRE A COMSEC ACCOUNT

g. NATO INFORMATION

i. HAVE TEMPEST REQUIREMENTS

h. FOREIGN GOVERNMENT INFORMATION

j. HAVE OPERATIONS SECURITY (OPSEC) REQUIREMENTS

i. LIMITED DISSEMINATION INFORMATION X

k. BE AUTHORIZED TO USE THE DEFENSE COURIER SERVIC E

j. FOR OFFICIAL USE ONLY INFORMATION WILL BE HANDLED IAW FOUO Addendum l. OTHER (Specify ) NONE x

k. OTHER (Specify) Automated Information Systems NIPRNET and SIPRNET

DD Form 254, DEC 1999 PREVIOUS EDITION IS OBSOLETE

12. PUBLIC RELEASE. Any information (classified or unclassified) pertaining to this contract shall not be released for public dissemination except as provided by the Industrial Security Manual or unless it has been approved for public release by appropriate U.S.

Government authority. Proposed public releases shall be submitted for approval prior to release. Direct Through (Specify)

Public Affairs Office HQ AFSOC/PA Hurlburt Field, FL 32544 Hurlburt Field, FL 32544

To the Directorate for Freedom of Information and Security Review, Office of the Assistant Secretary of Defense (Public Affairs)* for review.

* In the case of non-DoD User Agencies, requests for disclosure shall be submitted to that agency

13. SECURITY GUIDANCE. The security classification guidance needed for this classified effort is identified below. If any difficulty is encountered in applying this guidance, or if any other contributing factor indicates a need for changes in this guidance, the contractor is authorized and encouraged to provide recommended changes. The contractor may also challenge guidance or the classification assigned to any information or material furnished or generated under this contract; and may submit questions for interpretation of the guidance to the official identified below.

Pending final decision, the information involved shall be handled and protected at the highest level of classification assigned or recommended. (Fill in as appropriate for the classified effort.

Attach, or forward under separate correspondence, any documents/guides/extracts referenced herein. Add additional pages as needed to provide complete guidance.)

1. Support USAF organizations will provide security classification guides and other classification guidance to the contractor as required for contract performance. Contractors will comply with all Hurlburt Field, support unit and special program requirements. Supported units will provide security requirements and instructions, and will include contractors in the unit Information Security Program.

2. Classified markings on all working, draft, and final copies of deliverables material shall be in accordance with Executive Order 12958, The Controlled Access Program Coordination Office (CAPCO) guidelines , DOD 5220.22-M, DOD 5200.1R an applicable instructions contained in the respective security classification guides.

3. For on-base contractor, the NISPOM security standards can be satisfied by incorporating AFI 31-401, Information Security Program Management, and AFI 31-601, Industrial Security Program Management, requirements into the Visitor Group Security Agreement.

4. All classified material provided shall be returned by the contractor at contract completion. Individuals are responsible for safeguarding classified information entrusted to them.

5. Use only AF certified AIS for performance on base and will comply with all AF AIS procedures.

Ref Item 8a-c. 27 SOCESE, Cannon AFB NM

14. ADDITIONAL SECURITY REQUIREMENTS. Requirements, in addition to ISM requirements, are established for this contract. YES NO

(If Yes, identify the pertinent contractual clauses in the contract document itself, or provide an appropriate statement, which identifies the additional requirements. Provide a copy of the requirements to the Cognizant Security Office. Use Item 13 if additional space is needed.)

Provide the information, required by the Notification of Government Security Activity clause and Visitor Group Security Agreement Clause, AFFARS 5352.24-9000, to the Servicing Security Activity indicated in Item 13 above. Refer to the contract document for these clauses. The visitor group will operate per DOD 5200.1-R, AFI 31-401, AFI 31-601, Hurlburt Field supplements and unit security program operating instructions, plans d procedures. Se appropriate addendum.

15. INSPECTIONS. Elements of this contract are outside the inspection responsibility of the Cognizant Security Office. YES NO

(If Yes, explain and identify specific areas or elements carved out and the activity responsible for inspections. Use Item 13 if additional space is needed.)

Long term visitor groups will be inspected as part of the supported organizations annual Information Security Program review, conducted by the SSA, while operating on an Air Force Installation. The contractor will comply with the visitor group security agreement pro vided by the USAF Program/Project manager at the performance location. The above does not apply to intelligence, SCI and SAP. See appropriate addendum.

X

16. CERTIFICATION AND SIGNATURE. Security require ments stated herein are complete and adequate for safeguarding the classified information to be released or generated under this classified effort. All questions shall be referred to the official named below.

a. TYPED NAME OF CERTIFYING

OFFICIAL

Gregory J Brauer

b. TITLE J6 Contract Manager

c. TELEPHONE (Include Area Code)

(813) 826-7086

d. ADDRESS (Include Zip Code) 17. REQUIRED DISTRIBUTION

HQ USSOCOM / J65

7701 Tampa Point BLVD MacDill AFB FL 33621-5323

a. CONTRACTOR

b. SUBCONTRACTOR

c. COGNIZANT SECURITY OFFICE FOR PRIME AND SUBCONTRACTOR

e. SIGNATURE D. U.S. ACTIVITY RESPONSIBLE FOR OVERSEAS SECURITY ADMINISTRATION

E. ADMINISTRATIVE CONTRACTING OFFICER

F. OTHERS AS NECESSARY USSOCOM SSO/SAPCO

DD FORM 254 (BACK), DEC 1999

PROTECTING "FOR OFFICIAL USE ONLY" (FOUO) INFORMATI ON

1. GENERAL:

a. The "For Official Use Only" (FOUO) marking is assigned to information at the time of its creation in a DoD

User Agency. It is not authorized as a substitute for a security classification marking but is used on official government information that may be withheld from the public under exemptions 2 through 9 of the Freedom of Information Act (FOI A).

b. Other non-security markings, such as "Limited Official Use" and "Official Use Only" are used by non-DoD

User Agencies for the same type of information and should be safeguarded and handled in accordance with instruction received from such agencies to the extent that such may be withheld from the public under exemptions 2 through 9 of the FOIA and marked in accordance with 2.c below. As used herein, “FOUO” markings shall only be applied to information described in 5 USC § 552(b), and shall also indicate the applicable FOIA Exemption. Contractor shall apply this Attachment 4A in a manner consistent with its policies implementing Section 15 of the Federal Advisory Committee Act, 5 USC App. § 15 (1997).

c. Use of the above markings does not mean that the information cannot be released to the public under FOIA, only that it must be reviewed by the Government prior to its release to determine whether a significant and legitimate government purpose is served by withholding the information or portions of it.

2. MARKINGS:

a. An unclassified document containing FOUO information will be marked "For Official Use Only" at the bottom of the front cover (if any), on the first page, on each page containing FOUO information, on the back page, and on the outside of the back cover (if any). No portion markings will be shown.

b. Within a classified document, an individual page that contains both FOUO and classified information will be marked at the top and bottom with the highest security classification of information appearing on the page. If an individual portion contains FOUO information but no classified information, the portion will be marked, "FOUO."

c. Any "'For Official Use Only" information released to a contractor by a DoD User Agency is required to be marked with the following statement prior to transfer.

“This document contains information EXEMPT FROM MANDATORY DISCLOSURE UNDER THE

FOIA. Exemptions apply.”

d. Removal of the "For Official Use Only" marking can only be accomplished by the originator or other competent authority. When the "For Official Use Only" status is terminated, all known holders will be notified to the extent practical.

3. DISSEMINATION: Contractors may disseminate "For Official Use Only" information to their employees and subcontractors who have a need for the information in connection with a classified contract. Contractors must ensure employees and subcontractors are aware of the special handling instructions detailed below.

4. STORAGE: During working hours, "For Official Use Only" information shall be placed in an out-of-sight location if the work area is accessible to persons who do not have a need for the information. During nonworking hours, the information shall be stored to preclude unauthorized access. Filing such material with other unclassified records in unlocked files or desks, is adequate when internal building security is provided during nonworking hours.

When such internal security control is not exercised, locked buildings or rooms will provide adequate after- hours protection or the material can be stored in locked receptacles such as file cabinets, desks, or bookcases.

5. TRANSMISSION: "For Official Use Only" information may be sent via first-class mail or parcel post. Bulky shipments may be sent by fourth-class mail. DoD components, officials of DoD components, and authorized DoD contractors, consultants, and grantees send FOUO information to each other to conduct official DoD business. Tell recipients the status of such information, and send the material in a way that prevents unauthorized public disclosure. Make sure documents that transmit FOUO material call attention to any FOUO attachments. Normally, you may send FOUO records over facsimile equipment. To prevent unauthorized disclosure, consider attaching special cover sheets, the location of sending and receiving machines, and whether authorized personnel are around to receive FOUO information. FOUO information may be passed to officials in other departments and agencies of the executive and judicial branches to fulfill a government function. Mark the records "For Official Use Only" and tell the recipient the information is exempt from public disclosure under the FOIA and requires special handling.

Electronic transmission of FOUO information, e.g., voice, data or facsimile, and e-mail, shall be by approved secure communications systems or systems utilizing other protective measures such as Public Key Infrastructure (PKI), whenever practical.

6. DISPOSITION: When no longer needed, FOUO information must be shredded.

7. UNAUTHORIZED DISCLOSURE: Unauthorized disclosure of "For Official Use Only" information does not constitute a security violation but the releasing agency should be informed of any unauthorized disclosure. The unauthorized disclosure of FOUO information protected by the Privacy Act may result in criminal sanctions and disciplinary action may be taken against those responsible.

File details come from the government source that posted it. Updated .