Role: Data architect
Goal: Build consensus on 800 data elements
Model: XML Schema, XSLT, HTML, Apache Ant, UML, XDoclets
Results: Although the schemas were technically successful the organization did not have the political clout to convince participants to adopt the CriMNet data standards. Current CriMnet Metadata Repository
Organization: US Department of Justice (2002-2003)
Role: Participant in standards creation, data architect, XML evangelist
Goal: Federal Criminal Justice Data Sharing Project
Standard: Global Justice XML Data Model (GJXDM)
Model: ISO/IEC 11179 Metadata Registry
Result: Since organizations were required to adopt GJXDM to receive federal grants many vendors complied and are using the standard.
Link to DOJ GJXDM Standards
Organization: US Department of Homeland Security (2004-2008)
Role: Extended model, training, implemented registries that use NIEM elements
Goal: DHS Data Sharing Standards for Document Exchanges
Standard: National Information Exchange Model (NIEM)
Model: ISO/IEC 11179 Metadata Registry
Result: Because NIEM standards already had data elements for most common structures (Events, Documents, Organizations, People) and excellent subschema generation tools, organization could focus on extending NIEM structures and implementing precise data exchanges.
Link to National Information Exchange Model Web Site
Organization: Minnesota Department of Education (2005)
Role: Data architect, BA, PM, training, design
Goal: Analytics and reports for No Child Left Behind Data Warehouse
Model: ISO/IEC 11179 Metadata Registry based on NIEM standards
Result: Minnesota Department of Education received a $3.3M Dept. of Education grant for the creation of data warehouse standards based on Kimball conformed dimensions. The metadata registry is in use today.
Minnesota Department of Education Data Dictionary
Organization: Minnesota Department of Revenue (2006-2007)
Role: Data architect, developer, facilitator, project manager
Goal: Precise exchange of homestead and property valuation data
Model: ISO/IEC 11179 Metadata Registry based on NIEM standards
Result: Highly complex XML Schemas with over 250 data elements created with subschema generation tools have successfully validated over 30 million data transfers with no issues related to unclear semantics or vague business rules. Kimball warehouse created to analyze millions of property tax records.
Link to Minnesota Department of Revenue Property Taxation Metadata Registry Web Site
Organization: Thrivent Financial (2007-2008)
Role: Data architect, developer
Goal: Precise exchange of compensation data from 26 administrative systems into central rules engine and Inman data warehouse.
Model: ISO/IEC 11179, SKOS
Result: Metadata registry technology used in all areas of project including controlled vocabulary development, project and task management, approval workflow and business rules development.
Link to a Case Study on a Financial Customer