DRAFT TO-0001 - Program Management.pdf

Section C - Descriptions and Specifications

F-35 JOINT PROGRAM OFFICE (F-35 JPO) / SERVICES ACQUISITION TEAM (SAT)

PROGRAM SECURITY SUPPORT SERVICES

SINGLE AWARD - INDEFINITE DELIVERY / INDEFINITE QUANTITY (ID/IQ)

TASK ORDER 0001

PROGRAM MANAGEMENT

STATEMENT of WORK (SOW)

12 August 2020

1.0 OVERVIEW

The F-35 Lightning II Program (also known as the Joint Strike Fighter Program) is a joint, multi-national program and is the Department of Defense's (DoD) focal point for defining affordable next generation strike aircraft weapon systems among the United States (U.S.) Air Force (USAF), U.S. Navy (USN), U.S. Marine Corps (USMC), and U.S. allies composed of seven (7) cooperative international partners: the United Kingdom, Italy, Netherlands, Canada, Australia, Denmark, and Norway. The program’s objective is to develop and deploy the F-35 Air System (AS), a three (3) variant family of highly common and affordable 5th Generation strike fighter aircraft that meets the operational needs of the USAF, USN, USMC, and cooperative partner international services.

Additional production of the F-35 is made through Foreign Military Sales (FMS). The F-35 Enterprise is defined as, but not limited to: Air Vehicle (AV), AS, AS Ground Support, Support Equipment (SE) Systems, Depot Maintenance, Business, Flight Test, and Training Systems. The F-35 security team has a mature Program Protection Plan (PPP), robust policies and procedures and established SAP facilities throughout the world. Requirements continue to evolve as the program matures and the F-35 security team is responsible for ensuring that any new security challenges are appropriately identified and safeguarded in accordance with (IAW) DoD regulations and specifications.

2.0 SCOPE

The F-35 Joint Program Office (F-35 JPO) requires program security support services as a critical mission in developing, deploying and sustaining the next generation strike fighter aircraft. The program security support disciplines consist of Program Management, General Security Support, Information Security Support, Industrial Security Support, Physical Security Support, Personnel Security Support, Counter-Intelligence Support, Special Security Studies, Foreign Disclosure Support, Program Protection Cybersecurity/Security Control Assessment Services and Program Protection Engineering Services. The Program Security Support Services encompass the

DRAFT

https://hub.jsf.mil/sites/OCIO/win10

Page | 2 management and control of controlled unclassified information (CUI), collateral/general service (GENSER) information, Special Access Program (SAP) information, North Atlantic Treaty Organization (NATO) information, Critical Nuclear Weapons Design Information (CNWDI) and Sensitive Compartmented Information (SCI). This is an Indefinite Delivery/Indefinite Quantity contract which sets forth the conditions and clauses under which future acquisitions between the parties shall be governed. This Task Order (TO) will be used as a means of providing Security Program Management including Financial Management to the F-35 JPO.

3.0 TASK ORDER PERFORMANCE REQUIREMENTS

The Contractor shall furnish the necessary personnel, skills, material, and other services as required to perform the following tasks. All tasks shall be performed in accordance with applicable security regulations and policies including, but not limited to, those referenced at Attachment 1.

The following tasks may be in support of Continental United States (CONUS) and/or Other than Continental United States (OCONUS). The tasks are not assigned to any one specific security business area, and are intended to provide maximum flexibility and support to the enterprise.

3.1 Provide Program Management. The contractor shall provide program management under this TO, including but not limited to the following tasks:

3.1.1 Provide top-level management for all TOs associated with this ID/IQ, including management and oversight of all activities performed by contractor personnel, including subcontractors, to ensure all F-35 program security support services satisfy the requirements identified in each TO SOW

3.1.2 Gather and provide all data for deliverables as detailed in Section 7.0. This includes consolidation of deliverables from other TOs associated with this ID/IQ unless those deliverables are unique to that particular TO

3.1.3 Provide management, direction, administration, quality assurance, and leadership of the execution of the overall ID/IQ

