MXPA06014713A - Systems and methods for managing litigation and other matters - Google Patents

Abstract

A litigation management system (100) includes one or more devices (110) in communication via a network (120) with a case management system (130). The case management system device (130) is in communication with a case management database (132) and a structure and rules database (134). The litigation management system includes a document management device (140), a document retention device (150), a billing device (160), and a human resources device (170). The human resource device is in communication with an employee database (172).

Description

SYSTEMS AND METHODS TO MANAGE LITIGATION AND OTHER MATTERS CROSS REFERENCE TO RELATED REQUESTS This application claims priority and benefit under 35 U.S.C. § 119 (e) for the provisional patent application of E.U.A. series No. 60 / 477,516, entitled "Systems and Methods for Handling Litigation and Other Matters", filed in the name of Sammons and others, on June 11, 2003, the contents of which are hereby incorporated by reference in their entirety for all purposes FIELD OF THE INVENTION The embodiments of the present invention generally relate to litigation and other matters. More particularly, the modalities can refer to systems and methods for handling litigation and other matters.

BACKGROUND Tracing litigation and other disputes can be a bit complicated. This is particularly true when it is done to track key dates, witnesses and documents, especially when faced with numerous issues. For example, large companies often face a wide variety of disputes and a large company may have hundreds, if not thousands of disputes pending at a time. These disputes may relate to different aspects of the business and may involve various complex legal or technical issues. Errors or faults concerning deadlines or obligations can expose the company to varying levels of risk and therefore it is important to track and manage these issues. Mismanagement of discovery claims (which include preservation obligations) in particular can be extremely risky in pending litigation. It would be desirable to provide systems and methods to handle litigation that overcomes deficiencies in existing systems.

BRIEF DESCRIPTION OF THE DRAWINGS Figure 1 is a block diagram of a litigation management system according to some modalities. Figure 2 is a flow diagram of a method for establishing litigation management rules according to some modalities. Figure 3 is a flow diagram of a method for entering litigation management data according to some modalities. Figure 4 is a flow chart of a method for entering subject information according to some modalities. Figure 5 is a flow chart of a method for closing a matter according to some modalities. Figure 6 is a diagram of a portion of a database table according to some modalities. Figure 7 is a diagram of a portion of a database frame according to some modalities. Figure 8 is a block diagram of a user device according to some modalities. Figure 9 is an illustrative screen presentation according to some modalities. Figure 10 is a block diagram of a case management device according to some modalities.

