Maryland Broadband Mapping Initiative: Year 2 Team Meeting

1. Maryland Broadband Mapping Initiative: Year 2 Team Meeting Data Collection, Integration, Verification, and Display

2. Develop: Provider Data • Gather data at the address level • Develop language to encourage address level data from providers • Propose “destruction” of address level data after processing? • Send maps to providers with January data request • Collect data from Resellers • Method for identifying resellers • Develop language to encourage participation of resellers • Submit data in a single geodatabase format, maintaining the integrity of the NSGIC data model • Include Data Package and Whitepaper • Include provider maps in Whitepaper summary • Data Package must be ready two days before delivery (March 29, 2011) • Offer technical assistance to small providers • Over the phone/in office assistance to help gather data • Technical help by processing queries so they don’t have to use InfoUSA

3. Develop: CAI Data • CAI collection summary as a starting point, where do we go from here? • Define the target for CAI in MD • Map CAI on the website • Incentives to participants? • WIFM (what’s in it for me) • Access to data by participant? • Target maps with % complete by County (WA Site) • Meeting with DoIT Preparation • Alignment with BTOP work • Crowd-sourcing tool for CAI (see application slide)

4. Integration: Wireline • Create a more formal provider feedback loop • Receive data • Send thank you/response email, review format/table for errors • Request additional information if necessary • Process data • Send map (within 10 days) to provider and request confirmation of service area • Schedule for wired verification • All verification tests completed by March 18, 2011

5. Integration: Wireless • Considerations to the approach for future project years: • Redefine sampling points • Continuation of QOS software • Determine new criteria for sampling: Only areas which did not have broadband in previous years, areas where providers have reported new coverage data, plus areas defined by weak sample results, sample every point again, • Consider ongoing verification beyond year 2? • Consider ongoing verification of new coverage data only assuming all previously sampled areas with coverage have not changed. • Schedule for wireless verification: • April-May process improvements and development • June-Aug data verification implementation

6. Display: Application Updates 1 • Banner update (DoIT request) • Multiple address comparison capabilities • Panel text update (getting started) • How can we support Adoption • Demographic info • Business application support • Providers by business only • Business Zoning mapping, population density, land use density, DEM data for providers • Updates • Stagger functionality updates with data updates

7. Display: Application Updates 2 • Free Wi-Fi • Confirm the Why? • to show where access exists • Do we need to Validate, Verify, and Maintain • Duration of these activities over contract period • Begin with larger chains (SB, MD, Panera) • Crowd source application verified by another crowd sources application…..asking is this location real • Site allowing business to update/upload business info • Access to info about business such as Google map rollover • Leverage current sites that have this information, don’t reinvent the wheel • http://www.Wififreesource.com • http://www.wi-fihotspotlist.com/

8. Display: Application Updates 3 • ETL tool • Can we Update, Verify, data collection and updates via website? • Provider • Option: Providers would input data via website with a login Admin process with logins for security • ETL takes the data—input into the data model • Verify the data • Provide geocode map of address or census block • Option: Automate the process at MDBC—a slightly manual provider feedback loop • minimized providers who won’t/can’t use tool • Duration of access for updates : constant or specified times (quarterly/biannual) • Pilot with providers • Consideration? • CAI • Updates? • How long are we collecting and updating

9. Display: Data Service Creation • Process discussion • IMap process • Technical team communication—Wiki

10. Display: Website Enhancements 1 • Make the website more dynamic • Aspects of the site that can be refreshed on a regular basis • Centralize news/info for BB in the state • Current news feeds about BB in the state (news aggregators) • What does all this mean—digest the info • Blogging, vetting process can’t be too cumbersome • Area to describe what we are doing technically • Data • Processes used • Wireless • Give some justification for the work being done • Stimulus money working for the state on a daily basis • Text based search for providers http://pages.towson.edu/jparfitt/mobile/mobile.html • Works on mobile devices • List of bb providers • Search by address • What service providers at my location

11. Display: Website Enhancements 2 • Provider tab • Information for providers (updates) • Other info to share on a regular basis • Integrate planning activities (Beacon work) • Capacity building components • Update schedule • Content review every 6-months • Review other state site (incorporate this as a practice) • Dynamic update schedule

12. Promotional Support • Website • Offer signup option for users to receive emails from MBBMI • Events/Meetings • Which events • Press releases • Duration • Advertising • Utility companies • CAI-library newsletters • Community associations • Face book fan page/twitter account (support news stream activities)

13. Address File Development • What are other states doing? • How will Numbers board funding assist in this task? • When is this funding and activities too late? • Will this info be publicly available?

14. State Broadband Capacity Building CGIS/ESRGC/MdBC Support • Yes • Yes • No • Yes* • No • Yes* • No • Yes • Yes* Outcomes • Promotion of efforts • Website content expansion • Coordination • Adoption of BB • Participate in dissemination activities DoIT Actions • Develop a strategic broadband plan • Collect state and local benchmark data • Provide leadership at the State level • Identify and assess existing programs within Maryland that support broadband growth, adoption, and integration within communities • Ensure that efforts to promote and expand broadband availability and adoption are integrated with strategic IT master plan • Support local governments in developing broadband strategic plans • Provide leadership for State agencies to reach out to their constituents and stakeholders to improve access to and adoption • Provide leadership in working with CAIs to gain an understanding of their immediate and long-term broadband needs • Conduct statewide and regional events to disseminate the vision