M00264-23-R-0010 WDALab.pdf

SEE ADDENDUM

(No Collect Calls)

M0026423R0010 22-May-2023

b. TELEPHONE NUMBER

703-432-1927

8. OFFER DUE DATE/LOCAL TIME

10:00 AM 30 Jun 2023

5. SOLICITATION NUMBER 6. SOLICITATION ISSUE DATE

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

STANDARD FORM 1449 (REV. 2/2012)

Prescribed by GSA – FAR (48 CFR) 53.212

(TYPE OR PRINT)

(SIGNATURE OF CONTRACTING OFFICER)

ADDENDA X ARE

26. TOTAL AWARD AMOUNT (For Gov t. Use Only )

23.

CODE 10. THIS ACQUISITION IS

SUCH ADDRESS IN OFFER

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT

BELOW IS CHECKED

TELEPHONE NO.

M002649. ISSUED BY

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

7. FOR SOLICITATION

INFORMATION CALL:

a. NAME

SHAYE NELSON

2. CONTRACT NO. 3. AWARD/EFFECTIVE DATE 4. ORDER NUMBER

(TYPE OR PRINT)

30b. NAME AND TITLE OF SIGNER 30c. DATE SIGNED 31b. NAME OF CONTRACTING OFFICER

30a. SIGNATURE OF OFFEROR/CONTRACTOR 31a.UNITED STATES OF AMERICA

27a. SOLICITATION INCORPORATES BY REFERENCE FAR 52.212-1. 52.212-4. FAR 52.212-3. 52.212-5 ARE ATTACHED.X

25. ACCOUNTING AND APPROPRIATION DATA

1. REQUISITION NUMBER

20.

ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED.

OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, AND 30

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

ARE NOT ATTACHED

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

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

SET FORTH HEREIN, IS ACCEPTED AS TO ITEMS:

. YOUR OFFER ON SOLICITATION

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN

% FOR:SET ASIDE:UNRESTRICTED OR X

SMALL BUSINESSX

17a.CONTRACTOR/ CODE FACILITY

OFFEROR CODE

MCINCR - RCO

2010 HENDERSON RD SHAYE NELSON

QUANTICO VA 22134

18a. PAYMENT WILL BE MADE BY CODE

RATED ORDER UNDER

DPAS (15 CFR 700)

13a. THIS CONTRACT IS A

13b. RATING

CODE15. DELIVER TO CODE 16. ADMINISTERED BY

SEE SCHEDULE

12. DISCOUNT TERMS11. DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS

MARKED

SEE SCHEDULE

14. METHOD OF SOLICITATION

RFQ IFB RFPX

FAX:

TEL: 703-432-1927

SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

8(A)

HUBZONE SMALL

BUSINESS

SIZE STANDARD:

$30,000,000

NAICS:

541511

X

OFFER DATED

29. AWARD OF CONTRACT: REF.

DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND ON ANY

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND

EMAIL:

TEL:

31c. DATE SIGNED

SEE SCHEDULE

SCHEDULE OF SUPPLIES/ SERVICESITEM NO. QUANTITY UNIT UNIT PRICE AMOUNT

24.22.21.19.

WOMEN-OWNED SMALL BUSINESS (WOSB)

ELIGIBLE UNDER THE WOMEN-OWNED

SMALL BUSINESS PROGRAM

EDWOSB

32g. E-MAIL OF AUTHORIZED GOVERNMENT REPRESENTATIVE

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

(CONTINUED)

PAGE 2 OF74

ACCEPTED, AND CONFORMS TO THE CONTRACT, EXCEPT AS NOTED: ______________________________________________________

32a. QUANTITY IN COLUMN 21 HAS BEEN

RECEIVED INSPECTED

32b. SIGNATURE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32c. DATE 32d. PRINTED NAME AND TITLE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32e. MAILING ADDRESS OF AUTHORIZED GOVERNMENT REPRESENTATIVE 32f . TELEPHONE NUMBER OF AUTHORIZED GOVERNMENT REPRESENTATIVE

37. CHECK NUMBER

FINALPARTIALCOMPLETE

36. PAYMENT35. AMOUNT VERIFIED

CORRECT FOR

34. VOUCHER NUMBER

FINAL

33. SHIP NUMBER

PARTIAL

38. S/R ACCOUNT NUMBER 39. S/R VOUCHER NUMBER 40. PAID BY

41a. I CERTIFY THIS ACCOUNT IS CORRECT AND PROPER FOR PAYMENT

41b. SIGNATURE AND TITLE OF CERTIFYING OFFICER 41c. DATE

42a. RECEIVED BY (Print)

42b. RECEIVED AT (Location)

42c. DATE REC'D (YY/MM/DD) 42d. TOTAL CONTAINERS

STANDARD FORM 1449 (REV. 2/2012) BACK

Prescribed by GSA – FAR (48 CFR) 53.212

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

SEE SCHEDULE

20.

SCHEDULE OF SUPPLIES/ SERVICES

21.

QUANTITY UNIT

22. 23.

UNIT PRICE

24.

AMOUNT

19.

ITEM NO.

M0026423R0010

Section SF 1449 - CONTINUATION SHEET

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0001 12 Each

MODIFY, UPDATE, & MAINTAIN WDALAB

FFP

In accordance with PWS para 6.1.

FOB: Destination

PSC CD: R425

NET AMT

0002 4 Each

DATA FILE INPUT

FFP

In accordance with para 6.2.

0003 4 Each

DATA FILES OUTPUT

FFP

In accordance with PWS para 6.3.

0004 12 Each WDALab DOCUMENTATION

FFP

In accordance with PWS para 6.4.

0005 Each Travel

COST

Government directed travel in accordance with PWS para 8.3. The Government estimate for the base period is $50,000.00. This is a Not-to-Exceed (NTE) cost reimbursable, non-fee bearing line item. Travel shall be in direct support of tasks within the attached PWS and will be reimbursed only in accordance with FAR

