Last Mile/First Mile EVA Blueprint - Revision history

imported>Niveditasinghvi at 18:12, February 24, 2017

2017-02-24T18:12:42Z

@@ Line 183: / Line 183: @@
 | Vehicle software of all types
 | Yes
+| Tier 1 Supplier in auto industry
 |}
@@ Line 213: / Line 213: @@
 * '''Other software & services'''
-** Describe range of solutions.
+In addition to the autonomous software to operate the vehicle and route scheduling software, there are other categories of software that might be required.
 * '''System tester'''
 ** Test tracks, on-street testing…

imported>Niveditasinghvi at 21:57, February 17, 2017

2017-02-17T21:57:09Z

← Older revision		Revision as of 21:57, February 17, 2017
Line 188:		Line 188:

	* '''Routing software'''		* '''Routing software'''
	This includes software which manages and displays transit vehicle routes and schedules, stops, and possibly updates in real-time with information about delays, changes, and so on. There are a very large number of such transit apps both free and open source, as well as commercial software packages. They can be bundled with "fleet management" software, which includes information about the transit vehicles such as hours in operation, maintenance schedule, state of components, etc. It is recommended that the software provide and comply with an open ~~specification~~ for its routing and scheduling ~~feed~~. Relevant API specifications for transit include GTFS and GTFS-RT shown below.		This includes software which manages and displays transit vehicle routes and schedules, stops, and possibly updates in real-time with information about delays, changes, and so on. There are a very large number of such transit apps both free and open source, as well as commercial software packages. They can be bundled with "fleet management" software, which includes information about the transit vehicles such as hours in operation, maintenance schedule, state of components, etc. It is recommended that the software provide and comply with the industry-standard, widely-used open specifications for its routing and scheduling. Relevant API specifications for transit include GTFS and GTFS-RT shown below.

	{\| class="wikitable" style="color:darkblue;background-color:#B8CDD2;" cellpadding="10"		{\| class="wikitable" style="color:darkblue;background-color:#B8CDD2;" cellpadding="10"
Line 210:		Line 210:
	\|}		\|}

			A comprehensive look at transit specifications and apps is available at the [http://www.transitwiki.org/TransitWiki/index.php/General_Transit_Feed_Specification TransitWiki page on GTFS].

	* '''Other software & services'''		* '''Other software & services'''

imported>Niveditasinghvi at 21:40, February 17, 2017

2017-02-17T21:40:52Z

← Older revision		Revision as of 21:40, February 17, 2017
Line 188:		Line 188:

	* '''Routing software'''		* '''Routing software'''
	This includes software which manages and displays transit vehicle routes and schedules, stops, and possibly updates in real-time with information about delays, changes, and so on. There are a very large number of such transit apps both free and open source, as well as commercial software packages. They can be bundled with "fleet management" software, which includes information about the transit vehicles such as hours in operation, maintenance schedule, state of components, etc. It is recommended that the software provide an open specification for its routing and scheduling feed.		This includes software which manages and displays transit vehicle routes and schedules, stops, and possibly updates in real-time with information about delays, changes, and so on. There are a very large number of such transit apps both free and open source, as well as commercial software packages. They can be bundled with "fleet management" software, which includes information about the transit vehicles such as hours in operation, maintenance schedule, state of components, etc. It is recommended that the software provide and comply with an open specification for its routing and scheduling feed. Relevant API specifications for transit include GTFS and GTFS-RT shown below.

	{\| class="wikitable" style="color:darkblue;background-color:#B8CDD2;" cellpadding="10"		{\| class="wikitable" style="color:darkblue;background-color:#B8CDD2;" cellpadding="10"
	\|- style="text-align:center;"		\|- style="text-align:center;"
	! Feature		! Feature
	! ~~Company~~		! Description
	! ~~Open API?~~		! Standard/Specification
			! Use
	! Comments		! Comments
	\|- style="text-align:center;"		\|- style="text-align:center;"
	\| ~~Google~~ Transit Feed Specification (GTFS)		\| General Transit Feed Specification (GTFS)
	\| ~~Google~~		\| Specification to define static transit vehicle routes, schedules, stops
	\| Yes		\| Yes
	\| ~~Uploaded static route information can be displayed by any app that serves~~ GTFS ~~data~~		\| Many applications support GTFS. Google Transit Support allows you to upload your GTFS feed for display on Google Maps.
	\|- style="text-align:center;"		\|- style="text-align:center;"
	\| ~~Google~~ Transit Feed Specification Real Time (GTFS-RT)		\| General Transit Feed Specification Real Time (GTFS-RT)
	\| ~~Google~~		\| Dynamic update enhancement of the GTFS Specification for real-time data
	\| Yes		\| Yes
	\| ~~Allows dynamic~~ updates in real-time ~~for arrival times, delays, etc~~.		\| Google Transit Support allows you to upload GTFS-RT data for consumption by Google apps. Many applications support GTFS-RT to show transit updates in real-time.
			\|
	\|}		\|}

imported>Niveditasinghvi at 16:00, February 17, 2017

2017-02-17T16:00:17Z

← Older revision		Revision as of 16:00, February 17, 2017
Line 14:		Line 14:
	\|-		\|-
	\|Intro		\|Intro
	\|Nivedita Singhvi		\|style="text-align:center;" \|Nivedita Singhvi
	\|style="text-align:center;" \|Yes		\|style="text-align:center;" \| Yes
	\|		\|
	\|-		\|-
	\|Design Pilot Concept		\|Design Pilot Concept
	\|Daniel Frye		\|style="text-align:center;" \|Daniel Frye
	\|style="text-align:center;" \|Underway		\|style="text-align:center;" \| Underway
	\|		\|
	\|-		\|-
	\|Choose System Components		\|Choose System Components
	\|		\|style="text-align:center;" \| Nivedita Singhvi
	\|style="text-align:center;" \|~~Not yet~~		\|style="text-align:center;" \| Underway
	\|		\|
	\|-		\|-
	\|Build Out Partner Ecosystem		\|Build Out Partner Ecosystem
	\|		\|
	\|style="text-align:center;" \|Not yet		\|style="text-align:center;" \| Not yet
	\|		\|
	\|-		\|-
	\|Build, Integrate and Test		\|Build, Integrate and Test
	\|		\|
	\|style="text-align:center;" \|Not yet		\|style="text-align:center;" \| Not yet
	\|		\|
	\|-		\|-
	\|Operate Pilot & Learn		\|Operate Pilot & Learn
	\|		\|
	\|style="text-align:center;" \|Not yet		\|style="text-align:center;" \| Not yet
	\|		\|
	\|-		\|-
	\|Manage Optics and Community Perceptions		\|Manage Optics and Community Perceptions
	\|		\|
	\|style="text-align:center;" \|Not yet		\|style="text-align:center;" \| Not yet
	\|		\|
	\|-		\|-
	\|Municipality		\|Municipality
	\|		\|
	\|style="text-align:center;" \|Not yet		\|style="text-align:center;" \| Not yet
	\|		\|
	\|-		\|-
Line 59:		Line 59:
	\|-		\|-
	\|Summary		\|Summary
	\|Nivedita Singhvi		\|style="text-align:center;" \| Nivedita Singhvi
	\|style="text-align:center;" \|Not yet		\|style="text-align:center;" \| Not yet
	\|Needs other sections complete		\|Needs other sections complete
	\|}		\|}