DETAILED DESCRIPTION Introductory Example Before a detailed description of the present invention, a brief introductory example will now be provided to illustrate characteristics of some embodiments of the present invention. This introductory example will be transported throughout the rest of the application to describe features of various embodiments of the present invention. In the example, a company ("ABC Corp.") implemented features of the present invention to handle litigation matters. The company is a large, multinational organization that has two primary business segments: a commercial business, and a client business. Each of the business segments operate both in the U.S.A. and in other regions around the world, and each one actively engages in a large number of disputes at any given time. Each of the business segments has a number of different employees that handle litigation issues. In particular, both segments have their own house litigation management council and division General Councils (GCs). Both division GCs report to a corporate GC. Different employees for each of the business segments handle litigation issues that arise in different geographic regions. further, each business segment adopted different procedures to handle litigation issues. Despite having different procedures, different employees, and different types of disputes, the business segments share best practices, higher level management and reporting requirements. The modalities described here can allow the company (despite having different business segments that have different requirements and employees) to track and efficiently and systematically handle litigation matters. When implementing the system, the ABC corp. it can deploy a litigation management system accessible by a number of user devices as further described below and following the present invention. System administrators (employees with administrator authority) interact with the system to enter data and. rules that define the organizational structure and that define the litigation management rules of the company and of each of the business segments. For example, the ABC corp. it may have a company rule that all litigation matters involving claims exceeding 50 million must be reported to the GC of the ABC corp. together with the CEO and CFO. These individuals must also require approval of any settlement or conclusion of the matter. The commercial business may have a rule that if the exposure exceeds 5 million, the GC of the commercial business must be notified (and the individual is authorized to establish the claim as well). A number of other rules can also be implemented to enforce controls and to ensure that the litigation issues handled by the system are handled in a systematic and controlled manner. Once the system is configured, it is available for data entry. Certain employees may have authority to add and edit information litigation issue. When a new issue arises, an authorized employee enters the data when interacting with a data entry screen number (for example, accessible through a web browser). While entering the data, it is compared to any of the relevant litigation management rules. For example, if an employee in the commercial business enters information about a patent infringement lawsuit that was filed against ABC Corp. in which the total full exposure exceeds 50 million, the rules will require that notifications be sent to the GC, CEO and CFO . In addition, the data record associated with the new subject will be associated with information or a rule that ensures that the member can not be closed or established without the approval of the appropriate parties. The user who enters data will be guided through a series of data entry screens to ensure that all relevant data associated with the subject is entered. Some or all of the data entry screens can be associated with data entry rules that control which users can enter or avoid data, which data fields are required, and which data fields contain data that can not be modified. Notifications, status emails, and other information can be generated automatically by the system during the life of each issue. In some modalities, notifications are automatically generated and transmitted to relevant parties based at least in part on information retrieved from the ABC Corp's employee database. For example, each member of the commercial business litigation team can automatically receive email messages each time the issue of patent litigation is updated or modified. You can also reserve a preservation notice when discovery requests are served at ABC Corp. as well as subsequent reminders to produce the documents in response and a notification the matter concluded so that you can summarize the implementation of ABC Corp's record management policy. The identification of the litigation team can be done by referring to the employee database. Thus, the litigation management system does not need to be modified each time the employee status information changes. The demand for patent infringement can be traced by using the system through its dependence. Yes ABC Corp. wants to establish the matter (or if ABC Corp. prevails in the trial), the finalization of the matter to be approved for by the designated individuals. If the designated individuals do not authorize the closure, the matter will remain open in the system. In this way, the modalities can allow, for example, that a company (and each of the various business segments within the company) establish its rules of litigation and procedures and ensure that employees who enter, see, and avoid Litigation information comply with these rules. The modalities can also allow each business to share best practices and information, including performance evaluations, on litigation service providers. Other features, benefits, and / or configurations will be evident upon reading this description.Terms and Definitions Some modalities described here are directed to systems and methods to handle litigation. As used herein, the term "litigation" can generally refer to any of a number of different types of disputes and / or other matters involving complaints against (or by) an entity. The term "litigation" may include, for example, actions filed in court either in the United States (for example, including state, local, federal or other courts) or on board, as well as administrative disputes and other interactions between an entity and one or more third parties (for example, government research) Some modalities, for example, may be used to track third party situations and / or other actions, ignitions, documents, and / or other matters. it can or alternatively is used to refer to other non-contentious matters, which include, for example, proactive and / or risk litigation projects taken by an organization or other entity.Other issues can be tracked or handled by using modality characteristics as well. used here, the entity's operation (or utilization) characteristics of the claimed modalities can generally be termed as an organization). As used herein, the term "organization" may refer to any corporation, company and / or other entity that has a need and / or desire to handle litigation or other matters. For example, an organization can be a large company that has a number of different units or divisions of operation, each one that can be involved in litigation matters. Some modalities may allow, for example, such an efficient and accurately traceable organization and / or handle any or all litigation matters. In addition, as used herein, each "organization" may have one or more "sub-units" or "business groups," "businesses," and / or "branches," each of which may have one or more " business segments "and operate in one or more" business regions ". As a particular example, a corporation may have a "client business" and a "business business". The "commercial business" may have a number of business segments tai such as "valuation assurance", "bank loans", "business credit", "corporate loans", and / or "human resources." Each business (and / or each business segment) may operate in a region such as "business credit-Northeast USA" or "Business Credit, Canada," for example.Some modalities described here are associated with a "network devices." used here, the phrase "network device" can refer to any device that can communicate over a network, eg network devices include a Personal Computer (PC), a workstation, a server, a printer, a scanner, a facsimile machine, a copier, a Personal Digital Assistant (PDA), a storage device (for example, a disk unit), a switchboard, a router, a switch, and a communication device (for example, a modem, a wireless phone or, etc.) The network device may comprise one or more network components. As used herein, the term "network components" may refer to a network device, or a component, piece, portion, or combination of network devices. Example of network components may include a static random access memory (SRAM) device or module, a network processor, and a network, connection, port, or cable communication path. In addition, some modalities associate with a "network", or a "communication network". As used herein, the terms "network" and "communication network" may be used interchangeably and may be referred to as any object, entity, component, device, and / or any combination thereof that allows, facilitates, and / or contributes in another way or is associated with the transmission of messages, packets, signals, and / or other forms of information between and / or within one or more network devices. The networks can be or include a plurality of interconnected network devices. In some embodiments, the networks may be wired, wireless, virtual, neural, and / or any other configuration and / or type that is or is known. Communication networks may include, for example, one or more networks configured to operate in accordance with the fast Ethernet 802.3-2002® LAN transmission standard published by the Institute of Electrical and Electronics Engineers (IEEE). In addition, some modalities here, are associated with "information" or "data". As used herein, the terms "information" and "data" may be used interchangeably and may be referred to as any data, text, voice, video, image, message, bit, packet, pulse, tone, waveform, and / or another type or configuration of signal and / or information. Information may be or include information packets transmitted, for example, in accordance with one or more Internet Protocol standards, such as Internet Protocol Version 4 (Ipv4) or IPv6, the one defined above by "Internet Protocol Version Specification". 6 (Ipv6) "RFC 1883, published by the Internet Engineering Task Force (IETF), Network Working Group, S. Deering and others, December 1995). The information may, according to some modalities, be compressed, locked, and / or otherwise packaged or handled according to any method that is or becomes known. Some modalities described here are associated with "information indicative of" or "indication" of information associated with a subject, article, entity, and / or other object and / or idea. As used herein, the phrase "information indicative of" and "indications" may be used to receive any information that represents, and describes, and / or is otherwise associated with an entity, subject, or related object. The indicia of information may include, for example, a code, a reference, a link, a signal, an identifier, and / or any combination thereof and / or any other informational representation associated with the information. In some modalities, indication of information (or indicative of information) can be or include the information itself and / or any portion or component of the information.