Part 31.205-46 and only up to the NTE amount identified in this order or as modified by the Government.

ESTIMATED COST

1001 12 Each

OPTION MODIFY, UPDATE, & MAINTAIN WDALAB

FFP

In accordance with PWS para 6.1.

1002 4 Each

OPTION DATA FILE INPUT

FFP

In accordance with para 6.2.

1003 4 Each

OPTION DATA FILES OUTPUT

FFP

In accordance with PWS para 6.3.

1004 12 Each OPTION WDALab DOCUMENTATION

FFP

In accordance with PWS para 6.4.

1005 Each OPTION Travel

COST

Government directed travel in accordance with PWS para 8.3. The Government estimate for the base period is $52,000.00. This is a Not-to-Exceed (NTE) cost reimbursable, non-fee bearing line item. Travel shall be in direct support of tasks within the attached PWS and will be reimbursed only in accordance with FAR

Part 31.205-46 and only up to the NTE amount identified in this order or as modified by the Government.

2001 12 Each

OPTION MODIFY, UPDATE, & MAINTAIN WDALAB

FFP

In accordance with PWS para 6.1.

2002 4 Each

OPTION DATA FILE INPUT

FFP

In accordance with para 6.2.

2003 4 Each

OPTION DATA FILES OUTPUT

FFP

In accordance with PWS para 6.3.

2004 12 Each OPTION WDALab DOCUMENTATION

FFP

In accordance with PWS para 6.4.

2005 Each OPTION Travel

COST

Government directed travel in accordance with PWS para 8.3. The Government estimate for the base period is $54,080.00. This is a Not-to-Exceed (NTE) cost reimbursable, non-fee bearing line item. Travel shall be in direct support of tasks within the attached PWS and will be reimbursed only in accordance with FAR

Part 31.205-46 and only up to the NTE amount identified in this order or as modified by the Government.

3001 12 Each

OPTION MODIFY, UPDATE, & MAINTAIN WDALAB

FFP

In accordance with PWS para 6.1.

3002 4 Each

OPTION DATA FILE INPUT

FFP

In accordance with para 6.2.

3003 4 Each

OPTION DATA FILES OUTPUT

FFP

In accordance with PWS para 6.3.

3004 12 Each OPTION WDALab DOCUMENTATION

FFP

In accordance with PWS para 6.4.

3005 Each OPTION Travel

COST

Government directed travel in accordance with PWS para 8.3. The Government estimate for the base period is $56,243.00. This is a Not-to-Exceed (NTE) cost reimbursable, non-fee bearing line item. Travel shall be in direct support of tasks within the attached PWS and will be reimbursed only in accordance with FAR

Part 31.205-46 and only up to the NTE amount identified in this order or as modified by the Government.

4001 12 Each

OPTION MODIFY, UPDATE, & MAINTAIN WDALAB

FFP

In accordance with PWS para 6.1.

4002 4 Each

OPTION DATA FILE INPUT

FFP

In accordance with para 6.2.

4003 4 Each

OPTION DATA FILES OUTPUT

FFP

In accordance with PWS para 6.3.

4004 12 Each OPTION WDALab DOCUMENTATION

FFP

In accordance with PWS para 6.4.

4005 Each OPTION Travel

COST

Government directed travel in accordance with PWS para 8.3. The Government estimate for the base period is $58,493.00. This is a Not-to-Exceed (NTE) cost reimbursable, non-fee bearing line item. Travel shall be in direct support of tasks within the attached PWS and will be reimbursed only in accordance with FAR

Part 31.205-46 and only up to the NTE amount identified in this order or as modified by the Government.

PERFORMANCE WORK STATEMENT

PERFORMANCE WORK STATEMENT

FOR

U. S. MARINE CORPS TRAINING & EDUCATION COMMAND (TECOM)

RANGE AND TRAINING AREA MANAGEMENT (RTAM)

WEAPON DANGER AREA LABORATORY SUPPORT

1. BACKGROUND

RTAM has agreed to lead a group comprised of the United States Marine Corps, United States Army and the United

Kingdom (UK) Ministry of Defence (MOD) in the development, maintenance and standardization of the Weapon

Danger Area Laboratory application and associated models. As the resource sponsor, RTAM is responsible for the development and implementation of institutional programs to sustain, upgrade, and modernize Marine Corps training ranges that support the achievement and maintenance of combat readiness. RTAM provides for Range and

Training Area (RTA) management through a myriad of functions/programs with a focus in this requirement related to range safety. Tasked with those responsibilities, RTAM executes and implements requirements as derived from numerous Marine Corps Orders, North Atlantic Treaty Organization (NATO) Standardization Agreements

(STANAGS) and Allied Range Safety Publications (ARSP) that delineate the responsibilities and requirements for range safety and operations. The UK MOD is the British government department responsible for implementing the defence policy set by His Majesty's Government and is the headquarters of the British Armed Forces.

Due to increasing encroachment and longer effective distances of weapons the United States and United Kingdom have incorporated a modeling-based approach to quantify risk associated with direct fire and indirect fire weapons and their projectiles as we operate some of the most complex and dynamic training ranges in the world. The modeling-based approach is based upon the Weapon Danger Area Laboratory (WDALab) Application. The

WDALab Application is a suite of software initially developed by the Ministry of Defence (MOD) Defence

Ordnance Safety Group (DOSG) to simulate the behavior of non-complex ballistic projectiles to determine the projectiles behavior against specified probabilistic criteria required for range safety assessments. It is a Graphical

User Interface (GUI) based application written in both Visual Fortran (GUI) and standard Fortran (engine).

WDALab was initially developed to undertake Probabilistic Risk Assessments of unguided weapon systems fired on a range. The WDALab application is the practical implementation of Allied Range Safety Publication (ARSP) 02

