Attachment 0001 - Draft Depot Maintenance Operations Planning System (DMOPS) PWS 08AUG2023.pdf

Depot Maintenance Operations Planning System (DMOPS)

PERFORMANCE WORK STATEMENT (PWS)

Revised 8 August 2023

1 SCOPE

The scope of this Performance Work Statement (PWS) is to provide support services to the Office of the Deputy Chief of Staff (ODCS), Army G4:

Provide technical and analytical support to integrate information from disparate data sources into one program and budget-tracking system for the Army Organic Industrial Base (OIB), which allows each organization to determine unique business rules and interface with the agency’s Program Objective Memorandum (POM), Budget Estimate Submission (BES), and President's Budget (PB). The Depot Maintenance Operations Planning System (DMOPS), records previous year executed workload, current year projections, forecasted funding and obligated workload for reporting against the Congressional organic and contract workload distribution report.

1.1 BACKGROUND

DMOPS integrates information from disparate data sources into one program and budget-tracking system, which allows each organization to determine unique business rules and interface with the agency’s POM, BES, and PB. The DMOPS sponsor is Army G4. This PWS outlines the tasks supporting the DMOPS application in support of the Army G4 program office.

1.2 ORDER TYPE

This PWS is for a hybrid contract. Fixed Firm Price (FFP) for services. Travel and materials will be funded on a Cost-Plus Fixed Fee (CPFF) basis in accordance with Federal Acquisition Regulation

(FAR) 16.302.

1.3 PERIOD OF PERFORMANCE

The period of performance, consist of a twelve (12) month base period with three (3) twelve (12) month option periods.

1.4 PLACE OF PERFORMANCE

The primary work performed under this contract shall be performed at the National Capital Region (NCR). Contractor personnel supporting this PWS shall be located onsite at government facilities in the NCR.

1.5 MATERIALS, EQUIPMENT, AND FACILITIES

The government will provide access to the equipment, facilities, and information for the contractor to perform the support services as required by this PWS. All equipment will remain on Government property book.

Equipment: The Government will provide access to computers, peripherals (printers, fax, scanners, backup drives, etc.) office supplies, classified SIPRNET and Controlled Unclassified Information

(CUI) access, telephone, and reproduction capabilities for contractor employees working at Government facilities in support of this effort.

Facilities: The Government will provide access to the necessary workspace and furniture for contractor personnel to provide the support services required by this PWS.

1.6 SECURITY

The facility security requirements are defined in the PWS DD Form 254, Contract Security Classification Specification.

The highest level of facility clearance required for the contractor to perform on this PWS is Secret.

The highest level of classified material the contractor will be required to safeguard at its own facility is None.

This Contract will require access to Controlled Unclassified Information (CUI) In performing this contract, the contractor will have access to classified information only at another contractor's facility or a government activity.

In performing this contract, the contractor will perform services only.

In performing this contract, the contractor will have operational security (OPSEC) requirements.

1.7 PHASE IN AND PHASE OUT

The Phase in and Phase Out Period shall be 14 days. Within 14 days of vacancy, the contractor must provide a suitable replacement.

1.8 PERSONNEL QUALIFICATIONS

The contractor shall provide fully qualified and competent personnel with the minimum training and certification requirements specified below.

1.8.1 Army Training & Certification Tracking System (ATCTS). All contractor employees with access to a Government information system must be registered in the ATCTS at commencement of services, and must successfully complete the DoD Cyber Awareness Challenge Training prior to access to the IS and then annually thereafter. All required training certificates as identified within this PWS will be uploaded in ATCTS at the following website: https://atc.us.army.mil/iastar/index.php.

The ISSM will be responsible for maintaining and tracking credentials within ATCTS.

1.8.2 Level I Antiterrorism Awareness Training. All contractor employees, to include subcontractor employees, requiring access to Army installations, facilities and controlled access areas shall complete Level I AT Awareness training within 30 calendar days post on-boarding date and annually thereafter. The Contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee, to the COR within 60 calendar days after completion of training by all employees and subcontractor personnel. Level I AT Awareness training is available at the following website: http://jkodirect.jten.mil.

