navis_sparcs_n4_v2_web

Whats new in Navis SPARCS N4 version 2.2 1

Whats New in Navis SPARCS N4 version 2.2

October 1, 2011


Navis SPARCS N4 version 2.2 is Generally Available!

Whats New in SPARCS N4 version 2.2

Navis SPARCS N4 version 2.2 represents the largest new feature release to date with new modules such as General Cargo, Multi Lift and Yard Editor, as well as new functionality to existing modules which provide customers with greater flexibility to configure and extend SPARCS N4.

Navis SPARCS N4, version 2.2 has been extensively tested for performance and scalability, certified for 5M TEU for import/export terminals and 10M TEU for transshipment terminals. This version also supports, Windows 2008, Oracle 11g and 64-Bit systems and includes a unified N4 based multi-tiered J2EE architecture.

Some key changes to the Navis SPARCS N4 in version 2.2 include:

New functionalities to support general cargo and container freight station operation

Enhancements to ECN4, which now becomes generally available

The addition of Yard Editor

Configurable reporting entities

Documentation of the SPARCS N4 domain model and public SPARCS N4 APIs

The addition of Multi-lift functionality

New Modules

NEW: Yard Editor

New in the Systems Foundation Options II, Yard Editor is a graphical yard editing tool in the SPARCS N4 user interface used to set up your yard(s). Yard Editor provides a quicker, more dynamic editing technique, as opposed to the slower conventional spreadsheet methodology. This enables you to easily configure your yard for implementation and to make changes to your yard on the fly in production.

In addition, Yard Editor provides:

The ability to create a yard from scratch in SPARCS N4 for customers that do not already have a yard file.

A mechanism to import an existing compiled yard file for customers that already use SPARCS or that have a yard file. This enables you to use or edit your existing yard file with Yard Editor instead of creating a yard from scratch.

A forward- and backward-compatible yard file for customers that already use SPARCS N4 in production. This enables customers that are upgrading SPARCS N4 the ability to still use their existing yard file until they are comfortable with Yard Editor.

Support for PDS positions via an API for ECN4, enabling a third-party location system to provide raw location information eliminating the need to maintain a parallel yard file.


A mechanism to import and export your configured yard file. This enables you to configure and test your yard on a test system before deploying it in production.

With this option, you can:

Import an image of your yard, such as a CAD drawing, satellite, or other aerial imagery, to serve as a background for the yard map.

Define reference points in the yard map to determine the geographic coordinate system of the physical space. SPARCS N4 uses this to calculate conversions between map points and latitude and longitude information.

Draw the yard perimeter on the yard map with just a few mouse clicks.

Add yard elements, such as a yard block, track plan, and berth, to the yard map, each with just a few mouse clicks.

Edit a yard element on the map by resizing or moving it, or delete or copy yard elements.

Define yard stacks and sections for yard blocks.

Automatically generate all yard bin model components and then edit or configure them. SPARCS N4 draws bin entities on the map based on the geometries defined in the database.

Associate transfer zones with yard blocks, or delete and update transfer zone associations.

Add rail information, including a track plan and rail tracks.

Create berth blocks and berth markers.

Create and modify yard models separately from the one associated with the current yard.

Apply changes from the one yard model to the yard model associated with the owning (active) yard.

Additional Functionality: If you license one of the PrimeRoute Options

Advanced Berth Scheduling or the Expert Decking Option you can use Yard Editor to

define vertices and yard paths for your Yard Path Model.


The following displays a yard block being added or drawn over an imported image in Yard Editor:

Yard block being added (highlighted in light blue)

The following displays a yard block being edited or moved in Yard Editor:

Yard block being edited or moved (highlighted in dark blue while the configured yard blocks are orange)

Reporting

The ability to add any field in SPARCS N4 to a report using the metafield ID, including fields not available in a reportable entity.


A report analyzer tool that returns the count of synthetic fields, database-backed fields, and metafield IDs along with the report query and report output type in a separate window to identify if the report hydrates data. This enables you to test and edit report designs to receive better performance tradeoffs.

With this feature, you can define:

The operational scope of the data in the report, such as if a report displays data for a specific yard, terminal, group of terminals, or for all operations.

The filter criteria to determine the data included in the report output, such as if the report only covers export containers.

