NIEM : Is it a Model, a Methodology, or a Community?
Late last month I joined over 500 people gathered at the National Information Exchange Model (NIEM) annual Training Event in Philadelphia to discuss progress in NIEM adoption, hear about tools that have been developed by government and industry to facilitate NIEM processes, and learn about best practices developed by the NIEM community. In addition to 20 federal agencies and 40 state and local government agencies, both Canada and Mexico were represented by senior government IT executives. A range of very diverse projects were discussed at the Philadelphia event, including the initial Canada-USA-Mexico data exchange project that will facilitate sharing of stolen vehicle data beginning in 2012.
So, what is NIEM and why all the buzz?
NIEM is, at its most fundamental level, a U.S. Federal government initiative that promotes the accurate exchange of data between organizations through the use of Extensible Markup Language (XML). This may sound elementary - after all, this was what XML was intended to be used for since its approval as a W3C recommendation in 1998. However, when two or more participants in a data exchange begin to work through the 'details' it becomes readily apparent that the vocabulary that one uses internally may be quite different from that used by the other. For example, does the database field identified as 'Name' by one entity refer to a person or something else? A person's full name? Including suffixes? Is the database field 'surname' equivalent to the second agency's database field 'Last_Name' or a local police department's field 'perpetrator'? Is a single agency's internal database design guideline consistent across various databases from which data might be pulled for sharing as a consolidated record about some individual?
I could go on but I think you get the idea: There is a substantial risk that without some collaborative effort to agree on these details that the true meaning of the data being exchanged might be used in error. Consider a medical data exchange for dosage amounts given to a soldier moving through the healthcare system where the DoD and the Veteran's Administration have a different understanding for dosage units for a medication - mililiters, microliters, or drams. A lack of consistency in dosage unit agreement could have serious consequences.
The Federal Enterprise Architecture Data Reference Model was originally intended to address these issues. However, it became 'a bridge too far' with respect to obtaining agreement among all agencies with respect to consistency sufficient to facilitate data exchange. NIEM is a smaller bite at the apple in that NIEM segregates data exchange participants into communities of interest that work out vocabularies and dictionaries among themselves, with only a small core set of definitions being common to all domains (the NIEM Core). Current NIEM domains include Biometrics; CBRN (Chemical, Biological, Radiological, Nuclear); Children, Youth, and Family Services; Cyber; Emergency Management; Immigration; Infrastructure Protection; Intelligence; International Trade; Justice; Maritime; Screening (Homeland Security); and Human Services.
Oracle, one of DLT Solutions' major vendor partners is investing in supporting government adoption of NIEM. Oracle has established a special web section devoted to NIEM. These investments include the establishment of a dedicated NIEM team within Oracle Public Sector, participating as a sustaining member of the Integrated Justice Information System Institute, providing a NIEM Starter Kit to the Justice and Public Safety (JPS) community, and by providing primary support for the ongoing development of the Content Assembly Mechanism (CAM).
CAM, a free open-source tool that allows organizations to quickly build NIEM-based exchange schemas and NIEM Information Exchange Package Documentation (IEPD) using a drag-and-drop GUI, was presented at the Philadelphia NIEM Training Event by David Webber. A complete description of CAM and a download link can be found here.