On USACE contracts, and NAVFAC jobs whose spec calls for the same deliverables, the schedule spec typically requires four things: a cost-loaded CPM baseline in Primavera P6 built to the section's coding, logic, calendar and settings, monthly updates with narratives, time impact analysis for changes and delays, and a Standard Data Exchange Format (SDEF) export that imports into RMS (Contractor Mode on your side, the government side for review). The last one is where compliant-looking schedules quietly fail, and it hits your money most directly.
Which spec is on your contract
Federal schedule requirements live in Division 01, and the section number tells you which rulebook you are under:
- UFGS 01 32 01.00 10, Project Schedule. The standard USACE section for projects of any real complexity. Versions of it also show up on NAVFAC, AFCEC, NASA, and VA work.
- UFGS 01 32 16.00 20. The lighter section used on smaller, simpler projects.
- UFGS 01 32 17.00 20. The NAVFAC network schedule section.
- VA 01 32 16.xx, Network Analysis Schedule. The VA sections. The major-project section adds the independent CPM consultant requirement on top of the technical rules.
Behind the sections sit ER 1-1-11 and FAR 52.236-15, which is why the schedule requirements read like contract terms. They are contract terms.
What the baseline has to be
The spec doesn't ask for a schedule. It asks for a specific one: activity coding structures, maximum durations, calendar rules, limits on constraints, lags and open ends, and the settings the network runs under. It requires the baseline within a set number of calendar days of NTP and makes its acceptance a condition of progress payments.
Two requirements matter most, because they connect to the payment system:
- CLIN cost loading. Cost-loaded activities are coded to their Contract Line Item Number, and the costs under each CLIN sum exactly to the CLIN value on the schedule of prices. Not close. Exactly. A network a dollar off doesn't balance, and an unbalanced network doesn't become the payment basis.
- The earnings link. Once the cost-loaded baseline is accepted, monthly progress on the schedule generates your earnings. Your pay application comes off the network.
The monthly cycle
Every period you status the network with actual dates and remaining durations, run it, and submit the update with a narrative covering progress, critical path changes and delays. An accepted update supports the period's earnings, and a rejected one can hold them up. When changes or government-caused delays hit, the spec calls for fragnets and a TIA tied to the network, not a letter, to support a request for time.
The SDEF / RMS export trap
The spec states this in one sentence and contractors learn it the hard way: the schedule must be delivered as an SDEF file that imports into RMS without errors.
SDEF is a fixed-format standard older than any P6 version you have used, and rigid in ways a healthy P6 schedule isn't. Activity IDs over the character limit, coding that doesn't map to SDEF fields, cost loading that doesn't resolve to CLINs, and calendars the format can't carry all produce a file that fails the import or loads garbage into RMS.
The trap: P6 will let you build a schedule that passes logic review, reads well in a PDF, and can't produce a clean SDEF. Nothing warns you until the import bounces, and because your pay application runs through RMS, that is a payment problem, not an IT problem. Fixing it usually means restructuring IDs, coding and cost assignments on a live, accepted schedule, which is slow and invites a new review cycle.
The way out is boring: build the network SDEF-ready from day one, with ID lengths, coding, CLIN assignments and calendars chosen so the export runs clean every month.
What this looks like on a real job
As lead scheduler on a pump station and dissolved oxygen system project for USACE at Savannah Harbor, we ran this exact chain. The P6 network was CLIN cost loaded and balanced to the schedule of prices, monthly updates carried earned value and critical path review, and every cycle exported as SDEF and uploaded into RMS clean. The updates drove the pay applications, as the spec intends.
Send it over. We'll tell you which requirements bite, what the baseline must look like, and whether your current schedule can produce a clean SDEF before the import tells you.