ATCH_1_Performance_Work_Statement_(PWS)_Basic.pdf

PERFORMANCE WORK STATEMENT (PWS)

FOR

Nuclear Data Evaluation Services (NDES) III

Air Force Technical Application Center

January 28, 2019

1 Table of Contents

1 DESCRIPTION OF SERVICES

1.1 INTRODUCTION

1.2 BACKGROUND

1.3 SCOPE

1.4 PERIOD OF PERFORMANCE

2 SPECIFIC TASKS

2.1 MAINTENANCE AND SUPPORT TO TRACKMAN APPLICATION

2.2 MAINTENANCE AND SUPPORT TO DASSLE SYSTEM

2.3 MAINTENANCE AND SUPPORT TO WORKFLOW SYSTEM

2.4 MAINTENANCE AND SUPPORT TO OTHER IT SYSTEMS

2.5 STIG (SECURITY TECHNICAL IMPLEMENTATION GUIDE) REQUIREMENTS

3 SERVICES SUMMARY (SS)

4 GOVERNMENT FURNISHED PROPERTY AND SERVICES

4.1 SERVICES

4.2 FACILITIES

4.3 UTILITIES

4.4 EQUIPMENT

4.5 MATERIALS

4.6 INFORMATION

5 GENERAL INFORMATION

5.1 CONTRACTOR IDENTIFICATION IN THE GOVERNMENT WORKPLACE

5.2 INDUSTRIAL SECURITY

5.3 PHYSICAL SECURITY

5.4 LOCATION(S) OF WORK

5.5 SAFETY REQUIREMENTS

5.6 CONTRACTOR PERSONNEL TRAINING

5.7 RECORDS

5.8 CONTRACTOR MANPOWER REPORTING

5.9 SPECIAL TRAINING, CERTIFICATIONS AND QUALIFICATIONS…………..……….13

5.10 KICK-OFF MEETING AND PERIODIC PROGRESS MEETINGS

5.11 CONTRACTOR TRAVEL. ............................................................................................ …133

5.12 TRANSITION PERIOD

5.13 DELIVERABLES

APPENDIX A - ACRONYMS AND ABBREVIATIONS LIST

APPENDIX B - ESTIMATED ANNUAL WORKLOAD DATA

APPENDIX C – GOVERNMENT FURNISHED EQUIPMENT/INFORMATION

SECTION 2

1 DESCRIPTION OF SERVICES.

1.1 Introduction.

This is a non-personal services contract. The Government will neither supervise contractor employees nor control the method by which the contractor performs the required tasks. The Contractor shall manage its employees and guard against any actions that are of the nature of personal services, or give the perception of personal services. The Contractor shall notify the Contracting Officer (CO) immediately if they perceive any actions constitute personal services.

These services shall not be used to perform any Inherently Governmental Functions.

1.2 Background.

The 24th Analysis Squadron Nuclear Sciences Flight (24ANN), part of the Air Force Technical Application Center (AFTAC) 709th Surveillance and Analysis Group (709SAG), contracts with multiple laboratories to perform analysis of samples and uses the results to create reports.

During previous contracts, mostly recently Nuclear Data Evaluation Services, NDES, a suite of software and hardware systems were developed to manage sample logistics and analytical information. The systems developed under previous NDES contract include the Trackman application, Data Acquisition System Lab Extraction (DASSLE), and Workflow. These items are described in more detail below as part of the overall 24ANN process.

The overall process begins when 24ANN receives a sample and creates a new project in the database using the Trackman tool. As 24ANN processes the sample they use Trackman as a virtual lab notebook and load basic sample processing information into the 24ANN database through Trackman. After samples are processed by AFTAC, they are sent to a network of contracted labs where samples are processed through multiple analytical techniques. The labs then load this information in the Data Acquisition System Lab Extraction (DASSLE) system.

DASSLE transfers the data through a series of steps to a server at AFTAC where the information is stored on the 24ANN database. This database can be accessed by Workflow and Trackman for displaying and visualizing data. Evaluators use tools in both these programs to visualize data and write reports. Once a report is written and approved, the report is loaded into Trackman and the project is closed. The report and information associated with the report is part of a library which is searchable using Workflow and other tools. The report and other documents associated with the project are stored on shared drives managed by AFTAC.

The NDES system manages four (4) primary elements: DASSLE, Trackman, Workflow and the 24ANN database.

Element Description Associated Software & Hardware

Trackman

Interfacing tool to 24ANN database to record and view files and information associated with a sample