System Some modalities will now be described when making reference first to Figure 1, where a system 100 is shown. The various systems described herein are illustrated for use in explanation but without limitation, of described modalities. Different types, designs, quantities, and configurations of any of the systems described herein can be used without deviating from the scope of some modalities. According to some embodiments, the litigation management system 100 includes one or more user devices 110 in communication (e.g., through a network 120) with a case management device 130. In some embodiments, the device case management 130 can be or be included and / or are in communication with a case management database 132 and / or a structure and database of rules 134. According to some modalities, the litigation management system 100 it may also alternatively include a document handling device 140, a document retention device 150, a billing device 160, and / or a human resources device 170. In some embodiments, the human resource device 170 may be or include and / or be in communication with an employee database 172. Any of the devices 110, 130, 140, 150, 160, 170 of the litigation management system 100 can be or include any type or network device (or combination of network devices) that is or becomes known. More databases 132, 134, 172 associated with the litigation management system 100 can, according to some modalities, be or include any type of data and / or storage structure, device, and / or a means that is or becomes known. In some embodiments, the information may be stored in an individual database and / or other storage device which may, for example, store the information associated with the various databases 132, 134, 172 shown in Figure 1. In some embodiments, less or more devices and / or other components may be included within the litigation management system 100. In addition, network 120 and / or any other type or method of communication may be linked and / or associated and / or otherwise allowed communication and between and the components of the litigation management system 100. In some modalities, the litigation management system 100 may include one or more networked computers configured and operated to perform the functions described herein. For example, in some embodiments, the case management device 130 may be configured to operate as a server accessible to one or more user devices 110 in the network 120. More users operating the user devices 110 may interact, for example , with the case management device 130 to enter information associated with new litigation matters, view information on existing matters, close existing issues, create reports, and / or perform other functions (for example, as described herein). In addition, following some modalities, certain users (such as users provided with "administrator" privileges are described elsewhere herein) can interact with case management device 130 to establish an entity structure and establish entity litigation rules associated with structure of entity. In this way, for example, different organizations and different businesses or other groups within the organization can establish relevant litigation management rules that allow efficient, accurate, and timely review of litigation matters. In some embodiments, the case management device 130 may interact with data sources and / or information. For example, the case management server 130 may interact with a human resource device 170 to access and / or use employee data and / or other data stored within and / or with the employee database 172. In some embodiments , the case management device 130 can be used to track and handle litigation matters in a large corporation that has many employees. It can be difficult to keep track of the state as location, contact information associated with each employee in a large corporation. Some modalities may be confronted with the resource device 170 (and / or other system that maintains on current employee information) to ensure that the case management device 130 has access to current and / or accurate employee information. For example, the employee database 172 can store information identifying each employee name, organization, contact information, imposition. In general, while employees change positions, move within the company, or leave the company information is updated. This information is used for a number of purposes in some modalities. For example, as will be discussed further below, the information is used to identify employee authority for certain actions (for example, such as establishment approval). The information is also used to quickly and efficiently add employees to contact and witness lists associated with different issues. In addition, the information can be used to identify and increase the access and use privileges for the litigation management system 100. In some embodiments, the access and use permits can be defined for each individual user (for example, only selected employees can have the ability to add or edit subject information). In some modalities, groups, classes or user organizations can grant different levels of access and privilege of use. For example, each user in the "general legal" group or organization may have the right to see selected issues. As another example, each employee in the "litigation" group (a subgroup of the "general legal" group) may have the right to view, add, and edit matters. As another example, each employee in a "litigation tool administrator" group may have the right to view, add, edit, close or delete issues, and may additionally have the right to perform other administrative tasks (including, for example , the right to create "lesson lists", the right to enter and update rules, etc.) - These access and use privileges may be revised each time a user attempts an action (for example, if a user attempts to edit subject information, the litigation management system may determine if the user has sufficient access privileges before allowing the action). As another example, the case management device 130 may interact with billing device 160 to ensure that third-party service providers associated with litigation matters are paid. For example, the billing device 160 can be or include a payable system of organization accounts. In some modalities, each litigation issue can be established with one or more billing identifiers. In some modes, the billing identifier can be used to track individual issues. In other modalities, a file number or other identifier can be used. Even another example, the case management device 130 may interact with the management device 10 to provide standardized document formats and / or to create a centralized repository of documents that are associated with tracked items and / or by the handling device. of case 130. For example, the document handling device 140 may store settlement agreements, pleadings, summaries, and / or other documents in training associated with the case management device 130. As another example, the management device case 130 may also or alternatively interact with the document retention device 150 to ensure that document retention procedures are properly followed and / or to create an easily accessible collection of documents associated with each litigation issue tracked by the management device Case 130. In some modalities, the litigation management system 100 can be operated to initiate iar the document retention policies once a new litigation issue is opened. For example, the document retention letter can be automatically distributed employees that is associated with a recently unclear issue. Other segments, components, and / or devices can cope with the case management device 130 without deviating from the range of some modalities. According to some embodiments, the case management device 130 can transmit (and / or receive) information to (and / or from) different devices through different networks. For example, in some modalities, the litigation management system 100 may be operated by an organization that includes a number of different businesses, some or all of which may be geographically separated. In such an organization, for example, the case management device 130 may communicate with user devices 110 (and / or other devices) operated by users in different business locations on separate networks (for example, network 120 may be or include one or more separate and / or different networks and / or network types) although only one individual case management device 130 is shown, multiple case management devices 130 may, according to some modalities, be provided for an organization. In some embodiments, different organizations may have access to the same case management device 130 (which may be configured with appropriate security and privacy protection to ensure that the case management data of each organization is properly stored). The case management device 130 and / or each of the other devices 110, 140, 150, 160, 170 may be or include any device capable of performing the various functions described herein. The case management device 130 may be, for example, a Web server. According to some embodiments, the user device 110 may be a PC capable of operating the web browser, such as Web browser INTERNET EXPLORER® 4.0 / 5.0 / 6.0 available from MICROSOFT CORP.®, which allows a user to direct the web browser to interact with web pages hosted by, for example, a case management device 130. A The number of illustrative user interfaces that can be used in conjunction with some modalities will be discussed later in conjunction with Figure 9.

