SYSTEM AND METHOD FOR CONFIGURABLE DEPLOYMENT OF TRANSIT AGENCY CONTENT

• US 20130275324A1
• Filed: 04/12/2013
• Published: 10/17/2013
• Est. Priority Date: 04/13/2012
• Status: Abandoned Application

• Current Assignee: Trapeze Software Inc.
• Original Assignee: Trapeze Software ULC (Constellation Software Incorporated)
• Inventors: GODDARD, Matthew Carl, PAYNE, Bruce, GAVIN, David, BOWN, Damian
• Application Number:
  US13/861,877
• Publication Number:
  US 20130275324A1
• Time in Patent Office: Days
• US Class Current: 705/325
• 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

A system for managing incidents for a transit agency is disclosed, comprising an incident manager, configured to enable establishment and storage of one or more user profiles for one or more users, each profile indicating characteristics of transit incidents the user wishes to be notified of, create a transit incident having one or more incident characteristics, determine which users are to be notified of the transit incident based on their user profiles, and provide one or more notifications to the users that are to be notified.

Claims

1. A system for managing incidents for a transit agency comprising:

an incident manager, configured to;

enable establishment and storage of one or more user profiles for one or more users, each user profile indicating characteristics of transit incidents the user wishes to be notified of;

create a transit incident having one or more incident characteristics;

determine which users are to be notified of the transit incident based on their user profiles; and

provide one or more notifications to the users that are to be notified.

2. The system of claim 1 wherein the incident manager is further configured to receive information to create a transit incident having one or more incident characteristics.

3. The system of claim 2 wherein the receiving further comprises information provided by an administrator via one or more user interface elements.

4. The system of claim 3 wherein the incident manager is further configured to allow characterizing of the transit incident, by the administrator, according to pre-defined tags.

5. The system of claim 4 wherein the notification is auto-generated from the pre-defined tags.

6. The system of claim 2 further comprising one or more transit data servers configured to:

provide transit functionality, via one or more functionality modules, for the transit agency; and

communicate information to create a transit incident with the incident manager.

7. The system of claim 6 wherein the one or more transit data servers are users and have user profiles.

8. The system of claim 1 wherein each of the one or more users has a user type and mediums preference and the notifications are different for each user type and sent according to the users'"'"' mediums preferences.

9. A method for managing incidents for a transit agency, the transit agency having an incident manager and one or more transit data servers providing transit functionality to the transit agency, the method comprising:

enabling establishment and storage of one or more user profiles for one or more users, each user profile indicating characteristics of transit incidents the user wishes to be notified of;

creating a transit incident having one or more incident characteristics;

determining which users are to be notified of the transit incident based on their user profiles; and

providing one or more notifications to the users that are to be notified.

10. The method of claim 9 further comprising receiving information to create a transit incident having one or more incident characteristics.

11. The method of claim 10 wherein the receiving is from an administrator via one or more user interface elements.

12. The method of claim 11 further comprising characterizing, by the administrator, the transit incident according to pre-defined tags.

13. The method of claim 12 wherein the notifications are auto-generated from the pre-defined tags.

14. The method of claim 10 wherein the receiving is from a transit data server.

15. The method of claim 14 wherein the one or more transit data servers are users and have user profiles.

16. The method of claim 9 wherein each of the one or more users has a user type and mediums preference and the notifications are different for each user type and sent according to the users'"'"' mediums preferences.