Work Zone Activity Data Publication

740.03(a)__. Work Zone Activity Data Publication. The employee designated under Item 740.03(a)1, or connected field devices deployed at the work site that automatically report status and location, shall record each work zone activity event — the activation, material modification, or removal of a temporary traffic control installation — at the time it occurs. The Contractor shall cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed, or transmitted to the Department's designated system, within 30 minutes of occurrence. Where connectivity is unavailable at the work site, the event shall be recorded contemporaneously and transmitted upon restoration of connectivity, and no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records shall not satisfy this Item.

Each event shall include: route and direction; begin and end coordinates (milepost where available); field-verified actual start and end date-times; vehicle impact and lane-level status where applicable; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the records of the same installation.

The Contractor may comply by any of the following, alone or in combination, as approved by the Engineer: (1) entry into a Department reporting system where field-level access is provided; (2) an approved data source — any device, system, or service — publishing a conforming feed listed in the USDOT WZDx Feed Registry; (3) transmission to a Department WZDx feed by a provided interface; (4) connected field devices publishing a conforming device feed for the elements they report, remainder by (1)–(3). No specific manufacturer, product, or service is required or preferred. Published event records may serve as source records supporting the Department's Form C-25 inspections.

Work under this Item will not be measured for payment; include the cost in the lump sum price for Item 740-A, Traffic Control Scheme, or where no Item 740-A is included, in the unit prices for the Section 740 items.

c. Work Zone Activity Data Publication. The WTS, or connected field devices deployed at the work site that automatically report status and location, shall record each work zone activity event — the activation, material modification, or removal of a temporary traffic control installation — at the time it occurs. The Contractor shall cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed, or transmitted to the Department's designated system, within 30 minutes of occurrence. Where connectivity is unavailable at the work site — including remote segments without coverage — the event shall be recorded contemporaneously and transmitted upon restoration of connectivity, and no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records will not satisfy this subsection.

Each event shall include: route and direction; begin and end coordinates (milepost where available); field-verified actual start and end date-times; vehicle impact and lane-level status where applicable; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the records of the same installation. The twice-daily inspections and Form 25D-104 reports required by 643-1.04.2.b, and the Form 25D-103 daily device counts, remain in effect; the same field records may serve as source records, and published event records containing the required content may serve as those reports for the events they cover, as approved by the Engineer.

The Contractor may comply by any of the following, alone or in combination, as approved by the Engineer: (1) entry into a Department reporting system where field-level access is provided; (2) an approved data source — any device, system, or service — publishing a conforming feed listed in the USDOT WZDx Feed Registry; (3) transmission to a Department WZDx feed by a provided interface; (4) connected field devices publishing a conforming device feed for the elements they report, remainder by (1)–(3). No specific manufacturer, product, or service is required or preferred.

The Engineer may compare published data with observed field conditions, including for the purposes of the Traffic Price Adjustment of 643-3.06; systematic discrepancy constitutes non-conformance. Work under this subsection is subsidiary to Item 643.0001, Traffic Maintenance.

701-3.__ Work Zone Activity Data Publication: The employee designated under Subsection 108.03 to implement and monitor the traffic control plan, or connected field devices deployed at the work site that automatically report status and location, shall record each work zone activity event — the activation, material modification, or removal of a traffic control installation — at the time it occurs. The contractor shall cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed, or transmitted to the Department's designated system, within 30 minutes of occurrence. Where connectivity is unavailable at the work site, the event shall be recorded contemporaneously and transmitted upon restoration of connectivity, and no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records will not satisfy this subsection.

Each event shall include: route and direction; begin and end coordinates (milepost where available); field-verified actual start and end date-times; vehicle impact and lane-level status where applicable; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the records of the same installation. Event records reporting device placement, operating status, and removal may support the measurement of In-Use elements under Subsections 701-4 and 701-6.

The contractor may comply by any of the following, alone or in combination, as approved by the Engineer: (A) entry into a Department reporting system where field-level access is provided; (B) an approved data source — any device, system, or service — publishing a conforming feed listed in the USDOT WZDx Feed Registry; (C) transmission to a Department WZDx feed by a provided interface; (D) connected field devices publishing a conforming device feed for the elements they report, remainder by (A)–(C). No specific manufacturer, product, or service is required or preferred.

The Engineer may compare published data with observed field conditions and the Department's work zone traffic control inspections; systematic discrepancy constitutes non-conformance and grounds for the payment consequences of Subsection 701-4.03. Work under this subsection is not measured for payment; the cost shall be included in the contract prices for the Section 701 elements of work.

Add the following to Subsection 604.03(a): The Contractor shall also record each work zone activity event — the activation, material modification, or removal of a temporary traffic control installation — at the time it occurs, by the traffic control supervisor or other personnel present at the work site or by automatic report of connected field devices deployed at the site, and shall cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed, or transmitted to the Department's designated system, within 30 minutes of occurrence. Where connectivity is unavailable at the work site, the event shall be recorded contemporaneously and transmitted upon restoration of connectivity, and no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records will not satisfy this requirement.

Each event shall include: route and direction; begin and end coordinates (log mile where available); field-verified actual start and end date-times; vehicle impact and lane-level status where applicable; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the records of the same installation. The daily Traffic Control Device Inspection Checklist may serve as the source record, and published event records containing the checklist's content may serve as the daily checklist documentation.

The Contractor may comply by any of the following, alone or in combination, as approved by the Engineer: (1) entry into a Department reporting system where field-level access is provided; (2) an approved data source — any device, system, or service — publishing a conforming feed listed in the USDOT WZDx Feed Registry; (3) transmission to a Department WZDx feed by a provided interface; (4) connected field devices publishing a conforming device feed for the elements they report, with the remainder furnished by (1)–(3). No specific manufacturer, product, or service is required or preferred.

Systematic discrepancy between published data and field conditions constitutes non-conformance with this subsection. This work will not be measured or paid for separately; the cost shall be included in the lump sum prices for Maintenance of Traffic and, where included, Traffic Control Supervisor (Section 603.04).

Replace "Reserved" in section 12-4.02C(5) with:

12-4.02C(5) Work Zone Activity Data Publication

12-4.02C(5)(a) Record each work zone activity event — the activation, material modification, or removal of a traffic control system — at the time it occurs. Use personnel present at the work site or connected field devices deployed at the work site that automatically report status and location. Publish each event, or transmit it to the Department's designated system, as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA) — a Road Event Feed or Smart Work Zone Device Feed — within 30 minutes of occurrence. If connectivity is unavailable at the work site, record the event contemporaneously and transmit it when connectivity is restored, and no later than the end of the work shift. Data derived solely from planned schedules, closure charts, or office records does not comply with this section.

12-4.02C(5)(b) Include for each event: (1) route and direction affected; (2) beginning and ending locations as geographic coordinates, with postmile reference where available; (3) actual start and end date-times flagged as field-verified; (4) vehicle impact and lane-level status where lane-level traffic control is used; (5) worker presence status while workers are within the activity area; (6) reduced regulatory speed limit where imposed; (7) identifiers associating the activation, modification, and removal records of the same traffic control system.

12-4.02C(5)(c) Comply using any of the following, alone or in combination, as authorized by the Engineer: (1) status updates entered under section 12-4.02C(2), where the Department makes the resulting data available as or into a conforming feed; (2) an approved data source — any device, system, or service — publishing the events as, or into, a WZDx feed listed in the USDOT WZDx Feed Registry; (3) transmission to a Department WZDx feed using a Department-provided interface; (4) connected field devices, including automated work zone information systems under section 12-3.35, publishing a conforming device feed for the elements the devices report, with remaining elements furnished by another authorized method. No specific manufacturer, product, or service is required or preferred.

12-4.02C(5)(d) Form CEM-2210, Traffic Control Daily Report, and the status updates required under section 12-4.02C(2) remain required; the same field records may serve as source records for this section. The Engineer may compare published data with field conditions; systematic discrepancy is non-conformance.

12-4.02C(5)(e) Work under section 12-4.02C(5) is not paid for separately; payment is included in the payment for the traffic control system bid items.

In subsection 630.11, add the following duty: (__) Recording each work zone activity event — the activation, material modification, or removal of a traffic control installation, including each MHT setup and takedown — at the time it occurs, and causing each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed, or transmitted to the Department's designated system, within 30 minutes of occurrence. Recording may be performed by the TCS or by automatic report of connected field devices deployed at the work site. Where connectivity is unavailable at the work site, the event shall be recorded contemporaneously and transmitted upon restoration of connectivity, and no later than the end of the work shift. Data derived solely from planned schedules, the approved MHT, or office records does not satisfy this duty.

Each event shall include: route and direction; begin and end coordinates (mile reference where available); field-verified actual start and end date-times, consistent with the setup and takedown times recorded in the daily traffic control diary; vehicle impact and lane-level status where applicable; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the records of the same installation and its MHT number.

