Draft PWS - SPP Edited - B.08 SOW - Line of Sight Software Support Contract.pdf

STATEMENT OF WORK

LINE OF SIGHT

SOFTWARE SUPPORT

U.S. ARMY CORPS OF ENGINEERS

ENGINEERING AND SUPPORT CENTER,

HUNTSVILLE, ALABAMA

5 JUNE 2024

1. OBJECTIVE: The Contractor shall provide and support a software tool used to design and analyze/validate the Line of Sight (LoS) on Live Fire Training ranges including technical training and support. The Contractor shall provide Line of Sight analysis/validation expertise to the U.S. Army Corps of Engineers, Engineering and Support Center on Live Fire Ranges. All software used to support this contract must be preapproved for use on U.S. Army Corps of Engineers Information Technology systems and be compatible with terrain/surface and geometry data originated using either Bentley OpenRoads Designer CONNECT Edition or Autodesk Civil 3D engineering software.

2. PERIOD OF PERFORMANCE:

Base Year: 12 months 30 Sep 2024 - 29 Sep 2025 Option Year 1: 12 months 30 Sep 2025 - 29 Sep 2026

Option Year 2: 12 months 30 Sep 2026 - 29 Sep 2027 Option Year 3: 12 months 30 Sep 2027 - 29 Sep 2028 Option Year 4: 12 Months 30 Sep 2028 - 29 Sep 2029

3. SCOPE OF WORK

3.1 TASK 1- Software Tool: The Contractor shall furnish a software tool to be used specifically for designing, analyzing, and validating the LoS of Live Fire Training Ranges. The contractor shall provide a user’s manual detailing proper installation and usage of the software. The U.S .Army Corps of Engineers, Engineering and Support Center, Huntsville (CEHNC) will have unlimited use of this software as a design tool and for evaluating and validating the line-of-sight capability of live fire training ranges. Use will be limited to within CEHNC. The software shall run on Windows 10 operating systems using a commercial-off-the-shelf PC that meets minimum operating specs but requiring no proprietary hardware. Specifically, the contractor shall provide a LoS software update that is compatible with the latest released versions of Bentley OpenRoads Designer CONNECT Edition and Autodesk Civil 3D. The contractor shall supply all updates made to the software to CEHNC during the period of performance. The contractor shall state the necessary hardware and software required on CEHNC’s computers for the software tool to function. The software shall support the following requirements:

3.1.1 Design Tool: The software program shall facilitate the development of training range designs in conjunction with the latest versions of Bentley OpenRoads Designer CONNECT Edition and Autodesk Civil 3D civil design softwares. The software shall include the following key attributes:

• The software shall accept Bentley OpenRoads Designer CONNECT Edition and Autodesk Civil 3D terrains/surfaces and geometry data.

• The software shall have the ability to transfer locations of line-of-sight failures back to Bentley OpenRoads Designer CONNECT Edition and Autodesk Civil 3D, for revision to the data.

• The software shall accept customized parameters to be used in the evaluation of pass/failure of line-of-sight (i.e., angle of fire (up/down and left/right), vertical offset to be used from firing points, target points, and intermediate terrain features).

• The software shall provide a view shed analysis that shows the downrange areas visible from each firing line. In performing this functionality, the software shall allow multiple user-defined firing positions (i.e., foxhole, prone, etc.), user-definable vertical offsets applied to each type of firing position, and user-definable vertical offset applied to target and target area ground surfaces. The purpose of this functionality is to provide the users with possible locations for portable targetry.

• The software shall provide a beaten zone analysis. The intent of this analysis is to understand the impact on areas beyond the targets and use this information in the placement and protection of design features (roads, targets, PC, drainage structures, etc.). In performing this functionality, the software shall allow different, user-definable vertical offset to be applied to each target type (i.e., SIT, SAT, etc.).

• The software shall have the capability to capture and report angle of fire at each target from any and/or all training tables or firing positions analyzed. The report shall be able to include max, min, and mean, and standard deviation for angle of fire at each target.

The report shall also be able to report pass/fail based on user definable values. The intent of this functionality is to use this information in the design of individual target berms.

3.1.2 LoS Evaluation/Validation Tool: The software program shall facilitate the evaluation and validation of completed/in-progress range designs by others. The software shall include the following key attributes:

• The software shall be capable of evaluating line of sight from a single firing point to a single target, a single firing point to multiple target locations and multiple points at each target location, multiple firing locations to single target locations, and multiple firing points to multiple target locations with multiple points at target locations. The software shall be capable of emulating moving firing positions against stationary and moving target locations and stationary firing positions against stationary and moving target locations.

• The software shall be capable of producing a single graphic line of sight profile or specified multiples. These profiles shall include multiple layers of existing and design data with labels.

• The software shall be capable of producing numerical profiles and provide output in formatted reports, both pre-formatted and customizable. The reports shall include but are not limited to;

Availability Report (line of sight from all firing points to target points); Utilization Report (number of time target positions can be seen from differing firing points); Target Catalogs (Firing point and target combinations meeting training requirements).

