Fusion Analyst

0530: check overnight message traffic and reporting in your AOR. Update running threat estimates if anything changed. 0700: attend or support the wing standup, which may include a brief intel summary. 0800-1100: production work — updating threat assessments, working a specific tasking from wing or MAJCOM, reviewing imagery. 1100: pre-mission brief support for afternoon launches. You either brief or support the senior analyst who briefs. 1300: AOR update, check for new reporting, flag anything that affects current or upcoming operations. 1500: product coordination — getting draft products reviewed, submitting finished products. 1700: debrief the returning missions. What did they see? Does it match your picture? Update accordingly. The debrief is where you actually learn whether your analysis was right.

Monday: AOR review, update running order of battle products, attend wing battle rhythm meetings. Tuesday-Thursday: steady-state production, exercise support if applicable, supporting any deployed detachments. Friday: weekly threat summary, lessons learned from the week's missions, product maintenance. Overlaid on all of this: supporting whatever exercises or contingency taskings come in, which will disrupt the schedule regularly. Intel does not follow a nine-to-five rhythm when operations are running.

All-source integration is not a title, it is a discipline. Learn to hold contradictory reporting in tension without forcing premature resolution — SIGINT says the unit moved north, IMINT shows activity at the original location, HUMINT is two weeks old. Your job is to assess what is most likely true and communicate your confidence level honestly, not to pick the source you trust most and paper over the others. Learn imagery analysis beyond 'there is a thing in this box.' Learn how SIGINT collection works well enough to understand what gaps exist. Read the finished intelligence from theater-level organizations and understand why they wrote what they wrote.

ATP 2-01 (Intelligence Preparation of the Battlefield) — the Army wrote it but Air Force intel lives by the same framework. AFI 14-119 (Intelligence Support to Force Protection) — know this cold. Your unit's applicable CONPLAN and OPLAN threat annexes — read them even before you are fully cleared, get read-in as fast as possible. DIA threat system references for every platform in your AOR. The ACO (Airspace Control Order) and ATO (Air Tasking Order) — not intel products, but you cannot brief a mission without understanding what's on them. JIPOE (Joint Intelligence Preparation of the Operational Environment) doctrine — JP 2-01.3.

Intel products at this tier are evaluated on accuracy, timeliness, and relevance to the specific mission. 'Accurate but irrelevant' is a failure. A route threat assessment that covers every threat system in the country but does not tell the aircrew which ones are within lethal range of their specific route is not a useful product — it is coverage purchased at the cost of clarity. Every product you produce should be able to answer the question: 'So what does the pilot do differently based on this?' If you cannot answer that, revise the product.

Over-reliance on CPOF, MIDB, or whatever the current authoritative database is — databases reflect what was reported, not what is true. Treating finished intelligence from higher as ground truth instead of as one input. Not understanding the collection timelines behind your sources — imagery that is 72 hours old in a contested environment is not the same as imagery that is 72 hours old over a static garrison. Letting tool proficiency substitute for analytical judgment. The DCGS-AF system is powerful and confusing; learn it, but do not let it think for you.

Your first PCS assignment matters more than your score in training. A wing intel section that is operationally busy — actually flying combat or ISR missions, not just training — will develop you faster than a garrison job. Volunteer for deployments early. The AFSC progression wants you to have breadth (multiple platforms, multiple AORs) at the junior level. Bonus programs for 1N4 exist and are worth understanding when you approach your first contract decision point, but the career field has a relatively small community — your reputation starts forming now.

Fighter wing intel section: you brief combat-coded aircrew daily. High tempo, high stakes, direct relationship with operators. The feedback loop is fast and honest. ISR unit: more analytical depth, less frequent direct operator interface, but you are often building the products that feed everyone else. Mobility wing: different threat sets, different mission profiles, but intel is still integral to force protection and planning. AOC (Air Operations Center): staff work, high volume, less individual ownership of products but more visibility into how intel integrates across the joint force. Deployed locations: all of the above, compressed, with constrained resources.

A good junior 1N4 can walk into a pre-mission brief with a pilot who has never met them, establish credibility in the first thirty seconds, deliver the threat picture in a way that is honest about uncertainty, and answer follow-up questions without flinching. They update their products when new reporting changes the picture — not when told to, but because they are tracking the AOR continuously. They know which threats are the most dangerous to the specific mission profile, not just which threats exist. Good looks like: the aircrew debrief references something from your brief that changed how they flew. That is the standard.

SrA is where you are expected to own a lane independently. Junior analysts who get promoted early have demonstrated they can produce without supervision, brief without hand-holding, and bring something new to the shop's understanding of the AOR. Start looking for that one area — a specific threat system, a specific adversary unit, a specific geographic area — where you become the person others consult. That expertise is your SrA story.