The Contractor may comply by any of the following, alone or in combination, as approved by the engineer: (1) entry into a Department reporting system where field-level access is provided, where the Department makes the resulting data available as or into a conforming feed (including the Department's WZDx and CWZ feeds); (2) an approved data source — any device, system, or service — publishing a conforming feed listed in the USDOT WZDx Feed Registry; (3) transmission to a Department feed by a provided interface; (4) connected field devices publishing a conforming device feed for the elements they report, remainder by (1)–(3). No specific manufacturer, product, or service is required or preferred.

The daily traffic control diary of subsection 630.11(5), its 24-hour submittal, and the daily inspections of 630.11(6) remain in effect; the same field records may serve as source records, and published event records containing the enumerated diary content may serve as the diary for the events they cover, as approved. Systematic discrepancy between published data and field conditions constitutes non-conformance. Work under this provision is not measured separately; the cost is included in the prices for Traffic Control Management (per day) or, where applicable, the lump sum traffic control items.

U. Work Zone Activity Data Publication: The Contractor shall record each work zone activity event — the activation, material modification, or removal of a traffic control pattern or temporary traffic control installation — contemporaneously in the field, and shall cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed. On limited access highways, the Traffic Control Supervisor required by 9.71.01 shall be responsible for event recording; elsewhere, recording shall be by personnel present at the work site or by automatic report of connected field devices deployed at the site. Each event shall be published, or transmitted to the Department's designated system, within 30 minutes of occurrence; where connectivity is unavailable, events shall be recorded contemporaneously and transmitted upon restoration, and no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records shall not satisfy this part.

Each event shall include: route and direction; begin and end coordinates (route/milepost reference where available); field-verified actual start and end date-times, including the times traffic control patterns are installed and removed; vehicle impact and lane-level status; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the records of the same installation. The event record of pattern installation and removal times shall be consistent with the lane-closure times recorded by the Department on Form CON-134.

The Contractor may comply by any of the following, alone or in combination, as approved by the Engineer: (1) entry into a Department reporting system where field-level access is provided; (2) an approved data source — any device, system, or service — publishing a conforming feed listed in the USDOT WZDx Feed Registry; (3) transmission to a Department-designated WZDx feed by a provided interface; (4) connected field devices publishing a conforming device feed for the elements they report, with the remainder furnished by (1)–(3). No specific manufacturer, product, or service is required or preferred.

(Amend 9.71.05—Basis of Payment:) The cost of work zone activity data publication shall be included in the contract lump sum price for "Maintenance and Protection of Traffic."

812.3.___ Work Zone Activity Data Publication. A. The traffic control supervisor shall record each work zone activity event — the activation, material modification, or removal of a temporary traffic control installation — at the time it occurs. Recording may also be by automatic report of connected field devices deployed at the work site. The Contractor shall cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed, or transmitted to the Department's designated system, within 30 minutes of occurrence. Where connectivity is unavailable at the work site, record the event contemporaneously and transmit upon restoration of connectivity, and no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records does not satisfy this subsection.

B. Each event shall include: route and direction; begin and end coordinates (milepost where available); field-verified actual start and end date-times; vehicle impact and lane-level status where applicable; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating records of the same installation. The Daily Log required by 812.3.E.b may serve as the source record, and the published events may serve as the Daily Log where they contain the information 812.3.E.b requires.

C. The Contractor may comply by any of the following, alone or in combination, as approved by the engineer: (1) entry into a Department reporting system where field-level access is provided; (2) an approved data source — any device, system, or service — publishing a conforming feed listed in the USDOT WZDx Feed Registry; (3) transmission to a Department WZDx feed by a provided interface; (4) connected field devices publishing a conforming device feed for the elements they report, remainder by (1)–(3). No specific manufacturer, product, or service is required or preferred.

D. (Amend 801.5 / 812.5:) The cost of work zone activity data publication is included in the lump sum price for Maintenance of Traffic (Item 801000), or where Item 812500 is included in the contract, in the hourly price for the certified traffic control supervisor.

Work Zone Activity Data Publication. The Traffic Safety Officer shall record each work zone activity event — the activation, material modification, or removal of a lane closing or temporary traffic control installation — at the time it occurs. Recording may also be by automatic report of connected field devices deployed at the work site. The Contractor shall cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed, or transmitted to the Department's designated system, within 30 minutes of occurrence; where connectivity is unavailable, the event shall be recorded contemporaneously and transmitted upon restoration, and no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records shall not satisfy this provision.

Each event shall include: route and direction; begin and end coordinates; field-verified actual start and end date-times; vehicle impact and lane-level status; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the records of the same installation.

The Contractor may comply by any of the following, alone or in combination, as approved by the Engineer: (1) an approved data source — any device, system, or service — publishing a conforming feed listed in the USDOT WZDx Feed Registry; (2) entry into a Department reporting system where field-level access is provided; (3) transmission to a Department-designated WZDx feed by a provided interface; (4) connected field devices publishing a conforming device feed for the elements they report, with the remainder furnished by (1)–(3). No specific manufacturer, product, or service is required or preferred. A machine-readable log meeting this provision and containing the content required by 612.02(B)(1)(g) may be submitted for approval as the Traffic Control Device Inspection Log.

The cost of work under this provision is included in the lump sum price for CONSTRUCTION LANE CLOSING. (For non-contract work in public space: the same publication requirement may be attached as a condition of Public Space Permits requiring a Traffic Control Plan, through the permit special conditions.)

102-3.__ Work Zone Activity Data Publication: The Worksite Traffic Supervisor, or connected field devices deployed at the work site that automatically report status and location, shall record each work zone activity event — the activation, material modification, or removal of a temporary traffic control installation — at the time it occurs. Cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed, or transmitted to the Department's designated system, within 30 minutes of occurrence. Entries made in the Lane Closure Notification System pursuant to 102-3.3 satisfy this requirement for the lane-closure events they record, where the Department makes the resulting data available as or into a conforming feed. Where connectivity is unavailable at the work site, record the event contemporaneously and transmit upon restoration of connectivity, and no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records does not satisfy this Subarticle.

Include for each event: route and direction; begin and end coordinates (mile marker where available); field-verified actual start and end date-times; vehicle impact and lane-level status where applicable; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the records of the same installation.

Comply using any of the following, alone or in combination, as approved by the Engineer: entry into Department reporting systems (including the LCNS) where field-level access is provided; an approved data source — any device, system, or service — publishing the events as, or into, a WZDx feed listed in the USDOT WZDx Feed Registry; transmission to the Department's WZDx feed by a Department-provided interface; or connected field devices publishing a conforming device feed for the elements the devices report, with remaining elements furnished by another approved method. No specific manufacturer, product, or service is required or preferred.

The WTS inspection duties of 102-3.2 and the MOT Review Report processes remain in effect; the same field records may serve as source records. The Engineer may compare published data with observed field conditions; systematic discrepancy constitutes non-conformance. The work of this Subarticle is not measured for payment; include the cost in the lump sum price for Item 102-1, Maintenance of Traffic.

150.1.__ Work Zone Activity Data Publication

A. The Worksite Traffic Control Supervisor (WTCS) designated under Subsection 150.1.04.A, or connected field devices deployed at the work site that automatically report status and location, shall record each work zone activity event — the activation, material modification, or removal of a temporary traffic control installation — at the time it occurs. The Contractor shall cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed, or transmitted to the Department's designated system, within 30 minutes of occurrence. Where connectivity is unavailable at the work site, the event shall be recorded contemporaneously and transmitted upon restoration of connectivity, and no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records shall not satisfy this Subsection.

B. Each event shall include: route and direction; begin and end coordinates (milepost where available); field-verified actual start and end date-times; vehicle impact and lane-level status where applicable; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the records of the same installation.

C. The Contractor may comply by any of the following, alone or in combination, as accepted by the Engineer: (1) entry into a Department reporting system where field-level access is provided; (2) an approved data source — any device, system, or service — publishing a conforming feed listed in the USDOT WZDx Feed Registry; (3) transmission to a Department WZDx feed by a provided interface; (4) connected field devices publishing a conforming device feed for the elements they report, with the remainder furnished by (1)–(3). No specific manufacturer, product, or service is required or preferred.

D. The Traffic Control Inspection Report (TC-1) requirements of Subsection 150.1.04.A remain in effect; the same field records may serve as source records for this Subsection. The Engineer may compare published data with observed field conditions; systematic discrepancy constitutes non-conformance subject to the adjustments of Subsection 150.7.01. The cost of work under this Subsection is included in the lump sum price for Item 150, Traffic Control.

645.03(__) Work Zone Activity Data Publication. The Contractor shall designate the person responsible for work zone traffic control recording, and that person, or connected field devices deployed at the work site that automatically report status and location, shall record each work zone activity event — the activation, material modification, or removal of a temporary traffic control installation, including each lane closure opening and closing — at the time it occurs. The Contractor shall cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed, or transmitted to the Department's designated system, within 30 minutes of occurrence. Where connectivity is unavailable at the work site, the event shall be recorded contemporaneously and transmitted upon restoration of connectivity, and no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records will not satisfy this subsection.

Each event shall include: route and direction; begin and end coordinates (milepost where available); field-verified actual start and end date-times, including compliance with the lane-closure hour limitations of this Section; vehicle impact and lane-level status where applicable; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the records of the same installation.

The Contractor may comply by any of the following, alone or in combination, as accepted by the Engineer: (1) entry into a Department reporting system where field-level access is provided; (2) an approved data source — any device, system, or service — publishing a conforming feed listed in the USDOT WZDx Feed Registry; (3) transmission to a Department WZDx feed by a provided interface; (4) connected field devices publishing a conforming device feed for the elements they report, remainder by (1)–(3). No specific manufacturer, product, or service is required or preferred.

The Engineer may compare published data with observed field conditions, including the lane-closure time limitations and rental-fee provisions of this Section; systematic discrepancy constitutes non-conformance. 645.05: The Engineer will not measure work zone activity data publication; include the cost in the contract lump sum price for Traffic Control.

Work Zone Activity Data Publication. The traffic control supervisor, or connected field devices deployed at the work site that automatically report status and location, shall record each work zone activity event — the activation, material modification, or removal of a temporary traffic control installation — at the time it occurs. Cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed, or transmitted to the Department's designated system, within 30 minutes of occurrence. Where connectivity is unavailable at the work site, record the event contemporaneously and transmit upon restoration of connectivity, and no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records does not satisfy this requirement.

Include for each event: route and direction; begin and end coordinates (milepost where available); field-verified actual start and end date-times; vehicle impact and lane-level status where applicable; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the records of the same installation.

Comply by any of the following, alone or in combination, as approved by the Engineer: (1) entry into a Department reporting system where field-level access is provided; (2) an approved data source — any device, system, or service — publishing a conforming feed listed in the USDOT WZDx Feed Registry; (3) transmission to a Department WZDx feed by a provided interface; (4) connected field devices publishing a conforming device feed for the elements they report, remainder by (1)–(3). No specific manufacturer, product, or service is required or preferred.

The daily records and weekly reports required by 626.04, and the Department's ITD-1406 inspections, remain in effect; the same field records may serve as source records, and published event records may serve as the required reports for the events they cover. The Engineer may compare published data with observed field conditions; systematic discrepancy constitutes non-conformance. (Add to 626.05:) Work zone activity data publication is not measured for payment; include the cost in the contract prices for the Section 626 items, including Temporary Traffic Control Maintenance.

701.___ Work Zone Activity Data Publication.

(a) The Contractor shall record each work zone activity event — the activation, material modification, or removal of a work zone traffic control installation — contemporaneously in the field, and shall cause each event to be published as machine-readable data according to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed.

(b) Events shall be recorded by personnel present at the work site or reported automatically by connected field devices deployed at the site, and shall be published, or transmitted to the Department's designated system, within 30 minutes of occurrence. When connectivity is unavailable at the work site, events shall be recorded contemporaneously and transmitted upon restoration of connectivity, but no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records will not satisfy this Article.

(c) Each published event shall include: route and direction affected; begin and end locations as geographic coordinates, with station or milepost reference where available; actual start and end date/times flagged as field-verified; vehicle impact and lane-level status where lane-level traffic control is used; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the activation, modification, and removal records of the same installation.

(d) The Contractor may comply by any of the following, alone or in combination, as approved by the Engineer: (1) entering events into the Department's lane closure reporting system where field-level access is provided; (2) an approved data source — any device, system, or service — that publishes the events as, or into, a WZDx feed listed in the USDOT WZDx Feed Registry; (3) transmitting events to a Department WZDx feed according to an interface provided by the Department; or (4) connected field devices publishing a conforming device feed for those elements the devices report, with remaining elements furnished according to (1)–(3). No specific manufacturer, product, or service is required or preferred. Where the work is within Illinois Tollway jurisdiction, the Engineer will designate the receiving feed.

(e) The project traffic control diary required by the contract remains required; the same field records may serve as source records for this Article. The Engineer may compare published data with observed field conditions; systematic discrepancy will constitute non-conformance.

(f) This work will not be paid for separately but shall be considered as included in the cost of TRAFFIC CONTROL AND PROTECTION.

801.___ Work Zone Activity Data Publication.

(a) Each work zone activity event, consisting of the activation, material modification, or removal of a temporary traffic control installation, shall be recorded contemporaneously in the field and published as machine-readable data in accordance with the Work Zone Data Exchange, WZDx, Specification, version 4.2 or later, FHWA, as a Road Event Feed or Smart Work Zone Device Feed.

(b) Events shall be recorded by personnel present at the work site or reported automatically by connected field devices deployed at the site. Each event shall be published, or transmitted to the Department's designated system, within 30 min of occurrence. Where connectivity is unavailable at the work site, events shall be recorded contemporaneously and transmitted upon restoration of connectivity, and no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records will not be accepted.

(c) Each event shall include the route and direction affected; the begin and end locations as geographic coordinates with reference post where available; the actual start and end dates and times, designated as field verified; the vehicle impact and lane status where lane-level traffic control is used; the worker presence status while workers are within the activity area; the reduced regulatory speed limit where imposed; and identifiers associating the records of the same installation.

(d) Compliance may be by one or more of the following, as approved: entry of events into the Department's lane closure reporting system where field-level access is provided; an approved data source, consisting of a device, system, or service, publishing the events as, or into, a WZDx feed listed in the USDOT WZDx Feed Registry; transmission to a Department WZDx feed in accordance with an interface provided by the Department; or connected field devices publishing a conforming device feed for the elements the devices report, with remaining elements furnished by another approved method. No specific manufacturer, product, or service is required or preferred. This provision applies to Department lettings; it does not extend to the Indiana Toll Road concession.

(e) The Traffic Control Device Report and daily device inspection required by 801.03 remain in effect, and the same field records may serve as source records for this provision. The certified worksite traffic supervisor responsible for review of the Traffic Control Device Report under 801.03 shall be responsible for event recording under this provision. Published data may be compared with observed field conditions; systematic discrepancy will constitute non-conformance.

(f) The cost of work under this provision shall be included in the cost of the maintaining traffic pay items of 801.17 and 801.18.

4. Work Zone Activity Data Publication.

a. The Traffic Control Technician maintained under Article 2528.01, C, 1, or connected field devices deployed at the work site that automatically report status and location, shall record each work zone activity event — the activation, material modification, or removal of a traffic control installation, including each Safety Closure placed under Article 2528.03, N — at the time it occurs. Cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed, or transmitted to the Contracting Authority's designated system, within 30 minutes of occurrence. Where connectivity is unavailable at the work site, record the event contemporaneously and transmit upon restoration of connectivity, and no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records does not satisfy this Article.

b. Include for each event: route and direction; begin and end locations as geographic coordinates, with station or milepost reference where available; actual start and end date-times flagged as field-verified; vehicle impact and lane-level status where lane-level traffic control is used; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the activation, modification, and removal records of the same installation.

c. Comply using any of the following, alone or in combination, as approved by the Engineer: 1) entry into a reporting system designated by the Contracting Authority where field-level access is provided, where the resulting data is made available as or into a conforming feed (including the feed generated from 511 construction events); 2) an approved data source — any device, system, or service — publishing the events as, or into, a WZDx feed listed in the USDOT WZDx Feed Registry; 3) transmission to the Contracting Authority's WZDx feed by a provided interface; or 4) connected field devices publishing a conforming device feed for the elements the devices report, with remaining elements furnished by another approved method. No specific manufacturer, product, or service is required or preferred.