• The software shall be capable of displaying an area having line of sight in a planimetric graphic display.

3.1.3 The software shall be the current version used by the contractor in the design and LoS validation of at least two (2) Mounted Maneuver type ranges for the U.S. Army. The software shall be the current version used by the contractor and require only minor upgrades.

3.2 TASK 2-Technical Support: The technical support below includes up to 100 hours of technical support for the software tool. Technical Support includes on call assistance provided to HNC staff as requested on the latest version of the software including live fire range line of sight analysis/validation expertise, reviewing the use of the software on specific project data, reviewing results obtained from the program, questions about the functionality of the program and system specific issues and question. Support may also include functional training issues. Contractor will be responsible for tracking and reporting monthly to HNC the Technical Support hours used and available. The monthly report shall include who requested the support and a brief summary of the support provided. The contractor shall coordinate support through the COR and Huntsville Center Technical POC (TPOC).

3.3 TASK 3- Training: The contractor shall provide a one-day training class for up to 10 CEHNC Engineers once the base year software is developed and operational. Training for option years is optional and is based on available funding and need for updated training. Class/classes will be located at a government provided facility in Huntsville, AL.

The fee for base year software development shall be invoiced in total upon receipt and successful installation of the software and receipt of user manual.

Fees for the remaining tasks shall be invoiced as each is executed.

3.4 Travel- Training: Travel costs shall comply with the Federal Travel Regulations and the Government Joint Travel Regulations (JTR) in accordance with FAR 31.205-46. Only actual travel costs are allowed. No profit or other additions are allowed. All necessary travel shall be approved in advance by the COR or Contracting Officer.

4. SCHEDULE: The Schedule is shown in Table 1.

5. CLIN Structure:

Base Year Option 1 Option 2 0001 Software Development 1001 Software Maint. 2001 Software Maint.

0002 Technical Support 1002 Technical Support 2002 Technical Support 0003 Training 1003 Training (Option) 2003 Training (Option) 0004 Travel 1004 Travel (Option) 2004 Travel (Option)

Option 3 Option 4

3001 Software Maint. 4001 Software Maint.

3002 Technical Support 4002 Technical Support

3003 Training (Option) 4003 Training (Option) 3004 Travel (Option) 4004 Travel (Option)

6. DELIVERABLES: The contractor shall submit deliverables in accordance with Table 1 below. Hard copies will be bound loose leaf or A-4 notebook and shall include an electronic format/CD (MicroStation compatible, MS Office, Acrobat, and others as mutually agreed upon). All other deliverables shall be in electronic format (preferably email or CD). Source files, if necessary, should allow users to manipulate files with existing software (Acrobat, MS Office, and/or MicroStation).

Monthly Progress Reports: The Contractor shall provide a monthly progress report to include a concise narrative assessment of the status of each task listed above. The report shall address the work accomplished during the reporting period, the work to be accomplished during the next period, and significant problem areas with recommended solutions. The Contractor shall also include copies of all projects related correspondence, minutes of meetings, and records of verbal (telephone) communications.

Written Records: The Contractor shall provide a written record of all significant conferences, meetings, discussions, verbal directions, telephone conversations, etc. with Government representative(s) relative to this order in which the Contractor and/or a designated representative(s) participates. These records shall be dated and shall identify the contract number and the paragraph references, if applicable, participating personnel, subject discussed, and conclusions reached. Records shall be sent to all parties listed in the distribution list within 1 week of the event.

Table 1

7. SAFETY: All contract employees and any sub-contractors must follow all applicable local, state, and federal safety requirements that apply to the work as described in this Statement of Work.

Deliverables Description Distribution /Due Date

Format

LoS Software & User Manual

SOW Para 2.1

30 days after award for software, 45 days after award for user manual.

All deliverables must be approved by the Gov.

Tech POC within this timeframe.

Electronically (PDF, with bookmarks) of user manual to TPOC, PM and

COR

Progress Reports Meeting/Telecon Minutes

Includes summary of items discussed, agreements reached, action items, attendees, and any other significant information

Monthly and as required Electronically to KO, PM, COR, and TPOC

QC/ Work Plan SOW Para 7.4

14 days after award Electronically to KO, PM, COR, and TPOC

8. OTHER ADMINISTRATIVE REQUIREMENTS:

8.1 Progress Payment: Progress payment estimates will be accepted and processed not more than monthly and should be submitted the first duty day of each month. Do not calculate percentages billed beyond two decimal places for each line item on a payment estimate. Each line item must give a detailed description of the invoiced item, the negotiated amount, the percentage of work completed, and the earnings to date with balance remaining. A signed ‘Release of Claims’ with a visible corporate seal will accompany the final invoice submitted. Interim or progress payments without properly submitted documentation will be rejected and returned for correction.

8.2 Progress Reports: The contractor shall prepare and submit to the COR for approval a progress chart showing the various items included in the work as a percentage of the total fee, the order in which the work will be carried out, and the dates on which the items of work will be started and completed. The contractor shall submit a brief narrative of monthly events, which will include any discussion point, deemed to have a potentially significant impact on project outcome. Significant milestones such as review submittals will be shown.

