MASAS Meeting

Final Report of the MASAS 2011 National Stakeholders Workshop









Multi-Agency Situational Awareness System (MASAS) - “Operationalizing MASAS”

National Stakeholders Workshop, March 1st & 2nd, 2011

Government Conference Centre, Gatineau Room, 4th Floor, 2 Rideau Street

Ottawa, Ontario







This report documents the proceedings of the March 1-2, 2011 MASAS Workshop held in Ottawa.



The workshop was organized by GeoConnections to bring together various stakeholders of the Multi-

Agency Situational Awareness System to deliver on the following objectives:



Workshop Objectives:

 Hear about real challenges and solutions to situational awareness from first responders;

 To present a current status and overview of the MASAS and how it can assist your

organization;

 To seek input and formulate options with stakeholders on how the national MASAS evolves;

 To seek input from stakeholders and explore options for governance and sustainability of

MASAS;

 Present opportunities on how to get involved and connect to the system.



The national Multi-Agency Situational Awareness System initiative has established an innovative

approach and technical solution for sharing authoritative location-based situational awareness

information, in near real time, within Canada’s emergency management community, and across the

border with our American colleagues. The MASAS initiative is under the sponsorship of Natural

Resources Canada (GeoConnections) and the Centre for Security Science with collaboration from

Public Safety Canada.



The attached table summarizes the comments, questions, ideas and recommendations gathered

during the workshop. Annexes have been included to provide insight for the reader on the actual

presentations and comments (notes tables) that were made during the workshop.





Summary Recommendations

As an overview, the following are summary highlights of the various recommendations that surfaced

during the many exchanges that took place through the facilitated process. Some are expressed

directly; others result from a review of the essence of the comments recorded. There is no particular

order of priority. Recommendations have been regrouped under the following themes:



Governance

 Plan to meet the Fall 2011 target of Public Safety Canada – governance and structure (on time

and within budget)

 Establish a steering committee to ensure focused and strategic development (3-6 months)

Prepared by MCO Business Group Rev. 1 March 22, 2011 Page 1 of 29

Final Report of the MASAS 2011 National Stakeholders Workshop





 Institute a Standard Operating Practices Working Group that will have mandate to review and

integrate operating practices in MASAS

 Define roles and responsibilities for governance

 Develop a Return On Investment (ROI) process to establish the true financial benefits of

MASAS

 Involve private sector stakeholders in all aspects of the operationalization of MASAS



Policies

 Develop policies that streamline the application and limit scope crawl

 Develop policies, a framework and a scope that covers all levels of government – federal,

provincial, municipal, communities

 Information security parameters must be defined to apply adequate and effective filters –

sensitive and non-sensitive information; restricted and non-restricted information

 A pan-Canadian policy on information protection and security is required



Implementation

 Work to maintain the momentum of the March 1-2 workshop

 Stay away from complexity – start small and simple

 Take a pilot project approach – prove the concepts before going national

 Validate tools through pilot tests

 Think in terms of progressive integration. Look for opportunities to expand the application of

MASAS to new areas or domains

 Involve partners/stakeholders who have expertise, experience and knowledge

 Focus on first responders’ needs and input; keep public domain aside at first

 Let information providers determine scope of their filters – limiting access

 Define/determine benefits (tangible and intangible) to provide justification for resource

allocation

 Use a progressive approach to implementation – do not wait until all standards are defined

 Use Best Practices from other proven systems (e.g., Public Health)

 Survey what already works; don’t re-invent the wheel

 Focus on client-driven core platform (municipalities); let individual users define their

respective tool



Design & Technology

 Use existing symbology

 Ensure data integrity through modern firewall technology

 Develop a vendor engagement model to ensure use of best available technology

 Use testing results to guide the design of the permanent systems

 Build planning capability in MASAS along with reactive capability (case studies, event

resolution, outcome history)

 Make extensive use of acquired knowledge (IRCan)

 Make use of existing plug-ins for peripheral modules

 Develop tools aligned to desired outcomes.



Prepared by MCO Business Group Rev. 1 March 22, 2011 Page 2 of 29

Final Report of the MASAS 2011 National Stakeholders Workshop





 Focus on building a core platform that is robust, flexible, integrating specifications of modern

technology (Open Source, Object Design, compatibility with new Social Media technology);

plug-ins to easily and individually attach to the core

 Continue building on NIEM to ensure compatible and workable information exchange

solutions

 Define levels of use and access with respect to security and confidentiality of the information

 Focus on feasible/rewarding areas (capture the low hanging fruits: systems, technology,

people)

 Design scope and framework – can’t be everything to everyone. Focus on the systems with

biggest impact on results



Communications/Information

 Develop communication strategy to explain and demonstrate the benefits and urgency of

implementing MASAS; also its capabilities and limitations, and who it is intended for

 Establish a standard process for: a) application design and development; b) application

updating

 Make it a priority to ask First Responders for input in the design

 Standardize data entry to ensure accuracy and reliability

 Integrate results of workshop into the Capability Gap Assessment (CGA) matrix.

 Issue Capability Gap Assessment document to stakeholders for comments.



These recommendations should be reviewed and prioritized to ensure that the activities requiring

immediate attention are planned and funded to keep the momentum going on the implementation of

MASAS. Best use of resources and existing practices and similar systems expertise will help to

expedite the issues that could unblock the rapid progress of a permanent rollout of this very

promising platform for information exchange for first responders in emergency situations.



General Conclusions



The exchanges during the two day workshop brought out many facts, ideas and information to bring

every stakeholder up to speed as far as progress in the development of MASAS is concerned.



There was general consensus on the need to continue building momentum in the roll-out of the

system of systems. To do so, governance and scope of the project require immediate attention to

define clients (who will you serve?), services (what will be done?), processes (how the services will be

rendered) and structure (partners, stakeholders working together to provide the services).



There was concern on the security of the information shared or not shared and the need to define

how existing barriers (policies, governance, systems, tools) can be worked around.



A strong message emerged with respect to taking an approach that makes use of existing expertise,

knowledge, tools and systems (NIEM, symbology, Public Health system, etc.) so that we don’t re-

invent the wheel.



Prepared by MCO Business Group Rev. 1 March 22, 2011 Page 3 of 29

Final Report of the MASAS 2011 National Stakeholders Workshop









There was general agreement that more work is required to define the benefits associated with

MASAS, and link them to existing operating budgets so that the decision-makers are provided with

justification to make MASAS a high priority.



From an objective point of view, there was a sense that work has already been done (Sarnia, Windsor,

BC, etc.) that points the activities in the right direction. These exercises have also produced

knowledge and expertise which should be put to use in developing a framework and scope for

MASAS. Also, the experience of other systems already in place should be studied to establish best

practices in gathering, storing, managing and communicating information to first responders.



The technology is quite advanced. Make sure to integrate existing technology and make use of

modern day cyberspace tools like social media to enhance the reach of the system of systems. There

is a need to define what access will be included and what information will be disseminated.



Perspective on Governance



Since there is a multitude of partners, stakeholders and identified needs, it would be useful to review

the approach in light of the questions listed in the March 2-3, 2010 workshop report on the Virtual

Canada Capability Roadmap:

 what do participating stakeholders want to achieve through the agreement?

 what will they contribute (money, resources, information, time, equipment, technology, etc.) to the

partnership?

 how will the partnership share information?

 how will the partnership measure progress towards its objectives?

 how will the partnership communicate results to its members and to the public?

 how will the partnership take decisions?



There is a need for a consolidated and normalized approach across the board to ensure the viability,

stability, robustness and usefulness of the MASAS. As participants underlined, without a clear

understanding of who does what, when, how, and why, and with what tools, forward progress will be

difficult.



There was general consensus that the federal government should lead the charge to ensure

uniformity across the board and to make use of existing governance organizational structures already

in place for other significant pan-Canadian projects.



It is paramount to develop a framework and scope for MASAS to allow all partners and stakeholders

to find their niche and focus on what they can contribute in the context of a growing demand for

easily manageable and accessible information in emergency situations. MASAS offers the best

solution to raise situational awareness not only vertically through the various levels of partners and

users, but also horizontally through those levels to make sure different issues regarding the economy,

the environment, the public safety and the planning of future necessary interoperable systems are





Prepared by MCO Business Group Rev. 1 March 22, 2011 Page 4 of 29

Final Report of the MASAS 2011 National Stakeholders Workshop





widely disseminated and included in the day to day and long term decision-making processes that

provide an effective emergency infrastructure for Canadians.



Next Steps

As operationalization of MASAS is nearing, priority actions will be taken to ensure the goal is reached.

During the wrap up, a number of ideas were noted as to what is planned to be done next.

NRCan:

 Report of the March 1-2 workshop to be issued

 Workshop results will be integrated into the Capability Gap Assessment document; it will be

issued and shared with the community of MASAS stakeholders

 The elements of the CGA will be integrated into a broader roadmap – particularly our

technology community will see how we achieve the vision – that will be part of the Business

Plan. GeoConnections will use the input – with funding available – to progress the

operationalization of MASAS

 Governance –within a 3-6 months time frame, a steering committee will be set up to provide

