PORT OF MELBOURNE ECOMMUNITY
SMART FREIGHT SINGLE WINDOW PILOT Contract No. 13110 Closing date: Thu 07 Dec 2006 - 1200 Melbourne time
PORT OF MELBOURNE ECOMMUNITY-SMART FREIGHT SINGLE WINDOW PILOT SMART FREIGHT SINGLE WINDOW PILOT - Expression of Interest [EOI] Design, develop, build, operate, maintain and evaluate the Smart Freight Single Window Pilot on-line system. A Background A.1 Objective of the Single Window Pilot A.2 Port of Melbourne Supply Chain Community a Shipping Lines/Agents b Freight Forwarders c Customs Brokers d Stevedores e Port of Melbourne Community [PoMC] f Transport Companies g Exporters h Importers B System Requirement B.1 Overview 1 Background The Port of Melbourne is Australia's largest port for containerised and general cargo, handling approximately 40% of the nation's exports. The Port of Melbourne supply chain involves 3200 ships from over 40 shipping lines. Nearly 2M containers and 50M tonnes of bulk cargo transits the wharves of the two stevedores, serviced by three train operators and 250 trucking companies. This trade generates an average of 80,000 shipping transactions per day between the involved parties. The supply chain is characterised by some large freight forwarders and transport operators accounting for nearly half of the container moves through the port, and a large number of small to medium enterprises (SMEs) accommodating the balance. The current ICT systems that support the participants in the supply chain cater for the larger organisations but are arguably less useful to the smaller companies due to the cost of developing a capability to effectively use the services (subscription costs, inadequate infrastructure etc.). This can lead to the continuation of manual links between supply chain participants which affects the reliability and performance of carriers, shippers and terminal operators. Increasingly the lack of effective information sharing among stakeholders is creating bottlenecks and unnecessary delays in the efficient movement of freight. These inefficiencies increase supply chain costs which directly impact the economy of Victoria. It is anticipated that these inefficiencies will be amplified as more security and other regulation is imposed on supply chain participants. This Department of Infrastructure (Victoria) initiative therefore seeks to develop a Smart Freight Single Window system to provide ICT services for the participants in the Port of Melbourne supply chain. The system will assist the supply chain by: A developing appropriate sub-systems to automate procedures and improve interoperability between parties in the port of Melbourne's supply chain B providing easy and equitable access to trade and transport systems to move cargo from exporter to port and port to importer C promoting new ICT solutions to supply chain impediments, particularly where they assist the optimisation of public infrastructure D providing appropriate governance to the trading environment through the endorsement of open standards and the support of industry regulatory bodies E addressing the need for appropriate security and protection of critical infrastructure. This EOI is to solicit interest, from experienced organisations, in building/operating a pilot system to achieve these critical success factors. A.1 Objective of the Single Window Pilot The Single Window pilot is to test the viability and user acceptance of providing a Trade and Community System that improves the ability of participants in the supply chain to move containerised cargo through the Port. Successful deployment of the pilot will allow the addition of value-added services provided by other supply chain participants who service to the Port of Melbourne containerised cargo supply chain. The pilot is to operate for an initial period of 12 months. If it is deemed successful the system may be expanded to include additional facilities and the possible addition of commercial services that would be of benefit to the supply chain community. A.2 Port of Melbourne Supply Chain Community The following participants comprise the Port of Melbourne supply chain community: a Shipping Lines/Agents b Freight Forwarders c Customs Brokers d Stevedores e Port of Melbourne Community [PoMC] f Transport Companies g Exporters h Importers a Shipping Lines/Agents Shipping Lines and Agents will use the Single Window pilot to submit Vessel Arrival Requests using a web form, an EDI service or an email attachment. Lines and agents will also be able to use the system to send incoming hazardous cargo information to the PoMC, freight forwarders and AMSA. Examples of shipping lines servicing the Port of Melbourne are: 1 Maersk Australia Pty. Ltd. 2 Mediterranean Shipping Co (Aust) P/L 3 NYK LINE (Australia) Pty Ltd b Freight Forwarders Freight forwarders will initially use the Single Window to verify information currently received from other systems. The pilot system will include the functionality to submit hazardous goods information to shipping lines and generate the requisite notifications for hazardous goods imports. In some cases freight forwarders will access container gate in/out information via the Single Window. The directory service component of the Single Window is expected to be invaluable to the freight forwarder community. Examples of Freight forwarders operating in Melbourne are: 1 Intergroup Australia 2 Patrick Logistics 3 Strang International Pty Ltd c Customs Brokers Custom brokers are very dependent upon information regarding their customer's shipments. The Single Window will primarily be of interest to the smaller operators who will use the system to access ship arrival information and possibly for container event information. All Customs brokers will benefits from the contact details and directory service available via the Single Window. Examples of Customs Brokers are: 1 C. Strokes and Co Pty Ltd 2 I.C.S International Customs Services Pty Ltd 3 Select Customs Services Pty Ltd d Stevedores Stevedores will initially use the system to verify information already obtained from their 1-Stop and terminal operations systems. They will benefit from fast access to accurate contact details via the directory service. Stevedores will also be recipients of hazardous goods declarations lodged via the Single Window. The two main stevedores operating in the Port are: 1 Toll (formerly Patricks) 2 DP World (formerly P&O) e Port of Melbourne Community [PoMC] The main benefit to the PoMC will be the increased visibility to the movement of containerised cargo through the port. The PoMC will receive Berth Notification requests from the system. It will also be the source of arrival, departure and movement information. PoMC will be a recipient of hazardous cargo information, for import, export and in transit cargo. f Transport Companies Transport companies will be able to use the system to monitor expected vessel arrival and departure information. For import cargo it will be used to plan pickups from the terminal. Transport companies will also receive hazardous goods notifications pertaining to cargo they are contracted to carry. For export cargo the system will advise on the packing restrictions and placarding requirements for hazardous goods. g Exporters Exporters will be able to monitor vessel arrival and departure information. They will also use the system for hazardous cargo information, and input the information into the Single Window system for hazardous goods notification to the relevant authorities and supply chain participants. Contact details for participants in the supply chain available via the directory service will be invaluable for exporters. h Importers Of prime interest to importers will be the expected vessel arrival times which will be available on the Single Window in an easy-to-use format. They will be interested in individual container status, for which the Single Window will provide an easy-to use update service. 2 System Requirement 2.1 Overview The Single Window Pilot will provide the following facilities: A Directory of participants - to include a entries for the entire community of interest, b basic contact details will be provided as well as a white pages function to allow users to perform searches on a variety of attributes such as 1 name, 2 type of industry and 3 location. B Ship arrival and departure information - to show a the estimated (or actual) arrival time and b allocated berth for arriving ships and c the cut-off time and d estimated sailing dates for departing vessels. The screen operation will be intuitive and not require any industry specific knowledge. c Hazardous goods notification - to provide assistance in meeting the submission and distribution requirements for the transit of hazardous cargo through the Port. The system will facilitate both exporters and importers, or their agents, to generate the required documentation (IFTDGN/MO41 forms) on line and then submit the form to the appropriate authorities. The system will also provide the option to generate the PRA as part of the export process, sending the electronic message to the 1-Stop system). D Berth services notification - a shipping lines, or their agents, will advise the PoMC of estimated ship arrival and b advise terminal berth allocations. The notification form will also provide a facility for the shipping line, or agent, to advise of the required services such as pilots, tugs and linesman. E Container status - basic container status information for imports will be provided; this will include a the ability to enter container numbers for containers being off-loaded at the Port b the system will return available time and gate out time. For those containers being handled via Importnet, additional detail such as container type and return depot will be shown. For those containers being returned to a deport that has the appropriate facilities to notify the Single Window, the return status of the container will be shown. For containers returned to other depots, a facility to allow transport companies to enter empty container return receipts will be made available. For containers being exported the system will display gate in time at the terminal and vessel loading time. The pilot system will be basic in its operation in order to limit the development time and the impact on source systems (SHIPS, 1-Stop and MaxeTrade). Since the system will be expanding the user-base of current systems to a wider cross-section of the supply chain community with potentially less experience of ICT services, operation of the site must be as intuitive as possible.
[ Home ] [ eCommunity Tenders ] [ This EOI ] [ Q&A on EOI ] [ Port Info Flows ] [ AS 4590 Status ] [ Timetable AS4590 Conflict ] [ Copyright ] RUBAC Electronic Information Management Methodology Copyright of Hamme Family Trust