| Better management of street works through accredited software | |
|
The
EToN Developers Group is an important industry body that coordinates the
development of software for the management of street works in the UK.
The Group, which represents the industry’s experts in information
technology, advises on street works technical specifications and provides
accreditation to ensure software is compliant with agreed standards. |
|
![]() |
As
a technical development alliance between different software suppliers, one
of the Group’s primary functions is to ensure better compatibility
between systems. This is crucial as new street works legislation requires
automation including the electronic transfer of information between
highway authorities and the many services involved in street works. |
| Objectives of Group |
| Assist the various national
Street Works bodies in the production of technical specifications for
implementation of Street Works Codes of Practice.
Provide an industry-based consultation route for national bodies. Maximise on degree of compatibility between software systems produced by Group members. Agree change control strategies for
implementation of new procedures, in order to Where possible, resolve areas of contention which arise as a result of differing interpretations of the various Street Works Codes of Practice and associated specifications. Where the solution to problems is beyond the scope of the Group, identify the problems, and recommended solutions, to the relevant national Street Works bodies. As a result of above, maximise the
effectiveness of end-user operations, and minimise disruption resulting
from the introduction of new procedures. |
| Structure of the Group |
|
A Central Working Body
will be responsible for determining topics to be addressed, detailed
discussion of issues, canvassing opinions, and the drafting of agreed
solutions.
All other members of the Group will operate in a consultative capacity, with a direct access path via any of the Working Body members, to raise topics for consideration, express views, and propose solutions for consideration. The Central Working Body will comprise permanent representatives of the four major software developers of Street Works software, plus one representative of the other members of the Group. This latter representative will be rotated amongst the other group members, excluding any member who wishes not to be included. The status of all members of the Central Working Body will be equal. Each of the four permanent representatives will in turn (6 month intervals) act as "Spokesperson" for the Group, and provide a single point of contact externally to the Group. Any organisation
with an active involvement in the development of software for Street Works
purposes is entitled to be represented by a consultative member of the
Group. |
| Methods of Operation |
| The
workings of the Group will typically take place via email communications,
with occasional technical meetings, when necessary, to discuss and resolve
differences and confirm decisions. All working email communications will
be copied to all Central Working Body representatives. Detailed interim
communications on specific issues which take place between representatives
of the Central Working Body will not necessarily be circulated throughout
the Group (although they may be, at an individual representative's
discretion). All key decisions will be circulated to all members of the
Group.
The objectives of the Central Working Body will be to reach unanimous decisions by means of reasoned argument and multi-lateral compromise. In the event of being unable to reach a unanimously acceptable solution, the Central Working Group will decide either to adopt and ratify a majority decision, in which case opposing views will be documented, or to refer the issue as an un-resolved problem to another body. Since the aim of the Group is to resolve problems which others have been unable to address, the latter course of action would be a last resort. The objective of the Group would be to conform to Codes of Practice and technical implementation specifications (e.g. Appendix E and the Data Capture Codes) to the maximum extent possible. Only where clear contradictions exist, or the specification would introduce serious logical anomalies, would the recommendations be made to adopt a standard which is different to that published by the national bodies.
|