Program methodology
Justransform provides best practices for integration program management using a proven methodology that optimizes the use of people, process, and technology.
EDI integration programs take many shapes, but a robust B2B program management lifecycle can increase onboarding velocity and time to value. Justransform Services focuses on two tracks, each with multiple phases, that can run in parallel instead of a traditional serialized waterfall.
- Track 1 — Onboard scope definition and enterprise integration. During these phases, onboarding planning for the trading network is defined, capabilities are assessed, and backend integration for the business process is implemented.
- Track 2 — Onboarding execution: plan, build, and deploy. Onboarding planning is baselined; execution assets are developed, tested, and delivered.
Onboarding scope definition
Goal: Set enterprise business and technical readiness for process integration onboarding and assess gaps. What capabilities must be delivered for optimal results?
- Assess the trading ecosystem: which electronic processes can participants support, and what are their preferred trading mechanisms?
- Gather trading network business and technical capabilities via partner outreach and capability assessment; develop an initial plan (to be locked during the onboarding plan phase).
Trading partner readiness
- When can they get started?
- Are there resource constraints?
- What is required to commit resources to the onboarding effort?
- Are commercial contracts complete or validated before onboarding commitment?
If gaps exist, develop a mitigation plan (for example raw data integration, mobile integration, or web portal integration — additional fees may apply). Develop a high-level ramp plan for onboarding.
Enterprise integration solution build
Purpose: Create the interconnect between the enterprise application (SaaS or on-premise) and complete systems integration testing (SIT) for process-level execution that meets business and technical requirements.
- Justransform develops map specifications using enterprise application interfaces (e.g. web services, database, message queuing).
- After map specifications are complete, complete message mappings for each required message and unit test each mapping.
- After unit tests, perform end-to-end SIT scenarios (for example TMS: tender offer and EDI output, tender response injection, accept/decline flows, shipment status, freight invoice).
- Update message implementation guides as needed (status milestones, freight codes, etc.) across nodes.
Onboarding planning phase
Goal: Confirm onboarding scope and baseline the plan (e.g. network profile: count of EDI partners, API partners, and other channels).
- Confirm solution interlock with trading partner(s).
- Notify all parties for onboarding kickoff: expectations and milestones.
- Obtain API guidelines for API-based integrations.
- Submit or receive EDI guidelines with sample transactions (may depend on enterprise build completion).
- Obtain connectivity details and begin setup.
- Tenant defines core UAT scenarios for sign-off.
- Enterprise application integration is a prerequisite before this gate.
Onboarding development phase
Complete EDI, API, raw data, and WebEDI connectivity provisioning.
- Trading partner EDI mapping to tenant requirements.
- Where applicable, development between enterprise application and partner API endpoints.
- Where applicable, raw data mapping and/or WebEDI provisioning.
- UAT: Formal tests with the partner before production approval; defects addressed in this phase.
- Update EDI guides and maps if needed.
- Tenant, Justransform, and partner(s) begin change management for go-live; set production release date.
Deploy phase
Trading partner(s) are promoted to production.
- Tenant is introduced to Justransform global support; process and technical contacts enabled.
- Training overview of the network console for monitoring and troubleshooting.
- After production promotion: hyper care phase.