Structure Definition Method Turning now to Figure 2, a flow diagram of a method 200 is shown according to some embodiments. In some embodiments, the method 200 may be conducted by and / or by using the litigation management system 100 described above and / or otherwise may be associated with the litigation management system 100 or any of the system components described collectively. with Figure 1 above. In some embodiments, for example, method 200 may be performed by, on, and / or within the case management device 130. The flowcharts described herein do not necessarily imply a fixed order to the actions, and modalities may be performed in any order which is practicable. It should be noted that any of the methods described herein may be performed by hardware, software (including micro codes), firmware, manual means or any combination thereof. For example, a storage medium can store therein instructions that when executed by a machine result in performance according to any of the modalities described herein. The method 200 is a processing that can be performed, according to some modalities, by the case management device 130 to create a new organizational structure (or modify or update an existing structure) and / or to remain (or modify or update ) Litigation rules associated with an organization or business of the organization. The procedure may begin, for example, at 202 to establish or otherwise define an organizational structure so that the litigation issues of the organization can be handled in an automated or semi-automated way using the 100 litigation management system. embodiments, the organization structure can be established for an organization that uses and / or is otherwise associated with the case management device 130. According to some embodiments, a user (e.g., who operates a user device 110) You can enter information that is used, at least in part, to establish the organizational structure. For example, in the example introduced above, processing in 202 may involve entering data and information that identifies the organizational structure that includes the businesses (for example, the "commercial business" and the "client business"), each one that can have multiple business segments and operate in different business regions. In some modalities, data entry (in 202 and in other interactions with the 100 system) can be facilitated through the use of "choice lists" or other Graphical User Interface (GUI) tools that allow a user to easily specify information In 202 the choice lists can help a user to enter information to define an organizational structure.In some modalities, the processing in 202 can also include the creation of new choice lists by authorized users.For example, the data entered at 202 they can be stored in one or more databases (eg, such as databases 132, 134, 172.) The others can be used to generate one or more choice lists that can be used to facilitate data entry when the information you enter into definition litigation issues associated with the businesses.For example, the election lists can allow users to enter Quickly and accurately information associated with a particular business, segment and / or region. The others entered can also or alternatively include data used to associate information from the database used with the business structure 172 (for example, information that can be entered is associated with groups of employees with particular businesses, segments or regions). In some modalities, method 200 may continue at 204 to establish execution litigation rules. For example, a user operating a user device 110 may enter information that establishes one or more litigation rules associated with the organization. In some modalities, a hierarchy of litigation rules can be identified as being provided, and / or otherwise established. For example, a higher level group of rules can be established which applies to all businesses within the organization. In some modalities, if a total exposure amount is so large that it would be considered a "material" item that requires public description or other treatment, a broad organizational rule can be defined which requires immediate reporting to the General Council (GC) as well as other individuals in superior management. Additional rules may be specified and / or established as applicable to individual businesses. For example, additional rules may include rules that define specific notification requirements associated with different types of issues. As a specific example, when information is entered regarding a new issue involving a trade secret or a patent dispute, a business may specify that the Chief Intellectual Property Officer of the business must also be notified as the business GC. Other rules can be established to allow information to be shared efficiently with relevant individuals and groups. Even other rules can be specified that approval authorities are related. For example, a business may specify that matters involving certain types of establishments or resolutions require particular approvals (for example, a business may indicate that establishments over $ 50 million must be approved by the CEO, the CFO and the business GC ). Once an organization and / or each business established a structure and defined litigation rules the case management device 130 can be made available for data entry. In some modalities, method 200 can be updated, repeated, and / or reviewed on a regular basis (or others) as long as the business changes and while different rules are implemented. In some embodiments, a central service and / or other entities (e.g., operating and / or having the litigation management system 100) can perform method 200 and / or any of the methods 202, 204 associated therewith.

Data Entry Method Referring now to Figure 3, a flow chart of a method 300 according to some embodiments is shown. In some embodiments, the method 300 may be conducted by and / or by using the litigation management system 100 described above and / or otherwise may be associated with the litigation management system 100 and / or any of the system components described. in conjunction with Figure 1 above. In some embodiments, for example, method 200 may be performed on, in, and / or within the case management device 130. In some embodiments, method 300 may be a continuation and / or a component of method 200 described above. For example, a method 300 may begin at 302 to receive details of litigation matter. In some embodiments, method 200 may, for example, already be performed and / or initiated (for example, through a central organization and / or service). According to some modalities, the information received at 302 can be or include information received through data entry (for example, from a user device 110). The litigation and / or other subject details may, according to some modalities, be entered by one or more authorized users when interacting with the case management device 130 through a device case 110. The subject details may be entered. in an initial case creation procedure, during the suspension of the matter, and / or when the matter is closed. Each time piece is entered with respect to the subject (for example, in 302), the procedure can proceed to 304 to compare details of litigation issue with organization litigation rules. In some modalities, the comparison can be revised, for example, to identify notifications and / or other actions that should be initiated. This comparison can be made to ensure that the rules are met and that any of the notifications or other actions are taken by the system. For example, if data entry (for example, at 302) includes opening a new issue that has a large potential dollar amount at risk, notifications to the appropriate parties can be automatically generated based on the comparison at 304. In some embodiments , organization litigation rules compare those of 304 can be or include the organization litigation rules set forth in 204 in method 200 described above.

New Subject Method Reference is now made to Figure 4, where a flow diagram of a method 400 is shown according to some modalities. In some embodiments, the method 400 may be conducted by and / or by using the litigation management system 100 described above and / or may otherwise be associated with the litigation management system 100 and / or any of the system components described. in conjunction with Figure 1 above. In some embodiments, for example, method 400 may be performed on, in, and / or within the case management device 130. In some embodiments, method 400 may be a continuation and / or a component of and / or otherwise associated with any of the methods, 200, 300 described above. Method 400 may, for example, be or include procedure 302 described in conjunction with Figure 3 above. In some modalities, method 400 may occur and / or be performed at any time a new issue arises. In addition, the method 400 can be performed under the direction or control of an authorized user. Processing can begin, according to some modalities, at 402, to create a new issue. In some modalities, a request to create a new subject can be received, from a user for example. In some modalities, only certain authorized users can create a new subject. User interfaces can be presented to the user who, for example, can prompt the user to enter information. Method 400 can continue at 404 where the business information associated with the new litigation issue is received. Business information may include, for example, business information is related to, involved with, important to, and / or otherwise associated with the litigation issue. In some modalities, method 400 may continue at 406 to receive case details and identify information associated with the new litigation issue.

For example information that includes case information and other identification details may be received from a user. According to some modalities, the method 400 may also alternatively receive programming data associated with the new litigation issue, at 408. For example, the programming information may include information such as programming, time recording, and / or other information. date or calendar information associated with the new litigation issue (and / or that relates to existing litigation issues). In 410, method 400 can continue to assign a responsible party to the new litigation issue. For example, a responsible party such as a corporation officer, executive, and / or legal representative can be assigned to the new litigation issue. According to some modalities, the assignment or responsible party may include and identify privileges to be associated with the responsible party. For example, the responsible party may have full access to and / or control over the litigation issue and / or may be limited to certain necessary functionalities. In some modalities, only certain users (for example, such as users who have "administrator" or designated privileges or assigned responsible parties) can assign or identify responsibilities and privileges. This information may be stored for use and / or reference (for example, in a database such as that described in conjunction with Figure 1).

