PWS FOR ISRMAT RECOMPETE DRAFT - SSN (7-20-21).docx

PERFORMANCE WORK STATEMENT

FOR

Intelligence Surveillance Reconnaissance Mobile Advisory Team (ISRMAT) Support

Training and Doctrine Command Deputy Chief of Staff for Intelligence

As of 9July 2021

TABLE OF CONTENTS

SECTION C-1 GENERAL

SECTION C-2 ACRONYMS

SECTION C-3 GOVERNMENT FURNISHED PROPERTY AND

SERVICES

SECTION C-4 CONTRACTOR FURNISHED PROPERTY AND

SERVICES

SECTION C-5 SERVICES REQUIRED/SPECIFIC TASKS

SECTION C-6 PROGRAM MANAGEMENT SUPPORT/DELIVERABLES

SECTION C-7 DELIVERY, INSPECTION/ACCEPTANCE BY GOVT

SECION C-8 ANTI-TERRORISM/ SECURITY

SECTION C-9 ARMING FOR PERSONAL PROTECTION

SECTION C-10 DELIVERABLES

SECTION C -11 ATTACHMENTS AND FORMS

ATTACHMENT A NON-DISCLOSURE AGREEMENT FOR

CONTRACTORS

ATTACHMENT B SENSITIVE DATA NON-DISCLOSURE AGREEMENT

ATTACHMENT C TRAVEL AUTHORIZATION REQUEST FORM

ATTACHMENT D CUSTOMER FEEDBACK FORM

ATTACHMENT E PERFORMANCE REQUIREMENTS SUMMARY

(PRS)

C-1 GENERAL

1.0 Background. TRADOC’s Deputy Chief of Staff for Intelligence (G2) studies, designs, coordinates, and applies current and future Operational Environment (OE) in support of joint and Army programs for training and leader development, concept development, experimentation, and requirements determination. As part of executing this mission, TRADOC G2’s Joint Intelligence, Surveillance, and Reconnaissance (ISR) Directorate develops and provisions ISR integration training, aimed at Area of Responsibility (AOR)-focused, operating force unit-tailored training in employment of organic and non-organic ISR capabilities.

1.1 Scope. The mission of the TRADOC G-2 Joint ISR Directorate is to coordinate integrate and de-conflict TRADOC and Army ISR concepts and capabilities to include staff coordination with Deputy Director Joint Staff J-7, Joint and Coalition Warfighting (JCW), United States Strategic Command, and other service and United States national intelligence agencies. The Joint ISR Directorate, led by an Army civilian, is responsible for researching, developing, and characterizing current and future threat signatures, patterns, and processes for application in the development of ISR concepts, systems, doctrine, force design, and training development and in support of all Modeling and Simulation (M&S) efforts; coordinates with JCW and other agencies to integrate Army ISR and battle space awareness concepts into experimentation, concepts, and developmental; advises TRADOC Major Subordinate Organizations and Headquarters Department of the Army (HQDA) on the development of bridging strategies between current and future ISR capabilities to include staff processes. ISR integration work includes deployable requirements. ISRMAT has a proven capability to rapidly deploy small teams of personnel, with little life support requirements, providing direct over-the-shoulder advising/coaching/mentoring assistance to tactical U.S. and Coalition units. Deployed teams provide support to the Resolute Support Mission (RSM) Joint Command (Afghanistan), Combined Joint Land Forces Component Command-Iraq (CJFLCC-I) and within other Combatant Commands (COCOM) as required, with government oversight through the TRADOC G-2.

1.2 General Information.

1.2.1 Period of Performance.

1.2.2 Phase-in Period/Transition. The phase-in period consists of 60 days. During the phase-in period, the Contractor shall prepare to assume full responsibility for all areas of operation in accordance with (IAW) the terms and conditions of this contract. The Contractor shall take all actions necessary for a smooth transition of the contracted operations. The Government will make all facilities and equipment accessible to the Contractor during the phase-in period and throughout the period of performance. During the phase-in period, the Contractor shall, at a minimum:

a. Establish the Project Management Office.

b. Recruit and hire all necessary personnel.

c. Ensure 100% of the contractor work force is in-processed and has completed mandatory training, secured security badges and Common Access Identification Cards (CACs) by the end of phase-in. NOTE: Travel costs during transition are factored into travel amounts provided by the Government.

d. Obtain all required certifications and clearances, including personnel security clearances.

e. Participate in joint inventories and sign for Government-furnished property (GFP).

f. Develop and submit any deliverables.

g. Attend post award meetings.

h. Accomplish any necessary training to support the functions listed in the PWS.

