FA4452-08-R-0001-0002-ATT1-PWS.pdf

i

Programs & Integration Branch Applications Infrastructure and Systems Support (AISS)

PERFORMANCE WORK STATEMENT

RFP FA4452-08-R-0001

Amendment 0002

Section J, Attachment 1

Prepared by Air Mobility Command (AMC)

Programs & Integration Branch (PIB)

August 28, 2008

Lt Col Scott Borchers

HQ AMC/A6I

ii

Table of Contents

1. INTRODUCTION

1.1 ORGANIZATION: HEADQUARTERS AIR MOBILITY COMMAND

1.1.1 Background

1.1.2 Scope

1.2 PURPOSE/OBJECTIVE

2. TECHNICAL REQUIREMENTS

2.1 PROCESS SUPPORT

2.1.1 Plans and agreements

2.1.2 Reports/White Papers/Briefings

2.1.3 Products, Procedures & Descriptions

2.1.4 Meetings

2.1.5 Technical Proposals

2.1.6 Cost Proposals

2.1.7 Configuration Management

2.1.7.1 Mission Systems CM Support

2.1.7.2 CM Records

2.1.7.3 Contractor CM

2.1.8 Quality Assurance Program

2.1.8.1 Procedures and Practices

2.1.8.2 Reporting

2.1.9 Documentation Support

2.2 ENTERPRISE CAPABILITIES

2.2.1 Capabilities

2.2.1.1 Enterprise Management System

2.2.1.2 Missions Systems Infrastructure

2.2.1.3 Automated Cross Domain Security

2.2.1.4 Computer Based Training

2.2.2 Programmatic and System Architecture Support

2.2.2.1 Programmatic

2.2.2.2 System Architecture

2.2.3 Upgrade and Modernization Support

2.2.3.1 Version Release Lists

2.2.3.2 Analysis support

2.2.3.3 Design

2.2.3.4 Development

2.2.3.5 Testing

2.2.3.6 Enterprise Impact Mitigation

2.2.4 Technical

2.3 ADMINISTRATION AND ENVIRONMENT SUPPORT

2.3.1 Operational Environment Support

2.3.2 Development, Exercise/Experiment, Test, and Training Environments Support

2.3.2.1 Customer Support

2.3.2.2 Planning and Preparation

2.3.2.3 Operation & Maintenance

2.3.3 Security

2.4 MISSIONS SYSTEMS TESTING SUPPORT

2.4.1 Requirements Analysis

2.4.2 Test Planning

2.4.3 Collaborative Testing

2.4.4 Test Execution

2.4.5 No Service Interruption Testing

2.5 FUNCTIONAL AND TECHNICAL TRAINING

2.5.1 Training Development

2.5.2 Training Execution

2.5.3 Training Quality

iii

2.5.3.1 Course Exit Criteria

2.5.3.2 Formal Reviews

2.6 TRANSITION PLAN

2.6.1 Phase-in

2.6.2 Phase-out

2.7 FUTURE NEGOTIATED TASKS

2.7.1 Related Support Services

2.7.2 Exercise/Experimentation Infrastructure Planning and Support

2.8 SERVICE SUMMARY

3. FUNDING

4. REVIEWS AND APPROVALS OF REPORTS, DATA, AND DELIVERABLES

4.1 GENERAL

4.1.1 List of Deliverables

4.1.2 Standard Distribution

4.1.3 Delivery Schedule

4.1.4 Delivery Instructions

4.1.5 Document Management

4.2 INSPECTION, ACCEPTANCE, AND REVIEWS

4.2.1 Government Responsibility

4.2.2 Government Acceptance Time Period

4.2.3 Comprehensive quarterly reviews

5. CONTRACTOR PERSONNEL TRAINING

5.1 TECHNICAL CURRENCY

5.2 CERTIFICATIONS

5.3 SPECIAL TRAINING

6. PERSONNEL REQUIREMENTS

6.1 STAFFING PLAN

6.1.1 Key Position Vacancy

6.1.2 Filling Vacancy

6.2 KEY PERSONNEL

6.2.1 Contractor Program Manager

6.2.2 Contract/Business Manager

6.2.3 Chief Systems Engineer

6.2.4 Chief Quality Assurance Engineer

7. TRAVEL

7.1 TERMS AND CONDITIONS

7.2 AIRFARES

7.2.1 Full Fare Approval

7.2.2 Non-refundable Airfare

7.2.3 Government Refund

8. PRIVACY AND SECURITY

8.1 SECURITY CLEARANCES

8.2 ORGANIZATIONAL CONFLICT OF INTEREST

8.2.1 Identification and Mitigation Plan

8.2.2 Mitigation Plan Revision

8.2.3 Violation Reporting

8.2.4 Waiver Request

8.2.5 Notification of Possible Conflict Restriction

8.3 AMC SECURITY REQUIREMENTS

8.4 ANTITERRORISM LEVEL I TRAINING

iv

8.5 PERSONAL SERVICE

8.6 NON-DISCLOSURE REQUIREMENTS

8.7 SYSTEM REQUIREMENTS

8.8 CERTIFICATION AND ACCREDITATION

9. LIMITATIONS, CONSTRAINTS, CONDITIONS

9.1 ACCESS TO GOVERNMENT FACILITIES

9.2 PROPERTY PROTECTION

9.3 TASKING

9.4 INSPECTION & ACCEPTANCE

9.5 PERFORMANCE MEASUREMENT

9.6 PLACE OF PERFORMANCE

9.7 HOURS OF WORK

9.8 SECTION 508 COMPLIANCE

10. GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, FACILITIES

10.1 GENERAL

10.2 ACCESS

11. SPECIAL INSTRUCTIONS

11.1 APPLICABLE REGULATIONS, SPECIFICATIONS, AND STANDARDS

11.2 OTHER DIRECT COST ITEMS