direction on governance and policies around the MASAS

 Communicate to increase awareness of the outreach

 Additional work on the sandbox

 Design and run more exercises; lessons learned, future oriented action and program



Public Safety Canada:

 Public Safety Canada work plan – national MASAS framework – all deliverables in 2011

 SOREM EXECUTIVES clear directives for national roll-out

 Consolidate and synthesize all the information for SOREM

 Filling out the governance model

 Ministers and ADMs expecting completion – this is a winner (Public Safety)

 SCOPE – what MASAS is, is not – priority task; guides everything going forward including

governance – documented and communicated.









Thank You

MCO Business Group appreciates the opportunity to have participated as facilitators in the exchanges

of many stakeholders to design and move forward on the development of a Multi-Agency Situational

Awareness System tool for the benefit of Canadians.





Raymond Perras, facilitator

Louise Gravelle, note taker









Prepared by MCO Business Group Rev. 1 March 22, 2011 Page 5 of 29

Final Report of the MASAS 2011 National Stakeholders Workshop





Contents of Annexes



1. List of attendees

2. Workshop final agenda

3. March 1-2 National Stakeholders Workshop Report Summary (attached to this report)

4. RAW DATA – DAY 1 - tables of presentations, with questions and comments as recorded

5. RAW DATA - DAY 2 tables of presentations, with questions and comments as recorded

(verbatim as much as possible) and group discussions flipcharts

6. All available presentations in PDF format or Powerpoint slides – referenced in the notes and

summaries. The following is a list with the following legend:

Day – segment (am or pm) – Order sequence presentation = 1a1, 1a2, 1a3, etc



Day 1 - AM

1a1 – Sarnia PC&JB Ottawa Presentation.ppt

1a2 – Sarnia Mike Morrow MASAS Workshop Mar 1 2011 – Cross border.ppt

1a3 – Sylvain Latour – MASAS GeoConnections 110301.ppt

1a4 – The Centre for Security Science viewpoint

1a5 – Allport MASAS Workshop Introduction.ppt

1a6 – Becking ODonnell – Business Case.ppt

1a7 – Todd Smith – MASAS Workshop.ppt



Day1 -PM

1p1 – MASAS Status – Ottawa Workshop – KenV1and JackV1.pptx

1p2 – Table 7 afternoon workshop – 01Mar2011.pdf (notes from status discussions)



Day 2 - AM

2a1 – Doug Carnegie – PS-SP-#346321-v1B- Interoperability Dev Office (Word doc)

2a2 – Doug Carnegie – PS-SP-#364009-v3-IDO-Presentation (for MASAS) – Powerpoint

2a3 – Ken Marshall – MASAS Governance.ppt

2a4 – Ken Marshall – MASAS Operational Policies.ppt

2a5 – Mark Sondheim – SymbologyPresentation – March 2011-1.pdf

2a6 – Day2 Facilitated Session.pdf – DarrellO’Donnell’s notes on Governance discussion



Day 2 - PM



2p1 – NEED Michel Savoie – PS-SP-#378792-v1-NIEM-in support of MASAS.ppt

2p2 – Ken Marshall – MASAS VGI Crowd Social.ppt

2p3 – J Potvin IRCan Overview BusinessPurpose....pdf

2p4 – Joseph Potvin – Overview FormFitsFunction...pdf

2p5 – MASAS NIT Master Deck DRafgt 110204.pptx

2p6 – links.pdf (how to find internet based information on MASAS technology)

2p7 – outline of system Jacob.pdf (graphical representation of MASAS)







Prepared by MCO Business Group Rev. 1 March 22, 2011 Page 6 of 29

Multi-Agency Situational Awareness Systems - “Operationalizing MASAS”





*** Day 1 *** National Stakeholders Workshop Report

Agenda Item Presentation Overview Observations/Comments Recommendations

Challenges in Emergency

Management: Experience First Responders speak to what is happening on the ground. They Q. when you mentioned BP head leak – you thought everyone knew MASAS will improve communications –

from the Sarnia-Lambton are believers in the MASAS. MASAS is about information flowing. but no one knew. MASAS – would you consider it a primary source to enabling systems

County Region Getting the data to ground level to decrease the risks associated provide info. Not the only one – when dispatch tones us – enter data Need inter-governmental agreement re:

with incidents on the ground. – feed off to MASAS. Would you expect other services to see this and bring organizations across the border to

 Sarnia/Lambton Region acknowledge that they saw the information?. help out without the constraints

Risk Factors Pat Cayen and Jeff Brooks (Powerpoint Presentation to be added) A. Acknowledge is good but would not rely on that for sole source of imposed by different jurisdictions.

 December 2010 Snow Bluewater Region A Shared Community – Sarnia has relationship information – would expect a call from the agency or organization to

Storm Situational with Lambton County – partner needs to know what’s happening confirm reception and understanding of the event. The exercise in Windsor provides

Awareness Gaps in Sarnia. Border city issue; some information is a challenge for elements for design of MASAS.

 Lessons Learned from first responders. Mutual arrangement with Port Huron, they will Q. at what point do you start being worried about sharing too much Risk is really high. Municipality don’t

MASAS Demo in Cross- man our station when dealing with the incident. Immediate information to too many people. have the funds. As it appears now,

Border Exercise notification is crucial. Sarnia is a main hazmat corridor to Windsor. A. Every user will have to draw that line as to what is being shared – MASAS would be used daily, at our

Slide presentation – community profiles (Sarnia and Lambton will probably be filters in the future – EMS amount of data being desks, vehicles on the beat.

Doug Allport County) shared is very limited due to privacy.

Allport Group If MASAS is to reach its full potential –

Moderator The exercise with MASAS was a wonderful experience! Last week – C. public awareness – filters would be obstructive in what is going out we must pay attention to the needs of

an actual re: BP event going on presently. Input was made into MA – may impact on your response time. the service providers!!

Pat Cayen SAS – in 3 minutes phone was ringing with questions. MARVELOUS! A. if activate Emergency Operations Centre (EOC)... will put

Fire Chief, Sarnia Fire We are a border community – we were able to alert everyone at the information out to the public. Do we want to know that we are going Ultimately we need to meet needs of

Rescue Services same time to a particular address? No – crisis of the family. If something is public awareness.

Issues last week – information released to public was wrong! – happening in the Chemical Valley – the control group decides whether Roles and responsibilities – these need

Jeff Brooks another real opportunity for MASAS for people to receive accurate to send the information out. to be clarified – people want to know all

(A) Manager, information. BP well-head leak – thought everyone knew (police, the information – filters are important.

The County of Lambton paramedics, etc)... NO ONE KNEW!! Not sure where the Q. What is the coordination in Lambton? Flexibility is important.

Emergency Medical Services communication break happened. It demonstrated another clear A. 2 tier approach in Lambton – if we have an event that activates

Department opportunity for MASAS. EOC, we will decide with Industry how serious it is – if outside our MASAS – fundamental tool to be used

border – will notify the other areas as well – EOC in Sarnia – by all – for operational or tactical – it has

Additional on-the-ground case study: Snow- mageddon this winter – operational, Lambton county will take the lead because of the size of to be fundamental, the basis, the core.

huge event. Gaps in who was out dealing with what – EMS - Fire – the area.

police (two different police forces - Sarnia and OPP). Military came As we move forward – filters need to be

in. Same vehicle was checked 4 times by the different agencies!! One person commented that he worked in a lot of EOC - some built into the system for data integrity.

Depending on what force – some on foot, etc. Roads closed – City information you want and may or may not want to share. More than

pulled plows off the road. Became a real issue with tiered response. tracking tactical information. He sees MASAS as overview of what is The ability to predict the requirements

No coordinated response. Response from MTO and City was crucial. happening where – Using our tools to carry out operations. We can related to different types of incident



Prepared by MCO Business Group Rev. 0 March 14, 2011 Page 7 of 29

Multi-Agency Situational Awareness Systems - “Operationalizing MASAS”



*** Day 1 *** National Stakeholders Workshop Report

Agenda Item Presentation Overview Observations/Comments Recommendations

What we would have wanted to know is which roads are open and consume the information feeds and direct it to the interested parties. should be a priority to guide the design

closed so that ambulance can reach the site. For the city, any road Processing and alerting of the information at the Olympics showed of MASAS toward a planning tool.

closures were distributed via mass e-mail – need forum to get it out overview is the better term and not tracking tactical.

to the first responders.

MASAS provides backbone whereby we share the information –

Cross Border Discussions – US did not know what was happening in providing situational overview. Vendor community does not want the

Sarnia with traffic backed up to the US at the Blue Water Bridge.. government to ignore that fact. Vendor has tools – creating the basis

to create the tools.

Information Technology – overview of tools being used currently –

would like to layer into a common tool.

MIKE MORROW (Powerpoint Presentation attached )

Mike Morrow LESSONS LEARNED – if IMS system is being well understood – discover OPPORTUNITIES FOR ADVANCEMENTS –