Any parameters to enable users to select additional reporting criteria when running the report. This enables you to produce multiple reports from just one report.

Multiple sorting rules to sort the data in the report.

The output type for the report, including PDF (Portable Document Format), RTF (Rich Text Format), CSV (Comma Separated Value file), TSV (Tab Separated Value file), or XLS (Excel Worksheet Format).

A schedule for SPARCS N4 to automatically run a report at specified times, such as scheduling a report to run daily or weekly.

Notifications to send the generated report output file(s) as email attachment(s) to specified recipients. In addition, you can specify the recipients that want to receive email notification when SPARCS N4 fails to generate a report.

Optional Functionality: With the Advanced Configuration, Customization, and Integration Option you can create your own business reportable entities to use to define specific reports.

Data Conversion

The Data Conversion feature provides an SNX tool for importing and exporting reference data in SPARCS N4 and a SPARCS data import tool to enable you to import legacy SPARCS or XPS data in SPARCS N4.

SNX is a family of APIs for interacting with SPARCS N4 based on XML documents. SPARCS N4 provides a user interface to enable you to import data from a legacy system into SPARCS N4 for data conversion at system implementation. The data you can import includes reference data, working data, and event history data for current and past containers, including their billable service events. You can import your legacy data into SPARCS N4 as many times as needed prior to go-live for testing and system verification. When importing data, the user interface displays the status of each record as the server processes it, and SPARCS N4 writes any failed records into a log file for easy review and re-importing.

In addition, SPARCS N4 provides a user interface to enable you to export base system data in the form of an XML text file, including the entire database, in one easy step. This enables you to easily create reference data for a test system or a system snapshot. In addition, you can export subsets of working data from various list views in SPARCS N4 into XML files.

The SPARCS data import tool facilitates transitions from a legacy SPARCS system to SPARCS N4, from an XPS client, or from a test system to a production system. This tool enables you to export data from a SPARCS or XPS client and import it into SPARCS N4 using an upgraded XPS client. With this tool, you can import the following data:

Allocations, including allocation filters, allocation groups, allocation ranges, and allocation weight groups

EC, including pools, POWs, CHEs, and CHE zones


Yard data, including stack notes, stack status, and stow factor filters

Radio Server users (EC users)

Color palette

Users and groups

Container filters

Recap formats

Expert Decking strategies and EC parameter values (for shared parameters)

Optional Functionality: With the Advanced EDI Foundation Option, you can export inventory data and import third-party EDI reference data.

Optional Functionality: With the SNX Option, you can automate SNX imports and exports to synchronize SPARCS N4 data with other foreign systems.

NEW: General Cargo

The new General Cargo Option provides a simple, fast, and efficient way to manipulate non-containerized cargo, such as break-bulk, rolling cargo, and bulk cargo. This Option enables you to view and track non-containerized cargo and perform actions, such as stuffing and striping cargo, manifesting cargo, and loading and discharging cargo from a carrier.

With this Option, you can:

Define reference data for cargo, such as commodities, special stow codes, hazardous placards, package types, product types, cargo damage types, hazardous goods, and subsidiary risks.

Define cargo details for a bill of lading item, such as the commodity, package type, package contents, reefer requirements, and more.

Manage cargo lots for each pile of cargo at a specific location or for each piece of cargo, and associate cargo lots with a bill of lading.

Manage holds and releases by the number of packages in a bill of lading item.

Receive and deliver cargo through a gate or load and discharge cargo from a vessel or train.

Optional Functionality: With the Advanced EDI Foundation Option Option, you can configure customs holds for a bill of lading using EDI. With the Billing Option, you can extract and bill for general cargo activities, services, and storage events. However, this does not include extracting and billing for cargo lot events.

The features in this Option includes:

Cargo Lot Management

Cargo Operations

Cargo Lot Management The Cargo Lot Management feature enables you to track cargo in three basic ways:

Bulk Cargo: Cargo is tracked by weight or volume, such as coal, wheat, and crude oil.


Quantified Cargo: Cargo is tracked by quantity. This is sometimes referred to as Pseudo Bulk Cargo. In this case, each piece of cargo does not have a unique identifier either because the identifier is unknown or because the pieces are too numerous and interchangeable; therefore, this type of cargo is tracked only by quantity.

