Attachment_8_Task_Order_1_-_AME_SME_PWS.pdf

PERFORMANCE WORK STATEMENT (PWS)

The Undersecretary of Defense for Policy (USD(P)) and The Defense Security Cooperation Agency (DSCA)

Assessment, Monitoring, and Evaluation (AM&E) of Security Cooperation Programs Task Order #1 – AM&E Subject Matter Expertise (SME)

PART 1

GENERAL INFORMATION

1. GENERAL. This is a nonpersonal services task order to provide subject matter expertise (SME) support services to the Assessment, Monitoring, and Evaluation (AM&E) of Security Cooperation Programs. The Government will not exercise any supervision or control over the contract service providers performing the services herein. Such contract service providers shall be accountable solely to the Contractor who, in turn, is responsible to the Government.

1.1 Description of Services/Introduction: The Contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to provide SME support services to the AM&E Security Cooperation Programs as defined in this Performance Work Statement (PWS) except for those items specified as Government furnished property and services. The Contractor shall perform to the standards in this task order.

1.2 Background: The National Defense Authorization Act (NDAA) for Fiscal Year (FY) 2017, contained sweeping reforms to the Department of Defense’s security cooperation (SC) authorities. These reforms were enacted as Chapter 16 of title 10, United States Code (U.S.C.)

(hereafter, “Chapter 16”). Section 383 of Chapter 16 (hereafter “Section 383”) requires that the Secretary of Defense maintain a program of assessment, monitoring, and evaluation (AM&E) in support of security cooperation programs and activities of the Department of Defense (DoD). The elements of this program include the following:

• Initial assessments of partner capability requirements, potential programmatic risks, baseline information, and indicators of efficacy for purposes of planning, monitoring, and evaluation of security cooperation programs and activities of the DoD.

• Monitoring of implementation of such programs and activities in order to measure progress in execution and, to the extent possible, achievement of desired outcomes.

• Evaluation of the efficiency and effectiveness of such programs and activities in achieving desired outcomes.

• Identification of lessons learned in carrying out such programs and activities, and development of recommendations for improving future security cooperation programs and activities within DoD.

1.3 Objectives: The overall objective of this acquisition is to provide the U.S. Department of Defense (DoD) with SME support services to the AM&E of Security Cooperation Programs.

1.4 Scope: Scope of work performed includes a broad range of assessment, monitoring, and evaluation expertise to implement the new AM&E requirements. This includes expertise in planning and conducting evaluations that are based on standards articulated by the American Evaluation Association and the Development Assistance Committee of the Organization for Economic Cooperation and Development, as required by DoDI 5132.14. Requirements also include access to expertise to facilitate the development of initial assessments, initiative design documents, and monitoring of security cooperation programs and activities.

1.5 Period of Performance: The period of performance is for a 12-month base period and four 12-month option periods.

1.6 General Information:

1.6.1 Type of Contract: The Government will award a hybrid task order which consist of firm-fixed price (FFP) and labor-hour (LH) CLINS.

1.6.2 Quality Control: The Contractor shall develop and maintain an effective quality control program to ensure services are performed in accordance with this PWS. The Contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The Contractor’s quality control program (QCP) is the means by which he assures himself that his work complies with the requirement of the contract. The QCP shall be delivered via electronic mail within ten (10) days of task order award. Amendments/changes to the QCP shall be delivered to the Contracting Officer’s Representative (COR) and Contracting Officer (KO) within three (3) business days following any change.

1.6.3 Quality Assurance: The Government will evaluate the Contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan (QASP). This plan is primarily focused on what the Government must do to ensure that the Contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s).

1.6.4 Recognized Holidays: Contractor personnel are not customarily expected to work on holidays, but holiday work is possible, subject to advance scheduling with the Contractor.

Recognized Federal holidays are as follows:

New Year’s Day Labor Day Martin Luther King Jr.’s Birthday Columbus Day President’s Day Veteran’s Day Memorial Day Thanksgiving Day Independence Day Christmas Day

1.6.5 Hours of Operation: The Contractor is responsible for conducting business Monday through Friday except U.S. Federal Holidays (unless holiday work is approved and scheduled in advance) or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. For other than firm-fixed price task orders, the Contractor will not be reimbursed when the Government facility is closed for the above reasons. Workers typically work eight (8) hours per day, 40 hours per week.

Flextime workers start not earlier than 0600 and not later than 0900. Core hours of work are from 0900 to 1500 daily. All employees are expected to be available during core hours as required.

When the Government grants administrative leave to Government employees, or is closed as a result of inclement weather, potentially hazardous conditions, or other special circumstances, Contractor personnel working at the specific facility/location granted administrative leave may also be dismissed at the discretion of the On-site Manager to the extent that the overall performance is not adversely impacted. The Contractor shall at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS when the Government facility is not closed for the above reasons. The Contractor shall provide the COR a current schedule for its entire staff assigned to the contract, including planned leave. The

