SOFTWARE OBJECTS

BACKGROUND [0001] Field [0002] This application relates to risk management, to systems and methods that manage risk, and to content, process, document and records management systems. [0003] Related Art [0004] Many risk control systems are built on flat databases that are merely used to record and monitor a catalog of risks. Information concerning the status of these management efforts is typically entered manually into the risk control system. The actual management of the risks is typically handled outside of these systems. [0005] Frequently, the risk database that is used in these systems lags behind the actual risk circumstances and adds little value to the risk management process, other than to create a record for compliance purposes. Losses that are associated with these risks also often tend to be kept separately. [0006] At the same time, there has been a growing need to properly control operational risks. Regulatory authorities are tightening up on the required degree of controls, including regulations such as the Basel Accord II, the FSA Risk Framework, and the Tumbull Report/Common Code of Practice. [0007] In short, there is a growing need to be proactive in the management of risk, to reduce and mitigate risk, to reduce the capital needed to cover risk, to better control the processes associated with risk, to more promptly identify risk, to move business rules management away from legacy systems, and to transfer the management of risks to the owners of them. SUMMARY [0008] A risk management system may include a memory system containing a plurality of risk software objects, each of which represents a risk associated with an enterprise and which is configured to contain attributes and methods. The memory system may include a plurality of non-risk software objects, each of which represent something associated with the enterprise other than a risk, and a relationship between one of the risk software objects and one of the non-risk software objects. The risk management system may include a computer processing system configured to manage the software objects and the relationship. [0009] The computer processing system may be configured to trigger a process in response to a change in one of the risk software objects. The process may be specified by a method associated with the risk software object that is changed. [0010] The computer processing system may be configured to cause a change in one of the risk software objects upon the occurrence of an event. [0011] The event may be one that occurs outside of the risk management system. [0012] The event may be one that occurs within the risk management system. The event may be based on the passage of a period of time. [0013] The relationship may be represented by a link object. [0014] The relationship may be represented as an attribute of the risk software object that is related by the relationship. [0015] The computer processing system may be configured to allow a user of the risk management system to define the risk software objects. [0016] The non-risk software object that may be related by the relationship may represent a person. [0017] The non-risk software object that may be related by the relationship may represent a policy. [0018] The non-risk software object that may be related by the relationship may represent an asset. [0019] The non-risk software object that is related by the relationship may represent a transaction. [0020] The non-risk software object that may be related by the relationship may represent a loss. [0021] The non-risk software object that may be related by the relationship may include a document. [0022] One of the attributes of one of the risk software objects may represent a loss that may be associated with the risk. [0023] The computer processing system may be configured to grant a user exclusive access to a risk software object that the user is changing. [0024] The computer processing system may be configured to generate and store an audit trail relating to accesses that are made to the risk software objects. [0025] The computer processing system may be configured to allow each risk software object to be changed a plurality of times by a user of the risk management system and to allow each risk software object to be reconstructed to each of its states prior to each of the changes. [0026] The memory system may include a plurality of workflow processes relating to the enterprise and a relationship between one of the risk software objects and one of the workflow processes. The computer processing system may be configured to manage the workflow processes and the relationship. [0027] The memory system may include a relationship between two of the risk software objects, and the computer processing system may be configured to manage this relationship. [0028] The computer processing system may be configured to allow the user of the risk management system to navigate to a software object based on its relationship to another software object. [0029] The memory system may include a template for a risk software object, and the processing system may be configured to allow a user of the risk management system to define a risk software object based on the template. The template may have been based on one of the risk software objects, and the processing system may be configured to allow a user of the risk management system to create a template based on one of the risk software objects. [0030] A process for managing a plurality of risks associated with an enterprise in a computer processing system may include defining a risk software object that is configured to include attributes and methods to represent each risk. The process may include defining each of a plurality of non-risk software objects to represent something associated with the enterprise other than a risk, establishing a relationship between one of the risk software objects and one of the non-risk software objects, and managing the risks using the software objects, the relationship and the computer processing system. [0031] Computer-readable media may contain programming that, when installed in a computer processing system, allows a user of that computer processing system to define a risk software object configured to include attributes and methods to represent each risk in an enterprise. The programming may also allow the user to define each of a plurality of non-risk software objects to represent something related to the enterprise other than a risk, establish relationships between the risk software objects and the non-risk software objects, and manage the risks using the software objects and the relationships. [0032] A risk management system may include a memory system containing a plurality of risk software objects, each of which represents a risk associated with an enterprise and which is configured to contain attributes and methods. The memory system may include a plurality of workflow processes relating to the enterprise and a relationship between one of the risk software objects and one of the workflow processes. The risk management system may include a computer processing system configured to manage the risk software objects, the workflow processes and the relationship. [0033] The computer processing system may be configured to trigger one of the workflow processes in response to a change in one of the software objects. The triggerable, workflow process may be specified by a method associated with the risk software object that is changed. [0034] The computer processing system may be configured to cause a change in one of the risk software objects upon the occurrence of an event. [0035] The computer processing system may be configured to execute a user- defined process upon the occurrence of an event. [0036] The event may be one that occurs outside of the risk management system. [0037] The event may be one that occurs within the risk management system. The event may be based on the passage of a period of time. [0038] The relationship may be represented by a link object. [0039] The relationship may be represented as an attribute of the risk software object that is related by the relationship. [0040] The computer processing system may be configured to allow a user of the risk management system to define the risk software objects. [0041] The computer processing system may be configured grant a user exclusive access to a risk software object that the user is changing. [0042] The computer processing system may be configured to generate and store an audit trail relating to accesses that are made to the risk software objects. [0043] The computer processing system may be configured to allow each risk software object to be changed a plurality of times by a user of the risk management system, and to allow each risk software object to be reconstructed to each of its states prior to each of the changes. [0044] The memory system may include a template for a risk software object, and the processing system may be configured to allow a user of the risk management system to define a risk software object based on the template. The template may have been based on one of the risk software objects, and the processing system may be configured to allow a user of the risk management system to create a template based on one of the risk software objects. [0045] A process for managing a plurality of risks associated with an enterprise using a computer processing system may include defining a risk software object to represent each risk and configured to contain attributes and methods in a computer processing system. The process may include defining a plurality of workflow processes relating to the enterprise, establishing a relationship between one of the risk software objects and one of the workflow processes, and managing the risks using the risk software objects, the workflow processes and the relationship using the computer processing system. [0046] Computer-readable media may contain programming that, when installed in a computer processing system, allows a user of that computer processing system to define a risk software object configured to contain attributes and methods to represent each risk in an enterprise, define a plurality of workflow processes relating to the enterprise, establish relationships between the risk software objects and the workflow processes, and manage the risks using the risk software objects, the workflow processes and the relationships. [0047] A risk-management system may include a content management system and a process management system. The risk management system may include a computer processing system configured to allow risks to be defined as risk software objects that are related to the content and process management systems and that are configured to contain attributes and methods. [0048] The content and process management systems may be part of a single, integrated system. [0049] The content and process management systems may be separate systems. [0050] The risk management system may include a document management system, and the computer processing system may be configured to allow the risks that are defined as risk software objects to be related to the document management system. [0051] The computer processing system may be configured to allow the risk software objects to be declared as records that are managed by a records management system. [0052] The process management system may include a workflow management system. [0053] A risk management system may include a memory system containing a plurality of risk software objects, each of which represents a risk associated with an enterprise and which is configured to contain attributes and methods. The memory system may include multiple relationships between two of the risk software objects that were defined by one or more users of the risk management system. The risk management system may also include a computer processing system configured to manage the risk software objects and the multiple relationships. [0054] A process for managing a plurality of risks associated with an enterprise may include defining a risk software object that is configured to include attributes and methods to represent each risk in a computer processing system. The process may include establishing under the direction of one or more users of the risk management system multiple relationships between two of the risk software objects in the computer processing system, and managing the risks using the risk software objects, the multiple relationships and the computer processing system. [0055] Computer-readable media may contain programming that, when installed in a computer processing system, allows a user of that computer processing system to define a risk software object configured to include attributes and methods to represent each risk in an enterprise. The programming may allow the user to establish under the direction of one or more users of the risk management system multiple relationships between two of the risk software objects, and manage the risks using the software objects and the multiple relationships. [0056] A risk management system may include a memory system containing a plurality of risk software objects, each of which represents a risk associated with an enterprise and which is configured to contain attributes and methods. The risk management system may include a computer processing system configured to allow a user to be granted exclusive access to a risk software object that the user is changing. The computing processing system may be configured to allow each risk software object to be changed a plurality of times by a user of the risk management system, to allow each risk software object to be reconstructed to each of its states prior to each of the changes, and to allow the access users of the risk management system have to the risk software objects to be regulated. [0057] A process for managing a plurality of risks associated with an enterprise may include defining a risk software object that is configured to include attributes and methods to represent each risk in a computer processing system. The process may include granting a user exclusive access to one of the risk software objects that the user is changing, reconstructing one of the risk software objects that was changed by a user to its state prior to the change, and blocking a user from access to some but not all of the risk software objects. [0058] Computer-readable media may contain programming that, when installed in a computer processing system, allows a user of that computer processing system to define a risk software object that is configured to include attributes and methods to represent each risk in an enterprise, grant a user exclusive access to one of the risk software objects that the user is changing, reconstruct one of the risk software objects that was changed by a user to its state prior to the change, and block a user from access to some but not all of the risk software objects. [0059] These as well as still further features, objects, benefits, advantages, components and steps will now become clear upon a review of the Detailed Description of Illustrative Embodiments and the accompanying drawings. BRIEF DESCRIPTION OF DRAWINGS [0060] FIG. 1 illustrates a risk management system in which risks are defined as software objects. [0061] FIG. 2 illustrates a type of risk software object that may be used in the risk management system shown in FIG. 1. [0062] FIG. 3 illustrates types of non-risk software objects that may be used in the risk management system shown in FIG. 1. [0063] FIG. 4 illustrates multiple relationships between two risk software objects. [0064] FIG. 5 illustrates a risk management system in which risks are defined as software objects and in which the risk software objects are managed by various types of object management systems. DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS [0065] FIG. 1 illustrates a risk management system in which risks are defined as software objects. As shown in FIG. 1 , a computer processing system 101 may operate in conjunction with a memory system 103, a user interface 105 and external events 107. [0066] The computer processing system 101 may be configured to perform any or all portions of the functions described in this application, as well as other functions. For example, the computer processing system 101 may be configured to manage the various components in the system, including the various objects, processes and relationships that are discussed below. The computer processing system 101 may be configured to create, delete and modify any or all of these components. [0067] The computer processing system 101 may be constructed from any type of computer processing system and may include computer hardware and/or software. The computer processing system 101 may include a general purpose computer or a computer that is dedicated to the risk management system. The computer processing system 101 may include a single computer or multiple computers and/or processors. When using multiple computers and/or processors, the multiple computers and/or processors may be at a single location or at several locations. When using multiple computers and/or processors, the multiple computers and/or processors may be interconnected by a network system, such as a local area network, a wide area network, and/or the Internet. The computer processing system 101 may include any combination of these embodiments. [0068] The memory system 103 may include any type of memory system, including one or more hard disk drives, magnetic tape drives and/or RAMs. The memory system 103 may consist of a single device or multiple devices. When multiple devices are used, they may all be at the same location or at different locations. When multiple devices are used, appropriate hardware and/or software may be used to facilitate their intercommunication. [0069] Any one of the functions that are performed by the computer processing system 101 may be performed in response to input from the user interface 105 that originates with one or more users of the risk management system. The user interface 105 may include any type of user interface components, including one or more keyboards, mice and/or display screens. The user interface 105 may include appropriate software to process information. The user interface 105 may include communication links to other computing systems and/or databases. [0070] The memory system 103 may contain a plurality of risk software objects 109. Each software object may represent a risk associated with an enterprise, such as a business or other type of organization. One example of a risk software object is discussed below in connection with FiG. 2. [0071] The memory system 103 may include a plurality of non-risk software objects 111. Each non-risk software object may represent something associated with the enterprise other than a risk. Examples of non-risk software objects are discussed below in connection with FIG. 3. [0072] The memory system 103 may include a plurality of workflow processes 113. Each workflow process may represent a workflow process relating to the enterprise. The workflow process may be a fully automated workflow process or one that requires human intervention at one or more stages of the process. Processes related to the enterprise other than workflow processes may also be stored in the memory system 103. [0073] Various risk templates 115 may be stored in the memory system 103 and managed by a template management system 117 in the computer processing system 101. Each template may represent a particular type of risk. Under the control of the template management system 117, the user of the risk management system may create one or more risk templates 115 from which new risk software objects may be created. Each risk template may impose structures and/or associated processes for the risk object that is created based upon that template, thus facilitating consistency and comprehensive treatment of risks that are created from the template. The template management system 117 may be configured to allow the user to create one of the risk templates 115 based on an existing risk software object. [0074] The memory system 103 may include a plurality of relationships 119. Each relationship may specify an association between two or more components in the risk management system, such as between two or more of the risk software objects 109 and/or between one of the risk software objects 109 and one or more of the workflow processes 113. [0075] One or more of the relationships 119 may be an indirect relationship. For example, a relationship may be established between one of the workflow processes 113 and a particular type of risk software object, as defined by one of the risk templates 103. In this instance, each of the risk software objects 109 that are produced from this risk template may be indirectly related to this workflow process. [0076] The computer processing system 101 may be configured to allow the user operating through the user interface 105 to create, modify and/or delete one or more of the risk software objects 109, non-risk software objects 111 , and/or relationships 119. [0077] The memory system 103 may include a version history 129 which is created and managed by a version control system 123 in the computer processing system 101. As changes are made to one or more of the components in the risk management system, such as to one or more of the risk software objects 109, the version control system 123 may retain information in the version history 121 that will allow each component to be reconstructed to each of its states prior to each of the changes that are made to it. The information that is stored in the version history 121 may include complete replicates of earlier component versions and/or merely information indicative of the changes that are made thereto. [0078] The processing system 101 may include an event management system 125. The event management system may be configured to cause one or more processes to be implemented and/or to be altered during their implementation in response to one or more detected events. [0079] A broad variety of events may be detected. For example, one of the external events 107 may be detected, such as the arrival of a document or claim and/or a change in a market price. Internal events may also be detected, such as a change to one of the risk software objects 109. Certain events may also be triggered by the passage of time, such as periodic reviews, timed communications, diary events, risk deadlines and expiries, and time-based SLAs. A timer 127 in the computer processing system 101 may be used to provide the timing in connection with such timed events. [0080] A broad variety of processes may be implemented in response to events. These processes may be stored separately, such as in the form of one or more of the workflow processes 113. They may also be stored as part of the risk software objects 109, as will become more clear in connection with the discussion below of FIG. 2. [0081] One type of process can be to issue notifications. The risk management system may be configured to allow internal and/or external users (or organizations) to subscribe to individual risk software objects for the purpose of being notified whenever certain characteristics of the object change or when certain processes are initiated or completed. Notifications may be sent by e-mail or through the automated generation of letters. [0082] Escalations may also be handled by the event management system 125. When an attribute of a risk exceeds or declines below a certain threshold value and appropriate actions have not been instigated or completed, such an event may be used by the event management system 125 to automatically launch escalation processes that may minimize or capitalize upon the impact of such changes. [0083] Events and their triggered processes may be cascaded. For example, an event may trigger a first process which, in turn, may cause an event that triggers a second process. [0084] A check out system 129 may be employed in the computer processing system 101 to grant the user of the risk management system exclusive access to a risk software object that the user is in the process of changing. [0085] A security system 131 may be employed in the computer processing system 101 to govern who has access to particular risk software objects and the components that may be related to them. The security may be applied at various levels, including to groups of users and/or particular classes of information. [0086] An audit system 125 may be included in the computer processing system 101 to keep an audit of accesses that are made, including accesses to the risk software objects 109. The audit system 125 may keep track of who access an object, when it is modified, who authorizes the modification, who generates documentation related to the object, and when these events take place. All of this information may be reported on for auditing and compliance reporting purposes. [0087] A navigation system 128 may be included in the computer processing system 101 to allow a user of the risk management system to navigate from one component of the system, such as from a risk software object, to other components that are related to it. The navigation system 128 may include functionality that allows all relationships to a particular component, such as to a risk software object, to be displayed, and to allow the user to select from this display the next component with which the user wishes to work. [0088] The risk management system may include a different combination of components, as well as additional components. For example, the risk management system may include a life cycle management system that manages the life cycle of each risk software object, such as managing status transitions in the object, review and approval levels, version control, security, retention periods, expiry dates and electronic sign-offs. [0089] External management systems may be linked to the risk management system. [0090] The risk management system may include a rules-based regulatory reporting system. Regulatory reporting controls may be used to monitor risk status and plan scheduled activities. Exception reporting may be controlled automatically by the system, once risks meet (or fail to meet) certain pre-defined criteria. Business rules may be combined with automated processes to support automatic notifications and exception escalation. [0091] Trends and forecasts may be reported. Using process analyzer and simulation tools, trends and patterns in risk management may be identified and explored with what-if scenarios. [0092] Risk dependencies across departments in the enterprise may be analyzed. Using an enterprise-wide repository with a consistent method for managing risk, users may extend the concept of risk association to expose risks that are dependent on other risks or assets that are managed by different departments. One example may be fire on a property that is related to business liability on a business housed on that property. Another example is to associate medical conditions with car insurance. [0093] FIG. 2 illustrates a type of risk software object that may be used as or more of the risk software objects 109 shown in FIG. 1. As shown in FIG. 2, the risk software object 201 may be configured in conformance with the classic model of a software object that has been developed in object-oriented programming to include one or more attributes 203 and one or more methods 205. [0094] A broad variety of characteristics may be assigned as attributes 203 to the risk software object. The examples shown in FIG. 2 include attributes that are related to the risk that is embodied in the risk software object such as a name 207 for the risk, a description 209 of the risk, the type 211 of the risk, an identification of the owners 213 of the risk, audit information 215 relating to the risk software object, electronic signatures 217 that may have been procured in connection with the risk software object, notifications 219 that should be issued upon a change in an aspect of the risk software object, security information 221 relating to the risk software object, information about losses 223 that have been sustained in connection with the risk, status information 225 that is associate with the risk software object (such as under evaluation, accepted, rejected and/or loss occurred), information indicative of the value 227 of the risk, relevant dates 229 (e.g., creation date, expiry date, and/or key risk timelines, including multiple, periodic or cyclical information), and relationships 231 between the risk software object and other components. The relationships may be between the risk software object and one or more other risk software objects, non-risk software objects, workflow processes, or external references. [0095] Although each of these characteristics are illustrated in FIG. 2 as an attribute 203 of the risk software object 201 , each of these may also or instead be stored as separate components or objects in the risk management system. [0096] FIG. 2 similarly illustrates examples of methods 205 that may be related to the risk software object 201 , including methods that include or relate to rules 233, status changes 235, timed events 237, external events 239, triggered updates 241, aggregate updates 243, notifications 245, escalations 247, audits 249, reports 251 and trends and forecasts 253. Each of these may constitute software subroutines that initiate, alter or interrupt one or more processes. As with the attributes 203, the methods 205 may be stored separately from the risk software object 201 in another object or component. [0097] FIG. 3 illustrates types of non-risk software objects that may be used as one or more of the non-risk software objects 111 in the risk management system shown in FIG. 1 and that may be related to one or more of the risk software objects 109. As shown in FIG. 3, these non-risk software objects may include persons 301 (e.g., owners of risks and risk managers), policies 305, assets 307 (e.g., buildings or other property), losses 309, transactions 311, documents 313 (e.g., insurance policies), relationships 315 and workflow processes 317. Each non-risk software object may be in the form of the classical software object known to object-oriented programming that includes both attributes and methods. [0098] The risk management system may be configured to explore the associations between one or more of the risk software objects and one or more of the non-risk software objects. [0099] The system may also be configured alert one or more users of the risk management system who are responsible for the management of one or more of the non-risk software objects to the existence of one or more of the associated risk software objects and the corresponding relationships between one or more of the non- risk and one or more of the risk software objects. [00100] Using the navigation functionality described above, a user of the risk management system may transition between the management of one or more of the non-risk software objects and the management of one or more of the risk software objects that are associated with them. [00101] Relating one or more of the risk software objects to the management of one or more of the non-risk software objects may be referred to as "Contextual Risk Management". [00102] As should now be clear from a review of FIGS. 1-3, the same component may appear in one or several of many different ways in the risk management system. For example, a relationship may take the form of a separate component in the memory system 103, such as the relationships 119. Relationship may in addition or instead be attributes of a risk software object 201, such as the relationships attribute 231. They may instead be non-risk software objects, such as the relationships 315 shown in FIG. 3. [00103] Similarly, workflow processes may be defined in the system as separate components, such as the workflow processes 113 shown in FIG. 1 , as one or more of the methods 205 in the risk software object 201, and/or as one or more of the non-risk software objects shown in FIG. 3, such as the workflow processes 317. [00104] These are but a few examples of the infinite variations that may be implemented. [00105] FIG. 4 illustrates multiple relationships between two risk software objects. As shown in FIG. 4, a risk software object 401 may be related to a risk software object 403 with a plurality of relationships, such as by a relationship 405 and a relationship 407. Additional relationships may also be established. This multiple-relationship model between two risk software objects may be used in connection with the risk management system shown in FIG. 1. [00106] Although not illustrated, multiple relationships may also be established by the user between one or more of the risk software objects 109 and one or more of the non-risk software objects 111 and/or one or more of the workflow processes 113. [00107] FiG. 5 illustrates a risk management system in which risks are defined as software objects and in which the risk software objects are managed by various types of object management systems. As shown in FIG. 5, risk software objects 501 may be managed by a content management system 503, a process management system 505, a records management system 507 and a document management system 509. These systems may be collectively configured to create one or more of the structures and/or to implement one or more of the processes that are discussed above in connection with the risk management systems shown in FIGS. 1-4. A different combination of management systems and/or additional types of management systems may also be employed. [00108] The various management systems that are shown in FIG. 5 may, in whole or in part, be consolidated into a single, integrated management system, such as an integrated content management system and process management system. Alternatively, one or more of the various management systems may be separate, stand-alone systems that have been brought together and integrated merely for the purpose of creating the risk management system. [00109] The records management system 507, the process management system 505 and the risk software objects 501 shown in FIG. 5 may be configured to monitor the value(s) of one or more attributes of one or more of the risk software objects 501. In response to this monitoring and based on one or more pre-defined rules and/or conditions, the risk management system may be configured to automatically initiate one or more processes in the process management system 505. One or more of these processes, in turn, may declare one or more of the risk software objects 501 or other information associated with one or more of these objects to be a record in the records management system 507. One or more of these processes may in addition or instead classify one or more records in the records management system 507 and/or apply one or more pre-defined retention periods to one or more of them. [00110] The automatic application of records management process in response to changes in one or more attributes of one or more risk software objects may be referred to as "Zero-Click Records Management." This approach may also be applied in response to changes in one or more non-risk software objects. [00111] A broad variety of risks may be managed in a broad variety of ways using one or more of the systems and processes that are described above. [00112] For example, the departure of an employee from a company may be defined as one risk. [00113] Associated with that risk may be a set of rules. For example, one rule might be that no single employee may be assigned projects having a collective value in excess of $200,000. If this rule is violated, for example, a re-assignment process might be triggered. [00114] Another rule that might be associated with this risk is that no single project should carry a risk above $70,000. If this rule is violated, the occurrence of such an event might trigger a risk review process. [00115] After the user defines this risk, these rules, and these associated processes, the risk management system may implement these processes in an automated fashion in accordance with the rules. [00116] For example, the risk management system may record that project A carrying a risk of $50,000 has been assigned to employee X. Since this event does not violate any rule, no process is initiated as a result. [00117] Later, the risk management system may record that project B has also additionally been assigned to employee X and that project B carries a risk of $80,000. The risk management system will detect that this violates the rule against a single project carrying a risk above $70,000. In turn, the risk management system will initiate the associated risk review process. In turn, this may result in a notification being sent to a manager of the problem. The manager may then sub-divide the project into two smaller projects and reassign the set. [00118] Additional projects may then be assigned to employee X that cause a violation of the rule against any single employee carrying a risk of over $200,000. This will trigger the re-assignment process. Again, a notification may be sent to a manager of the problem who, in turn, may reassign the risk to another employee. [00119] Monitoring conditions associated with one or more of the risk software objects and automatically initiating relevant actions in response may be referred to as "Active Risk Management". [00120] The foregoing is but a simple example of how an embodiment of the risk management system may be configured to automatically and effectively manage a risk of an enterprise. A more comprehensive system may manage hundreds or risks and involved hundreds of associated persons, processes, events, etc. [00121] The features, objects, benefits, advantages, components and steps that have been discussed are merely illustrative and are not to be interpreted as limiting the scope of protection in any way. Numerous other embodiments are also contemplated, including embodiments that have fewer, more, and/or different features, objects, benefits, advantages, components and/or steps. The components and/or steps may also be arranged or ordered differently. In short, the scope of protection is limited solely by the claims that now follow. In these claims, the phrases "means for" and "step for" are intended to embrace the corresponding structure, material and acts that are described herein and to their equivalents. Conversely, the absence of either phrase is intended to mean that the claim is not limited to any such corresponding structure, material or acts.