Identified Cargo: Each piece of cargo is tracked by a known and unique identifier, such as the VIN number of a car.

With this feature you can:

Enter and manage full cargo lot details, such as the quantity manifested, cargo lot total weight, brand, model, color, export release number, and the planned position for a cargo lot.

Add cargo lots for cargo manufactured at the facility.

Record damages against a cargo lot.

Move a cargo lot to a new position.

Strip and stuff cargo.

Apply or release holds on cargo lots to prevent or allow cargo lot events, such as loading or unloading a cargo lot on a vessel.

Record service events against a cargo lot for reporting.

Manifest cargo lots to a container, vessel, or train.

Configure reports for cargo lot data.

Split cargo lots on a single bill of lading to multiple bills of lading to ease processing of bill of lading items, such as when a bill of lading belongs to multiple consignees and you want to split the cargo to manage delivery to each consignee separately.

View cargo lot details in various Inspectors, including the Unit Inspector, Train Inspector, Truck Visit Inspector, and Vessel Inspector.

In addition, use the Cargo Lot Inspector for quick and easy access to fully detailed cargo lot information, including the cargo lot ID, quantity, associated units for manifested cargo, manifested quantity, associated bill of lading information, associated bill of lading items, any recorded damages, any discrepancies, any associated holds or permissions, and the full cargo lot event history.

Optional Functionality: With the Service Order Management Option, you can create a service order to plan for services performed against cargo, such as stripping the contents of a container into one or more cargo lots.

Cargo Operations The Cargo Operations feature enables you to receive and deliver cargo through a gate or load and discharge cargo from a vessel or train.

With this feature, you can:

Configure gate forms to deliver and receive break-bulk cargo.

Configure validation rules for delivering and receiving cargo at the gate.

Record damages against cargo arriving or departing through a gate.

Deliver cargo lots out the gate or on a train using a delivery order for one or more bill of lading items on the same or different bills of lading.


Deliver break-bulk cargo out the gate using a bill of lading.

Optional Functionality: With the Service Order Management Option, you can also deliver break-bulk cargo using a service order. With the RDT Cargo Tracking Option, you can load or unload cargo on a vessel, train, or truck and inspect and record damages for cargo during all of these activities.

Container Freight Station

The Container Freight Station Option is designed for terminals that operate a Container Freight Station (CFS). This Option highly automates the stuffing and stripping of containers. This Option provides multiple cargo tracking, handling, and reporting functions that can improve the overall management of warehousing and container operations.

With this Option, you can:

Stuff/strip cargo to and from the warehouse into and out of containers.

Stuff/strip cargo directly to or from a truck into or out of containers.

Integrate CFS activities with work orders and billing systems.

Track cargo details by ID, VIN# , marks and numbers, unit ID, or BL quantity.

Configure reports for CFS, such as dock receipt/cargo tally sheets, stuff/strip activity, cargo shift summary, cargo remaining summary, CFS activity by vessel voyage, cargo stevedoring statement, cargo gate activity, and CFS activity by date range.

Optional Functionality: With the RDT Cargo Tracking Option, you can strip and stuff cargo using the Navis SPARCS N4 Mobile Cargo Inventory.

New: Data Model Extensions

The Data Model Extensions Option enables to you add features to SPARCS N4 that are not currently in the product. This extensibility allows you to build custom functionality in SPARCS N4 based on new tables and fields.

With this Option, you can add:

Dynamic entities for new entities that do not currently exist in SPARCS N4.

Dynamic fields for dynamic entities, such as a name or ID field.

Menu options, forms, and list views to enable users to create, edit, delete, and view dynamic entities.

Code extensions for new menu options, action menu options, and business logic for dynamic entities.

Dynamic flex fields for system entities, including system entities that do not have flex fields in SPARCS N4.


The following figure illustrates how dynamic and system entities and fields are related.

In addition, this Option provides the ability to:

Configure and run reports for dynamic entities and fields.

Purge system entities with dynamic flex fields.

Configure security to control user access to the data model extension functionality.

Import and export data model extensions, including dynamic entities and dynamic flex field definitions. This enables you to transfer a data model extension from a test system to a production system.

Prerequisites: Advanced Configuration, Customization, and Integration Option

Optional Functionality: With the SNX Option, you can import and export data derived from dynamic flex fields.

