13.07.2015 Views

2004 US Air Force OPERATIONAL REPORTING ... - Survival Books

2004 US Air Force OPERATIONAL REPORTING ... - Survival Books

2004 US Air Force OPERATIONAL REPORTING ... - Survival Books

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

WWW.SURVIVALEBOOKS.COMAFI10-207 4 APRIL 2008 23tion and award of final Top Secret clearance. Controllers serving in a critical Personnel Reliability Program(PRP) billet must be eligible for a Top Secret security clearance based on a SSBI or SSBI-PRcompleted and adjudicated within the last five years. At no time will the EA console be manned whereboth controllers on duty possess only an interim Top Secret clearance, refer to AFMAN 10-3902, NuclearWeapons Personnel Reliability Program (PRP) for additional information on initial and interim certification.This restriction also applies to positions with single controllers trained in Headquarters, UnitedStates Strategic Command EAP (EAP-STRAT) and/or deployed to an overseas theater for OPLAN 8010reconnaissance operations; at no time will the single controller possess only an interim Top Secret clearance.All personnel from other functional areas performing duties in the CP must possess, as a minimum,a Secret clearance (e.g., MOC, ATOC, etc.).3.2.1. All 1C3X1 personnel will maintain a current Top Secret security clearance once an initial TopSecret has been awarded.3.2.2. CP Chiefs/Superintendents will ensure each 1C3X1 assigned to the CP has a current Top Secretsecurity clearance and submits their periodic review in a timely manner. This includes all 1C3X1 personnelserving in C2 facilities where Top Secret information is not processed/maintained on a routinebasis.3.2.3. If a 1C3X1’s Top Secret security clearance has been permanently revoked, the CP Chief/Superintendentwill immediately initiate procedures to remove the individual from AFSC 1C3X1.3.3. Additional Qualifications. Additional qualifications may be required locally or by MAJCOMs tosupport unique mission or functional area requirements (e.g., certification under the PRP, access to SensitiveCompartmented Information (SCI), or OPLAN 8010).3.4. Duty Schedule and Restrictions. Due to the 24-hours a day, 7 days a week, 365 days per year (24/7/365) manning requirement for the C2 facility, CP controllers working rotating shifts (i.e., console controllerduty) will not perform additional duties/details beyond the scope of C2 functions (e.g., base clean up,snow removal, etc.) outside of the command post/C2 work center. This provision does not apply to personnelassigned to overhead positions and working normal day shift schedules. CP personnel who residein the dormitory are not exempt from performing bay orderly functions in the dorm common areas.3.4.1. The duty schedule is managed by the CP Superintendent or designated alternate.3.4.2. When possible, CP controllers should be scheduled to work eight-hour shifts, typically six dayson, three days off rotating between day-, swing- and mid-shifts. Controllers will not perform morethan 12 hours of continuous duty (plus necessary time for shift changeover) and should have eighthours of uninterrupted rest before shift. EXCEPTION: In times of emergency, controllers may berequired to perform duty in excess of 12 hours to ensure uninterrupted C2. The standard for deployedoperations is 12-hour shifts, 6 days on duty, 1 day off. This standard supports the C2 force moduleconcept of two 9ACP* Unit Type Codes (UTC) (6 x 1C3X1s) per location as the manpower baselinefor deployed operations.3.4.3. CP controllers will not consume alcohol within eight hours preceding a scheduled shift. Morestringent requirements may apply due to position/unit of assignment. MAJCOMs will address thisparagraph in their supplement to this AFI.3.4.4. Within the CP, personnel may be assigned duties as deemed appropriate by the CP Chief orSuperintendent with the exception of the issue/receipt of weapons while performing EA duties.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!