d. The project traffic control daily diary of Article 2528.01, C, 2, and the Traffic Control Technician's documentation duty of Article 2528.01, C, 3, remain in effect; the same field records may serve as source records for this Article, and a machine-readable record meeting this Article and containing the content required by Article 2528.01, C, 2, a may be approved by the Engineer as the format provided by the Contracting Authority for the daily diary. The Engineer may compare published data with observed field conditions; systematic discrepancy constitutes non-conformance with the Contractor's traffic quality control program. Per Article 2528.05, A, work under this Article is not measured separately and is included in the lump sum price for Traffic Control as traffic quality control.

805.3___ WORK ZONE ACTIVITY DATA PUBLICATION

a. General. Record each work zone activity event (activation, material modification, or removal of a temporary traffic control installation) contemporaneously in the field and cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed.

b. Recording. Record events by personnel at the work site or by automatic report of connected field devices deployed at the site. Publish each event, or transmit it to KDOT's designated system, within 30 minutes; where connectivity is unavailable, record contemporaneously and transmit on reconnection, no later than end of shift. Data derived solely from planned schedules or office records does not comply.

c. Data elements. Route and direction; begin/end coordinates (mile reference where available); field-verified actual start and end date-times; vehicle impact and lane-level status where applicable; worker presence while workers are in the activity area; reduced speed limit where imposed; identifiers linking records of the same installation.

d. Methods. Comply by any of the following, alone or in combination, as approved by the Engineer: (1) entry into KDOT's lane closure reporting system where field access is provided; (2) an approved data source — any device, system, or service — publishing a conforming feed listed in the USDOT WZDx Feed Registry; (3) transmission to KDOT's feed by a KDOT interface; (4) connected field devices publishing a conforming device feed for the elements they report, remainder by (1)–(3). No manufacturer, product, or service is required or preferred.

e. Records; verification. The traffic control diary and Traffic Control Checklist required by the KDOT Documentation Manual remain required; the same field records may serve as source records for this subsection. The Engineer may compare published data with field conditions; systematic discrepancy is non-conformance.

f. Payment. (Add to 805.4 MEASUREMENT AND PAYMENT:) Work zone activity data publication is not measured for payment and is subsidiary to the Section 805 traffic control pay items.

1.0 The Project Traffic Coordinator designated under Subsection 112.03.12, or connected field devices deployed at the work site that automatically report status and location, shall record each work zone activity event — the activation, material modification, or removal of a temporary traffic control installation — at the time it occurs. The Contractor shall cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed, or transmitted to the Department's designated system, within 30 minutes of occurrence. Where connectivity is unavailable at the work site, the event shall be recorded contemporaneously and transmitted upon restoration of connectivity, and no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records will not satisfy this Note.

2.0 Each event shall include: route and direction; begin and end coordinates (milepoint where available); field-verified actual start and end date-times; vehicle impact and lane-level status where applicable; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the records of the same installation.

3.0 The Contractor may comply by any of the following, alone or in combination, as approved by the Engineer: A) entry into a Cabinet reporting system where field-level access is provided; B) an approved data source — any device, system, or service — publishing a conforming feed listed in the USDOT WZDx Feed Registry; C) transmission to a Cabinet WZDx feed by a provided interface; D) connected field devices publishing a conforming device feed for the elements they report, remainder by A)–C). No specific manufacturer, product, or service is required or preferred.

4.0 The per-shift inspection and incident-reporting duties of Subsection 112.03.12 remain in effect; the same field records may serve as source records for this Note. The Engineer may compare published data with observed field conditions; systematic discrepancy constitutes non-conformance subject to Subsection 112.03.15. The Department will not measure this work for payment; include the cost in the contract lump sum price for Maintain and Control Traffic.

713.3.070.__ Work Zone Activity Data Publication. The TCS shall record each work zone activity event — the activation, material modification, or removal of a temporary traffic control installation — at the time it occurs; recording may also be by automatic report of connected field devices deployed at the work site. Cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed, or transmitted to the Department's designated system, within 30 minutes of occurrence. Where connectivity is unavailable at the work site, record the event contemporaneously and transmit upon restoration of connectivity, and no later than the end of the work shift; the timing allowances of 713.3.070.D for diary entries apply. Data derived solely from planned schedules, permits, or office records does not satisfy this subsection.

Each event shall include: route and direction; begin and end coordinates (logmile reference where available); field-verified actual start and end date-times; vehicle impact and lane-level status where applicable; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the records of the same installation.

The contractor may comply by any of the following, alone or in combination, as approved by the engineer: (1) entries in the traffic control diary maintained in the Department's system under 713.3.070.D, where the Department makes the resulting data available as or into a conforming feed; (2) an approved data source — any device, system, or service — publishing a conforming feed listed in the USDOT WZDx Feed Registry; (3) transmission to a Department WZDx feed by a provided interface; (4) connected field devices publishing a conforming device feed for the elements they report, remainder by (1)–(3). No specific manufacturer, product, or service is required or preferred.

The Traffic Control Diary requirements of 713.3.070.D, the daily inspections of 713.3.070.E, and their associated deductions remain in effect; the same field records may serve as source records for this subsection. Work under this subsection is not measured for payment; the cost is included in Item 713-01.

652.3.__ Work Zone Activity Data Publication. The Traffic Control Supervisor named in the Traffic Control Plan under 652.3.3(a), or connected field devices deployed at the work site that automatically report status and location, shall record each work zone activity event — the activation, material modification, or removal of a temporary traffic control installation — at the time it occurs. The Contractor shall cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed, or transmitted to the Department's designated system, within 30 minutes of occurrence. Where connectivity is unavailable at the work site, the event shall be recorded contemporaneously and transmitted upon restoration of connectivity, and no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records will not satisfy this subsection.

