Skip to main content

How we created our winter updates

It's that time of year again, when council highways staff can be out all hours, keeping us safe by treating and clearing the roads from the effects of the winter. Where I work we've offered alerts on what's happening for a while and I thought it might be useful for other councils to let you know how this works.

To start I'll explain the restrictions we work with. We couldn't have a comms officer on call 24 hours a day, 7 days a week, for the whole of the winter, just to let people know about gritting. Also, a number of highways officers deal with treating and clearing the roads on a rota, and it wouldn't be cost effective to train them all up in how to update our website, Twitter and so on.

The challenge was to make this work with no additional operational resource or skills.

So how did we make this happen?

During the winter at least once a day, a highways officer makes a professional judgement as to whether and what type of treatment the roads in our area need and they record this in an IT system. We spoke to MeteoGroup, the suppliers and asked them to build something that was triggered every time an officer saves an update.

The content management system (CMS) we use has an application programming interface (API) which lets other IT systems talk to it, so we created a web service that MeteoGroup could call which stores all the right information in the right places in our CMS, to update our website.

We then created a new template to pull out this information and display links to other useful stuff, like a map of where we were gritting or clearing, which is already stored in our mapping system. You can see the winter service update page here.

Once the information is in our CMS we can use it in lots of ways. So there's an alert on our home page that during the winter is there even if we're not doing anything. One of the things I learned during past snowy periods is that it's important to tell people some of the stuff we're not doing or we don't know, to keep them informed, as it really cuts down calls to a call centre.

We also offer an RSS feed of the same information which means anyone can take it and put it on their own website, or create their own alerts. It also enables us, through Twitterfeed to update a Twitter account dedicated to roads.

So there we go, updates and alerts on our website, Twitter and RSS and with no additional operational resource needed. That's Government as a Platform in action years before the term became widely fashionable.

The most amusing element of this work? Because highways officers kept using the acronym RST, we wrote a line of a line of code that saves this text as "road surface temperatures" in our CMS and therefore wherever it's used online.

Do let me know if you'd like any help and advice getting this up and running at your council. In the spirit of LocalGov Digital, work and other time permitting, I'm always happy, to think, do and share.

Image By Editor5807 (Own work) CC BY 3.0, via Wikimedia Commons.

Comments

Popular posts from this blog

Digital best practice checklist

This week I finished the draft of a digital best practice check-list. It's not digital strategy, in fact I'm increasingly thinking organisations don't need a digital strategy, they need a delivery strategy. My draft has check-list of seven questions and recommendations, with one overall recommendation regarding best practice for delivering digital. Ideally it would be incorporated into a wider service and information delivery strategy. Below I've omitted the bulk of the content, the reasoning behind arriving at the recommendation from the question because it's still in draft, but here are the seven questions and eight recommendations: 1. Is the council properly promoting its digital services and content, to reduce avoidable contact? Recommendation: Establish a “digital first” ethos to the promotion of services and better targeting what, when and where they're promoted. 2. Are the digital services the council offers, especially where the design and

Carl's Conundrum of Internal Influence

I'm writing this partly as a reply to an excellent piece that Carl Haggerty published about the disconnect between internal and external influence and partly due to various conversations over the past month about how to make using tools like collaboration platform  Pipeline common practice. This isn't really about Carl though, or Devon County Council, or any other council specifically, it's more a comment on the influence of digital teams in local governments, or lack of, and how to resolve this. So here's the question that prompted this piece. How can someone who's been recognised nationally for their work, first by winning the Guardian's Leadership Excellent Award and who has more recently been placed in the top 100 of the Local Government Chronicle's most influential people in local government , "sometimes feel rather isolated and disconnected to the power and influence internally". First, let's consider whether is this a problem to

Pipeline Alpha

In September 2014, officers from 25 councils met in Guildford to discuss a platform to enable collaboration across Local Government. A "Kickstarter for local government" is the missing part to Makers Project Teams , a concept to enable collaborative working across different organisations put forward by LGMakers the design and development strand of LocalGov Digital . Based on the user needs captured at the event, LGMakers created collaboration platform Pipeline and by October people from over 50 councils had signed up . Pipeline is an Alpha, a prototype set up to evaluate how a Kickstarter for councils might work. It is a working site though, and is being used as the platform it is eventually intended to be, at present without some of finer features a live offer might have. So what have I've learnt in the eight months since we launched Pipeline? There's a strong desire to collaborate  LocalGov Digital isn't a funded programme. I wrote about how much it

Superfast highways

You may have seen this slide I put together to help explain digital transformation This week we launched a new beta service to report speeding traffic. It looks fairly simple but to give you an idea of what's happening in the background I thought it might be useful to show you the before and after. So here's the before and as you can see it's completely a manual process. Stuff might be recorded electronically but it takes someone to do something seven time to make the process work and send it to the parish or the district. Here's the after What this doesn't tell you is that it's basing whether the request is for the parish or district on three questions. It's also doing a spatial look up to find the parish and returning the parish clerk details using the Modern.Gov API. Because these are already part of our platform this is data that we currently maintain, so there's no additional work to keep this up to date and we've reduced the h

Defining transformation to a wider audience

For the past month I've been putting together a paper on the next steps of digital transformation, for the organisation I work for. I'm proposing we look at two capabilities and two business areas, and if approved I'll be writing more about it. It's been a great exercise in gathering my thoughts and helping me to define digital transformation to a wider audience and how it fits into the bigger picture of service improvement. Here's some of the stuff I've learnt or had affirmed: Transformation, digital or not, starts with understanding the needs of the user through research. This should be obvious, but in local government too often I've seen "build it and they will come" approach applied. It's unlikely a commercial operation would launch a new product without first researching the market, so why would a digital service be any difference? A couple of years ago I wrote how the phrase "digital transformation" was hindering digit