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 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.
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
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
From the guide to go-live
Put this into practice with ECOM
Reading about EDI is the first step. When you are ready to meet a trading partner's requirements, an ECOM specialist can help.
-
EDI compliance help
Check documents against the partner's rules before they are sent, and find out why labels, ship notices or invoices are rejected or short-paid for EDI 650.
-
EDI implementation
Map, test and certify the documents for EDI 650, and connect them to your ERP, warehouse or order system.
-
Managed EDI
Have ECOM run the day-to-day EDI: monitoring, error handling and new trading partner setup.
Need help with the EDI 650?
ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.