Software (Visual Basic)

DASSLE

System which transfers data from the labs to AFTAC’s system

Software (XML, JAVA, Oracle SOA Suite, Oracle

Business Intelligence, Oracle Data Integrator, Oracle Web

Portal, Oracle WebLogic, PLSQL), Solaris UNIX

Servers

Workflow A report writing tool that displays and charts particle data

Software (Java, PLSQL, XML, Fortran)

24ANN Database Database which stores 24ANN data

Oracle 11g Enterprise Edition Release 11.2

Trackman: Trackman is 24ANN’s software tool that interfaces users to the 24ANN’s database and various directories. This allows users and data managers to save and access documents related to projects and some basic information from the database. The software acts as a virtual notebook, allowing users to track, put in sample descriptions and save photo documentation from sample processing.

DASSLE: DASSLE is a hardware and software system that allows 24ANN’s contracted analysis labs to upload sample information from their labs to secure Government servers.

Analysis data generated at the labs is loaded onto a secure webpage and converted to XML where it is submitted to an Oracle server. The data is then uploaded to another Oracle database through AFTAC specialized software. The data is then posted for use in the Workflow and Trackman tools.

Workflow: Workflow is a software interfacing tool that accesses 24ANN’s database and allows users to view data, display data in various graphical forms and search the sample collection.

Workflow provides graphical user interface to users for running nuclear reactor models and advanced algorithms in Java, C++ and FORTRAN.

1.3 Scope.

The Contractor shall maintain the hardware and software systems associated with 24th Analysis Squadron Nuclear Sciences Flight (24ANN) data management system. Services shall include but are not limited to the maintenance of Data Acquisition System Services Lab Extract (DASSLE) system, Trackman, and Workflow. The contractor shall also assist 24ANN interfacing between existing tools/database and modernization efforts which may consist of different tool applications.

1.4 Period of Performance.

The performance period is one year base with four option years.

2 SPECIFIC TASKS.

2.1 Maintenance and Support to Trackman Application.

2.1.1 The Contractor shall maintain the software code associated with the Trackman application.

2.1.2 The Contractor shall ensure Trackman is properly interfaced with the Oracle database to ensure data from Trackman is correctly entered into the database and Trackman displays accurate information from the database.

2.1.3 The Contractor shall ensure Trackman is properly interfaced with modernization efforts which may include new tool applications.

2.1.4 The Contractor shall ensure Trackman meets the requirements of AFTAC guidance TM 10-01. Government will provide to the contractor when required.

2.1.5 The Contractor shall support the install and troubleshooting of Trackman software on analysts’ operating systems

2.2 Maintenance and Support to DASSLE System.

2.2.1 The Contractor shall maintain all aspects of the DASSLE Enterprise Lab Extraction (ELE system). This includes:

2.2.1.1 The Contractor shall maintain the website the AFTAC's contract labs use to input their data into the 24ANN database. This shall include making modifications to input fields used to enter data, ensuring webpage functionality and its ability to properly transmit and save data.

2.2.1.2 The Contractor shall maintain the Oracle database which receives the data from the labs.

The Contractor shall perform quality assurance checks and modifications on the data to ensure the data is accurate and properly stored.

2.2.1.3 The Contractor shall check to ensure all data received and entered into the DASSLE ELE system is transmitted to the ATAC secure servers.

2.2.1.4 The Contractor shall identify and report all data rejected from the ELE and AFTAC secure servers. The Contractor shall notify the contract Contracting Officer’s Representative (COR) of the data rejection and provide support to the Government in correcting the situation.

2.2.1.5 The Contractor shall maintain the DASSLE ELE system under the requirement set forth in AFTAC guidance TM 10-01 and other official guidance provided by the Government.

2.2.2 The contractor shall maintain all aspects of the DASSLE on AFTAC secure network.

This shall include:

2.2.2.1 The Contractor shall ensure data transmitted from DASSLE ELE is complete and accurately captured on the AFTAC secure network database.

2.2.2.2 The Contractor shall ensure data saved on the AFTAC secure network database is properly formatted for size optimization and is available for SQL query.

2.2.2.3 The Contractor shall maintain the AFTAC secure network DASSLE system under the requirement set forth in AFTAC guidance TM 10-01 and other official guidance provided by the Government.

2.2.3 The Contractor shall ensure DASSLE is properly interfaced with modernization efforts which may include new tool applications.

2.3 Maintenance and Support to Workflow System.