President, EmerGeo Lessons learned from MASAS Demo in Cross-border Exercise how we are using tools that could create problems. Who does what! (as a VENDOR) – if government levels

City of Windsor, U of Windsor, Essex County Duplication can be a challenge. MASAS can solve this: Mapping. want Industry (tool vendors) to be part

Worked hands on in EMS Contacts. Standard Definitions. Preparation and Education. of this, they need to engage industry in

Intent – leverage what you already have – use MASAS for the the process of developing MASAS .

publishing and distribution of information. Clearly position MASAS – define scope

Fusion point application MASAS running live in the portal – daily and framework. Develop a vendor

dashboard with real time links with border streets. engagement Model.





Facilitated Session A brainstorm of ideas from the group recorded as potential After hearing from the people on the ground, first responders, the - Next steps - need more than vendors

Brainstorm what success directions for guidance in the development of the framework for audience was asked to state their expectations for the workshop: and municipalities; also need

would look like MASAS what would we accomplish if we were successful in our information provincial and federal counterparts to

exchange and discussions? get aligned

- Ensure viability; need full engagement

If we were to be successful in the next two days... from stakeholders

- Understand the backbone basics of the system of systems - MASAS is not a stand-alone system –

- Some of the definitions of the MASAS; Standards; needs alignment with other initiatives

functionality; What it is – what it is not with public safety and facilitate –

- Get a sense of a transition plan to self-sustainability MASAS = a platform that is required

- Others required – power, gas (utilities) – nice to have their - require strategic and targeted

information included in MASAS communication to get buy-in across

- Start seeing the integration and layering into existing systems the board – strategic benefits

- Information clearinghouse – summary statement of desired - Define user group – establish Steering

features Committee



Prepared by MCO Business Group Rev. 0 March 14, 2011 Page 8 of 29

Multi-Agency Situational Awareness Systems - “Operationalizing MASAS”



*** Day 1 *** National Stakeholders Workshop Report

Agenda Item Presentation Overview Observations/Comments Recommendations

- Find out who we are serving etc. - First responders need to be involved

- clarity of roles and responsibilities in the international committee /

- Development of the tracking system concept – extending steering committees which are

beyond our borders developing tools to manage parts of

- Overall boundary definition of the MASAS project and its the emergency management planning.

integration – framework for the project - Account for the fact that there are

- a lot of buy-in in the room – but not the case across the more things to be developed (a lot has

country already been done) – think of the

- good system of ambulance etc. Managing day to day – different generations of the system –

MASAS provides more ... need to include the benefits in the apply a strategy that scopes from day

communications strategy – not as much technical but more in to day to the long term.

how it will bring benefits to the public through better, more

coordinated, effective and efficient situational awareness

- recognize MASAS as a common operating picture (move from

where we are using what already exists)

- identify MASAS as a space where we can share experiences

and lessons so that we can leverage best practices

- National link into the US system – key for where the border is





Executive Panel

Representatives from the three main departments collaborating to implement MASAS at the national level. With the renewal effort in systems,

Natural Resources Canada, looking at more holistic and

GeoConnections Program, Sylvain Latour – GeoCconnections – Director (Powerpoint Presentation to be added) comprehensive program that will allow

 Sylvain Latour, Connecting machines to connecting bureaucracy to connecting to people (3 levels) establishing a shared vision; History more flexibility – need to work on

Director, MASAS Partnership Evolves... critical infrastructure and EMS.

GeoConnections

Program, Mark Williamson – Dep. DG, Centre for Security Science (will provide power point presentation - Ken)

Key message: funded over the last 9-10 years ++ exercices – practice – report back on their lessons learned and get into the development of Main focus is to develop the plan to

Centre for Security Science technology. make sure it will be done on time within

 Mark Williamson, Unique construct – struck in 2006 – MOU with Public Safety Canada and DND. Make investement in science and technology in the field of budget.

Deputy DG, CSS safety and security. Through good leadership and linkages we have with first responders and planners, the idea has come to fruition.

Manage 3 projects – CBRN .... Canadian Centre for Security. Need to look at business model (same as

Public Safety Canada 3 critical outcomes – 1) one is related to the border, 2) another long-term priority is the interconnectedness of the government and the public what we did with broadband is now

 Pierre Trudel, Director, and how we prepare in the case of an event and, 3) public confidence. available across the country) and work

Science, Technology & Interested in funding some of these activities because we will not be able to deliver on these if we don’t have tools to help us. to justify the tools and find money. Will



Prepared by MCO Business Group Rev. 0 March 14, 2011 Page 9 of 29

Multi-Agency Situational Awareness Systems - “Operationalizing MASAS”



*** Day 1 *** National Stakeholders Workshop Report

Agenda Item Presentation Overview Observations/Comments Recommendations

Interoperability Investing in other areas – critical infrastructure, surveillance technology. Emergency management systems domain. also link with the provinces – build on

the experience in Sarnia and Lambton –

PIERRE TRUDEL – (See Doug Carnegie’s Powerpoint Presentation given DAY 2) use their experience to tell other area

View of public safety – department more involved in the operational and technological aspects. Dealing with Emergency management that this is where they should go. Need

systems that work with first responders. Need to be more present at their level to develop policies that work for them. to understand each our roles. Need a

policies – interoperability – 27 people are now working to develop structure and framework – the department is really working on being working Group to know what needs to

more focused. Both CBN and interoperability were approved last month. be delivered.

Re: MASAS – three groups involved GOC, ST&I, CSS

Main focus is to develop the plan to make sure it will be done on time within budget. Senior officials responsible for emergency management

(SOREM) – will make sure that a good idea is rolled out nationally; have obtained political approval – it makes getting the right policies and

funds easier. We will use the Interoperability office – part of ST&I. These people will work with the people involved in the technical aspects of

MASAS to make sure the right framework is in place to move MASAS forward – need to put a plan together and determine how we will

sustain it (no money from government).



MASAS Open Technology (Powerpoint Presentation to be added)

Demonstration What MASAS is and is not. MASAS runs on any browser - some have tried it and it works

Primary purpose – link your tools with someone else’s tools – People managing the Canadian CAP would love to hear from Canadian Clear understanding of the scope of the

Jacob Westfall users tools is required because some may

NetAlerts Inc. 3 initial MASAS Canadian Instances consider these tools as an answer to

- MASAS Sandbox Something that is being explored at this point – deployment and user their needs and will not pursue other

Doug Allport - Read only (weather) access will be further discussed and defined. tools that may be required. It must be a

Allport Group - Near operable (end of March) system of systems.

Mapping – how can we integrate to the maps we would use in

Focus on connections – handshake between the tools Manitoba to report on flooding? It’s possible to take this information

Not everyone has tools – created some basic tools – and put it in your map system – tool remains basic - Will be doing Need to provide clear instructions on

One includes a basic communal tool - made them available – open layering at the national level. the limitations of the tools.

source code. If we look as MASAS as an enabler –keep

Can download the system – can provide comments and advice on Q. What capability will this tool have in tracking information in day to it simple, build it solidly and make it

where we should go day incidents and the crises - need for communities to make business available.

Basic tool kit set gets things working faster cases – get funding for managing people – also risk management

process – how the community can cope with the incidents

A demonstration of the MA SAS as used for the Sarnia exercise was A. Out of scope for this tool – this tool is meant for people who

viewed, illustrating the capabilities to pinpoint geodata associated don’t have tools

with an event, providing first responders with critical information to

launch their actions in a coordinated fashion.





Prepared by MCO Business Group Rev. 0 March 14, 2011 Page 10 of 29

Multi-Agency Situational Awareness Systems - “Operationalizing MASAS”



*** Day 1 *** National Stakeholders Workshop Report

Agenda Item Presentation Overview Observations/Comments Recommendations

The Business Case for

MASAS and Improved Overview from a business perspective (Becking-O’Donnell Todd Smith (Powerpoint to be added) Review and study benefits (both

Information Flow in Support Powerpoint to be added) Show what we’re doing with our E-map – emergency map viewing tangible and intangible)

of Government Operations Purpose – give ideas going forward to beef up our arguments to ROI conducted on their application; assumptions deemed to be

 Information, Q&A justify the MASAS concept for organizations. conservative There is a need to identify correctly how

the use of MASAS can be an attractive

Federal Operations MASAS - using the underlying geography to improve info sharing Organizational Context investment; BC EM project a 60% ROI

Perspective: between different groups EMBC - Four business units – planning, mitigation, emergency

Own tools – own process – using geography to get the information coordination and BC Coroners service

Ian Becking Emergency Coordination – 24/7 operations

CAE Professional Services Darrell O’Donnell

Darrell O’Donnell Talk about federal space – whose information is to be shared BCeMap – in the process of operationalizing the tool – mid-April –

Continuum Loop Inc. information? pattern of information flow is same across federal and phased approach in the coming months – a few years to total

provincial implementation -

Todd Smith Provincial Information Flow – lots of info amongst first responders ROI – perceived not actual, based on known and/or estimated facts

Operations & Return on MASAS allows all levels to get the same information at the same Significant benefit – tangible and non-tangible. Tangible conservatively

Investment (ROI) time (real time) expected to be around 60% ROI