Contractor shall assign alternates to cover assignments of any of its staff that are absent sufficient to ensure that the services are not disrupted.

1.6.6 Place of Performance: The work to be performed under this task order will be performed at various Government Continental United States (CONUS) and Outside Continental United States

(OCONUS).

1.6.7 Security Requirements: Contractor personnel performing work under this task order shall have at a minimum a favorable National Agency Check (NAC). All personnel performing tasks associated with Part 5 and listed in Technical Exhibit 3 must have a minimum of a Secret clearance. Deliverables will be Unclassified when possible, but may be classified Secret if directed by OUSD Policy. The security requirements are in accordance with the attached DD254.

1.6.7.1 Physical Security: The Contractor shall be responsible for safeguarding all Government equipment, information and property provided for Contractor use. At the close of each work period, Government facilities, equipment, and materials shall be secured.

1.6.7.2 Key Control: The Contractor shall establish and implement methods of making sure all keys/key cards issued to the Contractor by the Government are not lost or misplaced and are not used by unauthorized persons. NOTE: All references to keys include key cards. No keys issued to the Contractor by the Government shall be duplicated. The Contractor shall develop procedures covering key control that shall be included in the Quality Control Plan. Such procedures shall include turn-in of any issued keys by personnel who no longer require access to locked areas. The Contractor shall immediately report any occurrences of lost or duplicate keys/key cards to the Contracting Officer.

1.6.7.2.1. In the event keys, other than master keys, are lost or duplicated, the Contractor shall, upon direction of the Contracting Officer, re-key or replace the affected lock or locks; however, the Government, at its option, may replace the affected lock or locks or perform re-keying. When the replacement of locks or re-keying is performed by the Government, the total cost of re-keying or the replacement of the lock or locks shall be deducted from the monthly payment due the Contractor. In the event a master key is lost or duplicated, all locks and keys for that system shall be replaced by the Government and the total cost deducted from the monthly payment due the Contractor.

1.6.7.2.2. The Contractor shall prohibit the use of Government issued keys/key cards by any persons other than the Contractor’s employees. The Contractor shall prohibit the opening of locked areas by Contractor employees to permit entrance of persons other than Contractor employees engaged in the performance of assigned work in those areas, or personnel authorized entrance by the Contracting Officer.

1.6.7.3 Lock Combinations: The Contractor shall establish and implement methods of ensuring that all lock combinations are not revealed to unauthorized persons. The Contractor shall ensure that lock combinations are changed when personnel having access to the combinations no longer have a need to know such combinations. These procedures shall be included in the Contractor’s Quality Control Plan.

1.6.8 Post Award Conference/Periodic Progress Meetings: The Contractor agrees to attend any post award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5. The Contracting Officer, Contracting Officers Representative (COR), and other Government personnel, as appropriate, may meet periodically with the Contractor to review the Contractor's performance. At these meetings the contracting officer will apprise the Contractor of how the Government views the Contractor's performance and the Contractor will apprise the Government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the Government.

1.6.9 Contracting Officer Representative (COR): The (COR) will be identified by separate letter.

The COR monitors all technical aspects of the contract and assists in contract administration. The COR is authorized to perform the following functions: assure that the Contractor performs the technical requirements of the contract; perform inspections necessary in connection with contract performance; maintain written and oral communications with the Contractor concerning technical aspects of the contract; issue written interpretations of technical requirements, including Government drawings, designs, specifications; monitor Contractor's performance and notifies both the Contracting Officer and Contractor of any deficiencies; coordinate availability of Government furnished property, and provide site entry of Contractor personnel. A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost or price, estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting order.

1.6.10 Key Personnel: The Contractor shall provide qualified personnel for the following key position (one) CONUS Program Manager who will serve as the primary liaison and point of contact for the contract. The Contractor shall provide a resume and letter of commitment with their proposal for the proposed Program Manager.

1.6.10.1 Program Manager.

Program Manager will have minimum/general experience 10 years’ of program or executive-level management experience with emphasis on project cost, schedule, performance, requirements management and experience leading multi-disciplinary teams of analysts, and other personnel, including requirements gathering, design, implementation, and on-going program management.

Additionally, experience running a project/program with a geographically distributed staff. Must meet minimum education requirement of Master’s degree in related field.

Functional Responsibility: The Program Manager will assume responsibility for overall management and functioning of task order activities. This includes overseeing all aspects of contract performance for required assessment, monitoring, and evaluation support activities.

Identify appropriate staffing levels, secure appropriate qualified staff, and report on required deliverables. Must maintain a Secret clearance.

Desired Other Qualifications:

• Demonstrated understanding of planning, designing and implementing assessment, monitoring and evaluation programs or projects in the security sector;

• Demonstrated understanding of organizational differences at the GCCs and how to adequately support them;

