SOW.Synopsis.docx

FY25.SOW.RTLP LoS Statement of Work RangeSight Engineering Software U.S. Army Corps of Engineers (USACE), Engineering and Support Center, Huntsville

29 Aug 2025

1. Objective The U.S. Army U.S. Army Corps of Engineers (USACE) has a requirement to procure RangeSight Engineering Software in support of Range Training Land Program (RTLP).

2. Background RTLP serves as the Mandatory Center of Expertise (MCX) for USACE, supporting military agencies in the design of live-fire training ranges across the enterprise. As the RTLP MCX, it ensures design compliance through technical reviews, review meeting participation, and construction inspections to maintain interface integrity and standardization.

A critical aspect of range design is Line of Sight (LOS) engineering. This requirement covers the procurement and renewal of LOS software, along with ongoing support for RTLP engineers using these tools.

3. Description RangeSight is a Commercial Off-The-Shelf (COTS) software used by civil engineers in designs, to analyze, and validate LOS for live-fire training ranges. It is a key component for civil engineers for design validation by integrating with tools from Bentley (DGN) and Autodesk (DWG), ensuring seamless compatibility across platforms.

Running as an ArcGIS Pro add-in (v3.2.0 with 3D Analyst extension), RangeSight batch-processes tens of thousands of LOS calculations, comparing them against training table criteria. This ensures compliance with LOS requirements and helps deliver optimized range designs that maximize training value and cost efficiency.

RangeSight is compatible with both Bently MicroStation, OpenRoads Designer CONNECT Edition, and Autodesk AutoCAD Civil 3D (DWG) files.

3.1. RangeSight Functions:

· Operates successfully with / without Bentley OpenRoads Designer and/or Autodesk Civil 3D installed on the user’s PC.

· Accepts Bentley OpenRoads Designer CONNECT Edition and Autodesk Civil 3D terrains/surfaces and geometry data.

· Transfers line-of-sight (LoS) failure locations to Bentley OpenRoads Designer and Autodesk Civil 3D for revisions.

· Accepts customized parameters for evaluating pass/failure of LoS (e.g., angle of fire, vertical offset from firing points, target points, and terrain features).

· Provides view shed analysis showing visible downrange areas from each firing line, with customizable firing positions, vertical offsets for firing and target positions.

· Provides a beaten zone analysis to identify impact areas beyond targets and support design features like roads, drainage structures, etc.

· Captures and reports the angle of fire at each target, including max, min, mean, and standard deviation, and provides a pass/fail determination based on user-defined values.

3.2. LoS Evaluation/Validation

· Evaluates and validates completed/in-progress range designs, including:

· Line of sight from single/multiple firing points to single/multiple targets.

· Moving and stationary firing and target positions.

· Produces single or multiple graphic LoS profiles with existing design layers and labels.

· Provides numerical profiles and formatted reports (Availability, Utilization, Target Catalogs).

· Displays LoS areas in a planimetric graphic.

· Provides current version of software used by the contractor in the design and LoS validation of at least two U.S. Army Mounted Maneuver type ranges, requiring only minor upgrades.

3.3. Technical Considerations

· Application/Software must be preapproved for USACE systems.

· Must be capable of analyzing/validating LOS designs, including maneuver targets.

· Fully compatible with the latest versions of Bentley Systems (MicroStation, OpenRoads Designer CONNECT Edition) and Autodesk (Civil 3D) products, as mentioned above is Section (3.1).

· Technical Support Contractor shall deliver technical support as necessary to ensure users are able to utilize the LoS software as stated above. In the event software is not working for the user as it should, contractor shall ensure trouble shooting and/or errors in the software are corrected.

4. Requirement

4.1. RangeSight Software

The Contractor shall deliver and support Line of Sight (LoS) engineering software for up to five (5) end-users. The software shall meet the following requirements:

4.1.1. Software Delivery

· Provide LoS software with full compatibility for integration with Bentley (DGN) and Autodesk (DWG) platforms.

· Provide user manual(s)/guide(s) for:

· Installation procedures

· Operational use

· Integration with Bentley and Autodesk tools

· Ensure software operates on Microsoft Windows 10 or later, and on commercial off-the-shelf (COTS) PCs, without proprietary hardware requirements.

· Notify the Government of any additional software/hardware prerequisites necessary for full functionality.

4.1.2. Software Access

· Provide unlimited access for CEHNC users.

· Supply necessary license keys/access codes, including a point(s) of contact for distribution and activation.

4.1.3. Updates/Operability

· Deliver timely updates, patches, and bug fixes throughout the delivery period to maintain software operability.

· Provide Help Desk/Technical Support services, including:

· End-user troubleshooting

· Software fixes

· Functional support

4.2. Training and End-user Support

4.2.1. RangeSight Training

· Deliver up to two (2) days of annual in-person training (8 hours/day) for up to ten (10) students.

· Training shall take place onsite at a Government facility (reference Section 5.2).

4.2.2. Autodesk Civil 3D Training

· Deliver up to three (3) days of annual in-person training (8 hours/day) for up to ten (10) students.

· Training shall take place onsite at a Government facility (reference Section 5.2).

· Focused on Autodesk Civil 3D in conjunction with LoS software. Instruction shall include:

· Contractor shall deliver comprehensive training on Autodesk Civil3D software, focusing on range-specific civil design applications (i.e.: stationary and moving targetry, firing/battle positions, facades, mass and strategic grading areas, etc.) and associated grading technique and alignments / coordinate points with the goal of interaction with the LOS software and production of construction drawing submissions.

4.2.3. Remote End-User Support and Training

Upcoming changes in Bentley products, there is an increased reliance on Autodesk tools. Contractor shall provide up to 100 hours of remote/virtual training and technical support. This includes:

· Comprehensive instruction on LoS software use in conjunction with Autodesk Civil applications

· On-demand end-user support and guidance for civil engineers transitioning from Bentley-based workflows

4.3. Materials

Items to be delivered are defined below in Table (1).

Table 1

Base Period

Optional Training

Option Year (1)

Optional Training

Option Year (2)

Optional Training

Option Year (3)

Optional Training

4.4. Responsibilities

4.4.1. The Government (RTLP) shall be responsible for the following:

· Coordinating with the Contractor at least 30 calendar days in advance of any scheduled training events.

· Limiting each training course to a maximum of 10 students.

· Ensuring students have access to all necessary equipment and software required to participate in training. Ensuring students are present, prepared, and ready to begin at the start of the first training day.

4.4.2. The Contractor shall be responsible for the following:

· Delivering off-the-shelf virtual or in-person training as outlined in Section 4.2 of this SOW.

· Coordinating training start dates and times in collaboration with RTLP.

· Providing all required training materials (e.g., PDFs, zip files) to the Government in advance, allowing time for distribution and installation/printing prior to training.

· Ensuring all instructors are qualified and proficient in:

· Autodesk software

· 3D Civil Design applications

· Line of Sight (LoS) engineering software and integration

5. Delivery Training dates are to be determined as stated above in Section (4) “Requirement”, However training must be scheduled and complete within the 1-year period in which they were awarded.

5.1. Delivery Period

RangeSight Software shall be valid and functional, for a period of no less than 365days/12-months. Per fully executed period. Table (2) below defines the delivery periods:

Table 2

5.2. Delivery Location(s)

5.2.1. Onsite Training shall occur as the location provided below:

USACE, Engineering and Support, Huntsville Center 300 Secured Gateway SW Redstone Arsenal, AL 35898

**Any anticipated travel shall be included in vendor quote as part of training cost**.

5.2.2. Additional End User Support shall be delivered:

· Remotely/Virtually. As needed.

· Contractor/Engineer shall coordinate times/as needed for assistance.

5.2.3. LoS Software shall be delivered electronically/remotely as follows:

· Delivery Shall occur On/before 5 business days from date of award (DOA)

· Electronic Delivery shall include the following:

USACE, Engineering and Support, Huntsville Center PO Box 1600 Circle Huntsville, AL 35807-4301

6. Administrative Requirements

6.1. Point(s) of Contact (POC)

Project Manager (PM),Contracting Officer (KO), Technical and RTLP/MCX

6.2. Communication

Communication pertaining to delivery of software and/or training shall be coordinated through the RTLP and Technical POC(s) identified above in section 6.1. Communication pertaining to terms and conditions of contract, scope determination and or contractor concerns shall go to the KO identified above in section 6.1 (POCs)

6.3. Security

Contractor shall verify all deliverables, to include training materials, are free of computer viruses.

6.4. Travel

N/A

6.5. Safety

Best practices shall be utilized during on-site training. Vendor shall adhere to guidelines provided by safety postings in the facility, and/or and directions provided by government personnel.

7. Invoicing Contractor shall provide invoices upon delivery and confirmation of licenses in accordance with FAR 32.905(b). Invoices submitted to the mailboxes/POC’s identified below NLT 14 Working days after Contract award and/or execution of option period. The delivery period or each invoice shall be submitted for each 12-Month period. Meaning 1 invoice for each 1-year delivery period. Contract should result in a total of 5 invoices (Base Year, Option(s) 1 -4), for this effort (unless for some unforeseen reason contract is modified, at which time additional invoices may be appropriate).

7.1. Invoice Submission

Invoices shall be submitted to the email addressed identified below. Upon confirmation deliverables have been received/accepted. Invoices will be processed.

7.2. Invoice Mailboxes/POC’s

Contractor shall submit invoices via email to the following locations for processing: **Invoices not submitted to the below E-Mail addresses will be rejected.

**Submissions via Wide Area Workflow (WAWF) will not be received and/or processed**

7.3. Content of Invoice

Invoice shall be submitted on official letterhead in Adobe’s Portable Document Format (PDF) and shall include the following information at a minimum. Invoices submitted with incorrect information and/or missing required content will be rejected within 5 working days to vendor for corrections.

· Contractor Name **Must be full/complete company name associated with UIC in Sam.Gov, to include any acronyms (LLC, Inc., Corp.,).

· Address of the contractor (Note: Differences between the remittance address on the invoice and the data on record in the System for Award Management (SAM) can potentially cause delays in payment. Please verify these data agree exactly.)

· Invoice date and number **Invoice must be dated on/or after the 1st date of POP, not date awarded**

· Entire contract number, contract line item (CLIN) number, the order number and modification number as applicable.

· Description, quantity, unit of measure, unit price and extended price of the item delivered. Item description must match those contained in the purchase order/contract description.

· Delivery tracking information to include tracking number and name of the person accepting delivery.

· In cases where there is no physical delivery, please include all email correspondence to the electronic delivery POC (the customer) when the product becomes available for download or is renewed in accordance with the statement of work. Read receipts may help substantiate electronic delivery.

· Name and address of official to whom payment will be sent.

· Invoices for final payment must be so identified and submitted within 60 days from task completion and no further charges are to be billed. A copy of the written acceptance of task completion must be attached to final invoices.

7.4. Final Invoice

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

7.5. Release of Claims

N/A Not Required for Supply/Commodity contract.

NOTE: Project Manager is responsible for acceptance/rejection of invoices and will annotate the Government’s official “received” date. Received date is used on occasions where interest must be calculated for late payment. Deficient invoice submissions will be rejected, in writing from the Project Manager with purpose of rejection.