SW1031M_CABLE_FIBER_LOCATION-Amendment_2.pdf

OMES FORM CP011 (11/2024) AMENDMENT OF SOLICITATION | Page 1 of 5

Central Purchasing

AMENDMENT OF SOLICITATION

GENERAL INFORMATION

Date of issuance 08/21/2026

Solicitation/Event #

EV00000948

Requisition # 0900020735

Amendment #

Hour and date specified for receipt of offers is changed:

No Yes, to this date: and this time: CST

Pursuant to OAC 260:115-7-30(d), this document shall serve as official notice of amendment to the solicitation identified above. Such notice is being provided to all suppliers to which the original solicitation was sent.

Suppliers submitting bids or quotations shall acknowledge receipt of this solicitation amendment prior to the hour and date specified in the solicitation by doing one of the following:

1. Sign and return a copy of this amendment with the solicitation response being submitted.

2. If the supplier has already submitted a response, this acknowledgement must be signed and returned before the solicitation deadline. All amendment acknowledgements submitted separately shall have the solicitation number and bid opening date printed clearly in the subject line of the email.

Return to:

Contracting officer Nicholas Linder

Phone 405-522-6606

Email nicholas.linder@omes.ok.gov

DESCRIPTION OF AMENDMENT

a. This is to incorporate the following:

On behalf of the State of Oklahoma, OMES gives notice of:

The following questions concerning this solicitation, received during the Q&A period, which closed on 08/04/2026. All questions and procurement/agency responses are detailed as follows:

1. Scope of the proposed solution Reference: Attachment A, Section I, Purpose Attachment A describes a complete solution that includes underground locating hardware, high accuracy positioning hardware, software, mapping tools, and support services. May a bidder propose a software, mapping, integration, and support platform that is compatible with locating and GNSS equipment from multiple manufacturers, or must every bidder directly provide all locating and positioning hardware as part of its proposed offering?

A: OMES has no hardware to offer (Telco/Banks does it currently) each vendor would supply their own. Every bidder must directly provide all locating and positioning hardware as part of its offering.

2. Multiple-supplier award structure Reference: Attachment A, Section I, Purpose The State indicates that it intends to award contracts to multiple suppliers. Does the State anticipate awarding suppliers that provide complementary portions of the requested solution, or must each awarded supplier independently provide a complete end-to-end hardware and software package?

A: Each bidder must supply their own end-to-end package.

3. Hardware manufacturer or reseller authorization Reference: Exhibit 1, Questions 6 through 10 When a bidder proposes compatibility with third-party locating or GNSS equipment, must the bidder be an authorized manufacturer, distributor, or reseller of every referenced device, or may the bidder identify compatible equipment that agencies can procure separately or through another awarded supplier?

A: The solicitation does not prescribe authorization-status requirements. Bidders should disclose their authorization or reseller status and may identify compatible equipment that agencies can procure separately or through other awarded suppliers subject to contract terms.

4. Existing State equipment inventory Reference: Exhibit 1, Question 9

OMES FORM CP011 (11/2024) AMENDMENT OF SOLICITATION | Page 2 of 5

Please identify the manufacturers and models of locating equipment, GNSS receivers, mobile devices, and related field equipment currently used by State telecommunications field teams.

A: OMES has no known hardware and a centralized inventory list is not available for this procurement.

5. Number of users and teams Reference: Exhibit 1, Questions 17, 21, and 22 Please provide the estimated number of field technicians, locate crews, supervisors, administrators, GIS personnel, and participating agencies expected to use the solution during the initial contract term.

A: User counts will vary by agency and by release under this statewide contract. Bidders should propose scalable licensing models that support small and large teams.

6. Expected statewide deployment model Reference: Attachment A, Section I, Purpose Will OMES initially deploy the solution for a defined central telecommunications team, or should bidders anticipate separate deployments and orders from multiple State agencies and affiliates throughout the contract term?

A: Bidders should anticipate separate deployments and orders from multiple State agencies and affiliates.

7. Estimated purchasing quantities Reference: Exhibit 2, Pricing Can the State provide estimated initial or annual quantities for software licenses, locating devices, GNSS receivers, RTK subscriptions, training sessions, implementation services, and support services?

A: State (OMES) does not have this equipment/software. Estimated quantities are not available. They will be defined per Statement of Work (SOW) at the release level. Tiered or bracket pricing is recommended.

8. Mandatory minimum offering Reference: Attachment A, Sections 3.2 and 3.5; Exhibit 2, Pricing Is there a minimum required combination of products and services that must be included in the bidder’s base offering, or may bidders separately price software, implementation, hardware, correction services, integrations, training, and value-added services?

