Candidates Request Form 1 Job Title Data Analyst 2 Client Company/Dept. Name FSIS, OAS, ACQUISITIONS 3 Address MAILDROP 5230, 5601 SUNNYSIDE AVENUE City Name BELTSVILLE State Name MD-Maryland Zip Code 20705 If others (Address) 6 Duration of the project Project Start Date Oct 20, 2022 Project End Date Oct 19, 2023 Due date for Resume submission Sep 27, 2022 7 No. of Openings 1 No. of Maximum Submissions 2 8 Job Description 1.0 Scope of Work
The United States Department of Agriculture (USDA) has been protecting the nation's food supply since 1906, with the inception of the Federal Meat Inspection Act. The Food Safety Inspection Service (FSIS) is the USDA agency responsible for food safety. The FSIS mission is to ensure that the nation's commercial supply of meat, poultry, and egg products is safe, wholesome and correctly labeled and packaged as required by the Federal Meat Inspection Act, the Poultry Products Inspection Act, and the Egg Products Inspection Act. While carrying out this mission, FSIS generates both structured and unstructured data from its sampling, inspection, verification, and other activities.
This requirement is to provide assistance to the Office of Planning, Analysis, and Risk Management (OPARM) in addressing data quality issues found in Food Safety Inspection Service (FSIS) data systems and making recommendations to decrease data quality issues in the future. This includes utilizing test data systems, evaluating data tables for data quality issues, and developing SQL code to resolve data quality issues. Python, R, and SQL are the main tools used to complete this work, in addition to Microsoft Suite tools.
2.0 Background
OPARM coordinates FSIS's data collection, analysis, and integration activities across all program areas. OPARM is responsible for ensuring data analyses are consistent and of high quality. OPARM conducts data analyses to inform mission and workforce-related Agency decisions, in addition to processing ad hoc and Freedom of Information Act data requests.
One of the key building blocks to data analysis is the data itself. While the Office of the Chief Information Officer is responsible for making actual changes and updates to the data, OPARM takes a leading role in finding data issues and making recommendations to clean the data and improve data quality. OPARM also implements preventive measures to minimize errors getting into the data by recommending enhancements to Agency systems, processes, and policies.
Contractor Requirements
3.0 Technical Requirements / Tasks
The contractor will be required to perform the tasks listed below. This list of tasks is not inclusive of ad-hoc and administrative tasks which the contractor may be required to complete. The required tasks are as follows:
Task 1: Identify Current Data Quality Issues
The contractor shall assist the Government in the identification of known and unknown data issues. As a part of this task the contractor shall:
1. Meet with the COR or the designated POC on a weekly basis to discuss and identify known data
issues, their status and resolution, and mitigations to the issue.
a. Prepare a weekly status report detailing the previous week's accomplishments and planned activities for the next week, along with targeted dates for each activity. The status report shall include summary information regarding the status of data quality tickets and counts of open vs. closed tickets.
2. Monitor USDA's customer relationship management/ticketing tool requests assigned to the Data Quality Queue and report any anomalies to the COR or COR's designee.
a. Reroute any tickets that belong to another queue to the appropriate POC.
3. Monitor the Data Quality shared inbox and respond within two business days. Respond to ad hoc requests from OPARM or other program areas. Share ad hoc requests with the COR, who will determine the priority of requests and the appropriate method to respond. The contractor shall track responses for continuity of communication with the customers. Any ad hoc requests that do not come through USDA's customer relationship management/ticketing tool shall be entered into this tracker by the contractor if it is determined that a data quality correction is required.
4. Document all incoming data issues, regardless of the source, within a Microsoft Access database or similar system for internal use and reporting purposes.
5. Maintain a record for each data quality issue, with each record containing as much detail as possible. The record shall include information including: Ticket number, requestor name and contact information, relevant status dates (i.e., when the issue was routed to the DQ queue, when it was submitted for data correction, and when it was resolved), categorization of the issue theme, subject area and problem classification. The contractor shall catalog these issues once identified and track relevant metrics and resolutions to these issues.
a. The contractor will prepare a monthly catalog that shall be updat
Location: Beltsville, MD
Posted: Nov. 3, 2024, 10:13 p.m.
Apply Now Company Website