1.8.3 Information Assurance/Information Technology (IA/IT) Training. All contractor employees and associated subcontractor employees must complete the DoD IA awareness training before issuance of network access and annually thereafter. All contractor employees working in IA/IT functions must comply with DoD and Army training requirements in Department of Defense Manual (DoDM) 8570.01-M, and Army Regulation (AR) 25-2 within six months of appointment to IA/IT functions.

1.8.4 IA/IT Certification. Per DoD 8570.01-M, Defense Federal Acquisition Regulation Supplement (DFARS 252.239.7001) and AR 25-2, the Contractor employees supporting IA/IT functions shall be appropriately certified upon contract award. The baseline certification and operating system certifications, as stipulated in DoD 8570.01-M, are required for all technical personnel with elevated privileges and must be completed upon contract award.

1.8.4.1 IA Technical Level I. Required for individuals with limited privileged access to the Computing Environment (CE) and works under immediate supervision and typically reports to a CE Manager. This applies to entry-level computer professionals, such as desktop support specialists and customer support personnel.

1.8.4.2 IA Technical Level II. Required for System Administrator (SA) / Network Administrator (NA) / Information Assurance Manager (IAM) and other associated IA titles working IAT-II functions. The IAT-II is usually an individual with Privileged Access to the Network Environment and work under general supervision and typically reports to a Level III Network Manager.

1.8.4.3 Contractor personnel without elevated privileges will require access as general computer users (IT-III) in performance of this contract. If the need for elevated privileges the contractor will advise the COR of the requirement change and complete the required training and certification for the expected IT level.

1.9 HANDLING OR ACCESS OF CLASSIFIED INFORMATION. Contractor shall comply with Federal Acquisition Regulation (FAR) 52.204-2, Security Requirements. This clause involves access to information classified “Confidential,” “Secret,” or “Top Secret” and requires contractors to comply with – (1) The Security Agreement (DD Form 441), including the National Industrial Security Program Operating Manual (DoD 5220.22-M); (2) any revisions to DoD 5220.22-M, notice of which has been furnished to the Contractor. If secure telecommunication requirements apply, include clause 252.239-7016 and follow guidance at 239.74. If covered system support requirements apply, include provision 252.239-7017 into the solicitation, clause 252.239-7018 into the contract, and follow guidance at 239.3

1.10 Contractors shall comply with Controlled Unclassified Information (CUI) DoDI 5200.48.

Contractors Contractor’s must monitor CUI for aggregation and compilation based on the potential to generate classified information pursuant to security classification guidance addressing the accumulation of unclassified data or information. Contractors shall report the potential of classification of aggregated or compiled CUI to ASA(ALT) Security Manager. Contractors, pursuant to mandatory DoD contract provisions, will submit unclassified DoD information for review and approval for release and approval for release in accordance with the standard DoDI 5230.09. All CUI records must follow the approved mandatory disposition authorities whenever the DoD provides CUI to, or CUI is generated by, non-DoD entities in accordance with Section 1220-1236 of Title 36, CFR, Section 3301a of Title 44, U.S.C., DoDU 5200.48.

1.11 THREAT AWARENESS AND REPORTING (TARP). All contractors with security clearances, contractor employees mush receive annual TARP training in accordance with AR 381-12.

1.12 OPERATIONS SECURITY (OPSEC) TRAINING. In accordance with Army Regulation (AR) 530-1 Operations Security, the contractor employees must be trained within 30 calendar days of their employment start date and annually thereafter. The Contractor shall develop an Operations Security (OPSEC) Plan within 90 days of contract award for review and approved by the responsible Government OPSEC officer. This plan will include a process to identify critical information, where it is located, who is responsible for it, how to protect it and why it needs to be protected. The Contractor shall implement OPSEC measures as ordered by the commander. In addition, the Contractor shall have an identified certified Level II OPSEC coordinator per AR 530-1.

1.13 iWATCH TRAINING. The contractor shall implement OPSEC measures as ordered by the commander. In addition, the Contractor shall have an identified certified Level II OPSEC coordinator per AR 530-1.

1.13.1 Personal Identifiable Information (PII) Training. The Contractor shall complete the necessary PII training as directed and provided by the COR.