A: No minimum bundle is required. Bidders may separately price all components.

9. OKIE811 platform and interface Reference: Exhibit 1, Question 4 Please identify the ticket management platform currently used for OKIE811 workflows relevant to this procurement and describe the available integration methods, such as API, web service, automated file exchange, email, or manual export.

A: Vendor calls OKIE811 in present state. Suppliers currently manage OKIE811 interactions within their own systems; the State does not operate a centralized ticket platform for these workflows.

10. OKIE811 integration responsibility Reference: Exhibit 1, Question 4 Is direct integration with OKIE811 required at contract award, or may the selected supplier configure and validate the final ticket-management integration during implementation after receiving authorized access, interface documentation, and State workflow requirements?

A: Vendor tracks, or has OKIE track, in their ticket system.

11. Required OKIE811 workflow functions Reference: Exhibit 1, Question 4 Which OKIE811 functions are required within the proposed solution: ticket receipt, map boundary display, assignment, status management, positive response, sketch creation, attachment management, ticket closeout, reporting, or historical record retention?

A: All functions may be required. Functionality requirements will be detailed at the release level post contract award. Please provide pricing accordingly and indicate any tiered or structured pricing packages.

12. Custom forms and data dictionaries Reference: Exhibit 1, Questions 11, 13, and 18

OMES FORM CP011 (11/2024) AMENDMENT OF SOLICITATION | Page 3 of 5

Does the State have existing field forms, telecommunications asset schemas, data dictionaries, required attributes, symbology standards, or reporting templates that bidders should configure or reproduce? If so, please provide representative examples and the estimated number of forms or workflows.

A: No statewide standards or templates are available. Agency specific requirements will be provided at the release level.

13. Existing GIS platform Reference: Exhibit 1, Question 12 Please identify the State GIS platforms, versions, deployment models, and primary systems of record with which the solution may be required to exchange data, including whether ArcGIS Online, ArcGIS Enterprise, ArcGIS Pro, or another platform is currently used.

A: ArcGIS Pro is used within the State. Additional platforms may exist at agency level and will be defined per release.

14. Required GIS integration method Reference: Exhibit 1, Questions 12 and 14 Does the State require real-time bidirectional integration with its GIS and enterprise systems, or will approved import, export, web-service, or scheduled data-exchange workflows satisfy the requirement?

A: Scheduled data exchanges will work best.

15. Required API endpoints Reference: Exhibit 1, Question 14 Please identify the enterprise IT systems expected to exchange information with the proposed solution and the preferred API, authentication, file-transfer, or geospatial-service standards for each system.

A: Target systems and standards will be identified during SOW development. Bidders should support common APIs and authentication protocols.

16. Required accuracy thresholds Reference: Exhibit 1, Question 2 Does the State have minimum required horizontal and vertical accuracy thresholds for mapped asset locations? If so, please identify the thresholds, confidence level, collection method, and conditions under which compliance will be evaluated.

A: Unknown, Currently Telco advises where it is and where it needs to go. Bidders should state achievable accuracy, confidence levels, collection methods, and evaluation conditions.

17. Meaning of vertical accuracy Reference: Exhibit 1, Questions 2 and 13 For purposes of this solicitation, does “vertical accuracy” refer to GNSS-derived elevation, electromagnetic locator depth estimates, verified depth of cover, surveyed utility elevation, or a combination of these measurements?

A combination. Vertical accuracy may include GNSS elevation, locator depth estimates, verified depth of cover, surveyed utility elevation, or a combination. Details will be defined per SOW.

18. Preferred RTK service Reference: Exhibit 1, Question 10 Does the State currently use or prefer a particular RTK correction network or service? If so, please identify the provider, coverage expectations, account structure, supported correction formats, and whether correction-service costs should be included in the proposed pricing.

A: No known preference.

19. Operations without cellular connectivity Reference: Exhibit 1, Questions 10 and 15 Must the proposed positioning solution maintain high-accuracy corrections in locations without cellular or Wi-Fi connectivity? If so, please identify the expected alternative correction method and required duration of disconnected operation.

A: High accuracy is preferred. Bidders should describe alternative correction methods and expected durations without connectivity.

20. AI requirement Reference: Exhibit 1, Question 5 Are AI or machine-learning capabilities required for responsiveness, or will a solution that provides automation, configurable quality controls, metadata capture, reporting, and human reviewed decision support satisfy this requirement?

