Technical update: Local Waste Service Standards Project | Paul MacKay | October 2015
Download as PPT, PDF1 like1,307 views
The document outlines a local digital program aimed at improving waste service standards through innovative, efficient, and user-focused services. It emphasizes the use of open data, APIs, and real-time tracking to enhance transparency and effectiveness in waste management. Key components include service accessibility, integration across government levels, and the incorporation of user consent for data sharing.
Technical update: Local Waste Service Standards Project | Paul MacKay | October 2015
- 1. Local Digital Programme Local Waste Service Standards Project Alpha Show and Tell#LocalDigital @LDgovUK
- 3. http://tom.loosemore.com/2015/10/01/presentatio n-to-code-for-america-summit-2015/
- 4. 1. Services so good they were previously unimaginable
- 5. 2. Services which work first time, usually in real time.
- 6. 3. New services set up in weeks, and run at fraction of today’s cost
- 7. 4. Ministers can see if their policy is working as intended within days or weeks, not decades
- 8. 5. Those on the front line can focus their effort on supporting those who need help the most.
- 9. 10. Open public data is canonical, infrastructural, and immutable. Services use open standards and create open standards.
- 10. 11. Services should gracefully span local, central and devolved governments… …provided the user consents.
- 11. 13. Everything is available through an API for 3rd party use… … provided the user grants permission, and it’s secure.
- 13. Data models Names and properties of things
- 15. Web APIs Server application interface Client application HTTP over the Web Exchange JSON or XML How software systems communicate using Application Programming Interfaces
- 16. Data formats OBJECTID,LOCATION,MATERIALS,CO_MINGLED,TEXTILES,SHOES,BOOKS,MEDIA,PRINTER_CARTRIDGES,WASTE_ELEC TRICAL,LIGHTBULBS,BATTERIES,CARRIER_BAGS,OIL_BANKS,EASTING,NORTHING 74,"Tulse Hill Estate, Scarsbook House, Next to Jubilee Primary School","T,S",No,Yes,Yes,Yes,Yes,No,No,No,No,No,No,531174,174224 75,Valley Road Junction with Streatham Common North,"L,B",No,No,No,No,No,No,No,Yes,Yes,No,No,530538,171051 Machine readable data X,Y,ogc_fid,datatablename,sitename,address,streetname,town,county,postcode,uprn,green_glass,bro wn_glass,clear_glass,newspaper,plastic_and_cans,cardboard,cds,books,textiles,shoes,printer_cart ridge,engine_oil,liquid_food_and_drink_cartons,aluminium_foil,waste_electronic_electrical,datas ource,copyright,easting,northing,mi_prinx,mi_style 500003.12582619902,149457.637451535,1,Recycling Centres/Bring Sites,Bright Hill Car Park,Bright Hill Car Park,Bright Hill,Guildford,Surrey,GU1 3RU,,,,,,,,,,Yes,,,,,,,GBC Cleansing and Recycling - July 2009,? Guildford Borough Council 2012,500003,149458,1,"Symbol (32, 5248000, 18)" 499876.08592475299,151200.998419649,2,Recycling Centres/Bring Sites,Woking Road Depot,Woking Road Depot,Woking Road,Guildford,Surrey,GU1
- 17. Data modelsData models TaxonomiesTaxonomies APIsAPIs Data formatsData formats
- 18. • Missed bin • Missed bins • Missed Collection • Missed bin or recycling collection • Report a missed collection • Report a missed bin collection How do we describe a thing?
- 19. Missed bin collection reasons largest 84 terms smallest 5 terms
- 20. Existing software systems What others? Smart Cities Concept Model Data modelsData models
- 21. ThingThing IntangibleIntangible ServiceService GovernmentServiceGovernmentService WasteServiceWasteService • name • description • url • provider • serviceArea • serviceOperator • lastCollections • nextCollections
- 26. Missed collection eventsMissed collection events
- 27. Sorry we didn't empty your bins – they were contaminated with food waste, so could not be collected. Contaminated: Food waste CONTAMINATED BROWN - FOOD CitizenCitizen CSRCSR In-cabIn-cab
- 29. Different ways to describe services: - Date first - Materials first
- 30. ItemItem
- 31. next collection finder Bulky items taxonomy
- 32. Rounds formatRounds format Starting new contracts…
- 33. Waste service Services Collections Rounds Containers Collection points Website Addresses (LLPG) Case management SMS Automated phone Payments Waste tracking system WasteDataFlow In-cab unitsCloud servers TrucksWeighbridges Customer care App CaseCase
- 34. ThingThing IntangibleIntangible CaseCase • name • description • url • customer • status MissedCollectionRequestMissedCollectionRequest NewBinServiceNewBinService
- 35. Waste service Services Collections Rounds Containers Collection points Website Addresses (LLPG) Case management SMS Automated phone Payments Waste tracking system WasteDataFlow In-cab unitsCloud servers TrucksWeighbridges Customer care App GOV.UK Pay?GOV.UK Pay? Notifications platformNotifications platform
Editor's Notes
- #5: What does Uber for waste look like? How to transition to the circular economy?
- #6: Real time aspect of missed collection reporting is bit generally not available and was highest priority.
- #7: What’s required to introduce a new food collection? How is the service rolled out and citizens informed?
- #8: Comes back to metrics, performance and reporting. See Solihull channel shift dashboard.
- #9: Make it much easier for those who need less support to do what they need without front line assistance.
- #10: These are good things.
- #11: How to build in feedback channels associated with each service?
- #12: Who is responsible? Who defines policy? How can I comment?
- #13: Interesting questions around use of GOV.UK Verify compared with “My Account” systems councils are using.
- #14: Heart of this project. Canonical - use APIs to get live data. Infrastructural - eat your own dogfood. Use the APIs for your infrastructure. Open standards - government can drive the market.
- #15: If I move house, how can services move easily? Consistency of service across local government.
- #16: Many small variations in policy around waste.
- #17: Create digital infrastructure that can and should be used by people we don't yet know to build services we can’t yet imagine. That’s government as a platform.
- #18: Registers - new idea GDS are blogging about.
- #19: Capital, UMS, BBC World Cup, blah blah blah. Producer, Editor, Senior Producer, Delivery Lead, Head of this, that and the other. All along, I was a product manager, or I was hiring product managers.
- #20: The types of objects and their properties. Can include defining taxonomies, e.g. missed bin reasons, material types, A-Z lists. Build a common language.
- #22: Definition of how a client can talk to a server. Typically over the Web in this case. Interact on demand. Faster than CSV.
- #23: Data formats are physical manifestations of parts of the model. Data transfer between systems at intervals. Single CSV file or data package (multiple combined).
- #24: Data models and taxonomies relatively abstract. Need applying to things. APIs exchange objects in format of models. Data files matching a format capture certain fields or taxonomy values.
- #26: Got 5-6 different lists from councils. Analysed and combined into a reasonable common list. Challenge: in-cab systems may need to copy some terms for each bin colour. Need to adapt and filter back. Further work: dig further into reasons for variations. Spread is 5-84 terms.
- #27: For data modelling, referenced several inputs. Concept model - high level view existing schemas, mostly schema.org. Supplier software systems.
- #28: Quick example. schema.org models derive from Thing, which has several common properties. Intangible is a grouping of non-physical things. Service can define any service. GovernmentService enables defining separate operator. WasteService is part of spec.
- #29: Place is basic model for a “thing with location”. It may have an Address, which is based on BS7666 definition. Aim for general model that can be widely applied across services. Luton’s data pulled from a test Bartec Collective database. Could be pulled from shared council LLPG system or other API. Could work differently if people logged into an account.
- #31: Worked with WRAP to put together a common list of container types. Raised “Triple box stack” question. Please suggest any other missing types. Discussing use of images, but other options exist.
- #32: Again, WRAP are the experts. Difference between material streams and materials. Created list of common materials collected at kerbside with associated stream colours and “typical” items they might take. This will vary. Could be candidate for register.
- #33: Issues arising during rounds recorded against property or street. Note this is a mockup. Have data via API. Also photos dependent on the ability to record them.
- #35: Pulled from OpenDataCommunities linked data. Perhaps trivial example for a council site, could be very useful for 3rd party services. Worth considering how to maintain data, keep uptodate. Useful example of rich data from separate API.
- #36: Different ways to model services.
- #38: Develop canonical terms. Separate out the metadata, allows it to be easily adapted. Ideally a linked data repository or register.
- #39: Have an initial version of a data format published. Very dependent on the supplier system, may need further iterations and discussion.
- #40: Have done some work to investigate ideas. Large problem space, outside of scope to tackle fully. CloudElements have built REST API across ~12 CRM systems, e.g. Dynamics, Salesforce, etc.
- #42: Have done some work to investigate ideas. Large problem space, outside of scope to tackle fully. CloudElements have built REST API across ~12 CRM systems, e.g. Dynamics, Salesforce, etc.