11.2.1 Overnight Travel

11.2.2 Consumables

11.2.3 Non-Consumables

12. WORK BREAK DOWN STRUCTURE AND PERFORMANCE-BASED MANAGEMENT

13. ADMINISTRATIVE CONSIDERATION

13.1 POINTS OF CONTACT

13.1.1 Contracting Office

13.1.2 Program Office

14. CONTRACT DATA REQUIREMENTS

EXHIBIT A — CONTRACT DATA REQUIREMENTS LISTS

INDEX OF CDRLS

INDEX OF DATA ITEM DESCRIPTIONS

ATTACHMENT I — NOTIONAL DELIVERY SCHEDULE

ATTACHMENT II — CM SPAN OF SUPPORT

This page intentionally left blank.

PERFORMANCE WORK STATEMENT

Applications Infrastructure and Systems Support (AISS)

1. INTRODUCTION

1.1 ORGANIZATION: HEADQUARTERS AIR MOBILITY COMMAND

1.1.1 Background

The Programs and Integration Branch (PIB) will manage the Headquarters Air Mobility Command (HQ AMC) infostructure environment designed to support the information needs of combatant commanders throughout the full spectrum of military operations. The AMC Missions Systems Frameworks will support the Missions Systems operations at all echelons of command and operating locations. The Missions Systems frameworks provide an integrated architecture to support monitoring global situational awareness; assessing operating environments;

formulating potential impacts and alternatives; and enabling decision superiority. It will enable development of optimized air mobility plans created in a collaborative environment resulting in synchronized operations. The users of the Missions Systems Frameworks at all echelons require interoperable, shared access to multi-mission partner domains (e.g. USTRANSCOM, AF, Joint, coalition, civil) information sources in a net-centric environment to enable global situational awareness, planning, execution, and assessment activities in support of joint, allied, and coalition operations. The fusing of information from these multiple sources will enable commanders and decision makers to attain improved global situational awareness to support dynamic C2 of MAF forces.

1.1.2 Scope

The Contractor shall provide Applications Infrastructure and Systems Support (AISS) for programs within the Missions Systems, which currently includes Advanced Computer Flight Plan (ACFP), Airlift Service Industrial Fund Integrated Computer System (ASIFICS), Commercial Operations Integrated System (COINS), Consolidated Air Mobility Planning System (CAMPS), Global Air Transportation Execution System/Worldwide Port Systems (GATES/WPS), Global Command and Control System (GCCS), and Global Decision Support System (GDSS).

This effort will be in the form of technical and support tasks associated with Missions Systems Enclave and Missions Systems Applications support, information assurance, testing support, configuration management, and training under the direction of the PIB. The Contractor will have a direct working relationship with (but no authority over) both the Missions Systems development contractors and operations and maintenance support.

1.2 PURPOSE/OBJECTIVE

The overall purpose of this Performance Work Statement (PWS) is to provide systems and technical support in order to enable AMC to fulfill its global mission.

2. TECHNICAL REQUIREMENTS

2.1 PROCESS SUPPORT

The Contractor shall accomplish the following tasks in the manner and schedule described in this PWS and the contract. In the absence of specific contract requirements, the Contractor shall use software development industry standards and industry best practices. The Contractor shall provide process support and prepare, submit, and maintain the documents as outlined below:

2.1.1 Plans and agreements Data Item Number

2.1.1.1.1 Technical & Management Work Plan (A001)

2.1.1.1.2 Management Plan (A006)

2.1.1.1.3 Continuity of Operations Plan (COOP) (A010)

2.1.1.1.4 Software Development Plan (B001)

2.1.1.1.5 Quality Plan (B012)

2.1.1.1.6 Configuration Management Plan (B013)

2.1.1.1.7 Training Plans (D002)

2.1.1.1.8 Lesson Plans (D003)

2.1.1.1.9 Technology Refresh Plan

2.1.1.1.10 System Services Architecture Plan

2.1.1.1.11 Exercise Support Plan

2.1.1.1.12 Conference/Demo Support Plan

2.1.1.1.13 Memoranda of Agreements

2.1.2 Reports/White Papers/Briefings Data Item Number

2.1.2.1.1 Contractor’s Progress, Status and Management Report (A002)

2.1.2.1.2 Equipment Inventory Record (A008)

2.1.2.1.3 Expenditure Report (A003)

2.1.2.1.4 Agenda and Minutes (A004)

2.1.2.1.5 Monthly Status Report (A007)

2.1.2.1.6 Scientific and Technical Report (A009)

2.1.2.1.7 Integrated Master Schedule (A005)

2.1.2.1.8 Test Report (C001)

2.1.3 Products, Procedures & Descriptions Data Item Number

2.1.3.1.1 Interface Requirements Specification (B002)

2.1.3.1.2 Software Version Description, Version Release List (B006)

2.1.3.1.3 Database Design Description (B004)

2.1.3.1.4 Software Design Description (B005)

2.1.3.1.5 System/Subsystem Design Description (B008)

2.1.3.1.6 Interface Design Description (B003)

2.1.3.1.7 Test Procedures, Plans, and Cases (C002)

2.1.3.1.8 Software Users Manual (B007)

2.1.3.1.9 Engineering Change Proposal (B009)

2.1.3.1.10 Baseline Description Document (B019)

2.1.3.1.11 Baseline Change Requests (B014)

2.1.3.1.12 Software Problem Reports (B018)

2.1.3.1.13 Request for Deviation (B010)

2.1.3.1.14 Computer Software End Items (B011)

2.1.3.1.15 Topology & Connectivity Diagram (B015)

2.1.3.1.16 Facility Drawing (B017)

2.1.4 Meetings

The Contractor shall support the following meetings and processes:

• Program Management Review (PMR)

• CIO Program Review Process (CPRP) preparation

• Accreditation and Security support

