OPSCON Inc's

MoveItNow Suite

Feature Matrix

We like to think this suite is a unique piece of design work that fits the needs of a diverse transportation company.

Transportation Management:

	Functionality	Comments
Freight Load Building and Optimization
1.	Orders from the WMS system need to be downloaded to the load building software. Downloads of the orders must be accepted by the software with the options of doing it automatically or by manual intervention.	Import from WMS on a per order basis. There is no download involved.
2.	Errors from each download must be shown on an error report that may be displayed on a screen or printed by the planner. The planner must be able to correct the errors in the download file.	No download involved.
3.	Ability to select groups of orders by warehouse location, geographical location, business group, and routing group for creating shipments.	Search functions available
4.	Carrier equipment availability needs to be tracked for truckload shipments based on commitments with the carrier.	n/a
5.	Orders selected must be viewable for the planner. A maintenance function is needed to make adjustments to the orders in such fields as delivery date and time, zip code, parcel indicator, and other miscellaneous fields.
6.	There must be an identifier on orders containing items with hazardous materials.	No support for Hazardous Materials
7.	The TMS must have a freight load builder and optimizer to get the lowest transportation costs. It is necessary to dynamically build loads and have the ability to save the optimized results.	n/a
8.	The TMS must have the ability to generate the VICS Bill of Lading (BOL) numbers for the loads. The TMS must store the VICS BOL numbers with the load information and pass them with load information on the load tenders and to our WMS.	n/a
9.	9. Tariffs and rates for TL, LTL, CZAR, parcel and expedited rates, pool distribution rates, inter-modal rates, and accessorial charges must be maintainable manually and from other sources.	Tariff and misc charges are available. Costing is not.
10.	10. Parcel rating will not be incorporated into the optimization process.	n/a
11.	11. All files needed for planning and optimization need to be maintainable. The files include carriers, consignee, shipper, distribution points, geographic, zip codes, product, equipment, and driver information.	No support for Optimization. Automated planning based on City, Prov, Postal is available.
12.	12. The optimizer is required to have parameters that may be maintained in order to get the lowest cost of shipping for a batch of orders.	n/a
13.	13. Shuttle dock loads which are loads containing finished goods that come off the production lines at the manufacturing plant, branch transfers loads, and truckload customer orders need to be received by the TMS with a ‘to be approved’ status.	n/a
14.	14. Audit trail reports from the files that are maintained should be available on demand by the user.	See user defined reports
15.	15. All screens displayed must have a screen print option or utilize the windows print capability.	yes
16.	16. “What if” analysis and comparison capabilities are needed to fine-tune the loads and direct shipments.	n/a
17.	17. A function is needed to assign carriers, set up appointments, and print Shipment/load manifests. Pool carriers will be ranked by least cost.	no costing support.
18.	18. Carrier appointments, track and trace, and all status messages regarding the open shipment file need to be accessed via the web.	Appointments not supported
19.	19. The ability to print load tenders at detail and summary levels is needed with options to auto-tender by EDI, e-mail, or fax (Order of preference).
20.	20. Special instructions that may come with orders passed from our WMS to the TMS are to appear on the load tender document as well as the EDI 204 transaction	no special instructions in WMS
21.	21. The software must contain service standards that are maintainable through parameters. The parameters include consignee hours of operation, truck speed, delivery windows, drive times and unloading time per hundred weight (cwt.)
22.	22. All shipment and load information must be stored in the TMS for analysis and management reporting	yes
23.	23. The software must be able to upload shipments/orders files for use by our WMS system	yes, WMS can import dispatch orders
24.	24. Load confirmation (actuals) from the WMS system need to be downloaded to the TMS software. Downloads of the actuals must be accepted by the software with the options of doing it automatically or by manual intervention.
24.1	24.1 Confirmation is to be done at the item level
24.2	24.2 Weight variance is to be allowed at load confirmation
24.3	24.3 The ability to change the carrier at load confirmation is needed
25.	25. Loads need to be changed to a history status automatically, when the actuals are received by the TMS from the WMS, except for those with errors. If updates are only to SKU information – weight, case, cube, the load should be automatically updated and put into a history status without any manual intervention.	Orders are considered done by the TMS when marked as delivered.

