Abstract: A method and a system for managing an electronic calendar. The method can include, in a calendar management system linked to a decision management system, associating a first calendar event with at least a first decision. In the calendar management system, prioritization information pertaining to the first decision can be collected. The prioritization information can indicate a decision type for the first decision and a value at risk in the first decision. A first calendar entry corresponding to the first calendar event, as well as the prioritization information pertaining to the first decision, can be presented to a user via a display of an electronic system.

Abstract: A method of managing decisions. The method can include identifying decision costs expended or projected to be expended for each of a plurality of decisions in a decision network and determining whether a sum of the decision costs expended or projected to be expended exceed at least one assigned cost threshold warning level. When the sum of the decision costs expended or projected to be expended exceed the assigned cost threshold warning level, a cost warning alert can be automatically generated and electronically communicated. The cost warning alert can indicate that the cost threshold warning level has been exceeded or is projected to be exceeded.

Abstract: A system is provide for effectively managing lease transactions in a comprehensive manner. Data is generated, processed, and stored at the lowest possible logical level in order to maximize the flexibility of a user to conduct processing at the asset, billing schedule, lease, account owner, master agreement, customer, or program level. Using a fully normalized data design, similar characteristics are treated similarly and different characteristics are treated differently. Unlike other systems, assets associated with the same lease can be treated differently without having to fake asset level processing by using multiple leases with one asset each, to represent one actual lease. A hierarchy of rule settings is enforced, whereby the rule at the lower more specific level trumps the rule at the higher or more general level. The system uses a highly encapsulated accounting engine which encapsulates accounting rules in a transparent incorporates accounting expertise in flexible and transparent manner.

Abstract: A system is provide for effectively managing lease transactions in a comprehensive manner. Data is generated, processed, and stored at the lowest possible logical level in order to maximize the flexibility of a user to conduct processing at the asset, billing schedule, lease, account owner, master agreement, customer, or program level. Using a fully normalized data design, similar characteristics are treated similarly and different characteristics are treated differently. Unlike other systems, assets associated with the same lease can be treated differently without having to fake asset level processing by using multiple leases with one asset each, to represent one actual lease. A hierarchy of rule settings is enforced, whereby the rule at the lower more specific level trumps the rule at the higher or more general level. The system uses a highly encapsulated accounting engine which encapsulates accounting rules in a transparent incorporates accounting expertise in flexible and transparent manner.