3.1.4 Provide top-level direction to facilitate the Project Managers on each TO to organize, direct, and manage contract operation support functions, involving multiple, complex, and inter-related project tasks

3.1.5 Oversee management of teams of contract support personnel at multiple locations

3.1.6 Maintain and manage the client interface at the senior levels of the client organization and serve as the primary interface and point of contact with Government program authorities and representatives on technical and program/project issues

3.1.7 Meet with Government and contractor personnel to formulate and review task plans and deliverable items

3.1.8 Ensure conformance with program task schedules and costs

3.1.9 Direct efforts of cross-competency team(s) to include contractors at multiple locations

3.1.10 Oversee contractor personnel program/project operations by developing procedures, planning and directing execution of the technical, programming, maintenance and administrative support effort and monitoring and reporting progress

3.1.11 Gather information, data and reports from each TO as applicable for consolidation

Page | 3 into contract deliverables

3.2 Provide Financial Management. The contractor shall provide financial management under this TO, including but not limited to the following tasks:

3.2.1 Create and review financial reports for all TOs associated with this ID/IQ

3.2.2 Manage financial records for all TOs associated with this ID/IQ

3.2.3 Monitor financial health of all TOs associated with this ID/IQ

3.2.4 Prepare financial forecasts and present them to Government leads no later than five (5) business days following request

4.0 GENERAL INFORMATION

4.1 Period of Performance. The period of performance (PoP) for this TO consists of one (1) base year and four (4) option years.

4.2 Place(s) of Performance. The primary place of performance will be the contractor location.

A hot desk may be established for contractor personnel at the F-35 JPO primary location in Crystal City, Arlington, VA. Travel to other F-35 JPO locations may include, but are not limited to:

• Naval Air Warfare Center/Aircraft Division (NAWC/AD), Patuxent River, MD

• Edwards AFB, CA

• Naval Air Warfare Center/Weapons Division (NAWC/WD) China Lake, CA

• NAWC/WD, Pt. Mugu, CA

• Wright-Patterson AFB, OH

• Eglin AFB, FL

• Outside Continental United States (OCONUS)

4.3 Hours of Operations. The contractor shall provide the required services and staffing coverage during normal working hours. Core hours are 0900-1500, Monday through Friday (except on the legal holidays specified in paragraph 3.5.3). Contractors on this TO must be available during core hours.

4.4 Compressed Work Schedule (CWS). CWS is not permitted on this TO.

4.5 Extended Core Business Hours. Contractor Staff may be required to work beyond Normal Core Business Hours. In the event that additional hours must be worked, prior approval must be obtained from the COR.

4.6 Overtime. Refer to ID/IQ.

4.7 Telework. Telework is permitted on this effort IAW ID/IQ Section 4.7.

4.8 Meeting Support. In support of the tasking outlined in this SOW, the contractor shall have the capability to support meetings at the TOP SECRET classification level at Government

Page | 4 location(s) captured in this TO at CONUS and OCONUS locations.

4.9 IT Operating Environment. Refer to ID/IQ.

4.10 Transition/Mobilization. Refer to ID/IQ.

4.11 Management of Contractor Personnel. Refer to ID/IQ.

4.12 Installation Closure. Refer to ID/IQ.

4.13 Holidays. Refer to ID/IQ.

4.14 Information Technology. Refer to ID/IQ.

4.15 Section 508 Compliance. Refer to ID/IQ.

4.16 Government Furnished Property (GFP). Refer to ID/IQ.

5.0 SECURITY REQUIREMENTS

5.1 DD-254, Contract Security Classification Specification. Refer to ID/IQ.

5.2 Basic Personnel Clearance Requirements. All personnel must have required security clearance at day one of TO Period of Performance (PoP). Personnel may not have an interim clearance at time of contract award unless approved in advance by the Government. The contractor is responsible for ensuring that all personnel receive the requisite investigation and are favorably adjudicated in accordance with DoDM 5220.22, National Industrial Security Program Operating Manual (NISPOM). Contractor employees who fail to meet security clearance requirements may not access classified information or perform sensitive duties. In such cases, the contractor employee may not perform on the contract.