Freight Bill Payment
1.	1. Freight Bill Payments module must have the ability to pay by the following methods:
1.1	1.1 Self Invoicing (Auto Payment)
1.2	1.2 Match and pay
1.3	1.3 Accessorial and other charges which are received after the original freight bill is vouchered

2.	2. Startup of carrier payments in match and pay mode with the capability to migrate by carrier to auto-pay

3.	3. Ability to add unplanned charges, such as accessorials, is necessary	yes

4.	4. Freight Bill Auditing and review is necessary for out of tolerance freight bills. The ability to set payment tolerance for a percentage and/or dollar amount is needed

5.	5. Reconciliation of freight payments is needed to show any bills that are outstanding, identify the payments that were under charged or over charged, or whether duplicate billing has been produced

6.	6. Freight Cost Allocation by weight will be needed to pro rate the charges based on the following splits - Load, Stops, Shipments, Orders and SKUs

7.	7. Ability to calculate and accumulate freight expense by specific general ledger account numbers and cost centers/departments

8.	8. Freight accruals will be generated by the package

9.	9. Freight Cost Analysis will be needed by the Traffic Department to see that we are shipping at the best cost that is available. Analysis reports needed are:
9.1	9.1 Freight Carrier Summary which shows Carrier Name/Number, Freight Charges by Charge Code, Weight, Number of Invoices, and Cost per Cwt., for the current month and year to date
9.2	9.2 Billing Analysis by Shipping Division, Sales Division, by Charge Code by Shipping Division showing within weight ranges, Number of Invoices, Avg. Invoice Dollars, Avg. Weight, Percent of Total Weight, and Avg. Cost per Cwt

10.	10. Freight Bill Cost per Cwt. which shows Branch, Product number, and cost per cwt. for various ranges of shipment cwt

11.	11. Ability to produce the Transportation Analysis report that summarizes Customer sales in dollars and weight, Customer freight costs, and Branch Transfer weight and freight costs. The report will have comparisons for the current month current year vs. current month last year, and current month YTD vs. current month last YTD	see End User Reports.

12.	12. Ability to add vendors to the Freight Payment system

Freight Accruals
1.	1. Hierarchy of freight cost allocation
1.1	1.1 Load
1.2	1.2 Stop
1.3	1.3 Shipment
1.4	1.4 WMS Order / Document Number
1.5	1.5 SKU

2.	2. Types of loads
2.1	2.1 Branch Transfers (1 stop or multiple stops)
2.2	2.2 Multi-stops
2.3	2.3 Each stop has a truckload portion of the allocated charge
2.4	2.4 Truckload cost + Pool cost = Total Allocated Cost
2.5	2.5 Single stop Customer loads
2.6	2.6 Single stop Pool loads
2.7	2.7 Multi-stop Pool loads
2.8	2.8 LTL Shipments combined into loads
2.9	2.9 Parcel Shipments

Carrier Claims
1.	1. Claims Management – Online Functions
1.1	1.1 Carrier Name or Number to Claims Cross-reference
1.2	1.2 Carrier Claims Display / Maintenance
1.2.1	1.2.1 Amending a Claim
1.2.2	1.2.2. Record an Acknowledgment
1.2.3	1.2.3 Record a Request for Document
1.2.4	1.2.4 Record That Documentation Was Sent
1.2.5	1.2.5 Print / Reprint a Claim
1.2.6	1.2.6 Enter / Remove a Special Status
1.2.7	1.2.7 Record a Partial Payment
1.2.8	1.2.8 Record a Full Payment
1.2.9	1.2.9 Close / Re-open a Claim
1.2.10	1.2.10 Add Manual Claim
1.2.11	1.2.11 Create a Claim