Volumes I and II, and the UK has made WDALab available to The Technical Cooperation Program (TTCP) partner nations beginning in approximately 2005. WDALab is comprised of a suite of tools with a modular code construction, with sections covering the key processes of the calculation namely - Metrology, Terrain, Firer, Warhead and configuration. Within each section a number of sub routines are managed to provide the necessary conversions, calculations and outputs that are required to produce the required result.

As part of The Technical Programme (TP) 8, Conventional Weapons Technology Group a comprehensive review and evaluation of the WDALab probabilistic tool was undertaken. TTCP is a five nation Memorandum of

Understanding (MOU) between Australia, Canada, New Zealand and the United Kingdom of Great Britain and

Northern Ireland and the United States of America. During this review and evaluation, it was discovered that the

United States Marine Corps, United States Army and the UK MOD are accepting risk on training ranges as there is no consolidated, consistent, and modern way to update and maintain the models contained within WDALab. In addition, as models were developed by the United States for indirect fire carrier shells and 120mm tank munitions it was discovered that incorporating an updated model into the WDALab is not defined nor do the existing models accept the newer model inputs for indirect fire or tank munitions.

2. SCOPE

The scope of this effort is to provide key expertise and support to the Marine Corps Range program for the updating and modification of the existing WDALab code, methodologies, and graphic user interfaces. These services will provide the required expertise and support for the updating or changing of Visual Fortran (GUI) and standard

Fortran (engine) models associated with the WDALab.

The primary place of performance shall be at the Contractors off base facility and off installation office spaces will be available at the time of award. It is anticipated to have meetings for individual requirements with 5-15 (15 maximum) personnel biweekly at the contractor off installation office spaces as well as a monthly on-site progress meeting with TECOM Government personnel on MCB Quantico, VA as well. The Government will provide user accounts and connectivity to the MCEN. The majority of the work shall be performed on normal Government workdays, legal holidays excluded, between the hours of 0700 and 1630. Video teleconference capability is required and access to various teleconference sites will be required. Primary teleconference site will be All Partners

Access Network (APAN) with access facilitated by the COR.

3. DIRECTIVE TYPE DOCUMENTS

Applicable Marine Corps Orders and Directive documents associated with the operation and management of the

WDALab.

• MCO 3570.1C, Range Safety

• STANAG 2470 Probabilistic determination of weapon danger areas

• ARSP-02 Volume I Guidance on the development of weapon danger areas/zones – probabilistic methodology – general principals

• ARSP-02 Volume II Probabilistic determination of weapon danger areas – probabilistic methodology -application to unguided weapons systems

• ARSP-02 Volume III Probabilistic deterministic of weapon danger areas – probabilistic methodology – application to guided weapons systems

• ARSP-02 Volume IV Probabilistic determination of weapon danger areas – application to unmanned aerial vehicles

4. OBJECTIVES

This effort is to provide support to modify, update, maintain and develop the WDALab program models and associated graphical user interfaces (GUI). Incremental updates will be required for all tasks outlined below as defined in the work breakdown structure (WBS).

5. KEY PERSONNEL

Key personnel shall be defined by the Contractor. Support shall be available to work on the first day of the period of performance of the resultant contract. If it becomes necessary to replace support over the course of the contract, replacement personnel shall possess equivalent or better skills and level of experience. Replacement support must be evaluated via written resume by the COR and approved by the Procurement Contracting Officer (PCO) before replacement support can begin work. Contractor is required to notify in writing to the PCO of any desired change of support within 72 hours of the initial Contractor desired change. The Government will provide their determination within 5 working days. A minimum of 30 days shall be allotted for transfer of knowledge from one person to that person's replacement without cost to the Government.

6. TASKS

6.1 MODIFY, UPDATE, AND MAINTAIN WDALAB. The Contractor shall modify, update, and maintain the

WDALab with data provided by and approved by the COR at a minimum quarterly.

6.1.1 The contractor shall update, identify, and remove unwanted data and organize the database repository structure once the data repository structure is approved by the COR.

6.1.2 The contractor shall update, compile, and process by forward engineering the terrain model and GUI source code into a stand-alone form that enables the code to successfully start / run or execute the script to run on a computer utilizing the version of Windows as provided by the COR.

6.1.3 The contractor shall update, compile, and process by forward engineering the object model and GUI source code into a stand-alone form that enables the code to successfully start / run or execute the script to run on a computer utilizing the version of Windows as provided by the COR.

6.1.4 The contractor shall update, compile, and process by forward engineering the meteorology model and

GUI source code into a stand-alone form that enables the code to successfully start / run or execute the script to the code to run on a computer utilizing the version of Windows as provided by the COR.

6.1.5 The contractor shall update, compile, and process by forward engineering the firer model and GUI source code into a stand-alone form that enables the code to successfully start / run or execute the script to the code to run on a computer utilizing the version of Windows as provided by the COR.

6.1.6 The contractor shall update, compile, and process by forward engineering the weapon model and

GUI source code into a stand-alone form that enables the code to successfully start / run or execute the

6.1.7 The contractor shall update, compile, and process by forward engineering the warhead model and

GUI source code into a stand-alone form that enables the code to successfully start / run or execute the

6.1.8 The contractor shall update, compile, and process by forward engineering the configuration model and GUI source code into a stand-alone form that enables the code to successfully start / run or execute the

6.1.9 The contractor shall update, compile, and process by forward engineering the projectile model and

GUI source code into a stand-alone form that enables the code to successfully start / run or execute the

6.1.10 The contractor shall update, compile, and process by forward engineering the impact model and

GUI in the source code into a standalone form that enables the code to successfully start / run or execute the script to the code to run in the WDALab trajectory model once the changes are approved by the COR.

6.1.11 The contractor shall update, compile, and process by forward engineering the post impact model and GUI in the source code into a standalone form that enables the code to successfully start / run or execute the script to the code to run in the WDALab trajectory model once the changes are approved by the

COR.

