Hi Jerome,
Apparently I was not understanding you. However, to address a
couple of issues. I am not attempting to type anything myself. I
am attempting to make it possible for anyone who types or has
typed resources to make their typing available and citable. As
long as the documentation for any given resource typing is
available, I can use it in EDXL.
So to reiterate, I'm not out to retype anything, just to make it
possible to translate between existing typing systems, whether it
is the european "Tactical Situation Object" being reworked by ISO
that produces a resource coding and typing system even more
complex that FEMA's, or FEMA's or anyone else's.
All anyone needs to do is publish their typing system. If they
don't, it will be difficult to use their resources, but even then,
if any jurisdictions purchases and uses any given resource, it
will eventually be possible. The only real problems are companies
attempting to manipulate the marketplace to create de facto
staandards by becoming monopolies (and this is clearly not you,
Jerome).
Anyway, I'm not competing with anyone here. I'm trying to make
things work, regardless.
Cheers,
Rex
On 10/16/2012 10:45 AM, Jerome Hamilton wrote:
Rex and
David,
I'm confused here...
Reiterating the NIMS
appointed subject matter experts comments "forget the
product name TractorFax". A resource is a resource, no
matter the resource (prescription drugs information
sharing). Hence the ongoing, never ending expansion of the
original 120 resource typing definitions. In
addition, FEMA's 2011 - 2014 Strategic Plan Initiative #1
(whole community approach to emergency operations) is
collaboration among public/private/NGO stakeholders-
beginning at the local level and in a continuum to state and
regional levels should the need arise. Right?? And now
you're attempting to resource type the ever changing world
of prescription drugs (and its ongoing medical research).
Resource typing prescription drugs (or untitled heavy
equipment resources) is a waste of time and money... Plus
continuing down this path makes it impossible for incident
command & resource managers to be the turn to experts in
all available public/private/NGO inventoried resources...
Impossible period.
Here's a question for you experts: "who is the best
choice regarding information surrounding available
resources?" The answer is: "The actual owner of
the resource being provided!!!"
David, your work here is another attempt in
reinventing the wheel since deployment ready TractorFax has
already been there, done that!
Rex, you mentioned IRIS, we know that IRIS was
developed by SAIC and that SAIC Corp. was contracted to ramp
up NIMS SC. So in essence, IRIS/SAIC (our competition)
has peeked under the NIMS evaluated TractorFax hood. It's
apparent IRIS liked their peek under our hood. This maybe
why NIMS has been "absorbed" by P-TAC.
It's also noteworthy that IRIS is rejected at the
local level, mainly because those officials view IRIS as "a
Internal Revenue System/IRS type system for reporting
resources in-resources that don't actually belong to local,
state, nor regional stakeholders and they're dealing with
resources they know little to nothing about".
We know what we have to offer; so we've been told (and
documented) by appointed Subject Matter Experts. Deployment
ready since early 2008 and now that the market has presented
itself; we simply seek funding and that first "end user" in
order to fulfill existing shortfalls within.
Then we can address the reality of a "BEOC in a Box,
one that can be unfolded in times of need, then folded away
and readied for the next event".
Hope you guys find this helpful and informative!
Always available,
Jerome
On the phone: 501-259-5007
Rex,
Please take a look at the new SQL -> XML
feature in CAM and the Open-XDX component Oracle has
developed.
If this can help provide low
cost information sharing API - would be very happy
to assist in packaging that.
We have one sample package done for PMIX
(Prescription Drug information sharing) - that can
serve as a guide.
Our estimates show you can build this stuff in
matter of hours - rather than weeks of traditional
hand coding.
By leveraging the web deployment metaphor and
providing these APIs - should be much easier for
emergency response sources to integrate together
with either publish/subscribe or query/response
services.
David Webber
--------
Original Message --------
Subject: Re: [emergency-comment] NIMS STEP comment
- TractorFax
From: rexbroo < rexb@starbourne.com>
Date: Tue, October 16, 2012 11:49 am
To: emergency-comment@lists.oasis-open.org,
emergency@lists.oasis-open.org
Thanks
Jerome,
This is important information for us to have, so
I am copying the OASIS EM TC list with this
reply.
While I can only speak for myself, I think that
the gap analysis I assume you have conducted to
fill "shortfalls" in EDXL coverage of incident
management systems could be perhaps one of the
most important tools we can support. Since NIMS
STEP has been absorbed by P-TAC Center, I will
add this to an ongoing ticket I have open with
P-TAC concerning a FEMA Grant-supported project
that uses Incident Resource Inventory System
(IRIS).
What I am working on is third-party translation
ontology that can provide EDXL-compatible
terms/datatypes for Resources in the FEMA
Resource Typing system which the firestations we
are supporting need to coordinate and align with
their own industry-supplied inventories. It is
no easy task getting interoperability at this
level.
I understand the problem only too well. Here in
California the company-product attempting to
build a monopoly-based interoperability by
giving away the beginners-level version of their
software product is making substantial inroads
that I consider a long-term recipe for disaster,
but I won't go into details, in order to avoid
arguments and entanglements that would only make
the situation even less solvable.
However, please keep beating the drums. In the
long term, the only way we can deliver
interoperability to the Emergency Management
field is through is to provide low-to-no cost
software systems at a basic level that products
such as you provide can build upon, and that is
the approach I am taking while working to
improve the overall situation with standards.
Speaking of Standards, we are looking for
vendors who are not necessarily OASIS members
who can vouch for using the EDXM-SitRep v1.0
specification so we can move forward to an
OASIS-wide vote for Standard status. If you
could help in that effort, we would be grateful.
However, in the meantime, you have brought
forward a set of issues that needs to be
addressed and I thank you again for that.
I wish I could be more hopeful, but I do think
that if we can provide those low-cost
alternative for local jurisidctions, they will
work with us to build more advanced systems
which implement genuine interoperability for the
long term.
Thanks,
Rex Brooks
On 10/16/2012 7:20 AM, Jerome Hamilton wrote:
Dear OASIS TC;
We, NIMS STEP
evaluated TractorFax Technologies, were
evaluated back in 2008 against NIMS
standards and criteria which is apparently
guided and driven by underlying OASIS
standards for interoperability, scalability,
flexibility, and affordability across the
board, as I understand things.
With that said, in the beginning (2008)
the NIMS STEP
evaluation process had a slight sense of
urgency. Now, 5 years later, this whole
process has fizzled out due in part to the
fact "NIMS
evaluated TractorFax fulfills longstanding
shortfalls and missing capabilities within
real world incident management/emergency
operations following OASIS standards and
criteria. If in fact public/private/NGO
collaboration remains key, then TractorFax
is in fact the technical environment where
all 3 can co-exist!
The NIMS STEP
process (utilizing OASIS standards and
criteria) has created a catch 22 offering
nothing in the form of funding and
implementing recommended pilots, even after
appointed subject matter experts asked this
vendor to document local, state, and
regional recommended pilots for bringing our
IT product from "Tech Lab" to "End User
reality"... What's up with that?
The situation has created a wonderful
deployment ready "all-in-one" solution to
local, state, and regional level incident
management/emergency operations shortfalls,
however, based on my first hand experience
since day one, local officials rely on their
state agency as the gatekeeper to fulfilling
their shortfalls and understanding the real
underlying brilliance
of NIMS.
Yet, SAA and State
Agency Directors are intimidated and
confused, thus rejecting any federal (NIMS/OASIS compliance)
standards and criteria; no matter how brilliant
the solution. And sadly most of these
state/governor appointees have their
own underlying agenda...
The bottom line here is; the InterAgency
Board (IAB) has
approved NIMS evaluated
TractorFax for 3 Standardized Equipment List
(SELs).
And according to our sources "TractorFax is
perfectly aligned with DHS/FEMA 2011
- 2014 Strategic Plan Initiative #1- the
whole community approach to emergency
operations". All the while (5 years now),
TractorFax recommended pilots have yet to be
funded and implemented at any level while
property and lives are at stake... Shame on
all.
In conclusion, I simply wish to get
TractorFax out of my in-box and
off my desk. Can you help? Any
and all suggestions are welcomed; but I
think OASIS TC involvement (oversight) is
called for... Otherwise there's no need for
TractorFax being evaluated against stringent
standards and criteria... even when the
market has finally presented itself...
Always available,
Jerome D. Hamilton, CEO
NIMS
evaluated TractorFax Technologies
Communities COLLABORATIVELY Sharing
Resources Securely
501-259-5007
--
Rex Brooks
Starbourne Communications Design
Email: rexb@starbourne.com
GeoAddress:
1361 Addison St. Apt. A
Berkeley, CA 94702
Phone: 510-898-0670
-- This publicly archived list offers a means to provide
input to the OASIS Emergency Management TC. In order to
verify user consent to the Feedback License terms and to
minimize spam in the list archive, subscription is
required before posting. Subscribe:
emergency-comment-subscribe@lists.oasis-open.org
Unsubscribe:
emergency-comment-unsubscribe@lists.oasis-open.org List
help: emergency-comment-help@lists.oasis-open.org List
archive:
http://lists.oasis-open.org/archives/emergency-comment/
Feedback License:
http://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines:
http://www.oasis-open.org/maillists/guidelines.php
Committee:
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=emergency
Join OASIS: http://www.oasis-open.org/join/
--
Rex Brooks
Starbourne Communications Design
Email: rexb@starbourne.com
GeoAddress:
1361 Addison St. Apt. A
Berkeley, CA 94702
Phone: 510-898-0670
|