Skip to main content
HonestMOS
●InvestigationsCongress made VA disability claims free to file. An entire industry charges veterans anyway — and nobody can stop them.→
←Back to 57A Simulations Operations Officer — overview, pay, training, civilian translation, reviews
57AO3-O4

Simulations Operations Officer

O-3 to O-4 (Field Grade) · Army

O1–O2O3–O4
HEADS UP

The MSEL is not the exercise. The MSEL is the instrument you use to create conditions the commander uses to train his formation. Every design decision you make — every inject, every OPFOR move, every notional friction point — either serves the commander's training objectives or it does not. The supported commander cannot see the difference between a well-designed exercise and a technically impressive one until the AAR. You can. That is the job.

The Honest MOS Read
The FA57 captain or major is the officer standing between the supported commander and a training simulation that runs or fails. The general is in the TOC. The brigade S-3 is running the planning cycle under exercise conditions. The OPFOR is maneuvering per the white cell's plan. The civilian role players are seeding the information environment. All of it is controlled, timed, and injected from the simulation cell you are running — and every fidelity decision you made in the six weeks of exercise design is now executing in real time, with no opportunity to revise it and no second chance to get the timing right. The Battle Command Simulation Team (BCST) is the operating unit of the FA57 world. The BSC is the facility. The JLCCTC — Joint Land Component Constructive Training Capability — is the simulation architecture, built around OneSAF (the simulation engine) and AARS (the AAR support layer). At the major Combat Training Centers — JRTC at Fort Johnson, NTC at Fort Irwin, JMRC at Grafenwöhr — the BCST operates within the Operations Group, a dedicated organization that has been running training rotations for years and has the institutional knowledge to support brigade-scale exercises with precision. At home-station BSCs, the FA57 officer is typically the most senior simulation professional in the facility, which means more ownership and less peer learning. Both are real FA57 billets. Neither is easier than the other. The exercise design cycle is the core of the FA57 professional skill set. It starts with the training assessment: what does the supported commander need to train, what has he identified as his formation's training gaps through CATS (Combined Arms Training Strategy) and METL assessment, and what training events in the CATS catalog can simulation best support? From that assessment, the FA57 officer builds the training support plan — a document that translates training objectives into simulation requirements, scenario conditions, OPFOR design, white-cell structure, civilian role-player requirements, and the pre-exercise technical coordination plan. The Master Scenario Events List (MSEL) is the operational instrument that executes the training support plan: a sequenced list of injects, each tied to a training task and standard, timed to create the right conditions at the right moment in the exercise. The unglamorous truth of the FA57 job is that the exercise design is roughly thirty percent of the work and the pre-exercise administration is the other seventy. Server configuration. Network architecture. Classification boundary establishment. Licensing and software maintenance. MSEL deconfliction with the white cell and the OPFOR controller. Coordination with adjacent units and civilian agencies who are providing role players or realistic stimuli. Site surveys and communications checks at the BSC facility weeks before the supported unit arrives. Pre-exercise technical rehearsals that reveal the problems the supported commander will never know happened because you fixed them before he walked into the TOC. The officer who is drawn to FA57 by the intellectual challenge of exercise design but who resists the administrative and technical labor of pre-exercise preparation produces exercises that work on paper and fail in execution. At the captain level, the key development is running a full exercise cycle — from training support plan through AAR product — as the primary FA57 officer for a brigade-level event. The BSC chief or the CTC Operations Group OIC is in the background, available when needed, but the planning, the MSEL design, the team management, and the AAR facilitation are the captain's. The OER narrative that comes out of that cycle is the FA57 equivalent of the company command OER — the primary instrument the major's board reads. At the major level, the seat shifts from exercise execution to organizational management and strategic exercise design. The BSC OIC at a major installation manages a team that includes officers, NCOs, DA civilians, and contractors — each with different authorities, different chains, and different levels of institutional knowledge. The FA57 major who cannot lead that hybrid team cannot run the BSC. The exercises at the major level are also typically larger: division and corps-level events, multi-echelon rotations, CCMD-supported exercises. The design challenge scales accordingly, and the political complexity of coordinating with the supported commander's two-star staff adds a dimension the BCST captain's seat does not prepare you for.
Career Arc
  • 01Captain's Career Course in the basic branch, followed by FA57 functional area transfer — the formal entry into the FA57 operational world.
  • 02First BSC assignment: BCST leader or simulation cell OIC at a home-station BSC or a major CTC — the exercise design and execution seat that produces the KD OER.
  • 03Full exercise cycle as primary FA57 officer: training support plan → MSEL design → exercise execution → AAR facilitation → AAR product delivery to the supported commander.
  • 04ILE / CGSC at Fort Leavenworth — required before the major's board; the FA57 officer competes on the same ILE slate as operational branch officers.
  • 05BSC OIC or senior simulation staff billet at a division, corps, or CCMD exercise directorate at the major level — the field-grade KD equivalent.
  • 06Joint exercise support credit on the O-5 path — CCMD-level exercise assignments or joint simulation billets at a geographic CCMD or USJFCOM successor.
  • 07Battalion XO / S-3 equivalent billet consideration and the centralized command board at the O-5 window — the FA57 path to lieutenant colonel.
