# Presentation: 294360

##   Mini Kanwal

- Core Data Type - PERSON

***December 02, 2004***

## Core Data Types 

- Core Data Types are the basic business data items that describe  common concepts used in general business activities
- Core Data Types provide a way to capture and maximize the reuse of business information to support and enhance information interoperability across multiple business communities
- Core Data Types contains only the information pieces necessary to describe a specific concept

## Process

- Identify Partners
- DHS - Internal
-  CBP, ICE, US Visit, IAIP, GMO
- DHS – External
- DOJ, DON, DOS, DOD, IC
- Identify Sources
- XSD, DDL, Taxonomy/OWL, Data Model, csv file, BPwin, Data Element Dictionary (DED)

## Core Data Types Of Interest 

- Person
- Organization
- Assets
- Location
- Communication
- Incident/Event
- Screening

## Benefits Of Core Data Types

- Identify Common Groupings
- Information Analysis
- Learning Metadata
- Standard Operating Procedure

## Sources  

- TWPDES (Terrorist Watchlist Person Data Exchange Standard)
- Department Of Justice
- Department Of Defense
- ICE (Immigration and Customs Enforcement)
- UN/CEFACT Person (adapted by Department Of Navy)
- DHS (EA v2)
- Information Analysis and Infrastructure Protection (IAIP)
- Department Of Interior - Sample Person Data Model (under consideration by several Agencies)

## PERSON Overview

***CORE METADATA***

## Variations in PERSON Definition

- TWPDE – A person maintained on a terrorist watchlist is considered to be an individual who is a known or suspected terrorist or criminal and who can either be prevented from entering the country, apprehended while in the country, or apprehended as they attempt to exit the country
- ICE - A foreign born person, who is not a United States citizen, of interest to the Department of Homeland Security (DHS), Immigration and Customs Enforcement (ICE)
- DHS (EA v2) - A person involved with, affected by, interested in, or otherwise of interest to the enterprise
- DOJ – An individual that describes inherent and frequently associated characteristics of a person

## PERSON Model

## Need for Harmonization 

*	*Harmonization is to take a set of proposed Core Data Types, Business Information Entities from different domains, identify differences and similarities between the various submissions, and produce a single, complete cross- domain set

## Procedure for Harmonization 

- Evaluate each submitted Core Data Types for consistently
- Compare the definition and structure of each submitted Core Data Types
- 	If the submitted Core Data Type is the same or similar
- 	- Compare the properties of each to identify any differences
- 	If the submitted Core Data Type has properties missing in the existing one
- 		- Enforce a harmonized form that contains the properties of each
- 	If the submitted Core Data Type is a subset of the existing Core Data Type definition
- 		- Recommend the use of the existing one
- If the definition of the Core Data Type does not match any existing  ones
- 		- Add that as a new core data type

## Sample PERSON -TWPDES (Unicorn)

## Sample PERSON - ICE Data Model 

## Sample Data Model Generated By Unicorn 

## Next Steps

- Continue to outreach
- Harmonization
- Continue evaluate tools for harmonization
- Maintain the standard operating procedures

## QA

- ?

**Questions & Answers**
**             ****Session**