Transcript Banking
Business and Information
Technology Working Together
for the Regulator
Stephen Hord, Director of Product Development – UBmatrix
About Me – Steve Hord
Director Of Product Development – UBMatrix
12 + years in the Technology Industry
Adobe – Print Publishing and PDF teams
Online Travel Solutions Travelport -> Orbitz
XML and Rules Engines
2 + years at UBmatrix
Managed UBMatrix FFIEC Solution
Oversee Development of Solutions for Regulators
Slide 2
Most Recent eBay Purchase
1967 Moto Guzzi V7
Slide 3
Introduction
The Goal of XBRL in the Regulatory
Environment
Slide 4
The Goal of XBRL in the Regulatory Environment
Easier and Faster Data Collection and Publishing
Electronic Forms and Documentation
Electronic Validation (Consistency Across Forms)
Offline Access to Presentation (Forms) and PreValidation of Aceptance Rules
Historic Reference (prior period data)
Slide 5
The Goal of XBRL in the Regulatory Environment
Reduce Risk in Regulated Industries
Reduce reporting irregularities from human error
Consistent collection of data across industries and
segments
Automated Analysis
Faster Data Publishing
Slide 6
How Do I Implement XBRL
The Analyst and the Information Professional
Slide 7
How Do I Do It
Today's Systems
Often Forms Driven (Maybe Paper)
Duplicated/Inconsistent Definitions Across Forms
Programmatic Validation Rule
Hard coded Collection Cycles
Tomorrows Systems
Data Driven Collection
Validation Workflow Driven by the Data
XBRL Ensures Consistent Models
Re-use Data in Multiple Presentations
Slide 8
How Do I Do It
Analysts focus on the content
Focus on the data not the forms
Separate data from presentation
Enforce consistency across your forms
Ensure comparability
Collect supporting data to ensure validity
Publish your rules - not your analysis
Private Rules for internal Use
Public Rules for Document Validation
Slide 9
How Do I Do It
Analysts focus on the content
Create Reportability Rules
Encode your instructions in Business Rules
Reduce Respondent workload from reporting the
wrong forms
If Assets < 100M
Slide 10
How Do I Do IT
IT professionals focus on workflow/collection
Put flexible tools in the hands of the Business
Analyst
Don’t require a programmer to change a form,
presentation, or validation rule
Allow for new reporting segments without new
code
Small banks report quarterly/Big banks
monthly (or by rating etc)
Slide 11
How Do I Do It
Information Architect
Put as much content into the message as
possible - XBRL is the message
Enforce change control and versioning on the
content – Taxonomies have a Development Life
Cycle and Require Project Management
Design for Content Driven Workflow
Use Message Queue
Flexible Storage
Slide 12
Measure Your Success
Key Attributes of a good XBRL System
Slide 13
Success Criteria
Key Attributes of a Good XBRL System
Well Defined Content
Data Elements are defined, documented and
Standardized
Business rules support Data Validation
If you have Forms they are part of the Taxonomy
Reporting Rules Driven Client Software
Automated Acceptance Workflow
Off-line Validation
Workflow Driven by the Contents
Slide 14
Success Criteria
Cost savings to the analyst
Reduced busy work
Increased analyst productivity
Cost savings to the IT dept
Faster data publishing
No retooling for new data/forms/rules
Cost Savings to the Respondent
Real-time Acceptance and Validation
Slide 15
Wrap up
Separate the content of what you collect from the
way you collect it
Analysts focus on the Content
Data model, Rules, Presentation
IT Professional focus on the Collection
Messages and Workflow
Slide 16
XBRL Product Development Cycle
Automated process
Meet deadlines
Taxonomy
Focus on Enhancements
Time: 1 Hour
FormBuilder
Automated processes
Quick checklist review
QA
Banks
Minimal verification
Release
Slide 17
Sample Taxonomy
Slide 18
Sample Form Presentation
Slide 19
Sample GUI
HTML GUI file added into FormBuilder
Slide 20
Contact Information
Steve Hord
UBmatrix
(425) 285-0200
[email protected]
www.ubmatrix.com
Mark Fahlsing
Jack Henry & Associates
(888) 345-4649
[email protected]
www.jackhenry.com
Slide 21