5.3 Citizenship Requirements: Refer to ID/IQ.

5.4 Command Access Cards (CAC) / Local Badges: Refer to ID/IQ.

5.5 SAAR-N: Refer to ID/IQ.

5.6 Information Security. Refer to ID/IQ.

5.7 Anti-Terrorism Force Protection and Emergency Management: Refer to ID/IQ.

6.0 TRAVEL AND OTHER DIRECT COSTS

6.1 Travel. Travel shall be allowable only when it is essential to the performance of the tasks detailed in this task order. Refer to ID/IQ.

6.2 Other Direct Costs (ODC). Refer to ID/IQ.

Page | 5

7.0 CONTRACT DELIVERABLES AND APPLICABLE DOCUMENTS

7.1 Contract Status Reporting: The following contract deliverables shall be provided in response to this task order:

Table 7.1. Deliverables

Name No. of Copies

SOW

Reference

Due

Management and Staffing Plan

1 7.1.1

With proposal for Government approval and as required post-award to capture any Contractor requested changes to the approved plan; or to add task order specific updates for further approval

Quality Control Plan 1 7.1.2

No later than 30 calendar days after award and as needed post-award to capture any Contractor requested changes to the approved plan for further approval

Kick-Off Meeting & Slides 1 7.1.3

No later than 10 business days of award notification for Government review

Monthly Status Report 1 7.1.5

No later than 30 calendar days after award & 15th calendar day of each month thereafter capturing the previous months activities, to include awarded task order activities

Monthly Expenditure Report 1 7.1.6

No later than 30 calendar days after award and 15th calendar day of each month thereafter capturing the previous months expenditures, to include detailed cost data for all awarded task orders (an attachment per task order capturing monthly expenditures)

Concept of Operations 1 7.1.7 No later than 45 calendar days after each TO Award

Weekly Activity Reports

(WAR) 1 7.1.8

1500 hours on Tuesday of each week capturing the previous week’s activities

Hiring Status Report 1 7.1.9 Every Friday through the end of the transition period & the 15th calendar day of each month thereafter

Page | 6

Name No. of Copies

SOW

Reference Due

Transition-In Plan 1 4.8 & 7.1.10

With proposal for Government approval;

as needed post-award to capture any Contractor requested changes for approval;

or in response to an awarded task order for Government approval

Travel Authorization Request

1 6.1 & 7.1.11

No later than 10 calendar days before the first travel date (CONUS) or 15 calendar days (OCONUS) for COR approval

Trip Report 1 7.1.12 No later than 5 business days after the last day of travel

Meeting Minutes 1 7.1.13 No later than 3 business days of the meeting conclusion

Problem Notification 1 7.1.14 As required; within 24 hours of identification of a problem that negatively effects cost, schedule, or performance

Transition-Out Plan 1 7.1.15

No later than 60 calendar days after request from the Government and as needed to capture any Contractor requested changes to the approved plan for further approval

Notes:

1. Submit one copy each electronically in Adobe (PDF) or as a Microsoft Office Suite product to the CO, COR, PM, CS, and acquisition analyst. If copies exceed five (5) megabytes of data, send through AMRDEC SAFE (Safe Access File Exchange) at https://safe.amrdec.army.mil/SAFE/. Submit classified reports only to the GCC point(s) of contact via SIPRNet or JWICS, as appropriate.

2. All deliverables shall be submitted by the established due date. If the due date falls on a weekend or holiday, the deliverable shall be submitted on the next business day. Unless specified otherwise, calendar days will be used. If the submittal is rejected by the Government the Contractor shall resubmit within 15 days.

3. The deliverables listed are not all inclusive and do not relieve the Contractor of responsibility for providing deliverables as required elsewhere in the SOW and the main ID/IQ if applicable.

4. All deliverables must meet professional standards and meet the requirements set forth in contractual documentation. The Contractor shall be responsible for delivering all end items specified unless otherwise directed by the COR/TPOC. Contractor format is acceptable for this effort, unless otherwise stated, as long as all required analysis is completed and provided to the Government

