Performance Work Statement.pdf

PERFORMANCE-BASED WORK

STATEMENT (PWS)

FOR

SYSTEMS ENGINEERING, SOFTWARE TEST ENGINEERING AND TECHNICAL

DOCUMENTATION SERVICES FOR THE 520th SMXS SOFTWARE MAINTENANCE

SQUADRON COMMAND AND CONTROL SYSTEM – CONSOLIDATED (CCS-C)

PROGRAM

520th SMXS

26 May 2010

Revision 29 December 22, 2010

PERFORMANCE-BASED WORK STATEMENT

TABLE OF CONTENTS

SECTION PAGE

1 DESCRIPTION OF SERVICES 3

2 SERVICES SUMMARY 5

3 GOVERNMENT FURNISHED PROPERTY AND SERVICES 6

4 GENERAL INFORMATION 6

5 APPENDICES 9

DESCRIPTION OF SERVICES

This Performance-Based Work Statement (PWS) outlines the tasks required of the Contractor in support of the 520th SMXS Software Maintenance Squadron’s Command and Control System -

Consolidated (CCS-C) program. The purpose of this effort is to contract for Systems

Engineering, Software Test Engineering and Technical Documentation services within the 520 th

SMXS Division to complete the required tasks. The Library Documentation Set will become the property of the federal government. The Contractor shall provide Systems Engineering, Software Test Engineering and Technical Documentation services for the tasking of creating a bidder’s library documentation set. The contractor shall work in integrated teams with

Government engineers and managers located in Colorado Springs, Schriever AFB, CO.

1. BASIC SERVICES

1.1. Provides Systems Engineering, Software Test Engineering and Technical

Documentation services.

1.1.1. Systems Engineering – The contractor shall perform requirements management and be responsible for creating Software Requirement Specifications (SRS) and Use Cases organized by subsystem, derived from the System and Sub-System Design Document (SSDD) and

System/Subsystem Specification (SSS), and SSDD for the Telemetry and Commanding (T & C) subsystem development. The contractor shall examine the “high-level view” of the system and create the corresponding requirements which will provide the necessary definition and traceability to allow completion of the software development. The contractor shall collaborate with the technical program manager to help further define the customer requirements; create subsystem and detailed requirements where gaps exist; shall communicate requirements to software developers, Test Engineers and CDL (Contractor Development Laboratory) developers and administrators by the creation of Software Design Change Requests (SDCRs), SSDDs, Interface Design Descriptions (IDDs) and Interface Requirements Specification (IRS). The contractor shall be using the software requirements management product DOORS to manage the requirements and work with OO-ALC so that the repositories in COS (Colorado Springs) are synchronized with the OO-ALC.

1.1.2 Software Test Engineering – The contractor shall develop, write and edit CCS-C Test documentation that verifies or validates Installation Packages. The contractor shall use the processes of both the 3 SOPS and 4 SOPS customers and make appropriate recommendations on process to improve the quality of the products delivered. The contractor shall develop automated test processes and software for CCS-C, within the CDL and/or CTF (CCSC-C Test Facility) to simulate both normal and anomaly based operational scenarios of the Satellite Operation Center

(SOC). The contractor shall identify problems with the CCS-C by developing an automated mechanism to record test results that will be uploaded into a database for reporting purposes. The contractor shall show traceability from the developed test procedures to the customer, based on defined requirements.

1.1.3 Technical Documentation - The contractor shall develop, write, and edit CCS-C documentation and follow processes defined by the OO-ALC. The contractor will adhere to current documentation standards, the OO-ALC Configuration Management Plan (CMP) as noted in Appendix D. The contractor shall breakdown technical content into user friendly step-by-step instructions and documentation.

1.2 Communicates with government personnel and organizations. The contractor shall keep government management informed of problems and risks that could impact the mission or organization as discussed in the weekly meeting. Cooperates and coordinates with others within the assigned organization, and functions well as a member of a project or government product team.

1.3 Follows processes, policies, regulations, and procedures.

The contractor shall accomplish the following:

1.3.1 Understands and follows a process specified for each assigned project that are consistent with a CMMI Level 3 Software organization.

http://www.sei.cmu.edu/library/abstracts/books/0321279670.cfm