Perspective: MASAS is not what does it mean to my organization? It is much

Todd Smith more in the realm of “What does it mean to me?” Comment – Doug Allport – re: measuring tangible benefits is

Emergency Management BC somewhat challenging – however in the Sarnia event, Harbour Master

and Canadian Forces said that had they had similar info, and levels of

situational awareness, they would have allowed snowmobilers to be

there earlier. The Sarnia HM said he was always the last to know. Hard

to put a dollar figure to the benefits.



The Current State of MASAS

Information, Q&A (Powerpoint to be added) Questions

Ken – progress update on the development of MASAS.

Ken Marshall (GeoConnections and Centre for Security Sciences). Q1. System resiliency measure? Do you have a DR?

GeoConnections Program Historical outline A. Not in operational mode yet. High resiliency environment – not at

Roadmap – we’ve been listening for 5 years point of deciding on operational levels – will use the highest one

Jack Pagotto Have had national workshops – ongoing working group – federal

Centre for Security Sciences steering committee for networking. Developed the capability gap Q2 – to whom do you envision handing off so that there is control of

assessment. and overview of this over time – my experience, if hand off without

Business case to advance MASAS – Development and also looking at clear lead assigned – there will be changes along the road and that will

sustainability aspect impact the resiliency –to be successful – need to maintain integrity



Prepared by MCO Business Group Rev. 0 March 14, 2011 Page 11 of 29

Multi-Agency Situational Awareness Systems - “Operationalizing MASAS”



*** Day 1 *** National Stakeholders Workshop Report

Agenda Item Presentation Overview Observations/Comments Recommendations

Who is working on this? Basis on where to get advice: see National A. There is an agency at government –lead government structure

Implementation Team (GeoConnections, Public Safety Canada and will be the same regardless of how we develop this (NGO). It will

contractors – Allport, Becking, O’Donnell and Westfall. Sandbox be developed with highest resiliency possible (99.8)

Hosting etc...)

Q3. In the future, do you see the shared files that we create and share

Current MASAS collaborators (See Powerpoint - graphical on our site populating MA SAS

representation of participants with colour code) – bold ones are A. NR Can offers mapping support – multi-mapping. How we see this

those who are doing something – gray color – contributing and have – not figured out yet. MASAS will certainly be an enabler for our

a real interest own department to improve our info sharing whether it is

tsunami, earthquake. Could be red alerts. Could be hyperlinks. It

1) MASAS Integration and Connection (see details) would be hyperlinked with agencies’ own website.

2) MASAS Architecture Version 2.0 – moving from architecture to

generation using the sandbox... looking at what future

generations might encompass

3) MASAS Stakeholder’s Workshop and demonstration next target

for demonstration – DC Washington State cross-border incident

on earthquake

FEMA asked Canada to participate - USResiliency (CUSA ? ) –

interoperability – broader case - experiment in mid-June

4) Awareness, Coordination, Knowledge Management & Transfer

Activities – have overview type webinars with Q&A - hopes to

share gap assessment with the community to get their input

5) Establishment of sustainable governance and policies –

6) Hoping to get resources once the agencies see that this is

serious and happening.



Status Briefings from PLENARY REPORT NOTES - Comments gathered during the group

Participants: Group 1 presentations at the plenary are summarized as captured by the note  Explore making MASAS mobile

FLIP CHARTS (priority items) taker, and represent as closely as possible the participants’

Format: Approach = each item identified with challenge and suggested comments.  Start integrating planning capability

Discussion groups were solution – stored data to help forecast

asked to address the  Incident aggregation (snow-mageddon) Group 1 – required services and resources in

following three questions:  Challenges: identifying scope of event; triggers EOC activation Experimentation – three levels of response using the tool want potential events

(P1) MASAS at their fingertips – next = make it mobile, available in vehicle

What have you done?  Future: contingency planning (weather – Sarnia phone call, Concept of operation development – know how to use the tool.  Integrity of data with respect to

What would you like to do Spring flooding) Challenge – identify definition requirements per group and look at social media



Prepared by MCO Business Group Rev. 0 March 14, 2011 Page 12 of 29

Multi-Agency Situational Awareness Systems - “Operationalizing MASAS”



*** Day 1 *** National Stakeholders Workshop Report

Agenda Item Presentation Overview Observations/Comments Recommendations

next? past experiences

Challenges the community  Security (big and small ‘s’) Incident aggregation – id early the scope of the event – include tool

needs to address?  Challenges: trust and confidence in information and system; for planning. Start contingency planning - historical information –

social media expectations (business integration rules) (P2) might need to look at further down the road

DISCUSSION Groups (1  Future: how to deal with social media; information fusion Security – general integrity of the system. Start looking at social

hour) media.

Future – how to deal with social media and fuse.... Security and social

Identification of two top media need to be addressed...

priorities (see all items in

Workshop Notes – RAW

DATA)

Group 2

PLENARY REPORT NOTES

FLIP CHARTS (priority items) Group 2 –

 Ensure resilient production

Host MASAS collaboration website – operationalizing service (P1) ONT working with management enterprise solutions – planning on a

environment

linkage to colleagues to integrate the system. Also doing work on free-

 Sustainability and governance

#2 – what to do next? flex ... with MASAS. Working at operationalizing the system.

 Information security parameters

 Look at how to integrate MASAS into EMES: resilient production What is really critical – clear model with integration; should we be

must be defined to apply adequate

environment (P1) looking at a resilient production environment.

and effective filters

 Data model and constraints (P2) #3 Challenges –

Sustainability and governance of the project. Need to know R&D but

#3 – Challenges we also need to know how we will sustain it. Need to know that it will

 MASAS sustainability and governance – (to show those in private have a future. It must be a workable service related to the

industry who are not yet doing it how to make money providing, architecture.

developing free tools) (“free” as in “free market”) (P1)

 Workable services oriented architecture (P2) Security will depend on level of government and protocols. We will

have to talk about Security and establish protocols.

Talking about the filters.. how people are added to the system – is it

everybody? Media access is a concern. Maybe there are opportunities

to deal with filters – the intent is to provide info to the community.

From a perspective of Security there is a question about too much or

too little security. Open source and open document concepts.

Defining communications plan. If challenges will be a major obstacle –

find a way around it!



Group 3



Prepared by MCO Business Group Rev. 0 March 14, 2011 Page 13 of 29

Multi-Agency Situational Awareness Systems - “Operationalizing MASAS”



*** Day 1 *** National Stakeholders Workshop Report

Agenda Item Presentation Overview Observations/Comments Recommendations

PLENARY REPORT NOTES  Sustainability with some set funding

FLIP CHARTS (priority items) Group 3 – level

Work on incident management system – did an exercise – had the  Develop Policies

#2 – What would you like to do next? feature – viewing with fusion point  Need actual potential customers to

 Engage/help small municipalities (P1) Want to engage the smaller municipalities that don’t have the identify their requirements

 Leverage existing GIS capabilities (P2) funding and also leverage the systems they may have on the shelves.  Data Sharing Agreement

There is a Canadian topographical map. Need education.  Common Language

#3 – Challenges to address future framework: integrate MASAS to other projects. Emergency  Equipment tracking as a feature

 Self-sustainable – how? – funding models (P1) resource network – info sharing among resources.

 Educate how to specify MASAS compliance in RFP’s (P2) Challenges to address:

- More self-sustainable with some set funding level

- Policies

- Need actual potential customers to identify their

requirements

- Data Sharing Agreement

- Common Language

Store who owns what – info available – standardized and classified

according to nomenclature – would like to have this tied into MASAS.

Also able to tie down assets and location). Based on a system in the

US – Canadianized.



People who are looking for equipment – will know where it is.

Currently looking at tracking helicopters. Technology exists – need to

look at how we capture the info and integrate.



Group 4

PLENARY REPORT NOTES  Keep it simple

FLIP CHARTS (priority items) Group 4 –  Link to common day occurrences

#1 – What have we done? Challenges – MOU – shared data who will do what with the data

 Validate tools through pilot tests

 Developed MASAS compliant systems (P1) Focus on something that can be used daily – road impacts – can be

 Exercised MASAS in tests (e.g. Windsor) (P2) used at many different levels. People will see the value on a day to

day basis

#2 – What do to next? Q1 – Implementation and Certification Suite – these tools are critical

 Answer governance questions (who owns what) (P1) tools?

 Business and communications plan (P2) A1- something that has been done and that would be helpful with

some kind of labels



Prepared by MCO Business Group Rev. 0 March 14, 2011 Page 14 of 29

Multi-Agency Situational Awareness Systems - “Operationalizing MASAS”



*** Day 1 *** National Stakeholders Workshop Report

Agenda Item Presentation Overview Observations/Comments Recommendations

#3 – Challenges Looking at a MASAS combined tool – validation tool for Canadian

 MOU/Charter (P1) profile – two tools could be on your laptop to validate the information

 Details to input: Roads, roads, roads (P2) – informal process vs formal process; that is really difficult.



A2 – Exercise such as Windsor exercise is something with which you