7.1.1 Management and Staffing Plan. The Contractor shall provide a Management and Staffing Plan in accordance with the timelines captured in Table 7.1. The plan shall delineate how the Contractor plans to support this effort. At a minimum, the Contractor’s management plan shall include the following elements:

• Management Plan portion:

o Team organization structure, management roles and workforce structure, including;

lines of responsibility, authority, and communication through which all tasks will be managed https://safe.amrdec.army.mil/SAFE/

Page | 7 o Subcontractor management plan to include details as to how the subcontractors will be managed (if applicable) to ensure cohesive integration into the overall management approach; describe the integration of the teaming partners into the overall management approach; how and why selected subcontractor(s) were chosen; which knowledge and skills will be acquiring through each subcontract;

level of subcontract effort expected o Task dependencies and interrelationships o Cost management plan o Schedule management plan o Resource management plan o Plan of action to address Government Equipment transfer and track of equipment from the F-35 JPO Operations o Risk management plan o Security plan

• Staffing Plan portion:

o Plan to attract, train, and retain qualified personnel to meet SOW requirements o Labor category titles and functional responsibilities for all key and non-key labor categories captured in the SOW, to include employee name, current position title, and company o Qualifications for key personnel to include educational history and current level of security clearance and status (final, interim, or pending).

7.1.2 Quality Control Plan. The Contractor shall provide a Quality Control Plan (QCP) in accordance with the timelines captured in Table 7.1. The Contractor shall establish and maintain a QCP that ensures services are performed in accordance with this requirement (see Section 8), applicable laws and regulations, and best commercial practices. The Contractor’s QCP shall provide, (at a minimum), a detailed approach for ensuring effective controls, processes, and procedures are developed and implemented to meet/exceed all requirements of this and each TO

SOW.

7.1.2.1 The QCP shall discuss how invoice reviews shall be conducted, to include discussion on how the primes, subcontractor, and supplier supporting data shall be reviewed for consistency with contract requirements.

7.1.2.2 As part of the Contractor’s Monthly Progress Report, the Contractor shall specifically discuss quality control activities over the reporting period and planned activities for the next period. Information shall specifically address WHO conducted the QC, WHEN was the QC executed, HOW was the QC executed and WHAT the findings and corrective actions were. Trends overtime shall be discussed

7.1.3 Kick-Off Meeting and Slides. The Contractor shall attend the contract Kick-Off Meeting and submit Kick-Off slides in accordance with the timelines captured in Table 7.1. The Contractors slides shall capture (at a minimum) the following data:

• Introduction of key personnel

• Roles and responsibilities

Page | 8

• Approach to overall ID/IQ management

• Approach to ID/IQ deliverables management

• Communication plan and lines of communication overview

• Schedule showing major tasks and milestones with start/completion dates

• Security requirements/issues/facility access procedures (if applicable)

• Sensitivity and protection of information (if applicable)

• Government Furnished Information (GFI) and Equipment (GFE) (if applicable)

• Initial deliverables (if applicable)

• Current status of transition-in plan (as proposed and approved by the Government)

• Any other information the contractor deems pertinent

7.1.4 Operations Security Plan. The Contractor shall provide an unclassified Operations Security Plan in accordance with the timelines captured in Table 7.1. The plan shall summarizing (at a minimum) how the Contractor will control critical program information, classified material, and sensitive data.

7.1.5 Monthly Status Report. The Contractor shall provide an unclassified monthly report in accordance with the timelines captured in Table 7.1. The report shall summarizing (at a minimum) the following elements, and shall include data from this and each TO SOW:

• Any information the Contractor determines to be mission essential

• Problems and shortfalls, identification of potential problems, and identification of any anticipated technical or funding shortfall or irregularity during the specified period of performance

• Projected travel and government approval status

• Summary of completed trips

• Quality Control activities completed and the outcome

• Activities during reporting period, by task, to include on-going activities, new activities, activities completed, and deliverables submitted

• Summary of contractor personnel gains, losses, and staffing status

• Government actions required

• Recommendations for change, modifications, or improvements in task or processes