1.3.2 Informs government management, through the reporting system, of process improvements, that could enhance the end product, to ensure the customer is given the highest quality product, at the lowest cost, in the shortest amount of time.

1.3.3 Follows time accounting procedures specified by the technical program manager, entering time accurately and when scheduled into the government time and accounting system (TAS).

1.4 Contractor Travel: The Contractor shall be required to travel to various bases, in accordance with (IAW) the Joint Federal Regulations (JFR), during the performance of this contract. This travel will be to perform investigations and data gathering, test hardware and software in labs, conduct DTs and OTs, and validate technical data and TOs. The allowable baseline for airfare cost is the “lowest priced airfare available to the contractor as outlined in

FAR 31.205-46(b) & (c). All travel requires Government approval/authorization and notification to the applicable TPM.

For purposes of this PWS, the following table shows an estimated travel schedule which may be required for each contractor personnel.

Destination No. Persons No. Trips No. Days/Trip

Los Angeles AFB, CA 2 2 5

Hill AFB, UT 2 5 25 days total each for life of contract

Vandenberg AFB, CA 2 1 5

1. 5 Reports. The Contractor shall provide a monthly statement, for each applicable line item on the contract, to the Quality Assurance Personnel (QAP).

http://www.sei.cmu.edu/library/abstracts/books/0321279670.cfm

1.5.1 Monthly Financial Report. The contractor shall prepare and submit a monthly financial report via email to the 520th Software Maintenance Squadron Technical Program Manager. The monthly statement shall be in a required format provided to the contractor by the QAP and shall identify the contract as it relates to, the specific line item, travel costs, the total amount of funds used for the month, and funds remaining. The monthly financial report shall include the total funded and funds expended in travel for the month, cumulative for the contract and funds remaining. The contractor shall submit this report broken out per CLIN and Project to the 520th

Software Maintenance Squadron TPM’s and Quality Assurance Personnel (QAP) within 15 days after the end of each month for the previous month’s work. Monthly reports/invoices should be submitted in compliance with contractual status.

1.5.2 Monthly Status Report. The contractor personnel shall provide monthly status reports that summarize the actions that occurred during the time period. The contractor shall submit a project planning chart detailing the project tasks and schedule. The reports will be reviewed in the approved format by the 520th Software Maintenance Squadron Technical Program Managers or other 520th Software Maintenance Squadron Flight Chiefs or Leads as assigned. The contractor shall submit this report to the 520th Software Maintenance Squadron TPM’s and

Quality Assurance Personnel (QAP) in accordance with Contract Data Reports List (CDRL)

A001. Monthly status report includes:

Progress of the previous month

Status of task

Issues/concerns and associated recommendations (any risks that would cause a change in schedule or cost, associated recommendations to mitigate the issue)

Lessons learned during the month

1.5.3 Trip Report. The Contractor (all contracted personnel) shall provide a trip report covering each travel assignment via MS Word electronic or contractor format (either is acceptable) to the TPM or designated government representative (Configuration Management –

CM) (CDRL A002). The trip report shall be:

required within 10 working days of the completion of the travel assignment.

Reviewed and approved by the TPM or government representative.

Required to include the following:

Goals

Itinerary

Accomplishments

Discussions

Conclusions

Recommendations

Minutes for any meeting attended

1.6 SPECIAL REQUIREMENTS

None.

2. SERVICES SUMMARY

Performance Objective PWS

Para

Performance Threshold

Contractor personnel shall accomplish

System/Subsystem Design Description

(SSDD) for the Telemetry and Commanding

(T&C) subsystem development.

1.1.1 One time requirement draft due by 8 months

after Contract Final, due 11 months upon government acceptance - CDRL A004.

Contractor shall accomplish Supplemental

Descriptions (IDDs) where required during the development and discovery of the T&C

SSDD.

1.1.1 One time requirement draft due by 8 months

Contract Final due 11 months upon government acceptance – CDRL A005.

Contractor personnel shall accomplish requirements management by creating

System Requirement Specifications (SRSs) as an optional delivery.

1.1.1 Upon completion of the SSDD and IDD the

SRS for the T&C subsystem due at the 12 months after Contract Final, upon government acceptance – CDRL A006.

The Contractor shall provide a monthly

Financial statement, for each applicable line item on the contract, to the Quality

Assurance Personnel (QAP). The monthly statement shall be provided by the 15 th day of the next month and will be archived in a configuration management system.

