Operational Contract Support stripped down to what you actually need to know. No fluff, no 200-page handbooks. Just the stuff that matters when you're the new CCO on the ground.
You just got to your deployed location. You've got your gear, your laptop, and your warrant. Before anyone says the words "operational contract support" to you, let's walk the base. You already know who runs what.
On a normal Air Force deployment, these units become expeditionary. Your home station CES (CE Squadron) becomes ECES. FSS becomes EFSS. SFS becomes ESFS. Same people, same mission, different name tape.
Simple enough. FSS feeds you and houses you. CE builds things and fixes things. LRS moves stuff. SFS guards stuff. JA keeps you legal. FM keeps you funded. As a contracting officer, you support all of them. They bring you requirements, you buy what they need. That's the job you trained for.
With that foundation, let's look at who's actually doing all that work.
Take a guess: on a mature deployed base, how much of this work is being done by contractors instead of uniformed personnel?
The trend is clear. As conflicts get more complex and the military gets leaner, the contractor footprint grows. In recent operations, there were as many contractors as troops. In humanitarian missions, contractors can outnumber military personnel 30 to 1. The person serving your food at the DFAC, the electricians, the fuel truck drivers, the security at the outer gate? Contractors, all of them.
And the types of services contractors provide have expanded too. It started with laundry and food, and now it includes communications, intelligence support, and armed security. The military doesn't have enough people to do everything, so contractors fill the gaps. They're a force multiplier baked into every operational plan.
That massive contractor workforce running all around you? Somebody had to plan for it, pay for it, hire it, and watch over it. That's OCS. And as the contracting officer on the ground, you're standing right in the middle of it.
Yes, OCS is doctrine. Yes, there are handbooks and joint publications and acronyms stacked on acronyms. But look at the name: Operational Contract Support. The emphasis is on "operational," not "contracting." Contracting is the mechanism. You write contracts, you award task orders, you manage the paperwork. That's planting seeds. OCS is about the plant that grows from those seeds and what it's capable of. It's about understanding what that contracted support actually does for the mission, how it fits into the operation, and where it falls apart if nobody's paying attention.
Every day in a deployed environment, someone is asking: "Can we do this ourselves, or do we need to buy it?" And then: who's buying it, who's paying for it, and who's making sure the contractor does what they said they'd do? That's OCS working.
And it happens at every level of the fight. At the tactical level, it's you on the ground buying generators and managing CORs. You're largely reactionary here, responding to requirements as they come in. At the operational level, it's theater planners integrating contractor support into campaign plans and standing up the boards that synchronize all of it. This level is anticipatory. Enterprise sourcing teams are constantly working to build contracts that are ready before the fight starts. Your AFCAP contracts, your LOGCAP task orders, those exist because somebody at the operational level asked "what could happen?" and built the contract vehicle to cover it. At the strategic level, it's the combatant commands and OSD making decisions about which theater contracts exist, how many contractors the force can absorb, and what the acceptable risk is. OCS runs through all three.
As a new CCO, you'll spend most of your time at the tactical level. But the contracts you task order against? Those were built by operational-level teams who were thinking ahead. Understanding that distinction helps you appreciate why those vehicles exist and how they got there.
All those contractors are on the base. Somebody told them to come here. Somebody's paying them. Somebody's supposed to make sure they're doing their job. Let's trace through a single scenario and see how the pieces fit together.
CE needs a new generator installed at a remote site. The existing one is failing, and the site supports a critical communications relay. CE doesn't have the manpower or the specialized equipment to do the install. They need a contractor.
First question: who writes the requirement? The requiring activity owns the requirement. CE knows they need a 500kW generator installed at a specific location with a concrete pad and fuel hookup. That's their expertise.
But here's where it matters for you as the CCO: your job is to help them get there. CE knows what they need. They probably don't know how to write it in a way that satisfies the FAR, that's clear enough for a contractor to bid on, and that doesn't accidentally box out competition or create a problem downstream. That's where you come in. You know the regulations. You know the contract types. You know how to structure a requirement so it actually works.
And this is the part that separates a good CCO from a bad one. If your mission partner comes to you with a need and your first instinct is to tell them all the reasons it can't be done, you're a liability. You know the FAR. Great. Use that knowledge to find the path forward, not to build a wall. Your job is to help CE, or LRS, or SFS, or whoever walks through your door, achieve the outcome they need. You can be the smartest contracting officer in the world, but if you're not using that knowledge to help your mission partner succeed, it doesn't matter.
Is there a balance? Of course. You can't ignore the law. But the scale should always be tipping toward the warfighter. If you're spending more time explaining why something can't happen than figuring out how it can, recalibrate.
CE brought the requirement. CONS puts together the solicitation, evaluates the offers, and awards the contract. This part you already know from your training. Maybe it goes on an existing theater contract as a task order. Maybe it's a new local contract using simplified procedures. The point is, this is CONS doing what CONS does. We own this step.
The contract is awarded and the contractor shows up. Now who makes sure they're actually installing the generator correctly? Not CONS. We awarded the contract, but we don't know the difference between a good generator install and a bad one. A Contracting Officer Representative (COR) from CE handles day-to-day performance monitoring. They have the technical knowledge to verify the work, document whether it meets the specs, and report back to the contracting officer. We delegate surveillance to the COR through a formal appointment letter. CONS retains the contract authority, meaning we're the ones who can modify, terminate, or take action. But the eyes and ears on the ground are CE's people.
The generator is installed. Contract's running. But now the contractor has a crew of eight people moving around the base every day, and one of them gets stopped at the ECP without proper identification. The gate guard turns them away. The contractor calls your office. CE calls your office. The project is stalled because the crew can't get on base. Whose problem is this?
Everyone's. The contract should have addressed base access procedures and credentialing requirements. The COR should have been verifying that contractor personnel had proper badges before work started. The base commander controls who comes onto the installation. And the contractor should have ensured their people had what they needed. No single office dropped the ball here. Multiple offices each assumed someone else was handling it. This is contractor management, and it's a team sport. When one link in the chain doesn't do their part, the mission stops.
| Task | Who | Why Them |
|---|---|---|
| Write the requirement | CE (Requiring Activity) | They know what they need. We don't tell them what generator to buy. |
| Shape it for contract | CONS | We make it biddable, measurable, and legally sound. |
| Certify funding | FM | They control the money. No certified funds, no contract. |
| Legal advice | JA | Advises on fiscal law, SOFA implications, inherently governmental questions. They're advisors, not decision-makers. Their input matters, but it's guidance, not a veto. |
| Solicit, evaluate, award | CONS | This is our lane. We own the acquisition process. |
| Monitor daily performance | COR (from CE) | Technical expertise to verify the work meets the specs. |
| Contract authority (mods, termination) | CONS | Only the KO can modify or terminate. CORs report, we act. |
| Base access & force protection | Commander + SFS + CONS | The commander controls who's on the installation. SFS executes at the gate. CONS ensures the contract addresses access requirements and pushes credentialing through. You support the commander by making it happen. |
| Contractor credentialing & base access | CONS + COR + Commander | Contract specifies requirements. COR verifies compliance. Commander controls installation access. |
Look at that table. CONS shows up repeatedly, but we're not the only ones there. That's the nature of OCS. No single office owns the whole picture. The system works when everyone understands their piece, and it breaks when anyone assumes it's somebody else's problem.
Whenever you're dealing with contracted support in a deployed environment, you can cut through the noise with three questions:
1. Who has the authority? (Who can make decisions about this contract?)
2. Who owns the requirement? (Whose need is being filled?)
3. Where are the resources coming from? (Who's paying, and with what money?)
If you can answer those three, you know who's in charge. If you can't, that's your first problem to solve. And notice: CONS has a hand in all three. You hold contracting authority. You help shape the requirement. You validate that the funding is certified before you obligate. You may not "own" every answer, but you're involved in every question.
That generator scenario touched requirement writing, contract award, COR oversight, commander authority, and contractor tracking. One scenario, five different offices involved. That's what OCS looks like at the tactical level. Now imagine scaling that across an entire theater.
One generator at one site is manageable. But now zoom out. You're in a theater with 50 bases, thousands of contractors, hundreds of active contracts, and multiple services all operating at the same time. Army is running LOGCAP. Air Force has AFCAP. Navy has WEXMAC. DLA is providing fuel and subsistence. And every unit on every base has their own requirements they want on contract yesterday. At the heart of all of it, every single one of those efforts requires a contract to execute off of. CONS is the conductor of that orchestra.
This is where it stops being about one scenario and starts being about a system. And that system doesn't just involve contracting.
When you deploy to a joint environment, your base or theater falls under a joint task force (JTF) or a combatant command (CCMD). Those organizations have a headquarters staff organized into numbered directorates, called "the J-staff." Think of it as the HQ's functional departments: J-1 handles personnel, J-2 handles intelligence, J-3 handles operations, J-4 handles logistics, and so on through J-9.
Where are these people? It depends. The combatant command HQ (like CENTCOM at MacDill AFB or EUCOM in Stuttgart) might be on the other side of the world from you. A JTF headquarters might be on your base or at a different location in theater. Sometimes you'll interact with them face-to-face. Sometimes it's all email and VTCs. Either way, their decisions affect your operations. When they identify a need that requires contracted support, that requirement flows down to you. OCS touches every single one of these directorates, but as a CCO, there are three you need to understand well.
J-4 (Logistics) is your closest partner. They're the lead integrator for commercial capabilities in the operation. Common-user logistics, host nation support, theater logistics analysis, sustaining and moving contractors. When the operation needs contracted support, J-4 is usually the one coordinating it at the staff level. You'll work with them constantly.
J-3 (Operations) validates and prioritizes requirements. They handle force protection, base access, contractor badging, arming of contractors, and private security oversight. When a requirement shows up that touches operational security or the day-to-day running of the base, J-3 is in the mix.
J-8 (Resource Management) controls the money. Budget estimates, types of funding, monitoring contract expenditures, cost analysis. If you don't have a relationship with J-8, you're going to have a hard time getting contracts funded. No certified funds, no contract.
The rest of the staff matters too. Click around the wheel below to see what each directorate brings to OCS. You don't need to memorize all of it, but knowing it exists helps when a requirement comes from a direction you didn't expect.
Every single one of those directorates generates or touches contracted requirements. J-4 needs a logistics contract. J-3 needs private security vetted. J-6 needs satellite communications. J-8 needs to certify funding before any of it moves. The requirement originates with them, gets shaped and contracted through CONS, and then gets managed by CORs from those same directorates. That's why OCS is a staff-wide function, not just a contracting function. Understanding who these people are and what they care about is how you connect the dots when work lands on your desk.
OCS doctrine organizes all of this into a 9-element process. Think of it as the lifecycle of a deployment, and at each step, there's a question to answer.
As a CCO on the ground, you're probably picking up this process somewhere around steps 4 through 8. Preparation, funding, award, integration, oversight. That's your daily reality, and that's fine. But somewhere down the road, you're going to be on a staff, and the front end of this process, the planning, the requirements, the support type decisions, that's going to be your world. The whole process matters. You just might not touch all of it yet.
Notice how CONS shows up at almost every step? We don't "own" the entire process. But we're the only career field that touches every single element. That's what makes contracting unique in OCS: we're never fully in charge, but we're never fully out of the picture either.
This is the judgment call that separates a good deployed CCO from one who's just filling a seat. You need to know when to step up, when to advise from the side, and when to stay out of the way.
There are a lot of contract vehicles in play across a theater. These are the major ones you'll hear about. You don't need to memorize every detail, but you should know they exist, how they work, and how to advise your commander on what they can do.
These aren't the only vehicles out there. There are construction contracts (like GCCMAC and GCSMAC), IT contracts, and service-specific vehicles for just about every functional area. The landscape is deep. But the ones above are the heavyweights you'll encounter most often.
You as a deployed CCO may not be the one executing task orders on LOGCAP or AFCAP. Those are typically managed by dedicated program offices or reach-back contracting teams. But you need to understand how they work so you can advise your on-site commander on what's possible and how fast.
Task orders are the primary execution mechanism. The base contract (LOGCAP, AFCAP, etc.) is already awarded and competed. When a new need comes up, a task order gets issued against that existing contract for the specific work. This is significantly faster than standing up a new contract from scratch because the competition already happened at the base contract level.
Undefinitized Contract Actions (UCAs) come into play when urgency demands that work start before all the terms are negotiated. The contractor begins performance under a letter contract or not-to-exceed ceiling, and the final terms get definitized later. This is a tool for when the mission can't wait for the full negotiation cycle, but it carries risk because you're committing to work before the price is fully agreed upon. Your commander should understand that UCAs are an option, but they come with oversight requirements and definitization deadlines.
The key thing for you to understand: when your commander asks "can we get this done?" the answer might not be "let me write a new contract." It might be "there's already a vehicle for this, let me coordinate a task order with the program office." Knowing which vehicle covers what, and how they execute, saves time, saves money, and gets the mission what it needs faster. That's you adding value as the contracting expert on the ground.
Up to this point, we've been talking mostly about what happens at your level: your office, your base, your contracts. But in a real-world deployment, you're almost never the only contracting shop in theater. The Army has their people. The Navy has theirs. The Marines have theirs. And you're all operating in the same area, buying from the same local vendors, sometimes contracting for the exact same services without knowing it.
That's the problem this phase is about. When multiple services are doing contracting in the same operating area, somebody has to coordinate. Otherwise you get duplicate contracts, services competing against each other for the same vendors (which drives up prices), and nobody with a clear picture of what's actually being spent. This happened repeatedly in Iraq and Afghanistan. One general officer described discovering units were contracting two and three times for the same services because nobody was talking to each other.
So how does the joint force solve this? Two ways. First, there's a staff cell called the OCSIC (Operational Contract Support Integration Cell) that integrates and coordinates contracted support across the operation. Second, there are theater contracting constructs that determine how the actual contracting work gets organized between the services. Let's break both of these down.
The OCSIC is the hub where all the OCS coordination happens. Remember the J-staff wheel from Phase 2? The OCSIC is where those staff functions come together specifically for contracted support. It's made up of logistics planners and contracting subject matter experts, and it exists to make sure everyone is on the same page about what's being contracted, by whom, and for how much.
There are three levels of OCSIC, and each one has a different focus:
Where: At the combatant command level (CENTCOM, EUCOM, INDOPACOM, etc.)
Who staffs it: Usually a small dedicated team, anywhere from 1 to 7 people. Sits under the J-4 (logistics directorate). Can be military, civilian, or contractor.
What it does: Steady-state planning across the entire area of responsibility (AOR). Analyzes the OCS aspects of the operational environment, develops AOR-wide contractor and contracting guidance, determines whether the theater needs an LSCC or LSC designation (more on those in a minute), and passes OCS estimates down to JTF-level OCSICs.
Think of it as: The long-range planners. They're setting the conditions before a crisis happens.
Where: At the Joint Task Force headquarters, inside the operational area.
Who staffs it: Ad hoc, pulled from whatever units are assigned to the JTF. Typically built around the Service headquarters that forms the core of the JTF (for example, an Army corps or a numbered Air Force). Often augmented by TRANSCOM's Joint Enabling Capabilities Command (JECC).
What it does: Execution-focused. Manages requirements, approves contracting priorities, runs the Joint Requirements Review Board (JRRB), coordinates with subordinate unit OCSICs, and oversees contract execution across the joint operating area (JOA). This is the one that runs the battle rhythm events you'll attend.
Think of it as: The execution hub. When you hear "the OCSIC meeting," this is usually the one people mean.
Where: At each Service component command (ARCENT, AFCENT, NAVCENT, MARCENT, etc.)
Who staffs it: Full-time or collateral-duty staff within the Service component's G-4/A-4/N-4. Each service does this a little differently. Army uses their G-4 and Theater Sustainment Command (TSC). Air Force uses the A-4/A-7 and an AFICC Operating Location (OL). Navy uses the N-4 and Fleet Logistics Centers (FLC). Marines use the G-4 and Marine Expeditionary Force (MEF) staff.
What it does: Service-specific, steady-state actions. Supports CCMD OCSIC planning, coordinates with units to identify contract support requirements, and recommends where the "best source of support" is for their forces (organic, multinational, host nation, or commercial).
Think of it as: Your service's home office for OCS. This is who connects you back to your service's contracting enterprise.
Here's the important part for you as a CCO: the OCSIC is not a contracting office. It doesn't award contracts. It doesn't hold warrants. Its job is to integrate contracted support into the operation and make sure the right hand knows what the left hand is doing. When you sit at the OCSIC table, you're the contracting subject matter expert. You bring the data on what's being contracted, flag duplication, and advise on what's feasible. That voice matters more than you think.
In one major operation, the OCSIC discovered that multiple units had submitted nearly identical requirements for generator maintenance. Each had contracted separately with different vendors at different price points. Nobody did anything wrong individually, but without someone looking across all the contracts, nobody saw the overlap. That's exactly the kind of problem the OCSIC exists to catch. And it's the kind of problem a sharp CCO brings to the table with the data and a recommended fix, not just a complaint.
The OCSIC handles the coordination and integration side. But there's a separate question: when multiple services are contracting in the same area, how do you actually organize who buys what? That's where theater contracting constructs come in.
There are four options, arranged from simplest to most complex. The combatant command (CCMD) picks which one to use based on the size and complexity of the operation. Think of it as a ladder, and the CCMD only climbs as high as the situation demands.
What it means: Each service does its own contracting for its own forces. No formal coordination structure between services. Army buys for Army. Air Force buys for Air Force. Navy buys for Navy.
When it's used: Single-service operations, small exercises, theater security cooperation events, humanitarian assistance projects, non-combatant evacuation operations (NEOs). Basically, any time the operation is small enough that there's no real overlap.
The upside: Simple. No extra staff, no extra coordination. Each service uses its own contracting processes and nothing changes.
The downside: No information sharing between services. If Army and Air Force are both buying fuel from the same local vendor, nobody knows. That can lead to duplicate contracts, competing bids driving up prices, and misalignment with the commander's priorities.
Bottom line: This is the default. It's where every theater starts unless the CCMD says otherwise.
What it means: The combatant command tasks one service to coordinate contracting activities across all the services in the area. The designated service's senior contracting official (SCO) chairs the Joint Contracting Support Board (JCSB), a regular meeting where all the contracting shops sit down together to share information and de-conflict.
The key word is "coordination." The LSCC has coordinating authority, not command authority. That means the LSCC SCO can require consultation through the JCSB, but cannot compel other services to use a specific contractor or change their contracting approach. Everyone still buys their own stuff. The LSCC just makes sure they're not stepping on each other.
When it's used: Steady-state operations or contingencies where two or more services are contracting in the same AOR or JOA. This is actually the most common construct globally. LSCCs are in place at most combatant commands right now, in steady state, before anything kicks off.
How it gets established: The CCMD tasks a Service component command through a plan or order. That service's HQ then delegates tasking to their theater contracting activity. For example, at INDOPACOM, PACAF (the Air Force component) is the LSCC, and AFICC-KH (the Air Force contracting office at Hickam) does the actual coordination work.
Real-world examples: INDOPACOM (Air Force), AFRICOM (Army, with the 414th CSB). Multiple designations can exist within one CCMD, split by country or region. In CENTCOM, there are Army, Air Force, and Navy LSCC designations split by country.
Bottom line: The LSCC is a unity of effort arrangement. It creates a forum for information sharing and de-confliction, but it doesn't change who buys what. Each service still contracts for their own forces.
What it means: Same as the LSCC, plus one service is now responsible for actually contracting for specific common supplies and services on behalf of all the services in the area. Think of it as LSCC-plus: you still coordinate everything, but for certain designated items, one shop does the buying for everybody.
What gets designated for common contracting: Things that every service needs and that make no sense to contract separately. Food preparation services, laundry, waste removal, facility maintenance, power generation, local transportation, showers, latrines, billeting and lodging, minor construction, heating/air conditioning, ice production, storage rental, non-tactical vehicles. Basically, base life support.
What does NOT get commonly contracted: Ammunition, weapon systems support, certain medical equipment, private security contractors, major construction, real estate leasing, depot-level maintenance, specialized IT and communications equipment. These stay with the services that need them.
The catch: When the LSC contracts for common items, the other services have to change how they request support for those items. Instead of going through their own contracting shop, requiring activities submit requests through the LSC's process. This also means money has to move between services. If the Army is the LSC and they're contracting for laundry that supports Air Force personnel, the Air Force has to transfer funds to the Army. That's called an Economy Act transaction, and it adds administrative overhead.
When it's used: Joint operations with a single funding source, or when one service has a preponderance of force. Usually geographically oriented (JOA-wide or FOB-specific).
Real-world examples: CJTF-OIR in Iraq/Syria (Army, through the 408th CSB). USFOR-Afghanistan was Army. JTF-HOA in Djibouti (Navy with joint manning augmentation). Cobra Gold exercise (rotates between Marines and Army).
Bottom line: The LSC creates efficiency by consolidating common buys under one shop. It reduces competition for local vendors and eliminates duplicate contracts. But it requires more staff, forces some units to change how they request things, and requires funds transfers between components. It works best when there's centrally managed money or one service is clearly in the lead.
What it means: A full-up joint command with both command and procurement authority over all deployed theater support contracting organizations. This isn't just coordination. The JTSCC actually commands the contracting forces from all services and provides procurement authority to them.
When it's used: Major, complex, long-term joint stability operations with significant theater contract support requirements. This is the heaviest option.
The upside: Gives the Joint Force Commander significant control over requirements prioritization. Consolidates all U.S. military demand for local resources under one organization, which promotes efficient use of contracting personnel and supports better information sharing.
The downside: Requires both command and contracting staffs. Long lead time to stand up. Requires significant changes to how every service does requirements development and contracting procedures. It's the most disruptive option.
Real-world examples: Various configurations were used in CENTCOM from 2010 to 2015. It's generally fallen out of favor because of the complexity and lead time required.
Bottom line: The JTSCC is the "we need to bring everything under one roof" option. It gives maximum control but at maximum cost and complexity. You'll likely never see one stood up, but you should know it exists as a concept.
Here's something that surprises a lot of people the first time they deploy to a joint environment: every service has contracting officers in theater, and they all do things a little differently. Understanding who the other players are will save you time and prevent you from duplicating work somebody else is already doing.
The Army has the largest expeditionary contracting force. Their primary units are Contracting Support Brigades (CSBs) and subordinate contracting battalions (CBns) with deployed detachments (DETs). The CSBs are the ones you'll most often see in the LSCC or LSC role because the Army tends to have the biggest ground presence. Example: the 408th CSB was the LSC for CJTF-OIR.
The Navy operates through Fleet Logistics Centers (FLCs) and Fleet/Expeditionary Contracting (FEC). Ship husbanding, port services, and anything maritime-related is Navy contracting. They also support shore-based operations through NAVSUP contracting activities. In the OCSIC org chart, the Navy component's N-4 owns the OCS function.
Marine contracting flows through the Marine Logistics Group (MLG) and Expeditionary Contracting Platoons (ECPs) within the Marine Expeditionary Force (MEF). Marines deploy with organic contracting capability embedded in their expeditionary units. The G-4 at MARFOR (Marine Forces) component commands handles OCS coordination, with OCS advisors on staff.
This is your world. Air Force contracting in theater runs through AFICC Operating Locations (AFICC/OLs) tied to the numbered air force or air component command. The A-4/A-7 at the AFFOR (Air Forces component command) is where OCS planning lives. OCS advisors (military) support the staff, and the AFICC/OL provides the contracting muscle.
Then there are the organizations that cut across all services. DLA (Defense Logistics Agency) has contracting activities in theater for items in their commodity lanes (fuel, food, medical supplies, construction material). USACE and NAVFAC handle major construction. LOGCAP (Army), AFCAP (Air Force), and the Marine equivalent are theater-wide contract vehicles managed from outside the theater that provide base life support and other services through task orders. And Theater Special Operations Commands (TSOCs) have their own contracting capability with SOCOM-warranted contracting officers under the J-4.
The point is: when you show up to a JCSB or OCSIC meeting, you're sitting across the table from Army contracting officers, Navy contracting officers, Marine contracting officers, DLA reps, and LOGCAP program managers. Each one has their own chain of command, their own contracting authority, and their own way of doing business. The construct (LSCC, LSC, etc.) determines how much they have to coordinate with each other. But regardless of the construct, the JCSB and OCSIC are where that coordination actually happens.
The Joint Contracting Support Board (JCSB) is the working-level meeting chaired by the LSCC or LSC contracting director. This is where all the theater contracting activities sit down and coordinate. The JCSB de-conflicts contracting actions (so two shops don't bid on the same local vendor for the same service), reduces duplication of effort, coordinates market research data sharing, and ensures the commander's priorities are reflected in how contracting resources are allocated. If the LSCC is the construct, the JCSB is the mechanism.
Now you know the players and the structures. Let's see if you can apply it.
Not dangerous in a bad way. Dangerous in the way that matters: you now know enough to ask the right questions when you show up to a deployment. You know who owns what, where CONS fits, when to lead and when to support, and what the big contracts look like.
The full JOPEC course goes deep on joint planning, Annex W development, theater-level OCS integration, and the strategic contracts that keep entire theaters running. What you've seen here is the foundation. Everything else builds on it.
Three questions. Every time.
Who has the authority? Who owns the requirement? Where are the resources?