Transcript Statewide Interoperability Executive Committee (SIEC) All documents presented during the meeting are available online: http://www.in.gov/ipsc/files/meeting_ documents.pdf Indiana Statewide Interoperability Executive Committee Meeting July 29, 2010

Statewide Interoperability Executive Committee (SIEC)
All documents presented during the
meeting are available online:
http://www.in.gov/ipsc/files/meeting_
documents.pdf
Indiana Statewide Interoperability Executive Committee Meeting
July 29, 2010
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
Indiana Statewide Interoperability Executive Committee Meeting
July 29, 2010
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.
Indiana Statewide Interoperability Executive Committee Meeting
July 29, 2010
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
Indiana Statewide Interoperability Executive Committee Meeting
July 29, 2010
SIEC Structure & Process
Reporting Process – District Summaries





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.
Indiana Statewide Interoperability Executive Committee Meeting
July 29, 2010
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
Indiana Statewide Interoperability Executive Committee Meeting
July 29, 2010
GOVERNANCE Initiatives
Initiative
Status
Request an investment of $1.4 million to directly supply local responders with 800 MHz radios
Complete
SCIP Initiative 5.1.1: Formalize Interoperability Coordinator.
SCIP Initiative 5.1.2: Establish data interoperability governance structure (INData) and planning
framework to develop policy for data integration, establish data architecture policy, and begin to
integrate various public safety/criminal justice data sha
Complete
In Progress
SCIP Initiative 5.1.3: Formalize Wireless Communications Policy Academy Executive Committee as
Statewide Interoperability Executive Committee (SIEC)
Establish common values
SCIP Initiative 5.5.4: Renew Midwest Public Safety Communications Consortium (MPSCC).
SCIP Initiative 5.5.5: Establish statewide and district user groups to facilitate implementation of the
SCIP.
Complete
Not Started
In Progress
In Progress
SCIP Initiative 5.5.9: Expand involvement of NGOs, private sector, and amateur radio entities in the
SAFE-T (Safety Action for Everyone – Together) system.
SCIP Initiative 5.6.1: Leverage grant writing resources for locals
Complete
In Process
Conduct a full SCIP review to update the plan
In progress
SOP Initiatives
Initiative
SCIP Initiative 5.3.1: Establish an online repository for SOPs
Status
Complete
SCIP Initiative 5.3.2: Hold discussions with the United States Coast Guard to develop
interoperable communications scenarios that will support operations Statewide.
Not Started
SCIP Initiative 5.5.1: Create a Common Language Task Force to research and implement a
common language protocol with the input of local first responders
In Progress
SCIP Initiative 5.5.3: Use County Communications Plans to identify gaps and to ensure NIMS
compliance
In Progress
SCIP Initiative 5.5.8: Maximize Amateur Radio User Community by continuing to expand
integration of radio amateur technology partners with public safety interoperable
communications and arrive at a set of recommended common standards and protocols for all
RACES Teams throughout the State
In Progress
Establish interoperable communications SOPs that direct inter-agency communications
response, use of statewide and regional interoperable communications talkgroups, and gateway
patching solutions
In Progress
Hold district meetings to share/develop SOPs
In Progress
Create County Communications Plans
In Progress
TECHNOLOGY Initiatives
Initiative
SCIP Initiative 5.2.1: Formalize strategy for Public Safety Interoperable Communications (PSIC) Grant Program initiatives
SCIP Initiative 5.5.7: Implement a web-based content management system
Expand the number of channels at 10 sites in three central Indiana counties: Boone, Hendricks, and Johnson
800 MHz Rebanding: Assess approximately 50,000 SAFE-T radios to determine whether they must be retuned, reprogrammed,
or replaced in order to operate using the newly allocated frequency pairs
Target PSIC funds towards radios
SCIP Initiative 5.2.2: Develop INData Plan for statewide data information sharing network and coordination
SCIP Initiative 5.5.2: Facilitate for the migration to the SAFE-T system by providing grants available to offset the cost of new
radios
SCIP Initiative 5.5.6: Use the Communications Assets Survey and Mapping (CASM) tool to conduct an updated and actual
portrait of the current systems in use across the State
Purchase and distribute Broadband Global Area Network (BGAN) satellite Internet Protocol (IP) based units capable of
supporting both IP phones and wireless internet. Purchase and implement two Cisco “Office in a Box” units and two 1.2 meter
satellite dishes.
Build seven additional sites for SAFE-T to provide concentrated coverage improvements throughout the State (5 of 7 complete, 2
on-going)
Make investment in a second mobile Intelli-repeater (MIRS)
Advance data communications interoperability between the State Emergency Operations Center (EOC) and its 92 counties via
WebEOC
Upgrade 800 MHz subscriber and infrastructure equipment and technology for long-term users of the statewide SAFE-T radio
system Project 25 (P25).
Make surplus equipment, resulting from upgrades by long-term users of SAFE-T, available for bid to public safety agencies not
yet operating on the statewide platform
Invest in increased capacity for the microwave network
800 MHz Rebanding: Assess system infrastructure equipment for each of the communications in order to operate using the
newly allocated frequency pairs
Define wireless approaches that include use of 700 MHz through INData for voice and data
Upgrade Hoosier SAFE-T infrastructure to standards based system
Comply with NDEX (National Data Exchange) NEIM (National Emergency Information Management) standards
Status
Complete
Complete
Compete
Compete
Compete
In Progress
Complete
In Progress
Complete
Complete
Complete
In Progress
In Progress
Complete
In Progress
In Progress
In Process
In Progress
In Progress
TRAINING Initiatives
Initiative
Status
SCIP Initiative 5.4.1: Develop web-based training and certification program to help Hoosier first
responders use communications equipment more effectively
In Progress
SCIP Initiative 5.4.1: Carry out regional, interagency, cross-discipline interoperability exercises
to assess interoperability
In Progress
Leverage IDHS’s Training Program
In Progress
Develop and deliver a communications train–the-trainer course
In progress
USAGE Initiatives
Initiative
Status
SCIP Initiative 5.5.3: Establish statewide requirement for NIMS compliance
Complete
SCIP Initiative 5.5.10: Conduct an annual Interoperability Conference including NGOs
Complete
Test the entire statewide network first Wednesday of the month–expand to all users
On going
Conduct monthly test among all IDHS users of satellite radios/telephones and other agency
users
Taking place every
month
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
Indiana Statewide Interoperability Executive Committee Meeting
July 29, 2010
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

