Vessel-Generated Vessel monitoring system (VMS) form data
Greater Atlantic Regional Fisheries Office
Project
(PRJ)
| ID: 22192
| Published / External
Created: 2014-09-12
|
Last Modified: 2022-08-09
Project (PRJ) | ID: 11899
ID: 22192
Project (PRJ)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | Vessel-Generated Vessel monitoring system (VMS) form data |
---|---|
Short Name | VMS forms data |
* Status | In Work |
Creation Date | |
Revision Date | |
• Publication Date | |
* » Abstract |
Many industry participants are required to send to NMFS electronically submitted forms pertaining to their fishing trips. These forms are ususally sent from a device on the fishing vessel itself and transmitted via satellite to the vendor of that particular device. These forms contain a variety of data, including the time that it was submitted, the latitude and longitude of the fishing vessel, the operator's permit number, the vessel trip report number and, depending on the type of report, such additional data as the landing port city and state, estimated arrival date/time, estimated offload date/time and the pounds of each species caught, etc. (See OLE's Forms Requirements document for details.) The forms messages are sent to GARFO through one of several methods, depending on the vendor. These methods include FTP, email and Amazon DropBox. When GARFO receives these messages, they are stored in a raw input table. Every 5 minutes, a cron job runs the VMS Parsing Engine, which parses and validates the data in the most recently received messages. Parsed messages are stored in the output table for the given form type. Data errors are logged in a data_error table and reviewed by OLE, which determines what action, if any, needs to be taken. Parsing errors are logged and resolved by the application developer. The output table data are then prepared for use in GARFO's production systems, including its industry-accesible web site, through a staging area managed by Denise Washick. The VMS data may be used by the fishery regulatory staff, statistical staff or the Office of Law Enforcement. The data are an important tool for ensuring compliance with fishery regulations. |
* Purpose |
The VMS Parsing Engine parses and performs a series of validation checks on the submitted form data to ensure that the forms have been correctly filled out. If there are any errors in the data, the VMS message is marked as having a data error and OLE staff can then determine how to resolve it. Messages without data errors are inserted into an output table, from where the data will eventually be accessible on the web site and available for GARFO staff who need to perform additional processing with it. |
Notes |
Since regulatory requirements and the csv list of the forms change often, there are several versions of the parsing engine. |
Other Citation Details | |
• Supplemental Information | |
DOI (Digital Object Identifier) | |
DOI Registration Authority | |
DOI Issue Date |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
None | Vessel Monitoring System |
None | VMS |
Temporal Keywords
Thesaurus | Keyword |
---|---|
* Spatial Keywords
Thesaurus | Keyword |
---|---|
Stratum Keywords
Thesaurus | Keyword |
---|---|
Instrument Keywords
Thesaurus | Keyword |
---|---|
Platform Keywords
Thesaurus | Keyword |
---|---|
Physical Location
• » Organization | Greater Atlantic Regional Fisheries Office |
---|---|
• » City | Gloucester |
• » State/Province | MA |
• Country | USA |
• » Location Description |
3rd Floor Server Room |
Project Information
Project Type | Project |
---|---|
Is Mandated? | |
Mandated By | |
Collection Type | VMS |
Collection Authority | Agency |
Collection Method | Electronic |
Support Roles
* » Support Role | Distributor |
---|---|
* » Date Effective From | 2010 |
Date Effective To | |
Organization | Greater Atlantic Regional Fisheries Office (GARFO) |
Address |
55 Great Republic Drive Gloucester, MA 01930 USA |
Email Address | |
Phone | (978)281-9300 |
Fax | |
Mobile | |
URL | |
Business Hours | 8:00 a.m. - 4:30 EST |
Contact Instructions |
* » Support Role | Metadata Contact |
---|---|
* » Date Effective From | 2010 |
Date Effective To | |
Person | Rohan, Patrick R |
Address |
55 Great Republic Drive Gloucester, MA 01930 USA |
Email Address | patrick.rohan@noaa.gov |
Phone | 978-281-9192 |
Fax | |
Mobile | |
URL | |
Business Hours | |
Contact Instructions |
* » Support Role | Point of Contact |
---|---|
* » Date Effective From | 2010 |
Date Effective To | |
Person | Ortiz, Ken J |
Address |
55 Great Republic Drive Gloucester, MA 01930 USA |
Email Address | ken.ortiz@noaa.gov |
Phone | (978)281-9316 |
Fax | |
Mobile | |
URL | |
Business Hours | 8:00 a.m. - 5:30 p.m. EST |
Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
Extents
Currentness Reference |
---|
Extent Group 1
Extent Description |
---|
Extent Group 1 / Geographic Area 1
* » W° Bound | |
---|---|
* » E° Bound | |
* » N° Bound | |
* » S° Bound | |
* » Description |
All waters regulated by the Greater Atlantic Region of NMFS. |
Extent Group 1 / Vertical Extent
EPSG Code | |
---|---|
Vertical Minimum | |
Vertical Maximum |
Extent Group 1 / Time Frame
* » Time Frame Type | |
---|---|
* » Start | |
End | |
Alternate Start as of Info | |
Alternate End as of Info | |
Description |
Access Information
* » Security Class | Sensitive |
---|---|
* Security Classification System |
All fishing industry related data managed by IRM is considered to be business confidential and may not be released without written consent of the data originator. |
Security Handling Description | |
• Data Access Policy | |
» Data Access Procedure |
Access to data is governed by 50CFR600 - Confidentiality of Information. Access by state fishery management agency staff and Fisheries Management Council staff may be allowed through Memorandum of Understanding that are signed by the Greater Atlantic Regional Administrator and Directors of the State Agency or Councils that describe the need and uses of the data and list the individuals who will have access to the data. Contractors may be granted access provided they are working under contract to NOAA or a cooperating partner (state, Council, Commission) on a specific project under the oversight of a partner. |
• » Data Access Constraints |
Access is restricted to personnel authorized in accordance with NOAA Administrative Order 216-100. A signed non-disclosure agreement must be on file for all authorized personnel. The IRM help desk or APSD Data Request staff are the POC for non-disclosure forms. |
• Data Use Constraints | |
Metadata Access Constraints | |
Metadata Use Constraints |
Distribution Information
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
URLs
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
Activity Log
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Issues
Issue Date | |
---|---|
Author | |
Issue |
Issue Date | |
---|---|
Author | |
Issue |
Issue Date | |
---|---|
Author | |
Issue |
Technical Environment
Description |
Relational database. |
---|
Data Quality
Representativeness |
NA |
---|---|
Accuracy |
NA |
Analytical Accuracy |
NA |
Horizontal Positional Accuracy | |
Vertical Positional Accuracy | |
Quantitation Limits |
NA |
Bias |
NA |
Comparability |
NA |
Completeness Measure |
NA |
Precision |
NA |
Analytical Precision |
NA |
Field Precision |
NA |
Sensitivity |
NA |
Detection Limit |
NA |
Completeness Report |
NA |
Conceptual Consistency |
NA |
» Quality Control Procedures Employed |
Acronyms
Acronym | Meaning |
---|---|
NMFS | National Marine Fishery Service |
OLE | Office of Law Enforcement |
PE | Parsing Engine |
VMS | Vessel Monitoring System |
Glossary Terms and Definitions
Term | |
---|---|
Authority | |
Description |
Term | |
---|---|
Authority | |
Description |
Term | |
---|---|
Authority | |
Description |
FAQs
Date | 2014-09-12 00:00:00 |
---|---|
Author | Patrick R Rohan |
Question |
How many VMS forms are there? |
Answer |
15 |
Date | 2014-09-12 00:00:00 |
---|---|
Author | Patrick R Rohan |
Question |
What packages comprise the VMS Parsing Engine? |
Answer |
Parse, Parse12, Utilities, Dev_Utilities |
Date | |
---|---|
Author | |
Question | |
Answer |
Child Items
Rubric scores updated every 15m
Score | Type | Title |
---|---|---|
100 | Data Set (DS) | VMS forms Output Tables |
Related Items
Item Type | Relationship Type | Title |
---|---|---|
Catalog Details
Catalog Item ID | 22192 |
---|---|
Metadata Record Created By | Patrick R Rohan |
Metadata Record Created | 2014-09-12 10:04+0000 |
Metadata Record Last Modified By | SysAdmin InPortAdmin |
» Metadata Record Last Modified | 2022-08-09 17:11+0000 |
Metadata Record Published | 2016-02-25 |
Owner Org | GARFO |
Metadata Publication Status | Published Externally |
Do Not Publish? | N |
Metadata Workflow State | Published / External |
Metadata Last Review Date | 2016-02-25 |
Metadata Review Frequency | 1 Year |
Metadata Next Review Date | 2017-02-25 |
Tags |
---|