The features in this Option include:

Dynamic Entities

Dynamic Flex Fields

Security

Dynamic Entities

The Dynamic Entities feature enables you to define new entities in SPARCS N4. In addition, you can define new fields for these new entities called dynamic fields. Once added, the dynamic field appears in the Fields view where you can edit it as needed.


Define new entities, including the entity name, database table name for the entity, description, a short prefix used for the form column and field names, if it is enabled or not, and notes.

Define new fields for your new entities, including the field ID, database column name, type, and length.

Define default application field definitions, such as the field short name, long name, help text, max characters, group category, group ID, secured, and widget type.

SPARCS N4 supports the following types of dynamic fields:

String


Boolean

Long

Double

Timestamp

System delivered enumerated type, such as a vessel visit phase

In addition, SPARCS N4 supports the following foreign key relationships to and from system and dynamic entities:

Many to one

One to one

Dynamic Flex Fields

The Dynamic Flex Fields feature enables you to add a new field to a system entity in SPARCS N4, such as a unit.

You can use dynamic flex fields when:

You want to add a flex field to a system entity that does not have system flex fields, such as a shipper or agent.

You have used up all of the available system flex fields for a system entity and require more flex fields.

You want to create a foreign-key relation to another entity or a data type that does not have system flex fields.

Dynamic flex fields are not yet supported for the gate, EDI, or Inspectors in SPARCS N4. In addition, you cannot define whether a dynamic flex field is nullable, unique, or indexed.

Once created, dynamic flex fields are generally available in the framework for create, read, update, delete, and search operations.

Code Extensions

The Code Extensions feature is available with the Advanced Configuration, Customization, and Integration Option, which is a prerequisite for this Option. With this Option, the Code Extensions feature is extended to support code extensions for dynamic entities and fields, such as:

Defining action menu options for dynamic entities.

Defining business logic for dynamic entities that you can invoke when a user creates, edits, or deletes a dynamic entity.

Creating a dynamic custom list of values for dynamic fields.

Configuring the scoping of dynamic entities

Security

The Security feature provides dynamic privileges to enable you to control user access to add, edit, delete, view, and perform actions for dynamic entities. SPARCS N4 automatically generates the following privileges:

A top-level menu privilege for a new list view created for a dynamic entity.

Add, edit, delete, and view privileges for a new list view created for a dynamic entity.


A privilege for each custom action menu option created for a new list view for a dynamic entity.

New: Multi Lift

Time is money in the shipping industry, and one high profile constraint for shipping companies is how long a vessel is alongside at a container terminal. With all the emphasis in getting vessels in and out of terminals as quickly as possible, container terminals have garnered quite a bit of interest in increasing a smooth and efficient operation while the vessel is alongside. One tactic that terminals have begun using is the ability to discharge and load multiple containers at the same time. The Multi Lift Option allows you to automate and optimize quay crane multi-lift operations for straddle and truck sites.

Simply stated, using multi-lift quay cranes can provide:

Higher quay crane productivity, which equates to quicker vessel turn times.

Fewer quay crane trolleys.

The ability to maintain yard container handling equipment (CHE) productivity with fewer lifts.

Fewer CHE trips into the yard.

With the Multi Lift Option, you can also fully integrate twin, tandem, and quad lifts with SPARCS N4 advanced applications providing you with a tool that is consistent throughout your CHE operations.

Prerequisites: Requires the Equipment Control Option with ECN4, Expert Decking Option, either the PrimeRoute for Straddle Carriers or Terminal Tractors Option and for truck operations the Truck Control Option.

The features in this Option include:

Improved UI for Quay Crane Multi Lifts

Expanded Vessel Planning Functionality

ECN4 and SPARCS N4 Mobile Support for Multi Lifts

Maximum CHE Weight Support

Updated Move Schedule Engine

Improved UI for Quay Crane Multi Lifts To easily and quickly distinguish between multi-lift moves and other moves, this feature provides the following fields and indicators in XPS for multi lifts:

Lift Type field displays in the various list views to indicate the multi-lift type, such as single, twin, tandem, or quad for work instructions. In addition, you can use this field to search for containers by multi-lift type. This field is updated in real time, such as when a container is discharged, to reflect any changes that occur during the execution of a planned multi-lift move.

