Vehicle Team Roadmap (with tentative timings)

M200 Support Deadlines

Timeline of known requirements for M200 feature support

NYC 1900MHz turndown - Deadline Met!

03/17/2014

Needs v135 (t-mobile support)
No vehicles should need replacement units. Sending as a backstop.
Turn down is 3/27 - deadline is for NYC to have units in hand.

Firmware for Initial Vienna Rollout - Deadline Met!

04/21/2014

Tentative. Confirming with Olly & Dirk.

Needs v136 for OBB support.

Fuel Level Support for One Way

07/31/2014

approximate deadline. Synchronized to support Beta 2 in ZipCity.

Needs v137 for fuel level support

M200

Wyless SIM support - DONE!

01/15/2014 - 02/07/2014

v135

Finalize Vienna/OBB Support - DONE!

01/15/2014 - 02/28/2014

Resolve bugs found in testing, work into release.

v136.

v135 Testing (QE) - DONE!

02/10/2014 - 03/01/2014

v135 Code Complete - DONE!

02/10/2014

v135 Rollout ready - DONE!

03/01/2014

Rental Mode (exit on scan in) - DONE!

03/10/2014 - 03/21/2014

Refinement to exit Rental Mode on scan in for known res.

Tentative v136

CONTINGENT ON AVAILABLE CODE SPACE

v136 code complete - DONE!

03/21/2014

v136 Testing (QE) - DONE!

03/24/2014 - 04/14/2014

v136 Rollout Ready - DONE!

04/14/2014

UK/EU SIM Support (tentative start) - NLN

05/01/2014

Support for SIM provider other than Wireless Logic

Tentative

All WL contracts being renegotiated. No longer needed.

GPS reporting changes

Approx. 05/12/2014 - 06/06/2014

One Way would like vehicle GPS data to be transmitted on each ignition off event.

Item includes verification of POC work.

to be included in v137

Read Honda Fit Fuel Level

05/14/2014 - 06/06/2014

CONTINGENT ON AVAILABLE CODE SPACE

Update - bumped due to lack of code space. May re-eval and reschedule as needed.

Re-evaled and prioritized. This is for basic fuel reporting with the M200 with basic VServer/DB support and display. Additional work will be needed to build this out.

Scheduled for inclusion in v137

Develop M200 Sunset plan

06/09/2014

v137 Code Complete

07/03/2014

Tentative scheduling

v137 QE Testing

07/07/2014 - 07/25/2014

Tentative scheduling

v137 Release Ready

07/25/2014

Tentative date

Australia SIM Support (tentative)

08/15/2014

Turkey Support (tentative)

08/15/2014

Next Gen Support Deadlines

Need OBD-II Provider

07/15/2014

Need OBD-II provider for v1 support.

Mar 1 ideal
Mar 15 absolute drop dead

Revised to 7/15 to match movement in rollout date

Rollout Support

11/03/2014 - 11/28/2014

Next Gen TCU Rollout

11/03/2014

Next Gen TCU

Bench & Test Vehicle tests

01/15/2014 - Approx. 06/30/2014

M200 Funct. Port and Testing (Iterating with bench testing)

01/15/2014 - Approx. 06/30/2014

Steve and Sara on dev. Misha and Jim (et. al.) on test.

Try to get Karl on this... want to do a clean implementation of this rather than just replicate PIC state machine code.

Ongoing for test/dev iteration and refintement

Power On Self Test (POST) - DONE

02/01/2014 - 03/01/2014

Sarah working on this. Estimates completion before end of Q1.

Logging (to local storage) - Done!

02/10/2014 - 03/31/2014

Approx 1 mo. effort but aiming to complete before Apr 1.

Sara

Engage QE on KITT Test Plan - Done!

02/17/2014

Assigned to Jim, Dick and Sarah.

Engagement is ongoing

Start planning Field Trial Program - DONE!

03/03/2014

Need

-ops support

-plan org and communication for MSA's and fleet
-cars

Assigned to Jim

This item is done but ongoing support and planning will be needed.

Basic FOTA - DONE!

04/21/2014 - 05/16/2014

Logging (to FTP) - DONE!

05/01/2014

TENTATIVE for v2

Contingent upon v2 spec meeting

  • Completed in v1 for employee trials

OBD-II (VServer) - Phase 1

05/05/2014 - 06/06/2014

VServer/DB components for vehicle diagnostic data.

Preliminary work for One Way Fuel data

OBD-II (protocols) - Phase 1

05/05/2014 - 06/06/2014

Build support for querying device.

Phase 1 is to support Fuel data for One Way

ODB-II (KITT hardware) - DONE!

05/05/2014 - 05/16/2014

hardware integration work for OBD-II support

TCU Field Trials (~10 production cars)

06/02/2014 - Approx. 07/31/2014

Starting with employee trial with 2 cars and increasing as we get more confident.

