Emergency Interoperability Consortium Enhancing EIC Marketing and Value

Emergency Interoperability Consortium Enhancing EIC Marketing and Value Steve Streetman Member of the Board

Overview § The Consortium needs to do a better job of representing its members to the community – More and more regular contact with Federal, state, and local groups that care (or should care) about interoperability – Provide competitive advantages in the marketplace to EIC members § Suggestions – Email marketing campaign – Enhanced website – Interoperability maturity model 2

Email Marketing Campaign § Use a standard email marketing service (e. g. Constant Contact) – Service manages forwards, subscribes and unsubscribes and ensures email is not identified as spam – Service provides templates and widgets to make email look professional and allow rich content (pictures, video, logos, links) § Members provide content – Opportunity to show off interoperability capabilities and activities – As email list grows, provides increased access to decision-makers § First newsletter planned for early April 3

Enhanced Website § Many possibilities for improving the website – Library of papers, standards, etc. for interoperability – Company profiles of EIC members – Calendar of interoperability events – Interoperability news items – Members-only section with extra content § Interoperability program information / bidding opportunities § Matchmaking area where EIC members could post profiles and look for teammates § Interoperability blog – Newsletter archives 4

Interoperability Maturity Model § Many professions are taking the opportunity to further define professional requirements. There is the Capability Maturity Model (software). There is, under development a risk analysis maturity model. We could do an Interoperability Maturity Model – Further defines levels of interoperability and sets requirements that could be leveraged by program managers – Allows for EIC members to be certified to interoperability levels – Promotes an industry-wide discussion of just what interoperability really means – EIC could manage model standards and requirements Draft / Notional Model Level Data Connectivity Permissions 1 Sends/receives CAP Common frequencies / internet Manages permissions locally 2 Implements OASIS / OGC / NIEM stds. Voice/data on common links Hierarchical authentication management 3 All data standardized Redundant common comms capabilities Peer-to-peer rolebased authentication 5