• Knowledge and experience designing tools for data collection such as survey instruments, data collection and reporting tools, analyzing the resultant data using quantitative and qualitative methods.

1.6.11 Non-Key Personnel: The Government understands that assessment, monitoring, and evaluation in the security cooperation framework is a developing field of expertise and desires a team willing to work within a dynamic and changing environment.

1.6.11.1 Project Manager.

Project Manager minimum/general experience eight (8) years’ experience in project management leading multi-disciplinary teams of analysts, and other personnel, including requirements gathering, design, implementation, and ongoing program management with demonstrated ability to identify requirements for full-spectrum security cooperation planning.

Functional Responsibility: Assists in planning and coordinating security cooperation PA and IDD development. At the GCCs, acts as the Assessment, Monitoring, and Evaluation Fusion Cell (AFC) team lead. Applies OSD Policy guidance including ensuring all required planning tools and products are completed, coordinated, and delivered on time. Engages with OSD Policy, DSCA, and Department security cooperation stakeholders on AM&E planning, implementation, and issues. Manages AFC personnel involved in all aspects of security cooperation activities, organizes and assigns responsibilities, and oversees the successful completion of all assigned tasks. Must maintain a Secret clearance.

Desired Other Qualifications:

• 8-10 years of management experience, leading multi-disciplined teams of analysts, and other personnel;

• Demonstrated ability to align needed subject matter experts to identified requirements, such as logistics, human resources, capability gap analysis;

• Experience planning, designing and implementing assessment, monitoring and evaluation programs or projects in the security sector;

• Knowledge of change management principles;

• Knowledge of the GCCs security cooperation portfolios;

• Master’s degree in related field.

1.6.11.2 Program Analyst.

Program Analyst minimum/general experience five (5) years’ experience with security cooperation programs and procedures. Must meet minimum education of a Bachelor’s degree.

Functional Responsibility: Assist Senior Program Analysts in the development and implementation of security cooperation programs by working across the Department and with key interagency and state partners, the broader security cooperation community, stakeholders, and interest groups. Participates with OSD Policy and DSCA in developing, supporting, and progressing security cooperation programs, activities, and initiatives. Supports program management, planning, logistics and administrative requirements, and interagency coordination in the field. Keeps abreast of new policies, procedures, regulations, and directives affecting security cooperation activities.

Desired Other Qualifications: Personnel should have subject matter expertise in the following functional areas: assessments and monitoring of key security cooperation functions such as strategy/policy, defense institution building/institutional capacity building, logistics, human resource management, resource management, and protection of civilians/SSR/civil sector/human rights. Efforts will support activities detailed in 5.1 and 5.2 of the task order.

1.6.11.3 Sr. Program Analyst.

Sr. Program Analyst minimum/general experience 10 years’ experience developing and implementing security cooperation policies, procedures, and programs. Must meet minimum education of a Bachelor’s degree.

Functional Responsibility: Serves as a senior advisor in the development and implementation of security cooperation programs and activities by working across the Department and with key interagency and state partners, the broader security cooperation community, stakeholders, and interest groups. Advises and participates in assessment, monitoring, and evaluation of security cooperation programs. Supports OSD Policy and DSCA in developing, supporting, and progressing security cooperation programs, activities, and initiatives and provides interagency coordination in the field. Keeps abreast of new policies, procedures, regulations, directives, and recommends changes to the agency.

Desired Other Qualifications: Personnel should have subject matter expertise in the following functional areas: assessment and monitoring of key security cooperation functions strategy/policy, defense institution building/institutional capacity building, logistics, human resource management, resource management, and protection of civilians/SSR/civil sector/human rights.

Knowledge of monitoring and data collection. Efforts will support activities detailed in 5.1 and

5.2 of the task order. Bachelor’s degree of Arts or Sciences.

1.6.12 Identification of Contractor Employees: All Contractor personnel attending meetings, answering Government telephones, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are Government officials. They must also ensure that all documents or reports produced by contractors are suitably marked as contractor products or that contractor participation is appropriately disclosed.

1.6.13 Contractor Travel: The Contractor may be required to travel CONUS and within the NCR during the performance of this task order. The Contractor will be authorized travel expenses consistent with the substantive provisions of the Joint Travel Regulation (JTR) and the limitation of funds specified in this task order. The Contractor shall submit a travel estimate to and obtain written approval from the COR before incurring any reimbursable travel expenses.

Reimbursement of expense shall be in accordance with FAR 31.205-46. The Contractor shall be reimbursed for actual expenses incurred, and allowable based on FAR 31.205-46 travel related expenses.

The Department of State Standardized Regulations (DSSR) govern allowances and benefits available to U.S. Government civilians assigned to foreign areas. Similarly, for work conducted under this PWS, the DoD requiring activity and COR will use DoD established guidelines formulated based on DSSR, Chapter 100, Section 130 and any other pertinent guidance found in the DSSR, to determine in advance Contractor eligibility for receipt of Overseas Cost of Living Allowances (COLA) and Overseas Housing Allowances (OHA) and to govern Contractor documentation and reimbursement of OHA/COLA expenses.