A: Not required.

OMES FORM CP011 (11/2024) AMENDMENT OF SOLICITATION | Page 4 of 5

21. Security standards and documentation Reference: Exhibit 1, Questions 16, 19, and 20; Attachment D Please identify the specific State cybersecurity standards, security questionnaires, audit reports, penetration-test documentation, cloud-hosting requirements, data-residency requirements, and security certifications that must be provided with the bid rather than during implementation.

A: Because this is a statewide contract, detailed security artifacts (e.g., questionnaires, audits, penetration-test documentation, hosting and residency certifications) are usually collected during implementation at the release/SOW level once integrations and environments are defined. Bidders should summarize security capabilities in the bid; specific documents may be requested post-award.

22. State data residency and offshore access Reference: Attachment D, Section 5 Must all State data be hosted, backed up, administered, and supported exclusively within the United States, and are there any additional geographic restrictions on cloud regions, support personnel, or subcontractors?

A: Data-residency requirements will be defined by ordering agencies per release. Bidders should state available hosting regions;

agency-specific restrictions will be applied during release.

23. Accessibility requirement Reference: Attachment D, Section 3 Which accessibility standard and VPAT version must bidders submit, and must the VPAT cover the mobile application, cloud/browser application, or both?

A: The most current VPAT template can be accessed here https://www.itic.org/policy/accessibility/vpat. Our standard is WCAG 2.1.

The VPAT covers the cloud/browser application not the mobile application. We don't have standards for mobile applications but you can find guidelines here Mobile Accessibility at W3C.

24. Single sign-on and identity provider Reference: Exhibit 1, Question 17 Does the State require single sign-on or multifactor authentication? If so, please identify the State-approved identity provider, authentication protocol, and user-provisioning requirements.

A: Requirements depend on each ordering agency’s environment. Bidders should confirm support for SSO/MFA and standard protocols; exact configurations are set per release.

25. Backup and disaster-recovery targets Reference: Exhibit 1, Question 19 Does the State have required recovery-time objectives, recovery-point objectives, backup retention periods, uptime commitments, data-restoration testing requirements, or geographic redundancy requirements?

A: These targets vary by agency and will be defined per release. Bidders should describe standard disaster-recovery options and service levels.

26. Implementation deadline Reference: Exhibit 1, Question 21 Does the State have a required implementation, pilot, or production go-live date? If not, should bidders propose a timeline based on stated assumptions regarding user count, hardware quantity, integrations, security review, and training?

A: This solicitation establishes a statewide contract, not a singular project. Individual agencies will issue SOWs for releases based on specific needs. Because work is ordered as needed, there is no single implementation timeline; schedules are defined per release.

27. Training quantities and locations Reference: Exhibit 1, Question 22 Please identify the estimated number of trainees, user roles, training locations, required class sizes, and whether travel-related expenses should be included in the firm fixed pricing.

A: Training quantities and logistics vary by agency and will be defined per release. Bidders should provide training offerings and rate structures.

28. Pricing treatment of third-party products Reference: Exhibit 2, Pricing When third-party hardware, RTK correction services, or integration services are included, should bidders provide firm fixed pricing for named products, percentage discounts from published pricing, not-to-exceed pricing, or separate hourly rates?

OMES FORM CP011 (11/2024) AMENDMENT OF SOLICITATION | Page 5 of 5

A: Provide pricing as follows:

• Third-party hardware/software: firm fixed pricing by manufacturer SKU with referenced price lists; include tiered or volume discounts.

• RTK services: percentage discounts from published pricing or firm fixed annual rates; include coverage and service tiers.

• Integration/professional services: hourly rates by role with not-to-exceed ceilings per SOW, or fixed-fee pricing for well-defined deliverables.

• Pass-through costs: list separately with basis of estimate; no cost-plus markups.

• Price adjustments: permitted in accordance with contract terms (e.g., manufacturer price list updates, CPI adjustments) with State approval.

All pricing must be transparent and auditable for statewide ordering.

29. Demonstrations or proof of concept Reference: Attachment A, Section 3.1 Will the evaluation include product demonstrations, oral presentations, field trials, proof-of concept activities, or requests for sample data and deliverables? If so, please describe the anticipated evaluation process and criteria.

A: If included in the evaluation plan, the State may request product demonstrations, oral presentations, field trials, proof-of-concept activities, or sample data/deliverables. Details will be provided to bidders if applicable.

b. All other terms and conditions remain unchanged.

SIGNATURES

Supplier company name

Date

Authorized representative name

Authorized representative signature