Common Screwups
  • ×Running an AAR as a narrative briefing rather than as a performance analysis. The supported commander's two-star does not need a slideshow recap of what happened during the exercise — he watched it happen. What he needs is a structured analysis of task-condition-standard performance against training objectives, with data from the AARS system and the observer-controller record. The FA57 officer who produces an AAR that summarizes the exercise timeline has failed the primary deliverable of the simulation job. The AAR product exists to improve performance, not to document the rotation.
  • ×Hiding a technical failure during the rotation. Network outages, simulation-engine crashes, MSEL timing failures — these happen. The supported commander and his G7 will find out. The FA57 officer who reports problems accurately, proposes solutions, and executes the recovery with minimum disruption to the training audience retains professional credibility. The FA57 officer who manages the perception of the problem rather than the problem itself — who tells the G7 'we're working it' when 'we lost the network for four hours' is the accurate description — produces a career-ending incident at the level of the two-star's debrief.
  • ×Failing to develop the simulation team. The DA civilians and contractors at a major BSC are often more experienced than any officer in the cell. The FA57 captain or major who treats that workforce as support staff rather than as technical professionals loses institutional knowledge the day they transfer and produces exercises of degrading quality across the rotation cycle. The officers who invest in the team — who understand the professional development challenges of a civilian workforce, who advocate for training and certification resources, who ensure the contractor team has what it needs to execute — run BSCs that improve over time instead of BSCs that coast on accumulated institutional knowledge.
  • ×Designing the exercise around the simulation's technical strengths instead of the commander's training objectives. OneSAF is good at certain things and constrained at others. The FA57 officer who designs the MSEL to leverage what the software does well — rather than to create the conditions the commander needs to train the specific task-condition-standard the CATS identified — produces a technically impressive exercise that fails the training audience. The supported commander's staff emerges from the rotation having practiced what the simulation made easy, not what they needed to master.
  • ×Missing the ILE / CGSC window by failing to plan the schoolhouse sequence. ILE is required before the major's board. The assignment timeline for functional area officers can create gaps in the schoolhouse sequence if the FA57 officer does not actively manage the career plan — a long BSC tour without a schoolhouse window, an extended CTC assignment that consumes the ILE slot, a joint tour that delays the CGSC completion. The FA57 officer who arrives at the major's board without ILE complete has a structural disadvantage that no OER narrative can fully compensate for.

A Day in the Life

  • 0530-0630PT — officer standard. As the BSC OIC, your PT schedule is your own to manage. Run with the NCOs if they will have you. The simulation team respects the officer who is not using the staff job as a fitness exemption.
  • 0630-0730Shower, change. Scan the overnight simulation-cell log if a 24-hour exercise is running — any network events, any MSEL deviations, any issues the overnight crew flagged for morning resolution.
  • 0730-0800Arrive at the BSC. Morning accountability of the team — military, DA civilian, contractor. Review the exercise day's MSEL execution schedule if a rotation is active.
  • 0800-0900Planning cell work — exercise design meeting with the white cell and OPFOR controller if in pre-exercise planning; MSEL status debrief if a rotation is executing. The morning meeting is the exercise control cell's primary coordination window.
  • 0900-1130Exercise execution oversight if a rotation is live: walking the simulation cell floor, monitoring MSEL inject delivery, coordinating with the white cell on timing adjustments, managing the network status board.
  • 0900-1130Exercise design work if in the planning phase: training support plan writing, MSEL development, coordination with the supported commander's G7, technical rehearsal scheduling.
  • 1130-1300Noon meal — the simulation cell goes to a staggered meal schedule during active rotations; the FA57 officer coordinates coverage before leaving the floor.
  • 1300-1500AAR support preparation if the rotation is in the AAR phase: pulling AARS data, building the performance analysis against training objectives, coordinating with observer-controllers on their observation records.
  • 1300-1500Administrative work during non-exercise periods: OERs on simulation team officers, TADSS accountability reports, coordination with the supported commander's staff on the next rotation's planning conference schedule, BSC facility maintenance coordination.
  • 1500-1700Briefings and coordination: update to the BSC commander or CTC Operations Group OIC on exercise status, coordination call with the supported commander's G7 on upcoming planning milestones, pre-exercise technical rehearsal oversight if a rotation is approaching.
  • 1700-1800End-of-day simulation cell status check. Confirm overnight crew coverage if the exercise runs 24 hours. Debrief the senior simulation NCO on the day's execution.
  • 1800-2000Personal time — but exercise planning does not stop at 1800 when the supported commander's training conference is in 72 hours and the MSEL is not finished. Expect extended planning sessions in the two weeks before a major rotation.
  • 2000-2200Doctrine reading, professional reading, or OER narrative development if not in an active rotation window. The FA57 officer who is not actively reading FM 7-0 and ATP 7-0.1 is falling behind the supported commanders he serves.