Indiana Statewide Interoperability Executive Committee Meeting
July 29, 2010
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
Indiana Statewide Interoperability Executive Committee Meeting
July 29, 2010
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.
Indiana Statewide Interoperability Executive Committee Meeting
July 29, 2010
Grants
Other
Office of Emergency Communications/ Interoperable
Communications Technical Assistance Program (OEC/ICTAP)
has provided SCIP workshops, SOP workshops, COML
training
Fire Grants
Indiana Statewide Interoperability Executive Committee Meeting
July 29, 2010
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%
Indiana Statewide Interoperability Executive Committee Meeting
July 29, 2010
SAFE-T P25 Migration Plan
Wireline Gold
Elite Consoles
1.
2.
3.
4.
5.
6.
Replace 4.1 Controller
with P25 core/controller
Device to interface Gold
Elite console to P25
core/controller
Add P25 coverage
(regional or overlay)
Interoperability by
patching talkgroups
between systems –
during the migration
Migration of 4.1 sites to
P25 through phase
implementation
Core Controllers North
Zone and South Zone
AEB
Existing (4)SAFET 4.1 Master Site
Controller
(2)Future P 25
N/S Core
Controllers
Existing SAFE-T
Sites
P25 Sites
SZ Radio
PD-1 TG
Scenario One
P25 Radio
PD-1 TG
Scenario Two
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.
Indiana Statewide Interoperability Executive Committee Meeting
July 29, 2010
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
Indiana Statewide Interoperability Executive Committee Meeting
July 29, 2010
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
Indiana Statewide Interoperability Executive Committee Meeting
July 29, 2010
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
Indiana Statewide Interoperability Executive Committee Meeting
July 29, 2010
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)
•
Indiana Statewide Interoperability Executive Committee Meeting
July 29, 2010
Capability Data for Goal 2 – What is Measured
Capability
Early Implementation
Intermediate Implementation
Established Implementation
Advanced Implementation
Governance
Urban Area/Countywide/ Tribal decisionmaking groups are informal and do not yet
have a strategic plan to guide collective
communications interoperability goals and
funding.
Some formal agreements exist and informal
agreements are in practice among members of
a(n) Urban Area/ countywide/ tribaldecisionmaking group; Urban Area/ countywide/ tribal
strategic and budget planning process are
beginning to be put in place.
Formal agreements outline the roles and
responsibilities of a(n) Urban Area/
countywide/ tribaldecision-making group,
which has an agreed upon strategic plan that
addresses sustainable funding for collective,
regional interoperable communications needs.
Urban Area/ Countywide/tribal decisionmaking bodies proactively look to expand
membership to ensure representation from
broad public support disciplines and other
levels of government, while updating their
agreements and strategic plan on a regular
basis.
SOP
Urban Area/Countywide/ Tribal
interoperable communications SOPs are not
developed or have not been formalized and
disseminated.
Some interoperable communications SOPs exist
within the Urban Area/ county/tribal community
and steps have been taken to institute these
interoperability procedures among some
agencies.
Interoperable communications SOPs are
formalized and in use by all agencies within the
Urban Area/county/tribal community. Despite
minor issues, SOPs are successfully used during
responses and/or exercise(s).
Interoperable communications SOPs within
the Urban Area/county/tribal community
are formalized and regularly reviewed.
Additionally, NIMS procedures are well
established among all agencies and
disciplines. All needed procedures are
effectively utilized during responses and/or
exercises(s).
Technology
Interoperability within the Urban
Area/county/tribal community is primarily
achieved through the use of gateways
(mobile/fixed gateway, console patch) or use
of a radio cache.
Interoperability within the Urban
Area/county/tribal community is primarily
achieved through the use of shared channels or
talk groups.
Interoperability within the Urban
Area/county/tribal community is primarily
achieved through the use of a proprietary
shared system.
Interoperability within the Urban
Area/county/tribal community is primarily
achieved through the use of standardsbased shared system (e.g., Project 25).
Training &
Exercises
Urban Area/Countywide/ tribal community
public safety agencies participate in
communications interoperability workshops,
but no formal training or exercises are
focused on emergency communications.
Some public safety agencies within the Urban
Area/ county/tribal community hold
communications interoperability training on
equipment and conduct exercises, although not
on a regular cycle.
Public safety agencies within the Urban Area/
county/ tribalparticipate in equipment and
SOP training for communications
interoperability and hold exercises on a regular
basis.
Urban Area/county/tribal community public
safety agencies regularly conduct training
and exercises with communications
interoperability curriculum that is modified
as needed to address the changing
operational environment.
Usage
First responders across the Urban
Area/county/tribal communityseldom use
solutions unless advanced planning is
possible (e.g., special event).
First responders across the Urban
Area/county/tribal community use
interoperability solutions regularly for
emergency events, and in limited fashion for
day-to-day communications.
First responders across the Urban
Area/county/tribal community use
interoperability solutions regularly and easily
for all day-to-day, task force, and mutual aid
events.
Regular use of solutions for all day-to-day
and out-of-the-ordinary events across the
Urban Area/county/tribal community on
demand, in real time, when needed, as
authorized.
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
•
Indiana Statewide Interoperability Executive Committee Meeting
July 29, 2010
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.
Indiana Statewide Interoperability Executive Committee Meeting
July 29, 2010
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
Indiana Statewide Interoperability Executive Committee Meeting
July 29, 2010
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
Indiana Statewide Interoperability Executive Committee Meeting
July 29, 2010
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
Indiana Statewide Interoperability Executive Committee Meeting
July 29, 2010
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!
Indiana Statewide Interoperability Executive Committee Meeting
July 29, 2010
Other Business
Future Discussions
•
Training
•
Communications Leader (COML) program
•
SOPs
•
FEMA/Regional Working Group update
Indiana Statewide Interoperability Executive Committee Meeting
July 29, 2010
Other Business
Comments?
THANK YOU!
Documents available for download:
http://www.in.gov/ipsc/files/meeting_documents.pdf
Indiana Statewide Interoperability Executive Committee Meeting
July 29, 2010