1. COMMANDseries Version 2 Roadmap and Product Forum
Eric Godsey
Product Development Manager
Ext. 1120

2. Session Objective
Give insight into the development process.
Review the progress that has been made to COMMANDseries Version 2 over the past year, including new features.
Outline the COMMANDseries Version 2 product direction for the future.
Provide an opportunity to discuss your ideas for the future of COMMANDseries Version 2.
Geared toward Executives, Managers, and Administrators responsible for the long term planning of your COMMANDseries installations.

3. Releasable state after every iteration
Our Process
Two week iterations
Releasable state after every iteration
Only schedule work in a release as we go
Auto Build and Auto Test every night
August Release/January Release
Schedule work as we go – this is important so we can be more responsive when unexpected work comes in

4. Current Product Release
COMMANDseries 2.28 SP3
Completed this past August
Supports:
Oracle 11g R2, 12c
SQL Server 2008, 2008 R2, 2012, 2014
Windows 7, Windows 8, Windows 8.1
Windows Server 2012, 2012 R2
Requires:
Microsoft .NET and 2013 C++ redistributable
COMMANDtrack 2.8 SP1
COMMANDfleet 2.17 SP4

5. Dropped support for Oracle 10.2 and SQL Server 2005

6. 2016 Feature Additions

7. Technical Feature Additions
“Upgrade” rather than re-install
Retains configuration files
Supports multiple regions
I showed this slide last year but it’s important, so incase you missed it.
2.26 and greater, the installation package upgrades previous installations now.

8. Increased Screen Sizes

9. FastReports Invoice Print

10. COMMANDbatch CPM cleanup
Better configuration editor when you enable a location (checks system and tells you which items have which problems on mixes and materials so you can fix them and not enable a location with batch code problems)
Unable to delete an item that is used as a batch code somewhere for a CPM enabled location
Unable to create an item that is used as an ad hoc batch code somewhere for a CPM enabled location

11. COMMANDbatch CPM cleanup
Only synchronize real batch code item rather than sold item (reduces traffic)
Increased dosage size field to handle instead

12. COMMANDbatch CPM Inventory cleanup
If an existing Material Receipt record is edited on CMDbatch, the adjustment is not transmitted to CMDseries.
If an existing Material Receipt record is deleted on CMDbatch, the adjustment is not transmitted to CMDseries.
If the on-hand-inventory quantity is adjusted on CMDbatch, the adjustment is not transmitted to CMDseries.
If the on-hand inventory quantity is set to a specific value on CMDbatch, the quantity or adjustment is not transmitted to CMDseries.

13. COMMANDqc integration
Order entry integrated to find mix submittal documents
Popup shows all approved/finalized documents for Customer/Project/Mix
Display selected PDF document

14. COMMANDqc integration

15. Integrated Mapping-FiveCubits

16. Integrated Mapping-FiveCubits
TrackIt is embedded inside of CT
Can display multiple signaling vendors inside TrackIt

17. Truck Unavailability

18. 3rd-party Order Mapping
No more freezing when mapping!
Google Chrome System Mechanic Active Care Software Lync Outlook Spotify Logitech Setpoint Symantec Endpoint Protection VMware View Agent 6.0 Adobe CEF Helper Office 365
Mapping orders to a map provided by a 3rd party vendor could hang if any of these other software were also running.
We researched and found a way to loosen our DDE communication to be more forgiving.

19. Rich Product Grid

20. Optimization – Driver Efficiency
Overview
For the Optimizer to become more efficient, additional information is needed to assign more efficient drivers to late or important loads. A driver’s efficiency should be assigned a value that is represented in CMDseries and passed to CM for assigning loads. A Driver’s Efficiency should compare his load completion times to order averages where the shipping plants were the same. ‘Mixing in the Yard’ and ‘To Job Travel Times’ will be used to provide a complete load time assessment each order. Order average times will be calculated for each plant in a given day. This will provide a baseline for driver comparison, producing a rolling Driver Efficiency calculation. CMDseries will provide CM a Driver Efficiency value that will be used to schedule drivers when each load’s lateness is determined by the Optimizer.

21. Contacts

22. Contacts
Primary record is shown in order entry and on customer inquiry display in receivables.

23. Order Modeling
Typical order modeling is for a new order not yet saved to see how it applies to all existing orders, this modeling is typically Yellow.
Modeling an existing order is displayed by itself and now in blue.
Only unticketed quantities are modeled. Order statuses are ignored.

24. Requested Start Time

27. Problem Recorder
Using Ctrl-Shift-R will toggle on and off Problem Steps Recorder.
Will create a zip file in the clients folder

28. Looking Forward

29. 2.29 to be released in January 2.30 next Summer
Looking Forward
2.28 SP3 is current release
2.29 to be released in January
2.30 next Summer
Continuing 8-4 plan
Each release will be supported by Service Packs on an as needed basis

30. Installation Improvements

31. Installation Improvements

32. Installation Improvements
Allow the user to stop processes crucial to the upgrade. These processes include:
uniface.exe
cmdnetw.exe
cmdstart.exe
CMDtrack or EXP tracking

33. Installation Improvements
Designing the website. It will show you:
The current COMMANDseries license on your system
The servers on your intranet in which CS is installed
CS version installed on those and the installation path
Release notes and download link for latest patch for version currently installed
Release notes and download link for newest released version

34. Installation Improvements

35. Apex Integration

36. Apex Integration
This approach accomplishes the following:
Eliminates double-entry of certain master data records: Customers, Credit Status, Items/Prices, and Projects (Sales Orders);
Provides a single place (COMMANDseries) to perform ticket prep, billing, and A/R. This reduces staff levels and training, and requires only one set of back office processes;
Provides a single interface point (COMMANDseries) to the upstream ERP or financial system, thus reducing errors, system maintenance, and program changes.

37. Apex Integration

38. Apex Integration

39. Multi-Drop (Milk Run)

40. Ability to assign leftover straight to new job
Multi-Drop (Milk Run)
Ability to schedule multiple tickets on a single truck to make multiple small load deliveries before returning to plant
Accomplish this through ‘Journey’ concept
Ability to assign leftover straight to new job

41. Multi-Drop (Milk Run)

42. New User Setup
Ability for admin to setup new users based on existing user settings
Can copy all lookup profiles, all privileges, price authority and preferences
Convenient one button click to copy everything

43. Optimization – Customer Performance

44. Online Help and User Guides Update

45. Questions Suggestions Improvements
Discussion
Questions Suggestions Improvements

46. Product Information
Don’t forget that you can get product information for all of our products from our customer portal:
Users.commandalkon.com
Password: Release
Sign up to receive release announcements for all products!

47. Please Complete Your Evaluation
Complete your evaluation online:
CS-001 COMMANDseries V2 Roadmap
All breakout session materials can be accessed at: marketing.commandalkon.com/cc2016/index.html
Thank You!