Weekly Cadence

The FA57 week is shaped entirely by the exercise calendar. During a rotation at a major CTC, the week is 24-hour operations: the simulation cell runs around the clock, the MSEL executes on the supported commander's battle rhythm, and the FA57 officer is on the floor from opening to closing of each exercise day with an overnight crew carrying the operation while he sleeps. The rotation week is the highest-intensity week in the FA57 year — everything that was not fixed in the pre-exercise technical rehearsal will surface in the first 48 hours, and every timing problem in the MSEL will become visible the moment the supported brigade's planning cycle is under stress. Between rotations, the week is an exercise planning week. The planning cycle for a major brigade-level CTC rotation runs six to ten weeks from the initial training support plan conference through the pre-exercise technical rehearsal. The early planning weeks are dominated by coordination meetings, training objective confirmation, MSEL drafting, and scenario development. The middle planning weeks are dominated by MSEL deconfliction with the white cell and OPFOR controller — the painful process of ensuring that every inject is timed correctly, sequenced logically, and does not conflict with adjacent injects in a way that creates confusion rather than training stress. The late planning weeks are dominated by technical rehearsals, network configuration verification, and the pre-exercise site survey at the exercise facility. At a home-station BSC between major rotations, the cadence is looser but not quiet. Exercise design for the next supported unit event, TADSS maintenance and readiness reporting, coordination with the division or corps G7 on the training calendar, OER and counseling cycles for the simulation team, and the administrative load of managing a mixed military-civilian-contractor workforce fill the inter-rotation weeks. The FA57 officer who treats the inter-rotation period as a rest period arrives at the next planning cycle behind the schedule he needs to be ahead of.

Key Skills — How to Drill Each

  1. 01
    Design a Master Scenario Events List (MSEL) tied to the supported commander's training objectives per FM 7-0 and ATP 7-0.1.
    Start with the training objectives — every MSEL design session begins with the question 'what is the commander trying to train?' before any inject is written. Read the supported commander's training assessment, his METL, and the CATS-identified collective training tasks. Map each proposed inject to a specific task-condition-standard. If an inject does not address a training objective on the list, do not put it in the MSEL — the exercise will run long and the AAR will have no data to analyze. Brief the supported commander's G7 on the MSEL design logic before a single inject is written in final form. The design that survives that brief is the design worth executing.
  2. 02
    Operate and troubleshoot the JLCCTC architecture — AARS, OneSAF, and supporting software — to the standard required to run a brigade or division exercise without losing fidelity mid-rotation.
    The FA57 officer does not need to be the lead software engineer on the simulation system — that role belongs to the contractor operators and the DA civilian workforce. But you need to understand the system architecture at the level required to recognize when a problem is a software issue, a network issue, a classification boundary issue, or a user-error issue — and to direct the right people to the right problem under time pressure. Study the JLCCTC architecture documentation. Run the pre-exercise technical rehearsals yourself, not through the contractor. Know what the system looks like when it is working correctly so you recognize immediately when it is not.
  3. 03
    Facilitate an After Action Review at the brigade or division level — driven by simulation data and observation records — that the commander and staff use for follow-on training planning.
    The AAR is not a briefing. It is a structured performance analysis. The FA57 officer who facilitates an AAR drives the session from the training objective list, uses AARS data and observer-controller notes to surface specific performance gaps, and closes each gap with a concrete training action the unit can take before the next event. Practice the AAR facilitation skill before the rotation by running internal AARs on the simulation team's own exercise execution — the MSEL timing, the inject delivery, the network performance. The team that AARs its own execution improves faster than the team that only AARs the supported formation.
  4. 04
    Translate a commander's training intent into an exercise design: training objectives, OPFOR design, scenario conditions, end-state, and constraints.
    This translation skill is the core FA57 competency and the hardest one to develop without repetition. The starting point is the training objective meeting with the supported commander or his G7 — a conversation, not a briefing. Listen to what the commander says about his formation's gaps. Ask questions that surface the implicit training requirements he has not articulated: 'What went wrong at the last rotation that you want the staff to be better at this time?' 'What decision point in the last exercise did the staff handle poorly?' The answers to those questions are the MSEL design inputs. The formal training objective list is the output.
  5. 05
    Manage exercise-network architecture and coordination: simulation cell connectivity, classified-network accesses, boundary coordination with adjacent units, white-cell and role-player integration.
    The network is the foundation of the exercise fidelity. Build the network architecture diagram before the first planning conference and brief it to the supported commander's G6 for coordination. Establish the classification boundaries — SIPR, NIPR, and the simulation network — in writing before the exercise site survey. Run the pre-exercise technical rehearsal at the BSC facility at least five working days before the supported unit arrives, not the day before the rotation starts. The technical failures that happen on Day 1 of a CTC rotation are, in almost every case, failures that could have been discovered and fixed during the pre-exercise rehearsal that the FA57 officer chose not to schedule.
  6. 06
    Supervise and develop simulation teams — military, DA civilian, and contractor operators — through exercise planning cycles, rotation execution, and AARs.
    The hybrid workforce at a major BSC is the most complex leadership challenge in the FA57 career. Military personnel follow the UCMJ and the officer-NCO relationship structure. DA civilians follow the civilian personnel system and have union protections that require a different management approach. Contractors follow the performance work statement of the contract vehicle. All three groups have different authorities, different evaluation instruments, and different professional development pathways. The FA57 officer who applies military leadership patterns uniformly across all three groups creates friction with the civilian workforce and degrades the team's institutional knowledge. Understand the authority boundaries. Work within them. Build the team across all three groups.