1.13.2 The Contractor shall be responsible for all costs, except labor, incurred to meet training requirements.

1.14 CONTRACTOR PERSONNEL SECURITY REQUIREMENTS

1.14.1 Contractor personnel requiring access to DMOPS to fulfill their duties must possess the required favorable security investigation, security clearance, or formal access approvals and meet any need-to-know requirements according to AR 25-2.

1.14.2 Contractor personnel who require access to Classified National Security Information (CNSI) or who work on Information Technology (IT) systems connected to the SIPRNET must possess a minimum of an interim SECRET security clearance. In addition, contract employees accessing SIPRNET must obtain an SIPRNET Public Key Infrastructure (PKI) Token, as identified in the Common Access Card (CAC) paragraph below.

1.14.3 All applicants and employees at a minimum will be the subject to an appropriate favorably completed or adjudicated background investigation conducted by the Office of Personnel Management (OPM) as identified in Table 2. Any unfavorable results of investigations may be grounds for denying or revoking access.

Table 2 – Security Investigation Type

1.15 The Contractor is not authorized to release any classified information to any activity or person, including subcontractors. All requirements as indicated in applicable DoD security policies for control and accounting of classified material will be applied and followed.

1.16 COMMON ACCESS CARD (CAC) / SIPRNET PUBLIC KEY INFRASTRUCTURE (PKI)

TOKEN

1.16.1 Contractor employees will be issued a CAC and SIPRNET PKI Token in order to maintain and sustain the DMOPS application. In addition, a CAC and SIPRNET PKI token as required to conduct daily functions which involve one of the following:

1.16.1.1 Both physical access to a DoD facility and access, via logon, to DoD networks onsite or remotely.

1.16.1.2 Remote access, via logon, to a DoD network using DoD-approved remote access procedures.

1.16.1.3 Physical access to multiple DoD facilities or non-DoD federally controlled facilities on behalf of the DoD on a recurring basis for a period of 6 months or more.

1.17 Before CAC and SIPR PKI Token issuance, the contractor employee requires a favorably adjudicated Tier 1 with Inquiries (T1) or an equivalent or higher investigation as identified in Table 2 above using Standard Form 85 (SF85) and/or Army Directive 2014-05, whichever is most restrictive.

At the discretion of the sponsoring activity, an initial CAC may be issued based on a favorable review of the FBI fingerprint check and a successfully scheduled Tier 1 at the Office of Personnel Management.

1.18 The Contractor shall coordinate with the COR to obtain a CAC through the Trusted Associated Sponsorship System (TASS) and appropriate agency for issuance of the SIPRNET PKI Token.

Position IT Level Investigation Type / Form for Contractors Reinvestigation IA Technical Level I (IT-I) SSBI / T5/T5RSF86 Every 5 years

IA Technical Level II (IT-II) NACLC / T3/T3R/SF86 Every 5 years IA Technical Level III (IT-III) NACI / T3/T3R/SF86 None

1.19 CONTRACT MANAGEMENT AND ADMINISTRATIVE SUPPORT

1.19.1 Contract Management shall be addressed in the contractor’s Progress, Status and Management Report, IAW DI-MGMT-80368A and the Funds & Man-hour Expenditure Report, IAW DI-FNCL-80331A.

1.19.2 The contractor shall provide the following administrative support, Conference, Working Groups & Trip Reports IAW DI-ADMN-81308A, and Record of Meeting Minutes IAW DI-

ADMN-81505.

1.20 CONTRACTOR MANPOWER REPORTING (CMR)

The Secretary of the Army requires all Army contracting agencies to comply with the "Accounting for Contractor Man-hours" memo dated 7 January 2005. The Contractor shall report manpower and cost data into the Army's Contractor Manpower Database as described below.

1.21 Accounting for Contractor Man-Hours: The Army's Office of the Assistant Secretary of the Army (Manpower & Reserve Affairs) operates and maintains a secure Army data collection site where the Contractor shall report all contractor manpower (including subcontractor manpower) required for performance of this contract. The Contractor is required to complete all information in the site's format using the following website https://sam.gov/. The required information includes, but not limited to:

(1) Contracting Office, Contracting Officer, Contracting Officer’s Technical Representative;

