Solicitation - N0018926RW016.pdf

WOMEN-OWNED SMALL

BUSINESS (WOSB)

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES

1. REQUISITION NUMBER PAGE 1 OF

2. CONTRACT NUMBER 3. AWARD/EFFECTIVE

DATE

4. ORDER NUMBER 5. SOLICITATION NUMBER 6. SOLICITATION ISSUE

DATE

7. FOR SOLICITATION

INFORMATION CALL:

a. NAME b. TELEPHONE NUMBER (No collect calls)

8. OFFER DUE DATE/

LOCAL TIME

9. ISSUED BY

13b. RATING

14. METHOD OF SOLICITATION

CODE

15. DELIVER TO 16. ADMINISTERED BY CODE

18a. PAYMENT WILL BE MADE BY CODE17a. CONTRACTOR/

OFFEROR

CODE

FACILITY

CODE

CODE

TELEPHONE NUMBER

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT SUCH ADDRESS IN

OFFER

18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a UNLESS BLOCK

BELOW IS CHECKED

REQUEST

FOR QUOTE

(RFQ)

INVITATION

FOR BID

(IFB)

REQUEST

FOR

PROPOSAL

(RFP)

SEE ADDENDUM

19.

ITEM NUMBER

20.

SCHEDULE OF SUPPLIES/SERVICES

21.

QUANTITY

22.

UNIT

23.

UNIT PRICE

24.

AMOUNT

(Use Reverse and/or Attach Additional Sheets as Necessary)

25. ACCOUNTING AND APPROPRIATION DATA 26. TOTAL AWARD AMOUNT (For Government Use Only)

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH

AND DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND

ON ANY ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS

SPECIFIED

29. AWARD OF CONTRACT: REFERENCE OFFER

DATED . . YOUR OFFER ON SOLICITATION

(BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE

SET FORTH HEREIN, IS ACCEPTED AS TO ITEMS:

30a. SIGNATURE OF OFFEROR/CONTRACTOR

30b. NAME AND TITLE OF SIGNER (Type or print) 30c. DATE SIGNED

31a. UNITED STATES OF AMERICA (SIGNATURE OF CONTRACTING OFFICER)

31b. NAME OF CONTRACTING OFFICER (Type or print) 31c. DATE SIGNED

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

STANDARD FORM 1449 (REV. 11/2021)

Prescribed by GSA - FAR (48 CFR) 53.212

10. THIS ACQUISITION IS UNRESTRICTED OR

NORTH AMERICAN

INDUSTRY CLASSIFICATION

STANDARD (NAICS):

SIZE STANDARD:

13a. THIS CONTRACT IS A

RATED ORDER UNDER

THE DEFENSE PRIORITIES

AND ALLOCATIONS

SYSTEM - DPAS (15 CFR 700)

SET ASIDE: % FOR:

11. DELIVERY FOR FREE ON

BOARD (FOB) DESTINATION

UNLESS BLOCK IS MARKED

SEE SCHEDULE

12. DISCOUNT TERMS

ARE ARE NOT ATTACHED

ARE ARE NOT ATTACHED

27a. SOLICITATION INCORPORATES BY REFERENCE (FEDERAL ACQUISITION REGULATION) FAR 52.212-1, 52.212-4. FAR 52.212-3

AND 52.212-5 ARE ATTACHED. ADDENDA

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED. ADDENDA

8(A)

ECONOMICALLY

DISADVANTAGED

WOMEN-OWNED SMALL

BUSINESS (EDWOSB)

SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

(SDVOSB)

HUBZONE SMALL

BUSINESS

SMALL BUSINESS

NOTE: OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, AND 30.

Section A - Solicitation/Contract Form

Operational Test and Evaluation Services

N0018926RW016

Section B - Supplies or Services & Prices or Costs

Additional Information/Notes

MINIMUM AND MAXIMUM QUANTITIES (FFP, SINGLE AWARD IDIQ) (SEP 2015)

As referred to in paragraph (b) of the "Indefinite Quantity" clause of this contract, the total contract minimum quantity is a total of $2,500.00 worth of orders at the contract unit price(s). The contract maximum quantity is a total of $ .

LOCAL TEXT "UNLIQUIDATED OBLIGATIONS"

The Government intends to unilaterally deobilgate any unliquidated obligations 90 days after each period of performance. Prior to doing so, the Contracting Officer (or Administrative Contracting Officer) will notify the contractor of the intended amount of deobligation and ask the contractor to confirm within one week that all invoices for the completed period of performance have been submitted and processed for payment (with the exception of any invoice for rate adjustment upon receipt of DCAA approved final rates for any cost-type CLINs or SLINs). Upon confirmation that all invoices have been submitted and processed for payment, or upon the contractor's failure to respond to the PCO/ACOs notification of intent to deobligate, the Contracting Officer or Administrative Contracting Officer will unilaterally deobligate the potential ULOs by reducing the funded amount to an amount equal to the contractors invoiced/paid amount for that contract period of performance.

Note: Reduction of cost-reimbursement CLINs or SLINs in accordance with the above DOES NOT change either party's obligations under a Final Invoice submitted upon DCMA establishing final rates for each CLIN and or SLIN.

Allowed Per Order Minimum: 1.00 Dollars, U.S.

Maximum: 5,000.00 Dollars, U.S.

Government Minimum/Maximum to Order Minimum: 1.00 Dollars, U.S.

Maximum: 5,000,000.00 Dollars, U.S.

Item Supplies/Service Estimated Quantity

Unit Unit Price Amount

Ordering Period One, Operational Test & Evaluation services in accordance with the enclosed Performance Work Statement.

Pricing Arrangement: Firm Fixed Price

Pricing Arrangement: Firm Fixed Price

1 Unit

Travel in accordance with Performance Work Statement (RDT&E)

Pricing Arrangement: Cost No Fee

Pricing Arrangement: Cost No Fee

1 Unit

Section C - Description/Specifications/Statement of Work

1. Scope of Tasking. Contractor will provide technical and analytical support to Operational Test and Evaluation (T&E) Force (OPTEVFOR) Technical Point of Contact (TPOC), the Test Design Division (01B). The contractor will facilitate processes, aid in production, train personnel, and collaborate with stakeholders. This work will require adherence to policy, review of existing material, creation of unique inputs, attendance at working-groups, briefing of leadership, and tracking of metrics.

1.1. Tasking Categories. The tasking within this contract is divided into four categories.

1.1.1. Statistical Analysis. Support use of Scientific Test and Analysis Techniques (STAT), including Design of Experiments (DOE) and regression analysis, for pre-test design, mid-test adjustment, and post-test analysis. Tasking specifics are provided in section 2.

1.1.2. MBTD. Perform Core Team Facilitator (CTF) and training duties when directed. Tasking specifics are provided in section 3.

1.1.2.1. Facilitate the Mission-Based Test Design (MBTD) process, consulting with test teams to improve their Integrated Evaluation Frameworks (IEF) creation efforts. Contribute per policy to test strategies, test plans, and post-test processing.

1.1.2.2. Provide on-site and offsite training on MBTD policies and practices, to include a multi-day course for a classroom of students that can be run at OPTEVFOR or other customer organizations.

Classroom training for the Mission-Based Test and Evaluation System (MBTES) is not part of this contract.

1.1.3. Modeling and Simulation (M&S). Aid test teams in following the Verification, Validation and Accreditation (VV&A) processes when directed. Contribute per policy to requirements, plans, analyses, and letters. Tasking specifics are provided in section 4.

1.1.4. Accelerator Team. Support test programs that 01B designates as needing early involvement and/or additional assistance in test design, test planning, and/or post-test processing. These are programs for which other contract support is not yet established, or will not be funded. Tasking specifics are provided in section 5.

1.1.5. Program Management Support. The statistical analysis, MBTD, and M&S tasking categories have a combined program management support line item. The accelerator team also has program management support.

1.2. Background. OPTEVFOR is the Navy's Operational Test (OT) Activity (OTA), providing credible, prompt, warfighting-focused test results to the operational and acquisition communities of the Navy, Marine Corps, and Coast Guard.

Within this matrixed organization describe in reference (a), 01B functions as one of the three Competency Divisions, aiding the five Warfare Divisions in execution of OPTEVFOR's policies and processes.

1.2.1. MBTD. MBTD, documented in reference (b), is the foundational approach used to structure OT.

1.2.1.1. In test design, test teams identify the minimum and adequate data needed to assess the effectiveness, suitability, and cyber survivability of a System Under Test (SUT) in the context of a System of Systems (SoS). The test design is documented in the IEF per reference (c) or (d).

1.2.1.2. The test strategy incorporates MBTD, establishing agreement on the resources required to support the scope of data collection, as well as a notional schedule for test execution and resource use.

Alignment of OT with Developmental Test (DT) events allows for integrated test. Test and Evaluation Master Plan (TEMP) and Master Test Strategy (MTS) policies are found in references (e) and (f).

1.2.1.3. The MBTD process enables the Level-of-Test Determination (LTD) process summarized in reference (b). The decision options are OT, OTA observe DT, and no OTA participation.

1.2.1.4. MBTD principles also apply in test planning per reference (g) and reporting per reference (h).

1.2.1.5. MBTD enables test for organizations other than OPTEVFOR. Personnel from those organizations have come to OTPEVFOR for training. OPTEVFOR also takes training courses off-site as needed. One of these courses has been focused on MBTD.

1.2.2. STATs. Complex statistical calculations are supported by the 01B Analyst cell per reference (i), and done using methods accepted by academia with tools hosted on OPTEVFOR networks.

1.2.2.1. Tests that measure stochastic behaviors may require multiple samples under varying conditions to characterize performance across the battlespace. If applicable, DOE will be used pre-test to identify the most efficient test design. When DOE does not apply, other statistical methods can be used to scope test.

Design efforts are per reference (b).

1.2.2.2. Data may be analyzed using inferential statistical methods after completion of the test to determine what effects were significant to the performance of the system. Regression analysis yields a predictive statistical model. Post-test analysis follows reference (h).

1.2.2.3. Training to test teams is required to ensure both OPTEVFOR personnel and external stakeholders understand the use and application of STATs. 01B accomplishes this on a team-by-team basis, rather than formal courses.

1.2.3. M&S VV&A. M&S use in OT is expanding. Effective use of M&S for OT relies on MBTD, STATs, and other disciplines specific to the VV&A process documented in references (j) and (k). The OTA documents M&S requirements per reference (l), documents the accreditation plan per reference (m), and issues accreditation conclusions per reference (n).

1.2.4. Accelerated Acquisition Paths. Programs following the Middle Tier of Acquisition (MTA) path move quickly, while Software Acquisition Pathway (SWP) programs move faster still. There are also tests associated with Science and Technology (S&T) Fleet Experimentation (FLEX), S&T Rapid Capability Delivery (RCD), and Urgent Capability Acquisition (UCA). 01B may provide support to augment the warfare division. Adjustments to MBTD processes to meet the speed of SWP are provided in reference (o). The applicability of MBTD and TIEFs to S&T is covered by Reference (p).

1.3. Period of Performance. Performance period is 12 months from date of award with the option for four additional 12 month periods (Base + four option years) to be exercised at the discretion of the government.

1.3.1. Facilitation. Statistical Analysis, MBTD, and M&S facilitation is anticipated to be needed for the base year and all four option years.

1.3.2. Classroom Training. Presenting of classroom training on MBTD will be a separate line item. Extension of other work into option years does not guarantee extension of the training class.

1.3.3. Accelerator Team. The Accelerator Team will be a separate line item from the other two. Extension of other work into option years does not guarantee extension of the Accelerator Team.

1.4. Place of Performance. Unless required to support mission accomplishment, work shall primarily be performed at the customer's site. The customer location is :

Operational Test and Evaluation Force

7970 Diven Street

Norfolk, VA 23505-1498

1.4.1. The contractor shall comply with reference (q) with specific regard to non-government hardware and software.

1.4.2. The government will provide the contractor access to government facilities, as required, for performance of tasks under this contract. Contractor personnel shall comply with the instructions/guidance required by the facility.

1.5. Travel requirements per year. All travel costs shall be In Accordance With (IAW) the Federal Travel Regulations (FTR). Invoices shall include actual costs experienced. Airfare shall be based on the lowest available cost for coach or economy in writing, in advance. Travel dates and locations must be confirmed and approved in writing through the TPOC prior to commencement of any travel. The boxes below depict the anticipated travel for one year but will be repeated for each Option Year if the associated tasking category is exercised.

1.5.1. Facilitation

Location # of Trips # of Days each Trip

Patuxent River, MD 2 2

Washington DC Area 2 2

1.5.2. Training

Location # of Trips # of Days each Trip

Port Hueneme, CA 1 5

1.5.3. Accelerator Team

Location # of Trips # of Days each Trip

Patuxent River, MD 1 2

Washington DC Area 2 2

China Lake, CA 1 5

1.5.4. The contractor is not authorized to perform any travel that is not in conjunction with this contract. It is the Department of the Navy (DON) policy not to allow a charge of profit or fee on reimbursable items. The government will make no reimbursements for a contractor's local travel. The contractor shall not exceed the amount specified in the contract for travel.

1.6. Other Direct Cost (ODC). No ODC expenses are budgeted for this contract.

1.7. Personal Services. This is not a personal services contract. The contractors/sub-contractors should be welleducated in respect to "personal services". No one (government employee or military) may task the contractor to perform work that is not listed in a task order.

1.8. Automated Data Processing (ADP) Requirements. The government will provide, if required, the necessary computer workstation/system access for on-site work. The offerors assigned ADP Government Furnished Property (GFP) will be held accountable to respond to the governments ADP inventory requirements conducted semi-annually re-occurring every Mar and Sep to ensure 100% accountability of all ADP assets. Any offeror not adhering to this call for inventory of ADP assets may be directed to forfeit their ADP GFP at no additional cost to the government IAW FAR 52.245-1.

1.9. Common Access Card (CAC) / Public Key Infrastructure (PKI), System Authorization Access Request (SAAR)-Navy (SAAR-N). All contractor personnel requiring access to Government Information Technology systems shall have an approved SAAR-N Form OPNAV 5239/14 (Rev Sep 2011) on file, and complete required Annual Information Awareness Training. New employees must submit their SAAR forms upon checkin on their first day of work. SAAR-N forms shall be submitted to the Command Information Officer (CIO) Department, specifically the Information Systems Security Manager (ISSM). Instructions for processing the SAAR-N forms are available from the CIO Department.

1.10. CAC / Local Badges. Contractor CACs and facility-specific identification badges will be issued by the government to on-site contractor personnel and shall be visible at all times while personnel are at the government site. The contractor shall furnish all requested information required to facilitate issuance of identification badges and shall conform to all instructions/guidance required by the facility. All CACs and identification badges issued to contractor employees shall be returned to the Government Security Department at the government site IAW the instructions/guidance required by the OPTEVFOR facility following completion of the contract, relocation or termination of an employee, or upon request from the Contracting Officer's Representative.

2. Statistical Analysis Tasking/Deliverables. The government reserves the right to specify deliverables at the task order level.

Items required from the contractor under this tasking are specified in the Contract Data Requirements List (CDRL) 001-005. Up to six separate programs will be worked in parallel. Tasking to support these programs simultaneously is expected to occupy the full workload of two personnel. The personnel offered as analysts will complete the following tasks:

2.1. Test design

2.1.1. The contractor will act in the STAT analyst role supporting creation of test designs to scope OT IAW references (b) and (i). When assigned, the contractor shall:

2.1.1.1. Review program source data and existing MBTD products, as needed, to implement STATs in the MBTD test design phase.

2.1.1.2. Train test teams on STAT implementation for design.

2.1.1.3. Appraise the candidate Response Variables (RV) and other effectiveness critical measures for validity of use of STATs.

2.1.1.4. Leverage existing data, performance predictions, and/or other quantitative means to inform STAT method selection and to align accepted uncertainty with expected results.

2.1.1.5. Consider the conditions/descriptors associated with each critical measure, including their assigned roles as blocks, factors, constants, or recordables.

2.1.1.6. Understand and account for test realities that yield blocking, hard-to-change factors, disallowed combinations, and/or other design constraints.

2.1.1.7. Coordinate with the test team to select deltas and/or interval widths that are operationally meaningful.

2.1.1.8. Consult with the test team to understand reasonable resourcing expectations for the test, and the related impacts to design.

2.1.1.9. Apply inferential statistical tools and methods to produce a test designs IAW OPTEVFOR best practices, Department of Navy (DoN) and Department of Defense (DoD) T&E policy, and commonly accepted industry practices.

2.1.1.10. Employ the appropriate statistical tools to make calculations.

2.1.1.11. Create sizing options that allow leadership to make impactful selections within the trade space of cost, schedule, and precision.

2.1.1.12. When needed, produce a run matrix for each RV, implementing randomization as appropriate.

2.1.1.13. Consult with the test team to verify the test design can be executed.

2.1.1.14. If warranted, propose changes to design inputs (measures, conditions, descriptors, roles, expectations, methods, etc.) to enable better design outputs.

2.1.1.15. Obtain peer review of test designs.

2.1.1.16. When appropriate, consult with test teams mid-test to adjust designs or to determine if data collection can end early based on results to date.

2.1.1.17. As needed, consult on other program documents and briefings to include the Executive In- Process Review (E-IPR), stakeholder collaboration briefings, and Running Comment Resolution Matrices

(CRM) (RCRM).

2.1.2. Collaboration and meetings. When assigned, the contractor shall:

2.1.2.1. Identify and recommend outside organization(s) for participation and inclusion in OT design activities.

2.1.2.2. Participate in briefings/meetings as a STAT analyst in support of Test Design activities IAW references (a), (b), and (i).

2.1.2.3. As directed, lead briefings/meetings in support of STAT implementation IAW references (b) and (i).

2.1.2.4. Aid the test team in responding to stakeholder comments specific to STAT implementation.

2.1.2.5. Attend trainings that promulgate policy and best practices relevant to the STAT analyst role.

2.1.3. Documents, briefs, and tools. When assigned, the contractor shall:

2.1.3.1. Provide any run table files to the test team that can be easily imported to MBTES.

2.1.3.2. Document the test designs by inputting the STAT Analyst portions of reference (c).

2.1.3.3. As directed, review and/or prepare OPTEVFOR Test Design Policy guidance.

2.1.3.4. When appropriate or as directed, review, recommend, or create STAT tools for design.

2.1.3.5. As directed, adjust and/or maintain STAT software tools for design.

2.2. Post-test analysis

2.2.1. The contractor will act in the STAT analyst role supporting post-test data analysis IAW references (g) and (i).

When assigned, the contractor shall:

2.2.1.1. Receive data from test teams, and consult on whether it contains the information implied by the original test design.

2.2.1.2. Apply statistical tools and methods to produce exploratory data analysis.

2.2.1.3. Train test teams on STAT implementation for analysis.

2.2.1.4. Advise the test team on whether the collected data is sufficient for the intended analysis.

2.2.1.5. Apply statistical tools and methods to produce performance characterization for RVs defined in the test plan.

2.2.1.6. Apply statistical tools and methods to produce descriptive statistics and/or hypothesis testing results for RVs identified in the test plan where sufficient data is not available for RV analysis.

2.2.1.7. As directed, calculate reporting inputs for non-RV confidence intervals, tolerance intervals, or hypothesis tests.

2.2.1.8. Obtain peer review of RV analyses.

2.2.1.9. Support 01B Director review of RV analysis results.

2.2.1.10. As needed, advise the test team on how to best capture the characterization results in the report.

2.2.2. Collaboration and meetings. When assigned, the contractor shall:

2.2.2.1. Identify and recommend outside organization(s) for participation and inclusion in OT Post-Test Iterative Process (PTIP) activities.

2.2.2.2. When appropriate, participate in briefings/meetings as a STAT analyst in support of PTIP activities IAW references (h) and (i).

2.2.3. Documents, briefs, and tools. When assigned, the contractor shall:

2.2.3.1. Document RV analysis briefs per reference (r) for critical measures defined as RVs in the test plan.

2.2.3.2. When appropriate, provide documents and/or briefings to the test team for inclusion in the Data Analysis Summary.

2.2.3.3. As directed, review and/or prepare OPTEVFOR PostTest Analysis Policy guidance.

2.2.3.4. When appropriate or as directed, review, recommend, or create STAT tools for analysis.

2.2.3.5. As directed, adjust and/or maintain STAT software tools for analysis.

2.3. Program management support

2.3.1. The contractor shall, IAW CDRL A001, provide trip reports with a synopsis of meetings attended, meeting attendees, major outcomes/coordination, and action items applicable to OPTEVFOR.

2.3.2. The contractor shall, IAW CDRL A002, provide the TPOC monthly reports including the progress of work on assigned tasks, conferences/meetings attended, work plans and the expenditure of funds, and labor hours during the month.

2.3.3. The contractor shall, IAW CDRL A003, provide the TPOC with a technical reports summary of all technical reports delivered during the reporting period.

2.3.4. The contractor shall, IAW CDRL A004, provide the government an annual assessment of performance in a Contract Performance Assessment Report (CPAR).

2.3.5. The contractor shall, IAW CDRL A005, provide resumes for all personnel proposed to perform work on this contract. The government shall review and determine acceptability.

*** See Attached Performance Work Statement for further Information ***

Requirements COMOPTEVFOR requires technical and analytical support within the 01B competency, completing documentation review, stakeholder collaboration, team training, process facilitation, working-group attendance, test desing, modeling and simulation support, test planning, data analysis, and product/document creation.

Section D - Packaging and Marking

All deliverables shall be packaged and marked IAW Best Commercial Practices.

Section E - Inspection and Acceptance

QASP

Purpose: To ensure that the government has an effective and systematic method of surveillance for the services in the PWS. The QASP will be used primarily as a tool by the contractor and the government to verify that the contractor is performing all services required by the PWS in a timely, accurate and complete manner.

1. Critical performance processes and requirements. Critical to the performance of these services is the timely, accurate and thorough completion of all contract/task order requirements.

2. Quality Definitions.

a. Milestones. A milestone is any meeting, defined as part of a test design, test planning, modeling and simulation validation or test reporting process as outlined in references listed in section 13 of this document, or any Test and Evaluation (T&E) meeting outlined by a formal or informal T&E WIPT determination. Informal or intermediate milestones may also be established by the government at the discretion of the Operational Test Director (or similar government representative); this informal milestone may also be referred as a "deadline" or "due date" etc.

b. Deliverables.

i. Any test document or product considered to be the final test document meant for routing to signature by the government as outlined in Table 2-4 of the OPTEVFOR M-3980.2 series. This includes but is not limited to Integrated Evaluation Frameworks, Test Plans, and Test Report products. in accordance with the specific work statement for a program. The contractor retains responsibility for performing any work specified in the Statement of Work until the specific test document or product is signed by the appropriate authority.

ii. Any intermediate test document or product created or edited by the vendor that is not considered to be a T&E document, as defined in QASP paragraph 2.b.i, intended to be in support of a final document deliverable. This includes all read ahead material to support intermediate or final Mission Based Test Design, Test Planning, Test Reporting, or other efforts directed by the government in accordance with the specific work statement for a program.

iii. Any draft test document or product developed for collaboration with the government or T&E stakeholders for intermediate or final test documents that is not considered to be a T&E document, as defined in QASP paragraph 2.b.i or 2.b.ii, purposed to be in support of a final document deliverable.

c. Quality Scale. In general terms, comments regarding quality may be described in the following terms:

i. Critical (C) comments are provided because sections in the document appear to be or are potentially incorrect, incomplete, missing pertinent T&E information, or not in accordance with the prescribed applicable template. Critical comments preclude the test team from proceeding to meet the next scheduled milestone.

ii. Substantive (S) comments are provided because sections in the document appear to be or are potentially unnecessary, have minor incorrect, incomplete, misleading, confusing information, or inconsistencies with other sections that do not preclude the test team from proceeding to meet the next scheduled milestone.

iii. Administrative (A) comments are provided because sections in the document appear to contain typographical, formatting, or grammatical errors. Administrative comments do not preclude the test team from proceeding to meet the next scheduled milestone.

iv. The government designated representative shall qualify each comment (or group of comments) with its appropriate level of criticality (C, S, A) to support First Pass Yield (FPY) determinations, when appropriate.

3. Performance Standards

Schedule - The due dates for deliverables and the actual accomplishment of the schedule will be assessed against original due dates and milestones established for the contract or task order(s).

.Performance Standard for Acceptable Quality Level

a. Performance Metric (Schedule). An accepted schedule metric of above 95 percent (>95%) FPY for delivery of all intermediate or final test document or products on time related to prescribed deadlines provided by the designated government representative. If the contractor does not provide a test document or product due to schedule slip by the contractor resulting in a missed deadline (termed here as a 'schedule defect'), it will result in a failure to meet the FPY performance metric.

b. Timeliness of Deliverables.

i. Intermediate Test Product Deadline. Delivery of all intermediate test product (i.e. read ahead material) shall be provided to the Warfare Division Section Head (or designated representative) for acceptance by the government in accordance with timelines outlined in the applicable published checklist, handbook, best practice, etc. These publications are posted to the OPTEVFOR SharePoint site (NIPR) or OT&E Reference Library folder or OT&E Production Library folder on the Y: drive (SIPR).

ii. Draft Test Product Collaboration. The contractor may submit draft or "working" versions of the intermediate test product to the Operational Test Director (OTD), Lead Test Engineer (LTE), etc. as required to enable collaboration, obtain early feedback, or facilitate efforts to resolve T&E issues or questions within the document. Review of a draft product shall not be considered as "Submission of Deliverables to the Government" and draft Test Product Collaboration shall not delay or disrupt required schedule of delivery for intermediate or final test product deadlines.

iii. Schedule Slip due to Government Induced Delays. Inherent to the acquisition process, a program may experience a schedule slip due to various factors. These "Government Induced Delays" may impact or affect the timelines for deliverables as outlined in the Statement of Work for each Task Order (TO). In the event of a Government Induced Delay, it is the responsibility of the OTD, Section Head, and contractor assigned to the specific TO, to alert the Warfare Division Deputy Director or their alternate at the soonest possible time. The OTD, Section Head, LTE and contractor shall assess the impact of the delay on schedule deadlines provided to the contractor. If the delay is significant enough to prevent the contractor from submitting deliverables on time, the OTD (or designated government representative) shall discuss the potential impact to the overall schedule with the Contracting Officer Representative (COR) and contractor to determine if a formal modification to the overall schedule with an updated schedule for deliverables (to include intermediate test products) is required.

iv. Schedule Slip due to Contractor Delays. If the contractor fails to submit deliverables to the government, not due to government induced delays or where an adjusted deadline has not been approved by the designated government representative, this will be considered a schedule slip due to contractor delays. Any unplanned schedule slip due to a contractor delay must be forecasted as soon as recognized to the government representative by the contractor to afford corrective mitigation to the acquisition schedule.

c. Deliverables - The deliverables section required to be submitted will be assessed against the specifications for the deliverables detailed in the contract/task order(s) and the Quality Control Plan (QCP), if required by the contract, for the required content, quality, timeliness, and accuracy.

i. Submission of Deliverables to the Government. All Deliverables listed will be delivered by the Contractor in accordance with the Quality Assurance Surveillance Plan (QASP). For determination of , the contractor shall "Timeliness" submit deliverables via email to the OTD, Section Head, and other applicable recipients identified at time of task order award and/or during execution during the Period of Performance (PoP). Upon receipt, the Section Head will send an email to the Warfare Division Deputy Director facilitating the formal government's position for the respective product for timeliness and/or accuracy within 48 hours upon receipt of the deliverable. The Warfare Division Deputy Director or alternate will forward a copy of this email to the Contracting Officer's Representative (COR) and prime vendor representative for the TO as required; the email will become part of the COR folder for that respective TO.

ii. Government Induced Errors (GIE) after Contractor submission to the Government . A government induced error is defined as an error that was determined to be qualitatively or quantitatively incorrect from the original contractor's submission of that deliverable to the government. Any GIE identified shall not be counted as part of the First Pass Yield (FPY) as described in paragraph 3.e. of this document.

iii. Acceptance of Deliverables by the Government. Any test document, as outlined above in QASP paragraph 2.

b.i, is accepted by the government when the specific test document or product is signed by the appropriate authority. Any intermediate deliverable, as outlined above in QASP paragraph 2.b.ii, is accepted by the government when the Section Head, OTC, or OTD (if delegated) has approved the deliverable to be issued as read ahead material for a test product milestone meeting or document routing for signature. Acceptance by the government may be via memorandum, e-mail (preferred), or verbal statement (followed by an email). Acceptance by the government states it now has sole responsibility for that document.

Performance Standard for Acceptable Quality Level.

i. An accepted quality metric of above 95 percent (>95%) FPY is desired for delivery of all intermediate or final test document or products without administrative, substantive, or critical comments related to document quality (termed here as a 'quality defect'). This is also defined as 'No rework required'.

ii. FPY percentage is defined as by the government for the first time for an number of documents accepted intended purpose divided by the to the government for the first time for an intended total number of documents provided purpose, . Draft test documents or products will not count towards FPY until formally submitted to the multiplied by 100 government for an intended purpose to meet intermediate or final test product milestones.

i. Any comment related to the lack of specific System Under Test (SUT) or programmatic information required for a T&E document is not considered to be a quality defect.

ii. If, at any time, the FPY is below 85 percent (<85%), or the government perceives repetitive or consistently poor performance regardless of FPY metrics, the issue shall be referred to the COR for further action.

b. Past Performance - In addition to any schedule and deliverable aspects of performance discussed above, pursuant to FAR 42.15, the government will assess the contractor's record of conforming to contract requirements and to standards of good workmanship, the contractor's adherence to contract schedules including the administrative aspects of performance, the contractor's history of reasonable and cooperative behavior and commitment to customer satisfaction, and the contractor's business-like concern for the interest of the customer.

2. Surveillance methods : The primary methods of surveillance used to monitor performance of this contract will include, but not be limited to, random or planned sampling, periodic inspection, and validated customer complaints.

3. Performance Measurement : Performance will be measured in accordance with the following table:

Performance Element

Requirement

Surveillance Method

Frequency Acceptable Quality Level

Contract Deliverable A001

T&E Documents or

Briefs

Periodic

/Customer Input

Planned/Task Order Initiated

>95% of deliverables submitted timely and without rework required

Periodic

A002

Trip Report

Input

Planned/Task Order Initiated timely and without rework required

A003

Monthly Status Report (MSR)

Periodic

Input

Planned/Task Order Initiated

A003

Financial Status Report

Periodic

Input

Monthly starting after the third month of contract award.

Overall Contract

Overall contract performance of sufficient quality to earn a minimum Satisfactory rating in the COR's annual report on contractor performance

Assessment by the COR

Annual or at completion of performance

All performance elements rated Satisfactory (or higher)

Invoicing

Invoices per contract procedures are timely and accurate.

Review and acceptance of the invoice

As specified in contract

100% accuracy

DFARS clause 252.239-7001, Information Assurance Contractor

Training and Certification

100% compliance with the clause (As required)

100% surveillance

As specified in DFARS clause 2 5 2 . 2 3 9 -

100% compliance

FAR clause 52.222-

50, Combating Trafficking in

Persons

100% compliance with the clause

100% surveillance

As specified in FAR clause

52.222-

100% compliance

If performance is within acceptable levels, it will be considered to be satisfactory. If not, overall performance may be considered unsatisfactory.

1. Incentives/Disincentives:

The COR makes an annual report on contractor performance Contractor Performance Assessment Reporting System (CPARS) or other annual report. The contractor's failure to achieve a minimum satisfactory performance under the contract/task order, reflected in the COR's annual report, may result in termination of the contract/task order and may also result in the loss of future government contracts/task orders. The contractor's failure to achieve a minimum satisfactory performance under the contract/task order may result in the non-exercise of any available options, if applicable.

For each item that does not meet acceptable levels, the government may issue a Contract Discrepancy Report (CDR). CDRs will be forwarded to the Contracting Officer with a copy sent to the contractor. The contractor must reply in writing within 5 days of receipt identifying how future occurrences of the problem will be prevented. Based upon the contractor's past performance and plan to solve the problem, the Contracting Officer will determine if any further action will be taken.

For fixed-price contracts/orders, in accordance with the inspection of services provisions, the contractor will be incentivized to provide quality products in a timely manner since the government can require the Contractor, at no additional cost, to replace or correct work that fails to meet contract requirements.

(End of QASP)

COMMUNICATIONS DURING THE LIFE OF THE CONTRACT (SEP 2015)

(a) Except as specified in paragraph (b) below, no order, statement, or conduct of Government personnel who visit the Contractor's facilities or in any other manner communicates with Contractor personnel during the performance of this contract shall constitute a change under the "Changes" clause of this contract.

(b) The Contractor shall not comply with any order, direction or request of Government personnel unless it is issued in writing and signed by the Contracting Officer, or is pursuant to specific authority otherwise included as a part of this contract.

(c) The Contracting Officer is the only person authorized to approve changes in any of the requirements of this contract and, notwithstanding provisions contained elsewhere in this contract, the said authority remains solely the Contracting Officer's. In the event the contractor effects any change at the direction of any person other than the Contracting Officer, the change will be considered to have been made without authority and no adjustment will be made in the contract price to cover any increase in charges incurred as a result thereof. The address and telephone number of the Principal Contracting Officer is:

Carlton Walton carlton.t.walton.civ@us.navy.mil

(564) 230-1424

Overall Contract Inspection/Acceptance Locations

Inspection and Acceptance Location

Both Destination Instructions: See Statement of Work (SOW) or Performance Work Statement (PWS) for Acceptance/inspection criteria.

DoDAAC: N57023 CountryCode: USA

OPERATIONAL TEST AND EVALUATION

FORCE, 7970 DIVEN ST

NORFOLK, VA 23505-1498

UNITED STATES

Tim Burrows, Contracting Officer Representative

Email: timonty.r.burrows.civ@us.navy.mil Telephone: (757) 457-6563

Section F - Deliveries or Performance

DURATION OF CONTRACT PERIOD (SEP 2015)

(a) This contract shall become effective on , or the effective date of award, whichever is later, and the 16 May 2026 ordering period shall continue in effect during the period ending unless terminated in accordance with other 15 May 2031 provisions herein. Performance under task orders issued under this contract may begin and may on the effective date of award continue in effect during the period ending after the last day of the ordering period. 365 days

(b) Notwithstanding the above, the Contracting Officer may extend the contract ordering period to accommodate the issuance of task orders in accordance with paragraph (e) of "Level of Effort".

Overall Contract Delivery Period

Period of Performance From 16 May 2026 to 15 May 2031

The ordering period above may include unexercised options

Contractor Destination

Line Item Delivery Schedule Estimated Quantity

Address and POC

Period of Performance From 16 May 2026 To 15 May 2031

1 Unit

Period of Performance From 16 May 2026 To 15 May 2031

1 Unit

Section G - Contract Administration Data

APPOINTMENT OF CONTRACTING OFFICER'S REPRESENTATIVE (SEP 2015)

(a) The Contracting Officer hereby designates the following individual as Contracting Officer's Representative(s) (COR) for this contract:

Timothy Burrows timothy.r.burrows.civ@us.navy.mil 1 (757) 450-9486

(b) In the absence of the COR named above, all responsibilities and functions assigned to the COR shall be the responsibility of the alternate COR acting on behalf of the COR.

The Contracting Officer hereby appoints the following individual as the alternate COR:

N/A

CONTRACT ADMINISTRATION PLAN (CAP) FOR FIXED PRICE, INDEFINITE DELIVERY, CONTRACTS

In order to expedite the administration of this contract, the following delineation of duties is provided. The names, addresses and phone numbers for these offices or individuals are included elsewhere in the contract award document. The office or individual designated as having responsibility should be contacted for any questions, clarifications or information regarding the administration function assigned.

1. The Procuring Contract Office (PCO) is responsible for:

a. All pre-award duties such as solicitation, negotiation and award of contracts.

b. Any information or questions during the pre-award stage of the procurement.

c. Freedom of Information inquiries.

d. Changes in contract terms and/or conditions.

e. Post award conference.

2. The Contract Administration Office (CAO) is responsible for matters specified in FAR 42.302, except those areas otherwise designated as the responsibility of the Contracting Officer's Representative (COR) or someone else herein.

3. The paying office is responsible for making payment of proper invoices after acceptance is documented.

4. The Ordering Officer is responsible for:

a. Requesting, obtaining and evaluating proposals for orders to be issued.

b. Select the most advantageous offer to the Government for individual Task Orders in accordance with contract provisions. Determining that the price

/estimated cost of the order is fair and reasonable for the effort proposed.

c. Obligating the funds by issuance of the delivery order/task order.

d. Authorizing the contractor to begin performance.

e. Providing subcontract approval.

f. Monitoring direct costs on orders issued.

NOTE: The PCO and the Ordering Officer may be the same individual, but in no case shall the COR perform the duties of the Ordering Officer.

5. The Contracting Officer's Representative (COR) is responsible for interface with the contractor and performance of duties such as those set forth below. It is emphasized that only the PCO/CAO has the authority to modify the terms of the contract. In no event will any understanding, agreement, modification, change order, or other matter deviating from the terms of the basic contract between the contractor and any other person be effective or binding on the government. If in the opinion of the contractor an effort outside the scope of the contract is requested, the contractor shall promptly notify the PCO in writing. No action may be taken by the contractor unless the PCO or CAO has issued a contractual change. The COR duties are as follows:

a. Technical Interface

(1) The COR is responsible for all Government technical interface concerning the contractor and furnishing technical istructions to the contractor. These instructions may include: technical advice/recommendations/clarifications of specific details relating to technical aspects of contract requirements; milestones to be met within the general terms of the contract or specific subtasks of the contract; or, any other interface of a technical nature necessary for the contractor to perform the work specified in the contract or order. The COR is the point of contact through whom the contractor can relay questions and problems of a technical nature to the PCO.

N0018926RW016

mailto:timothy.r.burrows.civ@us.navy.mil

(2) The COR is prohibited from issuing any instruction which would constitute a contractual change. The COR shall not instruct the contractor how to perform. If there is any doubt whether technical instructions contemplated fall within the scope of work, contact the PCO for guidance before transmitting the instructions to the contractor.

b. Contract Surveillance

(1) The COR shall monitor the contractor's performance and progress under the contract. In performing contract surveillance duties, the COR should exercise extreme care to ensure that he/she does not cross the line of personal services. The COR must be able to distinguish between surveillance (which is proper and necessary) and supervision (which is not permitted). Surveillance becomes supervision when you go beyond enforcing the terms of the contract. If the contractor is directed to perform the contract services in a specific manner, the line is being crossed. In such as situation, the COR's actions would be equivalent to using the contractor's personnel as if they were government employees and would constitute transforming the contract into one for personal services.

(2) The COR shall monitor the contractor's performance to see that inefficient or wasteful methods are not being used. If such practices are observed, the COR is responsible for taking reasonable and timely action to alert the contractor and the PCO to the situation.

(3) The COR will take timely action to alert the PCO to any potential performance problems. If performance schedule slippage is detected, the COR should determine the factors causing the delay and report them to the PCO, along with the contractor's proposed actions to eliminate or overcome these factors and recover the slippage. Once a recovery plan has been put in place, the COR is responsible for monitoring the recovery and keeping the PCO advised of progress.

(4) If the Contractor Performance Assessment Reporting System (CPARS) is applicable to the contract you are responsible for completing a Contractor Performance Assessment Report (CPAR) in the CPARS Automated Information System (AIS). The initial CPAR, under an eligible contract, must reflect evaluation of at least 180 days of contractor performance. The completed CPAR, including contractor comments if any, (NOTE: contractors are allowed 30 days to input their comments) should be available in the CPARS AIS for reviewing official (PCO) review no later than 270 days after start of contract performance. Subsequent CPARs covering any contract option periods should be ready at 1-year intervals thereafter.

c. Invoice Review and Approval/Inspection and Acceptance

(1) The COR is responsible for quality assurance of services performed and acceptance of the services or deliverables. The COR shall expeditiously review copies of the contractor's invoices or vouchers, certificate of performance and all other supporting documentation to determine the reasonableness of the billing. In making this determination, the COR must take into consideration all documentary information available and any information developed from personal observations.

(2) The COR must indicate either complete or partial concurrence with the contractor's invoice/voucher by executing the applicable certificate of performance furnished by the contractor.

(3) The COR will provide the PCO and the CAO with copies of acceptance documents such as Certificates of Performance.

(4) Upon completion of all services under the contract, the COR shall work with the Contractor to obtain and execute a final invoice no more than 60 days after completion of contract performance. The COR shall ensure that the invoice is clearly marked as a "Final Invoice."

d. Contract Modifications/Orders Under Indefinite Delivery Contracts.

(1) The COR is responsible (if necessary) for developing the statement of work for tasking orders, change orders, or modifications and for preparing an independent government cost estimate of the effort described in the proposed statement of work.

(2) The COR shall provide available and relevant Past Performance information with each request for new Task Orders. The COR shall review and evaluate the contractor's proposal and furnish comments and recommendations

e. Administrative Duties

(1) The COR is responsible for taking appropriate action on technical correspondence pertaining to the contract and for maintaining files on each contract. This includes all modifications, government cost estimates, contractor invoices/vouchers, certificates of performance, DD 250 forms and contractor's status reports.

(2) The COR shall maintain files on all correspondence relating to contractor performance, whether satisfactory or unsatisfactory, and on trip reports for all government personnel visiting the contractor's place of business for the purpose of discussing the contract.

(3) The COR must take prompt action to provide the PCO with any contractor or technical code request for change, deviation or waiver, along with any supporting analysis or other required documentation.

f. Government Furnished Property. When government property is to be furnished to the contractor, the COR will take the necessary steps to ensure that it is furnished in a timely fashion and in proper condition for use. The COR will maintain adequate records to ensure that property furnished is returned and/or that material has been consumed in the performance of work.

g. Security. The COR is responsible for ensuring that any applicable security requirements are strictly adhered to.

h. Standards of Conduct. The COR is responsible for reading…