6.1.12 The contractor shall update, compile, and process by forward engineering the post processing model and GUI in the source code into a standalone form that enables the code to successfully start / run or execute the script to the code to run in the WDALab trajectory model once the changes are approved by the

6.1.13 The contractor shall develop and implement a methodology in the WDALab trajectory model that will incorporate photogrammetric methods of recording, measuring, and interpreting photographic images into the terrain model and GUI once the changes are approved by the COR.

6.1.14 The contractor shall update, compile, and process by forward engineering the survey to terrain model and GUI in the source code into a standalone form that enables the code to successfully start / run or execute the script to the code to run in the WDALab once the changes are approved by the COR.

6.1.15 The contractor shall update, compile, and process by forward engineering the object to terrain model and GUI in the source code into a standalone form that enables the code to successfully start / run or execute the script to the code to run in the WDALab once the changes are approved by the COR.

6.1.16 The contractor shall forward engineer irregular grid, regular grid, triangulation, and digital terrain into the terrain model once the changes are approved by the COR.

6.1.17 The contractor shall provide a standard method to update and implement error logging that captures exceptions and errors to code running in the WDALab application once the changes are approved by the

6.1.18 The contractor shall update and maintain the exception handler library that is used to process a raised exception or specific errors within WDALab once the changes are approved by the COR.

6.1.19 The contractor shall provide subject matter expertise to develop and upgrade the models and GUIs within the WDALab once the changes are approved by the COR.

6.2 DATA FILE INPUT. The Contractor shall provide management, update and validation of the data files used to initially populate WDALab with data provided by and approved by the COR at a minimum quarterly.

6.2.1 The contractor shall provide technical knowledge of, and validate, and update input files for the impact data associated with USA and United Kingdom ammunition.

6.2.2 The contractor shall provide technical knowledge of, and validate, and update input files for the post impact data associated with USA and United Kingdom ammunition.

6.3 DATA FILES OUTPUT. The Contractor shall provide management, update and validation of the output data files used in the RMTK PSDZ tool and the United Kingdom GIS visualization tool with data provided by and approved by the COR at a minimum quarterly.

6.3.1 The contractor shall provide technical knowledge of and validate, update the USA surface roughness file.

6.3.2 The contractor shall provide technical knowledge of and validate, update the United Kingdom GIS visualization tool.

6.3.3 The contractor shall provide technical knowledge of and validate, update the output files to run with the USA RMTK PSDZ tool.

6.4 WDALab DOCUMENTATION. The Contractor shall provide support, analysis, and expertise for the development of documentation that provides long term capture of WDALab requirements not limited to includes the following. These tasks shall be updated continually as the WDALab is modified and updated for all data, data files input and output.

6.4.1 The contractor shall update and maintain the User Requirements Document once the document data and format are approved by the COR.

6.4.2 The contractor shall update and maintain the Software Requirements Document once the document data and format are approved by the COR.

6.4.3 The contractor shall develop an Architectural Design Document once the document data and format are approved by the COR.

6.4.4 The contractor shall develop a Detailed Design Document once the changes are approved by the

6.4.5 The contractor shall develop a Mathematical Models Document once the document data and format are approved by the COR.

6.4.6 The contractor shall document, consolidate, and disseminate errors in the WDALab code.

6.4.7 The contractor shall update and maintain ARSP 2 VOLUME I with methodology changes as provided by the COR.

6.4.8 The contractor shall update and maintain ARSP 2 VOLUME II with methodology changes as provided by the COR.

7. INFORMATION TECHNOLOGY (IT) REQUIREMENTS.

7.1 The Government agrees to provide NGEN seat and MCEN connectivity as needed in support of requirements.

There is no requirement to connect the Contractor computers to the MCEN.

7.2 It is expected that the contractors IT support of the various required software programs, ESRI and all RMTK extensions, to include the RMTK suite of tools and model development requires computers with system specifications that exceed Government network specifications. The contactor may use laptop computers in the field and in the office to create products to use in their analysis and for briefings. Additionally, while in remote areas, the contractor shall be responsible for providing the necessary air cards and the associated internet connectivity to provide products and analysis efficiently.

7.3 The COR will provide existing code via DOD Safe upon award to the Contractor. DOD safe will also be utilized to transfer data developed under this PWS.

7.4 The COR will facilitate access to NATO and US CAC enabled web sites.

7.5 The data developed under this PWS will be stored on contractor premises and provided to the COR with DOD safe.

8. PHYSICAL AND INFORMATION SECURITY.

8.1 CLEARANCE: Privacy and Security Non-Disclosure Statements shall be required for all employees working on this contract.

8.1.1 PHYSICAL access to the host installation(s) in support of this contract will abide by all base access requirements and HSPD-12 investigative requirements.

8.1.2 Facility Security Officers (FSOs) are responsible for notifying the COR and servicing Personnel Security

Office (PERSEC Office) if any contractor performing on this contract receives an unfavorable adjudication after being issued a CAC. The FSO must also immediately notify the servicing PERSEC Office of any adverse/derogatory information associated with the 13 Adjudicative Guidelines concerning any contractor issued a

CAC, regardless of whether a JPAS / DISS Incident Report is submitted. If a contractor loses their eligibility for a

CAC due to an adverse adjudicative decision, they have also lost their eligibility to perform on this contract. The issued CAC MUST be retrieved immediately from the individual along with any local access identification / cards.

8.2 INSTALLATION AND FACILITIES: There are no special requirements for Installation or facility access.

8.3 TRAVEL REQUIREMENTS: Travel in the performance of this effort shall be requested in writing to the COR within twenty (20) business days prior to performance and must be approved by the COR prior to the performance of said travel. Travel authorized in direct support of the requirements identified within the task order shall be conducted in accordance with the Federal Acquisition Regulations (FAR), including FAR Part 31.205-46, and consistent with the limits in the Joint Travel Regulations (JTRs). Also, Contractor shall provide receipts to the