(2) Contract number, including task and delivery order number;

(3) Beginning and ending dates covered by reporting period;

(4) Contractor Company name, address, phone number, e-mail address, identity of contractor employee entering data;

(5) Actual direct labor hours (including sub-contractors);

(6) Actual direct labor dollars paid this reporting period (including sub-contractors);

(7) Total payments (including sub-contractors);

(8) Predominant Federal Service Code (FSC) reflecting services provided by the contractor (and separate predominant FSC for each sub-contractor if different);

(9) Actual data collection cost;

(10) Organization title associated with the Unit Identification Code (UIC) for the Army Requiring Activity (the Army Requiring Activity is responsible for providing the contractor with its UIC for the purposes of reporting this information);

(11) Locations where the contractor and sub-contractors perform the work (specified by zip code in the United States and nearest city, country, when in an overseas location, using standardized nomenclature provided on website);

(12) Presence of deployment or contingency contract language;

(13) Number of contractor and sub-contractor employees deployed in theater this reporting period (by country). As a part of its submission, the contractor shall also provide the estimated total cost (if any) incurred to comply with this reporting requirement. Reporting period will be the period of performance not to exceed 12 months ending 30 September of each Government fiscal year and must be reported by 31 October of each calendar year. Contractors may use a direct XML data transfer to the database service or fill in the fields on the website. The XML direct transfer is a format for transferring files from a contractor’s systems to the secure web site without the need for separate data entries for each required data element at the web site. The specific formats for the XML direct transfer may be downloaded from the web site.

1.22 ACCESS AND GENERAL PROTECTION/SECURITY

The Contractor and all associated sub-contractor employees shall provide all information required for background checks to meet installation access requirements to the installation Provost Marshal Office, Director of Emergency Services or Security Office. Contractor workforce must comply with all personal identity verification requirements (FAR clause 52.204-9, Personal Identity Verification of Contractor Personnel) as directed by DoD, HQDA and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any facility or installation change, the Government may require changes in contractor security matters or processes.

1.23 GOVERNMENT FACILITY ACCESS WITHOUT CAC

The contractor and all associated sub-contractor employees shall comply with adjudication standards and procedures using the National Crime Information Center Interstate Identification Index (NCIC- III) and Terrorist Screening Database (TSDB) (Army Directive 2014-05/AR 380-67/AR 190-13). In addition, applicable installation/facility and area commander installation/facility access, local security policies and procedures (provided by Government representative), or at OCONUS locations in accordance with status of forces agreements and other theater regulations.

1.24 COMPLIANCE WITH ENVIRONMENTAL LAWS AND REGULATIONS

Contractors shall comply with all applicable federal, state, and local environmental laws, statutes, regulations, executive orders, permits, Army regulations (with supplements), as well as installation regulation, policy, Host Tenant Agreement, Interagency Service Support Agreement, or Status-of- Forces Agreement. Contractor shall immediately report any conflicts between applicable federal, state, local environmental laws, statutes, executive orders, and provisions of AR 200-1, and any specifications within this contract to the COR.

1.25 WORK HOURS

Normal workdays are Monday through Friday except US Federal Holidays. 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, with any Alternative Work Schedule (AWS) exceptions requiring COR approval.

1.26 RECOGNIZED HOLIDAYS

The following are recognized U.S. holidays. The contractor is not required to perform services on the following Government holidays:

New Year’s Day: 1 January Martin Luther King Jr.'s Birthday: Third Monday in January Presidents’ Day: Third Monday in February Memorial Day: Last Monday in May Juneteenth: 19 June Independence Day: 4 July Labor Day: First Monday in September Columbus Day: Second Monday in October Veterans Day: 11 November Thanksgiving Day: Third Thursday in November Christmas Day: 25 December

2.0 APPLICABLE DOCUMENTS AND WEBSITES

The following documents and websites are referenced for the performance of this PWS:

AR 25-2 Information Assurance (http://www.apd.army.mil/pdffiles/r25_2.pdf)

DODI 8500.1 Information Assurance (https://www.esd.whs.mil/portals/54/documents/dd/issuances/dodi/850001_2014.pdf)

DODI 8500.2 Information Assurance Implementation (https://www.osti.gov/servlets/purl/1116771)

3.0 PERFORMANCE REQUIREMENTS – The following section specifies the Performance Objectives and performance Elements for the contract.

3.1 Depot Maintenance Operations Planning (DMOPS) Support Activities

3.1.1 The contractor shall provide Army Depot Maintenance and Sustainment Systems Technical Support (SSTS) support for the Planning, Programing, Budget and Execution (PPBE) process.

3.1.2 The Contractor shall provide analytic support IAW all facets of the PPBE budget process for both the Depot Maintenance and SSTS programs.

3.1.3 The contractor shall provide the capability for reports generation for both depot maintenance and SSTS programs to support Management Decision Package (MDEP) reviews and the MDEP Validation Letters as listed below. These are predefined reports and not manual reports.

- POM to POM requirements comparison report.

- Funding growth analysis report for the PB to POM report. This report entails the merging of two reports to support the PB to POM analysis.

- Split report by depot, other Services, contract and organic workload.

3.1.4 The contractor shall produce the OP-30/PB45/PB61 reports to support the Office of the Secretary of Defense (OSD) upload into Select and Native Programming (SaNP).

3.1.5 The contractor shall prepare and coordinate agendas, read ahead materials, and minutes associated with Organic Industrial Base Corporate Board (OIBCB) or Organic Industrial Base Execution Council (OIBEC).

3.1.6 The contractor shall develop, and present briefings and pre-briefings as required; support studies and reviews by examining key management reports and records and previous Government and contractor studies related to the functional area or issue under examination.

3.1.7 The contactor shall assist in analyzing industrial base issues that relate to policy, processes, workload, manpower, modernization, and provide solutions to resolve issues.

3.1.8 The contractor shall represent the Army G-4 on various Integrated Process Team (IPT) and working groups and developing courses of action and Army plans to resolve the depot maintenance issues.

3.1.9 The contractor shall provide guidance for developing Core module within the Army Work loading Performance System (AWPS) and/or Logistics Modernization Program (LMP).

Support the G-4 requirement to collect, analyze, prepare, and submit the Army's Biennial Core Logistics Report to the Department of Defense (DOD) IAW Title 10, U.S.C., Section 2464.

Provide input in response to General Accounting Office (GAO) and Army Audit Agency (AAA) reports concerning Core Requirements as recorded in DMOPS and AWPS.

3.1.10 The contractor shall update and maintain assigned tasks in the Army Strategic Readiness Assessment (ASRA). The system is responsible for providing the Army’s performance management solution in support of Army strategic initiatives.

3.1.11 The contractor shall provide training to LCMCs within Army Material Command (AMC), organic depots, and Army G4 staff.

3.1.12 The contractor shall assist the Government in development and/or review of technical documentation and briefings.

3.1.13 The contractor shall provide services to include database maintenance, Management Studies, Analyses and Program Management as directed by the Government.

3.1.14 The contractor shall provide guidance for developing Depot Maintenance Workload Distribution (DMWD) (50/50) report. Support the G-4 requirement to collect, analyze, prepare, and submit the Army's annual DMWD Report to the Department of Defense (DOD) IAW Title 10, U.S.C., Section 2466. Provide input in response to General Accounting Office (GAO) and Army Audit Agency (AAA) reports concerning 50/50 requirements.

3.2 Planning, Programming, Budgeting and Execution System (PPBES) Requirements.

The contractor shall provide analytic, technical, and systems services to support the following specific tasks outlined below. The Contractor will provide support at the Government's location.

3.2.1 Support for PPBES. The contractor shall provide Army Depot Maintenance and Sustainment Systems Technical Support (SSTS) support.

3.2.2 Programming Support. The Contractor shall provide support in accordance with all facets of the PPBES budget process for both the Depot Maintenance and SSTS and Industrial Facilities programs.

3.2.3 SPECIFIC REQUIREMENTS.

The contractor shall provide the capability for reports generation for both programs to support the validation letter and the MDEP reviews as listed below. The reports are either predefined reports, new custom reports, or created by support analysts based upon data constraints / conditions not available in DMOPS. Deliverables include:

a. POM to POM requirements comparison report.

b. Funding growth analysis report; PB to POM report. This report entails combination of merging two reports together to support the analysis.

c. Split report by depot, other services, contract and organic workload.

d. Contractor shall produce the PB61 to support OSD upload into SaNP. Data should consist of Base, Enduring Operations (EO) and Non-enduring Operations (NEO) requirements, Total Obligation Authority (TOA) and Resource Management Decisions (RMD) numbers.

e. Depot Maintenance and SSTS programs require the capability to use the Financial

Resource Allocation Module (FRAM). FRAM data should provide a before and after picture of a decrement and include percentage of funding.

The Contractor shall be required to provide, at the request of the USG, access to and purpose rights to modify, reproduce, release, perform, display, or disclose computer software or computer software documentation within the Government without restriction of the DMOPS current and historical database. The contractor shall be required to provide, at the request of the USG design, USG source code, source code listing, objective code listings, design details, algorithm, processes, flow charts, formulae and related materials that would enable the software to be reproduced, recreated or recompiled and configuration documents to the Government in a form capable of being processed by a computer.

f. DMOPS web tool shall function and provide the same capability as the current DMOPs. Data must be stored in the Enterprise Cloud Management Agency’s (ECMA) cArmy cloud.

g. The G44M Sustainment Maintenance Division Management Decision Package (MDP)

Managers and/or systems analyst will grant access to the DMOPS tool to Army Users.

3.2.4 DELIVERABLES. The Contractor shall provide the following deliverables in a timely manner which support the budget timeline during the course of the year:

a. Contractor shall collect the data from external sources (LMP, Vantage and Post

Production Software Support (PPSS) systems).

b. Contractor is required to perform data refinement (data verification and validation to ensure requirement is complete).

c. Contractor shall provide customer access to DMOPS historical archives.

d. Contractor shall update Depot Maintenance and SSTS data to support each budget cycle/sub-cycle position (which may include requirements, Total Obligation Authority or Resource Management Decision).

e. Contractor shall produce a predefined Split Report of Contractor and Organic workload to support the PB61 report input.

f. The contractor shall provide an updated file of external execution data in the appropriate Fiscal Years for the upload in SaNP.

g. The contractor shall assist G-4 MDEP managers and Action Officers with developing performance metrics to Monitor Program Budget Decisions, Management Initiative Decisions, OMB and DoD policy and regulation, and Business Army Campaign Plan (ACP) Improvements that impact the G-4 performance metrics and programs.

h. The contractor shall ensure ECMA cArmy Tenant User Agreement data is provided, upon request, to the Mission Owner (Govt.) to ensure ECMA cArmy compliance.

i. The contractor shall maintain system operational availability rate / up time of 99.9%.

Any planned system maintenance, that may cause system downtime, must be scheduled during Government off hours and/or weekends.

3.2.5 SYSTEM MODIFICATION DELIVERABLES. The contractor shall provide the following deliverables representing software modifications as needed to ensure the systems adapts to the evolving requirements of the DMx and SSTS PPBSS process. Modifications would fall under an "O&M" (Operations and Maintenance) scope of work. Larger modification requirements (adding new capability or requiring a technical refresh) would be considered Enhancements / Investments outside the scope of O&M requirements.

Deliverables include:

a. As required, add new data elements to support the MDEP reviews by HQDA G8 and/or SS PEG executives. These require the contract to apply rules/or system logic into the DMOPS system to define the different requirement thresholds for applying TOA.

b. System modifications for the SSTS program include:

Several "memo" fields that will hold large amounts of narrative text Data fields to capture metrics and justifications for building the J-book exhibit (number of Logistics Assistance Representative (LAR) actions Number of Technical Manual (TM) pages Complete list to be worked out with the government sponsor Updated description files to include descriptions of SSTS specific data such as Work

Performance Code (WPC) The contractor shall identify, with the government sponsor, the feasibility of custom interactive screens that use SSTS specific terminology when working with sustaining data.

c. SSTS programs capability to use the FRAM as described: FRAM should provide an option for spreading first to records with organic manpower, then just organic and then any contract requirements; spreading by priority within each subgroup.

d. New Detail or Summary Reports that include, but not limited to, supporting evolving POM requirements and the cSustain application.

e. Support required data files and format on Depot and SSTS for uploading into cSustain and support government to transition a file in an automated version for each requested POM sub-cycle.

Technical Exhibit 1 Performance Requirements

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

PERFORMANCE

OBJECTIVE

STANDARD

THRESHOLD

METHOD OF

SURVEILLANCE

(AND WHO

PERFORMS)

{E.G. 100%

INSPECTION BY

COR}

PRS # 1

Contractors shall provide Conference, Working Groups and Trip Reports

IAW DI-ADMN-81308A

PWS 1.19.2

Provide reports within 3 days of activity.

On time and 98% accurate

100%Inspection

COR/ACOR/PCO

PRS # 2

Contractors shall provide Record of Meetings

IAW DI-ADMN-81505

Provide reports within 3 days of activity.

On time and 98% accurate

100%Inspection

COR/ACOR/PCO

PRS # 3

Contractors shall provide Progress, Status, and Management Report

IAW DI-MGMT-80368A

PWS 1.19.1

Provided by the 10th of each month.

On time 100% Inspection

COR/ACOR/PCO

OBJECTIVE

STANDARD

THRESHOLD

METHOD OF

SURVEILLANCE

(AND WHO

PERFORMS)

{E.G. 100%

INSPECTION BY

COR}

PRS # 4

The contractor shall provide Funds & Man-hour Expenditure Report

PWS 1.19.1

Provided by the 10th of each month.

On time and 98% accurate

100% -Inspection

PRS # 5

The contractor shall provide

OP-30/ PB45/PB61

PWS 3.1.4

Timely and accurate. No deviation from standard.

100% -Inspection

PRS#6

Technical Documents & Briefings

PWS 3.1.12

Timely and accurate. 98% accurate 100% -Inspection

Technical Exhibit 2 Deliverables

The contractor deliverable schedule is summarized into performance objectives that relate directly to mission essential items. The deliverables schedules are outlined below. All deliverables shall be in Government approved contractor format and delivered by email to the

KO/COR/ACOR.

DELIVERABLE FREQUENCY # OF COPIES MEDIUM/FORM

AT

SUBMIT TO

Contractors shall provide Conference, Working Groups and Trip Reports

IAW DI-ADMN-81308A

Monthly 1 Electronic Microsoft Office

COR/ACOR/PCO

Contractors shall provide Record of Meetings

IAW DI-ADMN-81505

Within 3 days of meeting

1 Electronic Microsoft Office

COR/ACOR/PCO

Contractors shall provide Progress, Status, and Management Report

IAW DI-MGMT-80368A

PWS 1.19.1

Monthly 1 Electronic Microsoft Office

COR/ACOR/PCO

The contractor shall provide Funds & Man-hour Expenditure Report

PWS 1.19.1

Monthly 1 Electronic Microsoft Office

OP-30/ PB45/PB61

PWS 3.1.4

As required 1 Electronic Microsoft Office

COR/ACOR/PCO

The contractor shall provide briefing material

PWS 3.1.5 & 3.1.6

As required 1 Electronic Microsoft Office

COR/ACOR/PCO

The contractor shall provide training materials

PWS 3.1.11

As required 1 Electronic Microsoft Office

COR/ACOR/PCO

The contractor shall provide Technical Documents & Briefings

PWS 3.1.12

As required 1 Electronic Microsoft Office

4.0 DATA RIGHTS

4.1 The Government's rights in non-commercial technical data and software deliverables shall be governed by DFARS 252.227-7013 (Rights in technical data - Non-commercial items) and DFARS 252.227-7014 (Rights in non-commercial computer software and non-commercial computer software documentation), respectively. According to the requirements outlined in DFARS 252.227-7017, Offerors must specifically identify Data/Software Rights Assertions related to technical data and software deliverables. As indicated in DFARS 252.227-7017(e), an Offeror's failure to submit, complete, or sign the Data mentioned above and Software Rights Assertions with its offer may render the offer ineligible for award. This database shall be made available to the Government upon request and at task completion. All materials purchased under this contract shall remain the property of the United States Government and shall be returned to the Government upon completion or termination of this task or upon request by the Government at any time during the task.