NOAD Schema 3.4 — 60-day Notice
2/21/2014 - 11 Years Ago
As part of ongoing efforts to enhance maritime domain awareness, we continue to improve handling of essential data contained within Notices of Arrival and Departure (NOAD). On Tuesday, 22 April 2014, an updated NOAD schema, versioned 3.4, will be released that incorporates improvements in vessel response plan data reporting. When NOAD Schema 3.4 is released on 22 April 2014, NOAD Schema 3.2 and older versions will no longer be supported.
Schema Change Details
For your review, a draft of Schema 3.4 has been added to the Developer Resource Files, however, it is subject to change and is not intended for use in any production or otherwise official system/environment in the form in which it is presented.
The following is a list of the specific changes from Schema 3.3 to Schema 3.4
Affected Elements:
//NOTICE/NOTICE_DETAILS/VERSION
Change Details:
The only acceptable value for this field under Schema 3.4 will be "3.4" (not including the quotation marks)
Affected Elements:
//NOTICE/VESSEL/NON_TANK_VESSEL_RESPONSE_PLAN
Change Details:
The element NON_TANK_VESSEL_RESPONSE_PLAN has been renamed to VESSEL_RESPONSE_PLAN. Acceptable values for the element remain Yes or No
Affected Elements:
//NOTICE/VESSEL/NTVRP_NUMBER
Change Details:
The element NTVRP_NUMBER has been renamed to VRP_NUMBER. Content rules for the element remain “Must be numeric and no longer than 5 (five) characters in length. Leading zeros are allowed.”
Affected Elements:
//NOTICE/VESSEL/VRP_TYPE
Change Details:
A new element named VRP_TYPE has been added and will be used to indicate the type of response plan the vessel has, if any. If provided, acceptable values for the element are TANKED or NONTANKED.
Picklist Updates
The possibility exists that one or more picklist updates may be included in the Schema 3.4 release, specifically for domestic and foreign ports. As more details become available regarding these changes they will be sent as an update to this notification message as soon as possible.
|