Works Comments

Key Differences from EToN

Confirm models Works Comments, Informal Overrun Warnings and FPN Comments as Street Works Comments whereas Street Manager has a general concept of Comments with a Topic.

EToN already supports the concept of General, Overrun Warning and FPN comments but Street Manager also introduces two new Topics of "Inspection" and "Section 74". Two new Comment Types will be added to cover these new topics and Confirm will match them based on the Comment Type Code. For the topics that already exist, Confirm will match based on the DfT Ref. Street Manager has also removed the "Duration Challenge Nonacceptance" comment type. If this notice is logged in Confirm it will be sent to Street Manager under the "Section 74" topic, but the reverse will not apply and "Section 74" comments received from Street Manger will map to a new Comment Type. The following table summarises the changes:.

Street Manager Topic	Existing or New	Confirm Comment Type Code	Confirm Comment Type Name	Confirm Comment Type DfT Ref.	Notes
General	Existing	C15	EToN 4: Works Comments	EToN 4: Works Comments	Confirm will match based on the Dft Ref.
Overrun Warning	Existing	C14	EToN 4: Informal Overrun Warning	EToN 4: Informal Overrun Warning	Confirm will match based on the Dft Ref.
FPN	Existing	C22	EToN 4: FPN Comments	EToN 4: FPN Comments	Confirm will match based on the Dft Ref.
Inspection	New	CINS	Inspection	EToN 4: Works Comments	Confirm will match on Code
Duration Challenge Non-Acceptance	Existing	C13	EToN 4: Duration Challenge Non-Acceptance	EToN 4: Duration Challenge Non-acceptance	Mapping for export from Confirm to Street Manager only
Section 74	New	CS740	Section 74: Warning Issued	EToN 4: Works Comments	Confirm will match on Code
Section 74	New	CS741	Section 74: Received Overrun Warning	EToN 4: Works Comments	Confirm will match on Code
Section 74	New	CS742	Section 74: Site Visited Works Closed	EToN 4: Works Comments	Confirm will match on Code
Section 74	New	CS743	Section 74: Overrun Charges Ended	EToN 4: Works Comments	Confirm will match on Code
Section 74	New	CS744	Section 74: Withdraw Overrun Warning	EToN 4: Works Comments	Confirm will match on Code
Section 74	New	CS745	Section 74: Draft Invoice Issued	EToN 4: Works Comments	Confirm will match on Code
Section 74	New	CS746	Section 74: Received Draft Invoice	EToN 4: Works Comments	Confirm will match on Code
Section 74	New	CS747	Section 74: Reviewing Draft Invoice	EToN 4: Works Comments	Confirm will match on Code
Section 74	New	CS748	Section 74: Charge Reviewed	EToN 4: Works Comments	Confirm will match on Code
Section 74	New	CS749	Section 74: Mark as Resolved	EToN 4: Works Comments	Confirm will match on Code
Section 74	New	CS750	Section 74: Overrun Warning Disputed	EToN 4: Works Comments	Confirm will match on Code

Field Mapping

Street Manager Field	Confirm Field	Notes (When importing into Confirm from Street Manager)	Notes (When exporting from Confirm to Street Manager)
Topic	Street Works Comment > Comment Type	Inspection and Section 74 topics will be matched to the new Codes, other Topics will be matched by DfT reference. Note: Street Manager does not currently provide access to the Comment Topic via the APIs so all imported comments are being treated as "General" Comments until this is resolved	If the Comment Type is one of the new ones then the Code will be used to determine the Topic, otherwise the Dft Ref. will be used. If there are multiple matches when matching on DfT Ref then the first match will be used when sorting alphabetically by Comment Type Name.
Comment	Street Works Comment > Text	The comment text will be all of the Details that are displayed in the Works history. The Username who logged the comments will also be appended	For Duration Challenge Non- Acceptance this will be prefixed with the Comment Type Name
Date and Time	Street Works Comment > Issued		Note if a comment is edited and resent a new comment will be added in Street Manager
	Street Works Comment > Comment From	If the Highways Authority for the Works is flagged as an Initiator in Confirm and the Promoter is not then it is assumed the comment came from the Promoter. Otherwise the Highway Authority organisation will be used. The person who made the comment can be determined from the Username logged in the Text	We will use the API user (Authority or Promoter) that corresponds to whether the comment came from the Promoter or Highway Authority. The Authority API user will be used for Interested party comments.