Attachment 3 PWS Template.docx

Performance Work Statement (PWS)

United States Space Force (USSF) In-residence Intermediate Developmental Education (IDE) and Senior Developmental Education (SDE)

DATE: DD MMM YYYY

Table of Contents

1 Introduction/Background Collaborate with the USSF, Space Training and Readiness Command (STARCOM) Delta 13, to provide a graduate program for USSF Guardians, joint force, interagency, and international partners.

1.1 Mission Overview

The Delta 13 mission is to educate, and develop leaders in support of the National Defense Strategy who are prepared to dominate the space domain in a complex global environment.

1.2 Scope

Provide a 10-month in-residence graduate degree at a civilian university that will include a combination of existing university graduate-level courses and courses designed and taught by USSF instructors in accordance with Joint Professional Military Education (JPME) requirements. University will provide facilities, logistics, and appropriate support.

2 General Requirements This section describes the general requirements for this effort. The following sub-sections provide details of various considerations on this effort.

2.1 Non-Personal Services

The Government will neither supervise Contractor employees nor control the method by which the Contractor performs the required tasks. Under no circumstances will the Government assign tasks to, or prepare work schedules for individual Contractor employees. The Contractor shall ensure its employees understand the prohibitions imposed on the Government regarding personal services contracts, as defined in the FAR as “a personal services contract is characterized by the employer-employee relationship it creates between the Government and the contractor’s personnel.” 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. If the Contractor believes that any actions constitute, or are perceived to constitute personal services, the Contractor shall notify the Procuring Contracting Officer (PCO) immediately.

2.2 Contractor Management

The Contractor shall integrate and coordinate all activity needed to satisfy the requirement. The Contractor shall manage the timeliness, completeness, and quality of problem identification, and resolution, as applicable. The Contractor shall provide corrective action plans, proposal submittals, timely identification of issues, and effective management of subContractors. The Contractor shall seek to ensure customer satisfaction and professional and ethical behavior of all Contractor personnel. If the Contractor has any proposed revisions to this PWS or any other contract attachment, for the purposes of making the documents more accurate (regulatory changes) or complete (for clarity), the Contractor shall submit suggested revisions as word document with tracked changes and a change request to the COR and CO for consideration.

The Contractor shall provide a Monthly Status Report (MSR) covering activities of the preceding month.

Deliverable A001 – Monthly Status Report (MSR)

2.2.1 Contract Administration

The Contractor shall ensure its personnel do not perform inherently Governmental activities, as defined in FAR 7.5. The Contractor shall ensure its personnel do not attempt to represent the Government of the United States (US) to any other person or entity, US, or foreign, except for delivering a Government-approved message or position. All briefings, policies, plans and other formal products the Contractor develops, reviews, and creates, will be reviewed and approved by the Government.

2.2.2 Contractor POC

The Contractor shall have a single point of contact between the Government and Contractor personnel assigned to support this contract. This lead shall coordinate with the Contracting Officer’s Representative (COR) to obtain and clarify contract requirements and shall be responsible for the daily control and supervision of the Contractor’s employees.

2.2.3 Personnel Administration

The Contractor shall maintain the currency of their employees by providing initial and refresher training as required to meet the PWS requirements. The Contractor shall obtain approval from Government prior to attending Government-provided training classes. Provided there is no cost to the Government, the Contractor may be eligible to attend Government-sponsored and Government-provided training to maintain proficiency in software, administrative procedures or other areas. Additionally, provided there is no cost to the Government, the Contractor may be eligible to attend third-party-provided off-site seminars and classes.

2.2.4 Contractor Identification

Contractor employees shall clearly identify themselves as “Contractors” at all times, in all communications and representations, including in the workplace, at meetings, in conversations, telecommunications, mail, electronic mail (e-mail), and faxes, whether with Government personnel, other Contractor personnel, or with the public.

2.3 Contractor Personnel, Disciplines, and Specialties

The Contractor shall accomplish the assigned work by employing and utilizing qualified personnel with appropriate combinations of education, training, and experience. The Contractor shall ensure the labor categories, labor rates, and man-hours utilized in the performance of each Task Order (PWS line item) issued hereunder will be the minimum necessary to accomplish the task The Contractor shall provide the necessary resources and infrastructure to manage, perform, and administer the contract.

2.3.1 Personnel Turnover

The Contractor shall ensure continuity of services during personnel absences due to sickness, leave, and voluntary or involuntary termination from employment such that impact to the Government is minimal. Once the Contractor knows an employee will no longer support the requirement, the Contractor shall provide written documentation to the CO and COR within three (3) business days. In this notification, the Contractor shall include the date and time the position will be vacant, , anticipated fill date, and what management actions the Contractor will take to ensure uninterrupted performance. Position vacancies shall not exceed 14 calendar days unless approved in writing or otherwise directed in advance by the CO (e.g. a grace period associated with new awards and PWS modifications increasing the number of personnel on a task order).