can validate what you are doing. Compliance with tools already in

place is important to ensure smooth transition without reinventing

the tool. Need to have a systematic way of storing the information

.

Validation of the digital services. We need something that is agile that

can be put in place. Demonstrate the responsiveness – establish

what’s the reaction time to the issues.



Group 5

FLIP CHARTS (priority items) PLENARY REPORT NOTES

#1 – What have we done? Group 5

 Some use in-house manual tracking Integrate existing systems with MASAS

Think in terms of progressive

 Others develop web platforms Be part of the steering committee (Governance) integration. Look for

 Participated in inter-departmental meetings Determine what info can and cannot be shared. Validity of the opportunities to expand the

 No one has capability to share via same tool. information application of MASAS

#2 – what would you like to do next? Most of the people at the table were new to the concepts of MASAS

 Develop government of Canada-wide COP (P1) Focus mainly on awareness of the organization and advancing the

 Understand our own existing capabilities – needs before moving concept and integration business case. For instance, HRSDC have an

forward; get buy in; be on steering committee interest in using MASAS. There is an undeniable fact about MASAS –

 Determine what info can be shared and what can’t it’s the ground swell – in terms of possibilities. As people find out

 Governance (P2 – 3 previous bullets) about it, there will be increased demand and need for its capability to

facilitate interoperability of data and information flow.

#3 – Challenges

 Senior management in home organization (PT/municipalities;

DG federal operations work groups; ADM Emergency

Management Committee) (P1)

 Prevent scope creep; steering committee all members

understand their role and don’t promise senior management

the world (P2)

Group 6 PLENARY REPORT NOTES



Prepared by MCO Business Group Rev. 0 March 14, 2011 Page 15 of 29

Multi-Agency Situational Awareness Systems - “Operationalizing MASAS”



*** Day 1 *** National Stakeholders Workshop Report

Agenda Item Presentation Overview Observations/Comments Recommendations

FLIP CHARTS (priority items) Group 6 –  Governance – develop framework

 Incident notification required: borders; in-land ports; airports  Common language – attend to

Challenges potential barriers

Next Steps: - Common language  Road map – develop a structured

 Upload border closures and wait times - Standards approach to progressive

 Ongoing monitoring not currently required; reliance on GOC - What does it really mean? –framework and architecture – implementation

and front-line there are standards in regards to symbology and we have an  Information dissemination – policies

 Push info once – automatically: disseminate – SMS, e-mail, architecture (gen. 2). We have a gap assessment tool – need are required to establish boundaries

MASAS, etc a fully developed road map

- Governance

CHALLENGES - Who is authorized to interact with system – i.e. can I launch a

 Common language (standards); framework; architecture: search and rescue?

roadmap requirements, vendor development (P1) - Information classification – security and sensitivity

 Governance (P2) - Now that there are +++ info into common operational picture

– what does it mean to security and sensitivity

- Money is an issue

Next step – needs to be a spot for best practices and lessons learned.



Q1 common language – this may not be important from a national

level but is extremely important at the municipality level.

we’ve adopted an international symbology for MASAS – will be a

challenge to integrate to all – common denominator.



*** GROUP 7 REPORT ON FLIPCHART WAS A MINDMAP DRAWN PLENARY REPORT NOTES

BY DARELL O’DONNELL WHICH IS ATTACHED TO THE REPORT *** Group 7 – MASAS definition required to

Everyone’s definition is different. Until it’s defined don’t know what

to do next.

establish what to do next.



Together to shape MASAS in the best possible way. Point is to clearly Recommend two pronged

define it and communicate it to allow proper engineering. approach – develop a core

Don’t get too concerned with boundaries. platform, and allow data modules

MASAS has to remain fuzzy – as a user, if you bolt it down too tight,

my needs will not be the same at the GOC – my firefighters need to be

to be specific to user.

using it on the ground. Some of our recommendations – because

we’re on the grounds we may have a whole different view of how we

use it. Careful with how we view it. The core is the commonality part



Prepared by MCO Business Group Rev. 0 March 14, 2011 Page 16 of 29

Multi-Agency Situational Awareness Systems - “Operationalizing MASAS”



*** Day 1 *** National Stakeholders Workshop Report

Agenda Item Presentation Overview Observations/Comments Recommendations

and then there are all sorts of particularities.

At the end of the day, we’re talking about data – everything else flows

around that.



Thinks an incremental approach to core is important. Need to fix at a

point in time what the core will be and when it will be complete. A lot

of the confusion – when we talk to MASAS vision which may come in

two years vs SANDBOX in present day situation.









DAY 2 REPORT



*** Day 2 *** National Stakeholders Workshop Report

Agenda Item Presentation Overview Observations/Comments Recommendations

Advancing MASAS

Governance Doug Carnegie (Powerpoint to be attached to report) SOREM – act as a secretariat for overarching SOREM framework – SOREM is in place; use as leading

 Communications Working on interoperability issues since 1999. leading that group is Public Safety. body with Public Safety as lead group.

Interoperability Strategy MASAS connects to all of that. Each jurisdiction employing MASAS have their own group that look

and Action Plan for Progress to date – questions re: how much it will cost at how it’s being done. Develop standard certification

Canada Moved away from policy to implementation .... moved quickly since SOREM will look at all of the strategies – MASAS being one of process

 Stand up of the Public last summer SOREM approved plan and minister signed this past them. Government structure is already there – we need to find

Safety Canada January how you will fit into that. Establish Standards Directorate –

Interoperability MASAS has been identified as a major issues in the action plan CITEC took broadband issue – each of them talk to their political audit and maintain standards.

Development Office Next steps – masters ...– governance structure already in place - ADMC – use Leverage with Canadian General

 Governance via the Interoperability Development office (IDO) is accountable to SOREM that mechanism. Standards Board (CGSB)

SOREM Interoperability (Senior Officials Responsible for Emergency Management)

Working Group - PRIMARY FUNCTION is coordination Q2 – Are we saying that the 700 MG is a model for governance

- Reaching out to you, gathering your concerns and issues, structure? Apply a ISO-like standard to the

 Small Group Discussion developing national strategy and policies A2 – looking at the communications strategy of SOREM – MASAS is system of systems so that integrity,

guided by the Emergency Also broadband (worth a lot of money – billions) and Canada/US one of that group’s options – there is already a policy approach to viability, credibility and reliability are

Management Systems interoperability WG addressing the issue it. Collective process already in place. maintained.

Interoperability MASAS – What is it? Need clear definition, and boundaries Territories and provinces already established. – we can make a

Framework and the Current State – review inputs from all stakeholders and feeding back recommendations to them.



Prepared by MCO Business Group Rev. 0 March 14, 2011 Page 17 of 29

Multi-Agency Situational Awareness Systems - “Operationalizing MASAS”



*** Day 2 *** National Stakeholders Workshop Report

Agenda Item Presentation Overview Observations/Comments Recommendations

MASAS Capability Gap to you = coordination ONT has an Interoperability WG that reaches out – perhaps need

Assessment (CGA) Next Steps – continue with consultations with feds and provinces – to formalize the arrangement – that will provide the national

looking at ROI –an ROI of 2 years is very enticing for government. structure from municipality upwards -

Doug Carnegie, Public Safety many territories don’t have the capability of having

Canada Ken Marshall (Powerpoint to be attached to the report) representatives - suggesting to have a MATRIX linked to a core

Progress and governance platform – so that we don’t end up with a flavour in each province;

Ken Marshall, Looking for oversight, coordination, accountability need to agree on the core platform.

GeoConnections Define “Governance” as a function within a lot of the Public Safety community – a lot of

- Challenging to develop standards, commonality – fold Search &Rescue into emergency

Roles/services you’d like to see - We have national strategy and action plan which solidifies the activities as well as coastguard.

from a national office? next steps we will take Could a steering committee have representatives from each of the

- Recently we’ve been able to show the benefits groups? S&R as a subset of Public Safety

Need to determine who the prime customer is.

Governance Gap Statement

- Governance establishment = funding and sustainability THE NEED FOR A STANDARD PROCESS

- Have common learning protocol approved worldwide (ISO)

Governance on the Interoperability Continuum - Look standards CAPSI WG - typical standard review is 5 years

- formal coordination required

- policy framework – what needs to be governed? - Recommendation – develop a standard certification process -

- group authority that makes decisions (ISO type of approach that ensures uniformity, consistency

and reliability of design)

Keep MASAS Vision in mind - Recommend standard directorate – to audit and determine

Elements to be considered for Governance how standards will be maintained

- What will be governed - Key in standard – how to manage and how to update

- Focus on standards, technology and systems (some of the core - Propose build one standard – leverage it – with Canadian

functions we are expected to provide) General Standards Board



Discussion on possible options for governance Bottom Line:

- Activities We need a ISO-like process to frame plug-ins or any application

- Needs that would be part of the MASAS platform (including the core

- Who should be the lead of the activity – timeline – barriers and central object) to ensure that anything that is built after the base

risks associated with those has been developed follows a certain degree of uniformity,

consistency and reliability. Same concept should apply to the

updates.



