Production Schedule and Process Overview

Daniel J. Hocking

2026-04-01

Data Update Schedule

The CAMS production tables, housed in the CAMS_GARFO schema, are updated for each Thursday with a data snapshot on Wednesday morning. Dealers are generally required to submit all of the previous week’s landing weigh outs by Tuesday. The dealer data production system (CFDERS) runs every day at 3 am, so the updates from Tuesday are ready in CFDERS_ALL_YEARS are ready for use Wednesday morning. Therefore, the Matching and Analysis Program System (MAPS) run then on Wednesday using the up to date dealer data and when the process finishes it pushes the results to the tables in CAMS_GARFO for end users on Thursday morning.

During these regular program runs, the landings are updated for the current calendar year and the previous calendar year. The discards are estimated for each species based on their fishing year. All fishing years that intersect with that calendar year are then estimated. For example, if the program ran on 20 May 2023 then it would generate the landings for 2022 and 2023 then update the discard estimates for each groundfish species for FY21, FY22, and FY23 because those groundfish years that go from May 1 - April 30 intersect with the landings that were updated. However, in that same run a calendar year discard species such as Atlantic Mackerel would only get FY22 and FY23 updated because only those two fishing years intersect with those calendar years updated in landings.

The business rules and code used in MAPS to process the landings and discards during a regular weekly Wednesday update includes no new code updates. The version of the program run would be from the established version in the main gitHub branch. Changes to the code potentially necessitate runs over more years and would occur on an as needed basis over a weekend to allow the additional run time.

If a major data correction was made in an upstream data source of CAMS that was not in the current or previous year and does not require a program/code change then it would be rerun as soon as possible with notice to end users. This would occur outside the normal Wednesday run so as to not delay weekly quota monitoring.

Process and Code Updates

Changes to the underlying code or support tables are tested in a schema outside CAMS_GARFO so no production tables are impacted during testing. Once these changes are tested and approved for production by the CAMS Change Control Board (CCB), those changes are merged into the main GitHub branch, the package is rebuilt, and then a new rerun of the data is scheduled. This rerun of the data is separate from the weekly data updates on the production version described above. These are additional runs with notification to end users and the associated changes noted on the webpage news section along with appropriate changes to the documentation. These changes are associated with an appropriate update to the semantic version number and will be noted in an Oracle table starting with version 1.0.0.

The new updated program will be run across all appropriate years. For example, if the change is only a modification associated with a new rule and only applies to the current year, then only that year will be rerun. If a year-specific support table was updated then the associated years affected would be rerun. If a bug was corrected or other change that could potentially affect any data, then all years would be rerun. These runs would occur over weekends, separate from the Wednesday runs that are restricted to only data updates for the current and preceding year.

Please refer to the development instructions for more information about versioning and production code workflows.