Confirm

Expand all | Collapse all

Street Manager Update (UK)

  • 1.  Street Manager Update (UK)

    Pitney Bowes
    Posted 04-09-2018 12:04

    Street Manager Update (UK)

    Pitney Bowes attended a session with the DfT and other EToN Developer Group members on the 29th March to discuss the current status of the Street Manager project.

    The “Alpha” phase of the project is now complete and a working prototype showing Forward Planning and Granting a Permit has been demonstrated to selected stakeholders. We were only shown a PowerPoint of this during the meeting. The DfT stated that they were awaiting budget approval before proceeding to the next “Beta” phase.

    The current proposed timescales are to have a “private” beta early in 2019 with a public beta at the end of 2019. The private beta will be between a small group of authorities / utilities but the idea is that Street Manager would replace EToN for those participants. The public beta will be available to everyone and transition arrangements will apply regarding moving off EToN (a further workshop is planned to discuss transition).

    At the moment it is still not clear what functionality will be included in the first release. The DfT clearly stated that the scope would be limited to Street Works, but it is possible that not all aspects of a Street Works system will be included, such as overrun charging, inspection sampling, etc. The DfT stated it will be up to the user community to dictate how functionality is prioritised for delivery. It was reiterated that Application Program Interfaces (APIs) will be provided to allow systems like Confirm to interface with Street Manager, e.g. for noticing / permitting of own works, mobile inspections, etc.

    However, the DfT made it very clear that, although they were happy to keep developers informed on the progress of the project, they would not be directly seeking our input regarding system functionality or interfacing requirements. The DfT are expecting the end users (authorities and utilities) to fully specify all requirements and ensure for themselves that any gaps in functionality are covered by their systems.

    This does not mean that developers cannot participate in the process, but we will only be able to do so if we are invited to relevant workshops and requirements gathering sessions by our customers – the DfT will not invite us themselves.

    <