NOTE: It will take approximately 32 hours to complete required DOD and Army mandatory in-processing requirements for facility access badges, CAC ID and entry into contractor verification systems.

i. Reporting contractors shall have the following documents on day one of in-processing:

I. Two valid/current forms of photo identification.

II. Passport that is good for at least six months of starting ISRMAT program (passport may be one of the forms of photo identification).

III. Certificates awarded at completion of required on-line in-processing training already completed.

IV. Verification of valid Army Knowledge On-Line contractor account.

V. The Contractor, in coordination with TRADAOC G-2 Contracting Officer’s Representative (COR), is responsible for preparing and processing: Letters of Authorization (LOA) and Synchronized Pre-deployment and Operational Tracker (SPOT) - approximately two days in length; rules for Use of Force (RUF) packet construction - not less than three days to complete; Arming Memorandum - approximately two weeks turn-around after receipt by Theater.

1.2.3 Phase-Out Period. During the 45-day phase-out period, employees of the incoming Contractor may observe operations and performance methods of the incumbent Contractor. This will allow for orderly turnover of facilities, equipment, and records and will help to ensure the continuity of service. The Contractor shall not defer any requirements for the purpose of avoiding the responsibility or of transferring such responsibility to the succeeding Contractor. The incumbent Contractor shall fully cooperate with the succeeding Contractor and the Government so as not to interfere with their work or duties. In addition, 30-days prior to the Phase-out period beginning, the incumbent Contractor shall develop and submit a close-out report and Transition Plan to TRADOC leadership detailing the incumbent Contractor’s plans to left-seat/right-seat with the incoming Contractor personnel for the purpose of transitioning current workload, so as to ensure continuity of effort (see Section 6.1.1 for Transition Plan specifications).

During the phase-out period, the Contractor shall also complete the following: employee notification; retention of key personnel; turn-over of work-in-progress, inventories, and Government property; removal of Contractor property; data and information transfer; and any other actions required to ensure continuity of operations as designated herein.

1.2.4 Non-disclosure Requirements. All Contractor personnel (to include subcontractors, teaming partners, and consultants) personally and substantially involved in the performance of this contract shall execute and submit a “Non-Disclosure Agreement for Contractor Employees” Form (see Attachment A). Execution of this agreement by Contractor personnel (employee and supervisor) is required prior to the commencement of any work on this contract and whenever replacement Contractor personnel are proposed. Any information obtained or provided in the performance of this contract shall only to be used in the performance of this contract. Additionally, the Contractor (and any subcontractors, consultants, or teaming partners) is required to complete and sign a “Sensitive Data/Information Non-Disclosure Agreement” (see Attachment B). Execution of this agreement is required prior to the commencement of any work under this contract.

1.2.5 Personnel. The Contractor shall provide all necessary personnel and managerial resources for execution of this contract.

1.2.6 Supervision. Contractor personnel are employees of the Contractor and under the administrative control and supervision of the Contractor. The Contractor shall select, supervise, and exercise control and direction over its employees. The Contractor shall provide sufficient supervision of its workforce as necessitated by their staffing plan. However, the Contractor shall not supervise, direct, or control activities of Government personnel or the employees of other Contractors. The Contractor is accountable to the Government for the actions of its personnel and shall follow installation and Army regulations.

1.2.7 Key personnel. Certain experienced professional and/or technical personnel are essential for successful accomplishment of the work under this contract. The following personnel are identified as Key Personnel for the performance of this contract:

1.2.7.1 Contract Program Manager (PM). The Contractor shall provide complete program management support that shall fully integrate, manage, and document all phases of the PWS requirements. The Contractor shall be the focal point for all issues in the ISRMAT effort and shall keep the Government fully informed on ISRMAT status and events in theater and Continental United States (CONUS), both verbally and in writing. The PM shall have:

a. Minimum of 6 years of demonstrated program and personnel management experience

1.2.8 Hours of Operation and Location. The principal place of performance for support is Fort Eustis, Virginia; however, other locations, including Outside Continental United States (OCONUS), will be required in order to provide flexibility for the emerging and unique mission. The Contractor shall ensure adequate capability is available to provide responses to specific tasks. A business day is defined as Monday through Friday, except the legal public holidays specified below or any other day declared to be a holiday by federal statute or executive order. Federal Government holidays are as follows:

Independence Day

