I hope this group recognizes that there
are additional vendor organizations that represent the target community.
My perspective is that EIC and the IJIS Institute should be working
closely together on these kinds of efforts, and that both of them together will
provide you with a much more significant and appropriate base to your effort.
Paul S. Embley
Practitioner Resource
Group
G&H International
Services, Inc.
202.250.3498 (office)
202.288.3380 (cell)
502.695.0055 (fax)
pembley@ghinternational.com
Some suggestions:
Current Document Wording:
The Contractor may be required to join the Emergency Interoperability
Consortium (EIC) (www.eic.org) which DHS has a Memorandum of Understanding with
and communicates to the vendor community concerning the EDXL standards.
Suggested Change:
The Contractor is encouraged to join the Emergency
Interoperability Consortium (EIC) (www.eic.org) which DHS has a Memorandum of
Understanding with and communicates to the vendor community concerning the EDXL
standards.
Should the version numbers of DMIS, CAP,
and EDXL be included in the document? I believe they should be included.
Who is responsible for checking the vendor
for compliance with EDXL? Will there be an independent certifying group (such
as Wi-Fi) to ensure functional compliance?
Regards,
Tom Merkle
CapWIN: www.capwin.org
Phone:
(301) 614-3720
Cell Phone: (240) 375-1966
Fax:
(301) 614-0581
e-mail:
tmerkle@capwin.org
CapWIN
6305 Ivy Lane Suite 300
Capital Office Park
Greenbelt, MD 20770
From: Elysa
Jones [mailto:ejones@warningsystems.com]
Sent: Monday, September 12, 2005
6:25 PM
To: emergency@lists.oasis-open.org
Subject: [emergency] Fwd: OASIS EM
TC Category for EDXL standards
TC Members, I
received the following email from Bill Kalin representing the DHS/DM
program. There is specific grant guidance language proposed for our
review. I would prefer discussion begin on the list and then we can take
it up at the next regular TC call 9/20. Elysa
Delivered-To: ejones@warningsystems.com
From: "Kalin, Bill" <Bill.Kalin@associates.dhs.gov>
To: "'ejones@warningsystems.com'" <ejones@warningsystems.com>
Cc: Matt Walton <mwalton3@gmail.com>, "Hines, Chip"
<Chip.Hines@dhs.gov>,
"Baker, Ashley"
<Ashley.Baker@associates.dhs.gov>,
"McIntyre, Robert"
<Robert.Mcintyre@associates.dhs.gov>,
"Wood, Mark"
<Mark.Wood@associates.dhs.gov>
Subject: OASIS EM TC Category for EDXL standards
Date: Fri, 9 Sep 2005 10:11:51 -0400
X-Mailer: Internet Mail Service (5.5.2657.72)
X-Virus-Scanned: ClamAV 0.83/1071/Fri Sep 9 06:39:47 2005 on
magneto.pns.networktel.net
X-Virus-Status: Clean
X-NAS-Bayes: #0: 0; #1: 1
X-NAS-Classification: 0
X-NAS-MessageID: 50184
X-NAS-Validation: {4FFF9F5B-0862-47C2-858F-59F6F684AC80}
Elysa - We have been asked by the Office of Management and Budget (OMB)
to create standardized RFI/RFP language that federal agencies would required to
use when seeking to purchase an incident management software application.
We want to be able to refer to EDXL as a single set of standards as opposed to
listing them all individually, including CAP. This is the first step in
creating common grant guidance language that will be required when local,
tribal and state governments are seeking to purchase incident management tools
with DHS grant money. We believe this will strongly facilitate the
adoption of standards within the vendor community and further develop this
emerging market.
What can be done via OASIS to help create this single type of category under
the OASIS TC? I am attaching a draft of proposed language for the
RFI/RFP's which includes a desired reference to the OASIS web site.
Bill Kalin
Disaster Management eGov Initiative
Office of the Chief Information Officer
Emergency Preparedness and Response/FEMA
Department of Homeland Security
(202) 646-4347
bill.kalin@associates.dhs.gov