DataArc 360™ (DA360) powered by Aperture Data Studio is designed to help North American credit data furnishers meet their obligations under the Fair Credit Reporting Act (FCRA) by identifying issues within their Metro 2® files prior to submitting the information to the credit reporting agencies like Experian, TransUnion, and Equifax.
Data submitted electronically to the credit bureaus should follow the Metro 2® standard, which is documented in the Credit Reporting Resource Guide (CRRG). Aperture Data Studio can import and parse Metro 2® files containing hundreds of columns and millions of records. These files are evaluated against over 100 checks and rules that help identify non-conforming data in the base segment.
The results of the assessment are populated into an interactive Dashboard that highlights key statistics and allows users to drill down into specific records with data issues.
The DA360 Solution contains pre-built objects (including Spaces, Datasets, Functions and Dashboards) that must be deployed to your Data Studio environment before your Metro 2® data can be evaluated.
Go to System > Solution Deployments then Deploy or Upgrade the latest version of the DA360 Solution. This can take a few minutes while everything is set up.
There are two user groups that your administrator or the user deploying the Solution should add users to:
DA360 includes over 100 rules that check for inconsistencies with the definitions outlined in the CRRG. There are additional supporting functions for dates, regular expressions, and basic formatting.
The DA360 Portfolio Space contains these 3 Workflows:
The DA360 Dashboard displays the following:
After DA360 has been deployed, the preferred method of ingesting Metro 2® files is through a Dataset dropzone, which automatically polls a specific directory and transfers any uploads from that directory to Data Studio.
New Metro 2® files can also be uploaded directly through the user interface by adding a Dataset but you may experience slower performance.
A professional services consultant will assist with the following dropzone configuration:
After data has been ingested, the fields in the Dataset must be mapped to the base segment fields configured for DA360, which lists the fields in alphabetical sequence.
Only perform these steps when setting up the Dataset for the first time or if the schema in the Metro 2® file changes:
Once your file has been loaded and Mapped successfully, you can refresh your Dashboard data by running these Workflows:
Each stage can be run manually for testing or troubleshooting purposes, but longer term it is more efficient to set things up to process automatically.
The recommended approach to running DA360 is to connect the three Workflows in a single automated process. Each step can be run manually for testing or troubleshooting purposes.
A professional services consultant can assist with the following configuration to automate DA360:
To start investigating, open the WF 1 Validation Results by Rule Drillable widget, clicking on the expansion icon in the top right corner of the widget.
To isolate the records that failed for a specific rule, right click on the rule, and select Failing Rows.
If the columns relevant to a rule are not readily visible in the default view, extra columns can be hidden:
Data Studio provides data discovery and profiling tools to help with investigating data quality issues like those identified by DA360. These tools are available in the Results by Rule Drillable view.
The focus of DA360 is to help identify data quality issues that may be in a Metro 2® file. Any issue remediate must occur in the source data, from which the Metro 2® file was generated. If the results of an investigation need to be shared outside of Data Studio, a View of the data may be saved from Results by Rule Drillable as a CSV file.
Either the Space does not exist, the Solution hasn't been deployed, or it exists but you do not have access. Speak to your administrator to get you (or your user group) access.
Your user role has certain permissions assigned to it, which might restrict what you're allowed to access. Speak to your administrator.
Metro 2® files must confirm to either a character or packed Binary format. Make sure the Record/Block Descriptor Word (RDW/BDW) value correctly lists the number of characters included in each record – usually 0426 for character format or 0366 for packaged Binary format.
Make sure the file is formatted correctly in accordance to all definitions in the CRRG.
This is likely to do with your internet connection and possibly any antivirus scanning software you have running on your machine/network.
Setting up an External system to load large files is recommended, see 'Experian STS / SFTP' for details.
Go to the Jobs page to see if the Workflow is still running. If it's failed, check the reason for the error.
Yes, if you have the required user permissions. Contact your account manager/administrator about any modifications.
We provide a number of free help and learning resources:
Need further assistance? Get expert advice from our experienced product consultancy team or contact support.