imported>Niveditasinghvi at 15:56, February 17, 2017

2017-02-17T15:56:33Z

@@ Line 179: / Line 179: @@
 | Unknown
 | Oxford University offshoot
 |}
 * '''Routing software'''
-** What should this include?
+This includes software which manages and displays transit vehicle routes and schedules, stops, and possibly updates in real-time with information about delays, changes, and so on. There are a very large number of such transit apps both free and open source, as well as commercial software packages. They can be bundled with "fleet management" software, which includes information about the transit vehicles such as hours in operation, maintenance schedule, state of components, etc. It is recommended that the software provide an open specification for its routing and scheduling feed.
 * '''Other software & services'''
 ** Describe range of solutions.

imported>Niveditasinghvi at 07:15, February 16, 2017

2017-02-16T07:15:17Z

← Older revision		Revision as of 07:15, February 16, 2017
Line 171:		Line 171:
	\|- style="text-align:center;"		\|- style="text-align:center;"
	\| [http://www.meridianautonomous.com/ Meridian]		\| [http://www.meridianautonomous.com/ Meridian]
	\| Autonomous ~~Software~~ for electric vehicles		\| Autonomous software for electric vehicles of various types.
	\| Yes		\| Yes
	\|		\| Members from predecessor to the Navya AEV company
			\|- style="text-align:center;"
			\| [http://www.oxbotica.com/ Oxbotica]
			\| Autonomous software for electric vehicles of various types.
			\| Unknown
			\| Oxford University offshoot
	\|}		\|}


	** Describe range of solutions.
	* '''Routing software'''		* '''Routing software'''
	** What should this include?		** What should this include?

