Start by confirming the trading partners, required documents, communication method and system ownership. For Itron, the first build should focus on stable required documents before adding optional workflows.

Testing should include valid files, rejected files, acknowledgments, duplicate documents, missing required fields and system posting. The goal is to prove that partner files move correctly through Itron.

Common failures include missing required fields, wrong partner identifiers, document version mismatches, invalid codes, failed acknowledgments and system posting errors. These should be tested before production.

Technical delivery alone is not enough. Business validation confirms that quantities, prices, dates, items, addresses, references and statuses make sense inside the actual workflow.

Partner-specific fields should be mapped, validated and documented separately. They may not be required by the EDI standard but can still be required by the partner.

Yes. Itron can connect EDI with APIs, flat files, SFTP, AS2, VAN or other middleware patterns depending on the system and partner requirements.

General business teams should check the documents, partner rules, field validation and system posting points that affect their workflow. For Itron, this usually means aligning 810 and 820 with operational ownership.

Scope should be based on the selected trading partners, their required documents, testing rules and system posting needs. Portland General Electric, Amerigas, Ameren, Con Edison, PGE, Consumer Energy, National Grid, Conedison, Atlantic Power, Agl Resources, American Electric Power and Alabama Power should be treated as related examples, not a one-size-fits-all rule.