1.2.9 Privacy Requirements. Work on this contract shall require that Contractor personnel have access to sensitive, privileged, or Privacy Act information. Personnel shall adhere to the Privacy Act, (5 U.S.C. § 552a) and applicable Agency rules and regulations. Contractor personnel shall not divulge or release privacy data or information developed or obtained in the performance of this contract award, until made public or specifically authorized by the Government. Contract personnel are required to sign Non-Disclosure Agreements and Organizational Conflict of Interest statements (copies will be provided to the Government). The Contractor shall not use, disclose, or reproduce a third party company’s proprietary data, other than as authorized and required in the performance of this contract award. The Contractor shall notify the COR within 24 hours, identifying personnel that no longer require access to Government information systems.

1.2.10 Contractor Identification. The Contractor’s personnel shall conspicuously display on their person a Contractor-furnished photo identification badge while on duty, as well as a Government-issued photo identification badge. The badge shall display, at a minimum, the employee’s full name and legal name under which the Contractor is doing business. Contractor personnel must wear badges at all times, above the waist and shall identify themselves as Contractors at meetings, in emails (signature block shall include the company name and the word ‘contractor’), when answering government telephones, etc.

1.2.11 Travel

1.2.11.1 The Contractor shall perform temporary duty (TDY) to CONUS and OCONUS locations as required in this contract. Contractor shall demonstrate capability to expeditiously obtain Host Nation authority to arm, deploy and sustain contractors in hostile fire zones and uncertain threat environments conducting embedded tactical through operational advisement to Army and Joint Forces. Additionally, the Contractor shall be able to maintain any required host nation authority, licenses, or other permission to operate within the country. Note: Afghanistan and Iraq Business Licenses are REQUIRED and shall be MAINTAINED through the life of the contract. All travel required and approved will be paid IAW with provisions in this contract, by reimbursement to the Contractor. Only travel previously approved by the Contracting Officer or COR will be reimbursed. Guidance for Contractor travel may be found in Federal Acquisition Regulation (FAR) 31.205-46, the General Services Administration Federal Travel Regulations (FTR), Department of Defense Joint Travel Regulations (JTR) and Department of State Standardized Regulations (DSSR).

1.2.11.2 Travel Requests. All requests for travel shall be submitted within 48 hours of travel (see Attachment C) and approved by the Contracting Officer or COR prior to incurring cost, as travel will be reimbursed in accordance with the FTR, JTR, DSSR, and/or the provisions set forth in this contract. Contractors shall minimize the number of travelers and rental cars, and travel shall be scheduled to minimize payment of overtime whenever possible. Requests shall include a description of proposed travel, a list of travelers, the contract number, and contract line item number (CLIN).

1.2.12 Data Rights. The Government has unlimited rights to all documents and materials produced. All documents and materials, to include the source codes of any software, produced shall be Government owned and are the property of the Government with all rights and privileges of the ownership and 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 will be the sole property of the Government and may not be used for any other purpose.

The right does not abrogate any other Government rights under the applicable Data Rights clause(s). The Contractor shall ensure that all hardware and software agreements entered into are transferable to the Government and to other Contractors at the discretion of the Government.

1.2.13 Organizational Conflict of Interest. 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, in the event the Contracting Officer unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the Contracting Officer may affect 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.2.14 Contracting Officer Representative. 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: approve Contractor travel, 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 contract.

1.2.15 Other Direct Costs (ODCs). The contractor may be required to provide other direct materials in support of this PWS. Other direct materials/costs are costs not previously identified as direct material cost or indirect costs that can be identified specifically with a final cost objective. All contractor furnished materials requires Government approval and will be authorized to the extent that is necessary for performance of this requirement. Labor is not permitted to be proposed as an ODC. For proposal purposes, a CLIN shall be established at an estimated Not-to-Exceed (NTE) amount for each year. Some typical ODCs are: medical exams, DBA insurance, internet costs for communications while deployed, and uplifts on pay, danger/post hardship.

SECTION C-2 ACRONYMS

2.0 Acronyms and Definitions. The following terms, as used throughout this Operational Environment/Core Functions PWS, have the meaning set forth below.

Acronyms Definition

The principal set of rules established to govern the acquisition process of the Government purchasing goods and services.

Prescribed by the General Services Administration for travel in the contiguous United States.

Prescribed by the DoD, for travel in Alaska, Hawaii, and outlying areas of the United States.

Explains concisely what is to be accomplished in terms of results so that the Government can monitor and evaluate the progress and final result of the project effectively.

A web-based application that allows Contractors to electronically submit invoices and receiving reports and the Government to inspect, accept, receive, and pay electronically.

SECTION C-3 GOVERNMENT FURNISHED PROPERTY AND SERVICES