COR for single items that total $75.00 or more when submitting invoices (i.e., air fare, car rental, parking etc.).

Unauthorized travel or travel not coordinated with the COR shall not be reimbursed. Finally, the Contractor shall notify the Contracting Officer and COR when 75% of obligated travel funds has been reached.

Government requested travel in support of the PWS requirements below are in support of the PWS paragraph identified. Travel will be to the following CONUS and OCONUS locations, but will not include In Theater (i.e., Iraq, Afghanistan etc.):

Location # trips total all

PWS

para

# pers

Duration

(days)

PWS paragraph

Bristol, GBR 3 3 7 6

Fort Eustis, VA 3 3 7 6

Picatinny, NJ 3 3 7 6

9. DELIVERABLES. No deliverable shall be provided to the Marine Corps with corporate markings

(corporate logos, slogans, branding). All deliverables provided to the Marine Corps will allow the Marine Corps to use Marine Corps assets/applications to access/modify/edit the deliverables.

PWS

PARA

Deliverable Format Requirement Delivery

Monthly status report

MS Word Document via email

The contractor shall deliver a monthly status report that details monthly significant events to the Contracting

Officer’s Representative (COR).

Due to COR monthly

Kickoff Face to Face Quantico

VA

The Contractor shall submit a proposed agenda at least five business days prior to the kickoff meeting to the COR. The purpose of this kickoff meeting is to:

• Introduce key Government and

Contractor personnel

• Review PWS requirements, schedule (to include travel) and deliverables to ensure understanding between all parties

• Provide answers to Contractor questions

• Establish preliminary dates for future program events, Due to COR

NLT 15

working days after start of period of performance.

10. ACCESS TO PROPRIETARY DATA OR COMPUTER SOFTWARE.

10.1 Performance under this contract may require that the Contractor have access to technical data, computer software, or other sensitive data of another party (including an affiliated party) who asserts that such data or software is proprietary. Therefore, the Contractor must comply with DFARS 252.227-7025 when appropriate.

PWS

PARA

Deliverable Format Requirement Delivery

• Discuss any other item the COR may deem appropriate to discuss.

• Obtain Non-Disclosure

Agreements from ALL

Contractor Personnel (including

Sub-Contractors working on this effort)

In addition, administrative items, such as invoicing, communication mechanisms, access to Government systems, etc. will be addressed

6.1 WDALab Executable programs The contractor shall deliver the

WDALab executable to the COR.

Due to COR

Yearly

6.4.1 User

Requirement s Document

MS Word Document via email

The contractor shall deliver the document to the COR.

Due to COR

Yearly

6.4.2 Software

Requirement s Document

MS Word Document via email

The contractor shall deliver the document to the COR.

Due to COR

Yearly

6.4.3 Architectural

Design

Document

MS Word Document via email

The contractor shall deliver the document to the COR.

Due to COR

Yearly

6.4.4 Detailed

Design

Document

MS Word Document via email

The contractor shall deliver the document to the COR.

Due to COR

Yearly

6.4.5 Mathematic

al Models

Document

MS Word Document via email

The contractor shall deliver the document to the COR.

Due to COR

Yearly

6.4.6 Error

Document

MS Word Document via email

The contractor shall deliver the document to the COR.

Due to COR

Yearly

6.4.7 ARSP 2 Vol

I update

MS Word Document via email

The contractor shall deliver the document to the COR.

Due to COR

Yearly

6.4.8 ARSP 2 Vol

II update

MS Word Document via email

The contractor shall deliver the document to the COR.

Due to COR

Yearly

10.2 If access to such data or software is required and needs to be provided, the Contractor shall enter into a written agreement (NDA) with such party prior to gaining access to such data or software. The agreement shall address, at a minimum, (1) access to, and use of, the proprietary data or software exclusively for the purposes of performance of the work required by this contract, and (2) safeguards to protect such data or software from unauthorized use or disclosure for so long as the data or software remains proprietary. In addition, the agreement shall not impose any limitation upon the Government or its employees with respect to such data or software. A copy of the executed agreement shall be provided to the Contracting Officer prior to the start of any work under this effort. The

Government may unilaterally modify the contract to list those third parties with which the Contractor has agreement(s).

10.3 The Contractor agrees to: (1) indoctrinate its personnel who will have access to the data as to the restrictions under which access is granted; (2) not disclose the data to another party or other Contractor personnel except as authorized by the above-described NDA and the Contracting Officer; (3) not engage in any other action, venture, or employment wherein this information will be used, other than under this contract, in any manner inconsistent with the spirit and intent of this requirement; (4) not disclose the data to any other party, including, but not limited to, joint venture, affiliate, successor, or assign of the Contractor; and (5) reproduce any restrictive stamp, marking, or legend on each use of the data whether in whole or in part.

10.4 The restrictions on use and disclosure of the data and software described above also apply to such information received from the Government through any means to which the Contractor has access in the performance of this contract that contains proprietary or other restrictive markings.

10.5 The Contractor agrees that it will promptly notify the Contracting Officer of any attempt by an individual, company, or Government representative not directly involved in the effort to be performed under this contract to gain access to such proprietary information. Such notification shall include the name and organization of the individual, company, or Government representative seeking access to such information.

10.6 The Contractor shall include this requirement in subcontracts of any tier which involve access to information covered by paragraph (a), substituting "subcontractor" for "Contractor" where appropriate.

10.7 Compliance with this requirement is a material requirement of this contract.

11. SUMMARIZATION OF DATA RIGHTS.

11.1 Data, Software, and Intellectual Property Rights. In accordance with the DFARS data rights clauses associated with this effort, without limitation, all reports, materials (including, but not limited to, all models, methodologies/methods, and associated upgrades; all WDALab and other effort-associated documentation;

analyses/evaluations and analyses/evaluation criteria; computer software/applications and hardware, source code, interfaces, tools, works, and other related items) data, information, and all electronic/digital files and other items described herein, and any other items, (hereinafter referred to individually or collectively as the Work or Works) that are first created, generated, or produced and required to be delivered under, or as a result of, this PWS shall be provided to the U.S. Government/Marine Corps with the level of intellectual property/data rights provided by such

