DHS US-VISIT Standards for 

Multi-Modal Biometrics William Graves US-VISIT/Information Sharing and Technical Assistance International Biometric Performance Testing Conference 2012 
Why Use Multiple Modalities? 

• Improve identification accuracy • Allow capture of an alternative biometric if primary biome

poor quality or missing 

• Mitigate the risk of fraud or spoofing with a single biome

• Provide options for capture if there are environmental or 

constraints 

• Enhance compatibility with other biometric identification 

2 
US-VISIT Multi-Modal Limited Product

(LPP) 

 Build back-end capabilities to support multi-modal services 

VISIT customers 

– 1:1 Verification with face and iris images – 1:N Identification with iris images – Store and retrieve for DNA, palmprint, and SMT 

 Build a transmission specification to support multi-modal s

data sharing with multiple stakeholders 

 Front-end technology agnostic – accepts standards-confor

and iris images output by any device 

 Evaluate matcher performance on biometric data submitte

customers 

3 
Modalities for US-VISIT/IDENT 

4 

• Iris, Facial, Palm print, DNA profile, and Scars, Marks and

Tattoos (SMT)
LPP: Initial Stakeholders 

• CBP Office of Border Patrol (OBP) 

– Improved face image capture and dual iris capture in OBP op

southwest border 

– 1:1 verification for face and iris – 1:N iris identification – Capture devices: 

• Iris ID TD100 • SEEK devices from DoD 

• CBP Office of Field Operations Global Entry (GE) 

– Incorporates iris capture at two GE enrolment centers 

• Iris ID TD100 