3.0 Government-Furnished Property (GFP) and Services. The Government will provide workspaces/desks, chairs, and office automation to include computer(s), telephones, printers, etc. as necessary by the work performed for each contractor personnel. Tactical field equipment will be provided as necessary to each individual depending upon the deployment requirements for each individual. The Contractor shall provide a method of tracking and managing GFP, when issued. TRADOC G-2 Government personnel will determine property disposition, acquisitions, and final acceptance of deliveries of services/supplies. The Contractor shall not engage in inherently governmental functions associated with service/supply acquisition management (see FAR Subpart 7.5).

SECTION C- 4 CONTRACTOR-FURNISHED PROPERTY AND SERVICES

4.0 Contractor-Furnished Property and Services. The Contractor shall be responsible for providing management, labor, materials, equipment, and facilities, not otherwise provided as Government-furnished. The costs for contractor-furnished property must be included in the contractor’s quoted proposal. No contractor-furnished property shall be separately charged to the Government except as specifically authorized/required by Government Contracting Officer/COR. At contract completion, the contractor shall remove all contractor-furnished property from Government facilities unless title has vested in the Government.

SECTION C-5 SERVICES REQUIRED/SPECIFIC TASKS

5.0 Tasks. This PWS requires trained and certified and properly cleared ISRMAT personnel to provide advice and assistance on the Operational Environment to US/Coalition forces on the use of ISR at every echelon as required by the RSM Joint Command, and CJFLCC-I. This currently includes Train Advise and Assist Commands (TAACs), Combined Joint Special Operations Task Force (CJSOTF), Special Operations Joint Task force – Afghanistan and Iraq (SOJTF-A, SOJTF-I), and Resolute Support Mission – Special Operations Force (RSM-SOF), focusing on improving staff communication, processes, refinement of planning and requirements, and increasing ISR effectiveness from all aspects of ISR integration for units assigned to the CENTCOM AOR’s. Additionally, the ISRMAT shall highlight those actions necessary to improve staff functionality and efficiency by identifying internal and external friction points and gaps in communication, assisting units with process development, and refining staff planning cycles. The ISRMAT shall advise units on Collection Management and intelligence synchronization best practices; this includes assistance with intelligence requirements generation and refinement, ISR utilization assessments, and maximizing the use of organic, theater, and national level assets to best support the intelligence collection cycle and boots on the ground.

5.1. ISR Mobile Advisory Team (ISRMAT). Numerous advanced-technology ISR capabilities have been rapidly acquired and deployed to multiple Combatant Command (COCOM) operational areas in recent years. Examples of these systems include Quick Reaction Capabilities such as Saturn Arch, Night Eagle, Highlighter, Constant Hawk, as well as Joint and Theater capabilities such as Rivet Joint, U2 and the MC-12. Although some training on the systems' capabilities is provided in various venues prior to deployment, the number and diversity of capabilities is difficult to train during pre- deployment exercises, training is often incomplete (particularly for new-technology capabilities), and some systems arrive after personnel have deployed. Additionally, units deploy with significantly smaller staffs and without specific Combat Training Center Mission Rehearsal Exercises, leaving them less prepared to plan, prepare and execute sophisticated Theater and organic ISR operations. OSD, Joint Staff, and TRADOC have determined that the most effective method to mitigate this problem is through in-theater ISRMATs that deploy to operational environments (OEs) and provide specialized training on staff processes and communications, collection planning and requirements processes, and ISR systems' capabilities. Theater commands will determine the content and type of specialized training to be provided by ISRMATs. The primary customers will be tactical U.S. units and (when specifically funded and authorized) Coalition units preparing to and conducting operations in support of COCOM objectives. ISRMATs will provide advising/coaching/mentoring to the tactical units identified by Headquarter staffs (COCOM, Combined Air Operations Center (CAOC), and tactical level) to improve overall ISR effectiveness. Additionally, ISRMATs shall be capable of providing assessments of ISR systems' effectiveness, as requested by Joint Headquarter staffs. Because the Teams support levels of command from Four Star down to small units, they must have the maturity and experience to interact effectively at all of these levels; their operating conditions force them to work with a high degree of initiative; and they must be able to understand and advise and assist with ISR subjects ranging from detailed staff process and products, up to Theater level policy and procedures. As such, ISRMAT contractors shall have no less than 6 years of direct operational ISR experience, and at least two related deployed tours in order to meet the numerous and varied demands for expertise placed on them.