imported>Niveditasinghvi at 07:08, February 16, 2017

2017-02-16T07:08:02Z

@@ Line 162: / Line 162: @@
 * '''Autonomous software'''
 ** Describe range of solutions.
 * '''Routing software'''

imported>Niveditasinghvi at 17:51, February 11, 2017

2017-02-11T17:51:09Z

← Older revision		Revision as of 17:51, February 11, 2017
Line 141:		Line 141:
	\|[http://navya.tech/?lang=en Navya]		\|[http://navya.tech/?lang=en Navya]
	\|[http://navya.tech/?lang=en Navya Arma]		\|[http://navya.tech/?lang=en Navya Arma]
	\|~~Multi-passenger electric shuttle bus~~		\|Autonomous Electric Bus
	\|Upto 15		\|Upto 15
	\|Yes		\|Yes

imported>Niveditasinghvi at 17:33, February 11, 2017

2017-02-11T17:33:05Z

← Older revision		Revision as of 17:33, February 11, 2017
Line 138:		Line 138:
	!Autonomous or autonomous ready?		!Autonomous or autonomous ready?
	!Active pilots		!Active pilots
	~~!Link to Product page~~
	\|- style="text-align:center;"		\|- style="text-align:center;"
	\|[http://navya.tech/?lang=en Navya]		\|[http://navya.tech/?lang=en Navya]
	\|Arma		\|[http://navya.tech/?lang=en Navya Arma]
	\|Multi-passenger electric shuttle bus		\|Multi-passenger electric shuttle bus
	\|Upto 15		\|Upto 15
	\|Yes		\|Yes
	\|Yes		\|Yes
	~~\|[http://navya.tech/?lang=en Navya Arma]~~
	\|- style="text-align:center;"		\|- style="text-align:center;"
	\|Mobility Cubed		\|Mobility Cubed
	\|Mobility Cubed Bus		\|[http://www.mobilitycubed.net/ Mobility Cubed Bus]
	\|Electric Bus		\|Electric Bus
	\|Configurable		\|Configurable
	\|Not ~~standard~~		\|Not Standard
			\|Yes
			\|- style="text-align:center;"
			\|[https://localmotors.com/ Local Motors]
			\|[https://localmotors.com/olli/ Ollie]
			\|Self-Driving Electric Bus
			\|Configurable
			\|Yes
	\|Yes		\|Yes
	~~\|[http://www.mobilitycubed.net/ Mobility Cubed]~~
	\|}		\|}

imported>Niveditasinghvi at 17:26, February 11, 2017

2017-02-11T17:26:32Z

@@ Line 130: / Line 130: @@
 * '''Vehicle provider'''
 There is a significant range of EAVs already in the market with more coming.  Create a system to execute the vision and choose the right combination of technology. The table below will list applicable vehicle along with pointers to where more information can be found.  It is intended that all vehicles here are or can be electric only and are capable of being operated at least at Autonomous Level 3 or higher (there can be a driver-required mode, but there has to be a operational mode that has some level of Autonomous capability).
-{| class="wikitable sortable"
+{| class="wikitable" style="color:darkblue;background-color:#B8CDD2;" cellpadding="10"
 |-
 !Company Name
@@ Line 139: / Line 139: @@
 !Active pilots
 !Link to Product page
-!class="unsortable"|Photo
+|- style="text-align:center;"
-|-
+|[http://navya.tech/?lang=en Navya]
-|Example.com
+|Arma
-|Bus2Go
+|Multi-passenger electric shuttle bus
-|Multi-passenger luxury bus
+|Upto 15
-|Some
+|Yes
 |Yes
-|Winterfell & King's Landing
+|[http://www.mobilitycubed.net/ Mobility Cubed]
 |}