Manuals & References — What Chapters Matter

  • FM 7-0 — Train to Win in a Complex World.
    The capstone training doctrine and the conceptual foundation of every exercise the FA57 officer designs. Chapter 4 (collective training) and Chapter 5 (training assessment) are the primary FA57 references — the METL, CATS, and training management processes named there are the framework the supported commander is working from when he walks into the exercise design conference. Know this document as well as the supported commander's G7 knows it, because the design conversation is going to be conducted in FM 7-0 language.
  • ATP 7-0.1 — Brigade Combat Team Training Management.
    The BCT-level implementation guide. The BCST operations chapter names the FA57 officer's role explicitly — what a Battle Command Simulation Team does, how it integrates with the supported commander's battle rhythm, what the exercise design products look like, and how the AAR support function works. This is the document the supported commander's G7 will cite in the exercise design conference. Arrive having already read it.
  • AR 350-38 — Training Aids, Devices, Simulations, and Simulations (TADSS).
    The regulatory authority for all simulation systems. The FA57 officer as BSC OIC signs for government simulation equipment and manages the TADSS request, fielding, maintenance, and disposition process under this regulation. The specific requirements for TADSS accountability, readiness reporting, and modification authority are named here. A BSC that does not comply with AR 350-38 is a BSC that creates property accountability problems the commanding general sees.
  • AR 350-1 — Army Training and Leader Development.
    The commander's authority and responsibility framework for training. The FA57 officer is the staff integrator executing this policy at the BSC level — the regulation that gives the supported commander his training responsibilities is the same regulation that defines the simulation support function the FA57 officer provides. Understand how the training management authority chain works: the supported commander's commander owns the training assessment, the training objectives belong to the supported commander, and the simulation support is the FA57 officer's instrument — not his agenda.
  • DA PAM 600-3 — Officer Professional Development and Career Management, FA57 chapter.
    The authoritative source on FA57 KD requirements, ILE/CGSC gates, joint-duty credit requirements, and post-BSC billet options at the O-4 and O-5 level. Read this before every assignment discussion with the career manager. The field-grade career architecture described in this document is the one the centralized selection board uses when they read the FA57 major's OER record. Know what the board is looking for before you construct the OER narrative.
  • AR 623-3 / DA PAM 623-3 — Evaluation Reporting System.
    At the CPT/MAJ level the FA57 officer is writing OERs on his simulation team officers and senior warrant officers. The rated officer's performance is only as visible to the centralized board as the OER narrative makes it — a generic OER on a strong simulation officer wastes the career investment the officer has made. Write specific, action/result/impact narratives with measurable outcomes: exercise cycles managed, rotations executed without network outage, AAR products used by supported commanders for follow-on planning. The senior rater signs what is defensible. Make the bullets defensible.