5.1.1 For Afghanistan, at the direction of USAFOR-A Commander the contractor shall provide ISR Mobile Advisory Teams (ISRMATs), consisting of seven ISRMAT SMEs in theater (Mission Manager plus three teams of two), plus seven ISRMAT SMEs in CONUS. For support in Iraq, the contractor shall provide one personnel in Iraq, and one in CONUS. 8 SMEs in CONUS are responsible for training units prior to their deployment; assisting the Intelligence Community with assessments of ISR processes and capabilities in theater; assisting TRADOC Centers of Excellence in the development of training and doctrine; and documenting lessons learned and best practices for the Army and Joint communities.

5.1.2 The contractor shall respond to additional CONUS/global training requirements using CONUS-based ISRMAT personnel as requested by the Director, TRADOC G-2 ISR Directorate. This includes support to the TRADOC schools and centers, Combat Training Centers, conventional/unconventional Home Station Training, and joint training initiatives.

5.1.3 Each ISRMAT shall include multi-INT expertise (i.e. the ability to integrate multiple intelligence discipline to support operational activities such as Targeting and Force Protection.) Examples of integrated disciplines include GEOINT, SIGINT, OSINT, ISR synch and mission management) found in the Afghanistan and CENTCOM Joint Operating Area, as well as other COCOMs as required.

5.1.4 ISRMAT team members shall deploy forward on theater transportation, if available, throughout the CENTCOM Combined Joint Operations Area (CJOA) directed by the RSM Joint command or CJFLCC-I to provide requisite training and advice to CJOA based units. Teams may also deploy to and support other COCOMs as directed.

5.1.5 ISRMAT teams shall provide ISR training and ISR Interoperability training to U.S. forces in Afghanistan as required. The ISRMATs shall deploy throughout the CJOAs (which includes Afghanistan and Iraq, as well as all supporting CENTCOM locations such as Al Udeid Air Base, Qatar, and supporting U.S. bases in Kuwait) in support of the RSM Joint Command and CJLCC-I, and provide ISR training as determined and supporting RSM. Training and assistance varies considerably from unit to unit and over time, as mission priorities and threat activities change. ISRMAT shall support all Joint ISR integration requirements of units including:

a. Unit tailored training that assists units in requesting and employing all capabilities deployed to theater;

b. Staff Communication and Integration Processes (ISR synchronization) that integrate ISR into Mission Command functions such as: ISR Support to Targeting, ISR Support to Force Protection, ISR Support to Retrograde Operations, ISR Support to Counter-IED operations, ISR support to Convoy Operations, and ISR Support to Situational Awareness.

c. ISR-related communications and collaboration between Conventional and Special Operations Forces including: Sharing of ISR capabilities; sharing of targeting information; de-confliction of collection activities; and cooperative ISR execution.

d. Understanding and executing Theater Collection Planning and Requirements Processes, including use of request of request tools; timing for requests and approvals; ad hoc request processes; integration with unit and higher operations planning processes; and coordination with special operations forces and higher headquarters for collaborative collection operations.

e. Effective all-source intelligence integration, including coordination between current operations and collection management; de-confliction and coordination between echelons within the unit; dissemination of collected intelligence between intelligence staffs and between intelligence and operations functions; and internal staff processes for tasking and collecting against the commander’s priority requirements.

f. Signatures training in order to understand and collect against Improvised Explosive Devices (IEDs); threat direct fire engagements; threat indirect fire engagements; insider threats; and complex attacks against U.S. Coalition and Host Nation Security Forces.

g. Targeting Operations.

5.1.6 Direct, non-incidental training, non-interoperability to Coalition or Allied Foreign forces will not be provided unless specific authority and funding are provided.

5.1.7 ISRMAT Teams shall provide in-theater training and advisory assistance to military units assigned to the CENTCOM area of responsibility, or other COCOMs as required. The ISRMATs, as required, shall deploy to operational areas within CENTCOM to provide coordinated, tailored ISR training Staffs including:

a. Unit tailored training on specific capabilities deployed to theater,

b. Staff Communication and Integration Processes (ISR synchronization)

c. Conventional and Special Operations Forces Communication and Integration Processes (ISR synchronization)

d. Collection Planning and Requirements Processes,

e. Effective all-source intelligence integration,

f. Signatures training, and

g. Targeting.

5.1.8 ISRMAT Teams shall be capable of assessing and evaluating the effectiveness of ISR Systems operating in Theaters of Operation which includes providing specific items of information that must be collected. These items of information will vary depending on the requirement levied on the TRADOC G-2, but will generally include:

a. Assessing and evaluating the range of systems deployed to operational areas

b. Confirming or denying sensor, platform and processing, exploitation, and dissemination (PED) effectiveness.

c. Identifying best practices and provide immediate feedback to affected units and key theater and DOD stakeholders.