7.1.6 Monthly Expenditure Report. The Contractor shall provide a Monthly Expenditure Report in accordance with the timelines captured in Table 7.1. The reports shall be submitted based on the Contractors approved format, as long as the report properly segregates CLINs, SubCLINS, and other funding lines. The report shall include data from this and each TO SOW and shall contain (at a minimum):

• Information about labor to include:

o Employee name and company o SOW Labor category and company labor category if different o Monthly and cumulative hours worked o Fully burdened hourly rate o Corresponding contract ceiling rate o Current monthly total and cumulative amount billed per employee;

Page | 9 o CLIN o Total cumulative amounts invoiced and funds remaining for each CLIN

• Information about travel to include:

o Travel Authorization Request identifier o Approver name and approval date o Invoice period o Names of person(s) that traveled o Dates of travel and total of number of travel o Number of days per diem charged, per diem rate used, and total per diem charged o Transportation costs o Total charges o Explanation of variances exceeding 10% of approved versus total costs

7.1.7 Concept of Operations. The Contractor shall provide a Concept of Operations report in accordance with the timelines captured in Table 7.1. The report shall include data from this and each TO SOW and shall contain (at a minimum):

• Identify the forms, process, and procedures required for TO service execution

• Contractor-recommended service levels for the prescribed tasks

• Drafts and/or templates of all deliverables, to include invoices and supporting documentation

• Most current, relevant government policies and process interactions

• Detailed processes for all types of service, organized by task area

• Swim lane charts identifying the interaction of activities within contractor elements

7.1.8 Weekly Activity Report. The Contractor shall provide a Weekly Activity Report (WAR) in accordance with the timelines captured in Table 7.1. The report shall include data from this and each TO SOW and shall contain (at a minimum):

• Progress of current and future tasks with completion status

• Identification of any issues that require Government interaction for resolution

• Strategic planning necessary to draft, review, revise, and deliver documents identified within individual subtasks

• Support provided for capabilities demonstrations and conferences and other activities

7.1.9 Hiring Status Report. The Contractor shall submit a hiring status report in accordance with the timelines captured in Table 7.1. The report shall include data from this and each TO SOW and shall contain (at a minimum):

• Personnel name per position

• MPS number associated with position

• Start date

• Vacant positons and estimated fill date

Page | 10

• Other pertinent data concerning hiring actions the Contractor is taking to fill the position

7.1.10 Transition-In Plan. The Contractor shall submit a transition-in plan based on a 45-day period with their proposal for Government approval per paragraph 4.5. The schedule shall capture the proposed timelines for starting performance 45-days after award. The report shall include data from this and each TO SOW and shall contain (at a minimum):

• Timeline for onboarding of personnel (to include subcontractor personnel if applicable) as captured in the staffing plan and shall include 10 business days for Government onboarding actions prior to Contractors starting performance

• Actions to be taken for completing required CONUS and OCONUS related training in accordance with the SOW and training required to obtain a country clearances (as applicable)

• Actions to be taken to meet the requirements captured in SOW paragraph 4.8.1

• Proposed risks and the correlating mitigation strategies the offeror proposes to implement to allow for successful performance

7.1.10.1 The Contractor shall submit requested changes for Government approval as they are required. The Contractor shall keep in mind that their approved transition-in plan is/was used by the Government to plan onboarding and any changes may affect the Governments requirement.

7.1.11 Travel Authorization Request. The Contractor shall submit a travel authorization request in accordance with the timelines capture in Table 7.1 that includes (at a minimum) the following data for COR approval prior to incurring any costs (the Government may provide a travel authorization request template for use post-award):

• Contract Number

• Name of Traveler

• Dates

• Origin and Destination

• Owning IPT being supported

• Organization to be visited

• Purpose of Travel

• Estimated Airfare

• Estimated Lodging within regulatory limits

• Estimated Per Diem

• Estimate Ground Transportation

• POV Use

• Miscellaneous Costs

• Justification as to why teleconferencing or video teleconferencing cannot be used

• Employee signature

• IPT Signature

7.1.12 Trip Report. The Contractor shall submit a trip report in accordance with the timelines capture in Table 7.1 that includes (at a minimum) the following data:

Page | 11