Standards — How to Hit Each

  • Intermediate Level Education (ILE) / CGSC at Fort Leavenworth — required before the major's board.
    Build the ILE window into the career plan from the captain's career course — identify the assignment sequence that accommodates the schoolhouse slot before the O-4 board date. The assignment manager can help build the timeline if asked explicitly. The FA57 officer who arrives at the major's board without ILE complete has a structural disadvantage that no single OER can fully compensate for. If a long BSC tour or a joint assignment is consuming the ILE window, engage the career manager before the window closes, not after.
  • Successful BSC OIC or BCST leader tour with documented exercise outcomes — rotation executed to the supported commander's training objectives.
    The KD OER for the BSC tour is the primary instrument the major's board reads for FA57 officers. Build the OER narrative the same way a company commander builds the command OER narrative: measurable outcomes (rotations executed, AAR products delivered, simulation uptime percentage, MSEL fidelity), development of the team (officers mentored, DA civilians trained, contractor performance documented), and the commander's explicit assessment of the exercise quality. Get the supported commander's endorsement in writing — a command-team OER or an MFR of record — before the tour ends. The board cannot read what is not documented.
  • Joint exercise support credit on the path to O-5 — CCMD-level exercise assignments or joint simulation billets.
    Joint duty credit for FA57 officers comes primarily from CCMD-level exercise support billets, joint training center assignments, or coalition partner training coordination roles. The joint-duty requirement for field-grade officers is documented in DoD Instruction 1300.19 and the Army's implementing guidance. Build the joint assignment into the career plan at the captain level — identify the billets in your functional area that generate joint-duty credit and communicate that preference to the career manager before the major's assignment window. The FA57 officer who arrives at the O-5 board without joint-duty credit has a competitive disadvantage in the field-grade cohort.
  • Coordination-level proficiency with the simulation systems at the BSC — JLCCTC, OneSAF, AARS.
    Coordination-level proficiency means: you can describe the system architecture accurately to a supported commander's G6, you can recognize when the contractor operators are working around a problem rather than fixing it, and you can make the system-level decision (restart the simulation engine, rebuild the MSEL in a degraded-mode configuration, declare an exercise pause) without waiting for the contractor to propose it. This proficiency comes from observation during exercise execution, from the pre-exercise technical rehearsal you run yourself rather than delegating, and from the technical documentation the contractor team maintains on the JLCCTC configuration at your BSC. Read it. Study the architecture diagrams. The proficiency does not require software certification — it requires informed leadership.
  • Exercise design credit at brigade or above — at least one rotation as the primary architect of the training support plan and MSEL, signed off by the supported commander.
    The training support plan and MSEL that carries the supported commander's signature is the FA57 equivalent of the company command report — the primary instrument that says 'this officer designed a brigade-level exercise.' Ensure the training support plan document includes the FA57 officer's name as the primary author and that the MSEL reflects his design decisions, not just the default template. Brief the training support plan to the supported commander in person before the exercise kicks off and document that brief in the exercise record. The OER narrative built from a training support plan that the commander signed and the simulation executed without major deviation is a defensible KD bullet.

Technical Mistakes — Concrete Consequences

  • Building the MSEL around the simulation's technical strengths instead of the commander's training objectives.
    The supported commander and his G7 figure this out in the AAR — when the formation's documented training gaps remain unaddressed because the exercise created conditions for tasks the simulation could easily support rather than tasks the commander needed to train. The G7 debrief with the two-star goes poorly. The FA57 officer's next OER reflects the exercise quality. The rotation costs the supported formation time, resources, and opportunity they will not get back. A MSEL designed around software convenience instead of training objectives is the highest-frequency and highest-cost failure mode in the FA57 career.
  • Running an AAR as a narrative briefing rather than as a performance analysis.
    The supported commander leaves the AAR knowing approximately what he already knew going in — that certain things went well and certain things went poorly. He does not have a structured performance gap analysis tied to specific task-condition-standard data. He does not have a training action plan for the next event. The AAR product ends up in a SharePoint folder and the formation's next training event does not reflect the lessons from the simulation rotation. The FA57 officer's primary deliverable — closing the training feedback loop — has not been delivered. The G7 notes this. The OER narrative reflects it.
  • Missing the pre-exercise communications and network rehearsal because 'the contractor will sort it out on site.'
    Day 1 of the rotation, the supported brigade's command group arrives in the TOC and the simulation network is not up. The SIPR connection is not established. The OneSAF engine is throwing a configuration error that the contractor operator has seen before but did not flag in the pre-exercise site survey report. The two-star's aide calls the G7. The G7 calls the FA57 officer. The exercise is delayed by four hours. The supported commander loses four hours of the only three days his staff gets to train against the specific scenario conditions the MSEL was designed to create. That four hours is not recoverable. The technical rehearsal five days earlier would have caught the problem in 45 minutes.
  • Confusing exercise complexity with training value.
    A more complex MSEL — more injects, more OPFOR, more white-cell friction, more simultaneous threads — does not produce proportionally more training value. The supported commander's staff has a finite cognitive bandwidth. An exercise designed at higher complexity than the training audience can process creates confusion, not training stress. The formation learns to manage chaos rather than to execute their tasks correctly. The AAR data reflects degraded performance across all tasks because the exercise was too complex to isolate the performance gaps the commander needed to see. The FA57 officer who defaults to complexity as a design tool rather than calibrating complexity to the training objective has not understood the job.
  • Underestimating the civilian and contractor workforce as subordinates.
    The senior DA civilian at a major BSC may have been operating simulation systems for fifteen years across twenty CTC rotations. The lead contractor operator may have more JLCCTC hours than any officer in the cell. The FA57 captain who walks into the BSC as the OIC and immediately tries to demonstrate technical authority over people with ten times his exercise repetitions loses the team in the first week. The institutional knowledge leaves with the civilian workforce when they disengage professionally — and institutional knowledge at a major BSC is the primary quality differentiator between a well-run rotation and a rotation that barely executes the MSEL. The team disengagement does not appear in any official report. It shows up in the exercise quality, and the supported commander's G7 is the first to notice.