2.	2. Claim Items Display / Maintenance
2.1	2.1 Claims Aging by SCAC Code, Shipments, etc.
2.2	2.2 Text Information by Order No.
2.3	2.3 Generate Claim Ahead of Deduction on Customer Invoice

3.	3. Claims Management - Reports
3.1	3.1 Daily Additions Report
3.2	3.2 Daily Closed Carrier Claims Report
3.3	3.3 Daily Changed / Amended Carrier Claims Reports
3.4	3.4 Loss or Damage Claims Forms
3.5	3.5 Summary of Claims Printed Report
3.6	3.6 Open Carrier Claims Report
3.7	3.7 Summary of Unprocessed Carrier Claims
3.8	3.8 Carrier Claim Performance Report
3.9	3.9 Carrier Claims Dunning Letters
3.10	3.10 Carrier Claims Aging
3.11	3.11 Monthly Transactions Report
3.12	3.12 Monthly Claims Activity Recap

Generic Requirements
1.	1. Ability to download shipment, payment, and claims information to Excel or a report writer for inquiries, reports and analysis	yes

2.	2. Report writer, such as Crystal Reports, to produce the various reports/queries that are needed by management for analysis and decision making. The report writer will have a control limit for the number of records a user may access for queries and reports	yes. No control limits.

3.	3. Security for allowing personnel to do specific functions on the system. Only the transportation planners and supervisors should be able to plan and build loads using the load builder and optimizer. Only the freight payment person and the supervisor may pay the freight bills. Only an assigned person and a supervisor may perform the claims management functions. Only an assigned person and a supervisor may perform rate maintenance	Security by function for each user.

4.	4. Archiving and purge functions are required for all files whose records are no longer needed	Yes

Additional Features
1.	1. Rates - Accept rates from a diskette from a carrier to be loaded into the system
1.1	1.1 “What if “ analysis for analyzing rates	no
1.2	1.2 Rate shopping to get lowest cost carrier: LTL and TL	no
1.3	1.3 Copy capabilities must exist for the various types of tariffs	yes
1.4	1.4 Use existing tariff structures including discounts at the zip code level and/or weight ranges	yes
1.5	1.5 Standard look-ahead (deficit weight) rating is included in carrier contracts
1.6	1.6 Reasonability and validity checking for all carrier rates

2.	2. Accessorials
2.1	2.1 Accessorials by Carrier for all origins vs. individual origin tables
2.2	2.2 Accessorials by Customer	yes, see Rate Tables
2.3	2.3 Reporting capabilities from accessorial files; historical retention and reporting capabilities; graphing capabilities or capability to export to a spreadsheet program
2.4	2.4 Accessorial adjustments must be easily made with the ability to be copied across multiple carriers, especially ones like the fuel surcharges that have to be adjusted weekly	yes but no copy functions

3.	3. Carrier Information
3.1	3.1 Street and e-mail addresses are needed for each carrier, one of each type of address for dispatching, payments, claims, customer service, and sales representative	yes
3.2	3.2 Rank Carriers by performance, which will take precedence over the least cost carrier

4.	4. Export Files
4.1	4.1 Generate the freight expenses and accruals daily
4.2	4.2 Generate freight payments daily
4.3	4.3 Shipment information appended to daily to build a monthly file

5.	5. EDI
5.1	5.1 Ability to generate the following EDI transaction sets:
5.1.1	5.1.1 Load Tender transactions
5.1.2	5.1.2 Shipment Status transactions	yes

Warehouse Module:

Functionality		Availability	Comments
Receiving
	RF Receiving
	Receive against a PO		If you consider a Receiving Order the PO.
	ASN receiving
	Shipment-based receiving
	Shipment reconciliation
	Blind receipts
	Unknown receipts (no item or PO available)
	Damage identification on receipt
	Quality sampling and auditing		Manual process
	Receive against a generic license
	Receive and generate smart license
	Receive without a license
	Receive returns w/out a disposition
	Receive returns vs. a disposition
	Receive transfers without orders
	Prompt for open POs upon receipt
	Receivers
	Option to create receiver by PO		If you consider a Receiving Order the PO.
	Option to create receiver by load
	Option to pre-print receiving labels
	Check
	Reconcile PO lines w/receipts	M	add check to CountPcs
	Multiple operators on a single receipt
	Capture lot upon receipt
	RF display special instructions
	Attach graphic of exceptions
	RF capture user-defined license attributes (i.e., catch weight, owner)		RF system is not user adaptable.
	Verify/audit product in staging
	Reports
	Receiving exceptions
	Receiver list
	Productivity by user
	O/S/D report by PO by Load
	Vendor report card
	Open POs
	Yard and appointments		No support in current system
	Appointment scheduling
	Dock door assignments		updated via touch screen, scanner, or warehouse module.
	Project labor required to unload
	Ability to unload trailer w/out details
	Ability to RF-direct yard moves
	Ability to track demurrage by owner
	Ability to systematically assign docks
	Ability to systematically assign yard locations
	Full trailer visibility
	Trailer position in yard or dock	M	in dock only
	Trailer contents
	Pending trailer moves
Quality Control
	QC status
	License plate holds in non-QC location
	Hold and release by item
	Hold and release by lot
	Hold and release by location
	Reports
	QC Inventory visibility
	Vendor performance statistics
Put-away
	Select best location based upon user-defined rules
	Allow user to override
	Record overrides in exception log
	Put-away at the multiple units of measure
	System directs second put-away after override
	Put-away
	To quality control		Only if there is a location identified as Quality Control. Otherwise, manual quarantine assignment.
	To random storage
	To forward pick - if open replenishment
	To staging
	Cross-dock receipt to single order
	Cross-dock receipt to multiple orders
	To returns by vendor class
	Storage logic association to UOM
	Ability to split a single license plate receipt between replenishment and put-away		Not unless shipping item is split into multiple items
	Ability to store by owner
Location Mapping
	Location mapping
	Zones
	Special requirements (e.g. freezer)
	Mapping of acceptable vehicles by zone
	Configurable forward pick
	Multiple forward picks per item
	Ability to relieve inventory based upon merchandise verification to a certain location type
	Ability to define aisle contention criteria by vehicle
	Ability to have a location associated to multiple zones
	Reports
	Productivity by user
	Full location report		see "Reports \| Location Usage"
	Empty location report		see "Reports \| Location Usage"
	Warehouse location utilization report
Integrated WMS Slotting
	Slotting based on historical information
	Slotting based on forecasted information		No support for forecasting.
	Provides visibility to exception conditions		No support for exceptions.
	Creates move transactions based upon review
	Alters storage/pick/repl. logic based on re-slotting
	Graphical historical analysis