1.6.14 Other Direct Costs: There will be travel requirements to support assessment and monitoring roles within the PWS. Additionally, OCONUS relocation costs are expected.

1.6.15 Data Rights: The Government has unlimited rights to all documents/material produced under this contract. All documents and materials, to include the source codes of any software, produced under this contract shall be Government owned and are the property of the Government with all rights and privileges of ownership/copyright belonging exclusively to the Government.

These documents and materials may not be used or sold by the Contractor without written permission from the Contracting Officer. All materials supplied to the Government shall be the sole property of the Government and may not be used for any other purpose. This right does not abrogate any other Government rights.

1.6.15.1 The Contractor, without the written consent of the DoD, shall not provide any supporting documents, data files, reports, correspondence, and all other documents and writings, together with any charts, graphs, tables, illustrations, photographs, images, and other illustrative, explanatory, historical documents related thereto or independent thereof to any party outside of DoD, regardless of the medium (or media) by which they were produced, preserved, stored, or created. All documents, data files, reports, correspondence, and all other documents and writings, produced under this PWS and contract, are property of the Government and shall be delivered to the COR promptly, upon request.

1.6.15.2 The Contractor agrees to assume responsibility for protecting the confidentiality of Government records, which is not considered public information. Each Contractor or employee of the Contractor to whom information may be made available or disclosed shall be notified in writing by the Contractor that such information may be disclosed only for purposes and to the extent authorized herein. The Contractor shall not release any information related to this contract to the public, media or other unauthorized persons or organizations unless the Government has conducted the appropriate security review and granted written approval (e.g. posting information to a public website). The Contractor shall safeguard classified and unclassified information provided or generated under this contract.

1.6.15.3 The Contractor is responsible for obtaining non-disclosure agreements from all employees working under this task order, and all applicable corporate, supplier, and sub-tier vendors with proprietary, restricted, competition sensitive, or any other restricted (e.g. non-foreign disclosure due to public law) data that will be used or accessed during the duration of this contract.

1.6.16 Organizational Conflict of Interest: The Contractor and subcontractor personnel performing work under this contract may receive, have access to or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications or work statements, etc.) or perform evaluation services which may create a current or subsequent Organizational Conflict of Interests (OCI) as defined in FAR Subpart 9.5. The Contractor shall notify the Contracting Officer immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the Contracting Officer to avoid or mitigate any such OCI. The Contractor’s mitigation plan will be determined to be acceptable solely at the discretion of the Contracting Officer and in the event the Contracting Officer unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the Contracting Officer may use other remedies as he or she deems necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI.

1.6.17 Special Considerations due to Overseas Location:

In processing and initial training will be required prior to deployment to overseas locations. This includes, but is not limited to CAC issuance. The contractor's deployment date will be submitted to the Government for approval by the PM or COR at least 30 days prior to deployment execution.

Contractor will produce a Transition Plan as part of the task order proposal and update the plan 180 days after initial contract award to capture any additional information and/or lessons learned.

The plan will identify to the Government that the contractor has a plan in place to transition personnel both to and from the overseas place of performance as well as the transition period when personnel replacements occur. The plan should include such topics as how the contractor will transition overseas, to include timelines for events such as on-boarding, predeployment training, travel to the overseas location, the process to transition a new contractor heading overseas and the associated turnover process, and redeployment of a contractor transitioning back to the U.S. who will no longer support the task order. This plan will be submitted to the Government PM/COR for review and approval.

1.6.18 Phase-In Period: The Contractor shall have personnel on board, during the thirty (60) calendar days phase-in. During the phase-in period, the Contractor shall become familiar with performance requirements in order to commence performance of services for the PWS task areas described in Section 5.

1.6.18.1 Phase-In Plan Requirements.

The Contractor should prioritize phase-in of CLIN 1 requirements. CLIN 2 phase-in should begin in FY 2020. The Contractor shall:

(1) Deliver the Phase-In Plan as part of the proposal

(2) Obtain system documentation and verify system and facility access

(3) Conduct transition meetings with Government leadership

(4) Transition high quality incumbent personnel, re-badge, and conduct orientations

(5) Provide all contractor services from the award date

(6) Provide key and non-key personnel that must meet all qualifications and requirements specified in this PWS by functional area upon in-processing. The functional areas are PWS section 5.1 to 5.8.14.

1.6.18.2 Mobilization / Registration.

The Contractor shall establish a physical presence in each CONUS and Hawaii location and mobilize personnel to each no later than sixty (60) days from award.

The government is aware of potential delays fielding individuals to Germany based on Status of Forces Agreement (SOFA) requirements. In compliance with German laws and regulations, the Contractor shall establish a legal presence to manage and integrate the efforts of this task order.