Spec VServer needs for v1

06/03/2014

Initial meeting to determine revision needs for v1 rollout. Should happen after some initial field testing or bench load tests.

Manufacturer Test (tentative dates)

06/16/2014 - 08/15/2014

Contract work by Etherios with Sarah validating. Awaiting contract details for work.

On hold at Etherios. Pushing out.

VServer Testing & Modification for v1 Rollout

06/16/2014 - 08/15/2014

Placeholder for VServer testing and fixes needed to support initial KITT rollout.

System Scalability (by # cars)
Process optimization (i.e. car notification scheme)
Version numbering constraint (protocol issue, difficult but may be able to punt)
Issues with current DB connection pool system (ensure connections are not abandoned).

OBD-II (VServer)

Approx. 07/07/2014 - Approx. 07/25/2014

VServer/DB components for vehicle diagnostic data.

Second Phase work to add more data values beyond fuel

OBD-II (3rd Party Hardware) - Tentative

07/07/2014 - 07/18/2014

Test integration with 3rd party OBD-II hardware device.

Dependent upon our final OBD-II strategy and having a partner for this. May not be required if we do not use 3rd party hardware for this

OBD-II (Protocols)

07/07/2014 - 07/25/2014

Second phase work to support additional data values.

MVP is to properly read VIN, DTCs, Fuel Level and Odometer)

Steve on dev

Modem Status

08/04/2014 - 08/15/2014

enable read/report of network connect failure state in TCU modem (support future OOC work)

Adv. FOTA

08/04/2014 - 10/06/2014

VServer edit to handle M200/KITT revisions
VServer support build out
Need Prod FTP svr
~2mo. effort
Start date tentative

Steve on dev

Pushing out until after field trial.

Start Rollout Planning

09/01/2014

Determine initial markets/volumes, start communicating with fleets.

Need infleet model list!

Date revised to match new rollout date

Assigned to Jim

Revise v2 Spec

09/15/2014

Meeting to flesh out priorities and scope

Tentative date

Spec VServer needs for v2

11/14/2014

Meeting to outline VServer revisions following initial rollout. Should incorporate all pre-rollout testing and initial rollout results.

Toggle Card Security (FW-based)

11/14/2014

TENTATIVE for v2

Contingent upon v2 spec meeting

Improved Traka Support

11/14/2014

TENTATIVE for v2

Contingent upon v2 spec meeting

Further OBD-II support (Tire Pressure)

11/14/2014

TENTATIVE for v2

Contingent upon v2 spec meeting

Windshield unit support

11/14/2014

TENTATIVE for v2

Contingent upon v2 spec meeting

OBD-II Data integration support

11/14/2014

TENTATIVE for v2

Contingent upon v2 spec meeting

Accelerometer applications

11/14/2014

Still need definition on these.

TENTATIVE for v2

Contingent upon v2 spec meeting

VServer Updates

11/14/2014

scalability support. See v1 VServer item.

TENTATIVE for v2

Contingent upon v2 spec meeting

LRD Support

11/14/2014

TENTATIVE for v2

Contingent upon v2 spec meeting

Firmware Platform Refinements

11/14/2014

Restructuring of firmware code - if we can't fit this in to v1

TENTATIVE for v2

Contingent upon v2 spec meeting

Out of Comms Refinements

11/14/2014

Refine poor comms situations
-Possible to distinguish poor comms from no comms? Can we use modem signal strength metrics?

  • Can we send signal strength on keep alive and status messages? Develop our own coverage map?

Admin/DB

Revise Permissions for Vehicle Firmware Updates

05/26/2014 - 06/06/2014

Need to find resource and scope

Applies mostly to M200 firmware update process

Want to enable to for Vehicle Engineering, Fleet Ops Managers (?)

Doing this for V. Engineering. TCS is doing dev work.

Firmware Update Tool Revision

06/13/2014

Modification to avoid cars in Rental Mode.

Need to find resources for this.

Can depreciate when M200 update process is no longer needed

Vehicle Config Page: GPS location UX - DONE!

07/14/2014

Need to revise interface for requesting a GPS location from the vehicle AND for displaying this info.

May be done as part of v1 KITT support work. (Sara)

Vehicle Config Page: page re-org

08/04/2014

Revise/organize page data into items useful for MSA's and that useful for engineering/ops

Revise page permissions based on reorganization

Need to find resource, scope and prioritize

Vehicle History: Usage Update History

11/17/2014

Vehicle's report usage updates throughout reservation. These updates should be displayed on the vehicle history page in addition to the final reservation usage (currently displayed)

Firmware support exists. Need to find resource, scope UI changes and prioritize.

Cleaner Usage Tracking

11/17/2014

Allow reporting based on existing scan data for cleaning reservations and allow

Likely an integration on an existing cleaner activity tracking page

Quite possible doesn't belong to Vehicle.