CHICKEN OR EGG? STREAMLINING PROCESSES & IMPLEMENTING TECHNOLOGIES

1. CHICKEN OR EGG? STREAMLINING PROCESSES & IMPLEMENTING TECHNOLOGIES

2. EXAMPLE ‘STREAMLINING’ APPLICATIONS… • Back Office: P&I, Customer Service, Utilities, Billing, Code, Etc. • Web Portals for Citizens • Online Permit & Inspection Management • Electronic Plan Management & Document Management • GIS (Geographic Information Systems) • Mobile Inspection, Service, and Damage Assessment • Mobile Inspection, Service, and Damage Assessment

3. 30% USE MOBILE 29% USE MOBILE TECHNOLOGIES TECHNOLOGIES 2005 ‘ALLIANCE’ SURVEY 2006 ‘TOP 100’ SURVEY CASE IN POINT: MOBILE TECHNOLOGIES… • Top 100 Juri’s by Population • Direct calling campaign with 80% response • Sat level LOW without Streamlining • Sat level HIGH when Reengineered • 101 Respond out of ~5000 Juri’s nationwide • Spread was large & small jurisdictions

4. DOCUMENT PROCESS & CONSTRAINTS… Calls Field & Manual Itinerary Generation Manual Review, Validation, and Data Entry Handwritten Paper Forms Manual Entry Delivered into Office

5. FINDING YOUR ‘CRITICAL POINTS’… • Every Procedure or Process has various internal and external factors that impact it. They also have opportunities for improvement or streamlining. • Find the CRITICAL POINT(S) that generate the most return and implement technologies that exploit those points! Visual exam & Collection of Results, Violations, Etc. Data Entry into Permitting Systems Routing & Mapping to Inspection Location

6. PROCESS MARRIES TECHNOLOGY… • Target Technologies to Processes • Hone in on Critical Points • Use built-in Best Practices

7. APPLYING THE PROCESS: THE LA BASIN PROJECT… • DISASTER PREPAREDNESS / DAMAGE ASSESSMENT • ~10 Jurisdictions with OES & OHS support • Using many different procedures & systems • Evaluate feasibility to share resources & technology • Pilot Project to demonstrate cross-juri technology

8. Impact of Successful Streamlining on Technology • Assumptions: • Software is an enabler, not the solution in itself • Streamline efforts need to include the technology options • Business goals have to be established • Planning, planning, planning

9. Impact and Potential Benefits • Potential to establish jurisdictional priorities and goals • “Knit” together disparate departments (i.e. Planning with permitting, neighborhood enforcement, field operations, etc.) • Allow “universal” views of data • Establish “jurisdictional” metrics, as well as departmental • Solutions can be used for multi-jurisdictional comparisons (how are we doing compared to other like entities?) • Standardization will enable solutions to be designed and deployed in a more efficient manner (i.e. Universal code library, planning condition libraries, template use, etc.) • Enable technology to be used for Cross-Jurisdictional education and outreach • Possibly enable better technology procurement capabilities (i.e. Multi-jurisdictional purchasing power, Regional clout, etc.)

10. CONCLUSIONS… • Reach out to all STAKEHOLDERS and INVOLVE them • Target some EARLY WINS that can create momentum • Document the PROCESS and CONSTRAINTS first • Identify CRITICAL POINT(S) and core requirements • Seek out built-in BEST PRACTICES in the technology solutions • Implement STREAMLINED PROCEDURES alongside TECHNOLOGIES and understand how the technology will achieve your goals • Be CREATIVE and OPEN MINDED throughout the process

11. QUESTION & ANSWER JEFF EIBERGER & BOB BENSTEADJEFF.EIBERGER@MOBILEHWY.COMBOB.BENSTEAD@HANSEN.COM

12. ABOUT MOBILEHWY… • Enterprise Mobile Solution Provider • Customers using Hansen, Kiva, Tidemark, HTE, Perconti, Posse, Etc. • Based in Charlotte, North Carolina • Delivering mobile solutions for 6 years

13. REPRESENTATIVE CUSTOMERS…