• Technical Working Group (TWG) support

• Development Status Review

• Task Management Review (TMR)

• Scheduling meetings

• Support ad hoc teams as directed by the Program Office

The Contractor shall not conduct any meetings, conferences, presentations, whether planned or ad hoc, to discuss any Missions Systems requirements, policies, etc. without first obtaining the permission of this contract’s government lead/POC.

2.1.5 Technical Proposals

The Contractor shall prepare technical proposals as required for future negotiated tasks.

2.1.6 Cost Proposals

The Contractor shall prepare cost proposals as required for future negotiated tasks.

2.1.7 Configuration Management

The Contractor Configuration Manager (CCM) shall support the Missions Systems programs by ensuring a robust CM for all products resulting from the work described within this PWS.

2.1.7.1 Missions Systems CM Support

The CCM implements processes and procedures directed by the Government and assists in implementing software and hardware configuration management procedures and processes, based on current Missions Systems Configuration Management Plans (CMPs), to assure development, test, and production system configurations, as well as providing accurate tracking and reporting of all contract deliverables, materials, and government property.

This support shall include the following (A009):

2.1.7.1.1 The Contractor shall accomplish the following:

• Support existing Missions Systems CMP and CM tools

• Review all existing Missions Systems CMPs and recommend an approach to the SCM for creating a single

Missions Systems CMP

• Review existing CM tool sets and provide a plan for migrating to an enterprise CM tool set. (A009)

2.1.7.1.2 The Contractor shall complete the following tasks in support of the SCM’s CM of Missions Systems:

• Schedule and facilitate configuration control boards (CCBs).

• Ensure proactive CM controls of system and software configurations, software, and document library.

• Assist the SCM in conducting physical configuration audits of delivered products from the Missions Systems and notify the SCM of any noted discrepancies.

• AISS scope of CM responsibilities is illustrated in Attachment II—CM Span of Support.

2.1.7.1.3 The Contractor shall provide local equipment custodial duties in support of the PIB:

• Appoint an equipment custodian (EC) to assist the PIB equipment control officer (ECO) in monitoring, accounting, and tracking each program’s equipment in the local area, and to ensure all equipment transactions are properly recorded in the Government provided database (A008). For this PWS, the local area is designated as local travel in paragraph 7.

• Under the technical direction of the ECO, the Contractor’s EC shall operate and maintain the local Missions Systems equipment storage facility currently located in Bldg 700 and Bldg 1534 on Scott AFB. The operations of this facility consist of storing, in an organized manner, distribution, and disposal of equipment for Scott AFB and the local area.

2.1.7.1.4 The Contractor shall recommend, document, and maintain version release numbers and other unique identifiers in accordance with current practices.

2.1.7.2 CM Records

The Contractor shall prepare and maintain CM records to include a CM library. CM records are documents that record and verify the results of a controlled process associated with the Contractor’s efforts to meet the requirements of the contract. The following are some examples of acceptable CM records:

• Configuration Control Board minutes

• Change records

• Configuration audit reports

• Configuration status accounting records

• Delivery records (Data Transmittal Forms and Certification of Completion/Delivery Data Package)

• Specifications (drawings, parts lists, models, datasets, geometry, etc.)

• Evidence of completion records

• Change incorporation scheduling records

• Management plans (CMP and Data Management Plan)

• Test procedures (C002)

• Variance reports

• Test records

Upon the Government’s request, the Contractor shall provide the required CM records to the Government (or its designee) not later than the next work day. The Contractor shall provide to the 375th Communications Support Squadron (375 CSPTS), or its successor organization, approved updated configuration documents within 5 workdays after receipt of the documents.

The Contractor shall, when requested, assist the Government in maintaining accurate program-wide CM records by providing any or all CM records prepared under this section. In addition, as the listed programs migrate to this contract, all individual program configuration documents shall be collected by the Contractor and deposited in the CM library within 15 workdays of notification by the Government that the Contractor is to collect the particular configuration documents.

2.1.7.3 Contractor CM

The Contractor shall provide, manage, and implement a separate internal configuration management plan (B013) that supports the Contractor’s unique development and support efforts as outlined in this PWS. This plan shall address management and processes to assure control of development, test, training, and enclave system configurations as well as providing accurate tracking and reporting of all contract deliverables, materials, and government property. The Contractor shall ensure their CM proactively controls system and software configurations and provides the proper level of visibility into management, cost control, schedule, and performance for contract deliverables as defined by this PWS. The CCM shall deliver software/system products originated within this PWS to the SCM for physical configuration audits, and shall take positive actions to ensure correction of any discrepancies noted by the SCM.

2.1.8 Quality Assurance Program

The Contractor shall establish and maintain a contract Quality Assurance Program (QAP) according to the following and the instructions provided in B012:

2.1.8.1 Procedures and Practices

In establishing and maintaining a QAP, the Contractor shall plan, develop, and implement procedures and practices to ensure full and consistent compliance with all requirements of the contract.

2.1.8.2 Reporting

The QAP shall be part of the Contractor’s management reporting system during all phases of contract performance.

2.1.9 Documentation Support

The Contractor shall provide documentation support for the Government. The Contractor shall assist in development, coordination, and maintenance of program level agreements/memos with outside agencies for allied support, system connectivity, and enterprise interface and information services including the following:

Service-level Agreements—As required Memorandums of Agreement/Understanding—As required Information Support Plan – As required Project Support Agreements—As required Interface Design/Information Services Documents – As required Other documents as requested

2.2 ENTERPRISE CAPABILITIES

The Contractor shall provide programmatic, architecture, modernization, and technical support for enterprise capabilities that will provide consolidated services and service capabilities to all the Missions Systems. These capabilities presently exist.

2.2.1 Capabilities

Maintenance and development is limited to the following capabilities.

2.2.1.1 Enterprise Management System

