AABB Flashcards
Tell me about your current experience?
For the past 2 years I’ve been working at US Federal Aviation Agency as a Senior
Business Analyst, and was involved in handful projects. Couple of bigger projects involved development and deployment of the comprehensive data governance frameworks for the Office of Designated Engineering Department (DED) and to work closely with data governance leads to align initiatives with business values. I used Collibra as a data governance and catalog management tool to create a central source of truth for data assets, and streamline data management processes. I’ve defined a clear business rules to govern data handling, then collaborated with IT to gather metadata, and mapped it in the Collibra ensuring every piece of data was accounted for and cataloged. Through my initiatives, DED has strengthened its data governance, supporting the company’s commitment to operational excellence and informed business decisions.
What type of data did you managed?
The FAA’s Designated Engineering Department (DED) uses technical data that relate to the airworthiness and certification of aircraft and aircraft components. Specifically, DED is responsible for reviewing this technical data for compliance with FAA
airworthiness standards and regulations.
The data overseen by DED includes engineering reports, drawings, and other technical details relevant to the design, operation, and maintenance of aircraft, ensuring that they comply with the pertinent regulations.
How did you implement these Data Governance in Collibra?
To implement data governance and catalog management in Collibra to create a central source of truth for data assets, I’ve done the following:
Define Business Rules:
Establish clear data governance policies that dictate how data is to be handled, accessed, and managed. I’ve done it by JAD sessions with the Data Owners and Stewarts
Gather Metadata:
Collaborate with IT and data owners to identify all data sources.
Collect metadata from each source, which includes data type, data lineage, and data quality attributes.
Configure Collibra:
Create Communities, which are high-level groupings like departments or business units.
Map Metadata in Collibra:
Import metadata into the Collibra Catalog using the import functionality or via integrations with data sources.
Use the Data Dictionary in Collibra to document and manage metadata.
Catalog Data Assets:
Create Assets within the appropriate domain and attach the gathered metadata to these assets.
Ensure every data element is classified and cataloged according to the business rules.
Data Stewardship:
Assign data stewards who are responsible for the quality and management of the data assets.
Use the workflow engine in Collibra to automate data governance processes.
Validation and Quality Checks:
Set up data quality rules in Collibra to continuously monitor and maintain the
integrity of the data.
Another project at FAA
was designing and implementing an Okta-based Single Sign-On solution for an Enterprise Hosting Services Department of the IT division. I’ve assisted with the implementation of the Okta-based Identity Governance and
Administration solution incorporating over 30+ applications of the IT Department.
I worked with the technical team to design a robust access control model that ensured only authorized users could access sensitive data. The system was integrated with existing applications, which meant that access was only granted to those who needed it. I also worked with the IT team to configure Okta, integrating it with the network’s Active Directory infrastructure.
The outcome of this project helped to reduce the time required to complete access request workflows and improved efficiency and also enhanced security by ensuring that access requests were properly validated and authorized.
Where did you work prior to FAA?
Prior to the FAA, I worked at the Bank of New York Mellon for over a year and helped them to Develop a Data Management Best Practices. I conducted an audit of the existing data management practices, identified critical gaps, particularly in data entry, lifecycle management, and security protocols. With these insights, I’ve developed a comprehensive guideline document. This included standardized data entry procedures to ensure accuracy and consistency, clear instructions on data storage durations,
archiving methods, and stipulated roles and responsibilities to maintain data integrity.
For the MDM solution, I coordinated with stakeholders across various business units to understand their data needs and challenges. With a thorough needs assessment in hand, I led a team of developers and data architects to design a custom MDM solution on the Informatica platform. We focused on ensuring the solution could integrate disparate data types while providing a single source of truth, which was key to data consistency and reliability.
What type of data did you managed?
Transactional data from different financial operations and transactions. I also worked with the Market data, including stock prices, trading volumes, and financial indices. Investment data, covering portfolios, assets under management, and investment performance.
