EDI contingency planning process guides
An organization must plan for any disaster that would adversely affect the organization’s EDI systems. Hardware, software, and information (data) must be considered in the contingency planning process.
Hardware Contingency Planning
Management should take steps to ensure that any hardware failure will not adversely affect the organization’s EDI processing, for any extended period. Backup hardware (commonly called “hot sites”), and/or replacement components necessary to assure continued EDI processing, must be maintained and be available continuously.
Software Contingency Planning
Software used for EDI is subject to damage or corruption due to power failures, faulty hardware, and internal misuse. Management should initiate steps to make sure that the software is consistently “backed up” to avoid EDI downtime. This “back up” procedure should also assure that any new versions installed do not deter normal EDI processing while the new version of software is being tested.
Information (Data) Contingency Planning
Finally, and most importantly, the EDI information (data) electronically transmitted to the organization from their trading partner becomes invaluable. Many paper documents are taken out of the information exchange cycle between companies when EDI is implemented. Not only does this “data” become the lifeline of the organization, but many times it becomes the audit trail to be used in the organization’s standard accounting practices. Once implemented, EDI transmitted information (data) becomes the link between EDI trading partners, and management should take care to maintain the integrity of this information.
To learn more about EDI and become a CEDIAP® (Certified EDI Academy Professional), please visit our course schedule page.