1 / 35

Statewide Interoperability Executive Committee (SIEC)

Statewide Interoperability Executive Committee (SIEC). All documents presented during the meeting are available online: http://www.in.gov/ipsc/files/meeting_documents.pdf. AGENDA. Call to Order Introductions – Welcome new members Old business/SIEC Structure and Process

kirti
Download Presentation

Statewide Interoperability Executive Committee (SIEC)

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. Statewide Interoperability Executive Committee (SIEC) All documents presented during the meeting are available online: http://www.in.gov/ipsc/files/meeting_documents.pdf

  2. AGENDA • Call to Order • Introductions – Welcome new members • Old business/SIEC Structure and Process • Indiana Statewide Communications Interoperability Plan (SCIP) • Grants • System Update/Migration • NECP Update • Statewide Interoperable Communications Conference • Other (Future Discussions) • Adjourn

  3. SIEC Structure & Process SAMPLE Mission Statement The Indiana Statewide Interoperability Executive Committee (SIEC) serves as an advisory committee to the Integrated Public Safety Commission. Membership is comprised of one representative from each of the ten Homeland Security agencies as well as members from key state and local jurisdictions. The SIEC’s primary mission is to facilitate the flow of information between local agencies and to develop and recommend policy and best practices for statewide interoperable communications. The SIEC membership jointly reviews communications plans and policy recommendations brought forth from District Communications Advisory Boards and offers recommendations and/or alternatives as deemed appropriate to the IPSC. The Chair, Vice Chair, or designee shall make a formal Committee report of activity to the IPSC semi-annually. Meeting Schedule SIEC meetings are scheduled to occur (bi-monthly?). General meetings are held via conference call, with two (2) face-to-face meetings each year. The SIEC’s meeting schedule is subject to change based upon the work and needs of the IPSC as well as local/district needs. Meetings are conducted in accordance with Indiana open meeting laws(citation). Following each session, meeting notes will be made publicly available.

  4. SIEC Structure & Process Meeting Frequency? Possibilities - • Every two months via conference call • Face-to-face three times a year 1. Annual Conference 2. Northern part of state 3. Southern part of state

  5. SIEC Structure & Process • In order to keep flow of communication going, regular, brief reports of interoperable communications activities in each district. • Form provided to make reporting as painless as possible. • Twice a year? • SIEC member responsible for submitting, but can assign someone else to do it. • Summaries will be presented to IPSC and will also be used in annual SCIP Implementation Report. Reporting Process – District Summaries

  6. Indiana Statewide Communications Interoperability Plan (SCIP) • Original SCIP written and submitted in 2007. • 40 Initiatives across 5 Interoperability Continuum “Lanes” • Implementation Reports Due each year – used to assess progress on defined state goals and national requirements • 2010 Implementation Report due September 30 - must contain plan for assessing National Emergency Communications Plan (NECP) Goal 2…more on this later

  7. Grants Public Safety Interoperable Communications (PSIC) Grant Projects: • CASM - $120,628 • 1st Statewide Conference - $98,000 • InData - $1.9 million • Infrastructure - 7 sites – $3.36 million • Radios (5341) - $11.4 million • CTC Training Lab - $201,000 • STR Cache radios - $210,000 • Mobile Site (MIRS) - $648,407 • $94,800 balance Completed On hold per Gov. • Completed • Completed • $100,000 balance Completed • Completed minus tow

  8. Grants 2008 IECGP • Counties MOU’d $$$ back to state for CASM completion help with Technical Interoperability Plans (TICPs) • IDHS divided investment into two projects – dubbed them “Alpha” – CASM and “Beta” - TICPs • Complicated vendor procurement process – Haverstick is “Alpha” vendor, Crowe as “Beta” vendor • Expect contact from vendors in next few months • Approximately $10,000 left for district meetings

  9. Grants 2009 IECGP • Training - $347,000 (IDHS) • Statewide Conference (2 years) $200,000 • District Meetings - $9,650 • Infrastructure -Warrick Co. Site - $154,500 (completed) • MPSCC - $10,000

  10. Grants American Recovery & Reinvestment Act (ARRA) • $4 million for a multi-agency multi-jurisdiction interoperable Computer Aided Dispatch/Records Management System (CAD/RMS). Implementation based upon the highly successful buildout of SAFE-T • State provides the “backbone” for CAD/RMS, including implementation and maintenance. • Local agencies may purchase from established QPA, saving significant dollars on software, hardware & long term maintenance expenses. • End result fosters cooperation, common architecture, and data interoperability. • IPSC is currently implementing the first phase of the project by integrating the Indiana State Police consolidated dispatch center at Bloomington. Following successful implementation of the ISP Bloomington Region, system will be made available to state and local public safety agencies.

  11. Grants Other Office of Emergency Communications/ Interoperable Communications Technical Assistance Program (OEC/ICTAP) has provided SCIP workshops, SOP workshops, COML training Fire Grants

  12. System Update/Migration June 2010  Number of sites = 137* Device Addresses = 54,778   Group Calls = 11,773,221 Group Busies = 35,624 Channel Availability = 97.93% System Availability = 99.96%

  13. Scenario One

  14. Scenario Two

  15. Phase I Project Implementation Timeline Subsequent to contract signing, IPSC envisions a 20 month deployment of Phase I. The following project milestones are provided to help better understand the processes envisioned for completion of Phase I North Zone. • Notice to Proceed with RFP Day One • Write and publish RFP Day 60-90 • RFP Evaluation and vendor selection Day 90 -120 days • Contract Negotiations Day 120 - 170 • Detail Design Review Day 170 - 220 • Equipment Order, staging and factory acceptance Day 220 - 280 day • Master site preparation – Core Controller delivery Day 270 - 300 • Upgrade of selected radio sites to assure acceptance testing results Day 270 - 300 • Installation of Core Controller- testing, evaluation Day 300 - 330 days All of the above activities must be completed before the migration of radio sites begins.

  16. National Emergency Communications Plan • The NECP is a strategic plan delivered to Congress by Federal Homeland Security in July 2008 as a plan for improving: • • Interoperability • • Operability • • Continuity of Communications • The Plan is built around: • • 3 Goals that set performance metrics • • 7 Objectives that identify priorities • • 92 milestone activities

  17. National Emergency Communications Plan Goal 1 – By 2010 – 90% of Urban Area Security Initiative Areas (UASIs) within one hour (DONE – Indy 500 race) Goal 2 – By 2011 – 75% of non-UASI jurisdictions within one hour Goal 3 – By 2013 – 75% all jurisdictions re: significant events within three hours

  18. National Emergency Communications Plan GOAL 2 - By 2011, 75 percent of non-UASI jurisdictions are able to demonstrate response level emergency communications within one hour for routine events involving multiple jurisdictions and agencies. Two Evaluation Phases: Capability Data Performance Data

  19. National Emergency Communications Plan • First Phase – Capability Assessment • Self Assessment – every county • Where do we land on the interoperability continuum? • State must include plan for gathering these assessments in the 2010 SCIP Implementation update (due Sept 30)

  20. Capability Data for Goal 2 – What is Measured

  21. National Emergency Communications Plan • Second Phase – Performance • Each county must submit exercise to be used as evaluation (future or occurred after July 2008) • Focuses on 3 key areas- Common Policies & Procedures, Leadership Rules & Responsibilities; Quality and Continuity of Communications • Web-based incident evaluation tool • Evaluations and major capability findings must be included in 2011 SCIP Implementation Report

  22. Indiana’s Strategy for Documenting NECP Goal 2 • Documenting Capabilities • The Integrated Public Safety Commission and Indiana Department of Homeland Security directed grant funds towards helping counties complete agency data entry into the Communications Asset System & Mapping (CASM) tool and subsequently to use this data to create district Technical Interoperable Communications Plans (TICPs). The projects to achieve these goals will be underway in the fall of 2010. The vendor hired to direct the creation of the District TICPs will collect the National Emergency Communications Plan (NECP) required capabilities data during their meetings with county communications/public safety representatives • The Integrated Public Safety Commission (IPSC) will include level capabilities data from the communications portion of the TCA for inclusion in the 2011 Statewide Communications Interoperability Plan (SCIP) Implementation Report.

  23. Indiana’s Strategy for Documenting NECP Goal 2 • Documenting Capabilities Timeline(Estimated) • August, 2010: IPSC/SIEC coordinates with Crowe (vendor) to ensure draft NECP capabilities survey is included in the meetings with counties. • September-November, 2010: Capabilities Collection • November 2010: Federal Office of Homeland Security Office of Emergency Communications (OEC) publishes final capabilities reporting tool. IPSC determines if additional capabilities need to be documented • January 2010: Vendor provides IPSC with county level interoperable communications capability survey data • January - March 2011: Additional capability data collected (if needed) • April - May 2011: IPSC reviews and approves capability data for inclusion in 2011 SCIP Implementation Report • July 2011: Capabilities data included in 2011 SCIP Implementation Report submitted to OEC

  24. Indiana’s Strategy for Documenting NECP Goal 2 • Demonstrating Performance • · Performance will be assessed in each of Indiana’s 84 non-UASI counties • · Each non-UASI county will submit 2 or 3 possible planned events or exercises that will be used to assess their performance. If a county has conducted an event since July 2008, the county may use that event for purposes of demonstrating performance. • · IPSC will compile and publish a list of events or exercises to be assessed statewide (one per county) • · A Point of Contact (POC) for each non-UASI county will be designated by the county to coordinate local efforts • · The Indiana Department of Homeland Security (IDHS) Training & Exercise Division and IPSC will help counties with preplanning for the selected events and exercises • · IPSC/IDHS will observe and/or help with the selected events and exercises • · IPSC/IDHS will conduct after-action sessions with local staff to complete the OEC performance reporting tool • · IPSC will review and approve final performance reports to include in the 2011 SCIP Implementation Report

  25. Indiana’s Strategy for Documenting NECP Goal 2 • Demonstrating Performance Timeline(Estimated) • July 2010: SIEC discusses approach to NECP Goal 2 performance evaluation • August 2010: IPSC approves Indiana’s approach to demonstrating performance towards NECP Goal 2 during their quarterly meeting • September 2010: Indiana strategy documented in 2010 SCIP Implementation Report • September, 2010: NECP Goal 2 Strategy rolled out during the 3rd Annual Indiana Interoperable Communications Conference. SIEC members take lead in identifying county POCs. • November 2010: Counties submit 2 or 3 possible events or exercises for evaluation • November 2010: OEC publishes final performance reporting tool • December 2010: IPSC publishes lists of events or exercises to be assessed • December 2010 –May 2011: Non-UASI counties conduct assessment and after action sessions with PSIC Office • May – June 2011: IPSC reviews and approves assessments for inclusion in 2011 SCIP Implementation Report • July 2011: Performance Assessment data included in 2011 SCIP Implementation Report

  26. 2010 Statewide Interoperable Communications Conference • September 28 & 29 – SIEC members in on 27th for meeting • Amazing keynote speaker – Al Fuentes • Possible agenda topics: NECP, CASM, Narrowbanding • Rebanding; Migration; CAD; Dispatch issues; Training; Earthquake exercise; SOPs; Social Media • Hero Award? • Look for invite in email today and REGISTER!

  27. Other Business • Future Discussions • Training • Communications Leader (COML) program • SOPs • FEMA/Regional Working Group update

  28. Other Business Comments? THANK YOU! Documents available for download: http://www.in.gov/ipsc/files/meeting_documents.pdf

More Related