1.5.1 Reports provided by the 15

th day of the next month with no internal information errors –

CDRL A003

The Contractor shall provide a monthly status report, for each applicable line item on the contract, to the Quality Assurance

Personnel (QAP). The monthly statement shall be provided by the 15 th day of the next month and will be archived in a configuration management system.

1.5.2 Reports provided by the 15

th day of the next month with no internal information errors –

CDRL A001

The Contractor shall provide a Trip Report when travel is required

1.5.3 Reports provided 10 business days upon

return to Permanent Station – CDRL A002

3. GOVERNMENT FURNISHED PROPERTY AND SERVICES.

3.1 Shared Property of the Government, shall remain at all times Property of the Government. In accordance with Government procedures, the Contractor is authorized to share Property of the

Government, without cost, with Government personnel, in Government facilities, at Hill AFB

UT or Schriever AFB CO, for the duration of this contract, and only as needed for the performance of this contract. The Government maintains accountability for this Shared Property of the Government. This Shared Property of the Government is not considered Government

Furnished Property (GFP) requiring property administration IAW FAR Parts 45 and 52.245 plus supplements. The Government Organization that is accountable for this Shared Property of the

Government is also responsible for its Disposition.

3.2 The Government will provide the Contractor with workspace as required while performing work on site and reasonable access to information and data systems necessary to accomplish the requirements of this PWS. The Contractor will be provided access to the necessary facilities, equipment, and property as required for this specific contract.

4. GENERAL INFORMATION.

4.1 Security Requirements. The Contractor shall be required to obtain security clearance and controlled area badges for all of their employees. The CCS-C Program deals with classified data and information. The contractor will insure that all personnel will obtain a minimum of secret clearance. The contract administrator will provide a DD Form 254 at award of the contract.

4.1.1 The contract administrator shall complete a "Request for Identification Credential (AFMC

Form 496)" for each employee of the contractor requiring access to Hill AFB. The requests shall be submitted to Pass and Registration (South or West Gate Visitors Center).

4.1.2 The security manager shall complete an “Unescorted Entry Authorization Certificate” (AF

Form 2586) for each employee requiring entry into controlled areas. The request shall be submitted to Pass and Registration (Gates Visitor Center).

4.1.3 Personnel providing service under the basic contract shall be required to currently have the

DoD 8570.1-M certifications, as shown in the following table on the first day of performance on this contract:

4.2. Badge/Common Access Card (CAC) Information/Unescorted Entry Authorization.

Contractor personnel shall comply with the following:

4.2.1 Peterson AFB and Schriever AFB. Access will be coordinated through the TPM and the th

Security manager.

4.2.2 Common Access Card (CAC). For a Common Access Card (CAC) Complete the DD

Form 1172 for Contractor Personnel and submit to the Security Manager for the organization.

4.2.3 Vindicator Card. If needed, the contractor employee shall also obtain a Building ID and access card (vindicator card) from the appropriate Building Security Manager.

IAT LEVEL I IAT LEVEL II IAT LEVEL III

A+, Net+ or Security + Security+ CISA or

SSCP acceptable GSEC acceptable CISSP or

TICSA acceptable SCNP acceptable GSE or

SSCP acceptable SCNA

IAM LEVEL I IAM LEVEL II IAM LEVEL III

GISF GSLC GSLC

GSLC CISM CISM

Security+ CISSP CISSP

4.2.4 Return of Access Cards. When the period of performance is complete and/or contractor personnel leave work on this project they shall have 5 working days to terminate all their network user account and to return all access cards and base identification badges.

4.2.5 Unescorted Entry. The user security manager will complete an “Unescorted Entry

Authorization Certificate” (AF Form 2586) for each employee requiring entry into controlled areas. The request will be submitted to Pass and Registration (South or West Gate Visitor

Center).

4.3 PHYSICAL SECURITY. The contractor shall be responsible for safeguarding all government property provided for contractor use. At the close of each work period, government facilities, property, and materials shall be secured.

4.4 SPECIAL QUALIFICATIONS.

4.5 MANAGEMENT OF PERSONNEL. The contractor shall select, retain and support personnel. The contractor shall match the qualifications of the positions, as described in the contract. The contractor shall support personnel so they are able to work effectively.

4.6 QUALITY CONTROL

