1 / 11

Ingress Version 2 Launch Meeting and Demo

Ingress Version 2 Launch Meeting and Demo. September 9, 2009. Agenda. Review of Ingress Goals and objectives General issues and opportunities Ingress Version 2 Introduction Why What When v2 BETA demo Other Issues; Open Q&A. Ingress – A Brief History.

jaafar
Download Presentation

Ingress Version 2 Launch Meeting and Demo

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Ingress Version 2Launch Meeting and Demo September 9, 2009

  2. Agenda • Review of Ingress • Goals and objectives • General issues and opportunities • Ingress Version 2 Introduction • Why • What • When • v2 BETA demo • Other Issues; Open Q&A

  3. Ingress – A Brief History • Original challenge – regional access to secure applications • County applications went “live” ~18 months ago • BARS • JILS • ANI • All required shared security model • Ingress Version 1 “live” in October 2007 • Agency Registrars created users, granted access • Single sign-on for county applications • Result: Federated user administration model

  4. Good/Bad Features of Ingress • Good • Single source for regional applications • Single sign-on for applications • Very strong security model • Resonable administration for >4,000 users from >45 agencies • Not so good (a.k.a. Bad) • Limited to three King County applications • Some difficulties with user management • “Opportunities” • LSJ-I “portal” project • Insufficient funding for KCPCA “DIGS” project

  5. Ingress v2 Objectives • Expand on prior concepts • Single consolidated point of access to information • Integrated search capability (expanding JILS) • Further incorporation of information sources • Integrated and consolidated access to data across systems • Query tools to support searches across applications • Applicable inclusion of “public realm” information • Vision: A portal for criminal justice practitioners

  6. Ingress Portal Model (example: iGoogle)

  7. Ingress Model Basic Concepts • Continue to provide access to regional systems • Applications are primary source of data/information • Expand to support new systems (agency/ad hoc) • Provide information at user’s request • User adds and removes information • User decides where the information is on screen • Allow customization to fit individual needs • Users can tailor to fit their operations • Users can tailor to fit their preferences

  8. Timeline & Functionality Release • Phase 1 – Framework and Beta • Portal Framework • Standard Widgets • Bookmarks Widget • Application Launch Widget • External Application Widget • RSS Feed Widgets • Twitter Widgets • Phase II – Full Version 2 • Advanced Widget Administration • Agency Alerts and Notifications • Unified Search • Sending Results • Saving Results Beta Assessment 9/9 – 10/31 Phase 2 11/1 – 1/15? Phase 1 6/1 – 9/3 6/1 7/1 8/1 9/1 11/1 12/1 1/1 10/1 • Bookmarks Widget may include: • PAO Online Victim Assistance and Abuse Information • Public Defense Services • Court Jury Information • State AMBER Alerts • Application Launch Widgets may include • Booking and Referral System (BARS) • Jail Inmate Lookup System (JILS) • AFIS Name Index (ANI) • External Applications Widget may include: • DJA ECR Online System • King County Sex Offender Search • RAIN • LInX

  9. v2 BETA Demo

  10. What’s Next • Agency use of “Beta” • All agency users are “loaded” into Beta now • We are NOT reconciling logons between Ingress versions • Beta will improve over next two months • Addition and improvement of how applications are presented in widgets • Addition of new “widgets” • Looking for user feedback!!! • Future transition to v2 • At this time, users may use EITHER v1 or v2 Beta • Recommend doing an agency training and conversion • When v2 goes “live” (dates TBD) we will work with agencies to reconcile user accounts • At that time, agencies will have 30 days to transition users

  11. Q&A

More Related