Close A Subject Method Reference is now made to Figure 5, where a flow diagram of a method 500 is shown according to some modalities. In some embodiments the method 500 may be conducted by and / or by using the litigation management system 100 described above and / or otherwise may be associated with the litigation management system 100 and / or any of the system components described in FIG. set with Figure 1 above. In some embodiments, for example, the method 500 may be performed in, and / or within the case management device 130. In some embodiments the method 500 may be a continuation and / or a component of and / or otherwise associated with any of the methods 200, 300, 400 described above. The method 500 can be performed, according to some modalities, each time a subject tracked, stored, and / or handled by the litigation management system 100 is closed. Processing can start at 502 to receive an indication to close a matter. In some embodiments the indication may include a request, such as a request from a user. The request to close the selected litigation issue may, according to some modalities, be identified and / or otherwise terminated. Method 500 can continue at 504 to receive closure information associated with the litigation issue. In some modalities, closure information may include information such as establishment information (for example, information associated with the establishment of the litigation issue). The information regarding the closure and / or establishment of the litigation matter may, for example, be provided by a user operating a user device 110. The information may include, for example, information regarding the origin of the establishment or closure of the matter. of litigation. Method 500 can continue at 506 to receive approval information associated with the litigation issue. For example, the approval information may include information that identifies the individual who authorized (or needs to authorize) the closure of the litigation issue. The processing can continue, according to some modalities, in 508 to verify the approval information. For example, verification may include contacting the necessary individual or individuals through electronic mail or other means and / or confirming the business rules for the business to verify that the identified individual has the authority to authorize the closing of the matter. In some modalities, processing can continue at 510 to receive survey information for partnership with closing the litigation issue. The survey information may include, for example, an external advice assessment, an assessment of a witness, mediator, judge, or other entity involved in the matter. In this way, for example, current information can be captured to share with other businesses in the organization.

Illustrative Database Entries Referring now to Figure 6, a diagram of a portion of a 600 database chart according to some modalities is shown. The database box 600 may, according to some modalities, represent, be, and / or include a table representing the database such as the structure and rule database 134 that can be stored in (or accessible to ) the case management device 130. As shown, the database box 600 may include entries that identify a structure of an organization operating the case management device 130 and entries that identify the rules of litigation established by the organization (and / or by its units of the organization). Any and / or all the information in the entries may, according to some of the modalities, be entered by authorized users operating user devices 110. The database box 600 may, for example, define a number of fields for each one of the entries (for example, shown as fields 602, 604, 606, 608 but containing more or less as necessary). The fields shown specify: a business 602, a business segment 604, a business region 606, and a business rule 608. In some modalities, many, multiple, and / or alternative or additional business rules and / or business fields. Business rule 608 can be included in the 600 database box while it is or becomes practicable. In the database box 600 shown in Figure 6, only a portion of a database is necessarily shown, which specifies some of the businesses, segments and regions associated with a particular organization. Several illustrative rules are also shown. Other fields of databases, columns, structures, quantities, and / or configurations can be used without deviating from some modalities. Referring to Figure 7, a diagram of a portion of a database box 700 is shown according to some embodiments. The database box 700 can, for example, represent a database such as the case management database 132 that can be stored in (or accessible to) the term management device 130, according to some modalities . The database box 700 may, according to some modalities, include deliveries that identify specific litigation issues that were opened by using the litigation management system 100. The information may be received, for example, from authorized users operating devices. 110. Various amounts, types, and / or field configurations may be provided to track and / or handle litigation issue information. An illustrative number of fields 702, 704, 706, 708, 710, 712, 714, 716 are shown in Figure 7 for illustrative purposes. For example, the group ID field 702 may be or include a numeric identifier (and / or others) that uniquely identifies a particular litigation and / or other matter. The other field of the database box 700 may generally contain information that relates to various attributes and / or other information associated with various litigation matters and / or others (eg, as shown in Figure 7).

Illustrative User Device Figure 8 as a block diagram of a device 800 according to some embodiments is shown. As discussed above, users can interact with the case management device 130 which uses the user device 110. The device 800 can with the one according to some modalities, be or include a user device 110. In some embodiments, the device 800 may include a display 802. The display 802 may, for example, display a user interface 852. According to some embodiments, the user device 800 may alternatively or alternatively include one or more input devices such as a rotary 842 and / or a keyboard 844 (for example, to interact with the litigation management system 100). In the illustrative user interface 852 illustrated in Figure 8, a simple menu is presented which allows a user to select one or more options, which include the creation of a new subject (for example, which may result in the performance of a procedure such as according to method 400 described above), which opens an existing matter, and / or searches (for example, information associated with particular issues and / or subject types).