Career Decisions at This Rank

  • Whether to pursue a CTC-based assignment versus a home-station BSC billet as the primary KD tour.
    The major CTCs — JRTC, NTC, JMRC — offer higher exercise volume, stronger peer learning (from other experienced FA57 officers and the institutional CTC Operations Group), and more visible KD OER narratives because the supported commanders are senior and the exercise outcomes are closely watched by TRADOC and the Army Staff. The home-station BSC offers more exercise design ownership, a more direct relationship with the supported commander, and often more management responsibility because the FA57 officer is typically the most senior simulation professional in the facility. Both are legitimate KD tours. The CTC assignment is slightly more competitive for the major's board because the peer learning and volume produce stronger exercise design skills faster. The home-station assignment may offer better quality of life and more family stability. Neither choice is wrong — the question is which fits the officer's career trajectory and personal situation.
  • When to pursue the joint-duty assignment and how to sequence it with the ILE / CGSC requirement.
    The joint-duty credit requirement for field-grade officers adds a sequencing constraint to the FA57 career that operational branch officers manage differently. For most FA57 officers, the practical sequence is: (1) BSC or BCST leader KD tour at captain level, (2) ILE / CGSC before the major's board, (3) joint exercise support assignment at the major level or a CCMD-level billet before the O-5 board. Compressing or reordering this sequence — a joint tour before ILE, or a second BSC tour instead of a joint billet — creates downstream risk. The career manager can map the specific timeline for the current year group. Ask explicitly before the captain's career course assignment conference and again before the major's assignment window.
  • Whether to transition into a related functional area — FA24 (Telecommunications Systems Engineer), FA53 (Information Systems Management), FA26 (Information Network Engineer) — or remain in FA57.
    Some FA57 officers develop strong systems integration and network architecture skills through their JLCCTC work and find that FA24 or FA26 or FA53 is a better fit for the direction their expertise has grown. The cross-functional area transfer is possible but requires coordination with career managers in both functional areas and is typically managed at the major-to-lieutenant colonel window. The honest analysis: if the simulation operations work — the exercise design, the MSEL development, the AAR facilitation — is the intellectually compelling part of the job, stay in FA57. If the technical systems work — the network architecture, the software integration, the classified system management — is where the genuine professional interest lies, a technical FA may be a better long-term fit. Make the decision based on genuine assessment of where the work is most engaging, not on which functional area appears to have a better promotion rate at a given moment.
  • How to manage the BSC's DA civilian and contractor workforce — specifically the authority boundaries and the performance management tools available.
    The FA57 officer who arrives at the BSC OIC seat without prior supervisory experience with civilian personnel is immediately behind the learning curve. DA civilians are evaluated through the Army Civilian Evaluation System — a different instrument from the military OER system, with different performance dimensions and different authority structures. Contractors are managed through the performance work statement and the contracting officer's representative (COR) relationship — the FA57 officer may serve as the COR or may be adjacent to the COR function, but the authority to direct contractor work flows through the contract vehicle, not through military authority. Invest in understanding the civilian personnel system early in the BSC tour, before a performance problem requires you to use it. The HR advisor at the installation is the resource — use them before the problem, not after.
  • Whether to pursue the centralized selection list (CSL) for battalion-level command equivalent or the senior functional area staff path at O-5.
    FA57 officers at the O-5 level compete for senior staff positions at division, corps, and CCMD level — not for battalion command in the traditional operational sense. The functional area officer's O-5 career path is documented in DA PAM 600-3 and runs through senior simulation staff billets, TRADOC senior exercise designer roles, and joint exercise directorate positions. The selection for these billets is competitive and managed through the functional area assignment process. Officers who want the most competitive O-5 record build a major's career that includes the KD BSC tour, ILE complete, joint-duty credit, and at least one large-scale exercise (division or CCMD level) as the senior FA57 officer. Pull the current HRC board demographics before making the O-5 career plan — the selection math changes by year group and functional area.