4.6.1 Quality Control Program. The Contractor shall establish a complete Quality Control

Program (QCP) to ensure the requirements of this contract are provided as specified. The

Contract Officer (CO) will notify the Contractor of acceptance or required modifications (at no additional costs to the Government) and obtain acceptance of the plan by the CO before the start of the first operational performance period.

4.6.2 Quality Assurance

4.6.2.1 Contractor Quality Performance. The Government will periodically evaluate the

Contractor’s performance by appointing QAPs to monitor performance in order to ensure services are received. The QAPs will evaluate the Contractor’s performance and services through inspections and receipt of complaints from base personnel. All aspects of this contract are subject to surveillance.

4.6.2.2 Quality Assurance Personnel. The QAPs are authorized government representatives that assess the Contractor’s performance. Subsequent to contract award, the identity of the

QAPs, with a letter defining their duties and authority will be promptly furnished to the successful bidder/offeror.

4.6.3 Scope Change. Any matter concerning a change to the scope, prices, terms or conditions of this contract will be referred to the CO and not to the QAPs.

4.6.4 Quality Assurance Review. The tasks to be performed by the Contractor during the period of this contract will at all times and places are subject to review by the CO or QAPs.

4.6.5 Normal Hours of Operation. The contractor shall perform the services required under this contract within the following hours: Monday through Friday 0500–1800 – EXCEPT

FEDERAL HOLIDAYS. Contract personnel will work the same hours as government employees in the organization the contractor is assigned to. Work provided outside of normal hours shall be preapproved by the Program Manager at no extra cost to the Government.

4.6.5.5 Recognized Holidays. The Contractor is not required to provide service on the following days: New Year's Day, Martin Luther King Day, Presidents Day, Memorial Day, Independence Day, Labor Day, Columbus Day, Veterans Days, Thanksgiving Day and

Christmas Day. If the holiday falls on Saturday, it is observed on Friday. If the holiday falls on a Sunday, it is observed on Monday.

4.6.6 SAFETY REQUIREMENTS: While performing work under this contract, the Contractor shall follow Appendix C and adhere to the following:

The contractor shall follow Voluntary Protection Program (VPP) requirements of Hill AFB, Peterson AFB and Schriever AFB.

The Air Force is part of the OSHA VPP. The Contractor is required to attain familiarization with the requirements of VPP. Information on the VPP can be accessed at http://www.osha.gov/dcsp/vpp/index.html. VPP requirements apply to contractors whose employees work more than 1,000 hours per quarter. The contractor shall flow down these requirements to all subcontractors who qualify as applicable contractors under this contract. The

Contractor shall provide from its OSHA 300 information the Total Case Incident Rate/Days

Away Restricted or Transferred (TCIR/DART) rates by 15 January of each year to the CO for submission as part of the installation’s annual OSHA Voluntary Protection Program (VPP) self evaluation report.

4.6.7 Records Maintenance. The Contractor shall be responsible for creating, maintaining, and disposing of only those government records that are specifically cited in this PWS. If requested by the Government, the Contractor shall provide the original record or a reproducible copy of any such record within five working days of receipt of the request.

4.6.8 Government Required Training. The Government may provide training to the contractor personnel on an as needed basis. Special base access, computer security, and general security training will be provided to the contractor personnel by the appropriate government personnel.

4.6.9 Government Observation. Government personnel, other than CO and QAPs, may from time-to-time, with CO coordination, observe contractor operations. However, these personnel may not interfere with contractor performance or make any changes to the contract.

5. APPENDICES

A. Acronyms & Abbreviations List

B. Estimated Workload Data

C. Safety, Fire Protection and Health Specification Industrial Safety http://www.osha.gov/dcsp/vpp/index.html

D. RequirementsPublications/Instructions

APPENDIX A

ACRONYMS AND ABBREVIATIONS LIST

Acronym/Abbreviation Definition

AF Air Force

AFB Air Force Base

AFMC Air Force Material Command

CCS-C Command and Control System - Consolidated

CDL Contractor Development Lab

CDRL Contract Data Requirements List

CFR Code Federal Regulation

CM Configuration Management

CMMI Configuration Management Model Integrated

CMP Configuration Management Plan

CO Contracting Officer

COS Colorado Springs

CPARS Contractor Performance Assessment Reporting