8.3 Invoice Instructions: Electronic Invoice are required, invoices mailed will be disregarded. Electronic invoice submissions must be created in black and white and in Adobe's Portable Document Format (PDF) and comply with the requirements specified within this contract. Invoices larger than 10 megabytes in size will not be accepted through the e-mail process. The review/acceptance of all supplies and services rendered as described will be approved by the COR/ACOR.

Upon receipt, the COR shall examine the invoice(s) for accuracy. When submitting for final payment, include a signed ‘Release of Claims’ with a visible corporate seal. The format for all invoices shall include but not be limited to the following:

- Name of Contractor and Billing/Payment address **Must Match SAM.GOV**

- Contract Number and Task Order if applicable

- Invoice Number and Date of Invoice (the day emailed for payment)

- Period of Performance (monthly, quarterly, or semi-annual billing only)

- Description; quantity; unit of measure; unit price and extended price of items

- List each CLIN billed with remaining balance

All invoices for this contract action shall be emailed to the following;

Final invoices with respect to a specific contract/delivery order/task order shall be clearly marked “FINAL” and submitted within 45 days after period of performance end date specified in contract. NOTE – In some cases, the first invoice may also be the final invoice.

Payment Processing will begin: (1) after the Government accepts delivery of the supplies and/or services being billed, and (2) receipt of invoice in accordance with these instructions.

NOTE - The Project Manager or Program Manager is responsible for determining the acceptability of the invoice and annotating the Government’s official “received” date. The received date is used on occasions where interest must be calculated for late payment.

Deficient invoice submissions will be rejected.

**NOTE**

INVOICES MUST MATCH ALL AREAS ABOVE.

DEFECTIVE/DEFICIENT INVOICES WILL BE REJECTED.

8.4 Quality Control/Work plan: Within 14 calendar days after award of this task order the contractor shall submit to the Government for approval, a Quality Control/Work plan (QC) Plan. The QC/Work plan shall describe how the contractor will maintain a quality program and will outline all services, reports, plans, and other deliverables required by this contract. The Plan will describe how these activities will be performed and provided in a manner that meets industry, architectural, and engineering, as well as Project Management standards.

Computer media (CDs…etc.) shall be scanned for all known viruses. Deliverables are expected to have no more than ten deficiencies in the draft submissions.

8.5 Privacy Act: The contractor shall adhere to the Privacy Act, Title 5 of the U.S.

Code, Section 552a and applicable agency rules and regulations.

8.6 Clearances: None required to perform the task.

8.7 Personal Services: The Task Manager has determined that this task order is not being used to procure personal services prohibited by the Federal Acquisition Regulation (FAR) Part 37.104 titled "Personal Services Contract".

8.8 Conflict of Interest: The contractor shall ensure that all contractor personnel assigned to work under this effort sign a non-disclosure statement. If there is any doubt as whether furnishing services to the Government on this contract represents a conflict of interest, the contractor shall secure a written decision from the Government’s Contracting Officer on this contract.

8.9 All information/data generated or collected under this task is owned by the

Government. The contractor agrees not to use, release, or publish any data, notes, findings, reports, or any other information generated from this contract in any manner other than as required in order to meet the deliverables requested by the Government under the provisions of this contract, without written prior approval from the Contracting Officer or designated Representative.

8.10 Service Contract Reporting (SCR): Not Applicable.

8.11 Antiterrorism (AT) Requirements: All contractor employees, to include subcontractor employees, requiring access to Army installations, facilities, controlled access areas, or require network access, shall complete AT Level I awareness training within 30 calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable. Upon request, the contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee, to the COR or to the contracting officer (if a COR is not assigned), within 5 calendar days after completion of training by all employees and subcontractor personnel. AT Level I awareness training is available at the following website:

http://jko.jten.mil/courses/atl1/launch.html; or it can be provided by the RA ATO in presentation form which will be documented via memorandum.

8.12 Pre-screen candidates using E-Verify Program: The Contractor must pre-screen

Candidates using the E-verify Program (http://www.uscis.gov/e-verify) website to meet the established employment eligibility requirements. The Vendor must ensure that the Candidate has two valid forms of Government issued identification prior to enrollment to ensure the correct information is entered into the E-verify system.

An initial list of verified/eligible Candidates must be provided to the COR no later than 3 business days after the initial contract award." *When contracts are with individuals, the individuals will be required to complete a Form I-9, Employment Eligibility Verification, with the designated Government representative. This Form will be provided to the Contracting Officer and shall become part of the official contract file.

8.13 Suspicious Activity Reporting Training (e.g. iWATCH, CorpsWatch): The contractor and all associated sub-contractors shall receive a brief/training (provided by the RA) on the local suspicious activity reporting program. This locally developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the project manager, security representative or law enforcement entity. This training shall be completed within 30 calendar days of contract award and within 30 calendar days of new employees commencing performance with the results reported to the COR NLT 5 calendar days after the completion of the training.

9. Points of Contact:

http://jko.jten.mil/courses/atl1/launch.html http://www.uscis.gov/e-verify)