972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

X12 transaction guide · Planning

EDI 806 Project Schedule Reporting

The X12 document used to transmit project planning, scheduling and status information, from the initial plan to progress and changes.

Sent by
Contractor
Received by
Government agency or prime contractor
Standard
ANSI ASC X12

What is an EDI 806?

The EDI 806 Project Schedule Reporting is the ANSI X12 transaction set that provides for the transmission of planning, scheduling and status information. Its purpose is to establish an initial plan, report progress against the plan and report changes to it.

On large programs, the customer integrates contractors' schedules into an overall plan and tracks critical milestones. The 806 carries activities, dates, dependencies and progress, complementing the cost data sent with the 839. Updates are usually sent each reporting period.

How the EDI 806 worksDiagram of the EDI 806 Project Schedule Reporting. Contractor sends it to government agency or prime contractor. It usually starts the exchange. It is usually followed by 839 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BPP (Beginning Segment for Project Schedule Reporting). 4 optional loops are listed by their first segment.How the EDI 806 worksProject Schedule Reporting: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 806SENDERContractorRECEIVERGovernment agency orprime contractor997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY839Project Cost Reporting997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code PJGS … GETransaction set 806ST … SEHEADINGBPPBeginning Segment for Project Schedule Reporting+ 1 optional loop, starting with:N1DETAIL+ 3 optional loops, starting with:CALRSCTIDBlue box: required loop. Optional loops are listed by the segment that starts them; when a loop is used, that first segment is required. Optional segmentsoutside loops are not drawn.Structure: required segments and loops in the X12 008010 listing for the 806. Your trading partner's implementation guide adds its own requirements.
How the EDI 806 worksDiagram of the EDI 806 Project Schedule Reporting. Contractor sends it to government agency or prime contractor. It usually starts the exchange. It is usually followed by 839 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BPP (Beginning Segment for Project Schedule Reporting). 4 optional loops are listed by their first segment.How the EDI 806 worksProject Schedule Reporting: who sends it,where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 806SENDERContractorRECEIVERGovernmentagency or primecontractor997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY839Project Cost Reporting997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code PJ (GS … GE)Transaction set 806 (ST … SE)HEADINGBPPBeginning Segment forProject Schedule Reporting+ 1 optional loop, starting with:N1DETAIL+ 3 optional loops, starting with:CALRSCTIDBlue box: required loop. Optional loops are listedby the segment that starts them; when a loop isused, that first segment is required. Optionalsegments outside loops are not drawn.Structure: required segments and loops in the X12008010 listing for the 806. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 806, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 806 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.

Expand diagram Download SVG

When it is used

  • Submitting a baseline schedule
  • Reporting progress against the schedule
  • Reporting schedule changes

Where it fits in the document flow

This document 806 Project Schedule Reporting
Usually followed by 839 Project Cost Reporting997 Functional Acknowledgment

Structure

Mandatory segments in the 806 (X12 release 008010)

The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

  • ST
  • BPP
  • N1
  • CAL
  • RSC
  • TID
  • MTX
  • MLS
  • SE

Practical example

The 806 in practice

A shipbuilder reports its construction schedule to the navy program office. It sends an initial 806 with all activities and milestones, then monthly updates with actual dates, percent complete and revised forecasts. The program office identifies milestones at risk and discusses them at reviews.

Implementation

Implementation considerations for the 806

  • Keep activity identifiers stable between updates.
  • Report activity dependencies as well as dates.
  • Align schedule and cost reporting structures.
  • Explain significant changes to the plan.

How ECOM helps

Automate the 806 with ECOM

Industry

Industrial Manufacturing

Distributor, OEM customer and supplier integration for industrial manufacturers.

Solution

Supply Chain Visibility

Track orders, shipments and invoices across partners and catch exceptions early.

Solution

Enterprise Integration

Any-to-any integration across partners, systems, protocols, security requirements, formats and ERPs, in batch or real time.

More general questions about EDI are answered in the EDI FAQ.

Related transactions

Related planning documents

All 7 planning documents

Need help with the EDI 806?

ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.

Request a Demo Contact us