Lane field in various list views to indicate whether the truck uses the waterside or landside lane at the quay crane for tandem or quad multi-lifts.


Icons, such as a twin icon (underlined T), tandem icon (TD), and quad icon (Q), indicate the different multi-lift types for work queues. These icons display in work queues and in the EC Console when twin, tandem, or quad multi-lift moves exist.

Vertical bars between the planning dots for work instructions display to indicate twin, tandem, or quad lifting by a multi-lift quay crane.

In addition, when a hatch clerk discharges twin, tandem, or quad containers out of order, any previously planned containers that were not discharged as expected are abandoned until discharged. To highlight this state, XPS displays different indicators for these work instructions. For example, for an abandoned container that was previously planned as a twin discharge, XPS displays one broken vertical bar on the planning dot instead of the usual two vertical bars connecting the dot to the other planned twin container. When these abandoned containers are discharged, XPS updates the multi-lift type and re-draws the work instruction indicators accordingly.

The following illustrations display some of these indicators for multi-lift:

EC Console with points of work containing multi-lift work queues


Point of Work list with quad and twin work instructions

Point of Work list with tandem work instructions

Expanded Vessel Planning Functionality Vessel planning has been expanded to support Multi Lift. To make planning multi-lift moves easier, you can create PWPs to address tandem and quad quay lifts, and use Power tools for tandem and quad sequencing.

ECN4 and SPARCS N4 Mobile Support for Multi Lifts The ECN4 and SPARCS N4 Mobile Support for Multi Lifts feature provides multi-lift functionality and visibility for CHE operators and hatch clerks. With this feature:

Hatch clerks using the Hatch Clerk program can:

o Record tandem and quad loads and discharges.

o Assign two twin or tandem containers, or four quad containers, to a CHE at the same time.

o Create or break-up multi-lift moves.

CHE operators using an ECN4 Web CHE operator program are provided with additional information for multi-lift moves, such as:

o Indicators of the types of multi-lift moves that are being executed.

o The container number or CHE to pull up next to at the quay for tandem or quad loads.

o Water-side and land-side instructions for tandem-lift and quad-lift moves.

Optional Functionality: With the Advanced Configuration, Customization, and Integration Option you can add unit flex fields for tandem and quad containers in Hatch Clerk. This enables a hatch clerk to enter or edit data in unit flex fields when recording container loads.

Maximum CHE Weight Support This feature enables you to associate weight constraints and lift constraints for CHEs involved in multi-lift operations. This prevents a multi-lift quay crane or CHE from lifting tandem or quad containers that exceed the lift constraints of that crane or CHE. In addition, this provides valuable information to enable PrimeRoute to schedule and dispatch CHEs to the appropriate moves.


Updated Move Schedule Engine The Updated Move Schedule Engine feature provides enhanced functionality to enable PrimeRoute to schedule optimal yard movement of containers for multi-lift operations at the quay crane. PrimeRoute effectively manages yard CHEs and dispatches them accordingly. For example, PrimeRoute coordinates getting two trucks to the quay crane at the same time to support tandem and quad-lift loading.

New: Marine Telematics Solutions

Automated Vessel Load and Discharge

The Automated Vessel Load and Discharge Option enables ECN4 to process messages from Quay Crane Telemetry and OCR systems to record load, discharge, and shift-on-board events and simultaneously map them to business events in SPARCS N4. This Option is designed to be generic with a provided map to the APS message schema to accommodate future vendors. However, currently this Option supports only APS as the provider of the Quay Crane Telemetry and OCR system.

First ECN4 reads and processes the following incoming messages from the Quay Crane Telemetry and OCR system:

SpreaderStateStatus: Provides set and lift crane events. (CEDA)

CraneContainerImageEvent: Provides details about the container that has passed

through the OCR cameras. (CODC)

CraneToCHEHandOffEvent: Provides details about the CHE that the crane is either

lifting from or setting to. (CODM)

Then ECN4 translates each message into one of the following business events in SPARCS N4:

Vessel discharge

Vessel load

Shift on board

Shift on dock

The Quay Crane Telemetry and OCR systems also collect information about hatch cover moves and twist lock bin moves. However, these are not tracked in SPARCS N4 as business events.

In addition, ECN4 handles typical exceptions driven by incomplete information ensuring that the correct business event and all subsequent CHE events are sent for the resolved container ID.