• Personnel who traveled

• Dates of travel

• Destination(s)

• Purpose of trip

• Cost of the trip

• Approval authority

• Summary of events, action items, and deliverables

7.1.13 Meeting Minutes. The Contractor shall submit meeting minutes in accordance with the timelines capture in Table 7.1 that capture (as a minimum) the following data:

• Meeting attendees and their contact information

• Meeting date

• Meeting location

• Purpose of meeting

• Summary of events

7.1.14 Problem Notification. The Contractor shall submit a problem notification report capturing the following data in accordance with the timelines capture in Table 7.1 for Government review and feedback. The report shall include data from this and each TO SOW and shall contain (at a minimum):

• Potential cost/schedule overruns/impacts

• Delay to delivery

• Assumptions upon which tasks were based that have changed or were incorrect;

• Nature and source of the problem

• What corrective action needs to be taken to resolve the problem

• If government action is required

• When the action will be completed

7.1.15 Transition-Out Plan. The Contractor shall submit a transition-out plan based on a 45-day period with their as prescribed in paragraph 4.8.2 and table 7.1. The schedule shall capture detailed timelines for how the Contractor will fully cooperate in relinquishing responsibilities to the Government or a new Contractor. The report shall include data from this and each TO SOW and shall contain (at a minimum):

• How the contractor will coordinate with the incoming contractor/Government personnel to transfer knowledge

• POCs for all locations

• Location of technical and project management documentation

• Schedules and milestones

• Status of ongoing technical initiatives

• Plan to transition of key personnel

• Actions required of the Government

Page | 12

• Plan to establish and maintain effective communication with the incoming contractor/Government personnel for the period of the transition via weekly status meetings

• System access information

• Facility accreditation information

• Safe and vault access codes

• Open investigations and statuses of security clearances

• Schedule turnover

• Technical documentation and expectations

7.2 Applicable Documents. The Contractor shall comply with regulations or publications captured in Attachment 1. This list is not all-inclusive; additional policies may be identified as the program matures at the ID/IQ or task order level.

7.3 Enterprise-Wide Contractor Manpower Reporting Application (ECMRA): The contractor shall report contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the F-35 Office of Joint Reprogramming Enterprise (JRE) via a secure data collection site. The contractor is required to completely fill in all required data fields using the following web address: https://www.ecmra.mil. Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. Contractors may direct questions to the ECMRA help desk as needed. Contracted services excluded from reporting are based on Product Service Codes (PSCs).

8.0 QUALITY

8.1 Contractor Quality Control. Refer to ID/IQ.

8.2 Service Summary. The Service Summary captured in Attachment 3 will be used to develop or may serve as the Government Surveillance Activity Checklist (SAC) to audit performance in accordance with this TO. The SAC will identify the audit methods and procedures the Government will use to evaluate Contractor performance. The Government will provide a copy of the SAC and any updates to the Contractor as applicable.

9.0 KEY PERSONNEL, LABOR CATEGORIES, AND QUALIFICATIONS

9.1 Key Personnel. The following positions are considered key personnel in support of this requirement:

• Program Manager

9.2 Qualifications / Labor Categories /Level of Effort. The contractor shall be responsible for employing personnel with experience level and education as outlined in Section 9.3 and 9.4 that pertain to the labor categories specified. In addition to possessing clearance, certification (cert) and specific requirements for each labor category by level, personnel employed for each labor category will also possess the ability to perform SOW tasks that correspond with the labor category https://www.ecmra.mil/

Page | 13 and knowledge of documents/regulations that align with the specific labor category. The Standard Occupational Codes (SOC) are in accordance with the Bureau of Labor Statistics 2018 Standard Occupational Classification System.

Labor Category

SOC FTE Duty Location

Level Clear-ance

Cert Specific Requirements

Program Manager

11-

1 Contractor Senior Top Secret

PMP • Ability to fulfill tasks at SOW 3.1 and oversee contractor personnel associated with all other tasks on this

TO

• Demonstrated experience with flag-officer level briefings and senior-level interface

• Demonstrated knowledge of DoD 5000 series (DoD acquisition)