We have separated the Germany FTEs to a separate CLIN in order to address potential delays in fielding the team to this location. The Offeror shall address this phase-in requirement in the management section.

1.6.19 Phase Out Period: The Contractor shall provide a phase-out plan no later than sixty (60) days prior to expiration of this task order. The Contractor shall maintain complete documentation that is totally assessable to the designated Government representatives via a web portal or some other portal as the Government directs. The Contractor shall overlap with incoming Contractor during transition for a nominal period of 30 days and will work with Government personnel and the incoming contractor to transfer knowledge, information and documentation for all projects and tasks related to this contract. The type of information and documentation to be transferred includes but is not limited to:

• Project management processes,

• Points of contacts,

• Location of technical and project management documentation,

• Program data, data bases and data management systems,

• Status of ongoing technical initiatives,

• Appropriate contractor to contractor coordination to ensure a seamless transition,

• Identify schedules and milestones,

• Identify actions required of the Government,

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

Note: All automated data files in the possession of the Contractor are the property of the Government and shall be turned over to the KO or the COR at the completion or termination of the task order. Additionally, all records related to the execution of the current contract shall be returned to the Government as electronic copies that are readable and accessible by the Government.

1.6.20 Contractor Manpower Reporting:

(a) The Contractor shall report all Contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract via a secure data collection site.

The Contractor is required to completely fill in all required data fields using the following web address: http://www.ecmra.mil/.

(b) There are four separate ECMRA tools at the ECMRA website: Army, Air Force, Navy and All Other Defense Components. The appropriate ECMRA reporting tool to use is determined by the requiring activity being supported by the service. The Contractor shall use the “All Other Defense Components” tool unless otherwise directed by the Contracting Officer’s Representative or Contracting Officer.

(c) Reporting inputs will be for the labor executed 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. The Contractor shall completely fill in all required data fields. The Contractor shall enter initial data into the appropriate ECMRA tool to establish the basic contract record no later than 15 business days after receipt of contract award or contract modification incorporating this clause. The Contractor shall notify the Contracting Officer when the basic contract record has been established in the appropriate ECMRA tool.

(d) Contractors may direct technical questions to the help desk at: http://www.ecmra.mil.

[Reference: DPAP memorandum of 28 November 2012, “Enterprise-wide Contractor Manpower Reporting] http://www.ecmra.mil/ http://www.ecmra.mil/

PART 2

DEFINITIONS & ACRONYMS

2. DEFINITIONS AND ACRONYMS.

2.1 DEFINITIONS:

2.1.1 CONTRACTOR. A supplier or vendor awarded a contract to provide specific supplies or service to the Government. The term used in this contract refers to the prime.

2.1.2 CONTRACTING OFFICER. A person with authority to enter into, administer, and or terminate contracts, and make related determinations and findings on behalf of the Government.

Note: The only individual who can legally bind the Government.

2.1.3 CONTRACTING OFFICER'S REPRESENTATIVE (COR). An employee of the U.S.

Government appointed by the contracting officer to administer the contract. Such appointment shall be in writing and shall state the scope of authority and limitations. This individual has authority to provide technical direction to the Contractor as long as that direction is within the scope of the contract, does not constitute a change, and has no funding implications. This individual does NOT have authority to change the terms and conditions of the contract.

2.1.4 DEFECTIVE SERVICE. A service output that does not meet the standard of performance associated with the Performance Work Statement.

2.1.5 DELIVERABLE. Anything that can be physically delivered, but may include non-manufactured things such as meeting minutes or reports.

2.1.6 KEY PERSONNEL. Contractor personnel that are evaluated in a source selection process and that may be required to be used in the performance of a contract by the Key Personnel listed in the PWS. When key personnel are used as an evaluation factor in best value procurement, an offer can be rejected if it does not have a firm commitment from the persons that are listed in the proposal.

2.1.7 PHYSICAL SECURITY. Actions that prevent the loss or damage of Government property.

2.1.8 QUALITY ASSURANCE. The Government procedures to verify that services being performed by the Contractor are performed according to acceptable standards.

2.1.9 QUALITY ASSURANCE. Surveillance Plan (QASP). An organized written document specifying the surveillance methodology to be used for surveillance of Contractor performance.

2.1.10 QUALITY CONTROL. All necessary measures taken by the Contractor to assure that the quality of an end product or service shall meet contract requirements.

2.1.11 SUBCONTRACTOR. One that enters into a contract with a prime contractor. The Government does not have privity of contract with the subcontractor.

2.1.12 WORK DAY. The number of hours per day the Contractor provides services in accordance with the contract.

2.1.12 WORK WEEK. Monday through Friday, unless specified otherwise.

2.2 ACRONYMS:

ACOR Alternate Contracting Officer's Representative CFR Code of Federal Regulations CONUS Continental United States (excludes Alaska and Hawaii) COR Contracting Officer Representative COTS Commercial-Off-the-Shelf DD Form 254 Department of Defense Contract Security Requirement List DFARS Defense Federal Acquisition Regulation Supplement DOD Department of Defense ECMRA Enterprise-wide Contractor Manpower Reporting FAR Federal Acquisition Regulation GCCs Geographic Combatant Commands IDD Initiative Design Document KO Contracting Officer OCI Organizational Conflict of Interest OCONUS Outside Continental United States (includes Alaska and Hawaii) ODC Other Direct Costs PIPO Phase In/Phase Out POC Point of Contact PRS Performance Requirements Summary PWS Performance Work Statement QA Quality Assurance QAP Quality Assurance Program QASP Quality Assurance Surveillance Plan QC Quality Control QCP Quality Control Program TE Technical Exhibit TO Task Order WHS Washington Headquarters Services

PART 3

GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, AND SERVICES

3. GOVERNMENT FURNISHED ITEMS AND SERVICES.

3.1 Facilities: The Government will provide the necessary workspace for the Contractor staff to provide direct support outlined in the PWS to include desk space.

3.2 Utilities: The Government will provide basic work space and its associated operating requirements (i.e., phones, desks, utilities, information technology, and general office supplies) while working in Government facilities. The Contractor shall instruct employees in utilities conservation practices. The Contractor shall be responsible for operating under conditions that preclude the waste of utilities, which include turning off the water faucets or valves after using the required amount to accomplish cleaning vehicles and equipment.

PART 4

CONTRACTOR FURNISHED ITEMS AND SERVICES

4. CONTRACTOR FURNISHED ITEMS AND RESPONSIBILITIES.

4.1 General: The Contractor shall furnish all supplies, equipment, facilities and services required to perform work under this contract that are not listed under Section 3 of this PWS.

4.2 Facility Clearance: The Contractor shall possess and maintain at a minimum an active Secret clearance from the Defense Security Service. The DD 254 is provided as an Attachment.

PART 5

SPECIFIC TASKS

5.0 TASKS. The Contractor shall support OUSD(P) and the SC enterprise with planning, assessments, monitoring, evaluation support, and the implementation of lessons learned.

Evaluations will be directly implemented in functional area three of this IDIQ, or by other government partners, and is therefore not expected to be completed as part of this task order. The focus of this effort is to support the GCCs, Services, and Department in the implementation of the new requirements such as identification of comprehensive institutional capacity building capability opportunities to support security cooperation sustainability, develop logic frameworks, theories of change, and performance indicators to measure progress.

5.1. Embedded subject matter experts (SME) at the Geographic Combatant Commands (GCCs), Services, Special Operations Command, and components will support security cooperation AM&E initiatives. At the GCCs, the SMEs will form Assessment, Monitoring, and Evaluation Fusion Cells (AFCs). The AFCs will support GCC security cooperation planning, including the development of partnership assessments, initiative design documents, and monitoring of security cooperation programs and activities. Personnel assigned to this task will be Program Analysts, Sr.

Program Analysts, and Project Managers. For a breakdown of labor categories, locations, and FTE against this task, view Technical Exhibit 3.

5.1.1 AM&E SMEs at the GCCs, Services, Special Operations Command, and components should provide the following functional expertise: assessment of key security cooperation functions, monitoring, strategy/policy, defense institution building/institutional capacity building, logistics, human resource management, resource management, and protection of civilians/SSR/civil sector/human rights. Knowledge of monitoring and data collection. Please note that evaluations will be primarily handled through individual task orders, but the implementer of this task order will be expected to support the evaluations and provide support to program level evaluations.

• Apply OSD Policy-issued AM&E guidance, templates, and frameworks;

• Provide support for partnership assessments PAs), which are the first stage of the SC planning process, where the staff critically analyzes both U.S. strategic guidance and the international environment. The PAs also provide a record of the thinking at the beginning of an engagement, which is critical to the success of any future evaluation that seeks to measure how effective we were in meeting the SSCI objective. That analysis should include, but is not limited, to the following areas of analysis/research:

o Analysis of strategic context and U.S. interests in the country or region o Partner nation view of strategic context and priorities o Description of institutional and operational capacity of security sector and supporting agencies/organizations o Partner nation view of institutional and operational capacity and priorities o Analysis of bilateral relationship(s) o Partner nation absorptive capacity o Rule of law and human rights in the partner nation o Analysis of security cooperation opportunities o Identification of significant security cooperation initiatives and objectives o Effectiveness of partner nation approach(s) in achieving the desired effect of strategy o Identification of capacity and institutional gaps in the partner nation o Identification /analysis of the willingness and ability of the partner nation to make changes o Analysis of the strength/deficiencies of the bilateral relationship with the partner nation across stakeholders o Identification of related efforts currently ongoing that impact the desired partner nation role o Assessment of the risk of the partner’s ability to perform the desired role o Development of baseline measures, indicators of success, and milestones