2.3.1 The Contractor shall maintain current functionality of workflow. This shall enable the analyst to easily search and display analytical information from a project or series of projects. (Example data, searching techniques, and displays can be provided upon request)

2.3.2 The Contractor shall build wrappers for reactor modeling code and other code developed by third party companies written in languages such as FOTRAN, Java, or C++ for use in Workflow.

2.3.3 The Contractor shall assess the accuracy and completeness of the data transferred from the 24ANN database to workflow. The Contractor shall report all deviations to the Government and provide support in resolving the issue. The Contractor shall report these deviations as soon as possible (ASAP) to the NDES COR through email, telephone, or in-person.

2.3.4 The Contractor shall ensure Workflow is properly interfaced with modernization efforts which may include new tool applications.

2.4 Maintenance and Support to Other IT Systems

2.4.1 In the case the Government changes their data management system away from Trackman, DASSLE, or Workflow, the Contractor shall support the Government in the transition and support new lab data management software. New systems may leverage COTS Software packages such as SAS, Mathematica, MatLab, new versions of Oracle and others. These systems may use a combination of operating systems to include Windows, UNIX, Linux and others.

2.4.2 The Contractor shall update and modify the 24ANN database to support visualization of data in Google Earth or other Geo-locating software.

2.4.3 The Contractor shall support special projects and Research and Development (R&D) requests by extracting requested portions of the database for use in other software programs and for approved customers.

2.4.4 The Contractor shall support other AFTAC information technology operations and maintenance IT O&M efforts to include database maintenance and upgrades, graphical user interface (GUI) development, and computer modeling efforts.

2.5 STIG (Security Technical Implementation Guide) Requirements

2.5.1 All STIG compliance shall be applied to the relative environment.

2.5.2 All system vulnerabilities shall be resolved or mitigated to the fullest extent possible, regardless of requirement category; CAT I, CAT II and CAT III requirements shall be met. Any requirements with unresolved vulnerabilities shall have a documented Plan of Action Milestones (POAM).

2.5.3 All compliance shall be in accordance with the most recent STIG version found on the Information Assurance Support Environment website on the unclassified internet.

2.5.4 All in-progress STIG checklists and vulnerability scans shall be submitted with the monthly report.

2.5.5 Any system-specific standard operating procedures, system configuration guidance and user configuration guidance shall be incorporated into the monthly report.

2.5.6 The contractor shall meet the intent of the STIG in their own environment.

2.5.7 The contractor shall direct all STIG questions to the 24ANS ISSO and the AFTAC ISSM office.

SECTION 3

3 SERVICES SUMMARY (SS).

The contract service requirements are summarized in performance objectives that relate directly to mission essential items. The performance threshold briefly describes the minimally acceptable levels of service required for each requirement. The Services Summary (SS) provides information on contract requirements and the expected level of Contractor performance to be successful. These thresholds are critical to mission success. Procedures as set forth in the applicable Inspection clause in the contract will be used to remedy all deficiencies. The Government retains the right to inspect any item included in the contract.

Performance Objective

PWS PARA

Performance Threshold

SS # 1.

The Contractor shall maintain and support the Trackman application.

2.1 The Trackman application shall operate with full

functionality, during normal duty hours, 95% of the time or greater. This will be accessed on a monthly basis.

SS # 2

The Contractor shall maintain and provide support to the DASSLE system.

2.2

The DASSLE system shall be fully functional 90% of the time or greater. This will be accessed on a monthly basis. All system malfunctions shall be resolved within 48 hours of identification.

SS # 3

The Contractor shall maintain and provide support to the Workflow application.

2.3 The Workflow application shall operate with full

functionality, during normal duty hours, 95% of the time or greater. This will be accessed on a monthly basis.

SECTION 4

4 GOVERNMENT FURNISHED PROPERTY AND SERVICES.

4.1 Services.

The Government will meet with the Contractor to demonstrate software functionality, explanation of official guidance, and other areas to acquaint the Contractor with 24ANN data management systems.

4.2 Facilities.

The Government will provide up to two (2) workstations at AFTAC with telephone and NIPR and AFTAC secure network access.

4.3 Utilities.

The Government will not provide any direct utility support.

4.4 Equipment.

The Government will provide servers, personal computers, executables, software and database code listed in table in Appendix C.

4.5 Materials.

The Government will not provide any additional material outside of items listed in Appendix C

4.6 Information.

The Government will provide software and database code listed in table in Appendix C.

SECTION 5

5 GENERAL INFORMATION.

