Abstract: Disclosed is a system and method for generating a map. The system and method include a database for storing a list of recipients and characteristics associated with each recipient in the list of recipients. The method and system also include a control module for receiving a characteristic associated with at least one recipient in the list of recipients. The method and system also include a rule engine for generating a map based at least in part on the characteristic associated with the at least one recipient using programmable rules.

Abstract: Certain exemplary embodiments comprise a method, comprising: for each of a plurality of service offerings, via a rules interface, receiving a plurality of variables and corresponding values, the received variables and values defining the service offering; and representing the plurality of service offerings as a set of rules, each rule comprising one or more offering antecedents and one or more offering consequents, each of the plurality of service offerings corresponding to an offering antecedent of at least one of the rules.

Abstract: Certain exemplary embodiments comprise a method, comprising: via an antecedents user interface, receiving a plurality of customer antecedents, each of the customer antecedents corresponding to one of a plurality of variables associated with one or more rules from a set of rules defining a plurality of service offerings; generating a prioritized list of the plurality of service offerings based upon application of the set of rules to the received customer antecedents; and causing the prioritized list to be rendered to a user.

Abstract: A report definition file (FIG. 7) that is in XML format governs access to and presentation of data from a domain database 364. The report definition file may be created by inputting from a thin client 200 (such as a web browser) a set of report specifications, and converting the set of report specifications into the XML-format report definition file. The thin client 200 may input the report specifications through a definition wizard 314 (step 502), or by direct entry of SQL commands that are interpreted by an SQL builder 332 (step 512). The report definition file is converted to SQL (step 606) to allow retrieval of the data for output to thin client 200.