Finance Manager

13-

1 Contractor Senior Secret N/A • Ability to fulfill tasks at SOW 3.2

Total FTE: 2 (3,840 hours)

9.2.1.1 Minimum Education. Refer to Paragraph 9.3. For the Program Manager, the required degree shall be in Management, Administration, Business, Science or related discipline. For the Finance Manager, the required degree shall be in Business, Finance, Accounting or related discipline. Refer to Paragraph 9.4 for allowable substitution for lack of the required degree level.

9.2.1.2 Minimum Experience. Refer to Paragraph 9.3. The Program Manager must have the minimum required experience in: senior-level management including managing large teams (20 or more personnel); processes and procedures in major acquisition programs; demonstrated education and/or training in business and management; and possess knowledge of aircraft programs and systems. The Program Manager must also possess Subject Matter Expert (SME) level knowledge of the Air Staff/OSD organizations and processes, SME-level knowledge of Service and OSD policy and documentation related to PPBS, life-cycle management of military acquisition programs (as specified in the DoD 5000 series), and proven interpersonal/communication/briefing skills as the senior level. The Finance Manager must have the minimum required experience in: senior-level financial management and budgeting. The contractors shall have a the appropriate clearance as captured in paragraph 9.2 above with a Periodic Reinvestigation no older than five years for all positions under this TO.

Page | 14

9.3 Experience Level Definition. The contractor shall be responsible for employing personnel with the qualifications and skills required to successfully accomplish the tasking outlined in the SOW. The experience required in this TO is different from the standard at the ID/IQ level. The professional labor category experience and education requirements corresponding to the three levels specified for this TO (Junior, Mid and Senior) are as follows:

• JUNIOR: N/A for this TO

• MID: N/A for this TO

• SENIOR: A Senior level person within a labor category for this TO must have ten or more years of experience performing work related to the labor category functional description and a MA/MS degree, or a qualifying substitution as identified in Section

9.4. Six years must pertain specifically to the labor category (e.g. a Finance Manager must have at least six years performing duties specific to Finance Management) while the remaining experience must pertain to a related labor category (e.g. Accounting). A Senior level person typically works on high-visibility or mission critical aspects of a given program and performs all functional duties independently. A Senior level person may oversee the efforts of less senior staff and/or be responsible for the efforts of all staff assigned to a specific job.

9.4 Education Level Substitution. The following qualification substitution chart details the combination of education/experience that can be used as a substitute for the degree requirements applicable to the above experience/education levels, except as noted at the task order level:

Bachelor’s Degree 6 years of additional work experience related to the labor category functional description may be substituted for a Bachelor’s Degree Associate’s Degree plus 4 years of additional work experience related to the labor category functional description may be substituted for a Bachelor’s Degree.

Master’s Degree Bachelor’s Degree plus 4 years additional work experience related to the labor category functional description may be substituted for a Master’s Degree.

• Note: All degrees shall be obtained from an accredited college or university as recognized by the U.S. Department of Education

10.0 ATTACHMENTS

• Attachment 1 – Applicable Documents – Refer to ID/IQ

• Attachment 2 – Level of Effort – See SOW 9.2 (No Separate Attachment)

• Attachment 3 – Service Summary

• Attachment 4 - Purchase Request Form - Refer to ID/IQ

• Attachment 5 - Travel Authorization Request Form - Refer to ID/IQ

Page | 15

Attachment 3

Task Order Service Summary

Performance Objective Performance Standard Performance Threshold

Provide qualified personnel for task order performance

Qualified personnel are in place for task order performance

Performance is acceptable when qualified personnel are in place for task order performance no later than (NLT) 45 calendar days following task order award unless authorized by the Contracting Officer

Retain personnel with specified qualifications

Effectively replaces / substitutes personnel

Performance is acceptable when task order vacancies do not exceed 30 calendar days

Deliverables Management

Develop and submit all required deliverables

Performance is acceptable when:

a) 100% of deliverable requirements are met and received on time*; AND

b) Information is current and accurate

*Non-current or inaccurate deliverables (or those with conflicting information) may be considered late