The Enterprise Management System (EMS) monitors and proactively manages enterprise-wide mission-critical infrastructure services and equipment, including power, environmental, and support devices. It allows the administrator to resolve problems and performance bottlenecks before they impact enterprise and application services supporting the war-fighter.

2.2.1.2 Missions Systems Infrastructure

The Missions Systems Infrastructure (MSI) is the network, server, and storage capabilities provided to any or all Missions Systems. This includes enterprise system services (such as security, file transfers protocol services, mail services, and print services) as designated by the AMC IT Enterprise Services governance process. NOTE: It does not include information, application, or web services in direct support of information available within a given Missions System.

2.2.1.3 Automated Cross Domain Security

Automated Cross Domain Security (ACDS) is the capability or capabilities required to share information across multiple security domains. ACDS requires integrated solutions/access points from one or more Missions Systems through approved and certified security guards.

2.2.1.4 Computer Based Training

Computer Based Training (CBT) is a collection of computer-assisted instructions to help the operator understand how to use the capabilities of any or all Missions Systems.

2.2.2 Programmatic and System Architecture Support

For each of the capabilities given in 2.2.1, the Contractor shall provide programmatic and system architecture support by accomplishing the following tasks as directed by the Government:

2.2.2.1 Programmatic

2.2.2.1.1 Develop baseline descriptions coinciding with the baseline phases illustrated in Attachment I – Notional Delivery Schedule (B019).

2.2.2.1.2 Develop and update schedules to support all development activities (A005).

2.2.2.1.3 Participate in supporting Air Force, Joint, and federal agency certifications.

2.2.2.1.4 Ensure data and business rules comply with DOD Net-Centricity Strategy and USTRANSCOM’s Distribution Process.

2.2.2.1.5 Develop prototypes as proof of concepts.

2.2.2.2 System Architecture

2.2.2.2.1 Define and document system upgrades to the Missions Systems environment.

2.2.2.2.2 Participate in developing and validating architecture products.

2.2.3 Upgrade and Modernization Support

For each of the capabilities given in 2.2.1, the Contractor shall publish a Software Development Plan tailored to its development processes for Government approval (B001). The following subtasks are associated with and define the typical development activities.

2.2.3.1 Version Release Lists

Provide a specific list of requirements necessary to modify, expand, or correct operation of these capabilities by accomplishing the following tasks:

2.2.3.1.1 Based on guidance from the Government and in coordination with stakeholders, analyze, plan, and recommend system requirements and timing for the insertion of new technology via Version Release List (VRL) and baseline description (A009, B006, B019).

2.2.3.1.2 Prepare formal Change Requests containing descriptions and specifications of recommended technological requirements or enhancements, to include scope, details, and system interfacing requirements (B014).

2.2.3.1.3 Prepare or include, where appropriate and with Government approval, Problem Reports (B018) to correct noted deficiencies from previous releases.

2.2.3.1.4 Project a schedule for each VRL within a time period agreed to by the Government.

2.2.3.1.5 Develop a cost projection for incorporating each VRL into the appropriate Missions System (to include development, testing, and fielding) and present to the Government for approval.

2.2.3.2 Analysis support

Provide analysis support by accomplishing the following tasks (A009):

2.2.3.2.1 Prepare functional and technical use cases for each software and hardware requirement.

2.2.3.2.2 When requested by the Government, prepare and analyze functional and technical use cases, and propose (when necessary) refinements to (but not limited to) the same, and submit Change Requests (B014) or Problem Reports (B018) in accordance with business practices, processes, procedures, systems, and performance measures, and provide recommended changes to VRLs.

2.2.3.2.3 Analyze, define, and recommend system(s) enhancements, to include scope, details, interfaces, and timing of the technical insertions. This activity requires working and coordinating with all stakeholders (e.g. Government, FFDRC, government contractors, to include hardware suppliers and third party application developers) (B009, B014).

2.2.3.2.4 For other than CBT, evaluate and recommend fixed and deployable network topologies and connectivity within existing Mobility C2, Transportation, and Air Operations family of systems to include Local Area Networks (LANs), Wide Area Network (WANs), broadband transceivers, satellite communications, communications processor systems, and related systems (B015).

2.2.3.2.5 Conduct Joint Application Development (JAD) sessions when requested by the Government for refinement of requirements; provide minutes from all sessions with any proposed changes to business practices, processes, procedures, systems, performance measures, or changes to CBT approach or content with respect to same. No further action is to be taken from a JAD session without written approval from the Government or designated representative.

2.2.3.2.6 Based on analysis, provide or recommend modifications to the test pass/fail criteria for each VRL requirement for insertion into the VRL and Enterprise test and evaluation plans.

2.2.3.3 Design

Design and document system/software/services to meet requirements by completing the following tasks (B002, B003, B004, B005, B006, B007, and B008):

2.2.3.3.1 Design system/software/services to meet specifications and descriptions approved by the Government for each VRL item approved under paragraph 2.2.3.1 and analyzed under paragraph 2.2.3.2

2.2.3.3.2 Design system architecture to include all information flows and all applicable business rules. (B009)

2.2.3.3.3 For other than CBT, design Logical Data Model and Physical Data Model (LDM/PDM) products in accordance with AMC A6I Pamphlet 33-1 and USTRANSCOM Data Management Handbook, or as directed by the Government.

2.2.3.3.4 Conduct functional and technical design reviews with Government or designated representatives using prepared design products to obtain approvals of direction and decisions.

2.2.3.4 Development

Develop from designs accepted by the Government under paragraph 2.2.3.3 by completing the following tasks:

2.2.3.4.1 Develop, test, and document solutions, including refinement of business rules that do not interfere with currently fielded Government-accepted software (i.e., No Service Interruption).

2.2.3.4.2 For other than CBT, develop Logical Data Model and Physical Data Model (LDM/PDM) products in accordance with AMC A6I Pamphlet 33-1 and USTRANSCOM Data Management Handbook, or as directed by the Government.

