2 Data, Architecture, and Process Overview
2.1 CAMS Data Input Sources
| Source_Name | Abbreviation | Organization | Data_Steward_Representative |
|---|---|---|---|
| Allocation Management System | AMS | GARFO-TDMD | Torey Alder |
| Biological Sampling Mobile | BSM | NEFSC-READ | Josh Moser (NEFSC-ITD) |
| Biological Sample Monitoring Database System | BSMDBS | NEFSC-READ | Josh Moser (NEFSC-ITD) |
| Commercial Fisheries Database Biological Sample | CFDBS | NEFSC-READ | Josh Moser (NEFSC-ITD) |
| Commercial Fisheries Species Support Table | CFDBS.CFSPP | NEFSC-PEMAD | Eric Robillard |
| Commercial Fisheries Dealer Electronic Reporting System | CFDERS | GARFO-APSD | Bethany Brosnan (interim) |
| Cooperative Research Database | CO_OP_RESEARCH | NEFSC-FMRD | Anna Mercer |
| Fishery Biology Program Database | FISH_BIO | NEFSC-PEMAD | Eric Robillard |
| Northeast Electronic Monitoring Information System | NEMIS | NEFSC-FMRD | Chris Tholke |
| Observer and At Sea Monitor Database | OBDBS | NEFSC-FMRD | Chris Tholke |
| Observer Preliminary Data System | OBPRELIM | NEFSC-FMRD | Chris Tholke |
| Pre-Trip Notification System | PTNS | NEFSC-FMRD | Chris Tholke |
| Vessel Monitoring System | VMS | GARFO-OLE | Carl Lemire |
| Vessel Permit System | VPS | GARFO-APSD | Ted Hawes |
| Vessel Trip Reporting | VTR | GARFO-APSD | Bethany Brosnan (interim) |
| Surf Clam/Ocean Quahog | SFCLAM | GARFO-APSD | Bethany Brosnan (interim) |
2.2 Data sharing architecture
Figure 2.1: CAMS Service Account Model where 1) rectangles = data schema, 2) rhombus = service account with DB link, and 3) circles = end user schema with views of tables then granted to end users/roles.
2.3 Process overview
The MAPS (Monitoring Analysis Program System) R package runs all of the processes for CAMS within the architecture described above and outputs the results to the tables within the MAPS schema on the CAMSDB Oracle database instance. Those results are checked and then passed through to the CAMS_GARFO schema on CAMSDB which then have views on end-user database instances (e.g. DB01P, NEFSC01) through database links.
The overall process of the MAPS production system involves pulling in snapshots of the source data, matching trips across data systems, joining landings data and applying business rules across redundant or missing data elements, estimating discards, and producing end user tables and views 2.2. Each of these process steps are described in detail in the following chapters.
Figure 2.2: An overview of the data process by the MAPS R package and output of end-user tables to the MAPS schema on CAMSDB
Last modified: 2026-07-02