Download presentation
Presentation is loading. Please wait.
Published byRussell Jordan Modified over 9 years ago
1
National Operations Center/C4
2
Act as the coordinating element between customers, the US Air Force and CAP Wings Analyze Mission Requirements Assist in Risk Management Assist CAP Units in coordinating requests for additional resources to support local missions Consolidate and up-channel member reported mission results Serve as the focal point for emergency notification NOC C 2 = Coordination & Communication NOC Mission
3
Active Mission Tracking Aircraft Status Tracking Key Resource Tracking – SDIS – ARCHER Mission Reporting Web Mission Information Reporting System (WMIRS)
4
WMIRS Will be used for all AFAM and Corp Civil Support missions – If WWW access is not avail, NOC will input mission info Incident Commander and alerting officers should be WMIRS literate WMIRS
5
New Procedures AFI 10-2701 – Prescribes AFAM Approval Authority Military Interdepartmental Purchase Request (MIPR) – Military Customers must use beginning in FY06 – Drives lead time Customer request/OPLAN/Sortie plan/Cost estimates All required prior to MIPR acceptance – Get Fiscal Year forecast from military customer Request/OPLAN/MIPR cover entire FY Automation – Mission Approval & Reporting On-line Background
6
Air Force Assigned Mission Status AFAM required for CAP support to federal agencies or military The mission must be one that the AF could do for itself Some historical missions are no longer approved AFAM status determined by AF Officer w/ 1AF, AFRCC, AFNSEP or CAP-USAF – AFAM no longer automatic via MOU/MOA Execution
7
Corporate Missions Request procedures and requirements should parallel AFAM process FECA/FTCA coverage not available CAP Insurance for liability Mission requests for Civil Support (State, County, Local agencies) – To NOC for legal review – Approval by WG/CC May NOT be used for Fed/Mil Customer Requests
8
AFAM Mission Requests Written customer requests required Email preferred, fax or letter OK Must include identifiable dates, locations and objectives May be in future if data complete Mission numbers assigned after approval Procedures
9
AFAM Notes NOC does not approve…..AF does NOC coordinates customer request and relays CAP unit mission plans If AF required procedures are not followed or AF required information is not furnished, then 1AF/AFRCC/AFNSEP/CAP-USAF will not approve…..they are prohibited from doing so LIMFACs
10
AFAM’s reported to 1AF Air Task Order (ATO) – Two ATO briefs to 1AF/CC per week 3 day & 4 day periods Next period, all CAP AFAM’s scheduled are listed Previous period, CAP AFAM’s results are reported – Date, Results, Time flown, etc – Goal – List & Report all CAP AFAM’s – Classified “Secret” because of AF missions Coordination
11
Non CAP people in CAP Aircraft “Non CAP crew” vs. “passengers” – Crew members perform a function – Passengers go from Point A to Point B on a transportation mission – Difference important to FAA Passengers
12
Transportation missions Legal but several considerations – FAA rules…..not CAP or USAF – Customer can not pay, even indirectly – Commercial pilot preferred – Private pilot, yes but no “compensation” Can not count flight time (can be logged) No money reimbursement except for Search and Locate missions – FAA action for violation Directed at Pilot Transportation
13
Counterdrug missions Requests by federal drug law enforcement agencies – Request & sortie plan are both required before a mission number can be issued – Longer duration/complex missions may require an Operations Plan Requests below federal level require validation by a federal drug law enforcement agent – Marij. Erad missions (DEA DCE/SP coordinators) – All others any Federal drug LEA Counterdrug
14
WMIRS Automation Mission information gathered and stored in WMIRS, accessible via WWW Mission reporting – automated Financial reimbursement – auto fill for CAP Form 108 Reporting
15
Managed under NIIMS ref. Federal Response Plan Incident Commander assigned by lead federal agency Multi-Agency Events
16
NOC serves as Planning Section for CAP support – Accepts target decks from customers – Passes requirements to wings (Operations Section) for action C4 is the resource unit Multi-Agency Events
17
CAP (NOC) 888-211-1812 CAP Wing NORTHCOM AFNORTH-1AF (CAOC) CAP … Remain Under Military Operational Control … Tasking Execution Report Requirement DoD Report Tasking Workflow
18
FY05FY06* SAR5,8854,791 DR1,3192,135 CD7,3096,137 HLS1,3011,026 AF TRAINING29,06825,124 O FLIGHTS**10,0428,991 AF ROTC2,9562,746 OTHER AF2,5753,899 NOTES:*FY06 numbers do not include September **O FLIGHTS were not a USAF mission again until FY06 USAF Mission Flying
19
*FY06 numbers do not include September Flying Hour Comparison*
20
Conclusions We have become a resource of choice for a number of support functions Need to be customer and capability focused— not CAP-centric Training + Education = Preparedness
21
WMIRS Automation NOC Contact Information Toll Free: (888) 211-1812 Voice: (334) 953-7299 Fax: (334) 953-4242 E-mail: opscenter@cap.gov Weekdays: 0730 to 1630 CT 24/7 for Emergency Requests Toll Free: (888) 211-1812 Voice: (334) 953-7299 Fax: (334) 953-4242 E-mail: opscenter@cap.gov Weekdays: 0730 to 1630 CT 24/7 for Emergency Requests
Similar presentations
© 2024 SlidePlayer.com. Inc.
All rights reserved.