DFARS data rights clauses.

11.2 Using the format described by DFARS 252.227-7017, the Contractor will provide the COR with a data rights assertion listing for all deliverables including both non-commercial and commercial technical data and computer software. Furthermore, the contractor shall not use the contractor’s or a third-party’s proprietary data, information, software, items and/or other materials for any purpose without meeting the requirements of DFARS clauses

252.227-7020 and/or 252.227-7025, and without the specific, written approval by the Contracting Officer, prior to start of any work.

11.3 Except as provided in writing by the Contracting Officer, no Work, information, material and/or other item created, generated, produced, and required to be delivered under, or as a result of, this PWS/effort shall be used by the Contractor or any of its employees/agents, subcontractors and/or representatives, for any purpose other than for the support and performance of this PWS. Still further, the Contractor is obligated to protect from unauthorized use or disclosure all Government confidential or classified material and/or Government-owned proprietary, and/or

Personally Identifiable Information or Personal Privacy Items obtained in the course of performance under the

Government contract, as long as such data remains proprietary, confidential, sensitive, or classified.

12. TRANSITION-IN AND TRANSITION-OUT PLAN.

12.1 The Contractor shall provide the services necessary to ensure a successful transition of services for the same or similar requirement. Throughout the transition -in period & transition-out periods, it is essential that attention be given to minimize interruptions or delays to work in progress that would impact the mission. The contractor must plan for the transfer of work control, delineating the method for processing and assigning tasks during the transition-in/transition-out periods. The contractor shall follow the transition plan submitted and approved by the Government and shall keep the Government fully informed of status throughout the transition periods. The contractor under a current contract is ultimately responsible for ensuring that all work is performed/accomplished during the transition-in/transition-out periods.

12.2 Following contract award, there will be a 15-day transition-in period. The purpose of this transition-in period is to ensure a smooth transition of services from the predecessor contract to the current contract.

12.3 Contract transition-out period shall commence 30 days prior to the end of the contract. The purpose of the transition-out period is to ensure a smooth transition of services from the predecessor contract to the new contract.

13. DEVELOPMENT DETAILS.

13.1 Data shall be sufficient, competent, and relevant to support Contractor's findings and consistent with fact.

Third-Party or Contractor Proprietary, or commercial applications shall not be used unless previously approved in writing by the Contracting Officer Representative (COR).

14. DATA RIGHTS.

14.1 While the Contractor will be developing software based upon a commercial license (references the use of

ArcGIS and Fortran). The Government considers the updates and developments as non-commercial software, subject only to the software publisher’s license restrictions for software developed exclusively at private expense (if applicable).

14.2 At the end of the period of performance the Contractor shall delete all data from internal servers and networks.

The Contractor shall report positive deletion of all data to the COR with email and within the last monthly status report.

14.3 This contract is subject to DFARS 252.204-7000. The Government does not consider any information developed as part of a deliverable (including software code) as falling within the exceptions set forth in (a)(2) or

(a)(3) of DFARS 252.204-7000 without the express written permission of the contracting officer.

15. DEFINITIONS.

15.1 Terrain Model. The terrain model provides a representation of the surface of the ground over which firing takes place including height and implicitly the slopes of the ground, surface type e.g., turf, sand, concrete, surface roughness, Terrain data is converted to local Cartesian coordinates for trajectory calculations.

15.2 Irregular grid. A data structure that partitions geographic space into contiguous, nonoverlapping triangles. The vertices of each triangle are sample data points with x-, y-, and z-values.

15.3 Digital terrain data. A continuous model of ground-level land surface, represented by a digital raster grid with each grid cell holding an elevation value.

15.4 Regular grid. Is a tessellation of Euclidean space by congruent parallelotopes. Also, an arrangement of shapes closely fitted together, especially of polygons in a repeated pattern without gaps or overlapping of two- or three-dimensional space.

15.5 Triangulation. A data structure that partitions geographic space into contiguous, nonoverlapping triangles. The vertices of each triangle are sample data points with x-, y- and z-values.

15.6 Forward Engineering is a feature that allows you to transform a logical data model into a physical data model by generating the database schema. The generated schema is then used to create a new database or alter an existing one.

15.7 A User Requirements Document is a document used in software engineering that specifies what the user expects the software to be able to do.

15.8 A Software Requirements Document is a document that lays out functional and non-functional requirements, and it may include a set of use cases that describe user interactions that the software must provide to the user for perfect interaction.

15.9 An Architectural Design Document is a document to see how the software is structured. It helps you understand the software’s modules and components without digging into the code.

15.10 A Detailed Design Document is a document of the software product’s design, describing its overall architecture. Such design documents are usually written by software designers or project managers and are given to the software development team to give them an overview of what needs to be built and how.

15.11 A mathematical models Document is a document that outlines the mathematical models and is a description of the system in how it uses the mathematical concepts and language.

16. Quality Assurance.

16.1 The Government shall monitor Contractor performance in accordance with the Quality Assurance Surveillance

Plan (QASP).

16.2 Performance Requirement Summary (PRS). Performance of a service will be evaluated to determine whether or not it meets the performance standard. Inspections may be performed by the COR, or any tenant of the facilities designated by the COR. Re-performance/correction of action is the preferred method of correcting any unacceptable services. If an unacceptable service is annotated on a Contract Discrepancy Report (DA Form 5479-R) the contractor shall provide the Government written response stating why the performance standard was not met, how the performance will be returned to acceptable levels, and how recurrence of the cause will be prevented in the future.

Performance Requirements Summary

Service/Task PWS

Paragraph

Standard Acceptable

Quality

Level

Surveillance

Method

Incentive