Picking
	Planning
	Create waves through pre-defined criteria		Waves not supported by current system.
	Accept pre-determined waves via download		Waves not supported by current system.
	Automatically build waves based on rules		Waves not supported by current system.
	Manually override priority of an order		No support for order priority.
	Ability to cartonize on order import		Cartonization/Import are not supported.
	Ability to pre-manifest pick containers		Manifests drive the scanners.
	Ability to include orders in waves		Waves not supported by current system.
	Ability to include order lines in waves		Waves not supported by current system.
	Ability to include order line quantities in waves		Waves not supported by current system.
	Ability to wave for specific trailer sizes		Waves not supported by current system.
	Ability to define reservation rules by customer		No support for reservation rules.
	Ability to calculate metrics on simulated wave		Waves not supported by current system.
	Ability to release waves by pick type (i.e., pallets first)		Waves not supported by current system.
	Ability to release waves by zone		Waves not supported by current system.
	Ability to auto-create work orders for wave shortages upon release		Waves not supported by current system.
	Ability to wave by pick method (i.e., batch pick)		Waves not supported by current system.
	Ability to wave by owner		Waves not supported by current system.
	Kitting		Kitting not supported by current system.
	Bill of material (BOM) capability
	Kits exploded during release
	Directed assembly
	Multi-level BOM support
	Ability to backflush consumed parts
	Ability to identify scrap
	Ability to un-kit
	Ability to track WIP in assembly
	Ability to associate cost to assembly
	Ability to request kitting from an RF terminal
	Monitor the progress of a wave		Waves not supported by current system.
	Workload monitoring by wave by order by item
	Visibility of required wave replenishments
	Calculations of remaining time by wave
	Calculations of new work vs. existing work
	Replenishment		Replenishment not supported by current system.
	Created by min/max
	Created based upon released orders
	Created based upon day's demand
	Created via RF request
	Replenishment picks in reverse put-away sequence
	Support cascading replenishments
	Ability to hold demand-based replenishments
	Pick work queues held until replenishment work done
	Stock rotation
	User-configurable rotation rules
	FIFO
	LIFO
	FEFO		Add "Expiration" to WHSE_INVENTORY
	LEFO		Add "Expiration" to WHSE_INVENTORY
	Select stock by lot number		S/N and ControlNo are automatic on WSO.
	Customer-specific rules
	Pick option
	Discrete order picking
	Batch picking (multiple orders per picker, separated at pick location)
	Pick and pass across zones
	Bulk picking (multiple orders per picker, separated at pack or conveyor/sort)
	Configurable number of pickers per order		limited by scanning hardware/people
	Equipment-based picking
	Zoned picking
	Wave picking
	Label picking
	Use combination of the above options on same order
	Picking approach
	RF-directed		use the Shipping Order's Pick Slip.
	Pick confirm by exception on PC
	Pick to list
	Pick by label
	Display special picking instructions
	Honor item mixing rules (i.e., haz mat)
	Ability to dynamically change pick transaction priorities
	Unpick option	M	add to scanner
	Pick sequencing
	In location flow
	In user-defined flow		Shipping Order's Pieces list defines the order on the Pick Slip.
	Honoring aisle contention
Packing/Shipping
	Cartonization
	Determine optimal carton size		Cartonization not supported.
	Determine optimal carton contents		Cartonization not supported.
	Graphically display carton packing orientations		Cartonization not supported.
	Support system-directed packing
	Display special packing instructions
	Loading
	Direct loading regardless of order continuity
	Direct truck loading by order integrity
	Direct loading by route/stop integrity
	Parcel manifesting
	Support for all major domestic carriers, LTL and generic carriers		Parcel Manifesting not supported.
	Support for major international carriers		Parcel Manifesting not supported.
	Manage complex export documentation such as shipper's export declaration, commercial invoices, denied party screening and harmonization codes		Parcel Manifesting not supported.
	Other support (list)		Parcel Manifesting not supported.
	Print compliant and custom labels		Parcel Manifesting not supported.
	Rate shopping		Parcel Manifesting not supported.
	Support for bundling		Parcel Manifesting not supported.
	Support for LTL rating		Parcel Manifesting not supported.
	Support online carrier communications		Parcel Manifesting not supported.
	Support for 100,000+ parcels/day/site		Parcel Manifesting not supported.
	Pre-manifesting support		Parcel Manifesting not supported.
	Post-manifesting support		Parcel Manifesting not supported.
	Support for zone skipping		Parcel Manifesting not supported.
	Reports
	VICS standard bill of lading		Report design
	Packing lists		Use Shipping Order as a Packing List
	Customer-specific paperwork		Report design
	Hazardous material manifest		Hazardous material not supported.
	International documentation		Report design
	Unship option