Prerequisites: Equipment Control Option with ECN4

Whats new in Navis SPARCS N4 version 2.2NEW IN: System Options 15

NEW IN: System Options

Advanced Configuration, Customization, and Integration Option

Groovy Management To help Groovy developers facilitate writing Groovy code, this feature provides:

Documentation of the SPARCS N4 domain model and the published Java docs for all of the public SPARCS N4 APIs. This documentation is readily available from the SPARCS N4 user interface, if the user has the required privileges. The domain model documentation includes the SPARCS N4 entities with links showing their relationships. The Java docs consist of all of the SPARCS N4 public methods, including the entities, manager, business facades, and so on. This enables Groovy developers get the information they are looking for when writing Groovy code.

The ability to record the statistics of the code extensions to evaluate the Groovy code cost. This captures the Groovy cost across the whole process, not just for the user session.

A mechanism to compile the selected Groovy Plug-in(s) and display the status and any errors. This ensures that the modified Groovy Plug-ins are compatible with the SPARCS N4 system on which they are deployed.

In addition, SPARCS N4 provides a debugging tool that enables you to test and execute Groovy code on demand and displays any errors from executing Groovy code that require action. Once Groovy code is live, you can at any time easily disable all Groovy code execution in SPARCS N4 when trying to diagnose a problem that might be associated with Groovy code.

Configurable Reportable Entities

The Configurable Reportable Entities feature enables you to customize your own business reportable entities to use when creating report designs. Under the System Foundation II Option, SPARCS N4 provides a library of key business reportable entities allowing you to create reports based on one of these reportable entities. However, the Configurable Reportable Entities feature allows you to create very specific reports based on data that exists across more than one reportable entity or is not covered by the built-in reportable entities.


Add, edit, and delete custom reportable entities based on any SPARCS N4 database table, including joins and custom tables.

View all of the fields associated with both custom and built-in reportable entities.

Add custom fields to the both the custom and built-in reportable entities. Custom fields can include:

o An existing SPARCS N4 field that is not already in the reportable entity.

o A flex field.

o With the Data Model Extensions Option, a new field that you create.

Publish custom reportable entities when ready for use in creating report designs.

View and manage all of the custom and built-in reportable entities in one place.

Whats New in Navis SPARCS N4 version 2.2 16

Optional Functionality: With the SNX Option you can create export both custom and

built-in reportable entities using SNX.

NEW IN: Standard Options

Gate Option

Gate Configuration

Gate documents to print for a truck at a gate stage. You can configure gate documents for each type of gate transaction at each gate stage and an overall gate document for all of the transactions associated with a truck visit, as needed.

If you handle multi-trailer trucks at your gate, you can define chassis profiles for various chassis configurations and configure business rules to validate these chassis profiles. This enables SPARCS N4 to properly sequence the associated gate transactions, allowing for better customer service of multi-trailer trucks arriving at your gate.

Gate Lane Monitor You can quickly and easily view current and historical scanned data, including data sent

to SPARCS N4 in either the record-scan or create-truck-visit gate APIs, in the

Scan Sets view. A scan set is a collection of scanned data for a truck in a gate lane, such as the truck license number, scale weight, and any scanned container or chassis details. If configured and available, you can also view the current captured images in an external image viewer.

Appointments

Appointment Management You can flag certain appointment and truck visit appointment events, such creating, cancelling, or using an appointment, as billable. When these billable appointment events occur, SPARCS N4 stores them in the Chargeable Appointment Events view, where you can select them for invoicing.

Optional Functionality: With the Billing Option, you can also bill for appointment and truck visit appointment events, such as creating, cancelling, or using an appointment.

Billing Option

Invoicing

Set SPARCS N4 to round the invoice line items before computing the invoice total or compute and then round the invoice total.

Payments

Record payment for container charges by invoice line item or for the entire invoice.


Guarantees Option

Record and invoice guarantees for a container chargeable event by invoice line item or for the entire invoice.

Monitor

Gadget Configuration

Trucks In Yard: Displays the number of trucks in the yard by the number of gate transactions, including a truck status based on how long the truck has been in the yard.

Truck KPIs: Displays the trend of gate performance in the last 4 to 8 hours along with the current value of several inter-related gate and yard key performance indicators.

