2. Project Scope
• Define a Architectural flow diagram that
provides for basis for data governance, data
quality and impact analysis
• Create a framework to report on
inconsistencies in data (Initial emphasis on
Accounts)
3. FISMA
• The architecture provides a foundation for verifying
that Accounts are deleted after the employees leave
the Gallery
• The Exceptions Facility, Provides the ability for a
application administrator to request that an Non-AD
account be left on file
– Audit trails
– Non Standard accounts (e.g. TDP as Custodian)
– CIO can approvedeny and give timelines for resolutions
• Focus of first phase of the initiative
4. Why Consistency Reports
• Common Practice (Asset Inventory, …)
• Ensures that data is corrected in the correct
manner
• Re-validates automated processes
• Some changes need to be informed to system
manager (e.g. They should know if someone
has a new last name)
• Links into existing manual pratices
5. General Data Quality Process
1. Identify data stores (Based on priority)
2. Identify authoritative data
3. Identify Interfaces replicated redundant
data
4. Identify consistency analysis process
5. Correct and continuous monitoring
6. Identify data stores
• 1.1. Create list of all know data applications
– Define the name of the data application
– Define the contacts related to the application
• TDP Contact
• Application Administrator
– Categorize the application
7. Identify data stores
• 1.2. Link data into data flow representation
for a visual analysis on enterprise data flows
8. Identify authoritative data
• 2.1. Review Application data to determine
– What type of data is supported
– Is data authoritative
9. Identify Interfaces replicated
redundant data
• 2.1. Review Application data to determine
– Where the data is sent
– Where the data is received from
– Data Quality
– Note: Source assumed by reverse lookup of target definitions
10. Identify Interfaces replicated
redundant data
• Diagram linkages between data stores for
visual review and impact analysis
11. Identify consistency analysis process
Review participating data sources and
determine how to define consistency
* At this point only “SQL” methods are used.
12. Correct and continuous monitoring
• Inconsistencies are periodically sent to end users for “correction” or
“exceptions”
• Valid exceptions may be
– “Supervisor Accounts Outside Active Directory” (e.g. TMSAdmin)
– Ex-Employees with data attached to userid
– Contractor or testing userid
