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

2. 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

3. Fly - Fight - Win How is this done today? 3

4. 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

5. Fly - Fight - Win Potential Scenario 13 th 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 17 th Refueling Squadron Tanker customer is a no-show at nearby track-- Tanker RTB May have provided training to 13 th AS 5

6. 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 levels AFI – with flexibility built in 6

7. Fly - Fight - Win Future State: Operations 7

8. 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

9. Fly - Fight - Win 9 Demonstration Distributed Interaction: Decentralized Operation Shaw AFB – Ops input via real schedulers Langley 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

10. Fly - Fight - Win 10 Flight Scheduling Prototype Lab FSCOI-1 Red Hat FSCOI-2 Windows Server 2003 FSCOI-4 Windows Server 2003 Messaging Container (Java) IONAIONA Jetty Web Server PEX Services (.NET) WCF SQL Server IIS Web Server Jetty Web Server IONA EMOC (Java) SOAP/HTTP MySQL JDBC IIS Web Server PEX Whiteboard (.NET) EMOC UI (.NET) Login UI (PHP) SOAP/HTTP IONA Security (Java) Java Spring Container User Definitions

11. Fly - Fight - Win 11 FS Screen

12. Fly - Fight - Win MX Screen 12

13. Fly - Fight - Win IT Physical Architecture FSCOI-1 Red Hat FSCOI-2 Windows Server 2003 FSCOI-4 Windows Server 2003 Messaging Container (Java) IONAIONA Jetty Web Server PEX Services (.NET) WCF SQL Server IIS Web Server Jetty Web Server IONA EMOC (Java) SOAP/HTTP MySQL JDBC IIS Web Server PEX Whiteboard (.NET) EMOC UI (.NET) Login UI (PHP) SOAP/HTTP IONA Security (Java) Java Spring Container User Definitions

14. 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

15. Fly - Fight - Win Epic – The new era Mission Plan Mission Distribution Flight Scheduling Flight Planning Mission Execution Mission Documentation 15

16. Fly - Fight - Win 16 Questions?