d. Providing input on which platforms and sensors should be retained in theater and better enable and integrate ISR operations in theater.

SECTION C-6 PROGRAM MANAGEMENT SUPPORT/DELIVERABLES

6.0 Program Management Support

The Contractor shall provide complete program management support that shall fully integrate, manage, control, and document all phases of the PWS requirements. The Contractor shall provide all necessary personnel, administrative, financial, systems analysis, special operations, technical, and managerial resources necessary for the support of this contract. The Contractor's technical effort shall be under the direction of a Contractor PM. The Contractor PM shall provide the overall management of program, personnel, planning, quality control, direction, coordination, and reviews necessary to assure effective contract performance. It is the Contractor’s responsibility to provide and maintain a state-of-the-art trained workforce capable of providing the services specified herein.

The Contractor shall participate in a Government-scheduled Kick-off Meeting after contract award. The Government will schedule the Kick-Off Meeting (approximately one to three work-days). The purpose of the Kick-off Meeting is to: (1) aid both the Government and Contractor personnel in achieving a clear and mutual understanding of all requirements; and, (2) identify and resolve potential problems. The Contractor shall be prepared to discuss any issues requiring clarification and gather information necessary for the Project Management Plan (PMP), as discussed below.

6.1 Project Management Plan (PMP). The Contractor shall develop, maintain, and update a PMP that defines a management system to plan and control work efforts under this contract. The PMP shall be used as a foundation for information and resource management planning and guidance. The Contractor shall deliver the initial PMP within 45 days after start of the Phase-In period.

The PMP shall delineate how the Contractor plans to accomplish the effort supporting the specific contract, to include, but not be limited to, the following:

a. Status of current and planned tasks and subtasks.

b. Base schedule overlaid with actual schedules, for each task.

c. Project Organization.

d. Project Transition Plan, Processes, and Schedule.

e. Work Breakdown Structure (WBS).

f. Process Management and Control.

g. Contractor Organizational Structure (including subcontractors).

i. Personnel Staffing Plan (assignments, duration)

ii. Software

iii. Hardware

h. Project responsibilities to include process flowcharts for all major tasks.

i. Task dependencies and interrelationships.

ii. Project Management Deliverables.

iii. Transition Plan.

iv. Operations Security Plan.

v. Quality Control Plan.

vi. Quarterly Management Report.

vii. Monthly Status Reports.

viii. After Action Report (AAR).

ix. Meetings/Briefings/Publications.

i. Project Management Team Organizational Structure-describe how the contract will be managed, to include team structure, communication interfaces, and coordination.

j. Milestone scheduling (mission support, schedule accountability, and management).

k. Travel (management of expense tracking, reporting, and invoicing).

l. Updated Deliverable Schedule (based on solution).

m. Contingency Plans (where appropriate).

n. Monitoring mechanisms including program metrics.

o. Automated Tools, Techniques, and Methods.

The Contractor shall keep the PMP up-to-date and accessible electronically at all times on a secure storage location (such as AKO or SharePoint portals) by designating individuals with controlled passwords. The Contractor shall respond to Government business relations requests (changes in technical and contractual needs and data calls) within one work-day. The Contractor shall be prepared to brief any PMP content to the Government at short notice (within 24 hours).

6.1.1 Transition Plan. The Transition Plan shall detail the plan, staffing, and other information necessary to seamlessly transition the work performed to the Government at the conclusion of this contract. The transition activities shall minimize both loss of support and cost to the Government, and shall be performed without any interruption or degradation of any services. The Transition Plan shall address, at a minimum, the following areas:

a. Transition of Program Management Support and other personnel.

b. Transition of task requirements in the contract.

c. Asset Transfers (hardware, software, GFP).

d. Resource requirements (personnel and budget).

e. Security Clearance actions and status.

f. Transition milestones and timeline.

g. Risk mitigation practices.

6.2 Quality Control Plan (QCP). The Contractor shall develop, implement, and maintain a quality control system which includes a written a QCP. The QCP shall address methods for meeting contract performance standards and requirements delineated in section C-5, Specific Tasks. The basic principle of the QCP is to assign the Contractor responsibility for quality control. The Contractor shall institute and maintain a capability to ensure the quality of the services required, which is articulated in its QCP. The Contractor shall apply industry standards and best practices to develop a plan that describes the inspection system to cover services listed in the PWS including, at a minimum, the method of inspection, the specific areas to be inspected, frequency of inspections, the title and organization placement of the inspection, and a baseline performance criteria for Contractor support. Quality assurance practices in program management include, at a minimum, identification of quality control factors and processes, evaluation methods, process improvement, and risk management.

