2.2. B2B Integration Project Management

When you set up a channel to tranfer data between your system and the external system of your B2B partner, you must agree on a way to transfer these data. This activity is a project, possibly involving multiple parties: your company, your B2B partner, your and their IT integrator, etc.

So, before starting any implementation, even in a test configuration, Babelway recommends to follow a project management process such as this one:

Agree on project terms
You and your B2B partner should agree on the purpose of collaboration and data to be transferred. This part should also include the possible financial terms. Some exchanges may even require the writing of contracts.
Write specifications
Together with your B2B partner, you should write technical specifications about what is going to be transferred and how (gateway types and configuration, messages formats required, mandatory information included in messages, validation processes, test cases definition for project acceptance...)
Plan and execute work
Configure and test your channels to meet agreed specifications. The planning should include when your partner must have ressource available, for example, for testing and for acceptance phases.
Production and acceptance tests
Once the development and tests are completed, the system is used in production for a trial period. If adjustements are required, they should be implemented as soon as possible. Once all issues are solved and the trial period is finished, the system can be fully used in production.

Here is a short checklist of items that will be required during development and that sould be agreed between both sides and included in the specifications:

at account level:

Details of users who will have access and their respective roles.
Details of settings including volumes of transactions, price package, expected concurrent volume...

For each channel:

Details of gateways in and out including external systems details, usernames, passwords, certificates... Details of test environments of external partners prior to moving to production if relevant.
Details of messages in and out formats. Both sides should provide several examples of each in and out message types.
Details of message transformation rules, possible values mapping, exception, mandatory and optional fields...
Details of routing rules if relevant.
Details of in and out message validation rules if any.
Details of messages, channels and any other items naming conventions.
Details of users notifications (success and/or errors).
Detailed test plan including acceptance criteria.

Prev	Up	Next
2.1. Babelway Concept	User Guide	Chapter 3. Starting with Babelway