[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [emergency] EM TC 04-03-03 Meeting Minutes - Revised
EM TC Face-to-Face Meeting Minutes
April 3rd, 2003
Arlington, VA
GIS SC
Bill/Eliot: looking for input from the group. Did not have a charter to present. Anyone who has use cases for geospatial data should share
· Eliot: there may be an educational perspective - that might be what is really needed. Bill noted that there were white papers they could share with the group. Dan suggested that the SC could develop use cases and requirements and then find standards that overlay or fit.
· Allen: determining how GIS fit in was the reason the SC was created. Most of the members of the TC didn't have the experience to define the test cases, although we fully respective and are aware the role GIS plays in the TC.
· Bill: really wants use cases to drive work. Dan noted that there are existing standards that need to be explained. Geospatial part comes up with data model of what emergency management is and what GIS is. Need to ensure that the rest of the technical committee handles this right.
· Gary - other subcommittees to identify functional need and how GIS is applied. Also mentioned notion of NIMS.
· Rick - Very specific and applied point of contact but need to know what to apply to. NIMS is driven by ICS, doesn't it make sense to adopt?
· After a bit more discussion the SC reached the conclusion: collapsing in on threemain things that drive what the charter should be within the group.
o Educational
o Advice to other SC's
o Stay on top of other needs/efforts
· Allen: maybe we should have called this the GIS exploratory committee.
ISO 11179 Presentation (Experience with Data Elements: ISO 11179
John Silva: general lesson's learned presentation on 11179 within the National Cancer Institute project - needed to create CDE (Common Data Elements). Could be very costly to do, yet if there is funding available - this would be good. First step was to agree upon a common data element exchange. The purpose of ISO 11179 was to provide a starting point for data elements:
· identifying
· defining
· registering
· classifying
· managing
· standardization
· integration
Gary - do we want to run a registry? Costs and benefits can be defined.Dan thought registry would be a better follow on after we complete initial scope of work.
John said we need to find a way to get funded. May need to exploit data elements. Eliot - maybe we can take a stand on registries/repositories (e-gov). Right now OASIS is depending upon ebXML. Gary can the government sponsor the registry. US government running many trials including Justice, FAA, Census and EPA. Eliot - e-Gov won't endorse. John said that CommerceNet defines business processes. They may be interested in assisting.
Allen: based on experience, any thoughts on how to best utilize ISO 11179? Response is that if we plan on using a lot of other standards (aka referencing and leveraging them), then there might be a good use for it. However, this might be more of an OASIS thing to manage.
Art: Can you make any recommendations on some of the things we should consider as we work on our standards? Response: naming conventions. And use as guidance.
Presentation will be posted to EM TC OASIS site.
Breakouts
Due to time constraints Allen decided to skip the liaison and outreach sectionof the agenda. He will work with each subcommitte chair to identify the groups they need to liaison with. Each subcommittee will provide their own relevant notes to be published. After the breakouts, each subcommittee chair gave a brief summary of their individual meetings. For those members not in attendance at the meeting, please select a breakout group that you would like to belong to and email the chairperson.
Infrastructure
Members include:
Rick Carlton - chair (rcarlton@eteam.com)
Steve Siegel - RAMSafe
Gary Ham - DHS
Mark Benemerito - SunGard
David Hall - Federal Support Systems
Jerry Weltman - Innovative Emergency Systems
Allen Wyke
The group agreed to rename the subcommitte to EM Infrastructure Framework The scope of work: Currently, there exists a problem in choosing the appropriate set of individual standards to achieve a particular emergency function or capability. For instance, what components are currently available and are they valid in the context of an interoperable emergency management system?
The EM Infrastructure Framework subcommittee is a horizontal effort that will cross multiple standards and is therefore an EM Metadata Standard. This subcommittee will research, analyze, recommend, and organize a series of infrastructure components in order to bind various standards providing connectivity between systems. Rick will review eGov before finalizing deliverables.
Notifications, Methods and Messaging
Members include:
Art Boterell - Chair (acb@incident.com)
Joyce Kern - SunGard
Bosa Naustion - MTG
John Silva - SCS
Art reported that the committee didn't change scope. Deliverables will include:
· puruse standardization of a common alerting protocol (maybe based on work done by CAP)
· standardize a subset of ICS forms
· develop implementation of incident notification format
GIS
Members include:
Eliot Christian - Co-chair (echristian@usgs.gov)
Bill Schroeder - Co-chair (bschroeder@esri.com)
Dan Danko - ESRI
Mike Walker - Blue292
Eliot reported that the GIS subcommittee has three goals:
· GIS advice/educational
· Geospatial input from the TC
· Targeted outreach
ESRI is going to submit some symbology work.
Additional Notes
A rather large use case would be NIMS. SARS is another potential use case. Could involve a UDDI (or other) type of registry. Should consider multiple "views", such as an ICS view of these components. Deliverables will follow after Rick can review eGov.
Discussion on when/how subcommittees to meet. Was suggestion to replace weekly TC meeting with subcommittee meetings. Gary suggested that we have a half hour TC meeting followed by an hour subcommittee meeting. To be further discussed and finalized at next teleconference call on Tuesday, April 8.
Allen Special thanx to David Hall for hosting the face-to-face, and to Cathy Subatch who helped ensure we had the proper sugar and caffeine to keep us awake and energized for 7 hours.
Action Items
· Allen - post Cooper presentation to TC member page
· Allen - work to create budget for proposal to submit to Cooper
· Allen/Cathy - create one page description about EM-XML Consortium
· Allen/Rick/Eliot - Investigate how NIST works (to use for certification). Will it be too costly or will benefit outweigh
· Allen - liaison with e-Gov interoperability subcommittee
· Allen/Art - work on how to get CAP and OASIS to work together
· Allen - review OASIS documentation guidelines and templates. Forward a copy to group. Need to start creating a Guidelines document that tells the outside world how we build standards (i.e., details that are more granular than the basic OASIS templates, such as potential WAI support).
· Membership - select subcommittee to work on (if not at face-to-face meeting). Review charters and send email to appropriate subcommittee chair.
· Allen - talk with OASIS and get their thoughts on ISO 11179 as well as research in general terms for group. John, Eliot, and Gary to help.
· John Silva - post ISO 11179 presentation to OASIS EM TC site
· Allen - think about how to best utilize the "normal" meeting time. Talk with people at OASIS.
· Eliot/Rex - draft Advisory Note for vote by TC
· Rick - review e-Gov infrastructure charter/document and compare it to what he had in mind, and then make a recommendation as to next steps.
Next Meeting
The next meeting will be Tuesday, April 8th at 1:00pm EST/10am PST
Dial in: 1.800.453.7412 Access Code: 604776
Cathy M. Subatch
E Team Inc.
818.932.0660 x248
310.770.6885 (mobile)
csubatch@eteam.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]