As we discussed in the introduction, we have used a systems delivery lifecycle as a way to structure the manual and support finding the right guidance at the right time. Each stage of the lifecycle will present different challenges that need to be overcome to achieve success, and this manual provides guidance to help Authorities overcome these challenges. Whilst there are parallels with project delivery processes, it should be noted that in this manual we refer to a system engineering delivery lifecycle. This is distinct from a project lifecycle which typically ends at a defined project end point, whereas a system lifecycle only ends when the system is decommissioned.
We’ve assumed an idealised lifecycle for a Smart Street system consisting of 13 steps as illustrated in the adjacent diagram. The actual lifecycle steps followed by a specific organisations or projects will vary, and there are a variety of alternative lifecycle processes (e.g. SEHBoK, AgilePM). However, the intention of this section is to set out a general example to illustrate how this manual may be applied as part of the delivery process. For example, some projects may focus on changing internal working practices, and better using existing system capabilities , rather than involving procurement of new services and products.
This content is not intended to replace any existing resources that Authorities may refer to, particularly as part of procurement, which may include:
The table below provides a description of each lifecycle stage and discusses aspects that will need consideration at each of these stages.
The content of the use-cases in this manual are intended to help authorities progress through these steps, as described in the ‘Our Approach Use Case Overview’