System and method for configurable deployment of transit agency content

• US 9,892,470 B2
• Filed: 04/12/2013
• Issued: 02/13/2018
• Est. Priority Date: 04/13/2012
• Status: Active Grant

• Current Assignee: Trapeze Software ULC (Constellation Software Incorporated)
• Original Assignee: Trapeze Software ULC (Constellation Software Incorporated)
• Inventors: Goddard, Matthew Carl, Payne, Bruce, Gavin, David, Bown, Damian
• Primary Examiner(s): Padmanabhan, Kavita
• Assistant Examiner(s): Burke, Tionna
• Application Number:
  US13/861,763
• Publication Number:
  US 20130275861A1
• Time in Patent Office: 1,768 Days
• Field of Search: 715234
• CPC Class Codes: G06F 16/972 Access to data in other repository systems, e.g. legacy data or dynamic Web page generation
• CPC Class Codes: G06F 40/14 Tree-structured documents parsing G06F40/205; validation G06F40/226
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 30/0201 Market modelling; Market analysis; Collecting market data
• CPC Class Codes: G06Q 50/01 Social networking
• CPC Class Codes: G06Q 50/14 Travel agencies
• CPC Class Codes: G06Q 50/265 Personal security, identity or safety

Abstract

Systems and methods for configurable deployment of transit agency content are provided that allow plug and play functionality modules, based on available transit data required by such functionality modules, to be placed on webpages. Further, content may be developed and published to various transit data sinks from a single dashboard.

Claims

1. A system for configurable transit agency content management comprising:

one or more transit data databases containing one or more transit data datasets;

a computer system comprising a processor, computer-executable instructions stored on a non-transitory computer-readable medium, and one or more data servers comprising;

one or more functionality modules, executed by a computer processor, each being configured to interact with one or more transit data databases and transit data datasets to provide functionality, each having one or more functionality module user interface components to allow one or more transit data sinks to interact with the functionality module and wherein the functionality module user interface components are be different for each of the selected transit data sinks, based on the screen size of the transit data sink, a user of the transit data sink and one or more customization parameters; and

a webpage design module, executed by the computer processor and configured to i) allow an operator of the webpage design module to design a preview webpage for the one or more transit data sinks by selecting one or more functionality module user interface components via a module selector, such preview webpage being visible only in a preview portion of a design module user interface and not being exposed to the one or more transit data sinks, and ii) publish a webpage, based on the preview webpage, that is exposed to the one or more transit data sinks, the webpage design module comprising a design module user interface component comprising the preview portion displaying a preview webpage and a sink target user interface component configured to allow the operator to select the one or more transit data sinks that should receive the webpage, and the module selector configured to allow an operator to select one or more of the functionality module user interface components to be placed on the preview webpage in order to publish the webpage.

2. The system of claim 1 wherein the webpage design module is configured to determine which functionality modules'"'"' functionality module user interface components can be placed thereon.

3. The system of claim 2 wherein the determination is based on whether the one or more transit databases include the transit data datasets required by the functionality modules.

4. The system of claim 3 wherein the determination may be made in real-time or before functionality module options are presented to the operator.

5. The system of claim 4 wherein the one or more functionality modules may be configured to receive parameters relating to the functionality, query one or more transit data databases based on the parameters, and display one or more results of such query.

6. The system of claim 5 wherein the one or more transit data databases may comprise one or more of route databases, asset databases, schedule adherence databases and trips databases.

7. The system of claim 6 wherein the one or more functionality modules may comprise one or more of route planning, asset monitoring, schedule adherence and trip planning modules.

8. The system of claim 1 wherein the module selector contains one or more icons representing one of the one or more functionality modules, each icon being selectable or not selectable and wherein, if selectable, the functionality module can be placed on the preview webpage.

9. The system of claim 1 wherein the webpage design module further comprises a sink target user interface component configured to allow the operator to select the one or more transit data sinks that should receive the webpage.

10. A method for configurable transit agency content management comprising:

receiving a request to design a webpage for a transit agency by selecting one or more functionality module user interface components to be placed on a webpage preview displayed on a screen wherein the functionality module user interface components are different for each of the transit data sinks, based on the screen size of the transit data sink, and a user of the transit data sink, and the webpage preview is not exposed to one or more transit data sinks;

determining what transit datasets the agency has access to;

allowing one or more functionality modules, each functionality module requiring one or more transit datasets for operation, to be selected and placed on the preview webpage based on if the determining indicated the agency has access to the transit datasets required by the functionality module;

receiving customization parameters relating to the functionality module and adjusting the appearance and operation of the functionality module based on the parameters; and

publish the webpage based on the webpage preview that is exposed to the one or more transit data sinks wherein the publishing further comprises allowing the selection of the one or more transit data sinks to expose the webpage to.

11. The method of claim 10 further comprising placing a functionality module on the webpage preview based on a user action.

12. The method of claim 10 wherein the publishing further comprises allowing the selection of the one or more transit data sinks to expose the webpage to.

13. The method of claim 12 further comprising receiving customization parameters relating to the functionality module and adjusting the appearance and operation of the functionality module based on the parameters.