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 · Communications

EDI 650 Maintenance Service Order

The X12 document used to exchange maintenance information, from directives and estimates to assignments, status and completion reports.

Sent by
Equipment owner, maintenance planner or service provider
Received by
Service provider, maintenance organization or owner
Standard
ANSI ASC X12

What is an EDI 650?

The EDI 650 Maintenance Service Order is the ANSI X12 transaction set that provides a uniform medium for exchanging maintenance information among organizations involved in reporting, requesting, scheduling, planning, estimating, coordinating and performing maintenance actions. It covers maintenance directives, actions, cost estimates, assignments, status and completion reports.

Organizations that maintain fleets or complex equipment, often with outside maintenance providers, need to share what work is required, what it will cost and when it is done. One transaction set for the whole cycle keeps both sides' records aligned.

How the EDI 650 worksDiagram of the EDI 650 Maintenance Service Order. Equipment owner, maintenance planner or service provider sends it to service provider, maintenance organization or owner. It usually starts the exchange. It is usually followed by 810 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment) and detail: the required HL loop with HL (Hierarchical Level). 6 optional loops are listed by their first segment.How the EDI 650 worksMaintenance Service Order: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 650SENDEREquipment owner,maintenance planneror service providerRECEIVERService provider,maintenanceorganization or owner997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY810Invoice997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code MOGS … GETransaction set 650ST … SEHEADINGBGNBeginning Segment+ 2 optional loops, starting with:N1LMDETAILRequired loop HL · repeats many timesHLHierarchical Level+ 4 optional loops, starting with:CLILMNM1MTXBlue 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 650. Your trading partner's implementation guide adds its own requirements.
How the EDI 650 worksDiagram of the EDI 650 Maintenance Service Order. Equipment owner, maintenance planner or service provider sends it to service provider, maintenance organization or owner. It usually starts the exchange. It is usually followed by 810 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment) and detail: the required HL loop with HL (Hierarchical Level). 6 optional loops are listed by their first segment.How the EDI 650 worksMaintenance Service Order: who sends it, whereit fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 650SENDEREquipmentowner,maintenanceplanner orservice providerRECEIVERServiceprovider,maintenanceorganization orowner997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY810Invoice997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code MO (GS … GE)Transaction set 650 (ST … SE)HEADINGBGNBeginning Segment+ 2 optional loops, starting with:N1LMDETAILRequired loop HL · repeats manytimesHLHierarchical Level+ 4 optional loops, starting with:CLILMNM1MTXBlue 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 650. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 650, 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 650 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

  • Requesting maintenance work from a provider
  • Exchanging cost estimates for maintenance
  • Reporting maintenance status and completion

Where it fits in the document flow

This document 650 Maintenance Service Order
Usually followed by 810 Invoice997 Functional Acknowledgment

Structure

Mandatory segments in the 650 (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
  • BGN
  • N1
  • LM
  • LQ
  • HL
  • CLI
  • NM1
  • MTX
  • SE

Practical example

The 650 in practice

A transit agency outsources overhauls of its buses. It sends the maintenance provider a 650 directive for a bus with the work required. The provider returns an estimate, the agency approves it, and the provider reports status during the overhaul and completion when the bus is returned.

Implementation

Implementation considerations for the 650

  • Use equipment identifiers both parties track.
  • Approve cost estimates before work starts.
  • Report maintenance status changes as they occur.
  • Link completion reports to the invoices that follow.

How ECOM helps

Automate the 650 with ECOM

Industry

Industrial Manufacturing

Distributor, OEM customer and supplier integration for industrial manufacturers.

Solution

B2B Integration

Connect every customer, supplier, carrier and bank across EDI, API, file and portal channels.

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 communications documents

All 16 communications documents

Need help with the EDI 650?

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

Request a Demo Contact us