1 / 36

Post & Co (P&I) BV

Post & Co (P&I) BV. ABS implementation Jan Piet Slot. Who are we. Rotterdam based Specialist in Marine Liability Clients worldwide About 40 specialized employees Developing own applications since 1980’s Started with LINC10, user ever since. Agenda. Where were we before ABS

erelah
Download Presentation

Post & Co (P&I) BV

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. Post & Co (P&I) BV ABS implementation Jan Piet Slot

  2. Who are we • Rotterdam based • Specialist in Marine Liability • Clients worldwide • About 40 specialized employees • Developing own applications since 1980’s • Started with LINC10, user ever since

  3. Agenda • Where were we before ABS • Why migrating to ABS • What was needed before implementing ABS • The safe passage promise • ABS is running, what next? • Show some of the changes

  4. Where were we before ABS • EAE 3R3, deployed to MCP on LX6100 • Using terminal emulator, no graphics • 350+ ispecs, abt 400 reports • 8000+ FPA’s, 700,000+ EAE source lines

  5. Why migrating to ABS • Demands to modernize screens • Integration with other applications • New contract period, with new machine • End-of-life for EAE to be expected • Being early adaptor brought extra support

  6. What we needed to do before implementing ABS • Entered early adaptor program • Provided sources to ACUS • Helped testing during 2 weeks visit to ACUS in Sydney in April 2006 • First deadline sept. 2006 not met • Extra time used to integrate new branch opened in Belgium

  7. What we needed to do before implementing ABS (2) • Check EAE to be syntax-free • We already had “clean” sources • Do as many “dry-runs” as needed to be sure

  8. This was the safe passage promise • Export from EAE, import into ABS • Copy database to new machine • Set build properties and press Build • System is generated and deployed • Log-on and start working • Shut down EAE and don’t look back

  9. Did Unisys deliver the promise? • Picked weekend May 26 2007 with extra day • We had quite a few issues • Support was available • Solutions were provided promptly • Migration remained within time-frame • Users could log-on at normal begin of day • We never used EAE again

  10. ABS is running, what next? • Lessons learned • Upgrade ispecs to a more modern look and feel • Exploit developer advantages • Integration with other applications • Integrate acquired company

  11. Lessons learned • ASP’s prevent building new version “on the fly” • Reports build process changed • Don’t remove MCP workfiles • Backup of MCP code and source files takes longer (a lot more COBOL)

  12. Upgrading ispecs to a more modern look and feel • Changing presentation • Using listboxes for queries (eliminates copyfrom ispecs) • Implementing shortcuts for quick navigation • Alter tab sequence to user requirements

  13. Exploit developer advantages • What’s new and how to use it • New LDL+ language • Use parameters with methods • Qualification

  14. What’s new and how to use it • Validator not as good as EAE (yet) • Be careful with removing items • Build changed objects not up to EAE yet • Define methods with ispecs

  15. New LDL+ language • New notation • Migrated notation

  16. New notation MOVE  := A := ISPEC.MTH(B) DOWHEN  If If (A <>B) ATTACH  & A := B & C ATS  &+ A := B &+ C MOVE 1 ARR-PTR MOVE ARR-ITEM  Move ARR_ITEM[1]

  17. Migrated notation Automated change notation using ReEldor

  18. Use parameters with methods • Easier to use for developer • More possibilities • Use method as data-item What data to pass on / receive Which method to use

  19. What data to pass on EAE uses Global setupdata for interface Where to find the items needed Now simply type the name of the method

  20. Which method to use

  21. More possibilities • Use Return value

  22. Use method as data-item

  23. Qualification • Global / Local setupdata

  24. Integration with other applications • Using macro’s to access MCP-database for address info with correspondence • Provide tools to extract MCP-data for use in office-applications while preparing reports • Interact with electronic archive solution being implemented

  25. Word macro’s

  26. Import data in Excel

  27. Integrate acquired company • Enhance user administration • Shield branch-data from access by other branch • Setup Ledger schema and basic data • Prepare user documentation and provide training for new personnel

  28. User documentation

  29. Data-entry hours written Show some of the changes Work on file Check data entered Enter time spent

  30. OLD: Data-entry hours written

  31. New: Data-entry hours written

  32. Clausetext

  33. Invoice info

  34. Relations search

  35. Conclusions • Migration succeeded with safe passage • 11 months operational • Decreasing number open UCF’s • Developers productivity upto EAE • Intellisense is great help for developer • User satisfaction increased

  36. Post & Co (P&I) BV Questions ?

More Related