NEW IN: EDI

Advanced EDI Foundation

The following table lists the added EDI class, the supported EDI messages, and the provided XML schema files:

EDI Class EDI Message XML Schema File

RELEASE 350 (IN)

COREOR (IN)

CUSRES (IN)

release.xsd

EDI Configuration You can configure SPARCS N4 to automatically reprocess a failed inbound or outbound EDI job a specified number of times before SPARCS N4 considers the EDI job as failed.

In addition, you can add custom code via code extensions to an EDI session for SPARCS N4 to process when loading and posting the EDI session.

Optional Functionality:

With the Advanced Configuration, Customization, and Integration Option, you can add custom code via code extensions to an EDI session for SPARCS N4 to process when loading and posting the EDI session.

With the SNX Option, you can use SNX to import and export the code extensions for loading and posing an EDI session.

EDI Transaction Management When there are EDI batches with errors, you can cancel the batches that do not need to be fixed allowing you to easily view only the batches that need to be fixed.


NEW IN: Facility Planning and Control

Yard Planning and Control Option

Automated Yard Move Filters

The Automated Yard Move Filters feature can identify containers that need to be moved and schedule those moves automatically using the yard move filters that you configure. For example, you can configure a yard move filter to identify containers that have been damaged and are approved for repair, and to schedule those containers to be moved to the maintenance area. Yard move filters provide the ability to search the yard and automatically create work instructions for yard moves that will improve yard utilization.


Define the following for a yard move filter:

o A container filter criteria that must be met for the containers that are to be moved.

o The work queue where the generated plans are placed.

o The chassis type used to execute the yard moves.

o The logical block where the containers are planned.

Activate or de-activate yard move filters and set a cutoff limit to the number of plans automatically generated at one time.

Dedicate a separate XPS client machine to generate yard move filter plans, thereby keeping this additional load off of the XPS server.

Vessel Planning and Control

Vessel Preplanning

View already planned projections by the projection group or by container

NEW IN: Equipment Control

ECN4 performs the functions of communication and state management for all of the CHE operator programs. However, you can choose to use VMT functionality with either ECN4 or a radio server. For more information on the differences, see ECN4 vs Radio Server.

ECN4

Functionality to enable CHE operators and hatch clerks to merge actual empty containers with To Be Determined (TBD) units, with validation that you can customize to your needs

With the Vessel Hatch Clerk Option, you can support hatch clerk dispatch to internal trucks and hatch clerks can merge actual empty containers with To Be Determined (TBD) units.


With the Advanced Configuration, Customization, and Integration Option you can use code extensions to define specialized behaviors of certain CHE for the job lists and create custom sort and filter configurations for the jobs in a job list. You can also dynamically add, update, or delete a code extension to ECN4 without requiring a restart. This functionality is supported on both Windows and Unix systems.

The ability to configure Equipment Control to dispatch (single or twin) TBD units to straddle carriers in job step mode if the operator is not allowed to enter a container number due to labor rules.

For PDS-enabled CHEs, support for geodetic coordinates to integrate lifts and sets, from or to heaps, internal trucks using the Truck Control Option, and external trucks. In addition, if the operator is not allowed to enter a container number, ECN4 can sequentially display likely target container numbers to operators. Note: This requires Marine Telematics Solutions application software.

Additional job list functionality as follows:

o Functionality to enable CHE operators to place a container in a different location, other than the planned location, after selecting a job from a job list.

The ability to display your local language in the CHE's vehicle mounted terminal (VMT) screen and controller's workstation by configuring translation files. You can localize the text for buttons, options, instructions, field prompts, filter names, error messages, and more. In addition, for upgrades to SPARCS N4 you can use a third-party tool to easily compare translation files to see if new properties were introduced and to update these files accordingly.

The ability to open and view the VMT screen for a CHE operator in a browser window on an XPS client machine. In addition, you can configure XPS to launch a different tool for remote viewing instead of a browser window. The opened window displays all updates on the VMT screen in real time, regardless of whether the update is from the CHE operator or ECN4. There is no limit to the number of users that can open and view the same VMT screen for a CHE operator.

NEW IN: Radio Data Terminal Execution

This section describes the Radio Data Terminal Execution Options. These Options offer real-time monitoring and management of all equipment.

