The National Academies Press

Currently Skimming:

Pages 99-115

The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.

From page 99... ... 99 Detailed Specification Description A P P E N D I X D This appendix presents the proposed specification for demand-responsive transportation transactional data. A brief introduction to the overall approach is presented first; this approach centers around the concept of "telegrams," which are messages sent between entities. Read the entire page →
From page 100... ... 100 Development of Transactional Data Specifications for Demand-Responsive Transportation Each time information crosses a line in Figure D-1, a telegram must be sent containing the data necessary to advance the transaction to the next step. Since some telegrams confirm the receipt of information, this means the transactional flow is not necessarily one-directional as Figure D-1 would suggest (from planning through completion and payment) Read the entire page →
From page 101... ... Detailed Specification Description 101 The functional needs are specified in terms of data elements that describe a specific situation, as in Figure D-3. The collective set of functional processes involved and the data describing each process define the DRT trip use case. Read the entire page →
From page 102... ... 102 Development of Transactional Data Specifications for Demand-Responsive Transportation Telegram 1A Request a Trip Provider VehicleOrdering Client Telegram Flow Telegram 1B Trip Request Response Telegram 2B Confirm Trip Scheduled Telegram 2BB Vehicle Confirmation Telegram 3A Vehicle Trip Task Telegram 4A Completed Trip Data Telegram 2A Order Confirmation Telegram 2A1 Customer Information Telegram 3B Confirm Trip Task Telegram 5 Vehicle Current Status Telegram 4B Confirm Trip Data Received and Payment Status Figure D-4. Telegram flow. Read the entire page →
From page 103... ... Detailed Specification Description 103 Telegram 1:A – Request a Trip The first step in most transactions is to request a trip. The trip could be requested directly by the customer, or it might be requested by an organization on their behalf (such as a human service agency or healthcare provider) Read the entire page →
From page 104... ... 104 Development of Transactional Data Specifications for Demand-Responsive Transportation Telegram 1:B – Trip Request/Response The second step is to confirm the trip. The next telegram is the trip request/response or acknowledgment that would be sent from a provider to the ordering client to confirm that the provider can fulfill the needs requested in Telegram 1:A. Read the entire page →
From page 105... ... Detailed Specification Description 105 Telegram 2:A – Order Confirmation The next step is that the client system confirms the trip and sends a trip ticket ID. The ordering client sends Telegram 2:A to the chosen provider or providers to confirm additional details for the selected trip. Read the entire page →
From page 106... ... 106 Development of Transactional Data Specifications for Demand-Responsive Transportation Telegram 2:A:1 – Customer Information The next, nonmandatory step is that the ordering client provides additional details about the customer's trip. This is basically the same functionality as Telegram 2:A, but with customer information added so the provider can update the customer's information in their system. Read the entire page →
From page 107... ... Detailed Specification Description 107 Telegram 2:B – Confirm Trip Scheduled The next step is confirmation of the order details. Regardless of whether the ordering client sends information in Telegram 2:A:1, the provider needs to confirm information contained in Telegram 2:A. Read the entire page →
From page 108... ... 108 Development of Transactional Data Specifications for Demand-Responsive Transportation Telegram 2:BB – Vehicle Confirmation If special needs were communicated in Telegram 2:A:1, the next step is to confirm those special needs. For the special needs that could have been communicated in Telegram 2:A:1, Telegram 2:BB is the appropriate response confirming the features of the provider (vehicle and driver) Read the entire page →
From page 109... ... Detailed Specification Description 109 Telegram 3:A – Vehicle Trip Task At this point, the provider has confirmed that the trip will take place to the ordering client. This trip now needs to be dispatched. Read the entire page →
From page 110... ... 110 Development of Transactional Data Specifications for Demand-Responsive Transportation Telegram 3:B – Confirm Trip Task The next step is for the transportation service provider to confirm that the trip has been delivered. In response to Telegram 3:A, the transportation service provider's vehicle application (that is, the in-vehicle device and software that receives orders and displays the trip manifest) Read the entire page →
From page 111... ... Detailed Specification Description 111 Telegram 4:A – Completed Trip Data The next step is that the transportation service provider sends trip information to the ordering client. As soon as the service provider receives Telegram 3:B from the vehicle indicating the trip was completed, the provider can send information pertaining to the completed order to the initial ordering client as Telegram 4:A. Read the entire page →
From page 112... ... 112 Development of Transactional Data Specifications for Demand-Responsive Transportation Telegram 4:B – Confirm Trip Data Received and Payment Status The next step is that the ordering client confirms receipt of completed trip details. The ordering client then confirms that the details of the completed trip were received for that trip ticket and whether the payment was completed (the ordering client pays the provider) Read the entire page →
From page 113... ... Detailed Specification Description 113 Telegram 5 – Vehicle Current Status The final, optional step is that the information is sent from the vehicle to the provider for reporting purposes. Finally, the specifications could define a telegram whereby the vehicle sends information to the service provider in order to record information that may be useful for reporting in Telegram 5. Read the entire page →
From page 114... ... 114 Development of Transactional Data Specifications for Demand-Responsive Transportation Customer Attributes Many of the telegrams in the proposed specification listed a "Special Attribute" for the customer. A list of potential special attributes is detailed below in Table D-12. Read the entire page →
From page 115... ... Detailed Specification Description 115 Reporting Trip Purpose Finally, it may be necessary in some cases to report the trip purpose for various reimbursement rules or human service agency reporting needs. Trip purpose codes are given in Table D-13. Read the entire page →

From page 99...

... 99 Detailed Specification Description A P P E N D I X D This appendix presents the proposed specification for demand-responsive transportation transactional data. A brief introduction to the overall approach is presented first; this approach centers around the concept of "telegrams," which are messages sent between entities.