2.3.2 Removal of Personnel at Government Request.

The Government may request removal (permanent or temporary) of personnel for security, safety or health reasons, or when Contractor personnel behave in an unprofessional manner that would be considered unacceptable by a reasonable person.

2.4 Location and Hours of Work

This PWS requires work at [specify location] and at various Contractor and Government facilities (mainly in the continental United States). Normal workdays are eight (8) hours per day, Monday through Friday, except US Federal Holidays.

2.6 Security

2.6.1 Operational Security (OPSEC)

The Contractor shall adhere to OPSEC guidance as defined in Air Force Instruction (AFI) 10-701, Operations Security (OPSEC). The Contractor shall be familiar with the organization’s Critical Information and Indicator List (CIIL) and ensure indicators and vulnerabilities are protected from Unauthorized Disclosure (UD) per Space Training and Readiness Command (STARCOM’s) countermeasures and measures. The Contractor shall complete OPSEC in-processing training and follow-on OPSEC training such as event-driven and annual OPSEC training, as required by the OPSEC Program Manager per Department of Defense (DoD) Directive (DoDD) 5205.02E, DoD Operations Security (OPSEC) Program; DoD Manual (DoDM) 5205.02, DoD Operations Security (OPSEC) Program Manual; Chairman of the Joint Chiefs of Staff (CJCS) Instruction (CJCSI) 3213.01D, Joint Operations Security; and AFI 10-701.

2.6.2 Controlled Unclassified Information (CUI)

The Contractor shall safeguard all information provided and marked as CUI via this contract IAW DoD Instruction (DoDI) 5200.48, Controlled Unclassified Information (CUI). If the Contractor generates any CUI information, it shall protect and disseminate that information per the controls required by DoDI 5200.48. The Contractor shall monitor CUI for aggregation and compilation based on the potential to generate classified information pursuant to security classification guidance addressing the accumulation of unclassified data or information. The Contractor shall immediately report the potential classification of aggregated or compiled CUI to the CO and the COR.

2.7 Documentation

The Contractor shall make all information and documentation generated or maintained (to include Government-furnished documents) by this contract available for Government review upon request for the duration of the contract. The Contractor shall generate and maintain all such documentation in an electronic, editable (where appropriate) format. Contractor-generated format is acceptable, unless otherwise noted by this PWS.

The Contractor shall provide responses to requests for information. These requests are in addition to Deliverable submissions and other documentation that is available for review by request. Requests may cover the range of activities under this PWS.

2.7.1 Documentation Rights

The Government has unlimited rights to data for all deliverables developed under this PWS. The Contractor shall not use any materials pertaining to this contract for business development or any other Contractor purposes; however, the Contractor is authorized to include summary performance information in proposals to be submitted to the Government to satisfy past performance information requirements.

All products developed and produced by the Contractor in the performance of this PWS are the property of the Government, and this could include software, electronic files, hard copy documents, etc. Rights to all documentation are governed by Defense FAR Supplement (DFARS) 252.227-7032, Rights in Technical Data and Computer Software.

2.7.2 Government Data

The Contractor shall request Government approval prior to the use of any proprietary data or software tools to fulfill the requirements of this contract. The Government will provide the Contractor access to information required to accomplish assigned tasks commensurate with security clearance and on a need-to-know basis. The Contractor shall not retain classified or unclassified material generated or received under this contract after the contract ends without approval of the Contracting Officer.

2.8 Performance Evaluation.

Contractor performance is subject to Government surveillance to ensure PWS compliance. The Contractor shall comply with the following:

Access. The Contractor shall permit the CO or authorized representative access to all work areas, records, and data used in the performance of the contracted services. The Contractor shall provide support, and not interfere with the CO, Contracting Officer’s Representatives (CORs), state, federal, and other designated personnel in the performance of their official duties. The Contractor shall provide access as soon as possible, but not to exceed one (1) workday after the request.

Non-conformance. The Contractor shall identify root causes of non-conformances and shall control them through analysis, corrective actions, and preventive actions. The Contractor shall focus on eliminating the cause to prevent reoccurrence. The Contractor shall maintain records of non-conformities and actions taken. The Contractor shall correct and provide responses to all Government-identified non-conformances in accordance with (IAW) time frames specified by the CO. There are two types of non-conformances: Minor and Major.

Minor Non-conformance. A Minor Non-conformance is a non-conformance, which by itself does not adversely impact mission, safety of personnel and equipment, performance (quality), schedule (delivery), or cost. A Minor Non-conformance does not normally increase risk to the Government. Minor Non-conformances are typically low risk and are communicated through a Corrective Action Request (CAR) notice. First notices are issued for any identified non-conformance, second notices are issued for repeat non-conformances or failing to correct issues within a reasonable amount of time. Upon receipt of a non-conformance notification (first or second notice), the Contractor shall complete applicable sections and return it to the CO within time constraints directed by the CO in the notice. A formal corrective action plan may not be required for minor CAR notices.