How the Seat Varies by Unit Type

  • Combat Training Center — JRTC (Fort Johnson, LA)
    JRTC is the Army's premier joint and combined arms training center for light and airborne formations — 82nd Airborne, 101st Airborne (Air Assault), light infantry BCTs, ARSOF. The JRTC Operations Group runs FA57 officers through brigade-scale rotations focused on light infantry conditions: complex terrain, COIN-adjacent scenarios, joint fires integration, and ISR employment. The FA57 officer at JRTC develops expertise in simulation support for light maneuver that is different from the heavy combined arms environment at NTC. Rotations typically run roughly two weeks per brigade and the annual rotation count keeps the FA57 team at a high operational tempo.
  • Combat Training Center — NTC (Fort Irwin, CA)
    NTC is the Army's premier training center for heavy combined arms formations — Armored BCTs, Stryker BCTs, and the associated support formations. The desert terrain and the OPFOR's 11th ACR provide the most intense near-peer combined arms training environment in the Army's training system. The FA57 officer at NTC develops expertise in simulation support for heavy maneuver — JLTV, Abrams, Bradley, Paladin, HIMARS, and the full combined arms toolkit at echelon. The exercise complexity is higher than at JRTC because the formations are heavier and the OPFOR is a dedicated regimental-level opposing force with institutional knowledge of NTC terrain and doctrine.
  • Combat Training Center — JMRC (Grafenwöhr, Germany)
    JMRC is USAREUR-AF's combat training center, running rotations for European-based BCTs and supporting NATO coalition partner training events. The FA57 officer at JMRC adds a coalition and multinational dimension to the simulation support function — coordination with allied nation simulation cells, scenario design that incorporates NATO doctrine alongside Army doctrine, and the cultural competency requirements of a coalition exercise environment. Rotations at JMRC are also subject to the theater-specific OPSEC and information management requirements that USAREUR-AF manages for European-based exercises.
  • Division or Corps Home-Station BSC
    The home-station BSC at a major Army installation runs exercises in direct support of the organic formation — the 82nd Airborne Division BSC at Fort Liberty, the III Corps BSC at Fort Cavazos, the 25th Infantry Division BSC at JBLM. The FA57 officer here is typically the senior simulation professional at the facility, with more design ownership and a more direct relationship with the division or corps G7 than is possible at a CTC. The rotation pace is lower but the exercise design cycle is longer — the home-station BSC is planning exercises for its formation's annual training calendar, not running six-week rotational cycles. The supported commander relationship is also more sustained: the FA57 officer works with the same two-star staff across multiple exercise events rather than supporting a new brigade every six weeks.
  • CCMD Joint Exercise Directorate / Theater-Level Exercise Cell
    Senior FA57 officers — typically majors and above — serve in geographic CCMD exercise directorates at USINDOPACOM, USEUCOM, USAFRICOM, or USSOUTHCOM. These billets involve planning and executing theater-level command post exercises (CPX) and computer-assisted exercises (CAX) that support CCMD-level training objectives and theater security cooperation plans. The simulation architecture is joint — JTLS, JCATS, or other joint simulation systems alongside the Army-specific JLCCTC — and the coordination complexity involves multiple service components and coalition partner nations. The joint tour provides the joint-duty credit required for field-grade officers and expands the FA57 officer's professional toolkit beyond Army-specific simulation systems and doctrine.

What Good Looks Like at This Rank

