16
Fly - Fight - Win Headquarters U.S. Air Force AF Flight Scheduling MSgt Thomas Beatty AF FS CoI Lead NCOIC Aviation Management 1

Fly - Fight - Win Headquarters U.S. Air Force AF Flight Scheduling MSgt Thomas Beatty AF FS CoI Lead NCOIC Aviation Management 1

  • View
    213

  • Download
    0

Embed Size (px)

Citation preview

Fly - Fight - Win

Headquarters U.S. Air Force

AF Flight Scheduling

MSgt Thomas BeattyAF FS CoI Lead

NCOIC Aviation Management

1

Fly - Fight - Win

What is Flight Scheduling?

“A coordinated planning cycle that supports operational and training requirements, optimizes economy of force, and is published in a weekly schedule that assigns resources to task.”

The Core of Flight Scheduling Person Aircraft Time (Mission, Sortie, etc…)

Other factors are considered Deltas or Neighbors Weather Ranges

2

Fly - Fight - Win

How is this done today?

3

Fly - Fight - Win

Flight Scheduling – Current Problems

Primary Inaccurate data

Communication Errors/ Data Lag Faulty Logic

Lack of operational capability Inadequate/Over utilization of resources

Stove-piped Systems Lack of peripheral coordination

Secondary Lack of efficient training Cost of operations Environment Custodial responsibility to Taxpayers

4

Fly - Fight - Win

Potential Scenario

13th Airlift Squadron Wrong Aircrew member assigned to a mission

Data lag from Training inputs and transfer from ADS to FS System

AC takes off, range is not available, mission canx RTB

17th Refueling Squadron Tanker customer is a no-show at nearby track-- Tanker RTB

May have provided training to 13th AS

5

Fly - Fight - Win

Solving the problem:

Technological Provide data transparency to required users

Operational Review process and eliminate inefficiencies Turn to the Tactical operators for needs

Train, Organize & Equip Provide training to schedulers

Aviation Resource Management Doctrine

Provide Policy & Guidance from Strategic levelsAFI – with flexibility built in

6

Fly - Fight - Win

Future State: Operations

7

Schedule Build(-MX)

MX Loads Tails-autofill

Flight ScheduleApproval by

Unit (asrequired)

ElectronicSchedule(dissemit)

Changes go inSystem

Flight OrdersLast Look

Flight Execution

Post-MissionPaperwork Single

Entry withApproval

- Build Worldwide Central Database- Training Req - autofill - sim / DMG - PFT - CT- Range Availability and Schedule- Inside Base Agencies - A.P./A.D. - Fuel - Freq- External Unit Open Mission System- Auto Calculate Times Based MSN - T.O./LMD - MSN Read - Schedule Override- CPO Channel (G2) Alert HHQ- Aircrew Empowered in Schedule Process - leave - appts- Environmental Inputs (Bash/Bam)- Go/No Go - PHA (FLT Surs) - Quals - Currency - FCIF - etc.- Test Activity- Unit Customized View

Automate781s

yes no

no

yes

Stop LightElectronicSignature

- Change Notify - Approp Agencies - Crew Members - Leadership - MX- System Logic Dictates ifApproval is Needed Basedon Change

- By electronic or paper asrequired- Final go/no go- 11-401

- Digital completion by PDA/laptop- kiosk at MX something or SQ- 781s electronic with dig signature

Fly - Fight - Win

How can we get there?

Halt proliferation of duplicative systems Funds to be re-capitalized for operations development

Leverage existing capabilities Systems to services

COOL, GDSS2, GTIMS, PEX Migrate existing systems to web, or migrate with

imbedded SOA capability Ensure tactical input to process, requirements, and

capabilities Data compiled will inherently feed operational &

strategic levels

Fly - Fight - Win9

Demonstration

Distributed Interaction: Decentralized Operation

Shaw AFB – Ops input via real schedulersLangley AFB – Maintenance input

Services Running: Ops to MX with mission status MX to Ops with aircraft status updates ARMS data NRT, updates to ADS via user Inherent visibility & data reporting

Fly - Fight - Win10 10

Flight Scheduling Prototype Lab

FSCOI-1Red Hat

FSCOI-2Windows Server 2003

FSCOI-4Windows Server 2003

MessagingContainer

(Java)

IONA

Jetty Web Server

PEX Services(.NET)

WCF

SQLServer

IIS Web Server

Jetty Web Server

IONA

EMOC(Java)

SOAP/HTTP

SOAP/HTTP

MySQLJDBC

JDBC

IIS Web Server

PEX Whiteboard(.NET)

EMOC UI(.NET)

Login UI (PHP)

SOAP/HTTP

SOAP/HTTP

IONA

Security(Java)

Java Spring Container

UserDefinitions

Fly - Fight - Win11

FS Screen

Fly - Fight - Win

MX Screen

12

Fly - Fight - Win

IT Physical Architecture

FSCOI-1Red Hat

FSCOI-2Windows Server 2003

FSCOI-4Windows Server 2003

MessagingContainer

(Java)

IONA

Jetty Web Server

PEX Services(.NET)

WCF

SQLServer

IIS Web Server

Jetty Web Server

IONA

EMOC(Java)

SOAP/HTTP

SOAP/HTTP

MySQLJDBC

JDBC

IIS Web Server

PEX Whiteboard(.NET)

EMOC UI(.NET)

Login UI (PHP)

SOAP/HTTP

SOAP/HTTP

IONA

Security(Java)

Java Spring Container

UserDefinitions

Fly - Fight - Win

Foundation of “Epic”

MAJCOM agreement to: Move their service/process to a SOA Share their data and unique capabilities with

other services Explore the use of other services’ unique

capabilities Provide lessons learned to neighbors Publish data to be consumed by customers

Fly - Fight - Win

Epic – The new era

Mission Plan Mission Distribution Flight Scheduling Flight Planning Mission Execution Mission Documentation

15

Fly - Fight - Win16

Questions?