2.2.3.4.3 Conduct design and technical reviews with Government or designated representatives to ensure the software solution meets design specifications and is ready for testing.

2.2.3.4.4 Conduct security scans to ensure software configuration complies with DoD security standards.

2.2.3.5 Testing

Conduct the following testing tasks to ensure developed solutions meet requirements:

2.2.3.5.1 For other than CBT, prepare test procedures (C002). For CBT, produce and maintain a Master Test Plan, to include all applicable test cases and test descriptions (C001, C002).

2.2.3.5.2 Prepare test pass/fail criteria for each VRL requirement.

2.2.3.5.3 Perform development testing (e.g. unit, system, interoperability, regression, security, and performance) to ensure the baseline meets the VRL specifications and does not interfere with currently fielded Government-accepted software.

2.2.3.5.4 Provide to the Government all testing artifacts (e.g. simulators, models, and data) required to complete all government acceptance testing.

2.2.3.5.5 Prepare and deliver test reports for each release to include summary of test results, including all required components and documentation.

2.2.3.5.6 During internal testing, allow Government representative to collaborate with developer test members to help determine if the software development is suitable to advance to the next phase in the development life cycle.

2.2.3.5.7 Perform government acceptance testing, with direct Government oversight, to demonstrate developed solutions meet criteria as identified in the VRL.

2.2.3.5.8 Participate with the Government to complete and document any DoD, Joint, Air Force or other governing body certification and accreditation testing for all security classification domains.

2.2.3.6 Enterprise Impact Mitigation

Support the enterprise by ensuring that the software or hardware does not adversely affect the intended operational environment, by accomplishing the following tasks:

2.2.3.6.1 Prepare and deliver the configuration of the intended system (B015).

2.2.3.6.2 Ensure and demonstrate that the software is integrated into the intended system configuration.

2.2.3.6.3 Provide applicable training for key technical, functional, help desk, training, and testing personnel, both Government and Contractor, designated by the Government for each release (D002).

2.2.3.6.4 For CBT, prepare plans, coordinate, and execute the installation and fielding of the Government-accepted CBT baseline.

2.2.4 Technical

Provide technical support to all Missions Systems by accomplishing the following tasks:

2.2.4.1.1 For other than CBT, provide 24/7, federal holidays included, on-call Level III technical support of the fielded systems. For CBT, provide Level III technical support upon request from the government.

2.2.4.1.2 Prepare plans, coordinate, and execute installation and fielding of the delivered baselines, hot fixes, and upgrades. Coordinate all installation and fielding activities with the 375 CSPTS (or its successor organization).

2.2.4.1.3 Maintain existing hardware and software baseline definitions and ensure that the 375 CSPTS (or its successor organization) and its contractor(s) have the current baseline definitions. For other than CBT, deliver within 5 workdays after receiving the approval of the new baseline (B019).

2.2.4.1.4 Monitor and update Remedy Trouble Ticket System.

2.2.4.1.5 When requested, assist the 375 CSPTS (or its successor organization) and its contractor(s) in troubleshooting those capabilities identified in paragraph 2.2.1 and related performance concerns.

2.2.4.1.6 Coordinate all system problem and outage resolutions with appropriate agencies and/or action offices.

2.2.4.1.7 The Contractor shall provide a quarterly rolling 18-month technical refresh analysis, which includes future hardware and software changes, and projected impacts to the Missions Systems applications.(A009)

2.3 ADMINISTRATION AND ENVIRONMENT SUPPORT

The Contractor shall provide infrastructure support for the operational, development, training, and test environments, as described below.

2.3.1 Operational Environment Support

The Contractor shall provide Missions Systems operational environment and infrastructure support (for all designated security classifications) by accomplishing the following tasks within Air Force, USTRANSCOM, and DoD Net Centric Environment standards.

2.3.1.1.1 Provide Level III engineering support for production environment and infrastructure.

2.3.1.1.2 Prepare or modify architectural drawings (e.g. network and facilities/allied support) to support each planned version release (B015, B017).

2.3.1.1.3 Field hardware and software infrastructure baseline definitions of approved configurations.

2.3.1.1.4 Implement, test, and monitor the No Service Interruption (NSI) solution(s) for all hardware and software infrastructure releases and fieldings.

2.3.1.1.5 Recommend and assist in the analysis of production performance metrics.

2.3.1.1.6 Update and maintain the Continuity of Operations Plan (COOP) and environment (A010).

2.3.1.1.7 Support COOP exercises.

2.3.2 Development, Exercise/Experiment, Test, and Training Environments Support The Contractor shall provide infrastructure support for the Enterprise Capabilities and Missions Systems training, exercise/experiment, development, and testing environments by accomplishing the following tasks within Air Force, USTRANSCOM, and DoD Net Centric Environment standards:

2.3.2.1 Customer Support

2.3.2.1.1 Establish standardized services for all customers and ensure optimal service performance for systems users.

2.3.2.1.2 Provide all levels of technical support for development, exercise/experiment, training, and testing environments.

2.3.2.2 Planning and Preparation

2.3.2.2.1 In accordance with the Integrated Master Schedule (A005), the Contractor shall prepare and coordinate supported environments and schedules, and ensure sufficient resources are planned and deconflicted.

2.3.2.2.2 Ensure VRL requirements are incorporated in the supported environments.

2.3.2.2.3 Assess performance of new hardware and software in conjunction with stakeholders in preparation for operational fielding determination.

2.3.2.3 Operation & Maintenance

2.3.2.3.1 Provide administration of all supported Government environments using government-provided tools.

2.3.2.3.2 Monitor and maintain system backups and backup libraries.

2.3.2.3.3 Maintain configuration control of all aspects of the supported environments in accordance with the CMP, including performing administrative support duties for the supported environments CCB.

