1 / 26

BAPLIE

Audrey
Download Presentation

BAPLIE

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

    1. October 2007 SMDG meeting # 50 1 BAPLIE HISTORY AND CURRENT STATUS By Gerry Endenburg SMDG Secretary General BAPLIE Coordinator

    2. October 2007 SMDG meeting # 50 2 BAPLIE HISTORY Mid 80’s: Shipping Lines installed their own proprietary systems in the Terminal’s offices Ship planners had to work on each of these systems Bay-plans were exchanged in private flat file formats via dialup networks, like GEIS and IBM Internet was NOT AVAILABLE in those days! (imagine a world without Internet!!)

    3. October 2007 SMDG meeting # 50 3 BAPLIE HISTORY Some terminals had up to 7 different PC’s in the planning office, one from each shipping line. Planners had to learn to work with each one of these totally different systems These systems all had different protocols and dialup procedures for transmission and receipt of bay-plan data.

    4. October 2007 SMDG meeting # 50 4 BAPLIE HISTORY 1987 Computerized ship planning systems for Terminals came into the arena Ship planners entered bayplan data into those systems manually The need to exchange bayplan data electronically became urgent

    5. October 2007 SMDG meeting # 50 5 BAPLIE HISTORY That was not what the terminals wanted! Terminals developed and installed their own systems and ship planners learned to work with these systems Bay-plans had to be transmitted to the central planner and/or terminal in the next port in a standard format Such bay-plans could then be loaded automatically into the systems of the line and terminal, without manual re-typing

    6. October 2007 SMDG meeting # 50 6 BAPLIE HISTORY In the first SMDG meeting in 1987 it was agreed: The need and value of developing data standards along internationally agreed guidelines. The value of drawing contribution from a wide base of interested parties. The intention of placing any developed standards firmly in the public domain. That was easier said then done! How to get everybody’s attention? How to create such a standard format?

    7. October 2007 SMDG meeting # 50 7 BAPLIE HISTORY First: Which syntax to use? ANSI X12 or Edifact? In those days the UN promoted the use of Edifact (Electronic Data Interchange for Administration, Commerce and Trade) During the first SMDG meeting, in October 1987 it was decided to use Edifact

    8. October 2007 SMDG meeting # 50 8 BAPLIE HISTORY Second: Which data elements must be transmitted? How shall we code the cell positions? Which codes to use for vessels, ports, etc.? How to format these data elements into the message?

    9. October 2007 SMDG meeting # 50 9 BAPLIE HISTORY Initially we decided to go for two different BAPLIE messages, which were both filed with and accepted by the UN/Edifact Board: BAPLIE = Bayplan Including Empty Space BAPLEE = Bayplan Excluding Empty Space BAPLEE was soon abandoned and BAPLIE can be used with or without empty spaces (As far as we know nobody ever transmitted the empty spaces) In 1988 the first draft version of BAPLIE was developed by Simon Spoormaker (ECT) and Pierre Mijnsbergen (Nedlloyd).

    10. October 2007 SMDG meeting # 50 10 BAPLIE HISTORY In 1991 we filed the first BAPLIE structure with the UN/Edifact Board This structure was based on the 91.1 Edifact Directory

    11. October 2007 SMDG meeting # 50 11 BAPLIE HISTORY Notice that this was all armchair science! We could not test anything. Nobody wanted to develop anything until we finished all documentation and agreed about the complete message implementation Thanks to the close cooperation between the various terminals and shipping lines we arrived at the agreed structure of the message

    12. October 2007 SMDG meeting # 50 12 BAPLIE HISTORY However, we then were only halfway down the road! Having an agreed structure, fully accepted by the UN/Edifact Board, is not enough to implement the message The message structure only gives you the walls and purpose of the various rooms in the house, not its contents! We soon realised that a fully detailed implementation guideline had to be created and agreed between parties

    13. October 2007 SMDG meeting # 50 13 BAPLIE HISTORY Consequently we created an Implementation guideline or User Manual, as we called it then.

    14. October 2007 SMDG meeting # 50 14 BAPLIE HISTORY Note that there were no instructions from the Edifact Board about such User Manuals. There were no examples available to us The structure and conventions of this BAPLIE User Manual were designed and developed by SMDG members The structure and naming conventions developed by SMDG for BAPLIE have been a paradigm to all EDI groups worldwide!

    15. October 2007 SMDG meeting # 50 15 BAPLIE HISTORY Our User Manuals or Implementation Guidelines give clear instructions with examples about what data to enter where and which code tables to use.

    16. October 2007 SMDG meeting # 50 16 BAPLIE HISTORY The BAPLIE User Manual was printed and bound in booklets Distribution of same by post! After receipt members studied the manual and sent their comments to SMDG Secretariat by post or fax for further processing During the meetings such comments were discussed and changes in the User Manual were agreed

    17. October 2007 SMDG meeting # 50 17 BAPLIE HISTORY Then the new version of the BAPLIE User Manual was created, printed and distributed again by post. And so on!

    18. October 2007 SMDG meeting # 50 18 BAPLIE HISTORY BAPLIE versions 1.1 till 1.5 were based on Edifact directory 91.1 BAPLIE 2.0 was based on directory 92.1 and its Implementation Guide was released in March 1994. BAPLIE 2.0 was developed by the socalled ‘Joint BAPLIE 2.0 Development Team (JBDT) JBDT was a cooperation between SMDG, ISA/TOPAS (USA) and AS TWG (Asia Edifact Board Transport Working Group)

    19. October 2007 SMDG meeting # 50 19 BAPLIE HISTORY BAPLIE 2.0 remained stable for several years Small changes were applied until release 2.0.7 of September 1995 BAPLIE 2.1 was released in February 2001 and is based on Edifact Directory D95B In the meantime, of course, SMDG undertook several other projects, including the development of the stowage instructions message MOVINS and the socalled ‘Container Messages’, COARRI, CODECO, etcetera.

    20. October 2007 SMDG meeting # 50 20 BAPLIE TODAY Today ship planners, terminals, shipping lines cannot imagine life without BAPLIE BAPLIE messages are being sent and received by many parties all over the world We estimate the number of BAPLIE messages transmitted at around 50.000 per day! BAPLIE is being mentioned by the UN/Edifact Board as the example of a very successful implementation of Edifact

    21. October 2007 SMDG meeting # 50 21 BAPLIE TODAY BAPLIE has saved the Shipping Industry a fortune! BAPLIE has made life not only easier for the ship planners but made planning a lot more efficient. Terminals and Shipping Lines can simply continue to develop their own ship planning systems without interfering with their external communications, as long as you can support BAPLIE (and MOVINS) you’re OK! The Internet provided us with an efficient and reliable e-mail system, making sending and receiving of BAPLIE’s a simple and often automatic background process.

    22. October 2007 SMDG meeting # 50 22 BAPLIE TODAY Today all BAPLIE versions, 1.5, 2.0 and 2.1, are still being used. Most parties can work with all versions and can even convert one version to another, for example receive version 2.0 and transmit 1.5!

    23. October 2007 SMDG meeting # 50 23 BAPLIE TODAY BAPLIE 3.0 is now on the drawing board This new trial version is based on Edifact directory D00B and has not been implemented yet. This version will accommodate new requirements, like vessels with more than 10,000 containers, but also additional details about Dangerous Goods, Electronic Seals, etc.etc. Expected availability of a stable version: “to be decided by SMDG members”.

    24. October 2007 SMDG meeting # 50 24 BAPLIE FUTURE BAPLIE will stay ‘forever’ BAPLIE will evolve over time with new features and functionality Will we develop an ebXML version of BAPLIE? Perhaps we will. This is not a technical issue! Implementation of same will be decided by the users organized by SMDG! The same old question will always be asked: “Why must we invest in new technology?”

    25. October 2007 SMDG meeting # 50 25 BAPLIE NOW! In 1987 SMDG started with the following targets: Drawing contribution from a wide base of interested parties. The intention of placing any developed standards firmly in the public domain. I believe we can now say that we have achieved both objectives and we shall continue to serve the shipping industry to the best of our abilities, as long as you wish and are willing to support us!

    26. October 2007 SMDG meeting # 50 26 BAPLIE forever! I want to thank everybody who has worked with us for 15 years or more on the development of this important message! I am proud to be the BAPLIE coordinator and hope I can continue with this work for many years to come! Gerry Endenburg

More Related