• Perform pre-activity assessments and program monitoring in conjunction with other support staff, including government employees and designated federally funded research and development corporations;

• Identify gaps in partner nation institutional capacity, especially in four key areas:

policy/strategy, logistics, resource management, and human resource management;

• Develop plans to improve and develop partner nation institutional capacity and capability;

• Develop initiative design documents (IDD) related to security cooperation activities in a country. The IDD is intended to spell out enough of the design of the SSCI to inform funding decisions and lay the ground work for subsequent design. It is the presentation of a lot of staff work, working through the rationale as to why we believe a given set of activities will result in the desired outcomes. These include logic frameworks, theories of change, and performance indicators that include, but are not limited to, the following areas of analysis:

o Identify the desired security cooperation (SC) objective in the multi-year guidance and other relevant strategic objectives the SC initiative contributes to.

o Develop a theory of change that states why SC efforts enable the partner to perform the desired role(s) will contribute to the SSCI Objective. How do we expect our actions will contribute to changes in partner behavior (e.g. will, capacity, relationship) over time to fulfill the desired role?

o Identify the governance and management roles required to guide, absorb, and employ capabilities in the short to medium term and sustain capabilities long term.

o Describe the concept of operations for any improvements in operational effectiveness by describing the military concept of operations that the effort will support. Identify specific units or organizations responsible.

o Identify the partner nations support role and the specific combat support and combat service support roles required to achieve desired partner role at the required level of performance.

o Identify specific capability development requirements to address gaps necessary for performing the operational, support, and policy and governance roles identified.

o Determine partner nation compliance with human rights and the rule of law.

o Clearly detail assumptions in developing the logic framework for each objective and associated connection.

o Identify specific political risks from the Partnership Assessment that are relevant to initiative implementation and include a mitigation approach.

o Identify constraints and potential requirements for conducing the initiative, the effects, and mitigation measures.

• Develop monitoring plans (with indicators, baseline values, targets, and data collection support responsibilities) and conduct monitoring of security cooperation projects and activities;

• Support the execution of evaluations to include sitting for interviews, providing requested documentation, and supporting stakeholders with the evaluation process. Information provided for evaluations should support the analysis of the effectiveness of security cooperation programs in impacting the plans, concepts, organizations, and requirements of partner nations;

• Support, facilitate, and complete the documentation of five year plans that sequence activities and authorities necessary over five years to enable partner nation roles and address capability gaps with associate ROM projections by fiscal year;

• Track the partner nation recipient units’ integration of training and equipment into their processes, techniques, and operations;

• Maintain relationships with broader DoD entities and organizations to facilitate communication and exchange across GCCs and security cooperation stakeholders.

5.1.2 The estimated number of SMEs for this task is broken down as follows (68 SMEs):

• USAFRICOM, USCENTCOM, USSOUTHCOM: 6 AFC SMEs per GCC

• USEUCOM, USINDOPACOM: 8 AFC SMEs per GCC

• USNORTHCOM: 4 AFC SMEs

• Air Force: 5 SMEs (distributed across Service Headquarters and components)

• Army: 6 SMEs (distributed across Service Headquarters and components)

• Navy/USMC: 12 SMEs (distributed across Service Headquarters and components)

• SOCOM: 7 SMEs (distributed across the Headquarters command and components)

5.2 AM&E SMEs at DSCA, Joint Staff, and OSD Policy should provide the following functional expertise: assessment, monitoring, strategy/policy, defense institution building/institutional capacity building, logistics, human resource management, resource management, and protection of civilians/SSR/civil sector/human rights. Personnel assigned to this task will be Program Analysts, Sr. Program Analysts, Project Managers, and a Program Manager. For a breakdown of labor categories, locations, and FTE against this task, view Technical Exhibit 3.

5.2.1 SMEs at DSCA, Joint Staff, and OSD Policy will support security cooperation AM&E initiatives at the institutional level. Expertise should include program design, program management, and implementation of security cooperation guidance, templates, lessons learned, projects and activities as needed.

• Apply OSD Policy-issued AM&E guidance, templates, and frameworks;

• Support the development, review, and adjudication of partnership assessments;

• Analyze identified gaps in partner nation institutional capacity, especially in four key areas: policy/strategy, logistics, resource management, and human resource management;

• Identify areas and support plans to improve and develop partner nation institutional capacity and capability;

• Support the development, review, and coordination of initiative design documents including logic frameworks, theories of change, and performance indicators;

• Support monitoring of security cooperation projects and activities where required.

• Maintain relationships with broader DoD entities and organizations to facilitate communication and exchange across GCCs and security cooperation stakeholders.

5.2.2 The estimate FTE for SMEs for this task is broken down as follows (10 SMEs):

• DSCA: 4 SMEs

