Abstract: An event management architecture (EMA) for managing gaming events includes a plurality of sub-events associated with a gaming event. Each sub-event has at least one sub-event participant and provides a sub-event score to each sub-event participant according to a set of sub-event rules during a sub-event interval. A scheduling coordinator schedules, for each sub-event, the sub-event interval. A registration coordinator registers, for each sub-event, each participant. A scoring processor records, for each sub-event, the sub-event score for each participant, where the sub-event score is converted into a standard format. Each sub-event may be associated with a generic sub-event container, which takes advantage of the common characteristics or functionality requirements of the sub-events to facilitate the management of the sub-events. The EMA minimizes the need to administer the events individually, and can be scalably used to manage complex arrangements of interdependent sub-events of varying types.

Abstract: An event management architecture (EMA) for managing gaming events includes a plurality of sub-events associated with a gaming event. Each sub-event has at least one sub-event participant and provides a sub-event score to each sub-event participant according to a set of sub-event rules during a sub-event interval. A scheduling coordinator schedules, for each sub-event, the sub-event interval. A registration coordinator registers, for each sub-event, each participant. A scoring processor records, for each sub-event, the sub-event score for each participant, where the sub-event score is converted into a standard format. Each sub-event may be associated with a generic sub-event container, which takes advantage of the common characteristics or functionality requirements of the sub-events to facilitate the management of the sub-events. The EMA minimizes the need to administer the events individually, and can be scalably used to manage complex arrangements of interdependent sub-events of varying types.