Illustrative User Interface Now reference is made to Figure 9, where an illustrative screen display 900 is shown according to some modalities. In some embodiments, the screen display 900 may be or include an interface that may be presented, for example, to facilitate the opening and / or creation of a litigation matter in accordance with method 400 described above. In some embodiments, the screen display 900 may be associated with any of the methods 200, 300, 400, 500 and / or with the litigation management system as described herein. The screen display may include, according to modalities, several fields as shown in Figure 9. For example, the fields of the screen display 900 may allow a user to search, create, modify, and / or another way to retrieve and / or provide information associated with litigation and / or other matters. Other types, quantities, and / or configurations or designs of 900 screen presentations to be used without deviating from some modalities. For example, the case management device 130 of the litigation management system 100 can provide and / or serve multiple Web pages through which users can handle litigation information at the user interface shown in Figure 9, a user is presented with a number of navigation options. For example, on the left side of the interface, a number of "summarized" pages can be seen, showing an authorized user information regarding the case, a status / summary of the case, the advice associated with the case, case allegations , witnesses, key dates, etc. Some of this information can be entered by authorized users; other information can be retrieved automatically from one or more sources (for example, for a token information can be extracted from the employee database for employee tokens). Other pages can also be observed, which include search pages (which allow authorized users to search through open or closed topics) report pages (which allow authorized users to create various reports that include information retrieved from open or closed matters). Users who have administrative privileges can access other pages, which include pages for user management (for example, allowing the granting or changing of access permissions), managing the list of choice (for example, allowing the creation or modification). of choice lists), and other subject handling functions. The right side of the user interface in Figure 9 shows a case summary screen for an issue opened on 03/01/2003. An audience trial shows that the user performed the most current update as well as the date of the most current update. In some modalities, these fields may not be avoided or changed. The summary screen shows that the subject is active is associated with the commercial business of ABC Corp. Following some modalities, the "active" or "inactive" state can only be changed by authorized users and that they follow any of the rules necessarily for the matter . In some modalities, color coding can be used to further distinguish between different states or types of information. As shown, a lesson list is provided to allow a user to use or select from among the recognized businesses of ABC Corp. (for example, in this example, the election list can offer two choices: commercial and customer). The screen also allows a user to identify the business segment (s) and region (s) impacted by the issue (again, selections can be made through the choice list). As shown, the election lists can also be used to enter information that identifies the type of issue, and the claims or allegations thereof, the role of ABC in litigation, and the relation of the adverse part with ABC (if there is one). Through the use of lists of choice and forms of structured data entry, and information provided by different users, it is standardized, thereby enabling easy search and reporting. A number of other data entry screens can be provided by using common web or interface techniques. Several of the screens will now be described in general terms to provide other illustrative information regarding various modalities. Those skilled in the art will recognize that other screens, data collections, and data entry techniques can be used.

