Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Automating Field Data Collection

Automating Field Data Collection

From GIS-Pro 2016 in Toronto.

Coleman McCormick

November 01, 2016
Tweet

More Decks by Coleman McCormick

Other Decks in Technology

Transcript

  1. field data automation ✦ fulcrumapp.com/gispro2016 About me Coleman McCormick 12

    years in mapping / GIS 7 years developing software products Work with companies + organizations worldwide on business process, data management, software
  2. field data automation ✦ fulcrumapp.com/gispro2016 What we do Software company

    in St Petersburg, FL est. 2009 Mobile form builder — web, iOS, Android Workforce management Automation & streamlining of data collection SaaS subscription service Worldwide customer base — 100+ countries
  3. field data automation ✦ fulcrumapp.com/gispro2016 Field collection use cases •

    Asset management • Damage assessments • Inspections • Public works • Regulatory audits • On and on…
  4. field data automation ✦ fulcrumapp.com/gispro2016 Agenda Goals and objectives in

    collecting data Brief history of data collection A look at workflow Friction and its causes Techniques Some examples of automation in action
  5. field data automation ✦ fulcrumapp.com/gispro2016 Ideals + Goals i need

    to collect some data. what does “success” look like?
  6. field data automation ✦ fulcrumapp.com/gispro2016 What’s the ideal process? •

    Think about goals and objectives • What questions need answering? • Who are the stakeholders? (Who’s asking the questions?) • Interviews — understand the “why” of the requirements • Paint the picture — what does success look like? • Tasking your field workforces
  7. field data automation ✦ fulcrumapp.com/gispro2016 Start by defining the successful

    final result, and work backwards! bit.ly/amazon-product-dev Need consensus on goals from bottom to top “First write the press release, then build the product” Meeting Mission Objectives
  8. field data automation ✦ fulcrumapp.com/gispro2016 On-Demand • Leadership wants answers

    to questions now, not 3, 6, or 12 months later • Reporting on specific data views — the data I want, when I want it
  9. field data automation ✦ fulcrumapp.com/gispro2016 Other key goals • Cost

    savings — fieldwork is expensive; room for huge savings • Reliability — critical data can’t be wrong, costs incurred with unreliable inputs or systems • Speed — decisions can’t be made without the data in hand! • Compliance — proof of work, audit history • No duplication of effort
  10. field data automation ✦ fulcrumapp.com/gispro2016 Historic challenges • Error-prone —

    handwritten, hard to QC, clunky • Time-consuming — lots of duplication, revisits to fix mistakes and fill gaps • Delays — reporting + aggregation takes days or weeks • Difficult to integrate — needs transcription / cleanup
  11. field data automation ✦ fulcrumapp.com/gispro2016 Start at the beginning •

    What questions need answering? • What data do I need to get those answers? • Who are the stakeholders? • How will we get the needed info?
  12. field data automation ✦ fulcrumapp.com/gispro2016 Easy pitfalls • Overengineering •

    Minimize the “nice to haves” • KISS • YAGNI — “you aren’t gonna need it”
  13. field data automation ✦ fulcrumapp.com/gispro2016 • JIFX field experiments —

    Camp Roberts, CA • Goal: Field test technologies / tools for disaster relief scenarios • Work with FEMA to field test mobile tools for damage assessment data capture
  14. field data automation ✦ fulcrumapp.com/gispro2016 Automation = the removal of

    friction “Alexa, get me an Uber” Tap a button → Perform an action
  15. field data automation ✦ fulcrumapp.com/gispro2016 Common sources of friction •

    Technology — tools are too complicated, systems over-designed, “solution looking for a problem” • Work — complexity of the work, steps in the workflow • Human factors — compliance, need-to-know, organizational silos
  16. field data automation ✦ fulcrumapp.com/gispro2016 It’s not all bad, but

    should reduce what we can control There is always some friction in the workflow
  17. field data automation ✦ fulcrumapp.com/gispro2016 Iteration • Incremental reflection +

    improvement to reduce friction • Look at whole workflow, seek frictions, test new methods to reduce, re-deploy, re-test • Scrum!
  18. field data automation ✦ fulcrumapp.com/gispro2016 Some samples of what this

    looks like • Autofilling data • Real-time QA • StreetView integration • Capturing weather data
  19. field data automation ✦ fulcrumapp.com/gispro2016 QA settings read-only data fields

    required for submission validation if-this-then-that conditions
  20. field data automation ✦ fulcrumapp.com/gispro2016 Future capabilities • Workflow —

    triggers / actions, “if this, then that” • Dispatch / scheduling • On-demand metrics + reporting zapier.com ifttt.com workflow.is
  21. field data automation ✦ fulcrumapp.com/gispro2016 Automation in action • A

    few diverse examples: • Comcast — telecom • HALO Trust — humanitarian aid • Desert Channels — wildlife • Century Engineering — civil engineering