2.3.2.3.4 Prepare or modify architectural drawings (e.g. network and facilities/allied support) to support the supported environments (B015, B017).

2.3.2.3.5 Maintain, upgrade, or refresh the supported environments, as approved by the CCB.

2.3.3 Security

The Contractor shall perform Information Assurance (IA) activities for Enterprise Capabilities and Missions Systems environments in accordance with government policies and procedures by accomplishing the following tasks (A009):

2.3.3.1.1 Acknowledge, evaluate, and provide course of action ensuring compliance with Information Assurance Vulnerability Alert (IAVA) and Time Compliance Network Orders (TCNO) and other security vulnerability assessments.

2.3.3.1.2 Perform and support all actions in coordination with all stakeholders to ensure that the Missions Systems comply with Air Force and DoD Information Assurance Certification and Accreditation Process (DIACAP) regulations, procedures, and processes.

2.3.3.1.3 Implement IAVA and TCNO mitigating strategies for systems unable to reach compliance within allotted timeframe as appropriate. For systems unable to meet IAVA and/or TCNO compliance within allotted time, develop an extension request in accordance with AFI 33-138.

2.3.3.1.4 Ensure Missions Systems infrastructures comply with government-mandated identity management policies, e.g., Public Key Infrastructure (PKI) and biometrics.

2.3.3.1.5 Recommend course of action for system and network security architecture changes to mitigate identified vulnerabilities.

2.3.3.1.6 Develop, coordinate with the Government, and maintain the following documents for all Missions Systems:

• Authority to Operate (ATO), Authority to Connect (ATC) requests

• Special network approval requests

• Requests to operate on DoD and non-DoD enterprise networks

• Requests for Joint Interoperability to Test Command (JITC) certification

• Cross-domain solution requests

• Schedule inputs (A005)

• Other related documents, when required

2.3.3.1.7 Coordinate and support security assessments conducted by the Government.

2.4 MISSIONS SYSTEMS TESTING SUPPORT

The Contractor shall perform testing (collaborative, technical, security, functional, and interoperability) in support of the continuous operation of the fixed and deployed Missions Systems, and shall participate with the Government stakeholders to complete and document any DoD, Joint, Air Force, or other governing body certification or accreditation testing for all security classification domains. The Contractor shall coordinate and schedule with the Government for appropriate government oversight of the overall test function.

2.4.1 Requirements Analysis

The Contractor shall provide requirements analysis by accomplishing the following tasks:

2.4.1.1.1 Review requirements and any available use cases to ensure requirements assigned to a VRL are clearly defined for testing purposes and that those requirements are quantifiable and testable.

2.4.1.1.2 Document, implement, and maintain a process to exploit automated test management.

2.4.1.1.3 Update, and maintain existing test databases (containing test descriptions) with the goal of consolidation.

2.4.2 Test Planning

The Contractor shall conduct Missions Systems test planning by accomplishing the following tasks (C002):

2.4.2.1.1 Prepare a Master Test Plan (MTP) and a test procedure for each test incident to support functional, environment, and infrastructure services testing; and to support JITC Certification in multiple security domains.

2.4.2.1.2 Support, as directed by the PIB, out-of-cycle test requirements that are levied by external sources, systems, or agencies.

2.4.2.1.3 Where applicable, prepare additional Test Plans (TPs) as needed to validate any unique or out-of-cycle requirements that are not identified in the MTP.

2.4.2.1.4 Validate entrance and exit criteria for each test to include pass/fail criteria for each VRL requirement.

2.4.2.1.5 Collaborate with developers to construct test descriptions/cases to ensure each test description/case validates the criteria established in the MTP.

2.4.2.1.6 Provide and maintain schedules to conduct testing, and incorporate into the Integrated Master Schedule (A005).

2.4.3 Collaborative Testing

2.4.3.1.1 Develop a strategy and Memorandum of Agreement (MOA) with developers to plan and execute collaborative testing at the Government or developer’s facilities, and submit the MOA for Government approval.

2.4.3.1.2 Document the collaborative testing requirements in each applicable schedule (A005).

2.4.3.1.3 Provide status reports to the Government as required.

2.4.3.1.4 On a weekly basis, update, collaborative testing schedules with actual progress, and incorporate into the Integrated Master Schedule (A005).

2.4.4 Test Execution

The Contractor shall execute testing to validate requirements by completing the following tasks:

2.4.4.1.1 Conduct Test Readiness Reviews.

2.4.4.1.2 Perform functional, regression, and interoperability testing according to the approved TP.

2.4.4.1.3 Track and report problems identified during testing using government-provided tools.

2.4.4.1.4 Facilitate and document the review of problem reports for resolution with the functional and development communities. Provide in-progress testing status as required.

2.4.4.1.5 Publish test reports (C001).

2.4.4.1.6 Update testing schedules with actual progress and incorporate into the Integrated Master Schedule (A005).

2.4.5 No Service Interruption Testing

The Contractor shall coordinate NSI testing with all stakeholders for the Missions Systems environment to ensure no disruption to operational service as releases are fielded by accomplishing the following tasks:

2.4.5.1.1 Coordinate the planning, analysis, design, testing, and implementation for each Missions Systems NSI requirement.

2.4.5.1.2 Conduct testing and performance analysis activities across the Missions Systems to validate and ensure there is no service interruption during their deployment.

2.4.5.1.3 Ensure all NSI activities are scheduled and updated in the Integrated Master Schedule (A005).

2.5 FUNCTIONAL AND TECHNICAL TRAINING

This task provides training to the functional and technical help desks, technical support, testers, and field units as required and approved by the Government. This task applies to all AISS programs, with the exception of Global Air Transportation Execution System/Worldwide Port Systems (GATES/WPS) and Global Command and Control System (GCCS). As training tasks for GATES/WPS and GCCS become known in the future, they will be addressed as Future Negotiated Tasks (see paragraph 2.7). Computer based training should be the predominant form of training. This task requires the Contractor to develop, maintain, and update current training materials, and is intended to address the need to train trainers from fielded units.

