Downloaded 32 times
Efficient Stowage Planning
- 1.
- 2. Typical process 22016-07-01 Tonnage Planning •Allocationof vessel type to trade •Based on long term forecast •Only cargo volume available in forecast Voyage Planning •Assignment of vessel to route •Based on short term forecast •Required cargo area and deck type now available in forecast •Voyage number created •Booking allocations created Stowage Planning •Booking list with some cargo properties now available •Voyage schedule available •Booking allocation management is ongoing Stowage Registration •Load list with additional cargo id property now available 1 year until 6 month before loading 6 month until 6 weeks before loading 6 weeks until 1 day before loading Day of loading Focus area
- 3. 2016-07-01 3 Main issues IssueConsequences Solutions 1. Complete booking list is available too close to stowage plan deadline from stevedores Poor stowage plan quality with risk for: • Too many stevedores are ordered and causes unnecessary stevedore cost • Too few stevedores are ordered and causes extended port stay and high stevedore overtime cost • Too short time for elaboration over planning options when planning complex cargo mix may cause reduced space utilization • Plan readability is dubious and subject to errors in the execution (loading). This may cause unnecessary shifting cost and even damage to cargo and vessel Stowage Planning System 2. Incorrect and/or missing information in cargo deck drawings Vessel Editor 3. Assessment of vessel stability and floating condition is cumbersome and takes long time • Inadequate stability calculation before any operation such as loading, discharging, ballasting or bunkering is posing risk for excessive list followed by cargo shifting and ultimately capsizing • Sailing with poor floating condition (draft and trim) will increase bunker consumption Autoload Stowage Planning Stowage Registration
- 4. 2016-07-01 4 Main issues IssueConsequences Solutions 1. Stowage plans made by planmakers in port is often not entirely correct • Preliminary stowage plans for following ports becomes inaccurate. This will often force plan deviation decisions to be taken “on the fly” with costly impact. • Incorrect stability calculation that put ship safety in jeopardy ScanPlan 2. Stowage plans are often too general • Not possible to locate specific cargo from land based office. Onboard manual time-consuming search with risk for cargo damage is required. • Not possible to locate where Alternative Fueled Vehicles are stowed. Additional information is required. 3. It is difficult to validate services performed in stevedore invoice • Risk for being overcharged Stowage Planning Stowage Registration
- 5. 2016-07-01 5 Stowage PlanningSystem Fully customizable toolbar Bookings with EDI from database, file import or manual entry Key info from selected lineitem(s) in Booking List Detailed deck plan showing location of all types of cargo in correct scale Schedule with EDI from database, file import or manual entry Key deck property data Key cargo data for selected object Typical users: Stowage Planners, Planmakers in port, Chief Officer
- 6. 2016-07-01 6 Autoload Cargo weights withcoordinates from SPS Tank contents from sensors or manual input Section with essential data to assess ship safety Sections showing ship floating condition Typical users: Chief Officer and/or Stowage Planners
- 7. 2016-07-01 7 Vessel Editor Menuline include functions like: Save to Database, Info sheet report, plus all functions required for creation of a vessel model Expandable tree view for easy drill down to property window Property window for data entry Deck plan window include all functions required to draw deck plan and data entry for efficient stowage Typical users: Autoship and/or SPS superusers
- 8. 2016-07-01 8 Stowage Registration(ScanPlan) 1. Export load list data to scanner(s) 4. Import stowage plan data from scanner(s) 2. Scan cargo 3. Use ScanPlan Scanner(s) connected in office Typical users: Stevedore tally or ship crew
- 9. Next steps? 92016-07-01 Trial period •Twovessel models with expiration at trial end date (Rumarcon AB) •On-site user training and support and in one office (Rumarcon AB) •Client provide file export from booking and schedule system. ASC to make required adjustments for import to SPS. •Decision to go or not go to full production. Required modification. Full production •Support for full EDI with client booking and schedule system (ASC) •Vessel models for all vessels in fleet •On-site user training and support and in office (Rumarcon AB) • Services provided by Rumarcon AB • Maintenance and services contract with ASC • Services provided by Rumarcon AB