---

Oceana Naval Air Station

Status:

Existing

Definition:

Naval fighter and attack jet base, and one of the busiest Naval Air Stations in the country, averaging one take-off every two minutes. Oceana has 10,000 personnel, numerous squadrons, and several tenant units, including a detachment of SEABEES. On 5,916 acres near Virginia Beach, it has a remote airfield 13 miles away near Chesapeake, and operates one of six military aviation tracking stations along the east coast that manage the 94,000 square miles of off-shore training ranges.

Stakeholder:

Navy

Architecture Flow Diagrams
which include Oceana Naval Air Station:

• Oceana Naval Air Station City of Virginia Beach TMC

Architecture Flows
to/from the Oceana Naval Air Station:

Oceana Naval Air Station City of Virginia Beach TMC

• traffic images


• traffic information coordination

City of Virginia Beach TMCOceana Naval Air Station

• traffic images


• traffic information coordination

National ITS Architecture Subsystems
mapped to the Oceana Naval Air Station:

• Emergency Management Subsystem
• Multimodal Transportation Service Provider Terminator
• Traffic Management Subsystem

National ITS Architecture Services
associated with Oceana Naval Air Station:

• ATMS07 - Regional Traffic Management -- (Graphic)
• ATMS08 - Traffic Incident Management System -- Graphic 1 2 3 4

National ITS Architecture Functional Requirements
associated with Oceana Naval Air Station:

TMC Traffic Information Dissemination

1. The center shall retrieve locally stored traffic information, including current and forecasted traffic information, road and weather conditions, traffic incident information, information on diversions and alternate routes, closures, and special traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements), and the definition of the road network itself.
2. The center shall distribute traffic data to maintenance and construction centers, transit centers, emergency management centers, and traveler information providers.

TMC Incident Detection

1. The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.
2. The center shall exchange incident and threat information with emergency management centers as well as maintenance and construction centers; including notification of existence of incident and expected severity, location, time and nature of incident.
3. The center shall provide road network conditions and traffic images to emergency management centers to support the detection, verification, and classification of incidents.

Traffic Data Collection

1. The center shall collect traffic management data such as operational data, event logs, etc.
2. The center shall assign quality control metrics and meta-data to be stored along with the data. Meta-data may include attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.
3. The center shall receive and respond to requests from ITS Archives for either a catalog of the traffic data or for the data itself.
4. The center shall be able to produce sample products of the data available.