System

DEPT Department

DOD Department of Defense

DOORS COTS Product by Telelogic

FAR Federal Acquisition Regulation

GFP Government Funded Property

GR Government Representative

ICD Interface Change Description

IDD Interface Design Description

IRS Interface Requirements Specifications

JFTR Joint Federal Travel Regulations

OO-ALC Ogden Air Logistics Center

OSHA Occupational Safety and Health Act

PBSA Performance Based Service Acquisition

PWS Performance-Based Work Statement

QA Quality Assurance

QAE Quality Assurance Evaluator

QCP Quality Control Program

QMP Quality Management Plan

SOC Satellite Operation Center

SCM Software Configuration Management

SDCR Software Design Change Requests

SEP Software Engineering Process

SOC Spacecraft Operations Center

SOPS Space Operations Squadron

SRS Software Requirement Specification

SS Services Summary

SSS System/Subsystem Specification

SSDD Sub-System Design Document

TPM Technical Program Manager

USAF United States Air Force

VPP Voluntary Protection Program

APPENDIX B

ESTIMATED WORKLOAD DATA

ITEM

NAME

ESTIMATED QUANTITY

1 General Services Support 12 MONTHS

APPENDIX C

SAFETY, FIRE PROTECTION AND HEALTH SPECIFICATION

INDUSTRIAL SAFETY REQUIREMENTS

OGDEN AIR LOGISTICS CENTER

UNITED STATES AIR FORCE

HILL AIR FORCE BASE, UTAH 84056

TYPE WORK: CCS-C (SMXG)

PREPARED BY: John A. Foreman, 309 MXW/QPE, DSN 586-4176

SECTION I - GENERAL REQUIREMENTS

A. Safety Program Requirements.

In context with AFMC Acquisition Reform initiatives, contract language will now focus on ensuring safety objectives are met through contractor risk management rather than the traditional method of providing specific government guidance for risk elimination. With this new

“performance-based” language, the government will provide the contractor with areas of concern

(Protection of government personnel and property) and the contractor will be free to meet those objectives in a manner that is consistent with corporate standards. The contractor will implement a safety program plan that ensures protection of Government personnel and property. The program will consist of, as a minimum:

1. Mishap reporting, as defined in paragraph B1 below.

2. A Safety Plan and corresponding site specific checklist that addresses, as a minimum, the subjects listed in Section II –Specific Requirements, and will be used during the performance of the work described in the contract. The Safety Plan and checklist will be approved by 309

MXW/QPE (Safety Office) prior to commencement of any work described in this contract.

3. Routine and recurring surveillance to ensure the safety requirements of this contract are enforced.

4. Competent personnel to provide surveillance of the Safety Plan.

5. Identification of segregated work site locations for operations that cannot be co-mingled with general industrial operations and the process for ACO approval of operations and changes at these specific sites.

6. All contractor personnel shall be trained and qualified to perform their duties safely.

7. The contractor shall include a clause in all subcontracts requiring the subcontractors to comply with the safety provisions of this contract, as applicable.

B. Mishap Notification

1. The contractor shall notify 309 MXW Safety (Phone (801) 586-4176) who in turn will notify

75 ABW/SEG ((801) 777-3333) or 309 Wing Operations Center ( (801) 777-3238), or the Hill

AFB Command Post (777-3007) after normal duty hours, and the designated Government

Representative, i.e., the ACO, PCO, or QAE within one (1) hour of all mishaps or incidents at or exceeding $2,000 (material + labor) in damage to DOD property entrusted by this contract, even if the government is wholly or partially reimbursed. This notification requirement shall also include physiological mishaps/incidents. A written or email copy of the mishap/incident notification shall be sent within three calendar days to the GR, who will forward it to 309 MXW

Safety. For information not available at the time of initial notification, the contractor shall provide the remaining information no later than 20 calendar days after the mishap, unless extended by the ACO.

Mishap notifications shall contain, as a minimum, the following information:

(a) Contract, Contract Number, Name and Title of Person(s) Reporting

(b) Date, Time and exact location of accident/incident

(c) Brief Narrative of accident/incident (Events leading to accident/incident)

(d) Cause of accident/incident, if known

(e) Estimated cost of accident/incident (material and labor to repair/replace)

(f) Nomenclature of equipment and personnel involved in accident/incident