• Joint Staff: 1 SME

• OSD Policy: 5 SMEs (1 FTE will act as the Program Manager)

PART 6

APPLICABLE PUBLICATIONS

6. APPLICABLE PUBLICATIONS (CURRENT EDITIONS).

6.1. The Contractor shall abide by all applicable regulations, publications, manuals, and local policies and procedures. Reference documents include:

• Deputy Secretary of Defense memorandum of August 29, 2016 “DoD Guidance for Security Cooperation”

• DoDD 5132.03, “DoD Policy and Responsibilities Relating to Security Cooperation,” December 29, 2016

• DoDI 5132.14, “Assessment, Monitoring, and Evaluation Policy for the Security Cooperation Enterprise,” January 13, 2017

• Joint Publication 3-20, “Security Cooperation,” May 23, 2017

• Deputy Secretary of Defense Memorandum of January 05, 2018 “Guidance for Planning, and Assessment, Monitoring and Evaluation or DoD Security Cooperation Activities

• Government Performance and Results Act of 1993 (PL 103-62)

• Government Performance and Results Modernization Act of 2010 (PL 111-352)

PART 7

ATTACHMENT/TECHNICAL EXHIBIT LISTING

7. Attachment/Technical Exhibit List.

7.1. Attachment 1/Technical Exhibit 1 – Performance Requirements Summary

7.2. Attachment 2/Technical Exhibit 2 – Deliverables Schedule

7.3 Attachment 3/Technical Exhibit 3 – Estimated Workload Data

TECHNICAL EXHIBIT 1

PERFORMANCE REQUIREMENTS SUMMARY

The Contractor service requirements are summarized into performance objectives that relate directly to mission essential items. The performance threshold briefly describes the minimum acceptable levels of service required for each requirement. These thresholds are critical to mission success.

Requirements Performance Standards Acceptable Quality Level Method of

Surveillance Partnership Assessments (PWS Section 5.1)

Complete PA template

Each Partnership Assessment will be evaluated for completeness, reasonableness of strategic alignment, challenge identification, and soundness of end states and objectives.

ODASD/SC

Review

IDDs (PWS Section 5.1)

Complete IDD template

Each IDD will be evaluated on completeness, the alignment of activities to strategic end states, logic flow of course of action, soundness of rationale and theory of change, development of monitoring plans and five year plans. (All Annexes should be complete)

ODASD/SC

Review

Monitoring Plan (PWS Section 5.1)

Complete quarterly report

Provide initial approach and data collection requirements for each SSCI and provide identified data collection requirements in coordination with the CCMD and components. Quarterly provide status report on monitoring activities.

ODASD/SC

Review

Meeting Attendance Attend meetings hosted by

ODASD/SC,

DSCA, and SC stakeholders

Attendance includes but is not limited to progress reviews, planning meetings, and program reviews

ODASD/SC

Review

Monthly Activity/Status Report

Will include summary of labor hours for each functional category and itemized progress against initial stakeholder list

Standard project report providing update of ongoing activities, identified challenges, potential remedies, and burn rates.

ODASD/SC

Review

TECHNICAL EXHIBIT 2

DELIVERABLES SCHEDULE

All deliverables shall be submitted using Microsoft Office suite of tools (for example, MS Word, MS Excel, MS PowerPoint), or Adobe PDF format, unless otherwise specified by the COR.

Electronic submission shall be made via email, unless otherwise agreed to by the COR.

The COR has the right to reject or require correction of any deficiencies found in the deliverables.

In the event of a rejected deliverable, the Contractor will be notified in writing by the COR of the specific reasons for rejection.

The following table specifies the deliverables for this requirement. The Contractor is expected to adhere to the due dates for reference item 6.1-6.2. However, schedules for reference items 6.3-6.5 and beyond become dependent on a number of factors beyond the Contractor’s control including, but not limited to; force protection constraints, accessibility to Combatant Command and U.S.

Embassy locations, and availability of key stakeholders. The Contractor shall account for external schedule complications and will adjust staffing, billing and due dates of deliverables accordingly.

Delays in scheduling should not influence the labor hours required to complete a comprehensive strategic evaluation. Any reimbursable expenses (i.e., travel costs) incurred by the Contractor as a result of schedule delays shall be reimbursed by the government, provided all reimbursable expenses were previously approved and COR is notified of any increased costs due to external scheduling delays.

PWS

Ref. Deliverable Number of

Deliverables Due Date

6.1 Initial Meeting 1 NLT 7 days after award

(DoA)

6.2 Security Cooperation Basic

Course through the Defense Security Cooperation University

Certification required for all FTE over life of contract

NLT 30 days after personnel placement

6.3 Partnership Assessments TBD Due dates will be based on

annual guidance and Policy established suspense’s.

6.4 IDDs and Annexes TBD Due dates will be based on

annual guidance and Policy established suspense’s.

6.