Gate Clerk

Record damages for bundled equipment.

Yard Inspection


Vessel Hatch Clerk

Record single and twin-lift loads for To Be Determined (TBD) units, thereby merging the actual empty container(s) being loaded with the planned TBD unit(s). TBD units are generic empty containers without a specific unit number.



Rail Clerk / Rail Inventory


RDT Cargo Tracking

The RDT Cargo Tracking Option enables a clerk to perform various gate, vessel, rail, and yard operations for cargo using the Navis SPARCS N4 Mobile Cargo Inventory.

With this Option, a clerk can:

Load or unload cargo on or off a truck that is associated with an active truck visit for a break-bulk gate transaction.

Load or discharge cargo to or from a vessel.

Load or discharge cargo on or off a train.

Inspect cargo located in the yard and update the marks or position of the cargo.

Identify cargo thereby creating an identified cargo lot from a quantified cargo lot.

Strip or stuff cargo from or to a container.

Record damages for cargo during any of these operations.

Prerequisites: General Cargo Option

NEW IN: Advanced Vessel

Advanced Berth Scheduler Option

Track multiple berths for a single vessel visit.

Calculate which vessel position results in the shortest driving distance for loading all containers that are in the yard.

Vessel AutoStow Option

Analyze the AutoStow results including explanations of the penalties applied by running AutoStow Solutions Explorer.

NEW IN: Advanced Rail

Rail AutoStow Option

Analyze the AutoStow results including debug information for container selection and/or position selection for each slot filled by running AutoStow Solutions Explorer.


NEW IN: Advanced Yard

Expert Decking

Configure the algorithm to factor in:

Desired turnover time, in days, based on the time the container enters the yard.

Row weight distribution, which attempts to distribute containers by weight class by putting light to heavy containers in the filling direction of the row.

PrimeRoute for Straddle Carriers

Dispatching from the Quay Lane The Dispatching from the Quay Lanes feature provides the ability for PrimeRoute to automatically dispatch containers that are stacked under the quay crane in an optimal order to straddle carriers in job list or job step mode. Instead of dispatching containers based on the discharge sequence, PrimeRoute dispatches the containers stacked under the quay by the lane and tier values, from waterside to landside, and from top tier to bottom tier. For example, PrimeRoute dispatches containers in lower lane numbers before containers in higher lane numbers. In addition, for containers stacked in the same lane, PrimeRoute dispatches containers stacked in higher tiers before containers in lower tiers.

If PrimeRoute has already dispatched a container under the quay crane and the quay crane stacks a new container on top of it, PrimeRoute automatically swaps the dispatched containers as needed. In addition, this feature supports twin lift and operations with and without a position detection system (PDS).

The following illustration displays an example of PrimeRoute swapping containers stacked under the quay crane:


PrimeRoute swap for containers discharged under the quay

In this example, container 1 is discharged first and is dispatched to a straddle carrier. However, when container 4 is discharged on top of container 1, PrimeRoute swaps the containers so that container 4 is dispatched first instead of container 1.

With this feature, straddle operators under the quay crane can also indicate when they lift a container other than the planned dispatched container. To do this, the straddle operator can either select the container they lifted from a list or enter the container number, depending on your labor rules. In addition, the straddle operator can toggle the list to display either single or twin containers.

If you use PDS-enabled straddle carriers, this feature also supports using the geodetic coordinates to sequentially display likely target container numbers to operators under the quay crane, in the event that they do not lift the planned dispatched container. In this case, you can also configure the proximity radius from a straddle carrier used to generate the list of other containers.

Optional Functionality: With the Vessel Hatch Clerk Option, the hatch clerk can record container discharge positions under the quay crane by lane and tier, supporting the full vessel discharge sequence.

PrimeRoute for Terminal Tractors Option

New to the PrimeRoute for Terminal Tractors Option

Instantly query and view an explanation of PrimeRoute dispatching decisions in real-time using a diagnostic tool in XPS.

View more detailed dispatching information in a log file.

The following illustrations display examples of an automated vessel load and discharge:


Automated vessel load

Automated vessel discharge

navis_sparcs_n4_v2_web

Documents

yard map

yard editor new

yard block

yard elements

yard perimeter

existing yard file

navis sparcs n4 version

compatible yard file