(g) Corrective actions (taken or proposed)

(h) Other pertinent information

2. Ensure government contract lease agreements determine convening authority prior to executing the contract/lease agreements, and that all contracts ensure the following, IAW AFI

91-204, paragraph 2.4.6:

The contractor will support and comply with the safety investigation and report requirements of AFI 91-204

A record of all mishaps involving Air Force resources will be entered into the Air Force reporting system

A record of mishaps involving other DoD resources will be forwarded to the involved agencies

When a mishap involves a contract managed by DCMA, DCMA safety personnel will review the final safety report and send their response to HQ AFSC

3. Ensure contract/lease agreements for aerospace vehicles state: The Air Force is responsible for the investigation of mishaps involving aerospace vehicles. The Air Force is authorized to investigate mishaps involving non-accepted Air Force aerospace vehicles (Non-delivered vehicles for which the government has accepted responsibility; DD Form 250. Material

Inspection and Receiving Report, HAS NOT been executed).

4. If requested by authorized government personnel (ACO, PCO, QAE, safety representative, Fire Department, and Security Forces), the contractor shall immediately secure the mishap scene/damaged property and impound pertinent maintenance and training records, until released by safety investigators.

C. General Safety Requirements:

If the safety plan is modified, the contractor shall submit the proposed modification, in writing, to the Contract Administration Office safety representative.

Follow all applicable federal, USAF, state, and local safety directives outlined in Section

II below.

Ensure assigned personnel are adequately trained and qualified for the task being performed. Brief all personnel on the hazards involved with operations and applicable precautions to be taken. Should unidentified hazards arise, cease operations until actions are taken to eliminate or mitigate hazards to safe levels.

Contractor personnel must receive Explosive Safety Awareness Training if their duties require entry into the Explosive Clear Zone. This training will be provided by the 309 MXW

Safety Office.

SECTION II – SPECIFIC REQUIREMENTS

The contractor’s prepared Safety Plan shall:

Demonstrate a management commitment to employee safety and health

Identify applicable rules and regulations

Identify the roles and responsibilities of Management, Supervisors, Employees and

Safety Coordinator

Identify work to be performed and location of expected operations

Provide a description of safety program, safety monitoring responsibilities, organizational structure, and contact information for on-site personnel

Include a work hazard analysis of the worksite and operations to be performed to include baseline hazard identification and required control measures

Identify employee safety and health training requirements and the documentation process

Include emergency response plans and procedures that relate to protection of government personnel and property

Include a workplace inspection frequency, to include the identity of the individual responsible for conducting the inspection

Include hazard reporting procedures and identify individual(s) responsible for the correcting identified hazards

Identify first aid and injury procedures

Identify procedures for accident reporting and investigation

Identify the process for tracking controlled hazards in contractors work area

Provide a facility description to include the electrical wiring and fire protection systems

(i.e., fire suppression, fire detection, fire extinguishers, fire walls, etc.), required equipment and any other items necessary to fulfill the elements referenced below for the protection of government personnel and property. The contractor’s safety plan shall meet or exceed the referenced standards below.

The authorized Government Representative (309 MXW Safety Office) shall approve the contractor’s procedures within the Health and Safety Plan as meeting the intent of the below referenced standards, with the exception of Mishap Notification /Reporting Procedures, which are outlined in Section I, paragraph B of this Appendix C.

Element/Requirement Referenced Benchmark

Contract Safety AFPAM 91-210 Para. 6

Mishap Notification/Reporting Appendix A, Section I

AFI 91-204 Para. 4.9

Facility Fire Protection NFPA 13, 70, & 72

NFPA 409/410

AFOSH STD 91-501 Para. 6.2.4.5, 6.2.9, 6.2.10, 6.2.11, and 6.2.17 http://www.e-publishing.af.mil/shared/media/epubs/AFPAM91-210.pdf http://www.e-publishing.af.mil/shared/media/epubs/AFI91-204.pdf http://www.e-publishing.af.mil/shared/media/epubs/AFOSHSTD91-501.pdf

APPENDIX D

PUBLICATIONS/INSTRUCTIONS

Applicable PWS

Publication/Instruction /Name Date Paragraph/Chapter Paragraph

OO-ALC Configuration 10 March 2010 Entire Plan 1.1.3

Management Plan