Staffing: Includes selection of qualified staff to meet requirements

5 Staff stability maintained at 90% of target WBS allocation;

New hires within 30-days of notification of vacancy; and

100%

<30-days

-Assessment by the COR

Consequence of

Non-compliance

- Negative

CPARs entry

Backfill for unscheduled staff departures.

The WDALab shall be complete, accurate, modified, updated, and maintained with data provided by the COR;

6.1

Contractor modifies, updates and maintains the WDALab at a minimum quarterly.

>95% Error free

-Verification by the COR

Consequence of

Non-compliance

-Correction & resubmit within

10 business day

- Negative

CPARs entry

The WDALab data files input shall be complete, accurate, and prepared to a professional standard;

6.2 Contractor provides

management, updates, and validation of input data files used to populate WDALab at a minimum quarterly.

>95% Error free

-Verification by the COR

Consequence of

Non-compliance

-Correction & resubmit within

10 business day

- Negative

CPARs entry

The WDALab data files output shall be complete, accurate, and prepared to a professional standard;

6.3

Contractor provides management, updates, and validation of output data files used to populate WDALab at a minimum quarterly.

-Verification by the COR

Consequence of

Non-compliance

-Correction & resubmit within

10 business day

- Negative

CPARs entry

The WDALab documentation shall capture, update, maintain, and modify the WDALab requirements;

6.4

Contractor develops, updates, and maintains documentation related to WDALab continually as the

WDALab is modified, and updated.

-Verification by the COR

Consequence of

Non-compliance

-Correction & resubmit within

10 business day

- Negative

Meetings

Electronic form using

MS Office applications with additional hard copies as requested.

Due no later than the 5 days following each meeting

> 95%

Error free agendas, presentation materials, and minutes

-Assessment by the COR

Consequence of

Non-compliance

- Negative

INSPECTION AND ACCEPTANCE TERMS

Supplies/services will be inspected/accepted at:

CLIN INSPECT AT INSPECT BY ACCEPT AT ACCEPT BY

0001 Destination Government Destination Government

0002 Destination Government Destination Government

0003 Destination Government Destination Government

0004 Destination Government Destination Government

0005 Destination Government Destination Government

1001 Destination Government Destination Government

1002 Destination Government Destination Government

1003 Destination Government Destination Government

1004 Destination Government Destination Government

1005 Destination Government Destination Government

2001 Destination Government Destination Government

2002 Destination Government Destination Government

2003 Destination Government Destination Government

2004 Destination Government Destination Government

2005 Destination Government Destination Government

3001 Destination Government Destination Government

3002 Destination Government Destination Government

3003 Destination Government Destination Government

3004 Destination Government Destination Government

3005 Destination Government Destination Government

4001 Destination Government Destination Government

4002 Destination Government Destination Government

4003 Destination Government Destination Government

4004 Destination Government Destination Government

4005 Destination Government Destination Government

DELIVERY INFORMATION

CLIN DELIVERY DATE QUANTITY SHIP TO ADDRESS DODAAC /

CAGE

0001 POP 18-SEP-2023 TO

17-SEP-2024

N/A N/A

0002 17-SEP-2024 4 N/A

0003 17-SEP-2024 4 N/A

0004 POP 18-SEP-2023 TO

0005 POP 18-SEP-2023 TO

1001 POP 18-SEP-2024 TO

17-SEP-2025

1002 17-SEP-2025 4 N/A

1003 17-SEP-2025 4 N/A

1004 POP 18-SEP-2024 TO

1005 POP 18-SEP-2024 TO

2001 POP 18-SEP-2025 TO

17-SEP-2026

2002 17-SEP-2026 4 N/A

2003 17-SEP-2026 4 N/A

2004 POP 18-SEP-2025 TO

2005 POP 18-SEP-2025 TO

3001 POP 18-SEP-2026 TO

17-SEP-2027

3002 17-SEP-2027 4 N/A

3003 17-SEP-2027 4 N/A

3004 POP 18-SEP-2026 TO

3005 POP 18-SEP-2026 TO

4001 POP 18-SEP-2027 TO

17-SEP-2028

4002 17-SEP-2028 4 N/A

4003 17-SEP-2028 4 N/A

4004 POP 18-SEP-2027 TO

4005 POP 18-SEP-2027 TO

CLAUSES INCORPORATED BY REFERENCE

52.202-1 Definitions JUN 2020

52.203-3 Gratuities APR 1984

52.203-6 Alt I Restrictions On Subcontractor Sales To The Government

(JUN 2020) -- Alternate I

NOV 2021

52.203-11 Certification And Disclosure Regarding Payments To

Influence Certain Federal Transactions

SEP 2007

52.203-12 Limitation On Payments To Influence Certain Federal

Transactions

JUN 2020

52.204-7 System for Award Management OCT 2018

52.204-9 Personal Identity Verification of Contractor Personnel JAN 2011

52.204-13 System for Award Management Maintenance OCT 2018

52.204-16 Commercial and Government Entity Code Reporting AUG 2020

52.204-17 Ownership or Control of Offeror AUG 2020

52.204-18 Commercial and Government Entity Code Maintenance AUG 2020

52.204-19 Incorporation by Reference of Representations and

Certifications.

DEC 2014

52.204-20 Predecessor of Offeror AUG 2020

52.204-22 Alternative Line Item Proposal JAN 2017

52.209-7 Information Regarding Responsibility Matters OCT 2018

52.209-12 Certification Regarding Tax Matters OCT 2020

52.212-1 Instructions to Offerors--Commercial Products and

Commercial Services

MAR 2023

52.212-2 Evaluation - Commercial Items NOV 2021

52.212-4 Contract Terms and Conditions--Commercial Products and

Commercial Services

DEC 2022

52.217-5 Evaluation Of Options JUL 1990

52.219-1 Small Business Program Representations MAR 2023

52.222-22 Previous Contracts And Compliance Reports FEB 1999