Major Non-conformance. A Major Non-conformance is a non-conformance that adversely impacts (or has the potential to impact) mission, safety of personnel and equipment, performance (quality), schedule (delivery), or cost. A Major Non-conformance may also be a significant number of recurring non-conformances, which is an indication of inadequate preventive measures or actions and lowers the Government’s confidence that the Contractor can provide quality services on time and within costs. The CO will communicate Major Non-conformances using the CAR notice and will include a suspense date for the Contractor’s Corrective Action Plan. As a minimum, the Contractor’s Corrective Action Plan shall address:

• Actions taken to fix the immediate problem

• Root cause analysis of the problem to determine cause

• Corrective action on the cause of the problem

• Actions taken to prevent recurrence

2.9 Government Furnished

The Government will make available the materials, office space, communications capability and information on the dates specified as identified in Attachment XX for use by the Contractor in the performance of this contract.

2.9.1 Government Furnished Property (GFP).

The Government will not provide any GFP for Contractor use on this contract.

2.9.2 Government Furnished Information

Government staff personnel will be available for technical exchanges with the Contractor. Government personnel will provide technical input, answer questions, review and approve completed work, and provide feedback regarding Contractor efforts. The COR is the primary source of technical guidance for this PWS.

3 Performance Requirements The following section specifies the Performance Objectives and Performance Elements for the contract. Acceptable Quality Level (AQL) is a tolerable variation in the execution of a PWS Standard. Utilize standards, acceptable quality levels (AQL), and deliverables as examples show below.

#.# PARA – BOLD statement – tells in a performance based way the outcome expected – what service do we need the Contractor to perform (not how to do it) Not bold statement – clarification only if needed – describes what this requirement includes or specifies if Gov will provide information Performance Standards

a) Standard: Describes the standards that apply to the BOLD statement – how will the performance of the bold statement be measured so that the Gov knows it is being performed in an acceptable manner. Examples can include regulatory standards (DoDIs, AFIs, Guides) quantity/frequency (10 times per year), timelines (within 2 days of receipt/meeting), etc

b) Standard: When referencing a publication/regulation: describe if compliance is directive or guidance (and match this to the table in Section 4); tailor the reference to the paragraphs/chapters that are applicable to the Contractor’s performance (DO NOT list entire publications as mandatory).

c) Standard: There can be as many standards as needed to describe the measurements of the requirement Deliverable A0XX: TITLE – this lists any deliverable tied to the BOLD statement

3.# Transition

DEFAULT TEXT:

The Contractor shall follow the transition plan submitted as part of the proposal and keep the Government fully informed of status throughout the transition period. Throughout the phase-in/phase-out periods, it is essential that attention be given to minimize interruptions or delays to work in progress that would impact the mission. The Contractor must plan for the transfer of work control, delineating the method for processing and assigning tasks during the phase-in/phase-out periods. [Include and tailor this as necessary for the requirement; if not using transition plan in the technical evaluation criteria, modify this paragraph to either require a plan as a formal deliverable in the contract or remove “plan” language completely.]

SAMPLE SECTION 3 LANGUAGE BELOW – TAILOR TO THE REQUIREMENT

3.# Support the Satellite Control Network (SCN).

3.#.# The Contractor shall review and provide Research and Development (R&D) recommendations for SCN modernization programs.

Including but not limited to: Remote Tracking Station (RTS) Block Change (RBC) Hybrid, Multi-Band Multi-Mission (MBMM) i.e. Phased Array Radars Electronic Scheduling Dissemination (ESD)/Network Management System (NMS), High-Power Amplifier (HPA), and Transportables specifications design review data packages Performance Standards

a) Standard: IAW State of the Art (SOTA) Research and Development in regards to Transmit (Tx) / Receive (Rx) elements and Phased Array technology for modernization efforts to increase mechanical reliability, decrease manpower for RBC Systems.

b) Standard: E-mail updates 2x week to HQ SpOC S36R

c) Standard: Format report updates monthly to HQ SpOC S36R

3.#.# The Contractor shall participate in boards, groups and meetings and shall capture and disperse meeting minutes.

Performance Standards

a) Standard: Boards, groups, meetings not to exceed 10 per month

b) Standard: Participation to include comments and recommendations to allow HQ SpOC S36R to successfully resolve issues and meet action item suspense’s

b) Standard: Meeting minutes in Contractor format (email text is acceptable when a less formal meeting is held); due within 2 days after meeting occurrence / conclusion AQL: 4 submissions per year received within 5 days after meeting occurrence