In order to advance the development in a progressive and constructive way, the group suggested the need to keep the following in mind:



Prepared by MCO Business Group Rev. 0 March 14, 2011 Page 18 of 29

Multi-Agency Situational Awareness Systems - “Operationalizing MASAS”



*** Day 2 *** National Stakeholders Workshop Report

Agenda Item Presentation Overview Observations/Comments Recommendations

 Must set time targets; otherwise, either users will go their own way, or general interest will weaken making it much harder to Set time targets

Key Issues to Consider maintain momentum (initiated in this workshop)

(recorded during the  Funding justification: as one participant stated, there is a critical need to review thoroughly the benefits that can be accrued from Define justifications for MASAS

presentations on governance) such a system of systems. A clear definition of what MASAs is to be and what it will produce in the way of integration, elimination

– MASAS Development of gaps and duplication, and acceleration of response in general can be catalogued into efficiencies that will result in significant Develop communication strategy to

savings for a multitude of users and management organizations alike. inform and enrol stakeholders.

 There is a crying need to develop a communication strategy that will engage all partners and stakeholders into a common and

aligned purpose. Establish input standards for data

 In order to ensure credibility of data, it was suggested that there be input standards developed and system software designed and credibility and reliability

installed to filter information and direct it to the appropriate level in the responsibility matrix.

 It was suggested that a Working Group be struck to work on the integration of Standard Operating Practices (users’ needs and Working Group to be struck for

system management processes). integration of Standard Operating

 Clarification and definition of who needs to be engaged/involved and establishment of levels of use and access with respect to Practices (users’ needs and system

security and confidentiality of the information – who uses, who has access, who inputs, types of media, levels of interoperability, management processes).

boundaries of restricted data, etc

 Consider the USERS as the determining factor in establishing the scope and nature of the data filters (allow the user to define what Define levels of use and access with

is available to the public domain, and what is to be kept confidential). respect to security and confidentiality

of the information

Results of Discussion Groups – Governance Issues

General highlights of ideas

gathered in the discussion on

Governance – 3 questions Observation / Comments - Comments gathered during the group presentations at the plenary are summarized and represent as closely

where given to guide the as possible the participants’ comments.

groups

FLIPCHARTS – This a composite of the ideas noted by the groups during the discussion period at each table.

Q1 – Who should lead the

activity? Discussion groups were given the choice of two subjects and were asked to address the following questions with respect to:

Q2. When? EITHER