Other Functions
	Warehouse definition
	Support multiple warehouses on single application
	Support facility-specific item master		Presently using customer centric item master
	Cycle count		by Customer, by Product handled
	Generate counts through errors
	Generate counts by A/B/C
	Download counts from host		no host to download from
	Create counts by ranges of items, locations and price
	Opportunistic cycle count during picking
	Value-added services
	Configurable categories
	Configurable messaging
	Available for all warehouse processes (i.e., receiving, picking, shipping, etc.)
	Integrated alerts and messaging		only orders from Dispatch module support messaging.
	E-mail alerts/messages
	Pager alerts/messages		No integrated pager support.
	Fax alerts/messages		No integrated fax support.
	Create XML/FTP messages
	Built-in escalation profiles		Not supported
	Built-in resolution strategies		Not supported
	Ability to automatically change process flow upon exceptions		Not supported
	Wireless PDAs
	Support full WMS application UI on PDA
	Support full WMS RF function on PDA
	Integrated delivery confirmation		Delivery details not tracked by Warehouse. See Dispatch module instead.
	Support batch delivery confirmation
	Support RF delivery confirmation
	Support pick-ups (i.e., returns)
	Driver and odometer logging
	Signature capture
	Detailed audit trail
	Reason codes for missed deliveries
	Interleaving
	Interleave any directed task
	Interleave by priority
	Interleave by proximity
	Labor Management
	Static standards by function
	Dynamic standards by function
	Applying actuals against calculated and static standards
	Applying KPIs to transactional data
	Integrated activity-based costing
	Costing by owner	M	Report design & Costing configuration
	Costing by transactions by owner	M	Report design & Costing configuration
	Costing by space by owner	M	Report design & Costing configuration
	Costing by time by owner
	Ability to calculate costing based on combinations of above
	Audit history		for core functions
	Timestamp start/stop for all tasks		finish time available for Shipping and Receiving orders.
	Visibility and reporting by employee(s)		Report & query design
	Visibility and reporting by transaction(s)		Report design
	Equipment maintenance visibility		Equipment not tracked via Warehouse
	Visibility to required maintenance by vehicle
	Alerts based on required vehicle maintenance
	RF Messaging		RF Messaging not supported
	Ability to send RF message to specific end-user
	Ability to send RF message to specific group
	Ability for recipient to respond to message
RFID
	Does the system support RFID technology?
	What technology is integrated into your system to support RFID?
	What manufacturers of RFID tags, readers and printers do you support?
	Can your RFID capabilities be demonstrated?
	How does the system accommodate changes in RFID tag data, such as data elements, structures and identifiers?
	Can the same operations be performed by RFID that are already being performed with bar codes?
	What additional modifications are needed to 'swap' bar code input to RFID input?
	Can the RFID equipment be used in both hand-held and fixed applications?
	Does your product meet the RFID requirements set by Wal-Mart and the DoD?
	How will your product meet future specifications and requirements of RFID? (i.e., How can your product be modified to comply with new mandates and support new RFID standards?)
	Hardware restrictions
	Are you a member of EPCglobal?
	Do you provide RFID solutions that cover manufacturing?
	Do you provide RFID solutions for asset tracking?
	How many years have you been involved in providing true data collection services and expertise? (i.e., there are significant, fundamental differences in the way RFID data is collected and managed vs. traditional bar code methods in warehouse environments)
Manufacturing
	Manufacturing materials management
	Line replenishment picking
	Multiple bin or kanban replenishment
	Receiving finished goods or subassemblies from production operations
	Visibility to work-in-process inventory
	Manufacturing labor
	Labor assignment to jobs or work orders
	Labor allocation across multiple jobs or work orders
	Management of labor for groups/crews
	Extraction of breaks and lunches from labor assignment
	Manufacturing execution
	Touch screen data capture for the shop floor environments (paperless manufacturing)
	Tracking lot or serial number genealogy through production operations
	Shop floor visibility to work instructions or CAD drawings
	Integration with factory automation or shop floor material handling systems

These tables are based on the TMS and WMS RFP templates from HighJump Software.

last modified: Sunday, May 11, 2008 14:04