– Adds iris matching capability to GE kiosks at two POEs (Dulle

• AOptix VM for kiosk 
Iris 

Matcher

(Matcher 1)

LPP: Architecture 

Transactional 

Services 

Analytical & 

Managerial Services 

S E 

C U R 

I 

T 

Y S E 

R 

V 

I 

C 

E S 

Biometric Matchers 

US-VISIT Enterprise Service Bus (ESB) 

Reporting 

Services 

Local Service Bus 

Security Boundaries Interaction Layer Integration Layer Application Layer Data Layer

Audit 

Logs 

Data Security / Privacy 

Integrated US-VISIT Web 

Interface 

Biometric Middleware 

Image 

Repository 

Reporting 

Database 

US-VISIT Data 

Assets 

Transaction 

Manager (TM) 

ESB-IDENT Exchange 

Messages (IXM) 

Iris 

Matcher 

(Matcher 2) 

Facial 

Matcher 

(Matcher 1) 

Facial 

Matcher 

(Matcher 2) 

Client Solution 

3 

4 

6 

2 

5 

Iris 

Matcher 

(Matcher 1) 

7 7 7 7 

1 
LPP: Iris and Face Matchers 

• Iris Matchers 

– Iris ID matcher SDK and DaonEngine Snap-ins (1:1 and 1:N m

snap-ins and transform snap-in for template generation) 

– Iritech matcher SDK and DaonEngine Snapins (1:1 and 1:N m

snap-ins and transform snap-in for template generation) 

– Each supports gallery up to 30,000 iris pairs and 1:N and 1:1 

• Facial Matchers 

– NEC facial matcher and DaonEngine Snapins (1:1 matching s

transform snap-in for template generation) 

– Cognitec FaceVACS SDK with DaonEngine Snapin (1:1 matc

and transform snap-in for template generation) 

– 1:1 verify service only 
Limited Production Pilot Schedule 

• Design 

– Completed March 2010 

• Development 

– Completed October 2010 

• Testing 

– Product Application Testing (PAT) – Completed July 2011 – IV&V – Completed November 2011 – Product Integration Testing (PIT) – March 2012 – Performance Testing – Completed October 2011 

• Deployment 

– Production Deployment – February 2012 – Operational Evaluations – March 2012 
9 

Standards for Sharing Multimodal 

Biometrics 
IDENT eXchange Message (IXM

 IXM is the IDENT XML biometric 

standard messaging format for interacting with US-VISIT IDENT Biometric Services 

10 
IXM Goals & Principles 

 Establish common interfaces 

– Develop common interface specifications and mechanisms for US

 Support DHS/US-VISIT SOA Initiative 

– Develop IXM using XML/SOAP technology – Use existing Web services specifications (SOAP, WSDL, WS-Add– Support SOA Messaging Protocols and NIEM Conformance 

 Support DHS XML biometric standard messaging format  Leverage data exchange models 

– NIEM, ANSI/NIST-ITL 

 Promote interoperability between US-VISIT and others 

– Allow for XML file format, EFTS or EBTS 

 Leverage existing technology for binary data transmission 

– XML-binary Optimized Packaging (XOP) 
IDENT IXM Development 

5.0 

• GJXDM (Global Justice) based • Some NIEM elements • Fully backward compatible 

GJXDM/NIEM 

• Incorporates new 

modalities (palm print, SMT, iris, and DNA) 5.5 

NIEM Conformant 

6.0 

• Adds new services • Fully NIEM 3.0 conformant 

ANSI/NIST

ITL 1‐2011

NIEM

Subset

IDENT

Extensions
IDENT IXM 5.5 Multimodal Messag

 Based on a legacy data model GJXDM (Global Justice)  Updates select service messages and data elements to int

additional modalities for LPP 

 Services: Identify, IdentifySync, Verify, VerifySyncand Retrie

messages 

 Minimizes impact of existing IXM subsystem while introduc

elements 

 Uses ANSI/NIST ITL 2-2008 elements to satisfy requiremen

exchange of new modalities for LPP 
Moving forward to IXM 6.0 

 Maintains the data elements needed to meet technical and b

requirements 

 Replaces all GJXDM elements with NIEM  Fully NIEM 3.x conformant Domain model and subset schem Uses existing elements within NIEM core and domains  Extends NIEM where needed for IDENT  Provides services through IEPD Exchange schemas  Simplifies and extends IXM 5.X syntax 

• Increase flexibility and scalability 

 IXM 6.0 is NOT backward compatible with IXM 5.x  Provides improved messaging: 

• Easier client side development • Improve internal message transport • Enhance data sharing and interoperability 
National Information Exchange Model 

 Supports information sharing with enterprise-wide informati

standards and processes 

 Built on demonstrated success of GJXDM (Global Justice E

Model) 

 Common lexicon  Repository of information exchange packages  Increases and leverages “re-use” of 

– Existing Standards – Data Related Technology – Existing Infrastructure – Knowledge/Experience – Multi-organizational Interactions and Relations 

– Sponsored by US Dept of Justice, DHS and several other a
NIEM Benefits 

Results achieved with full NIEM adoption: 

– Measurable cost savings (both initially and ongoing) by utilizin

methodologies and reusable data exchange components and 

– Reduced development and deployment times by reusing exist

of information. 

– More efficient structure for information sharing with DHS Comp

semantic integrity across information systems. 

– Better decision-making from more timely, accurate, and compl

information, ultimately resulting in enhanced public safety and security. 

– Will, the first bullet above originally said, “For US-VISIT, th

results will be achieved” 
NIEM Domains 

NIEM is currently comprised of several key Domains such as the justice, emergency and disaster management, intelligence and homeland security enterpcan be defined as a sphere of activity, concern, or function. For purposes of Nrefers to a business enterprise broadly reflecting the agencies, units of governmefunctions, services, and information systems which are more or less organized meet common objectives. 

Properties Types 

NIEM 2.0 4,291 1,601 

NIEM 2.1 5,692 2,157 

+33% +35% 

NIEM 2.1 was published on 9/28/2009. Release of new domains, update of curreon cross domain info exchanges. Biometrics introduces a new domain for NUS-VISIT is the Biometrics Domain Stew
NIEM IEPD 

 An IEPD is a specification for an Information Exchange Docume

Package and defines a particular data exchange. It is generally of files that describe the structure of the information being exchadocuments that explain the business context and usage 

 Artifacts make up an IEPD: 

– Exchange files – the files that describe the possible arrangement 

information in a valid exchange document using a common vocab

– Documentation – artifacts pertaining to and supporting the busin

the exchange (definitions, processes, rules, etc. 

– Catalog Files – specification artifacts that are needed to meet the 

requirements which state that an IEPD should be portable, self-codocumenting and able to be registered anywhere 

18 
NIEM IEPD Development Process 

Person Name 

LastName FirstName MiddleName 

Subject Person 

PersonDriversLicenseID 

Activity 

ActivityIdentification 

CrossingEncounter 

Date CrossingTypeCode 

SubjectVehicle 

ConveyanceIdentification 

TravelDocument 

EffectiveDate ExpirationDate IssueCountry 

Document 

DocumentIDentification 
IEPD Benefits 

 Common message exchange  Availability of NIEM support tools and training  Accessibility to nationally known vetted data requirements 

implementers 

 Semantic Integrity: Coherent & consistent information exch

standards 

 Enhances organization and scalability through known NIE

processes 

20 
NIEM/IXM Mapping 

IXM 5.5/5.0 Elements

Semantic and structural equivalent, but NIEMvs GJXDM

Same element as IXM 5.5

IXM 6.0 Ele

PersonBiometricDetailsBiometricDetailsPerson (GJXDM) Person (NI

Deprecate, redundant and GJXDM based

RetrieveIdentity RetrieveIde

IXM 6.0 Element is structurally different andNIEM conformant, but semantically equivalentSemantic and structural different and NIEM

conformant

Encounter (GJXDM) Encounter (

BiometricD
IDENT IXM Supported Biometric Sta

• Iris 

– ANSI/NIST-ITL 2-2008 and 1-2011, Type 

17 

• Face 

– ANSI/NIST-ITL 2-2008 and 1-2011, Type 

10 

– ISO/IEC 19794-5 – ICAO 9303 

• Future • Scars, Marks, and Tattoos (SMT) 

– ANSI/NIST-ITL 1-2011, Type 10 

• Palm Print Standard 

– ANSI/NIST-ITL 1-2011, Type 15 

• DNA 

– ANSI/NIST-ITL (Annex to be published for ANSI/NIST-ITL 1-2011) 
Contact Information 

 William Graves  Chief Biometric Engineer  US-VISIT Program  Information Sharing and Technical Assistance  William.graves@dgs.gov  Tel: 202-298-5230