1 / 20

The Right Kind of Information Silos

The Right Kind of Information Silos. What should be unified a nd where diversity is key. 2019 CALACT Spring Conference. Thomas Craig, General Manager t homas@ trilliumtransit.com Portland, Oregon. Concepts. Individual vs the Community. Individual Cars Personalized apps. Community

versace
Download Presentation

The Right Kind of Information Silos

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Right Kind of Information Silos What should be unifiedand where diversity is key 2019 CALACT Spring Conference Thomas Craig, General Manager thomas@trilliumtransit.com Portland, Oregon

  2. Concepts Individual vs the Community Individual • Cars • Personalized apps Community • Public Transit • Unified apps

  3. Concepts Information silos vs multimodal systems Information silos • Fixed-route tripPlanners • Taxi booking app Multimodal systems • Flexible trip planning • One-call One-click

  4. Concepts Duplicated processes vs unified systems Duplicated processes • Configure AVL, Google, Website separately • Stop asset inventory and GTFS database Unified systems • All end points drawn from GTFS • Stops database linked to other systems

  5. Obviously, we need one big unified system that supports a perfect app that serves all our customers.

  6. Sorry, not that simple.

  7. Misconceptions The obvious answer isn’t the right one The desire to prevent duplication of work has led us to try to unify our data architectures and our user interfaces. That’s good for data architectures. That’s often bad for user interfaces.

  8. Data architecture What makes a good one?

  9. Data architecture What makes a good one?

  10. Data architecture What makes a good one?

  11. Data architecture What makes a good one? There’s no way around different pieces being involved--in fact that’s the point. The critical goal is to ensure that those pieces interact through standardized connections in a modular system. Often times, having one vendor causes more complications than multiple vendors.

  12. Application-centric design

  13. Standards-centric design

  14. User Interfaces What makes a good one?

  15. User Interfaces What makes a good one?

  16. User Interfaces What makes a good one? A good user interface is as simple as it can possibly be. Everything but the interaction points are should be totally hidden from the user. The number and context of interaction points must be limited and refined.

  17. Data systems and user interfaces What makes a good one? Data architectures have to be extensible. You have to be able to plug things in. User interfaces should avoid “extensions”.

  18. So what does the agency do? How does an agency maintain good data and support diverse users? • Use data standards wherever possible • Expect technology vendors to get data from other systems and/or provide data to other systems • Accept “free” things from the market where available, and where you understand “free” • Invest in the things the market doesn’t provide • Expect maintenance to cost more than estimated

  19. Who are your disadvantaged riders? They deserve good user interfaces too. Help them out.Build them the silo the market won’t provide. Thomas Craig, General Manager thomas@trilliumtransit.com Portland, Oregon

More Related