52.222-25 Affirmative Action Compliance APR 1984

52.232-1 Payments APR 1984

52.232-39 Unenforceability of Unauthorized Obligations JUN 2013

52.232-40 Providing Accelerated Payments to Small Business

Subcontractors

MAR 2023

52.233-4 Applicable Law for Breach of Contract Claim OCT 2004

52.237-2 Protection Of Government Buildings, Equipment, And

Vegetation

APR 1984

52.237-3 Continuity Of Services JAN 1991

52.245-1 Government Property SEP 2021

52.245-9 Use And Charges APR 2012

52.246-5 Inspection Of Services Cost-Reimbursement APR 1984

252.203-7000 Requirements Relating to Compensation of Former DoD

Officials

SEP 2011

252.203-7001 Prohibition On Persons Convicted of Fraud or Other Defense-

Contract-Related Felonies

JAN 2023

252.203-7002 Requirement to Inform Employees of Whistleblower Rights DEC 2022

252.203-7003 Agency Office of the Inspector General AUG 2019

252.203-7005 Representation Relating to Compensation of Former DoD

Officials

SEP 2022

252.204-7000 Disclosure Of Information OCT 2016

252.204-7003 Control Of Government Personnel Work Product APR 1992

252.204-7004 Antiterrorism Awareness Training for Contractors JAN 2023

252.204-7008 Compliance With Safeguarding Covered Defense Information

Controls

OCT 2016

252.204-7009 Limitations on the Use or Disclosure of Third-Party

Contractor Reported Cyber Incident Information

JAN 2023

252.204-7012 Safeguarding Covered Defense Information and Cyber

Incident Reporting

JAN 2023

252.204-7015 Notice of Authorized Disclosure of Information for Litigation

Support

JAN 2023

252.204-7016 Covered Defense Telecommunications Equipment or Services

-- Representation

DEC 2019

252.204-7017 Prohibition on the Acquisition of Covered Defense

Telecommunications Equipment or Services -- Representation

MAY 2021

252.204-7018 Prohibition on the Acquisition of Covered Defense

Telecommunications Equipment or Services

JAN 2023

252.204-7019 Notice of NIST SP 800-171 DoD Assessment Requirements MAR 2022

252.204-7020 NIST SP 800-171 DoD Assessment Requirements JAN 2023

252.204-7023 Reporting Requirements for Contracted Services. JUL 2021

252.205-7000 Provision Of Information To Cooperative Agreement Holders DEC 1991

252.209-7004 Subcontracting With Firms That Are Owned or Controlled By

The Government of a Country that is a State Sponsor of

Terrorism

MAY 2019

252.215-7008 Only One Offer DEC 2022

252.219-7011 Notification to Delay Performance JUN 1998

252.223-7006 Prohibition On Storage, Treatment, and Disposal of Toxic or

Hazardous Materials

SEP 2014

252.223-7999 (Dev) Ensuring Adequate COVID-19 Safety Protocols for Federal

Contractors (Deviation 2021-O0009)

OCT 2021

252.225-7001 Buy American And Balance Of Payments Program--Basic JAN 2023

252.225-7002 Qualifying Country Sources As Subcontractors MAR 2022

252.225-7012 Preference For Certain Domestic Commodities APR 2022

252.225-7048 Export-Controlled Items JUN 2013

252.227-7014 Rights in Other Than Commercial Computer Software and

Other Than Commercial Computer Software Documentation

MAR 2023

252.227-7015 Technical Data--Commercial Products and Commercial

Services

MAR 2023

252.227-7020 Rights In Special Works JUN 1995

252.227-7022 Government Rights (Unlimited) MAR 1979

252.227-7025 Limitations on the Use or Disclosure of Government-

Furnished Information Marked with Restrictive Legends

JAN 2023

252.232-7003 Electronic Submission of Payment Requests and Receiving

Reports

DEC 2018

252.227-7027 Deferred Ordering Of Technical Data Or Computer Software APR 1988

252.227-7028 Technical Data or Computer Software Previously Delivered to the Government

JUN 1995

252.232-7010 Levies on Contract Payments DEC 2006

252.237-7010 Prohibition on Interrogation of Detainees by Contractor

Personnel

JAN 2023

252.243-7001 Pricing Of Contract Modifications DEC 1991

252.243-7002 Requests for Equitable Adjustment DEC 2022

252.244-7000 Subcontracts for Commercial Products or Commercial

Services

JAN 2023

CLAUSES INCORPORATED BY FULL TEXT

52.204-24 REPRESENTATION REGARDING CERTAIN TELECOMMUNICATIONS AND VIDEO

SURVEILLANCE SERVICES OR EQUIPMENT (NOV 2021)

The Offeror shall not complete the representation at paragraph (d)(1) of this provision if the Offeror has represented that it "does not provide covered telecommunications equipment or services as a part of its offered products or services to the Government in the performance of any contract, subcontract, or other contractual instrument" in paragraph (c)(1) in the provision at 52.204-26, Covered Telecommunications Equipment or Services--

Representation, or in paragraph (v)(2)(i) of the provision at 52.212-3, Offeror Representations and Certifications-

Commercial Products and Commercial Services. The Offeror shall not complete the representation in paragraph

(d)(2) of this provision if the Offeror has represented that it "does not use covered telecommunications equipment or services, or any equipment, system, or service that uses covered telecommunications equipment or services" in paragraph (c)(2) of the provision at 52.204-26, or in paragraph (v)(2)(ii) of the provision at 52.212-3.

(a) Definitions. As used in this provision-

Backhaul, covered telecommunications equipment or services, critical technology, interconnection arrangements, reasonable inquiry, roaming, and substantial or essential component have the meanings provided in the clause

52.204-25, Prohibition on Contracting for Certain Telecommunications and Video Surveillance Services or

Equipment.

(b) Prohibition.

(1) Section 889(a)(1)(A) of the John…