Military Airfields / Common Operating Picture
Common Operating Picture: The Shared Airfield Map
One airfield map the whole base shares, drawing runway status, closures, discrepancies, parked aircraft, construction, and waivers as layers.
Request a demoThe airfield picture is spread across too many pages
Runway status lives on the board, discrepancies in their log, parked aircraft on the parking plan, and construction in its own project files. Reading the airfield at shift change means opening each of them and assembling the picture in your head.
The Common Operating Picture draws the records the base already keeps as layers over the satellite image, so a shift reads the airfield from one page. Every record lives once per base, so two people with the same layer on always see the same thing.
Turn on the layers the shift needs
Pick a view
Open a built-in view for the shift, parking, or construction, a view you saved for yourself, or one a manager saved for the whole base. A view keeps which layers show, never data.
Read the layers
Layers come in groups: the airfield (areas, runway status, lights and signs), operations (closures, discrepancies, wildlife), parking (parked aircraft, the plan, clearance envelopes), and planning (construction, imaginary surfaces, obstruction evaluations, waivers). Each layer is offered only to people whose role opens its module.
Click anything for its facts
A runway shows its status, surface condition, closures, open discrepancies, and inoperative lights. Any other record opens a short dialog with a link to the record in its own module. Records with no location are listed as not on the map.
Close an area and mark lights out
Draw or pick an area, mark it Closed or Restricted, and write the one sentence everyone reads about how it reopens. The same closure shows on the Airfield Status board, the kiosk, and the Events Log. Lights, signs, and NAVAIDs are marked out and back in from the map as well.
What it automates
One page at shift change
Runway status, closures, discrepancies, aircraft, and construction read together instead of from separate screens.
Everyone sees the same records
Views hold layers, not data, and the map refreshes on its own when a record changes anywhere at the base.
Closures that never reopen on their own
A closure stays active until a person reopens it, and its reopen sentence reads the same on every screen.
Straight answers
Does the map keep its own copy of the records?
No. It draws the records other modules keep. A dialog links back to the record in its own module, and the map keeps only its closures, response items, and drawn layers.
Can everyone see every layer?
A layer appears only for people whose role can open its source module at that base. Layers drawn from airfield setup, such as areas, runway status, closures, and imaginary surfaces, are offered to everyone who can open the map.
Can we save our own layouts?
Yes. Save views for yourself, and managers can save views and a default for the whole base. Built-in views cover the shift, parking, and construction.
Can we place response items during an incident?
Yes. Place fire, security forces, and medical resources, cordons, entry control points, and hazard pins, linked to an open incident if you choose, and draw your own layers in named colors.
Can the map be printed?
Export PDF prints the whole view with its layers. The lights map can also be exported on its own.
Connected modules
Airfield Status
Live runway, NAVAID, and weather status the whole base works from: one screen, always current.
Construction
Every airfield construction job from design through warranty: phases, closures, cranes, NOTAMs, waivers, and who was told.
Discrepancies
Every airfield discrepancy tracked from identification through verified closure.
Parking Plans
Aircraft parking plans with wingtip and taxilane clearance envelopes computed for you.