Different states or summary screens can be used. Some or all of the screens can use choice lists (if appropriate) or data entry screens. For example, screens may be provided that allow the selection or presentation of one or more "case valuation forms", insurance coverage status information (which includes the insurance company), the type of court, the court name, the judge or arbitrator, an individual identified as the key business contact (for example, an organization employee whose information is retrieved from the employee database, a unit of currency (identifying the base currency associated with the subject jurisdiction) , and an exposure range (which includes of, for, payment establishment, establishment received, and sub reservation fields that can be formatted automatically following the unit of currency.) As mentioned above, the rules of litigation can be applied to data entered. in some of these fields to ensure that the appropriate report is made Other screens can allow authorized users to enter, edit or view (such as appropriate and as authorized) advice data associated with an issue. For example, authorized users can enter, edit or view data associated with the opposing council (the information can be selected through a selection list if the information regarding the opposing council is previously entered into another matter, otherwise the information is newly entered and may be available as an election list for future issues) and the external council (again, if the external advice information was previously entered, it can be selected through an election list, otherwise the information will be enters recently and may be available as an election list for future issues). Other screens may allow authorized users to enter, edit or view (as appropriate and as authorized) summaries of allegations associated with an issue. For example, the information associated with a take of the subject can be entered. An issue may have multiple takes, each associated with multiple allegations. An authorized user can add a new outlet and avoid existing intakes. The new allegation can be added to the take or existing ones can be avoided (or eliminated). Each shot will include information that identifies the court, the type of court, the judge (s) and information about the shot and the group number. An authorized user can add new judges and courts to the system can also add allegations to a shot. The user can add multiple allegations with information such as a tab number, date, part, and description to facilitate easy retrieval and observation. The user can also create an updated group list based on the list of allegations, thereby allowing others to quickly see the status of the matter. Other screens may allow authorized users to enter, edit, or view (as appropriate as authorized) witness information associated with a subject. For example, a screen may be presented that has revision tables after existing tokens (which allow an authorized user to remove witnesses from the subject). Choice lists and other witness lists can also be provided to facilitate the addition of witnesses. The search mechanisms can be provided to quickly search the employee database for a desired witness to add the token to the list. In some embodiments, screens may be provided to list details associated with all witnesses assigned to a subject, which include information that designation of particular witness is a "key player" or key witness. Other information may be provided that includes information that designates whether any of the action items are due associated with the witnesses (as well as details regarding the article). Even other information can be provided to identify contact information, which is called the witness, relevant position of the witness of the matter, a list of document (s) produced, the role of witness in the matter, etc. Other screens can be provided for cross-reference to witnesses between subjects (for example, a screen can show a list of issues in which the witness is involved and a list of items assigned to the witnesses). None of the employee's witnesses can be added through a data entry screen (if the non-employee witness information was previously entered, it can be selected through a choice list, otherwise the information is entered recently and can be be available through an election list for future issues). Other screens may allow authorized users to enter, edit, move (as appropriate and as authorized) "key date" information associated with a subject. For example, key dates can be any date that is important to the issue. These dates can be used by the system to generate notes, reminders and other information for users assigned to the subject. In key date formation can be entered by authorized users through a data entry screen that may require a user to enter information such as a description of the event, the date a warning or reminder date (s), a warning or message (s) of reminder the date on which the event is created, the name of the person sending the event, etc. Reminders can be emailed automatically by the system on the warning or reminder date (s). In some modalities, "key dates" and other reminders may be presented in a calendar form. In some modalities, dates and reminders may be published or integrated with existing calendar systems. As an illustrative example, in some modalities, the dates and reminders generated by the system are integrated in Microsoft Outlook® (for example, dates can be programmed in a user's Outlook® calendar and reminders can be sent to users via email Outlook® e-mail). A number of screens may be available only to administrators, which allows them to handle abscess permissions and user privileges. In some modalities, full groups of employees may have certain access privileges (for example, the "litigation group" may have editing and observation privileges "in some modalities, individual employees are selected to have particular access privileges. Administrators can also have permission to create new issues and assign employees to the subject.A matter created by an administrator can be created automatically in the "active" state while an issue created by a "litigation" group member can be created in a " inactive state "and must be approved by an administrator before it becomes" active. "As discussed above, rules and controls can be enforced to ensure that a matter in the" active "state is only changed to" inactive "and the rules relevant are met (for example, including ensuring that the appropriate approval authorities are updated for the closure of the matter). Administrators may also have the ability and authority to eliminate issues. As discussed earlier, administrators can also access screens that allow the creation or editing of the election list. In general, choice lists are master data of the system. This information is available to all users through all groups. An administrator can access a list editing screen of choice that, for example, presents the existing choice list data in tubular format. For example, each item in the choice list may have a name and a description and may be associated with a more detailed screen that allows the data to be edited. An administrator can also remove an item from an election list; however, if the article is currently in use, in any active or inactive matter (or any matter marked by deletion), the system will not allow the article to be deleted. An election list number can be used to handle data and control data entry, which includes as an example the following types of choice lists: product (list products manufactured by the company, type of case (types of list of issues), organizational business (list of various organizational), adverse relationship with the organization (list a number of types of relationships that the opposing parties can maintain with an organization) group (a list of groups that are assigned issues, for example , to signify the different types of subject), assurance status (list of the various applicable insurance states such as "uninsured", "insured by" etc.); subfolder (lists the various subfolders available for use in the realization of file updates); type of court (lists the various types of court, such as "court of state" or "local court" etc.); claims / pleadings (list of various claims) icables and types of plea); role of accomplishment (list various organizational roles); standard links (maintains a list of links that are displayed in a summary section of all the issues Contains URL information that contains an address and names); user group (which identifies separate groups of an organization); courts (list names of several courts to be added to pleadings); judges (list names of judges); etc. Other screens can be provided to facilitate searches. For example, a search module may be accessible to authorized users that allow searches to be made on active or inactive issues. For example, a screen can be provided that allows a user to search by selecting whether to search through active topics, inactive issues or all issues. The user can also enter a particular file number and run a search. Similarly, a user can search for a name of subjects only. In some modalities, a user can search in at least three different ways that use the same searchable text. As an example, if the search argument "John Smith" is entered, several different searches can be performed: 1. - To search in the full search capability argument, the user selects "search in exact argument" (predetermined). In this case, the search will be done through the topics that contain the word 'John Smith'. 2. - To search for the presence of each word entered as an argument with search capability, the user selects "search in any word". In this case, the search will identify all subjects that contain the word "John" or "Smith." 3.- To search for the presence of each word entered as an argument with the ability to search in combination, click on "search in each word". In this case, the search will identify all the subjects that contain the word "John" and "Smith". For each of the searches, the system will search in fields that include: the subject summary, the subject status, the strategy field, the external advice and opposing councils, claimants, defenders, insurance company information, and history of process. Even other screens can allow authorized users to generate a variety of reports. In some modalities, the screens may allow the user to select different fields to search to identify all the issues that satisfy the search request. A screen can present all the issues that satisfy the search and allow the user to select among the issues to generate reports. Authorized users can print to list issues or certain issues in the list. Different reports can be generated, which include subject details, etc. Those skilled in the art, upon reading this description, will recognize that a number of other screens and data entry techniques may be used in conjunction with the present invention.

Illustrative Case Management Device Also now in Figure 10, a block diagram of an apparatus 1000 is shown according to some embodiments. The apparatus 1000 can, for example, be or include a network device. In some pluralities, the apparatus 1000 may be or include a device and / or multiple devices within the litigation management system 100 described herein. The apparatus 1000 may, for example, be a case management device 130. In some embodiments, the apparatus 1000 may include a processor 1002, a communication interface 1004, a display device 1006, a pointing device 1008, a keyboard 1010, and / or a storage device 1012. According to some embodiments, the processor 1002 can run an operating system 1014, operate device drivers 1016, and / or run program such as a litigation program 1018. Any or all of the operating system 1014, device drivers 1016, and / or litigation management program 1018 can be stored, for example, in and / or by storage device 1012. According to some modalities, the operation and / or execution of the program Litigation management 1018 may cause the apparatus 1000 to operate in accordance with any of the methods 200, 300, 400, 500 and / or any of the modes described herein. In some embodiments for example, the apparatus may be the case management device 130 and may communicate with a user device 110 (e.g., through the communication interface 1104) and / or present a user interface such as the screen display 900 (for example, using the presentation device 1006). Although embodiments of the present invention are described with respect to particular types of organizations, the present invention can be used with any type of organization. For example, the present invention can be used to acquire information for a trade association or government agency having a number of units. The present invention is described in terms of various embodiments solely for the purpose of illustration. Those skilled in the art will recognize from this disclosure that the invention is not limited to the embodiments described, but may be practiced with modifications and alterations limited by the spirit and scope of the appended claims.

Claims (33)

1. - A litigation management method, which includes: receiving information associated with the structure of an organization; receive information associated with a litigation rule of the organization; receive information associated with a litigation matter; compare the information associated with the litigation issue with the information associated with the structure and the litigation rule to identify an action to be taken.

2. - The method according to claim 1, wherein the information associated with the structure of the organization is indicative of a plurality of businesses associated with the organization.

3. The method according to claim 2, wherein the information associated with the organization's litigation rule includes information indicative of one or more litigation rules associated with each of the plurality of businesses.

4. The method according to claim 1, wherein the information associated with the structure of the organization includes information indicative of one or more employees associated with the organization.

5. The method according to claim 1, wherein the information associated with the organization's litigation rule includes information indicative of the notification procedure to be started with the occurrence of one or more events.

6. - The method according to claim 1, wherein the information associated with the organization's litigation rule includes information indicative of a required approval before submitting to one or more events.

7. - The method according to claim 1, wherein the information associated with the organization's litigation rule includes information indicative of an information sharing procedure.

8. - A method that includes: receiving information associated with a litigation issue; compare the information with one or more litigation rules associated with an organization; and determine whether one or more of the litigation rules require action to be taken with respect to the information associated with the litigation issue.

9. - The method according to claim 8, which further comprises: causing the action to be taken if required by one or more litigation rules.

10. - The method according to claim 9, wherein the action includes at least one notification, one approval, or one information sharing.

11. The method according to claim 8, further comprising: creating a record that identifies the individual providing the information.

12. - One method, which includes: receiving a request to create a new litigation issue; receive (i) business identification information, (ii) case detail information and (iii) programming information, each of the types of information received being associated with the new litigation issue; assign at least one of a responsibility and privilege associated with the new litigation issue; and provide information indicative of the creation of the new litigation issue.

13. - The method according to claim 12, further comprising: storing at least one of the types of information received in a database.

14. - The method according to claim 12, wherein the request is received from a user interface.

15. The method according to claim 14, wherein the user interface includes a plurality of input screens each having a plurality of data entry fields, wherein at least one of the plurality of input fields of Data has an associated rule that allows data entry or modification by individuals who have a designated assigned privilege.

16. - One method, which includes: receiving a request to close a litigation issue; receive at least one settlement and closure information associated with the litigation issue; receive information associated with the approval to close the litigation issue; verify the approval received; and provide information indicative of the closure of the litigation issue.

17. - The method according to claim 16, which further comprises: receiving survey information associated with the closure of the litigation issue.

18. The method according to claim 17, wherein the survey information includes information indicative of an assessment associated with the closure of the litigation issue.

19. - The method according to claim 17, wherein the survey information includes information that relates to at least one external counsel associated with the litigation issue, a witness associated with the litigation issue, a meter associated with the litigation issue, or a judge associated with the litigation issue.

20. - The method according to claim 18, wherein the information associated with the closure approval includes information that identifies at least one entity that authorized the closure.

21. The method according to claim 20, wherein at least one entity includes an employee of an organization associated with the litigation issue.

22. - The method according to claim 16, wherein the verification of the approval includes connecting an entity that authorized the closure of the litigation issue.

23. - The method according to claim 20, wherein the verification of the approval includes confirming that an entity that authorized the closure of the litigation issue has authority to authorize the closure.

24. - A litigation management system, comprising: a processor; and a storage device in communication with the processor and storing instructions adapted to be executed by the processor to: receive first information associated with a structure of an organization; receive second information associated with a litigation rule of the organization; receive third information associated with a litigation matter; and compare the second information and the third information to identify an action to be taken.

25. - A litigation management system, comprising: a processor; and a storage device in communication with the processor and storing instructions adapted to be executed by the processor to: receive a request to create a new litigation matter; receive (i) business identification information, (ii) case detail information and (iii) programming information, each of the types of information received being associated with the new litigation issue; assign at least one responsibility and privilege associated with the new litigation issue; and provide information indicative of the creation of the new litigation issue.

26.- A litigation management system, which includes: a processor; and a storage device in communication with the processor and storing instructions adapted to be executed for the processor to: receive a request to close a litigation matter; receive at least one establishment and closing information associated with the litigation issue; receive information associated with an approval to close the litigation issue; verify the approval received; and provide information indicative of the closure of the litigation issue.

27.- A litigation management system that includes: a processor; and a storage device in communication with the processor and storing instructions adapted to be executed by the processor to: receive first information associated with a litigation issue; identify at least one business rule associated with the litigation issue; and generating at least a first notification based on a comparison of at least one business rule and the first information.

28.- A computer-readable medium that has software code executable by computer stored in it, the code comprises: code to receive first information associated with a structure of an organization; code to receive second information associated with a litigation rule of the organization; code to receive third information with litigation issue; and code to compare the second information and the third information to identify an action to be taken.

29. - A computer-readable medium having computer executable software code stored thereon, the code comprising: code for receiving a request to create a new litigation matter; code to receive (i) business identification information (ii) case detail information and (iii) programming information, each of the types of information received being associated with the new litigation issue; code to assign at least one responsibility and privilege associated with the new litigation issue; and code to provide information indicative of the creation of the new litigation issue.

30. - A computer readable medium having a computer executable software code stored therein, the code comprises: code for receiving a request to close a litigation matter; code to receive at least one establishment and closure of information associated with the litigation issue; code to receive information associated with an approval to close the litigation issue; code to verify the approval received; and code to provide information indicative of the closure of the litigation issue.

31. - A computer-readable medium having a computer executable software code stored therein, the code comprises: code for receiving first information associated with a litigation matter; code to identify at least one business rule associated with the litigation issue; code to generate at least a first notification based on a comparison of at least one business rule and the first information.

32. - A subject management system, comprising: a processor; a communication device in communication with the processor and an employee database system; and a storage device in communication with the processor and storing adapted instructions to be executed by the processor to: identify a subject that has an action date; identify at least one first rule associated with the issue, the first rule identifies at least one first employee associated with the issue; and using information from the employee database system, communicating information about the action date and the matter to at least the first employee.

33. The subject management system according to claim 32, wherein the information about the action date and the subject are communicated by using at least one email message or a calendar entry. 34. - The subject management system according to claim 32, the processor also stores instructions adapted to be executed by the processor to: identify a request to add a witness to the matter; determine that the witness is an employee in the employee base system; and automatically add information associated with the witness to the subject. 35. - A method for configuring a litigation management system, the litigation management system having at least one first choice list that defines a group of actions and information associated with at least one first litigation issue, the method comprising: receive a request from an individual to perform an action, the action that includes at least (i) a request to close at least a first litigation issue; (ii) a request to eliminate at least one first issue of litigation; (iii) a request to avoid said at least first choice list; (V) a request to create at least one second choice list; confirm that the individual is authorized to perform the action; and present the individual at least a first data entry screen to perform the action.