6.2.1 Satisfaction Survey. The Contractor shall include in its QCP a satisfaction survey form. On a quarterly basis, the Contractor shall administer its QCP satisfaction survey. The Contractor shall include survey results in the next reporting period.

6.2.2 Problem Notification Report. The Contractor shall include in its QCP a plan to report problems or potential problems to the COR that affect performance under the contract within 24 hours. The report shall address, at a minimum, the nature and source of the problem; Government action required; the impact on delivery schedules; corrective action(s) needed; and whether or not there are anticipated increases to Government costs. All Program Notification Reports shall be incorporated into the Monthly Status Report (MSR) for the next reporting period.

6.2.3 Customer Complaints. The Contractor shall include in the QCP procedures for responding to customer complaints. The Government will request customer feedback using an internal Customer Feedback Form (see Attachment D). Upon receipt of a customer complaint, the COR shall immediately forward the form to the Contractor. The Contractor shall address any complaints. The Contractor shall provide appropriate response and submit to the COR.

6.3 Resource Plan. The Contractor shall develop a project schedule, a plan to determine project resource estimates, and how to ensure all project costs are captured at event completion. Project resource estimates shall be submitted by the 5th workday after notification from the Government and actual project resource amounts shall be due by the 5th workday after project completion. Specific resource requirements that require ODCs and supporting ROMs must be maintained online and provide workflow for the government to manage and approve all requests. The Contractor shall maintain a SharePoint repository that allows the Government to track resource requirements and execution. The Contractor shall provide a dashboard that provides the Government situational awareness to budgets and execution by task area.

6.4 Monthly Status Report (MSR). The Contractor shall provide the COR a MSR that analyzes the current contract status and provides current and projected contract accounting information. The MSR shall be submitted by the 5th work-day after the close of the monthly accounting period. The MSR shall include, at a minimum, the following elements:

a. A summary of work performed by each specific task area for the reporting period.

b. Contract Labor.

c. A summary of ODCs.

d. A summary of Travel (traveler, destination, dates, purpose and cost).

e. A summary of problems encountered and recommended solutions (see para 6.2.2).

f. A summary of problems anticipated and preventative measures.

Additionally, the Contractor shall attend a monthly program management review which discusses the MSR with the COR and Contracting Officer.

6.4.1 After Action Report (AAR). The Contractor shall provide an AAR for meetings and events attended and briefings given within five workdays of the event completion. The AARs serve as a documentation of meetings, briefings, and events and provides an overall synopsis of the discussion. The AARs shall include, at a minimum, an executive summary, objectives, action items, due dates, and responsible parties, and any resulting issues, resolutions, or outcomes.

6.4.2 Tactical Trip Reports. The Contractor shall provide tactical trip reports within five days of each mission completion (regardless of the trip length, purpose, or cost). Tactical trip reports shall be classified and used for OCONUS trips only. Tactical trip reports are normally completed as a team effort by the Government/Contractor field team members assigned to the mission. The Contractor shall participate in the team reporting effort. However, if a specific mission is executed by a Contractor-only team or individual, the Contractor is solely responsible for providing the tactical trip report and submitting to Government. The tactical trip reports shall include, at a minimum, the following information:

a. Executive Summary—briefly discusses purpose, support provided, observations, and mission conclusion (success).

b. Key observations—list key observations identified during the mission.

c. Mission—state mission purpose.

d. Tasks Conducted-list the tasks conducted during the mission trip (possibly identify tasks conducted by Contractor).

e. Personnel performing the tactical trip. Identify all team members with rank and position.

f. Dates and locations of the mission.

g. Mission Results: for each key observation, provide a description of the observation and any recommendations. Observations shall precisely describe what is occurring. Assessments shall describe G2’s assessment of the situation, any support/information provided, and any issues discussed and resolved or outstanding. Recommendations shall discuss future outlooks of the situation, dissemination of information, and potential solutions.

h. Points of Contact: Identify any key personnel met and gathered information from.

i. Results achieved (i.e., synopsis of meetings, issues discussed and resolved or outstanding, tasks performed, mission accomplished).

6.4.3 Trip Reports. The Contractor shall provide trip reports within five days of each CONUS trip/mission completion (regardless of the trip length, purpose, or cost). Trip reports may be classified or unclassified depending on nature of trip/mission purpose. The trip reports shall include, at a minimum, the following information:

a. Executive Summary—briefly discusses purpose, support provided, observations, and mission conclusion (success).

b. Mission-state mission purpose.

c. Tasks Conducted—list the tasks conducted during the mission trip (possibly identify tasks conducted by Contractor).