2.5.1 Training Development

The Contractor shall plan and conduct functional, technical, and end-user training, accomplishing the following tasks as appropriate (D001, D002):

2.5.1.1.1 Analyze enhancements as identified in VRLs for learning opportunities.

2.5.1.1.2 Plan, organize, and coordinate training courses.

2.5.1.1.3 Develop, identify enhancements to, update, and maintain all course materials, including but not limited to:

lesson plans, student texts, handbooks, and CBTs (D003).

2.5.1.1.4 Develop CBT and/or classroom courses and schedule all training development to support the Missions Systems.

2.5.2 Training Execution

2.5.2.1.1 Distribute training media as planned and coordinated with the Government.

2.5.2.1.2 Provide training to students/operators who are located throughout the world, as directed by the Government.

2.5.2.1.3 Periodically assess training effectiveness, obtain contingency/operational expertise, and provide just-in-time training at Missions Systems-equipped units.

2.5.3 Training Quality

The Contractor shall perform the following tasks to ensure training quality.

2.5.3.1 Course Exit Criteria

After the completion of each course, the Contractor shall accomplish the following tasks:

2.5.3.1.1 Solicit student and community feedback/assessment on training effectiveness.

2.5.3.1.2 For any classroom training, obtain written course assessment via a test covering key learning objectives of the course and a course survey from each student taking the course.

2.5.3.1.3 Provide a summary of the student course assessment and copies of all course surveys (A009).

2.5.3.1.4 Maintain a lessons learned file to be used for training course improvement.

2.5.3.2 Formal Reviews

As required by the Missions Systems, the Contractor shall support the following review activities.

2.5.3.2.1 Support Curriculum Review Boards when required.

2.5.3.2.2 Participate in Instructional System Design reviews as described in AMC Instruction 36-2207 and AMWC 01 36-108.

2.6 TRANSITION

2.6.1 Phase-in

The Contractor, in accordance with its phase-in plan, shall implement the phase-in strategy, schedule, and method of assuming responsibility for tasks described in this PWS.

The Contractor shall accomplish the following phase-in transition tasks:

2.6.1.1.1 Execute its phase-in strategy and schedule as described in the management plan. (A006)

2.6.1.1.2 Provide transition status reports when requested by the Government.

2.6.1.1.3 Implement the proposed methods, processes, procedures, and tools as described in the approved plan.

2.6.1.1.4 Assume technical support responsibilities.

2.6.1.1.5 Assume development responsibilities.

2.6.1.1.6 Assume testing and training responsibilities.

2.6.2 Phase-out

The Contractor shall provide and implement the Government-approved phase-out plan, being sure to:

• describe the method of transferring responsibility for tasks described in this PWS;

• provide recurring status briefings to the Government and associate contractors throughout the transition period; and

• cooperate fully with the Government and any successor Contractor(s) to ensure an orderly transition at the end of this contract.

The Contractor shall accomplish the following phase-out tasks:

2.6.2.1.1 Preserve and make available to the Contracting Officer, if requested, copies of all records and other documentation developed or acquired under this contract or preceding contracts for this effort, regarding performance of the work required by this contract.

2.6.2.1.2 Make available to the Contracting Officer, upon request, the names, job titles, and duties of all employees who have worked under this contract.

2.6.2.1.3 Permit current employees to be interviewed for possible employment by a successor Contractor.

2.6.2.1.4 Provide, as requested, an orientation for successor Contractor employees.

The Contractor shall supply to the Government 15 days prior to the completion of the contract, unless requested earlier by the Government, the following information:

• complete backup of all contract and contract-related data stored on each employee’s hard drive, along with any global data;

• list of all government furnished equipment and commercial off-the-shelf software utilized in support of this task;

• soft and hard copies of all procedures and training materials developed as part of this task; and a

• complete list of badges, site access, vehicle passes, and Government system access (e.g., ABSS, CRIS, etc.)

by individuals currently on the task, along with their physical location, full expense fund report, pending actions, and contract status.

The Contractor must ensure that no contract data is corrupted, changed, or altered such that it would cause damage to the Government.

Performance of phase-out activities will be implemented under a task order issued against resultant contract.

2.7 FUTURE NEGOTIATED TASKS

2.7.1 Related Support Services

In addition to the tasks specifically set forth in this PWS, the Contractor shall provide related support services when directed and authorized in advance by the Contracting Officer as requirements materialize, including Global Air Transportation Execution System/Worldwide Port Systems (GATES/WPS) and Global Command and Control System (GCCS) Functional and Technical Training requirements. The task order will describe additional efforts in support of Missions Systems. Tasks may include, but are not limited to, support for the requirements, architecture, design, development, performance, white papers, and prototypes of the advanced technology initiatives; technical meetings; support to transition efforts; maintenance of a project management plan; future documentation; and future document management requirements.

2.7.2 Exercise/Experimentation Infrastructure Planning and Support Exercise and experimentation infrastructure planning and support will be handled as Future Tasks. The Contractor shall provide Missions Systems environment and application infrastructure support by accomplishing the following tasks within Air Force, USTRANSCOM, and DoD Net Centric Environment standards and checklists:

2.7.2.1.1 Attend technical planning and coordination meetings/conferences as directed.

2.7.2.1.2 Identify any unique program support required to fulfill exercise/experiment objectives.

2.7.2.1.3 Provide engineering and/or technical support for exercise/experiment environments and connectivity to other environments.

2.7.2.1.4 Prepare exercise/experiment environments, as necessary.

2.7.2.1.5 Prepare or modify architectural drawings (e.g. network and facilities/allied support) to support the exercise/experiment environments (B015, B017).