Each event shall include: route and direction; begin and end coordinates (mile reference where available); field-verified actual start and end date-times; vehicle impact and lane-level status where applicable; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the records of the same installation.

The Contractor may comply by any of the following, alone or in combination, as authorized by the Resident: (a) entry into a Department reporting system where field-level access is provided; (b) an approved data source — any device, system, or service — publishing a conforming feed listed in the USDOT WZDx Feed Registry; (c) transmission to a Department WZDx feed by a provided interface; (d) connected field devices publishing a conforming device feed for the elements they report, remainder by (a)–(c). No specific manufacturer, product, or service is required or preferred.

The Resident may compare published data with observed field conditions and with the Project Diary and Inspector's Daily Report records; systematic discrepancy constitutes unacceptable maintenance of traffic control devices for the affected days. Work under this subsection is not measured separately; the cost is included in the price for Pay Item 652.36 or 652.361, Maintenance of Traffic Control Devices.

SECTION 104.__ — WORK ZONE ACTIVITY DATA PUBLICATION

104.__.01 DESCRIPTION. This work consists of recording maintenance-of-traffic activity contemporaneously in the field and causing it to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed.

104.__.03 CONSTRUCTION. (a) The Traffic Manager required by Section 104.18, or connected field devices deployed at the work site that automatically report status and location, shall record each work zone activity event — the activation, material modification, or removal of a maintenance-of-traffic installation — at the time it occurs. (b) Publish each event, or transmit it to the Administration's designated system, within 30 minutes of occurrence; where connectivity is unavailable, record contemporaneously and transmit upon restoration, and no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records does not comply. (c) Include for each event: route and direction; begin and end coordinates (milepoint where available); field-verified actual start and end date-times; vehicle impact and lane-level status where applicable; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the records of the same installation. (d) Comply by any of the following, alone or in combination, as approved by the Engineer: entry into an Administration reporting system where field-level access is provided; an approved data source — any device, system, or service — publishing a conforming feed listed in the USDOT WZDx Feed Registry; transmission to an Administration WZDx feed by a provided interface; or connected field devices publishing a conforming device feed for the elements they report, remainder by the other methods. No specific manufacturer, product, or service is required or preferred. (e) The Traffic Manager's daily inspection log required by 104.18.03(e), and its next-day furnishing to the Engineer, remain in effect; the same field records may serve as source records. The Engineer may compare published data with field conditions, including the TTC Inspection/Rating Report (SHA 52.4-01); systematic discrepancy constitutes non-conformance.

104.__.04 MEASUREMENT AND PAYMENT. Work zone activity data publication will not be measured but will be incidental to the Maintenance of Traffic lump sum item.

850.7___ Work Zone Activity Data Publication. Record each work zone activity event — the activation, material modification, or removal of a temporary traffic control installation — contemporaneously in the field, and cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed. Record events using personnel present at the work site or connected devices meeting Subsection 856 deployed at the work site. Publish each event, or transmit it to the Department's designated system (including the Work Zone Manager application), within 30 minutes of occurrence; where connectivity is unavailable, record contemporaneously and transmit upon restoration, and no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records does not satisfy this Subsection.

Include for each event: route and direction; begin and end coordinates (mile marker reference where available); actual start and end date-times flagged as field-verified; vehicle impact and lane-level status where lane-level traffic control is used; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating records of the same installation.

Comply using any of the following, alone or in combination, as approved by the Engineer: (a) transmission through the Connected Work Zone Notification System of Subsection 856, where deployed, for the elements those devices report; (b) an approved data source — any device, system, or service — publishing the events as, or into, a WZDx feed listed in the USDOT WZDx Feed Registry; (c) entry into a Department reporting system where field-level access is provided; or (d) a Department-provided feed interface — with any elements not reported by one method furnished by another. No specific manufacturer, product, or service is required or preferred.

The Traffic Management Plan requirements of Subsection 7.10 remain in effect; the same field records may serve as source records. The Engineer may compare published data with observed field conditions; systematic discrepancy constitutes non-conformance. Work under this Subsection is not measured separately; include the cost in the unit prices for the Subsection 850 and 856 items.

a. In addition to the daily inspections and records required by subsection 812.03.D of the Standard Specifications, record each work zone activity event — the activation, material modification, or removal of a temporary traffic control installation within the construction influence area — at the time it occurs. Record events using personnel present at the work site or connected field devices deployed at the work site that automatically report status and location. Cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed, or transmitted to the Department's designated system, within 30 minutes of occurrence. If connectivity is unavailable at the work site, record the event contemporaneously and transmit upon restoration of connectivity, no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records does not meet this requirement.

b. Include for each event: route and direction; begin and end coordinates (mile marker where available); actual start and end date-times identified as field-verified; vehicle impact and lane-level status where applicable; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the records of the same installation.

c. Comply using one or more of the following, as approved by the Engineer: entry into a Department reporting system where field-level access is provided; an approved data source — any device, system, or service — publishing the events as, or into, a WZDx feed listed in the USDOT WZDx Feed Registry; transmission to the Department's WZDx feed using a Department-provided interface; or connected field devices publishing a conforming device feed for the elements the devices report, with remaining elements furnished by another approved method. No specific manufacturer, product, or service is required or preferred.

d. The inspection records of subsection 812.03.D may serve as source records, and published event records containing that content satisfy the recording duty of 812.03.D for the events they cover. The Engineer may compare published data with observed field conditions; systematic discrepancy constitutes non-conformance. Do not measure this work separately; include the cost in the unit prices for the section 812 pay items, including the lump sum items Minor Traf Devices and Traf Regulator Control.

S-___ (2563) WORK ZONE ACTIVITY DATA PUBLICATION

A. General. Record each work zone activity event — the activation, material modification, or removal of a temporary traffic control (TTC) installation — contemporaneously in the field, and cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later, as published by the Federal Highway Administration. A WZDx feed includes a WZDx Road Event Feed or a WZDx Smart Work Zone Device Feed.

B. Recording and timeliness. Record each event at the time it occurs, by personnel present at the work site or by automatic report of connected field devices (arrow boards, portable changeable message signs, truck-mounted attenuators, traffic sensors, or other TTC devices equipped to report status and location) deployed at the work site. Publish each event, or transmit it to the Department's designated system, within 30 minutes of occurrence. Where connectivity is unavailable at the site, record the event contemporaneously and transmit upon restoration of connectivity, and no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records does not satisfy this provision.

C. Data elements. Include for each event: (1) route and direction affected; (2) begin and end locations as geographic coordinates, with mile reference where available; (3) actual start date-time and, on removal, actual end date-time, flagged field-verified; (4) vehicle impact and lane-level status where lane-level TTC is used; (5) worker presence status while workers are within the activity area; (6) reduced regulatory speed limit where imposed; (7) identifiers associating the activation, modification, and removal records of the same installation.

D. Methods. Satisfy this provision by any of the following, alone or in combination, as approved by the Engineer: (1) entry of events into the Department's lane closure reporting system where the Department provides field-level access; (2) an approved data source — any device, system, or service — publishing the events as, or into, a WZDx feed listed in the USDOT WZDx Feed Registry; (3) transmission to the Department's WZDx feed by a Department-provided interface; or (4) connected field devices publishing a conforming device feed for those elements the devices report, with remaining elements furnished under (1)–(3). No specific manufacturer, product, or service is required or preferred.

E. Relationship to existing records; verification. The daily traffic-control device inspection and discrepancy/action log otherwise required remain in effect; the same field records may serve as source records for this provision. Where the Contract includes a Traffic Control Supervisor under S-206 (2563), the Traffic Control Supervisor is responsible for event recording under this provision. The Engineer may compare published data with observed field conditions; systematic discrepancy constitutes non-conformance.

F. Payment. Work under this provision is not measured separately and is included in the lump sum payment under Item 2563.601 (Traffic Control).

After Subsection 618.01.2, add the following:

618.01.__--Work Zone Activity Data Publication. The Traffic Control Supervisor (or Traffic Control Technician under the TCS's direction), or connected field devices deployed at the work site that automatically report status and location, shall record each work zone activity event — the activation, material modification, or removal of a temporary traffic control installation — at the time it occurs. The Contractor shall cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed, or transmitted to the Department's designated system, within 30 minutes of occurrence. Where connectivity is unavailable at the work site, the event shall be recorded contemporaneously and transmitted upon restoration of connectivity, and no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records will not satisfy this subsection.

Each event shall include: route and direction; begin and end coordinates (milepost where available); field-verified actual start and end date-times; vehicle impact and lane-level status where applicable; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the records of the same installation.

The Contractor may comply by any of the following, alone or in combination, as approved by the Engineer: (a) entry into a Department reporting system where field-level access is provided; (b) an approved data source — any device, system, or service — publishing a conforming feed listed in the USDOT WZDx Feed Registry; (c) transmission to a Department WZDx feed by a provided interface; (d) connected field devices publishing a conforming device feed for the elements they report, remainder by (a)–(c). No specific manufacturer, product, or service is required or preferred.

The inspection and Form CSD-762 documentation requirements of Subsection 618.01.2, as amended, remain in effect; the same field records may serve as source records for this subsection. The Engineer may compare published data with observed field conditions; systematic discrepancy constitutes non-conformance. Work under this subsection will not be measured for payment; the cost shall be included in the contract lump sum price for Item 618-A (907-618-A), Maintenance of Traffic.

616.13 Work Zone Activity Data Publication.

616.13.1 This work consists of recording temporary traffic control activity contemporaneously in the field and causing that activity to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a WZDx Road Event Feed or WZDx Smart Work Zone Device Feed.

616.13.2 The contractor shall record each work zone activity event — activation, material modification, or removal of a TTC installation — at the time it occurs. Recording shall be by personnel present at the work site or by automatic report of connected field devices deployed at the work site. Each event shall be published, or transmitted to the Commission's designated system, within 30 minutes of occurrence; where site connectivity is unavailable, events shall be recorded contemporaneously and transmitted upon restoration, and no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records will not satisfy this provision.

616.13.3 Each published event shall include: route and direction affected; begin and end coordinates, with log-mile reference where available; actual field-verified start and end date-times; vehicle impact and lane-level status where lane-level TTC is used; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the records of the same installation.

616.13.4 The contractor may comply by any of the following, alone or in combination, as approved by the engineer: (a) entry of events into MoDOT's designated reporting system where field-level access is provided; (b) an approved data source — any device, system, or service — publishing a conforming feed listed in the USDOT WZDx Feed Registry; (c) transmission to MoDOT's WZDx feed by an interface the Commission provides; or (d) connected field devices publishing a conforming device feed for the elements the devices report, remainder by (a)–(c). No specific manufacturer, product, or service is required or preferred.

616.13.5 The records supporting the Temporary Traffic Control Inspection Worksheet (EPG 616) may serve as source records for this provision. All documentation requirements of Sec 616 and the contract otherwise remain in effect. The engineer may compare published data with field conditions; systematic discrepancy constitutes non-conformance.

616.13.6 No direct payment will be made for work under this provision. It will be considered completely covered by the contract unit prices for Sec 616 pay items.

618.03.__ WORK ZONE ACTIVITY DATA PUBLICATION. A. The personnel designated under Subsection 618.03.4 as responsible for traffic control work, or connected field devices deployed at the work site that automatically report status and location, must record each work zone activity event — the activation, material modification, or removal of a traffic control installation — at the time it occurs. Cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed, or transmitted to the Department's designated system, within 30 minutes of occurrence. Where connectivity is unavailable at the work site, record the event contemporaneously and transmit upon restoration of connectivity, and no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records does not satisfy this subsection.

B. Include for each event: route and direction; begin and end coordinates (reference post where available); field-verified actual start and end date-times; vehicle impact and lane-level status where applicable; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the records of the same installation.

C. Comply by any of the following, alone or in combination, as approved by the Project Manager: 1. entry into a Department reporting system where field-level access is provided; 2. an approved data source — any device, system, or service — publishing a conforming feed listed in the USDOT WZDx Feed Registry; 3. transmission to a Department WZDx feed by a provided interface; 4. connected field devices publishing a conforming device feed for the elements they report, remainder by 1.–3. No specific manufacturer, product, or service is required or preferred.

D. The traffic control review and surveillance duties of Subsection 618.03.4 and the certification submittals of 618.03.2 remain in effect; the same field records may serve as source records. The Project Manager may compare published data with observed field conditions; systematic discrepancy constitutes non-conforming traffic control subject to Subsection 618.04.6. Work under this subsection is not measured for payment and is included in the unit prices for the Section 618 traffic control items.

Work Zone Activity Data Publication.

1. The Contractor shall record each work zone activity event — activation, material modification, or removal of a temporary traffic control installation — contemporaneously in the field and shall cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed.

2. Events shall be recorded by personnel present at the work site or reported automatically by connected field devices deployed at the site, and shall be published, or transmitted to the Department's designated system, within 30 minutes of occurrence. Where connectivity is unavailable, events shall be recorded contemporaneously and transmitted upon restoration, and no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records will not satisfy this provision.

3. Each event shall include: route and direction; begin and end coordinates (reference post where available); field-verified actual start and end date-times; vehicle impact and lane-level status where applicable; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the records of the same installation.

4. The Contractor may comply by any of the following, alone or in combination, as approved by the Engineer: (a) entry into the Department's lane closure reporting system where field-level access is provided; (b) an approved data source — any device, system, or service — publishing a conforming feed listed in the USDOT WZDx Feed Registry; (c) transmission to a Department WZDx feed by a Department interface; (d) connected field devices publishing a conforming device feed for the elements they report, remainder by (a)–(c). No specific manufacturer, product, or service is required or preferred.

5. The detailed daily diary maintained in AWP and the daily verification of in-place traffic control remain required; the same field records may serve as source records for this provision. Where the Contract includes traffic control management or surveillance under Section 419, the personnel performing that work are responsible for event recording under this provision. The Engineer may compare published data with field conditions; systematic discrepancy constitutes non-conformance.

6. (Add to 422.05, Basis of Payment:) Work zone activity data publication is subsidiary to the Section 422 (and, where included, Section 419) items and will not be measured or paid for separately.

624.03.___ Work Zone Activity Data Publication.

(a) General. The Contractor shall record each work zone activity event — activation, material modification, or removal of a temporary traffic control installation — contemporaneously in the field, and shall cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed.

(b) Recording and timeliness. Events shall be recorded by personnel present at the work site or reported automatically by connected field devices deployed at the site. Each event shall be published, or transmitted to the Department's designated system, within 30 minutes of occurrence. Where connectivity is unavailable at the work site — including remote segments — events shall be recorded contemporaneously and transmitted upon restoration of connectivity, and in no case later than the end of the work shift. Data derived solely from planned schedules, permits, or office records shall not satisfy this subsection.

(c) Data elements. Each event shall include: route and direction; begin and end coordinates (milepost reference where available); field-verified actual start and end date-times; vehicle impact and lane-level status where applicable; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating records of the same installation.

(d) Methods. The Contractor may comply by any of the following, alone or in combination, as approved by the Engineer: (1) entry into the Department's lane closure reporting system where field-level access is provided; (2) an approved data source — any device, system, or service — publishing a conforming feed listed in the USDOT WZDx Feed Registry; (3) transmission to a Department WZDx feed by a Department interface; (4) connected field devices publishing a conforming device feed for the elements they report, remainder by (1)–(3). No specific manufacturer, product, or service is required or preferred.

(e) Records; verification. Form 040-056B, Work Zone Traffic Control Checklist, and daily diary/daily work report requirements remain in effect; the same field records may serve as source records. Where the Contract requires a traffic control supervisor under 624.03.06, the supervisor is responsible for event recording under this subsection. The Engineer may compare published data with field conditions; systematic discrepancy constitutes non-conformance.

(f) Payment. (Add to 624.05:) Work zone activity data publication is not measured separately and is included in the contract prices for the Section 624 and Section 625 traffic control items.

3.__ Work Zone Activity Data Publication. The responsible person designated under 618.3.4.3, or connected field devices deployed at the work site that automatically report status and location, shall record each work zone activity event — the activation, material modification, or removal of a temporary traffic control installation, including each implementation of or approved variation from the Traffic Control Plan — at the time it occurs. The Contractor shall cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed, or transmitted to the Department's designated system, within 30 minutes of occurrence. Where connectivity is unavailable at the work site, the event shall be recorded contemporaneously and transmitted upon restoration of connectivity, and no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records will not satisfy this subsection.

3.__.1 Each event shall include: route and direction; begin and end coordinates (mile marker where available); field-verified actual start and end date-times; vehicle impact and lane-level status where applicable; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the records of the same installation.

3.__.2 The Contractor may comply by any of the following, alone or in combination, as approved by the Engineer: entry into a Department reporting system where field-level access is provided; an approved data source — any device, system, or service — publishing a conforming feed listed in the USDOT WZDx Feed Registry; transmission to a Department WZDx feed by a provided interface; or connected field devices publishing a conforming device feed for the elements they report, with the remainder furnished by another approved method. No specific manufacturer, product, or service is required or preferred.

3.__.3 The Contract Administrator's work-zone inspections and daily-report notations remain in effect; the same field records may serve as source records. Systematic discrepancy between published data and field conditions constitutes non-conformance. 5.__ Work under this subsection will not be measured; the cost is included in the Contract lump sum price for Item 619.1, Maintenance of Traffic.

159.03.10 Work Zone Activity Data Publication.

1. Record each work zone activity event — the activation, material modification, or removal of a temporary traffic control installation — contemporaneously in the field, and cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed.

2. Record events using personnel present at the work site or connected field devices deployed at the work site that automatically report status and location. Publish each event, or transmit it to the Department's designated system, within 30 minutes of occurrence. If connectivity is unavailable at the site, record the event contemporaneously and transmit it upon restoration of connectivity, and no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records does not satisfy this subsection.

3. Include for each event: route and direction affected; begin and end locations as geographic coordinates, with milepost reference where available; actual start and end date-times identified as field-verified; vehicle impact and lane-level status where lane-level traffic control is used; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the records of the same installation.

4. Comply using one or more of the following, as approved by the RE: (a) entry of events into the Department's Lane Closure Management System (LCMS) or successor where field-level access is provided; (b) an approved data source — any device, system, or service — publishing the events as, or into, a WZDx feed listed in the USDOT WZDx Feed Registry; (c) transmission to a Department-designated WZDx feed, including a feed operated for the Department by an academic or research partner, using a provided interface; or (d) connected field devices publishing a conforming device feed for the elements the devices report, with remaining elements furnished by another approved method. No specific manufacturer, product, or service is required or preferred.

5. The Daily Work Zone Inspection Report (Form DC-189A) and daily traffic control plan inspection requirements remain in effect; the same field records may serve as source records for this Subpart. The Traffic Control Coordinator required by 159.03.01 shall be responsible for event recording under this Subpart. The RE may compare published data with observed field conditions; systematic discrepancy constitutes non-conformance.

6. The Department will not make separate measurement or payment for work under this subsection; include the cost in the traffic control items.

Add the following Subsection:

618.2.2.__ Work Zone Activity Data Publication. The TCS (or TCT under the TCS's direction), or connected field devices deployed at the work site that automatically report status and location, shall record each work zone activity event — the activation, material modification, or removal of a temporary traffic control installation — at the time it occurs. The Contractor shall cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed, or transmitted to the Department's designated system, within 30 minutes of occurrence. Where connectivity is unavailable at the work site, the event shall be recorded contemporaneously and transmitted upon restoration of connectivity, and no later than the end of the Day. Data derived solely from planned schedules, permits, or office records shall not satisfy this Subsection.

Each event shall include: route and direction; begin and end coordinates (milepost where available); field-verified actual start and end date-times; vehicle impact and lane-level status where applicable; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the records of the same installation. The Traffic Control Diary required by Subsection 618.2.2.1 remains required; the same field records may serve as source records for this Subsection.

The Contractor may comply by any of the following, alone or in combination, as approved by the Project Manager: (1) entry into a Department reporting system where field-level access is provided; (2) an approved data source — any device, system, or service — publishing a conforming feed listed in the USDOT WZDx Feed Registry; (3) transmission to a Department WZDx feed by a provided interface; (4) connected field devices publishing a conforming device feed for the elements they report, remainder by (1)–(3). No specific manufacturer, product, or service is required or preferred.

The Project Manager may compare published data with the Traffic Control Diary and observed field conditions; systematic discrepancy constitutes failure to comply under Subsection 618.3.1. Work under this Subsection is not measured for payment; the cost is included in the Contract price for Traffic Control Management (618.5).

619-3.__ WORK ZONE ACTIVITY DATA PUBLICATION. The work zone traffic control competent person designated under §619-3.01, the Traffic Control Supervisor where required under §619-3.20, or connected field devices deployed at the work site that automatically report status and location, shall record each work zone activity event — the activation, material modification, or removal of a work zone traffic control installation — at the time it occurs. The Contractor shall cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed, or transmitted to the Department's designated system (including the feed published through 511NY), within 30 minutes of occurrence. Where connectivity is unavailable at the site, the event shall be recorded contemporaneously and transmitted upon restoration of connectivity, and no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records shall not satisfy this subsection.

Each event shall include: route and direction; begin and end locations as coordinates (reference marker where available); actual start and end date-times flagged as field-verified; vehicle impact and lane-level status where lane-level control is used; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the records of the same installation.

The Contractor may comply by any of the following, alone or in combination, as approved by the Engineer: entry into a Department reporting system where field-level access is provided; an approved data source — any device, system, or service — publishing the events as, or into, a WZDx feed listed in the USDOT WZDx Feed Registry; transmission to the Department's WZDx feed by a Department-provided interface; or connected field devices publishing a conforming device feed for the elements the devices report, with remaining elements furnished by another approved method. No specific manufacturer, product, or service is required or preferred. The Department's Contract Diary and DWR work zone traffic control records (CAM Section 90, remark 02) remain in effect; the same field records may serve as source records.

619-5.__ Work zone activity data publication will not be measured for payment. Include the cost in the lump sum price for Item 619.01, Basic Work Zone Traffic Control. Systematic discrepancy between published data and field conditions constitutes a deficiency subject to §619-5.01.

Add the following Article to Section 1101:

1101-__ WORK ZONE ACTIVITY DATA PUBLICATION

(A) The qualified work zone supervisor required by Article 1101-13, the work zone installer of Article 1101-14, or connected field devices deployed at the work site that automatically report status and location, shall record each work zone activity event — the activation, material modification, or removal of a temporary traffic control installation — at the time it occurs. Cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed, or transmitted to the Department's designated system, within 30 minutes of occurrence. Where connectivity is unavailable, record the event contemporaneously and transmit upon restoration of connectivity, and no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records does not satisfy this Article.

(B) Include for each event: route and direction; begin and end coordinates (milepost where available); field-verified actual start and end date-times; vehicle impact and lane-level status where applicable; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the records of the same installation.

(C) Comply by any of the following, alone or in combination, as approved by the Engineer: (1) entry into a Department reporting system where field-level access is provided; (2) an approved data source — any device, system, or service — publishing a conforming feed listed in the USDOT WZDx Feed Registry; (3) transmission to the Department's WZDx feed by a Department interface; (4) connected field devices publishing a conforming device feed for the elements they report, remainder by (1)–(3). No specific manufacturer, product, or service is required or preferred.

(D) The daily scheduled inspections of Article 1105-4 remain in effect; the same field records may serve as source records for this Article. The Engineer may compare published data with observed field conditions; systematic discrepancy constitutes non-conformance. Work under this Article will not be paid for separately; the cost is included in the unit prices for the Division 11 pay items.

Add the following to Section 704.04 C.1.b: In addition to the daily inspection documentation required by this section, the traffic control supervisor (or, where no TCS is designated, the watchperson or other personnel present at the work site), or connected field devices deployed at the work site that automatically report status and location, shall record each work zone activity event — the activation, material modification, or removal of a temporary traffic control installation — at the time it occurs. The Contractor shall cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed, or transmitted to the Department's designated system, within 30 minutes of occurrence. Where connectivity is unavailable at the work site, the event shall be recorded contemporaneously and transmitted upon restoration of connectivity, and no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records will not satisfy this requirement.

Each event shall include: route and direction; begin and end coordinates (reference point where available); field-verified actual start and end date-times; vehicle impact and lane-level status where applicable; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the records of the same installation. The daily inspection documents required by this section may serve as source records, and published event records containing that content may serve as the daily inspection documentation for the events they cover.

The Contractor may comply by any of the following, alone or in combination, as approved by the Engineer: (1) entry into a Department reporting system where field-level access is provided; (2) an approved data source — any device, system, or service — publishing a conforming feed listed in the USDOT WZDx Feed Registry; (3) transmission to a Department WZDx feed by a provided interface; (4) connected field devices publishing a conforming device feed for the elements they report, remainder by (1)–(3). No specific manufacturer, product, or service is required or preferred.

The Engineer may compare published data with field conditions and the diary documentation required by the Construction Records Manual; systematic discrepancy constitutes non-conformance. Add to Section 704.06: Work zone activity data publication is not measured for payment; the cost is included in the lump sum price for Traffic Control.

8___.01 Description. This work consists of recording maintenance-of-traffic activity contemporaneously in the field and causing it to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed.

8___.02 Recording. Record each work zone activity event — activation, material modification, or removal of a traffic control installation — at the time it occurs. Where the contract requires a Worksite Traffic Supervisor (WTS) under Plan Note 642-44, the WTS is responsible for event recording; otherwise record events using personnel present at the work site or connected field devices deployed at the site that report status and location automatically. Publish each event, or transmit it to the Department's designated system, within 30 minutes of occurrence. Where connectivity is unavailable, record contemporaneously and transmit on reconnection, no later than end of shift. Data derived solely from planned schedules, permits, or office records does not conform.

8___.03 Data elements. Include for each event: route and direction; begin and end coordinates (straight-line mileage reference where available); field-verified actual start and end date-times; vehicle impact and lane-level status where applicable; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; identifiers associating the records of the same installation.

8___.04 Methods. Comply using any of the following, alone or in combination, as approved by the Engineer: entry into the Department's lane closure/permitted lane closure system where field-level access is provided; an approved data source — any device, system, or service — publishing a conforming feed listed in the USDOT WZDx Feed Registry; transmission to the Department's WZDx feed by a Department interface; or connected field devices publishing a conforming device feed for the elements they report, remainder by the other methods. No specific manufacturer, product, or service is required or preferred.

8___.05 Records; verification. The WTS daily inspection requirements of Plan Note 642-44, including completion of form CA-D-8 (TEM Figure 698-11) in the Department's electronic reporting system after each inspection, remain in effect; the same field records may serve as source records. The Engineer may compare published data with field conditions; systematic discrepancy constitutes non-conformance.

8___.06 Basis of payment. The Department will not measure this work separately; include the cost in Item 614, Maintaining Traffic.

___. Work Zone Activity Data Publication.

(1) Record each work zone activity event — activation, material modification, or removal of a temporary traffic control installation — contemporaneously in the field, and cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed.

(2) Where the Contract requires Surveillance of Traffic Control under 880.02.B(7), the certified observer is responsible for event recording under this subsection; otherwise recording shall be by personnel present at the work site or by automatic report of connected field devices deployed at the site. Publish each event, or transmit it to the Department's designated system, within 30 minutes; where connectivity is unavailable, record contemporaneously and transmit on reconnection, no later than end of shift. Data derived solely from planned schedules or office records does not comply. The traffic control device log maintained until completion and acceptance may serve as source records for this subsection.

(3) Include for each event: route and direction; begin/end coordinates (mile reference where available); field-verified actual start and end date-times; vehicle impact and lane-level status where applicable; worker presence while workers are in the activity area; reduced speed limit where imposed; and identifiers linking the records of the same installation.

(4) Comply by any of the following, alone or in combination, as approved by the Resident Engineer: (a) entry into the Department's lane closure reporting system where field access is provided; (b) an approved data source — any device, system, or service — publishing a conforming feed listed in the USDOT WZDx Feed Registry; (c) transmission to the Department's WZDx feed by a Department interface; (d) connected field devices publishing a conforming device feed for the elements they report, remainder by (a)–(c). No manufacturer, product, or service is required or preferred.

(5) The Resident Engineer may compare published data with field conditions; systematic discrepancy constitutes non-conformance with this subsection.

(6) (Add to 880.06 BASIS OF PAYMENT:) Work zone activity data publication is not measured for payment; include the cost in the contract prices for Section 880 pay items, including item (K) Surveillance of Traffic Control where that item is included in the Contract.

Add the following subsection to 00221.40:

00221.4_ Work Zone Activity Data Publication — Record each work zone activity event — the activation, material modification, or removal of temporary traffic control measures — at the time it occurs. Use the TCS (or the designated trained person under 00223.31(b)) or connected work zone devices deployed on the Project that automatically report status and location. Publish each event, or transmit it to the Agency's designated system, as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA) — a Road Event Feed or Smart Work Zone Device Feed — within 30 minutes of occurrence. If connectivity is unavailable at the Project Site, record the event contemporaneously and transmit when connectivity is restored, no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records does not comply.

Include for each event: highway and direction; begin and end coordinates (milepoint where available); actual start and end date-times identified as field-verified; vehicle impact and lane-level status where applicable; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the records of the same installation. The Traffic Control Inspection Report (Form 734-2474) requirements of 00223.31 remain in effect; the same field records may serve as source records, and published event records containing the Form 734-2474 content may serve as the inspection report for the events they cover, as approved.

Comply using one or more of the following, as approved: entry into an Agency reporting system where field-level access is provided; an approved data source — any device, system, or service — publishing the events as, or into, a WZDx feed listed in the USDOT WZDx Feed Registry; transmission to the Agency's WZDx feed using an Agency-provided interface; or connected devices publishing a conforming device feed for the elements the devices report, with remaining elements furnished by another approved method. No specific manufacturer, product, or service is required or preferred.

The Engineer may compare published data with observed conditions; systematic discrepancy constitutes non-conformance. (Add to 00221.90/00223.90:) Payment for work under this subsection is included in the payment made for the temporary protection and direction of traffic items; where the Traffic Control Supervisor item is included, submission of conforming published event records satisfies the inspection-report condition of 00223.80(a)(1) for measurement of the TCS unit.

901.3(dd) Work Zone Activity Data Publication —

Record each work zone activity event — the activation, material modification, or removal of a traffic control installation — contemporaneously in the field, and cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed.

Record events using personnel present at the work site or connected field devices deployed at the work site that automatically report status and location. Publish each event, or transmit it to the Department's designated system, within 30 minutes of occurrence. If connectivity is unavailable at the site, record the event contemporaneously and transmit when connectivity is restored, and no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records is not acceptable.

Include for each event: route and direction affected; begin and end locations as geographic coordinates, with segment/offset reference where available; actual start and end date-times identified as field-verified; vehicle impact and lane-level status where lane-level traffic control is used; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the activation, modification, and removal records of the same installation.

Comply using one or more of the following, as accepted by the Representative: entry of events into the Department's lane closure reporting system (RCRS or successor) where field-level access is provided; an approved data source — any device, system, or service — publishing the events as, or into, a WZDx feed listed in the USDOT WZDx Feed Registry; transmission to a Department WZDx feed using a Department-provided interface; or connected field devices publishing a conforming device feed for the elements the devices report, with remaining elements furnished by another accepted method. No specific manufacturer, product, or service is required or preferred.

Form CS-901 (Work Zone Traffic Control Compliance Checklist), the surveillance and review requirements of Section 901.3(p), and required MPT inspections remain in effect; the same field records may serve as source records for this subsection, and personnel performing surveillance under 901.3(p) may perform the recording. The Representative may compare published data with observed field conditions, including at the required MPT check intervals; systematic discrepancy constitutes non-conformance.

(Amend 901.4(a) to add:) Work zone activity data publication — included in the lump sum for Maintenance and Protection of Traffic During Construction; no separate measurement or payment.

937.03.___ Work Zone Activity Data Publication. The Temporary Traffic Control Implementation Manager (TTCIM) designated under 937.02, or connected field devices deployed at the work site that automatically report status and location, shall record each work zone activity event — the activation, material modification, or removal of a temporary traffic control installation — at the time it occurs. Cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed, or transmit it to the Department's designated system, within 30 minutes of occurrence. Where connectivity is unavailable at the work site, record the event contemporaneously and transmit upon restoration of connectivity, and no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records does not satisfy this Subsection.

Each event shall include: route and direction; begin and end coordinates (milepost reference where available); field-verified actual start and end date-times; vehicle impact and lane-level status where applicable; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the records of the same installation.

The Contractor may comply by any of the following, alone or in combination, as approved by the Engineer: (1) entry into a Department reporting system where field-level access is provided; (2) an approved data source — any device, system, or service — publishing a conforming feed listed in the USDOT WZDx Feed Registry; (3) transmission to a Department-designated WZDx feed by a provided interface; (4) connected field devices publishing a conforming device feed for the elements they report, remainder by (1)–(3). No specific manufacturer, product, or service is required or preferred.

The daily inspection and daily report required of the TTCIM by 937.02 remain in effect; the same field records may serve as source records for this Subsection. The Engineer may compare published data with observed field conditions; systematic discrepancy constitutes non-conformance. Work under this Subsection is not measured separately and is included in the lump sum price for Item 937.

601.__ Work Zone Activity Data Publication. An employee trained under Subsection 601.1.7 with supervisory responsibility for the TMP, or connected field devices deployed at the work site that automatically report status and location, shall record each work zone activity event — the activation, material modification, or removal of a work zone traffic control installation — at the time it occurs. The Contractor shall cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed, or transmitted to the Department's designated system, within 30 minutes of occurrence. Where connectivity is unavailable at the work site, record the event contemporaneously and transmit upon restoration of connectivity, and no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records does not satisfy this Subsection.

Each event shall include: route and direction; begin and end coordinates (mile marker where available); field-verified actual start and end date-times; vehicle impact and lane-level status where applicable; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the records of the same installation.

The Contractor may comply by any of the following, alone or in combination, as approved by the RCE: (1) entry into a Department reporting system where field-level access is provided; (2) an approved data source — any device, system, or service — publishing a conforming feed listed in the USDOT WZDx Feed Registry; (3) transmission to a Department WZDx feed by a provided interface; (4) connected field devices publishing a conforming device feed for the elements they report, remainder by (1)–(3). No specific manufacturer, product, or service is required or preferred.

The inspection and project-diary documentation practices of Engineering Directive ED-3 remain in effect; the same field records may serve as source records. The RCE may compare published data with observed field conditions; systematic discrepancy constitutes non-conformance and grounds for withholding under 601.5. Work under this Subsection is not measured separately and is included in the lump sum price for pay item 6011000, Traffic Control.

The designated traffic-control employee, or connected field devices deployed at the work site that automatically report status and location, will also record each work zone activity event — the activation, material modification, or removal of a temporary traffic control installation — at the time it occurs. The Contractor will cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed, or transmitted to the Department's designated system, within 30 minutes of occurrence. Where connectivity is unavailable at the work site, the event will be recorded contemporaneously and transmitted upon restoration of connectivity, and no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records will not satisfy this provision.

Each event will include: route and direction; begin and end coordinates (mile reference where available); field-verified actual start and end date-times; vehicle impact and lane-level status where applicable; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the records of the same installation. The weekly written report required by this section remains required; the same field records may serve as source records, and published event records may serve as the report content for the events they cover.

The Contractor may comply by any of the following, alone or in combination, as approved by the Engineer: (1) entry into a Department reporting system where field-level access is provided; (2) an approved data source — any device, system, or service — publishing a conforming feed listed in the USDOT WZDx Feed Registry; (3) transmission to a Department WZDx feed by a provided interface; (4) connected field devices publishing a conforming device feed for the elements they report, remainder by (1)–(3). No specific manufacturer, product, or service is required or preferred.

The Engineer may compare published data with observed field conditions; systematic discrepancy constitutes non-conformance. All costs for recording and publishing work zone activity data are included in the contract unit price for Traffic Control, Miscellaneous.

Add the following to 712.04: The responsible person designated under 712.04 to supervise traffic control, the certified personnel of Table 712.04-1 for lane-closure operations, or connected field devices deployed at the work site that automatically report status and location, shall record each work zone activity event — the activation, material modification, or removal of a temporary traffic control installation, including each lane closure — at the time it occurs. The Contractor shall cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed, or transmitted to the Department's designated system, within 30 minutes of occurrence. Where connectivity is unavailable at the work site, the event shall be recorded contemporaneously and transmitted upon restoration of connectivity, and no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records will not satisfy this requirement.

Each event shall include: route and direction; begin and end coordinates (log mile where available); field-verified actual start and end date-times; vehicle impact and lane-level status where applicable; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the records of the same installation.

The Contractor may comply by any of the following, alone or in combination, as approved by the Engineer: (1) entry into a Department reporting system where field-level access is provided; (2) an approved data source — any device, system, or service — publishing a conforming feed listed in the USDOT WZDx Feed Registry; (3) transmission to a Department WZDx feed by a provided interface; (4) connected field devices publishing a conforming device feed for the elements they report, with the remainder furnished by (1)–(3). No specific manufacturer, product, or service is required or preferred.

The Engineer may compare published data with observed field conditions; systematic discrepancy constitutes non-conformance. Add to 712.10: Work zone activity data publication will not be measured for payment; the cost shall be included in the lump sum price for Traffic Control.

Article 2, "Construction," is supplemented by the following:

Work Zone Activity Data. Record each work zone activity event — the activation, material modification, or removal of a traffic control installation — at the time it occurs. Record events using personnel present at the work site or connected field devices (arrow boards, portable changeable message signs, truck-mounted attenuators, traffic sensors, or other devices equipped to report status and location) deployed at the work site. Publish each event, or transmit it to the Department's designated system, as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA) — a Road Event Feed or Smart Work Zone Device Feed — within 30 minutes of occurrence. Where connectivity is unavailable at the site, record the event contemporaneously and transmit when connectivity is restored, and no later than the end of the work shift. Do not use data derived solely from planned schedules, permits, or office records to satisfy this Article.

Include for each event: route and direction affected; begin and end locations as geographic coordinates, with reference markers where available; actual start and end date-times flagged as field-verified; vehicle impact and lane-level status where lane-level traffic control is used; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the activation, modification, and removal records of the same installation.

Comply using any of the following, alone or in combination, as approved: entry of events into the Department's lane closure reporting system where field-level access is provided; an approved data source — any device, system, or service — that publishes the events as, or into, a WZDx feed listed in the USDOT WZDx Feed Registry; transmission to the Department's WZDx feed using a Department-provided interface; or connected field devices publishing a conforming device feed for the elements the devices report, with remaining elements furnished by another approved method. No specific manufacturer, product, or service is required or preferred.

Continue to document traffic control plan activities in Daily Work Report diaries and to complete Form 599, "Traffic Control Devices Inspection Checklist," as required; the same field records may serve as source records for this Article. The Engineer may compare published data with observed field conditions; systematic discrepancy between published data and field conditions is non-conformance with this Item.

Article 4, "Payment," is supplemented by the following:

Work zone activity data recording and publication is subsidiary to this Item.

1.15 WORK ZONE ACTIVITY DATA PUBLICATION

A. Record each work zone activity event — activation, material modification, or removal of a temporary traffic control installation — contemporaneously in the field. Publish each event as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed, or transmit the event to the Department's designated system, within 30 minutes of occurrence. Where site connectivity is unavailable, record contemporaneously and transmit upon reconnection, no later than end of shift. B. Record events using personnel present at the work site or connected field devices deployed at the site that report status and location automatically. Do not use data derived solely from planned schedules, permits, or office records to satisfy this Article. C. Include for each event: route and direction; begin and end coordinates (milepoint reference where available); field-verified actual start and end date-times; vehicle impact and lane-level status where applicable; worker presence while workers are within the activity area; reduced regulatory speed limit where imposed; identifiers associating records of the same installation. D. Comply by any of the following, alone or in combination, as accepted by the Engineer: (1) entry into the Department's lane closure/traffic management reporting system where field access is provided; (2) an approved data source — any device, system, or service — publishing a conforming feed listed in the USDOT WZDx Feed Registry; (3) transmission to the Department's WZDx feed by a Department interface; (4) connected field devices publishing a conforming device feed for the elements they report, remainder by (1)–(3). No specific manufacturer, product, or service is required or preferred. E. The Traffic Control Inspection forms required by Article 1.5 and the inspections performed by the Traffic Control Maintainer under Article 1.9 remain required; the same field records may serve as source records for this Article, and the Traffic Control Maintainer is responsible for event recording. The Engineer may compare published data against field conditions; systematic discrepancy constitutes non-conformance. F. Refer to Section 01282 — work under this Article is not measured separately and is incidental to the traffic control items.

641.0__ WORK ZONE ACTIVITY DATA PUBLICATION. (a) The person designated under Subsection 630.02(a) to coordinate traffic control, or connected field devices deployed at the work site that automatically report status and location, shall record each work zone activity event — the activation, material modification, or removal of a traffic control installation — at the time it occurs. The Contractor shall cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed, or transmitted to the Agency's designated system, within 30 minutes of occurrence. Where connectivity is unavailable at the work site, the event shall be recorded contemporaneously and transmitted upon restoration of connectivity, and no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records shall not satisfy this Subsection.

(b) Each event shall include: route and direction; begin and end coordinates (mile marker where available); field-verified actual start and end date-times; vehicle impact and lane-level status where applicable; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the records of the same installation.

(c) The Contractor may comply by any of the following, alone or in combination, as approved by the Engineer: (1) entry into an Agency reporting system where field-level access is provided; (2) an approved data source — any device, system, or service — publishing a conforming feed listed in the USDOT WZDx Feed Registry; (3) transmission to an Agency WZDx feed by a provided interface; (4) connected field devices publishing a conforming device feed for the elements they report, remainder by (1)–(3). No specific manufacturer, product, or service is required or preferred.

(d) The daily daytime and nighttime inspections required by Subsection 641.05 remain in effect; the same field records may serve as source records for this Subsection, and the published events may serve as the record of those inspections where they contain the required information. The Engineer may compare published data with observed field conditions and Daily Work Report entries; systematic discrepancy constitutes non-conformance. Work under this Subsection is not measured separately; the cost is included in the Contract lump sum price for Item 641.1000, Traffic Control, or Item 641.1100, Traffic Control, All-Inclusive.

(a) The person verified under Section 105.14(a)1, or connected field devices deployed at the work site that automatically report status and location, shall record each work zone activity event — the activation, material modification, or removal of a temporary traffic control installation, including each traffic switch or change — at the time it occurs. The Contractor shall cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed, or transmitted to the Department's designated system, within 30 minutes of occurrence. Where connectivity is unavailable at the work site, the event shall be recorded contemporaneously and transmitted upon restoration of connectivity, and no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records will not satisfy this provision.

(b) Each event shall include: route and direction; begin and end coordinates (mile marker where available); field-verified actual start and end date-times; vehicle impact and lane-level status where applicable; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the records of the same installation.

(c) The Contractor may comply by any of the following, alone or in combination, as approved by the Engineer: (1) entry into a Department reporting system where field-level access is provided; (2) an approved data source — any device, system, or service — publishing a conforming feed listed in the USDOT WZDx Feed Registry; (3) transmission to a Department WZDx feed by a provided interface; (4) connected field devices publishing a conforming device feed for the elements they report, remainder by (1)–(3). No specific manufacturer, product, or service is required or preferred.

(d) The daily inspections and Work Zone Safety Checklist documentation required by Section 512.03 remain in effect; the same field records may serve as source records for this provision. The Engineer may compare published data with observed field conditions; systematic discrepancy constitutes non-conformance. No separate payment will be made for work under this provision; the cost shall be included in the prices for the Section 512 pay items.

Supplement Section 2-04.3(1)B with the following: In performing duty 3, the TCS (or connected field devices deployed at the work site that automatically report status and location) shall also record each work zone activity event — the activation, material modification, or removal of a temporary traffic control installation — at the time it occurs, and the Contractor shall cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed, or transmitted to the Contracting Agency's designated system, within 30 minutes of occurrence. Where connectivity is unavailable at the work site, the event shall be recorded contemporaneously and transmitted upon restoration of connectivity, and no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records shall not satisfy this requirement.

Each event shall include: route and direction; begin and end coordinates (milepost where available); field-verified actual start and end date-times, including the times signs and devices are installed and removed; vehicle impact and lane-level status where applicable; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the records of the same installation.

The Contractor may comply by any of the following, alone or in combination, as approved by the Engineer: (1) entry into a Contracting Agency reporting system where field-level access is provided; (2) an approved data source — any device, system, or service — publishing a conforming feed listed in the USDOT WZDx Feed Registry; (3) transmission to a Contracting Agency WZDx feed by a provided interface; (4) connected field devices publishing a conforming device feed for the elements they report, remainder by (1)–(3). No specific manufacturer, product, or service is required or preferred.

Published event records containing the content required of the daily traffic control diary may be submitted, with the Engineer's approval, as the alternate form permitted by 2-04.3(1)B duty 3 for Forms 421-040A and 421-040B; the diary submittal deadline and the TCM's daily review of TCS diaries under 2-04.3(1)A remain in effect. Systematic discrepancy between published data and field conditions constitutes non-conformance. Work under this provision is not measured separately; the cost shall be included in the lump sum price for "Project Temporary Traffic Control" or, on itemized contracts, the lump sum price for "Traffic Control Supervisor."

636.___-WORK ZONE ACTIVITY DATA PUBLICATION: The Traffic Control Supervisor designated under 636.3 (or, where no TCS is required, personnel present at the work site), or connected field devices deployed at the work site that automatically report status and location, shall record each work zone activity event — the activation, material modification, or removal of a temporary traffic control installation — at the time it occurs. The Contractor shall cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed, or transmitted to the Division's designated system, within 30 minutes of occurrence. Where connectivity is unavailable at the work site, the event shall be recorded contemporaneously and transmitted upon restoration of connectivity, and no later than the end of the work shift. Data derived solely from planned schedules, permits, or office records shall not satisfy this subsection.

Each event shall include: route and direction; begin and end coordinates (milepost where available); field-verified actual start and end date-times; vehicle impact and lane-level status where applicable; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the records of the same installation.

The Contractor may comply by any of the following, alone or in combination, as approved by the Engineer: (1) entry into a Division reporting system where field-level access is provided; (2) an approved data source — any device, system, or service — publishing a conforming feed listed in the USDOT WZDx Feed Registry; (3) transmission to a Division WZDx feed by a provided interface; (4) connected field devices publishing a conforming device feed for the elements they report, remainder by (1)–(3). No specific manufacturer, product, or service is required or preferred.

The daily inspection duties of the Traffic Control Supervisor and the Daily Work Report and Traffic Control Worksheet documentation described in the Construction Manual remain in effect; the same field records may serve as source records. Work under this subsection will not be measured for payment and shall be included in the prices for the Section 636 pay items (or, where the contract contains no Section 636 items, shall be at the Contractor's expense as part of maintaining traffic).

Replace 643.3.1(5) with the following supplemented paragraph and add the following:

(5) Review signs, traffic control devices, and temporary marking for location, position, visibility, and appropriateness for job conditions immediately after each setup, and conduct additional reviews as necessary. In addition, record each work zone activity event — the activation, material modification, or removal of a traffic control setup or device deployment — at the time it occurs, using personnel present at the work site or connected field devices deployed at the site that automatically report status and location. Cause each event to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed, or transmitted to the department's designated system, within 30 minutes of occurrence. If connectivity is unavailable, record contemporaneously and transmit upon restoration, no later than the end of the work shift. Data derived solely from planned schedules or office records does not conform.

Include for each event: route and direction; begin and end coordinates; field-verified actual start and end date-times; vehicle impact and lane-level status where applicable; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating records of the same installation. Device out-of-service periods reported under this provision may support the measurement adjustments of 643.4.1.

The contractor may conform using one or more of the following, as the engineer approves: entry into a department reporting system where field-level access is provided; an approved data source — any device, system, or service — publishing a conforming feed listed in the USDOT WZDx Feed Registry; transmission to a department WZDx feed by a provided interface; or connected field devices publishing a conforming device feed for the elements they report, with the remainder furnished by another approved method. No specific manufacturer, product, or service is required or preferred.

The engineer's reviews under CMM 145 and project-diary documentation remain in effect; the same field records may serve as source records. Systematic discrepancy between published data and field conditions constitutes non-conformance. This provision is administered under the Traffic Control item (643.5000); the department will not measure the work separately.

Work Zone Activity Data Publication. The daily traffic control device record (Form E-101, Daily Traffic Control Device Record, where used) documents the traffic control devices in service each day. In addition, and regardless of the method of payment for temporary traffic control, the contractor shall cause each work zone activity event — the activation, material modification, or removal of a temporary traffic control installation — to be published as machine-readable data conforming to the Work Zone Data Exchange (WZDx) Specification, version 4.2 or later (FHWA), as a Road Event Feed or Smart Work Zone Device Feed, as follows:

(a) Events shall be recorded contemporaneously by personnel present at the work site or reported automatically by connected field devices deployed at the site, and shall be published, or transmitted to the Department's designated system, within 30 minutes of occurrence. Where connectivity is unavailable at the work site, events shall be recorded contemporaneously and transmitted upon restoration of connectivity, and in no case later than the end of the work shift. Data derived solely from planned schedules, permits, or office records shall not satisfy this subsection.

(b) Each published event shall include: route and direction; begin and end coordinates (milepost reference where available); field-verified actual start and end date-times; vehicle impact and lane-level status where applicable; worker presence status while workers are within the activity area; reduced regulatory speed limit where imposed; and identifiers associating the records of the same installation. The daily traffic control record for the same period (Form E-101 or the consistent form used under this subsection) may serve as the source record.

(c) The contractor may comply by any of the following, alone or in combination, as approved by the engineer: (1) entry into the Department's lane closure reporting system where field-level access is provided; (2) an approved data source — any device, system, or service — publishing a conforming feed listed in the USDOT WZDx Feed Registry; (3) transmission to a Department WZDx feed by a Department interface; (4) connected field devices publishing a conforming device feed for the elements they report, with the remainder furnished by (1)–(3). No specific manufacturer, product, or service is required or preferred.

(d) The engineer may compare published data with observed field conditions; systematic discrepancy constitutes non-conformance with this subsection.

(e) (Add to 703.5.1, General:) Work zone activity data publication will not be measured for payment and shall be included in the lump sum and unit prices for the Section 703 temporary traffic control items.