N4 and XPS Operations: Day 1 Senior Technical Trainer TRAINING Welcome to Introduction to N4 & XPS Navis Technical Trainers Navis Operations: Employees 1 2 202 1 5 3 2 4 Navis Market Share Growing 40% 54% 4,5,6,7,8, 16 3 9,10 1 2 1 2 1 7 1 5 1 3 1 4 11 6 Let’s get to know each other Please introduce yourself. • What’s your name? • Job Title? • What are you looking for in this training? Schedule Just so you’ll know: • Classes start at 09:00 AM • Open lab: 08:30 – 09:00 AM • Breaks: Mid-morning and mid-afternoon • Lunch: 12:00 – 13:00 • Questions welcomed at any time. • • Other conflicts? Please only check email during breaks and place phones on vibrate Who is this training for? In this five-day course, you will be introduced to the basic operational features and functionality of the Navis N4 Terminal Operating System. This introductory course is appropriate for all terminal personnel, including operations, IT, and management, who have completed the prerequisite elearning courses in Stack Academy. 9 N4 Topics • Architecture • Lists and Filters • Vessel Class • Vessel Service • Vessel Visit • Train Visit • • Train Reference Data • Pre-Advise Containers • Export Booking Management • Gate Overview • Gate strategy and business rules • Gate Config Using N4 Gate • Service Events • Holds and Permissions • Business Rules • Storage Rules • N4 Security: User Role Permission • Flex Fields • • EDI Overview • File formats and Standards • Processing Baplie EDI in N4 • Reports Overview • General Notices and Container Notices • Media Assets Report Designs and Definitions XPS Topics • Views • Lists and Recaps • Finding Containers • Filters • Color Palette • Time Frames • • Planning Containers • Yard Planning Overview • Basic Yard Allocations • Allocation Filters • Allocation Groups • Allocation Ranges • Expert Decking (logic) Testing Allocations • Vessel Views • PWP • Discharge Planning • Projections • Quay Commander • Load Planning • • Rail Track Plan • Rail Schedule • Adding rail car to track plan • N4 Mobile • Using EC • EC Coverage • • Monitoring and Dispatching Managing EC Operations Prime Route TRAINING Module 1 What can N4 do for you? By the end of this module, you should be able to: What can N4 do for you? o Understand basic architecture o Log into N4 and XPS 13 What is N4? What is N4? • Order • Plan Execute & Control • Innovative set of Technologies Advanced data model and architecture 25 years operational experience Report Data processing, EDI, load and discharge lists, gate processing, customs holds and releases, liner information The dispatching of plans to equipment and control of the equipmentStow planning for vessels, trains a nd yard moves etc.Understanding and documenting completed operations or those still in‐progress N4 Product Line RFID Gate Automation RTLS, GPS Software Development Kits Vessel Autostow Community Access Vessel Planning Rail Autostow PrimeRoute™ Expert Decking Business Intelligence Rail Planning Equipment Control Yard Planning Berth Scheduling Vehicle RDT General Cargo Billing Reporting EDI Reefer Care Hand held Clerking & Monitoring Gate Operations Import Processing Export Processing Services & Holds Cargo Management Work Order Management Software Development Kits Accounting 3rd Party Systems HR N4 Reefer Monitoring XPS XMLRDT In-house development ECN4 Edge Technologies N4 Modules System Options System Foundation II GateGate Standard Options Advanced Configuration Appointme Appointment nt Data Model Extensions Bills of Lading Guarantees Billing Service Order Management General Cargo CFS BI Live View Specific Chassis Tracking BookingsBookings Vessel Rail EDI EDI Op. Load & Discharge Facility Planning Yard Planning Vessel Planning Rail Planning Equipment Control Gate Clerk Yard Inspection Yard Inventory Truck Control RDT Refer Option Vessel Hatch Clerk QC Activity Rail Clerk / Inventory RDT Execution RDT Cargo Tracking N4 Modules continued Advanced Vessel Package Quay Commander ABS Ro Ro Hazardous Checking Vessel Stability Autostow Advanced Yard Package Hazardous Checking Expert Decking Prime Route Twin & Multi ‐ Lift IFT Prime Route Advanced Rail Package Track Plan Rail Autostow Automated Terminal ASC Manager AGV Manager Gate Automation SNX Inventory Management Automated Reefer Monitoring Equipment Control Equipment RTLS Equipment RTLS Scripting Crane Automation Emulation SDK N4 Integration Gate Automation Edge Technologies RFID RTLS GPS SDK’s Advanced Configuration Gate Automation SNX ICU, HPU, UQ Equipment RTLS Inventory Management Scripting Automated Reefer Monitoring Crane Automation Equipment Control Emulation N4 Modules Data Model Extensions Edi Maps 3rd Party Systems Code Extensions EDI Groovy Finance Labor planning HR M&R Security In‐house Development Configuration & Integration Tailor to your needs, without customization! Configure customer specific areas » Gate » EDI » Reports » Business rules Configuration » Flex fields » Multiple Scopes Enable Integration Integration Full EDI management XML, EDIFACT, ANSI, Etc. Transformation Engine Entity and Source Map & Rules N4 XML compliant Entity Update Document Posting, Filtering Rules User Defined Posting Rules Full EDI management • Posting and Extracting • Mapping, filtering, configurable posting rules • Communication – LAN, FTP, e-mail, SOAP, JMS EDI Mapping Quickly respond to customer requests Xenos Transform Designer – Java based • Multi-platform – XML based maps – 9 categories – Over 60 functions – Custom code Reporting Generate reports in various output formats • Creating a report – Entity and report design – Sorting – Additional criteria • Run-time criteria – Output type • PDF, XLS, CSV, RTF – Security • Roles & Instance • Scheduling Events and Services Everything is tracked as an event! • Define the event • Define the entity • Any required criteria • Additional effects – Tracking of attributes – Updating of attributes – User or automatic Business Rules Entities know about each other! • Holds and permissions • Target service • Rule types – Simple – Guardian – Guarded – Prerequisite • Entity relationships • Hold or permission • Required criteria Storage Rules Define and enforce demurrage rules • Demurrage rules – Full set of filter attributes – Various start count variables – Last Free Day – Paid Through Day • Incorporate within event based rules Flex Fields Track, view and integrate edge data • Flex Fields – Strings – Dates – List of values • Define Scope • Define the views • Apply business rules • Integrate via EDI Seamless Integration Extending N4 • Groovy customization • Integration via APIs • Freedom and Flexibility – Buy, build or outsource Configuration – Upgrade Compatibility Integration Groovy Extensions Last mile in defining your business rules • Inject Source Code • Interpreted • Capabilities – Read any entity – Set any entity value – Send XML via JMS (Java Messaging Service) SNX = Sparcs N4 EXchange • Intended for use by in-house systems • Powerful, low-level API for importing and exporting N4 entities • Message must conform to SNX schema Integration via SNX SNX • Data conversion • Update of Operational Entities – Units, Vessel Visits, Bookings, Bills of Lading • Reference Data – Equipment - Containers, Chassis, Accessories – Routing points, carrier-itinerary, carrier service, vessel, trucking company, truck-driver, shipper consignee • Move Units (In-Yard, Gate, Vessel, Rail transactions) • ICU – Incremental Container Update • HPU – Hold Permissions Update Enterprise Service Bus (ESB) Technology N4 center node • Message Queues: we use “reliable message queues” • Named by scope and origin, for example, “source.opr/cpx/fcy/yrd” N4 Architecture XPS ESB N4 Database IP Node A IP Node A BRIDGE IP XPS Node A EDI ESB IP Node A ‐ Apache customers Node A SPARCS Clients IP Simplified Architecture: Single-Facility N4 Architecture Overview Diagram • Example Architecture • Multiple Nodes • Single facility connected to cluster N4 Architecture: Multi-Facility N4 Architecture Overview Diagram Context Diagram Port Community N4 Cap Users DGPS N4 Users ECN4 WEB DAKOSY COPRAR BAPLIE MOVINS COPARN, COREOR CUSRES MGP S XMLRDT API ECN4 CODECO COARRI EDI BillSys Bridge SN4 XPS WS XPS Users (*) XPS WS XPS Users XPS SN4 DB N4 MOBILE GATE API GOS BI Operations' Clerks: Gate, Yard, Reefer, Hatch, Quay, Reefer, Rail (*) XPS Users: Vessel Planners Yard Planners Equipment Controllers (Dispatchers) 36 Users and Passwords Exercise EXE RCIS E Starting XPS Exercise • Copy the entire Sparcs N4 Client Folder from your memory stick to the desktop • Select SparcsN4Client.exe (application) – Hold and maintain the shift key down • Double click the SparcsN4Client.exe – Mode will be “Client” – For the Private Folder - Go to the Private Data folder (in the same folder as the application) – Select the SPARCS Banner.nbn file • IP address of server: Instructor to confirm • Port is 13000 • Select Registered User - username as N4 (userXY) – NO password EXE RCIS E Logging In Exercise 1. Use any Web Browser to access N4 2. IP Address to be provided by Instructor – http://IPADDRESS:9080/apex/apex.jnlp – Loads Java and brings up the login screen – User: userXY Password: XYuser – After logging, brings up the site selection screen. – Press Go! to start working. EXE RCIS E You should now be able to: What can N4 do for you? Understand basic architecture Log into N4 and XPS 40 TRAINING Module 2 XPS Review By the end of this module, you should be able to: o Understand the relationship between XPS and N4 o Understand what a work instruction is o Identify who mainly uses XPS o Understand how container information is displayed in XPS 42 What is XPS The XPS client, the graphical planning and control system for container handling from Navis. The XPS client is modular system that provides full control for yard, vessel, and rail planning, including dispatch of container handling equipment and other work at the terminal. CO NTE XT 43 43 Who uses XPS? Yard planners, vessel planners, and rail planners use it to visualize their plans for moving and placing containers. XPS produces Work Instructions These plans become work instructions for loading and discharging to Inbound and Outbound Carriers. XPS is customizable The multiple views of individual plans are completely customizable. Yard Planners use XPS • To “see” the containers that will be discharged from incoming vessels or trains into the yard • To pre-allocate space for containers in the yard • To plan where the container will go in the yard and what equipment will move it Vessel Planners use XPS • To plan the best way to discharge containers from a vessel • To create stow plans to load export containers • To create plans to handle restows Rail Planners use XPS • To visualize the best way to move containers scheduled to leave the terminal yard by rail • To move container from the yard or vessel to the correct track • To move the container from the track to the yard or vessel XPS works with N4 XPS and N4 show the same container data in two different ways: N4: XPS: Pop-up windows XPS and N4 work together • They share the same database in real time • XPS is a subset of N4 in terms of: – Scope – Information – Timeframe • N4 focuses on history of units • XPS focuses on future (planning) of units XPS and N4 strengths • XPS is a strong tool for: – Planning – Viewing physical locations • N4 is a strong tool for: – Viewing data in detail – Saving the container activity history – Creating and sending EDI messages For each container XPS knows • What it contains • Where it is coming from • Where it is currently located • Where it is going • How much it weighs • How long it is • If it is hazardous or if it requires special handling • And more… Viewing container information Ways to view container information: Views Lists Recaps Understanding yard views You should now be able to: Understand the relationship between XPS and N4 Understand what a work instruction is Identify who mainly uses XPS Understand how container information is displayed in XPS 56 TRAINING Module 3 N4 Review By the end of this module, you should be able to: o Use the Unit List view to search for specific unit information o Show the Unit Inspector o Create and Save a custom N4 Filter Review o Understand different views in N4 and XPS 58 Compare and contrast on your own You are new at a terminal and are familiarizing yourself with the dataset. You want to take a moment to browse N4 to get a better feel for what you will be working with. Each terminal will have its own unique dataset that will provide information that will be used for planning and execution of the live operation. CO NTE XT 59 59 N4 UI 60 Review: navigation basics Demo Navigate through 3 Modes in N4 Navigate through various menus in XPS DE MO 61 N4 Lists • OPERATIONS UNIT Units • Left click on attribute to sort by that attribute – Left click a second time to reverse sorting – Can sort by 2 attributes – right click to add second sort (ASC or DESC) • Click and drag to reorder attributes. • Right click to add new attributes to, or remove attributes from, the list. 62 Refresher N4 Lists Exercise Go to: N4 Operations Unit Units 1) How many total units are there in the system? 2) Sort by POD a) What is the first POD ascending? b) What is the first POD descending? 3) Remove “Last Move” attribute from the list. 4) Add “Is OOG” attribute to list. a) Are there any OOG containers? b) How many? EXE RCIS E 5) Are there any OOG containers that require power? (Reqs Power) 63 The inspector and searches • Inspector – Provides a quick view of many details about the entity – Can perform certain actions from the inspector – Used for a variety of entities (containers, visits, etc.) • Show Inspector – Click on Magnifying glass in upper right – Opens Inspector Launcher – Works for finding units (containers) only – Enter ending digits of container (at least 4 digits), or full container number. Hit OK. 64 Results from the Global Inspector • Can not find a unit • Not enough characters to uniquely identify the unit • Success 1 2 3 65 The Inspector Details Tab 4 The Inspector Details Tab 5 6 Update information to unit using Unit Inspector Exercise Go to: Inspect unit EXPT1234XY, where XY is individually assigned number • Update Seals • Modify Weight a) Who is the Recorder of the weight change event? • Add a damage. a) Is damage highlighted under All Equipment? • Add a hazard of IMDG 1.1 a) Do you see the hazard indicator? b) Where? • Update POD to HKG a) Do you see the update? b) Where? EXE RCIS E Review: Creating N4 Filters • For more complicated filters, use the filter icon to bring up the panel to define filter criteria. • Be sure to clear your quick search • Filter Criteria – Select appropriate attribute – Select Filter Operator • Is (=): Must match the criteria exactly (no wild cards allowed) • Matches (==): Wild card (%) allowed. – Use of “AND” and “OR” groupings to create more complicated filters. – Use Negate button Review: Saving N4 Filters • Saving a Filter – From the same pop-up, select Save table view as filter… – Give Filter a name and description – If no role assigned, filter only available to that user. – If a role is assigned, all users assigned to that role will be able to see and use the filter. • Reusing Filters – List of saved filters available from pop-up to left of quick search box. – Select a saved filter – enter value if filter has parameterized any attributes. Review: Re-using N4 Filters • Allows one filter for multiple searches – For example, empties in the yard by line operator – Can parameterize the Line Operator attribute – When run filter, will prompt user for specific Line Op • Parameterize a filter attribute – From Filter, select Attribute, and click on Parameterize – Parameter Name: Used to prompt user for what is expected (for example, ‘Cat’ if parameterized the category) – If Value not required, can leave blank and run the filter for all values of the attribute (for example, for all categories) 71 Review Filter Exercise Exercise Go to: Operations Unit menu Units 1. How many exports (category) with a transit state of yard are sealed (is sealed)? – Delete is sealed when you have the answer 2. How many exports with a transit state of yard have a prefix of TTNU? 3. Parameterize “prefix” and save filter a. Close units list and reopen b. Reuse saved filter c. How many exports with a transit state of yard have a prefix of CBHU? EXE RCIS E 72 You should now be able to: Use the Unit List view to search for specific unit information Show the Unit Inspector Create and Save a custom N4 Filter Review Understand different views in N4 and XPS 73 TRAINING Module 4 Vessel Setup By the end of this module, you should be able to: o Edit itinerary with all ports for the voyage rotation o Identify a Vessel and Vessel Class in N4 Vessel o Create Vessel Visit in N4 Setup 75 The Steps to Plan a Vessel 76 Initial Vessel Configuration • Vessel Classes CONFIGURATION Carriers Vessel Class Used by XPS to identify appropriate ship file Required Piece of a Vessel Record, even if site does not use XPS • Vessels CONFIGURATION Carriers Vessel Used to Define Vessels calling at the yard Does not define specific visit of the vessel, just the vessel itself Vessel must be defined before you can define visit of the vessel 77 • CONFIGURATION Carriers Carrier Services Carrier Services — Define Port Rotation for the service — Can map destinations to certain ports 78 Check a Carrier Service The vessel is on the Asia Pacific Service (APS) and the ports of call in the rotation are identified in an email. CO NTE XT 79 79 Check a Carrier Service Exercise 1.In Configuration Mode, Go to Carriers > Carrier Services 2.Find the APSXY service (XY is your user ID) 3.Edit Itinerary a. Make sure you have OAK as the 1st port b. OAK HKG PUS SIN TYO SYD LAX EXE RCIS E 80 Vessel Visits Ship File Line Operator Vessel Class Vessel Vessel Visit N4 Visit Phase set to “Inbound”, “Arrived” or “Working” XPS Bridge Carrier Service 81 About Vessel Visits • OPERATIONS Vessel Vessel Visits – Used to define specific Vessel Visits • Dates are ISO standard YYYY-MM-DD – Date format is controlled by N4 setting – N4 can auto fill current year and month • Visit Phase controls ability to load/discharge – Set Phase to Closed after vessel departure to delete vessel and on-board containers from XPS • Bookings are validated against the Vessel Visit. – Must associate lines to Vessel Visit. – Bookings for lines not associated with the Vessel Visit will be rejected at the gate. – Associate Lines via Vessel Inspector (Details Lines Tab) • Create Vessel Visit – Create in N4 – DB will update XPS Preparing for XPS Vessel Planning Create a Vessel Visit The Vessel Visit is the voyage into your port on a specific date. A regular service will have multiple Vessel Visits that arrive on a regular basis. A visit is different from a call. CO NTE XT When a vessel has to come back to your port it is defined as call number 2. (The second arrival) Some ships discharge on call 1 and load on call 2 84 Create a Vessel Visit Exercise • In Operations Mode, go to Vessel Vessel Visits • Enter Visit Reference code LSVXY Where XY is your user number Enter your vessel SXY • Make inbound and outbound voyage: 001 • • Leave call number = 1 • Enter your service: (APSXY) • Line Operator = LXY • ETA = T (for today) and N (for now) • Classification is Deepsea • Save your new Vessel Visit EXE RCIS E Cut-offs • Different lines have different agreements • Some terminals dictate the times – Some terminals have no cut-offs • Cut-offs control the late arrival of units • Business rules at the gate prevent receival after the cut-off time – RejectCarrierVisitPastCutoff • Different container types can have different cut-off times made – Dry – Hazard – Reefer • Agreed late containers need to be added to Late Arrivals list to bypass the reject business rule 86 Defining Cut-offs in N4 In Vessel Visit Edit Vessel Details, • You add cut-offs for cargo receival in the Vessel Visit • Ability to add other detail relevant to the visit You should now be able to: Edit itinerary with all ports for the voyage rotation Identify a Vessel and Vessel Class in N4 Create Vessel Visit in N4 Vessel Setup 88 TRAINING Module 5 Advancing the Vessel Visit By the end of this module, you should be able to: Advanci ng the Vessel Visit o Advance Vessel Visit in N4 o Check Vessel Visibility in XPS 90 Viewing the vessel in XPS • You cannot see the vessel in XPS when created • You “Advance Vessel Visit” through various stages of the entire visit – You take it from “Created” to “Inbound” to see it in XPS This confirms the visit – The visit should show as “Arrived” when it berths This confirms the vessel alongside – You advance to “Working” when ready to start work – At the end of the exchange you set it to “Complete” – “Departed” send all containers onboard out of the terminal • Remember: visit phase matters! Advance the Vessel Visit Advancing a visit updates the phase of operation and the visibility in XPS and allows the system to allow specific actions. For instance, you cannot discharge a container when the vessel is Inbound so it has to be Working. CO NTE XT You do not need to advance one step at a time. You can go up 2 phases from Created directly to Arrived for example. If you need to go back to Created, you can only go back one phase at a time so you need to go through Inbound before you can access Created. 92 Advance the Vessel Visit Exercise In XPS go to Vessel Open • Look for your vessel on the list • If you can’t see it, why not? EXE RCIS E Advance the Vessel Visit Exercise 1.In Operations Mode, go to Vessel Vessel Visit 2.Open your visit previously created (LSVXY) 3.Actions Advance Vessel Visit 4.Change from Created to Arrived – ETA Date= T (today) Time= N (now) – ETD Date=+5 Time= 21:00 – ATA Date= T Time= 08:35 EXE RCIS E Advance Vessel Visit to Inbound Exercise 1. Verify Vessel is visible in XPS 2. Extra Credit – What are the two reasons why a vessel may not be visible in a graphical view in XPS? EXE RCIS E You should now be able to: Advanci ng the Vessel Visit Advance Vessel Visit in N4 Check Vessel Visibility in XPS 96 TRAINING Module 6 Process BAPLIE IN By the end of this module, you should be able to: o Bring inbound BAPLIE EDI to N4 for vessel o Identify batch for EDI and check for errors or warnings Process BAPLIE o Add detail to EDI filter to change bad information into good IN during processing of the BAPLIE o Re-post BAPLIE EDI to clear errors, etc. o Check on-board list for complete details 98 Import EDI We need to understand what containers are to be handled for the vessel that will call the terminal. We exchange information with Trading Partners through the use of Electronic Data Interchange (EDI). EDI Trading Partners are Organizations, such as a Line Operator, with which EDI Messages are exchanged. CO NTE XT In order to plan the movements of containers in the terminals we must first make sure that we have the correct information to work with. 99 99 What is EDI? • EDI = Electronic Data Interchange • The process by which data files are exchanged electronically between one party and another • Allows the transmission of mass quantities of data between terminals, shipping lines, agents and other parties • Standardized file formats – ANSI X12, UN/EDIFACT N4 EDI: Introduction Outbound Stowplan (BAPLIE) Vessel Loads and Discharges (COARRI) Inbound Stowplan (BAPLIE) Pre-Advise (COPINO) Ingate/Outgate Activity CODECO COPRAR Load or Discharge List Export Bookings COPARN Terminology – Messages and Standards • Message (or EDI Document, EDI File) – File containing data formatted according to EDI standard • Standard – Set of standard EDI Message Types • EDIFACT or X12 • Message Type – EDI message template based on EDI Standard • BAPLIE, CODECO, 315, etc. • Segment – Structured parts of an EDI Message • equipment record in a stow plan • Field – Element within an EDI Segment that defines a particular attribute • container height, full or empty, routing, etc. 102 Terminology – EDI Processing • Load – Loading an inbound Message into the Staging Tables – Review in EDI Interchanges • Post or Extract – Commit inbound EDI data from Staging Tables to the N4 database – Extract data from N4 and convert to outbound Message • Error – Error that occurs when processing EDI Batch • Warning – Minor Problems (bad load port) • Mapping File – An XML file that maps Segments of Message to fields in N4 103 N4 EDI Setup • Overview of processing and sequence of setup – Directory Structure – Message Types • • Import predefined Message Maps (XENOS) Message Type linked to a Message Class stowplan, booking, release, etc – Trading Partners • Create Mailboxes within the Trading Partner form • • Change bad information to good ROT should read as RTM – Filters – Sessions • Assign predefined Filters • Assign predefined Sessions – Schedules • Validation – look in Interchanges, batches, segments • Execution – Post or Extract 104 Setting up an EDI Directory • Setup a unique directory for – each direction/message type/trading partner combination • N4 will automatically sweep to get inbound EDI files • N4 will automatically put outbound EDI files Examples: • /u01/edi/in/MSK/315 : – Inbound 315 received from Maersk • /u01/edi/in/MSK/baplie : – Inbound BAPLIE from Maersk • /u01/edi/out/MSK/322 : – Outbound 322 sent to Maersk • /u01/edi/out/MSK/baplie : – Outbound BAPLIE sent to Maersk • Note the archive folders. – Created automatically in the folder 105 Defining EDI Message Types • Version/Release Numbers validated against message • Default maps provided by Navis • Specify EDI map to be used with message type: custom or default 106 Tasks Effected by Posting the BAPLIE Create Vessel Plan berth Import vessel’s bay plan Plan discharge Plan and sequence projections Create crane plan Plan load Track work and re-plan as needed Export bay plan, reporting A closer look at a BAPLIE Message Reading a BAPLIE file Exercise UNB+UNOA:2+APL+FCP PLANNING+030626:1314+0' UNH+1+BAPLIE:D:98B:UN:SMDG20' BGM++0+9' DTM+137:200306261314:203' TDT+20+216R+++MSC:172:20+++H3LV:103::MSC Sandra' LOC+5+USNEW:139:6' DTM+178:200306261314:203' LOC+147+0010882::5' MEA+WT++KGM:16600' LOC+9+AUSYD' LOC+11+NZLYT' LOC+76+AUBNE' LOC+83+NZBLU' RFF+BM:1' EQD+CN+ASCU2643846+2200++3+5' Using Baplie.pdf (Baplies folder) • Message type identifier? (UNH) • Version and Release Number? (UNH) • Vessel Name? (TDT) • Containers No & ISO Code? (EQD) • Import or Transshipment? (EQD) • Full or Empty? (EQD) • POD? (LOC) • POL? (LOC) EXE RCIS E 109 N4 and the BAPLIE EDI message • EDI processing and viewing for stowplans made available under Operations Vessel menu • Manually imported through Vessel EDI Load – Also available under Administration EDI • Requires an EDI Session for the line operator of the vessel • Options available during EDI Load: – Post Immediate Used when you have a reliable and tested session and EDI message – Additions Only Looks for extra containers to add to the stowplan Ignores containers already processed – Positions Only Creates new containers and updates only the change in position for existing containers – Discharge Only N4 posts only the import and transhipment containers that must be discharged at the current facility 110 Before you load your first BAPLIE… • Expect errors in Load and Post • Go slowly • Read the error messages • Correct reference data in N4 Modify your inbound BAPLIE file There is more than one line being handled on this visit. In order to accept an export against a booking, the Line Operator must be associated to the Vessel Visit. CO NTE XT 112 Modify your inbound BAPLIE file Exercise 1. Open your Vessel Visit and select the Lines attribute 2. Add the following Line Operators to the list of who can work on your vessel: a. COS b. NYK c. MSK d. APL 3. Be sure to add inbound and outbound voyages 001 EXE RCIS E Load an inbound BAPLIE When we load a BAPLIE we have to see what happens. It may go through to MAPPED but if there is a problem it will stop with an ERROR. These have to be resolved and the session remapped and rerun to try to clear the error. CO NTE XT What do you see in your terminal? What kind of information do you have to change or filter to allow you to get to the equivalent of N4’s MAPPED stage? 114 The Inbound EDI Process – Receive Receive Load Classify Map Post • Raw interchange placed in directory by communications manger (VAN) via FTP or SMTP Receive The Inbound EDI Process – Load Load • Files moved from mailbox and loaded into N4 Staging Tables – Done manually or via scheduler task Classify Map Post • Creates Interchange and Segments within N4 • Archives initial EDI files into subdirectory of mailbox • Does not create, modify, or delete any operational data Receive The Inbound EDI Process – Classify Load • Interchange inspected to determine Message Types and EDI Partner • Corresponding EDI Session is identified • For each distinct Message Type an EDI Batch is created • Could have multiple Batches and Messages Classify Map Post The Inbound EDI Process – Map Receive Load Classify Map Post • For each batch, the correct EDI Map is now known • All Segments for a Batch are passed to the mapper • Applies Filters • EDISegments table read into Translator (XENOS GoXML) • Creates committable EDI Transactions from these Segments • Translates EDI to XML Receive Inbound EDI Process – Post Load • Finds key words • Commits the records to the database • Can be automatic or manual (determined by session) Classify Map Post Load an inbound BAPLIE Exercise 1. Go to: Vessel EDI Load. 2. Choose the EDI Session for your Line (L01, L02, etc.) 3. Click the Browse button and access the memory stick to locate the EDI BAPLIE file for your vessel 4. For this exercise, leave the Post Immediate, Additions, Positions, and Discharge Only checkboxes UNCHECKED 5. Click Load 6. Go to Vessel Stowplan Batches – what do you see? EXE RCIS E Process an inbound EDI file After receiving an inbound BAPLIE from the previous port, we discover anomalies in the file that need to be adjusted after posting. The file may have invalid load and discharge ports, incorrect radio call signs, ISO not known, etc. CO NTE XT 121 Process an inbound EDI file Exercise 1. Go to: Vessel Stowplan Batches 2. Find your EDI Batch (hint: look for your session name) 3. Double-click to see the EDI Batch Inspector 4. Go to the Details tab and look at the "Processes" 5. Did your BAPLIE load without errors? 6. How long did it take to load? 7. What other processes happened? EXE RCIS E Resolving Common EDI Loading Errors There are three process statuses: ERRORS • Occurs during the processing of an EDI batch • Prevents the batch from posting to the database WARNINGS • Occurs during the processing of an EDI batch • Indicates that attention could be required • Does not prevent the batch from posting to the database COMPLETE • Shows after EDI has successfully processed without ERRORS or WARNINGS Errors • You can see the detail in the Batch Inspector – Processes tab • Double click to see the errors • Every error will have a line – One transaction (container) could be mentioned on multiple lines • Invalid Port of Discharge : “CAVAN“ – CAVAN is not on the carrier service itinerary • POD USHOU is not found – USHOU is not a port in the database • Unknown container operator for code DLS and agency BIC – Line operator DLS is unknown – Because it is unknown, the BIC code is not correct as well 124 EDI Filters • We create a filter that will change ROT to RTM every time the Inbound Session for the line is run • Attached to the EDI Session — Translates data from one value to another when N4 posts an EDI message Invalid Port of Discharge : “ROT” — EDI message shows ROT as the discharge port — Our Routing Points refer to Rotterdam as RTM 125 Create a filter for your session Our EDI customers have their own systems and ways of describing attributes. Some will use a combination of letters and numbers for ports, some will use a phonetic way of writing a port code while others follow an industry standard and may have asked you for your way of describing a port. CO NTE XT You will use filters to change their information into a format and content that complies with N4 Reference Data. 126 Find a filter for your session Exercise 1. Go to Administration EDI Filters 2. Find and open your filter LXY_IN 3. Check the Direction as “Receive” EXE RCIS E EDI Posting Rules • ADMINISTRATION EDI Posting Rules – Controls what to do if EDI data conflicts with data already in the system – General Rules – Specific Rules for certain fields – Set Criteria on whether to apply new data or to ignore new data. 128 Post your BAPLIE After seeing your errors, you need to filter the bad information to make it good for N4 to use. CO NTE XT 129 Post Your BAPLIE Exercise Once the BAPLIE has mapped without errors: 1. Go to your batch: Actions Post 2. Look at the Processes in the EDI Batch Inspector, and find an ERROR process 3. 4. – Double-click on an Error Process – what were the specific errors? – Resolve the errors per the error messages – Add error changes to your edi filter and save. Go to your batch – Actions Remap – Actions Post Once you have resolved all errors and warnings go to: Operations Vessel Vessel Visit – Look at ‘Onboard’ in the Vessel Inspector – The containers from your BAPLIE should appear EXE RCIS E Check onboard lists • N4 – Vessel Visit Inspector On Board tab • Shows all containers that are Inbound on the vessel • XPS – Current Vessel filtered list • Shows all containers that are inbound on the vessel • Check that all containers have a vessel slot – May have been added manually and slot left out – Vessel slot on BAPLIE was invalid 131 Check on-board lists It is vital that we make sure everything is accounted for after your BAPLIE is brought in. Cross-checking N4 against XPS: CO NTE XT Using “Check Stowage” in XPS will show what errors it can see If we don’t check and balance it will cause problems further down the line as we load containers to the vessel. 132 Check on-board lists Exercise 1. Use N4 Vessel Visit Inspector On-Board tab a. How many containers are on the vessel? 2. Use XPS Container Find a. How many containers are on the vessel? EXE RCIS E You should now be able to: Bring inbound BAPLIE EDI to N4 for vessel Identify batch for EDI. Check for errors / warnings Add detail to EDI filter to change bad information in to good during processing of the BAPLIE Process BAPLIE IN Re-post BAPLIE EDI to clear errors etc Check on-board list for complete details 134 TRAINING Module 7 Vessel Views and Sequencing 55 HARRISON STREET, STE. 600, OAKLAND, CA 94607, USA WWW.NAVIS.COM TEL: +1 510 267 5000 FAX: +1 510 267 5100 EMAIL: TRAINING@NAVIS.COM 135 By the end of this module, you should be able to: o Open Vessel o Understand various vessel views Vessel Views and Sequenci ng 136 Open your Vessel You cannot imagine how a vessel looks by reading the vessel slot positions. You need visualization. CO NTE XT Opening the vessel scan plan will allow you to see where containers are positioned on board the vessel. 137 137 Opening Vessel Views • The XPS Client interface offers users many views and information options • Attributes of an open vessel in XPS: 138 Vessel Profile 139 Understanding the Vessel Scan Plan View • Select the Scan button on the vessel profile to open a scan plan • Increase the size with the scaling pop-up menu Scaling pop-up men 140 Scaling the Scan or Section View Scaling pop-up menu • Open a section (bay) view by selecting the magnifying glass and sweeping over the bay • Magnify the view to your liking 141 Open your Vessel Exercise 1. 2. 3. Open the scan plan of your vessel using the Scan button on the vessel profile Open paired bays by selecting the bays with the magnifying glass Change the sizes of the sections by changing the popup scale EXE RCIS E 142 You should now be able to: Open Vessel Understand various vessel views Vessel Views and Sequenci ng 143 TRAINING Module 8 Pre-defined Work Patterns 55 HARRISON STREET, STE. 600, OAKLAND, CA 94607, USA WWW.NAVIS.COM TEL: +1 510 267 5000 FAX: +1 510 267 5100 EMAIL: TRAINING@NAVIS.COM 144 By the end of this module, you should be able to: Predefined Work Patterns o Define what PWP means o Set PWP o Review PWP 145 What is PWP? • PWP = Predefined Work Pattern • Defines general load and discharge work patterns for vessels – Saves time by automating work sequences • Stored sequence of within a vessel bay – Configurable by Bay, Saved for entire Ship Class • Dictates normal order of load or discharge – Planner can change the sequence in real time • Continue to use Your Vessel for PWP Tasks affected by PWP Create Vessel Visit Plan berth Import vessel’s bay plan Plan discharge Plan and sequence projections Create crane plan Plan load Track work and replan as needed Export bay plan, reporting Setting PWP for a Vessel • Set Work Pattern menu item in Special menu of vessel profile • XPS automatically applies pattern to vessel class Setting PWP for a Vessel • Set work pattern — For 20s — For 40s — For multiple lids • Different patterns for loads vs. discharges • Different crane types handle load and discharge differently as well • Gantry operator has full visibility • Mobile Harbor Crane driver cannot see through high stacks Views from the cab 150 Setting PWP for a Vessel By Stack, Center First By Tier, Outboard First Sequencing by Tier Outboard First (Load) Inboard First (Discharge) Sequencing by Stack Outboard First (Load) Inboard First (Discharge) Sequencing Center First By Tier By Stack Sequencing Twins by Tier Outboard First (20’s only) 7&8 9&10 1&2 3&4 5&6 Inboard First is also available Sequencing Twins by Stack Outboard First 7&8 3&4 1&2 5&6 9&10 Inboard First is also available Sequencing Paired 20s Outboard First 11 12 Inboard First is also available Multi-Lift Multi Lift Terminology Quad Lift Twin Lift Tandem Lift Single Lift Define the PWP of a Ship The vessel will load and discharge by tier both on deck and under-deck. Twin-lifting on deck only is required. By taking a tier at a time we allow for a stable weight change across the vessel. CO NTE XT If we discharge from underdeck by stack we can create opportunities to dual cycle where you load into one cell and discharge from another cell utilizing the same transfer CHE. 160 Define the PWP of a Vessel Exercise 1. Select Bays with Power Flow Tool SPECIAL Set Work Pattern 2. Above Deck: 40s and 20s a. Load by Tier, Outboard First b. Discharge by Tier, Inboard First 3. Below Deck: 40s and 20s a. Load by stack, Outboard First b. Discharge by Stack, Inboard First 4. Bay 07/09 Above: 20s Only a. Load Twin Lift By Tier, Outboard First b. Discharge Twin by Tier, Inboard First c. Master Sections start with 40s Checked 5. Select All Bays from Vessel Profile a. SPECIAL Show Work Pattern to verify PWP EXE RCIS E You should now be able to: Predefined Work Patterns Define what PWP means Set PWP Review PWP 162 Fundamentals of N4 and XPS Operations: Day 1 Daniel Leask, Senior Technical Trainer TRAINING Thank you! NCC LINKEDIN TWITTER WEBSITE collaboration.navis.com linkedin.com/company/navis @naviscargo navis.com
0
advertisement
Add this document to collection(s)
You can add this document to your study collection(s)
Sign in Available only to authorized usersAdd this document to saved
You can add this document to your saved list
Sign in Available only to authorized users