3.3.# The Contractor shall coordinate and review legacy AF and AFSPC Instructions, author new versions or updates with Government input for new HQ SpOC Instructions (SpOCIs).

Performance Standards

a) Standard: Complete re-write within 180 days of final concurrence from team to start updating the instruction. The Government will provide the prioritized list of prioritized instruction re-writes

b) Standard: The document will adhere to AFH 33-337 guidelines and will be reviewed by a contractor technical editor or contractor Subject Matter Expert (SME) with experience / familiarity on writing DoD Service component, or Command-level instructions.

c) Standard: Spell Check and Grammar utilization in Microsoft Word or other word processing software is required and expected.

d) Standard: Acronyms will be defined in the glossary and standard ones frequently used in the AF and Space Force “commonly accepted list” will not require definition.

e) Standard: The document will not have more than 4 grammatical errors in the final product to be published on “AF E-Pubs”

3.#.# The Contractor shall develop and update the HQ SpOC S36R “SCN 101” briefing.

Performance Standards

a) Standard: Contains information on the SCN mission, how the organization supported accomplishes it, and major R&D efforts and utilization of efforts towards meeting operational and maintenance issues/programs and status of R&D accomplished to date.

b) Standard: With current information before subsequent briefings.

Deliverables A002: SCN 101 Presentation

4 Applicable Publications The Contractor shall comply with all documents listed below in the table of publications and referenced under paragraph 3.0, Performance Requirements. The Directive/Guidance (D/G) column indicates the extent of Contractor compliance with the publication that is prescribed by the PWS. A “D” in the column means the publication is a “directive publication,” that requires mandatory compliance by the Contractor. A “G” in the column means the publication is a “guidance publication.” Compliance with documents listed as guidance is the Contractors' option. If there is any conflict between the directive referenced in PWS paragraph 3.0 and the reference listed in the tables below, the reference in PWS paragraphs 3.0 takes precedence.

When directive chapters, paragraphs, appendices, attachments, etc. are referenced as a standard in this PWS, the standard shall be inclusive of all subordinate paragraphs unless specifically excluded. For example, if the PWS standard lists paragraph 1.2 as directive, and paragraph 1.2 has subparagraphs 1.2.1, and 1.2.2 those subparagraphs are directive as well.

Publications

5 Deliverables

DEFAULT TEXT:

The Contractor shall provide deliverables as described in the PWS. Format and delivery schedule for deliverables shall be outlined in the table below [If using CDRLs instead, the CDRL form will prescribe information required and format; CDRLs must link to a DID, if CDRLs are not used, the deliverable format/information required must be detailed in the table below. If Deliverables will contain CUI data, ensure this is noted in the description and instruct the Contractor to mark/disseminate/protect IAW CUI regulations]. All Deliverable distribution shall be by an electronic method unless otherwise specified. Email documents in a Microsoft Office or Adobe Acrobat-compatible format. Submit drawings in a uniform electronic format.

Informal, recurring work products may not require a deliverable. These products are still required as described in paragraph 3 of the PWS. [TAILOR as needed for the requirement]

If there is any conflict between the Deliverable reference in paragraph 3 of this PWS and the Deliverable specifics in the following table, paragraph 3 takes precedence. Days referenced shall be calendar days, unless otherwise noted. For recurring Deliverables, if the due date falls on a holiday or a weekend the Deliverable may be sent on the following business day. Contractor format is acceptable, unless a specific format is identified. The Contractor shall not include its name or any logos on any Deliverable except when a Contractor signatory is required by the Deliverable. The Contractor shall ensure all markings included in Deliverables are consistent with the contract’s requirements, to include copyright and proprietary markings addressed in the contract’s clauses.

Deliverable Table

SAM-D/PK

Description: (Contractor format acceptable) As a minimum, the MSR shall detail:

· Executive summary detailing a self-assessment of the Contractor’s performance during the reporting period

· Major tasks/activity status

· Contractual issues or risks requiring Government resolution/mitigation

· Self-identified performance efforts exceeding the PWS requirements, along with how these efforts provide a benefit to the Government

· Self-identified performance deficiencies during the period; including the cause of each identified deficiency, corrective actions, the impact, and actions taken to preclude recurrence

· Deliverables submitted

A002

Description:

A003

Description:

A004

Description:

6 Services Summary This Services Summary (SS) identifies the major performance objectives and performance thresholds required for Contractor performance. The Government retains the right to inspect, assess and enforce all services required by this contract, regardless of their inclusion in this SS.

Copy/Paste Standards from this PWS requirement

a) Deliverable requirements are met

Copy/Paste Standards from this PWS requirement

a) Deliverable requirements are met

Copy/Paste Standards from this PWS requirement

a) Deliverable requirements are met

Copy/Paste Standards from this PWS requirement

a) Deliverable requirements are met