5.1 Contractor Identification in the Government Workplace.

When conversing with Government personnel during business meetings, over the telephone or via electronic mail, the Contractor shall identify themselves as such to avoid situations arising where sensitive topics might be better discussed solely between Government employees. The Contractor shall identify themselves on any attendance sheet or any coordination documents they may review.

Electronic mail signature blocks shall identify their company affiliation.

5.2 Industrial Security.

5.2.1 DD Form 254. Overarching security requirements and Contractor access to classified information shall be as specified in the DD Form 254, Department of Defense Security Classification attached to the contract. The Contractor shall have a final U.S.

Government issued TOP SECRET (TS//SCI) security clearance and be DCID 6/4 eligible with a current Single Scope Background Investigation (SSBI) upon award of contract.

5.3 Physical Security.

The Contractor shall safeguard all Government property provided for contractor use. At the close of each work period, Government facilities, property, and materials shall be secured.

5.3.1 Key Control. The Contractor shall establish and implement methods of ensuring that all badges issued to the contractor by the Government are not lost or misplaced and are not used by unauthorized persons.

5.3.2 The Contractor shall immediately report the occurrences of a lost or duplicate badges to the COR.

5.3.3 The Contractor shall prohibit the use of badges issued by the Government by any persons other than the contractor’s employees. The Contractor shall prohibit the opening of locked areas by Contractor employees to permit entrance of persons other than Contractor’s employees engaged in the performance of assigned work in those areas, or personnel authorized entrance by the COR.

5.3.4 Combinations and Codes. The Contractor shall establish and implement methods to ensure all combinations and codes are not revealed to unauthorized persons. The Contractor shall ensure lock combinations are changed when personnel having access to the combinations no longer have a need to know such combinations.

5.3.5 Access lock combinations are “For Official Use Only” and shall be protected from unauthorized personnel.

5.3.6 Combinations to security containers, secure rooms, or vaults are classified information and shall be properly safeguarded. Only the Contractor employees with proper security clearance and need-to-know will be given combinations to security containers, secure rooms, or vaults.

5.3.7 Security alarm access codes shall be protected from unauthorized personnel. Security alarm access codes will be given to Contractor employees who require entry into areas with security alarms. The Contractor shall properly safeguard alarm access codes to prevent unauthorized disclosure.

5.4 Location(s) of Work.

The work to be performed under this contract shall be performed at Government, Contractor facilities, and facilities designated as Contractor work locations. In all cases the Contractor shall ensure all required security procedures are being implemented and maintained.

Contractor Secure Facility: The contractor shall house the 24ANN server data in an existing and certified TS Sensitive Compartmented Information Facility (SCIF) within a two (2) hour traveling distance to AFTAC (Approximately 120 miles). The SCIF shall be able to store data at the Top Secret/Sensitive Compartmented Information (TS/SCI) level.

5.5 Safety Requirements.

In performing work under this contract, the Contractor shall:

5.5.1 Conform to the safety requirements contained in the contract for all activities related to the accomplishment of the work.

5.5.2 Take such additional immediate precautions as the CO may reasonably require for safety and mishap prevention purposes.

5.5.3 Record and report promptly (within one hour) to the CO or COR, all available facts relating to each instance of damage to Government property or injury to either contractor or Government personnel.

5.5.4 In the event of an accident/mishap, take reasonable and prudent action to establish control of the accident/mishap scene, prevent further damage to persons or property, and preserve evidence until released by the accident/mishap investigative authority through the CO.

5.5.5 If the Government elects to conduct an investigation of the accident/mishap, the Contractor shall cooperate fully and support Government personnel conducting the investigation.

5.6 Contractor Personnel Training.

The Government will provide all training required for access to AFTAC and for use of its network. The Government will provide informal training to illustrate the functions and features of Trackman, DASSLE, and Workflow.

5.7 Records.

Records management oversight of a contractor’s records is necessary to ensure Air Force records keeping requirements are met. All records created as a result of processes prescribed in this PWS and resulting contract shall be maintained in accordance with Air Force Manual 33-363, Management of

Records, Air Force Instruction (AFI) 33-364, Records Disposition-Procedures and Responsibilities, the Air Force Electronic Records Management Solution, AFTAC’s supplements to each of the fore mentioned publications, and are disposed of in accordance with the Air Force Records Disposition Schedule. At the conclusion and termination of this contract, all records shall be returned to the AFTAC Office of Primary Responsibility (OPR) for proper disposition. Contractors who create and receive official records on behalf of the Air Force and are performing records management support are referred to as records professionals. Contractor records professionals shall be appointed in writing to the AFTAC Records Manager and shall meet the training and performance requirements identified in AFI 33-322, Records Management Program and applicable AFTAC supplement. Contact the AFTAC Records Manager for specific guidance and procedures.

5.8 Contractor Manpower Reporting.

The below information is for informational purposes only and shall not be initiated by the contractor without written direction from the Contracting Officer:

5.8.1 Overview. In accordance with Section 8108 of the National Defense Appropriations Act of Fiscal Year 2011 the contractor shall report, annually, for performing services on Department of Defense installations in support of this contract, all required prime contract and subcontract data, or require any subcontractors to report separately using the Enterprise-wide Contractor Manpower Reporting Application (eCRMA) located at http://www.ecmra.mil. There are four separate eCMRA tools: Army, Air Force, Navy and All Other Defense Components. The appropriate eCMRA reporting tool to use is determined by the requiring activity being supported (e.g., if DISA awards a contract for an Air Force requiring activity, the contractor shall load the required reporting data in the “Department of Air Force CMRA” tool). The contractor shall report ALL contractor direct labor hours and direct labor dollars (including subcontractor labor hours) required for performance of services provided under this contract. The contractor is only responsible for entering the Order, Contact, and Location Data. The contractor may view user manuals and frequently asked questions (FAQs) at https://cmra.army.mil/Help/help.html.

5.8.2 Initial Contract/Order Creation. The contractor shall enter initial data (Order and Contact Data only) into the appropriate eCMRA tool to establish the basic contract record no later than 30 calendar days after receipt of contract award. The contractor shall notify the COR and the CO when the basic contract record has been established in the appropriate eCMRA tool.

5.8.3 Annual Reporting. Reporting inputs will be for the direct labor executed during the period of performance (PoP) for each Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October of each calendar year. The contractor shall provide reporting inputs for the final PoP of this contract no later than 30 calendar days after contract expiration. The contractor may direct technical questions about the eCMRA tool to the CMRA help desk at dodcmra@pentagon.af.mil.

5.8.4 Uses and Safeguarding of Information. Information from the secure website is considered to be proprietary in nature when the contract number and contractor identity are associated with the direct labor hours and direct labor dollars. At no time will any http://www.ecmra.mil/ https://cmra.army.mil/Help/help.html mailto:dodcmra@pentagon.af.mil data be released to the public with the contractor name and contract number associated with the data.

5.9 Special Training, Certifications and Qualifications.

The Contractor shall provide expertise in the following software systems and languages: Visual Basic, C++, HTML, XML, JAVA, Oracle SOA Suite, Oracle Business Intelligence, Oracle Data Integrator, Oracle Web Portal, Oracle WebLogic, SQL, PLSQL, SQL Developer, TOAD for Oracle, Fortran, Oracle 11g Enterprise Edition Release 11.2, and Oracle 12, Solaris UNIX Servers, UNIX/LINUX, Application servers (Apache, Oracle), Microsoft Windows and Microsoft Office, SAS, Mathematica and Matlab. The Contractor shall also have IAW DoD 8570 certification requirements.

5.10 Kick-off Meeting and Periodic Progress Meetings.

The Contractor shall attend a contract kick-off meeting, or teleconference, five days after contract award. The Contracting Officer (CO), COR, and other Government personnel, as appropriate, may meet periodically with the contractor to review the Contractor's performance.

At these meetings the CO will apprise the Contractor of how the Government views the Contractor's performance and the Contractor shall apprise the Government of problems, if any, being experienced. The Contractor shall take the appropriate action to resolve all outstanding issues.

5.11 Contractor Travel.

All travel requirements (including destination, purpose, plans, agenda, itinerary, number and names of personnel, and dates) shall be pre-approved by the COR. Contractor shall submit a trip report upon completion of travel. Costs for travel shall be billed on a strictly cost reimbursable basis in accordance with (IAW), the regulatory implementation of Public Law 99-234, Federal Acquisition Regulations (FAR) subpart 31.205-46 entitled Travel Costs and the limitation of funds specified in this contract.

The Contractor shall, upon request, accompany and support AFTAC personnel in meetings with other Government and commercial agencies in support of AFTAC missions. This shall include current analysis processes and capabilities and future capabilities that may be developed. The Government estimates this requests will not occur more than one (1) time per year total for the contract.

The Contractor shall travel to Patrick Air Force Base, building 10989, AFTAC within 24 hours of a request to support emergency IT issues or high priority data loading events. The Government estimates this requests will be no more than three (3) times per year.

5.12 Transition Period.

In the event the incumbent is not the successful contractor for the follow-on contract award, the incumbent contractor hereby agrees to cooperate with the successor and to allow the successor to conduct on-site interviews with its employees. If said employees are agreeable to the change and are accepted by the successor, then the incumbent contractor shall release them at a mutually acceptable date. Further, the contractor shall turn over to the successor contractor all administrative records and technical data acquired or formulated during the life of this contract.

5.12.1 The incumbent contractor’s own work shall carefully fit into the successor contractor’s phase-in schedule. The incumbent contractor shall not commit or permit any act which will interfere with the performance of work by the successor contractor or by the Government. The incumbent contractor shall take reasonable steps to aid in the transition of the successor’s work force into the environment, on a non-interference basis with the incumbent contractor’s responsibilities.

5.12.2 On a non-interference basis the successor shall be allowed to observe all activities which occur during the phase-in period. These activities shall include as a minimum over-the-shoulder observance of daily activities and other requests mutually agreed to by the involved parties.

5.13 Deliverables.

Reports and other data required in this Performance Work Statement (PWS) shall be submitted IAW the Contract Data Requirements List (CDRL) in Exhibit A of the contract.

CDRLs Data Item Number Data Item Description

PWS

Para. Delivery Schedule

A001 DI-

MGMT-

80368A

Program Status Report

2.1, 2.2, 2.3

Shall be provided within ten

(10) calendar days of the preceding month

A002 DI-MGMT

81468

Contract Funds Status Report

2.1, 2.2, 2.3

Shall be provided within ten

(10) calendar days of the preceding month

A003 DI-MGMT

81505

Meeting Minutes Report 2.1, 2.2, 2.3

Shall be provided within ten

(10) calendar days after the meeting

A004 DI-

MGMT-

80508A

Technical Report Study 2.1, 2.2, 2.3

Shall be provided within fifteen (15) business days of request.

A005 DI –

MGMT-

80508A

Software Requirements Specification Report

2.1, 2.2, 2.3

Shall be provided within fifteen (15) business days of request.

APPENDICES

A. Acronyms and Abbreviations List

B. Estimated Workload Data

C. Government Furnished Equipment (GFE)

APPENDIX A - ACRONYMS AND ABBREVIATIONS LIST

Acronym/Abbreviation Definition

AF Air Force

AFB Air Force Base

AFTAC Air Force Technical Application Center

CDRL Contract Data Requirements List

CFR Code Federal Regulation

CO Contracting Officer

COR Contracting Officer’s Representative

DASSLE Data Acquisition System Lab Extraction

DOD Department of Defense

ELE Enterprise Lab Extraction

FAR Federal Acquisition Regulation

FOUO For Official Use Only

GFE Government Furnished Equipment

GUI Graphical User Interface

IAW In accordance with

IDIQ Indefinite Delivery/Indefinite Quantity

IT Information Technology

24ANN 24th Analysis Squadron Nuclear Sciences Flight

NDA Non-Disclosure Agreement

NDES Nuclear Sciences Data Evaluation Services

O&M Operations and Maintenance

OSHA Occupational Safety and Health Act

PBSA Performance Based Service Acquisition

PWS Performance Work Statement

R&D Research and Development

SCIF Sensitive Compartmented Information Facility

SS Services Summary

SSBI Single Scope Background Investigation

STIG Security Technical Implementation Guide

TS/SCI TOP SECRET/SENSITVE COMPARTMENTED

INFORMATION

USAF United States Air Force

APPENDIX B - ESTIMATED ANNUAL WORKLOAD DATA

The historical workload data provided is for informational use only and is based upon historical data. Contractors shall propose based on their own technical approach.

ITEM

NAME

ESTIMATED ANNUAL

WORKLOAD

1 Program Manager 400

2 Software Engineer – Senior 2500

3 Database Engineer 300

5 Administrative Assistant 240

APPENDIX C – GOVERNMENT FURNISHED EQUIPMENT/INFORMATION

The Government will provide up to two (2) workstations at AFTAC for Contractor use with NIPR and secure network access and telephone service. The Government will also provide the following items.

Item Description QNTY

24 Dell Ultrasharp Monitor 2

Dell Precision Tower 3620 XCTO Base 2

DASSLE Source Code 1

Trackman Source Code 1

Workflow Source Code 1