OCS for Dummies: The Stuff Part 1 Skipped

New CCOs hear "we need a contract" and jump straight to market research or an existing vehicle. Slow down one notch. The support problem comes first. Determine what the commander actually needs covered, decide how the pieces combine and prioritize, then put a buying path on it.

Part 1 covered the organizations. Part 2 is the rhythm: classify the buy, build a requirement that survives the board, get it into the planning products, and keep the contractor footprint manageable.

BOS is the bundle of contracted base support that lets the force live, work, and keep operating. Depending on the theater and the plan, that bundle includes billeting, showers, latrines, laundry, dining facility support, waste removal, vector control, facility maintenance, generators, water, sometimes transport, and sometimes common equipment maintenance. No single award buys all of it; the staff buys pieces and hopes the seams hold.

That is why BOS matters in OCS. Everyone thinks their piece is separate until the base ends up with three laundry contracts, two generator maintenance paths, one trash contract nobody monitors, and contractors at the gate with no clear life-support authorization.

Picture yourself at a normal deployed base. Al Udeid, for example. Requirements flow from end users through their own established processes. SFS submits a package for security gear, FSS submits one for dining facility augmentation, CE for facility work, and so on. The CCO sees a steady stream of validated unit-level requirements coming through that flow.

Then something pops off. A JTF stands up, and Al Udeid is tasked to provide support to it. The JTF doesn't ride your base's requirement process. It runs its own. That process is the JRRB.

Here's what the JRRB actually is. A panel. Senior leaders, functional experts, legal, finance, sourcing advisors. They sit down and review a requirements package before it ever lands at CONS. They make sure the requirement is real, that other sources of support (organic, host-nation, existing CAP, DLA, TRANSCOM) have been considered, that operational priority is real, and that funding and legal posture line up. The commander's intent, the threshold rules, and the special-interest items are all baked into how they vote.

In my experience, once you get a JRRB package on your desk, it is time to execute. Not question. The amount of lift it took to move that requirement through the JRRB is, frankly, somewhat insane. The package has already been reviewed by senior leaders, by the requirement owner's functional staff, by legal, by finance, and by sourcing experts. It will be cleaner than a normal acquisition package nine times out of ten, and if it is not clean, the people who pushed it through clearly thought it was important enough to push anyway.

The exception is the one most CCOs already understand intuitively: if you see something insanely illegal, a clause that violates statute, a structure that bakes in a conflict of interest, an award that would steer to an unqualified source, you raise that. That's the contracting officer's job, and a JRRB approval does not displace the warrant. Outside of that, execute. The board did the validation work for you.

The two-board structure traces back to CJCSM 4301.01.

Annex W is where the operation plan explains how contracted support will be used, controlled, synchronized, and managed. The structure and required appendices live in CJCSM 4301.01. You may not write the whole annex as a deployed CCO, but your work feeds it. If the plan says BOS will support FOB East in Phase II, somebody has to translate that into requirements, contracting capacity, CORs, contractor movement, and accountability.

Three Annex W products show up on the CCO desk: the OCS concept of support, the CSSM (CJCSM 4301.01, Annex W, Appendix 1), and the CSOR (Appendix 3). Treat them as the commander's intent, the timeline, and the shopping list with operational context. The CMP (Appendix 2) sits next to them and governs how the contractor footprint will actually be run.

Contractor management is the oversight and integration of contractor personnel and their equipment in support of the operation. That covers accountability, theater entry, movement, access, authorized government support, force protection, medical considerations, redeployment, and who in the staff owns each piece. JP 4-10 carries it as one of the three OCS subordinate functions, alongside contract support integration and contracting support.

For DoD operations, the SPOT Enterprise Suite is the contractor accountability system called out by official DoD OCS resources, and DoDI 3020.41 sets the broader contractor personnel policy for OCS outside the United States. A LOA tells contractor personnel what government support they are authorized to receive under the contract: badges, billeting, meals, medical, transport, mail, MWR, weapons, and PPE. If the contract brings people into the operational area, the command needs to know who they are, where they are, what they do, and what support they are allowed to use.

Most painful OCS failures are clean awards that no one can explain three weeks later, when the COR rotates, the funding line changes, or the gate guard wants to know why a busload of contractors is showing up at 0500. Use this card when you inherit a deployed file, brief the OCSIC, or hand support to the next rotation.

OCS isn't a paperwork problem. It's an operations problem that you happen to solve with contracts. Part 1 gave you the room, the players, and what each shop is actually responsible for. Part 2 gave you the work that moves across the room: requirements that arrive validated, support paths that don't duplicate each other, contractor footprints that don't surprise the gate guard, and a handoff your replacement can actually use.

A few things to take with you:

• Validate the requirement before you source it. The JRRB exists so contracting doesn't carry the validation job alone. Use it.
• Look across before you award. Existing theater vehicles, CAPs, DLA/TRANSCOM, host-nation, ACSAs, and another unit's active contract all live in the JOA. Check before you write a new one.
• Count contractors like you count dollars. Every body in the SPOT roster is a body the command has to feed, house, badge, move, and protect. The CSOR is where the staff sees that bill in advance.
• Leave a usable file. The COR plan, the LOAs, the support assumptions, and the next-action note matter more on day 91 of a deployment than the contract clauses do.
• Stay in your lane on policy stops. Armed contractors, private security, host-nation legal limits, SOFA reach, and medical care all sit outside contracting. The OCSIC and SJA own those calls. Bring them in early.

When a JRRB package lands on your desk, execute. When a CAP vehicle covers the gap, ride it. When the COR plan looks weak, fix it before performance starts. When the next rotation hits the ground, hand them more than a folder full of signed PDFs. Hand them a file that tells the story of what the unit is actually getting in return for every dollar and every contractor it has on the books.

That's the job. The acronyms are just the shorthand.