d. Personnel performing the trip—identify all team members with rank and position.

e. Dates and location of the trip/mission.

f. Specific information requirements.

g. Information of Value/Key Take-away.

h. Recommendations for dissemination of information.

6.5 Quarterly Program Management Review (PMR). The Contractor shall attend and participate in quarterly PMR to discuss and evaluate the Contractor’s efforts and accomplishments in direct relation to this contract. In the PMRs, the Contractor shall present the PMR and be prepared to discuss the specifics of technical monitor reports, manning, budget/financial information, overall contract status, and forecasted projects and expenditures.

6.6 Monthly Contractor Census Reporting. The prime Contractor shall provide deployed Contractor manpower information to the contract’s Contracting Officer and COR. Information shall be current as of the 25th day of each month and received by the Contracting Officer NLT the first day of the following month. The following information shall be reported:

a. The total number of prime and subcontractor employees.

b. The total number of prime and subcontractor U.S. citizens.

c. The total number of prime and subcontractor local nationals.

d. The total number of prime and subcontractor third-country nationals.

e. The location in which the work was performed.

f. The name of all company point of contacts (POCs) who are responsible for entering and updating employee data in the Synchronized Pre-deployment and Operational Tracker IAW Defense Federal Acquisition Regulation Supplement(DFARS) 252.225-7040 or DoD Class Deviation 2007-O0010.

6.7 Armed Personnel Incident Reports. All Contractors and subcontractors in the theaters of operations shall ensure that their personnel supporting forces are familiar with and comply with all applicable orders, directives, and instructions issued by the respective Commanders relating to force protection and safety. Contractors shall provide first aid and request medical evacuation of injured persons, and remain available for U.S. or Coalition response forces, based upon the situation. In the event Contractor personnel are detained by U.S. or Coalition Forces, prolonged detention due to lack of proper identification can be alleviated by Contractor personnel possessing on their person information that includes the Contractor’s name, the contract number, a Contractor management POC, and the phone number of the Contractor Operations Cell (CONOC)/Joint Operations Cell (JOC) Watch. Typically required information in notifications and reports include:

a. Name of the company.

b. Where the incident occurred.

c. Time the incident occurred.

d. A brief description of the events leading up to the incident.

e. A POC for the company.

6.8 Service Contract Reporting (SCR). The contractor shall report the total dollar amount invoiced for services performed during the previous Government fiscal year under the order, the number of Contractor direct labor hours expended on the services performed during the previous Government fiscal year, and data reported by subcontractors when applicable. This information shall be submitted via the internet at www.sam.gov.

Reporting inputs shall be for the labor executed during the period of performance during each Government FY, which runs from 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.

SECTION C-7 DELIVERY/ INSPECTION/ACCEPTANCE/INVOICING

7.1 Delivery, Inspection/Acceptance by the Government, and Invoicing. The COR will inspect and accept all contract work performed, reports and other deliverables, then report surveillance results to the Contracting Officer.

7.1.1 Deliverables. All deliverables shall meet professional standards, as determined by the Government, in order to fulfill contract requirements. The Contractor shall submit all written deliverables for Government review and include a transmittal letter identifying the contract by contract number. The Contractor shall be responsible for delivering all end items within specified timeframes (see Section C-9). The format for deliverables will be an agreed upon format between the Government and the Contractor, unless otherwise stated in the PWS. The Contractor shall utilize a secure electronic system to submit all deliverables, such as AKO or a SharePoint portal.

The Government will review all deliverables, including the validity of the data contained within and the overall quality of the deliverables. The Government will provide written notification of acceptance or rejection of all deliverables within 15 work-days. The Government has the responsibility and the right to reject or require correction to any output that does not meet the requirements of the PWS. All notifications of rejection will be accompanied with an explanation of the specific deficiencies causing the rejection and/or comments to be incorporated. The Contractor shall incorporate the Government comments into the deliverable before re-submission within the specified time. If no corrections, additions, or rewrites are required, the submission will become the final document. The Government is the final authority with regard to final acceptance and approval of the deliverable.

Note: The costs to develop and deliver all deliverables shall be included in the Contractor’s price.

7.1.2 Packaging. The Contractor shall submit documents using Microsoft Office 2007 or later version of Microsoft Office, to the Government electronically through a specified secure storage location. In the event that reports and deliverables are received in hard copy format, as opposed to electronic format, the Contractor shall follow appropriate procedures when providing and handling classified material IAW AR 380-5. Unclassified materials produced under this contract are to be handled by the Contractor as confidential documents and marked “For Official Use Only.”

7.1.3 Notice Regarding Late Delivery.