Q3. Barriers to success? STANDARDS: (e.g., existing governance by GeoConnections Program of CGDI endorsed geospatial standards (OGC, TB, ISO etc); EM

Mitigation measures? Symbology;

OR

TECHNOLOGY/SYSTEMS: (i.e. who maintains core functions such as messaging exchange hubs, development sandbox, web presence etc.)



FLIP CHARTS Q1

TECHNOLOGY Q1. Who should lead the activity? MASAS is a system for Public Safety Need to respect schedule for

Who leads now? Truism - whoever pays should lead completion by 2013

Prepared by MCO Business Group Rev. 0 March 14, 2011 Page 19 of 29

Multi-Agency Situational Awareness Systems - “Operationalizing MASAS”



*** Day 2 *** National Stakeholders Workshop Report

Agenda Item Presentation Overview Observations/Comments Recommendations

Who is this technology for? Momentum has started – looking at learning system in the US –

Q1 – Who should lead the Who ever pays has the say. Public Safety to lead from a federal level; provinces to front-line

activity? Fed/PSC (FEMA US) provide details on application. Need a simple solution for firewall

Q2. When? - Maintained by “IPAWS’ Crown corporation or established organization – need group that

Q3. Barriers to success? - Consolidation/foundation have the flexibility to move quickly. Funding mechanism is critical to

Mitigation measures? - User groups MASAS provides tool for interoperability. ensure future viability – partners and

stakeholders need to identify benefits

Suggest the establishment of a crown corporation or identification of GeoConnections – funding gone by March 2013 - need to have

an existing organization governance and framework within 6 months - October 2011 Use existing technology; improve

Implementation in 2012 through exercises and further

Q2 – When? focused development

Mandates Legislated mandate of the various organizations

Technology themes - FED has a responsibility to provide the overall guidance, and

Basic, reasonable, guidelines, vendors and add new tools based on develop basic tools (i.e. SandBox to which the front people

user-requirement can add their widgets)

Feds – establish and maintain baseline - e-Health - a methodology in place. National standards

Proposed 2012 implementation collaboration – Canadian InfoWay Standards = very expensive.

Oct 15, 2011 – foundation established – 2012 = transition year - efficiencies expected as a result of MASAS – should be

Sooner than later – 6 month target factored in the dollar value



Q3 - Barriers to success? Mitigation measures? Q3.

Money – mitigate – subscriptions, multi-level fee system, some JET

Fed and prov. IT policies and procedures are not always compatible (?) funding available to support MASAS

Mitigate by using an approach like e-health Participation – need complete buy-in at the provincial level and

$ mechanism – JEPP; Multi-level fees municipalities – mitigate – communication – benefits, case studies

Trust – data sharing and running exercises

Participation federal/provinces/territories/municipalities Trust in sharing information – mitigation = education and data

Federal , provincial and municipal legislation sharing understandings.

Mitigation – strategic communications

Interagency cooperation (egos & attitudes) Collaboration and cooperation – Provincial-federal legislation –

working out of existing framework





FLIP CHARTS PLENARY REPORT NOTES

STANDARDS Q1. Who should lead the activity? Q1 Lead: steering committee lead by

Need for MASAS Steering Committee – start with people in the PSC; members from interested



Prepared by MCO Business Group Rev. 0 March 14, 2011 Page 20 of 29

Multi-Agency Situational Awareness Systems - “Operationalizing MASAS”



*** Day 2 *** National Stakeholders Workshop Report

Agenda Item Presentation Overview Observations/Comments Recommendations

Q1 – Who should lead the – National MASAS Steering Committee room who are committed to it. stakeholders

activity? - SOREM. Overarching body

Q2. When? - High level approvals SOREM should lead – high level approvals Sub-working groups: updates and

Q3. Barriers to success? - Not detailed approvals Yes to steering committee Public Safety should lead changes as required

Mitigation measures? STEERING CTTEE Have diversity of those involved – reaching out to federal,

- PSC lead – chief information officer provincial, military, etc... fairly big community for representation Timeline is tight; users need a system

- Reps – federal, provincial, municipal, military, search and purpose – NOW

rescue, volunteers, CI, vendors, others? Sub-working groups – ongoing for the establishment and changes

SUBWORKING GROUPS as needs identified Use a progressive approach to

- Ongoing forums for established standards and addressing Subject-matter experts and people who are involved in policies implementation – do not wait until all

changes and doctrine standards are defined

- Subject matter experts – tech, ops (GCO and EM), policy /

document Standards are required: technical standards and operational

- Police, fire, F/P/T, military, S&R, volunteer, FN, etc. standards (drive the operations)



Q2 – When? Q2

The answer is predicated on: if we don’t have something soon, users may try something else

 What standards are needed and funding will disappear

 What exists – review internal and others ASAP – need to implement the program as well for standardization

 What needs to be developed – what’s required, what already exists – adapting or creating new

 Initially - Cyclical review ones

need to identify standards – should be in place at the front end –

Q3 - Barriers to success? Mitigation measures? based on feedback – will drive the constant evolution of these

 Fight hard not to reinvent standards

 Focus on international standards

 Follow single process for others Q3

 Get involved in international committees so don’t have to be Focus on International standards and get involved there

unique here. If we are to manage things – CAP study group – let’s get their

 Complexity process – no need to reinvent the wheel – real efficient process –

o Need for clear target – goals/objectives know where to bring things to.

o Generation 1 – staged implementation Could implement the tool right away – standards to be developed

o With established timeframes will delay implementation (municipal concern).

o Speed of – roadmap to standard development and

evolving standards Complex set of standards – need clear target with clear

expectations

 Technology Innovation

- Looking at staged implementation – once initial standard

o Road map to review changes and determine how to



Prepared by MCO Business Group Rev. 0 March 14, 2011 Page 21 of 29

Multi-Agency Situational Awareness Systems - “Operationalizing MASAS”



*** Day 2 *** National Stakeholders Workshop Report

Agenda Item Presentation Overview Observations/Comments Recommendations

incorporate or not ready – launch it – when changed, use an accepted process

 Different communities with different needs that provides uniformity, consistency and reliability

o Identify who, representation on working groups – - Establish time frame for re-release standards – then work on

police, fire, F/P/T, etc. revisions

 Lack of secure and up to date data - Road map to standard development (evolution)

o Data maintenance and updating - Wide variety of communities – corporate based, front-line –

o Data security need to establish clients – have representation on WG

o Establish data security standards - Lack of secure and up to date data – need to establish data

maintenance, security and implement these standards

 Culture of organization: mitigate –

communication/collaboration and research existing models organizational culture – will be prevalent – can be mitigated via

(best practices) communication collaboration across the stakeholders – each group

will have their resistance – communication will help overcome -

research best practices to establish solid bases







Results of Discussions – Operational Policies

Advancing Operational

Policies. Presentation on Policies: (Powerpoint to be added to report) Three questions apply to guide the discussions



Small Group Discussion: - Operational Policies – day to day level – how you go about doing • How do we handle IM ?

Emergency Management your business – data sharing agreements

Systems Interoperability - Users of the system need to set up policies and guidelines

Framework elements of - A few existing policies • Information protection and security

 Information Management - Policy requirements for MASAS - Guidelines for releasing restricted stuff

i.e. Data Sharing o Legal/Administrative

Agreements o Technological • Operating procedures – framework for success

 Information Protection & - Information Management – Capability Gap Statement

Security i.e. Guidelines for - Information protection and security

Releasing Restricted - Operating procedures – business rules

Information

 Operating Procedures



Ken Marshall







Prepared by MCO Business Group Rev. 0 March 14, 2011 Page 22 of 29

Multi-Agency Situational Awareness Systems - “Operationalizing MASAS”



*** Day 2 *** National Stakeholders Workshop Report

Agenda Item Presentation Overview Observations/Comments Recommendations

Information Management FLIP CHARTS PLENARY REPORT NOTES Provide Guidelines for releasing

(IM) Information management - IM – looked at 85% / 15% breakdown – Classified not on the restricted stuff

o Focus on 85% of the information – priority info application

o Start with “easy” data - accessible to everyone e.g. weather, road o Needs to conform with existing laws Develop terms of use agreement for

closure alert o Suggest look at current open source models users – due diligence on correctness

o Following the CAP-CP standards o virtually impossible to meet everyone’s IM requirements

o Conformance with existing laws - Problem – different ratings across municipalities Avoid scope creep

o Need terms of use agreement for users - Environmental scan to see if there are similar application and

o Information posted to MASAS is responsibility of poster, not see how it’s working

“MASAS” - Come up with Pan Canada POLICY

o User due diligence protocol - within federal family – agreement on shared info

o Look at existing open source software IM models eg. MIT - share with each other what we want to post

- share where we put the information not available on MASAS

Notes by Darrell O’Donnell – mindmap notes attached





Information Protection & FLIP CHARTS PLENARY REPORT NOTES Guidelines for restricted stuff

Security o Keep classified separate/out o anything restricted, keep it off MASAS – use own tools - 80-20 conclusion

o Rights by rule/agency/department o Tools – security rules i.e. ambulance etc. – use common sense, - Difficult to agree on what is and

o Limit what can go in by above ex. Location, event, security i.e. if there is an emergency – front line can post the event. If is not restricted

o Tag if open to others updating – don’t want to manage group it becomes a major issue, then EOC publishes the information. - Reality is that we would only put

security rights o Restriction – by agency, by geographic area, by severity non-classified stuff

o Promote classified using some API protocols o Make it easy to post and access - No problem sharing with other

o Passwords/account management o For more advanced restricted stuff put it in other systems EM groups – but more rigors if

o National ‘policy’ on MASAS - definitions of restricted, etc. than MASAS you add other groups to the

o 80% of info is unrestricted o Make MASAS unrestricted initially system

o Everybody can access everything vs obligation to administer at o In the classified domain – promote adoption of MASAS – if win - Certain amount of educational

detailed level the confidence of the clients pieces re: information

o Reality is we will only put unclassified info on a MASAS o Currently set up – updated by individuals – takes a lot of - Pan-Canadian policy

o Information protection & Security – MASAS not to be used efficiency for group to update –may want to put a tag allowing

securely - environment scan on similar initiatives this to happen

o Security ratings vary from F/PT—pan Canadian policy



Source rating (reliable, unconfirmed) – human intelligence, technical

intelligence, signal intelligence





Prepared by MCO Business Group Rev. 0 March 14, 2011 Page 23 of 29

Multi-Agency Situational Awareness Systems - “Operationalizing MASAS”



*** Day 2 *** National Stakeholders Workshop Report

Agenda Item Presentation Overview Observations/Comments Recommendations





Operating Procedures FLIP CHARTS PLENARY REPORT NOTES Need to have deeper guidance and

Q1. SOP WG (UNDER PSC) Understand how to engage between levels of government and understanding of the policies and

- Integrating SOPS throughout hierarchy of government front line users such as police, etc. Needs to be a good how to integrate them

- Across communities of practice (law, fire, SAR, ETC) understanding of how these integrate. Create matrix – who needs

to engage with whom and how MASAS can be used so that people Information posting requires a well-

Q2. Organizational engagement and information sharing matrix know when they post information. defined protocol



Best Practices for processes around MASAS Need to align various views about levels of sensitivity - let people Institute a Standard Operating

(consumers) set filters and these filters change based on the Practices Working Group that will

o Acknowledge SOP exists at multiple levels – important for event. have mandate to review and

consideration in architecture integrate operating practices in

o Suggest setting up WG to look at and be mandated to integrate if you want to limit the flow of information – MASAS may not be MASAS

SOPs horizontally and vertically the way to go

people will post according to their own filters.

should be useful dialogue – where your absolute restrictions are –

what you need to know in a general way – establish common

ground – as you aggregate information – can be sensitive.



Canadian Emergency Mapping (PDF Powerpoint attached to the report)

Symbology - Overview Symbology is used in MASAS as it stands now. Someone needs to take the

 Information, Q&A Emergency Mapping Symbology responsibility of making it standards –

Done by GeoConnections If building own software to connect to it – most important is the may be part of GeoConnections and

Mark Sondheim, Refractions What does constructing a symbology mean? semantic in how you factors are categorized – some R&D –

Research - Semantics, Design, utility incompatibility with colours vs B/W OR the image base.

Started with US Dept. Homeland Security Need a national approach to

Other efforts from around the globe Access a drawing (stroke-type) that would be useful if symbology

What direction should Canada take? GeoConnections could provide it to include in our system.

Design – hierarchical structure made sense

Everything is seen through the eyes of incident, infrastructure and Symbology in BCeMap – some challenges – what is the

operations maintenance process ?

Looking for symbols that are highly visible – colour scheme

EMS Licence The other component – need a national standard on symbology

Complementary symbologies - take EMS work and extend to it

Background: Shapes and Colors – want a point on the symbol to tell us



Prepared by MCO Business Group Rev. 0 March 14, 2011 Page 24 of 29

Multi-Agency Situational Awareness Systems - “Operationalizing MASAS”



*** Day 2 *** National Stakeholders Workshop Report

Agenda Item Presentation Overview Observations/Comments Recommendations

exactly where it is –different set of colours / according to level of

security

Crime Mapping Symbology – done for department of Justice – same

structure borrowed from EMS work –

Observations

Limitations

What’s next



Discussion on Future ( Powerpoint attached to the report – updated from Michel)

Developments MASAS going NIEM Need to define the service offering.

 Overview and Brief PS CIOD – Interoperability Program Portfolio – Michel Savoie - Concept: how we want to exchange at the fed level at the EOC Engaged in the design- looking for

Discussion on Leveraging NIEM Overview and GOC – in order to get greater adoption by our community compatibility with systems that are

the National Information Public Safety Perspective – greater limited access – in a more controlled way –service being used by other groups such as

Exchange Model (NIEM) – MASAS with NIEM need to control the info in a better way. New info police.

Emergency Data requirements will be modelled using NEIM. Task and analyse

Exchange Language and What is NIEM? 7,000 terms – keeps growing – object oriented to get to fit with MASAS – definition of user access/credentials

other related standards Library, supporting documentation, training Knowledge Centre, Help by defining contact information, association, authorization Continue building on NIEM to ensure

for MASAS. Desk contact, electronic identification, certification, etc. This could compatible and workable information

Justice XML provide model and leadership model be a solution with what we are doing with MASAS – when we exchange solutions

Michel Savoie Used by the states and municipalities – great deal of buy-in and find additional needs not already captured in standard we are

Public Safety Canada partnership – best practice driven using, we will research the NIEM that could fulfill that

requirement or could be useful for it – make it MASAS-

What NIEM is NOT. friendly.

- What is currently in MASAS is already NIEM compliant. The

Canadian Association of Chiefs (Police) promoting NIEM Americans are well engaged in NIEM use within their public

Need to build policies and agreements between two organizations safety efforts – we can reuse some of their approaches

wanting to exchange data - In terms of industry using NIEM -.... lots of offering happening

NIEM Overview – (flower diagram) every element that is common to in the states. We need to advise our clients to gain insight and

everyone is in the NIEM core. define and choose whatever information they need

Future Domains - at fed level very interesting at Treasury Board not - MASAS in the domain of EM – EOC and GOC looking at

only Public Safety but also back office such as PeopleSoft implemented systems.

NIEM Overview – how Niem is structured internally = the core

element Information and data on the NIEM can be accessed at niem.com

Public Safety perspective – important to understand our scope – our you will find all info about model, clearing house, business

mandate within our dept is with Public Safety which we see from a fed oriented documentation.

perspective - #5-6-8 items (Powerpoint slide) that we are attempting



Prepared by MCO Business Group Rev. 0 March 14, 2011 Page 25 of 29

Multi-Agency Situational Awareness Systems - “Operationalizing MASAS”



*** Day 2 *** National Stakeholders Workshop Report

Agenda Item Presentation Overview Observations/Comments Recommendations

to address with NIEM. Cross border Information Exchange – not NIEM.ca – not tested yet.

numbered but since USA using NIEM we will leverage the same

symbology.



Leveraging Volunteer Leveraging Information (Powerpoint attached to report)

Geographic Information, Open Discussion – three questions Already have social media (Twitter,

Crowd-Sourcing, Open Ken Marshall FEMA taking advantage of open data and social media. Same etc) another feed (georeferenced) we

Technologies, Open Data, - What’s coming down the pipeline in the future? standards that we are using and can be used. can include – does not need to be

Social Media included into MASAS - can subscribe

 Information & Discussion Q1 Social intelligence and citizen contributions of value to the MASAS A lively discussion on social media generated a number of ideas to the media to complement other

community? and questions concerning: activities coming from MASAS – turn

Ken Marshall Q2 How can we leverage?  the value of SM, up your Flickr, Twitter to augment

Q3 Challenges?  the limits of usability, your information

- Volunteer Geographic Information, Open Data – Open Street  the need to recognize its impact in emergency situations,

Map – government is looking at that to change detection and  the desirability of connecting without letting the integrity Need to set up appropriate

bring more information of the system of systems be jeopardized guidelines

 the need to consider integration in future designs

Open Technologies – making sense of real-time communication  the involvement of first responders in determining the There is research at the government

Crowd-sourcing, Volunteers – help each other as a community to get scope of the use of SM level re: how to use social media.

through it  Developers and designers of MASAS

More recently – Queensland Floods, Australia 2010-2011 – should review that research to have

OpenStreet Map See attached Annex – RAW DATA for workshop notes (Day 2) for an indication of what has already

ChristChurch, NZ Earthquake 2011 - the emergency workers or public a complete list of ideas recorded during the discussion. been discovered (avoid re-inventing

can access information i.e. a building is about to collapse – some info the wheel or making same old

marked as unverified – some verified – some level of trust in the mistakes)

information.

Need to differentiate between EM –

Can a trusted social media interface to MASAS be provided? i.e. one- Emergency Management, and First

way ingest of crowd-sourced information? Responders – define who is targeted

in MASAS







Highlights Recorded:

Highlights of ideas exchanged

during the plenary discussion  Could use authoritative source with GIS tool



Prepared by MCO Business Group Rev. 0 March 14, 2011 Page 26 of 29

Multi-Agency Situational Awareness Systems - “Operationalizing MASAS”



*** Day 2 *** National Stakeholders Workshop Report

Agenda Item Presentation Overview Observations/Comments Recommendations

on Leveraging Volunteer  Flickr is geo-referenced

Geographic Information,  Provide a viewer dashboard (viewing options) – Guidelines should be provided

 Emergency First Responders should be the authoritative source for MASAS requirements; ultimately, the information managed

through MASAS should provide help and guidance to allow the most effective and efficient response to the need of the public at

large in a situation of an emergency nature

 MASAS should be an intelligence gathering tool (data entered to allow study and strategy development for future events –

response results, real time facts, extent and breath of situation, use of Best Practices, expected and actual outcomes, etc)

 There is an issue of liability with crowd-source information (concerns about misinformation, garbled data, overstated and multiple

messages crowding out the real facts) which, if acted upon and causing ineffective or inappropriate response, cause make the

responding organization liable in the case of a significant negative result.

 The need to define what MASAS IS and IS NOT so that it Can be designed and used in a way that serves the user in the most

productive way – the thought is to adapt the system of systems to the need

 It was suggested that MASAS (at the outset) be aimed as a tool for emergency management organizations alone, not for public use

 The burning question is: who will be accountable, how will accountability be defined, what activities will be implemented to

support an accountability framework?

 Should monitoring of social media be part of the capability of the MASAS? Many instances were reported on how social media

(Twitter, Facebook, SMS, etc.) have already been demonstrated as key contributing tools in addressing emergency situations (New

Zealand, Haiti, Chile, avalanche rescues, etc.)

 MASAS should be viewed as an authoritative source for communications to first responder organizations and should be the

purview of agencies, not the public at large

 MASAS should not re-invent the wheel, but build on accepted Best Practices applied in other emergency response systems such as

Health (epidemics, etc.) or even in Public Education.

 Users see MASAS as a tool that can be used to monitor impact of situations so that response plans can be improved, enhanced and

made more agile and flexible in moments of critical need

 Development of the system of systems should explore actual users of similar technology (Virginia Tech emergency mobilization

system was referred to)



Open Approaches: Open Presentation + Q&A (refer to Powerpoint attached to the report)

Source, Open Technologies, Illustration of how free software can

IRCan approach etc Intellectual Resources Canada (IRCan) – started 10 years ago as an interest from Public Works Canada to make use of free open source. be used to develop plug-ins for

Planning until 2004 when money was put in to complete the infrastructure. Called Source Code Canada – became Intellectual – provide a MASAS

Joseph Potvin, way to have people share and jointly draft communications across boundaries.

Intellectual Resources Canada

(IRCan)  What it is – management framework first.

 Sequencing the SARS virus – article on the web site

 Advantage of using free software – had the capability of tweaking the information faster without need to check, get permissions,

Prepared by MCO Business Group Rev. 0 March 14, 2011 Page 27 of 29

Multi-Agency Situational Awareness Systems - “Operationalizing MASAS”



*** Day 2 *** National Stakeholders Workshop Report

Agenda Item Presentation Overview Observations/Comments Recommendations

etc.

 ENV Canada – Pointe Claire – entire data centre – is running free software – because they have full control of what they’re doing.

 Related concept in the security field – Open Source Security Strategy – developed by security software company Red Hat

 Made presentation on open source in military – When creating free software –

 Introductory presentations : Economic Drivers – Augment Benefits, Reduce Costs, Manage risk

 Licenses with free software: Permissive, Elastic, Unified---- license of original software, licenses of derivative software and licenses

of associated software

 The R project for statistical computing – suggest this provides the best model to develop a MASAS community and package = a

great code! Several packaging (what we call plug ins)

 Nagios – The industry standard in Open source monitoring- nagios.com – entire application under free license



More information is available on the website - http://tbs-sct.ircan.gc.ca/projects/ircan-initiative/wiki/Overview





Workshop Wrap Up Review highlights and note next steps

Path forward Integrate results of workshop into the

Ken – there are nuggets in the discussion – some immediate next steps : Capability Gap Assessment (CGA)

- Report of the March 1-2 workshop matrix.

- Results of exchanges will be integrated into the Capability Gap Assessment document which will be issued and shared with the Issue CGA to stakeholders for

community MASAS stakeholders comments.

- The elements of the CGA will be integrated into a broader roadmap – particularly our technology community will see how we achieve

the vision – that will be part of the Business Plan. GeoConnections will use the input – with funding available – to progress the Set up steering Committee within 3-6

operationalization of MASAS months.

- Governance – we expect that within a 3-6 months time frame, a steering committee will be set up to provide direction on governance

and policies around the MASAS Develop framework and scope for

- See more of the awareness of the outreach MASAS.

- more work on the sandbox

- Want to do much more exercises, lessons learned, future oriented action and program Need to decide what a core and what

a plug in is in the design of MASAS

PSC

- Instructions are pretty clear in the Public Safety Canada work plan – national MASAS framework – all deliverables in 2011 – have to be If we focus only on core – will push

done by end of the year everything to the provinces – that will

- SOREM EXECUTIVES have given us clear directives for national roll-out delay implementation

- Required: consolidate and synthesize all the information – in a format that they understand

- Michel Savoie work on the standards We must stay focused on who is the

- Filling out the governance model prime customer

Prepared by MCO Business Group Rev. 0 March 14, 2011 Page 28 of 29

Multi-Agency Situational Awareness Systems - “Operationalizing MASAS”



*** Day 2 *** National Stakeholders Workshop Report

Agenda Item Presentation Overview Observations/Comments Recommendations

- Take off this information

- Strong genesis to move forward – some ministers and ADMs level anxious to get this done – this is a winner (Public Safety) First Responders are the source of

one area on which we need to focus our attention is SCOPE – what it is, what it’s not – guides everything going forward including the information we are looking for.

governance – it should be one of the first task – documented and communicated - Will help focus

Develop tools aligned to desired

outcomes.

Technical Session Powerpoint Presentations

 Provide update on system See Annexes 2p5, 2p6 and 2p7

and application design Q&A

 Discuss architecture

approaches Refer to Powerpoint presentation and PDF files for highlights of

 Discuss other the developing technology and the strides made through

specifications: EDXL-DE exercises in Sarnia and Windsor.

Label in Atom GeoRSS,

GeoRSS GML, Tacticial

Situaton Object etc.



Jacob Westfall

NetAlerts Inc.



Doug Allport

Allport Group









Prepared by MCO Business Group Rev. 0 March 14, 2011 Page 29 of 29