The good FA57 captain is the one the supported commander's G7 calls before the training support plan conference, not after. Not because the FA57 officer has been marketing himself or lobbying for early access — but because the last rotation this officer ran came back clean: the MSEL fidelity was high, the AAR product was used by the commander's staff to restructure the next six months of home-station training, and there were zero network outages during the exercise that the two-star noticed. The G7 calls because trust is the product of execution, and execution built that trust across one rotation. His exercise design work is identifiable. The training support plan carries his analytical fingerprints: a training objective list derived from the supported commander's actual METL assessment rather than from the template, a scenario that creates conditions specifically tied to the tasks the formation needs to train rather than conditions the simulation can produce cheaply, and a MSEL with inject timing that reflects genuine understanding of how the brigade's planning cycle works — when the fires coordination meeting happens, when the FRAGO is typically issued, when the S-4 is most likely to be distracted by a logistics coordination problem and least likely to notice a sustainment inject. That level of design specificity comes from operational experience as a platoon leader who watched how the BCT's battle rhythm works under training stress. The branch-detail work was real, and it shows. At the major level, the good FA57 officer is running the BSC with a team that is better than when he arrived. The DA civilians are developing professionally — they have been given training resources, have been included in the exercise design conversation, have been recognized explicitly in the post-rotation AAR. The contractor performance work statement is being executed to standard because the FA57 major understands what the contract says and has held the contractor accountable to it from the first rotation. The junior simulation officers have OERs that reflect specific, measurable exercise outcomes rather than generic staff-billet narratives, and the senior rater has signed them without a rewrite because the bullets are defensible. The next FA57 captain who arrives will find a BSC that runs better than he was handed one — and that compounding improvement in institutional quality is the field-grade FA57 legacy that the general officers who use the BSC eventually notice, even if they cannot name exactly why this BSC is better than the last one they trained at.

Preview — The Next Rank

The O-5 FA57 career is a senior staff career. There is no battalion command equivalent in the functional area — the senior simulation billet at a major BSC or a CCMD exercise directorate is the capstone operational assignment, and the O-5 who holds that billet is the most senior FA57 professional in the organization. The weight is different from what the O-3 and O-4 years prepared you for: you are no longer the officer designing exercises and managing simulation cells — you are the officer whose job is to ensure that the entire simulation support function for a division, corps, or theater is properly resourced, properly staffed, and properly aligned to the commander's training objectives across a multi-year planning horizon. The O-5 seat also carries the institutional responsibility for the functional area itself. Senior FA57 officers serve in TRADOC and on the Army Staff in roles that shape FA57 doctrine, career management policy, and simulation system fielding decisions. The officer who has run three or four major exercise rotations and a joint billet arrives at the O-5 level with enough professional depth to contribute to those institutional conversations — and enough credibility with the operations community to be heard when the conversation is about what the Army's simulation training enterprise should look like at the next echelon. The honest preview: the transition from O-4 to O-5 in FA57 is a transition from technical professional to senior leader of a technical enterprise. The skills that made you a good BSC OIC — MSEL design precision, simulation technical proficiency, AAR facilitation depth — are necessary but no longer sufficient. The senior FA57 officer needs the organizational leadership skills to manage a large mixed workforce, the strategic communication skills to brief the general officer on training enterprise readiness, and the institutional knowledge to navigate the TRADOC and Army Staff processes that resource and field the simulation systems you have been operating for the last decade. Start building those skills at the captain level. The O-5 career starts in the decisions you make about team development and organizational leadership in the years before you are selected.
FAQ

57A O3-O4 — Frequently Asked Questions

Q01What does a O3-O4 57A (Simulations Operations Officer) actually do?
The FA57 captain or major is the officer standing between the supported commander and a training simulation that runs or fails.
Q02What's the most important thing to know as a O3-O4 57A?
The MSEL is not the exercise.
Q03What does a typical day look like for a O3-O4 57A?
Time-blocked day at the O3-O4 57A rank tier: 0530-0630 PT — officer standard. As the BSC OIC, your PT schedule is your own to manage. Run with the NCOs if they will have you. The simulation team respects the officer who is not using the staff job as a fitness exemption, 0630-0730 Shower, change. Scan the overnight simulation-cell log if a 24-hour exercise is running — any network events, any MSEL deviations, any issues the overnight crew flagged for morning resolution, 0730-0800 Arrive at the BSC. Morning accountability of the team — military, DA civilian, contractor.…
Q04What mistakes get O3-O4 57A soldiers fired or relieved?
Running an AAR as a narrative briefing rather than as a performance analysis. The supported commander's two-star does not need a slideshow recap of what happened during the exercise — he watched it happen. What he needs is a structured analysis of task-condition-standard performance against training objectives, with data from the AARS system and the observer-controller record.…
Q05What career decisions matter most at the O3-O4 57A rank tier?
Whether to pursue a CTC-based assignment versus a home-station BSC billet as the primary KD tour — The major CTCs — JRTC, NTC, JMRC — offer higher exercise volume, stronger peer learning (from other experienced FA57 officers and the institutional CTC Operations Group), and more visible KD OER narratives because the supported commanders are senior and the exercise outcomes are closely watched by TRADOC and the Army Staff. The home-station BSC offers more exercise design ownership, a more direct relationship with the supported commander,…
Q06What's next after O3-O4 for a 57A (Simulations Operations Officer) in the Army?
The O-5 FA57 career is a senior staff career.

Based on 6 tips from 0 contributors

Published by the Honest MOS Editorial DeskVerified against DoD/.gov sourcesUpdated May 2026Editorial standards