2.7.2.1.6 Recommend, maintain, upgrade, and refresh the exercise/experiment environment, as approved.

2.7.2.1.7 Provide CM duties as described in paragraph 2.1.7.

2.7.2.1.8 Provide systems administration.

2.7.2.1.9 Track the hours and related expenses associated with these exercises and provide this information for Government use concurrent with monthly invoices.

Note, exercise/experiment locations may vary; travel may be required.

2.8 SERVICE SUMMARY

Contractor performance will be evaluated against the following standards:

Performance Objective Tasks Performance Threshold Technical Expertise 2.1, 2.2, 2.3, 2.4, 2.5, 2.6, 2.7

The Contractor shall provide level of expertise, coordination, and support necessary to accomplish the contract in a responsive, satisfactory, and timely manner. The Government shall receive no more than one customer complaint per month in performance of required tasks, and all complaints shall be resolved not later than one working day beyond the agreed-to time period.

Responsiveness to Noted Deficiencies 2.1, 2.2, 2.3, 2.4, 2.5, 2.6, 2.7

The Contractor shall establish a corrective action program that precludes the Government from having to follow-up with the Contractor in order to ensure correction of a noted deficiency. All deficiencies shall be corrected not later than one working day beyond the agreed-to time period.

Interface 2.1, 2.2, 2.3, 2.4, 2.5, 2.6, 2.7, 8.2

The contract objective is, within the normal work day, to respond to the program office’s request for contractor support. The Contractor shall ensure that all Organizational Conflict of Interest (OCI) and information access concerns are resolved promptly. The Contractor shall provide initial notice of all unresolved issues within one day from the time the Contractor management is aware of the issue and provide update on status on the Contractor handling of OCI.

Technical Writing and Reports 2.1, 2.2, 2.3, 2.4, 2.5, 2.6, 2.7

All data deliverables shall be produced using prescribed formats, software tools and software versions as agreed to by the Government. All deliverables shall meet professional standards for technical writing and the requirements set forth in the contract. All deliverables shall not have more than two inaccuracies for cross-referencing source and reference material content. All deliverables shall clearly identify assumptions and personal opinions. Technical writing and reports shall be delivered to the Government by the agreed to schedule or in accordance with the terms of the contract with no more than two deliverables per month not being delivered on time. Late deliverables shall be submitted not later than one working day beyond the agreed-to time period

Briefs, Point/Talking Papers, e-mails, and Staff Summary Sheets

2.1, 2.2, 2.3, 2.4, 2.5, 2.6, 2.7

All deliverables shall be produced using prescribed formats, software tools and software versions agreed to by the Government. All deliverables shall conform to the tools and templates in the

Performance Objective Tasks Performance Threshold AMC Action Officers Guide and standard business practices. All deliverables shall not have more than one inaccuracy. All deliverables shall be in accordance with an agreed schedule or in accordance with the terms of the contract with no more than two deliverables per month not being delivered on time. Late deliverables shall be submitted not later than one working day beyond the agreed-to time period.

Meeting Schedule 2.1, 2.2, 2.3, 2.4, 2.5, 2.6, 2.7

All schedules shall be published in the Project Server database; and updated weekly, with no more than one deliverable per month not being delivered or updated on time. Late deliverables and updates shall be submitted not later than one working day beyond the agreed-to time period.

Technical On-call Support 2.2.4.1.1 Upon notification of on-call support request, the Contractor shall begin actions within one hour of notification 98% of the time, and within two hours, 100% of the time.

3. FUNDING

Funding will be provided in each individual task order.

4. REVIEWS AND APPROVALS OF REPORTS, DATA, AND

DELIVERABLES

4.1 GENERAL

Documents and deliverables described in this PWS and amendments or modifications shall be submitted in a professional manner and on the prime Contractor’s letterhead.

4.1.1 List of Deliverables

Data deliverables utilized during the performance of this contract are listed in Exhibit A — Contract Data Requirements Lists (CDRLs).

4.1.2 Standard Distribution

The Contractor will produce all deliverables in Contractor-recommended software tools/versions, as approved by the Government. All test materials, documents, notes, models, records, and software produced by the Contractor under this PWS shall become the property of the Government, which shall have unlimited rights to all materials and determine the scope of publication and distribution. The Contractor shall be required to deliver printed and electronic copies of all documents, notes, records, and software to the Government upon termination of the contract services or expiration of the contract period. To the fullest extent possible, the Contractor shall use processes that take full advantage of electronic storage, distribution, and manipulation of information.

4.1.3 Delivery Schedule

Delivery specifications, technical reports, and any other data shall be IAW the CDRLs. Delivery schedules for other deliverables not specifically addressed, e.g., special reports, white papers, etc., shall be agreed to by the Contractor and the program office.

4.1.4 Delivery Instructions

All deliverables shall be delivered to the Government no later than the date specified in the CDRL. Deliverables other than those required to be submitted with the proposal are to be uploaded into a Contractor-provided automated deliverable management system and tracked using Microsoft Project, as directed by the Government. Those deliverables that are to be provided outside the automated system must be transmitted to HQ AMC/A6IM, Bldg.

1700, 3rd floor, Scott Air Force Base, IL 62225-5523. The Contractor shall use Microsoft-compatible software, e.g., Microsoft Office Suite. Electronic deliverables in the form of e-mail or CD are acceptable.

4.1.5 Document Management

The Contractor shall ensure proper control and coordination of all documents generated to fulfill the requirements of this contract, such that all data deliverables are on time, fulfilling routine requests for published documents within one working day, and urgent requests for published documents within 4 hours.

4.2 INSPECTION, ACCEPTANCE, AND REVIEWS

4.2.1 Government Responsibility

Inspection, acceptance, and reviews of all work (deliverables) performed by the Contractor will be by PIB…