Classifications

• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q30/00—Commerce
  • G06Q30/06—Buying, selling or leasing transactions

Definitions

• the present invention relates generally to the purchase of items over an electronic network and, more particularly, to a system and method for creating, maintaining, and operating a forum through which buyers can purchase legal services from sellers via an electronic network, such as the Internet.
• BACKGROUND OF THE INVENTION Traditionally, services have been bought and sold through the interaction of people. Typically, the buy-sell process takes one of two forms: (1 ) a buyer determines the necessary service requirements and contacts one or more sellers of these services; or (2) a seller actively solicits the buyer, who may or may not be ready to purchase the services.
• outside counsel compensation may include performance bonuses coupled with fixed fee rates.
• In-house counsel may receive additional bonuses and stock options for reducing legal fees.
• a system consistent with the present invention facilitates the purchase of legal services from service providers.
• the system receives a service request including information reflecting a type of legal service, determines from a set of service providers a select group of service providers capable of satisfying the service request based on stored information associated with the set of service providers, provides the service request to each service provider of the select group of service providers, receives a response to the service request from any service providers from the select group, and outputs to the requester any responses from the service providers.
• the stored information includes at least an identification of types of legal services associated with each service provider, including for example, expertise of individuals.
• a method consistent with the present invention facilitates the purchase of legal services from service providers.
• the method includes a set of steps that may be performed in any order.
• service requests are stored, each including information reflecting a type of legal service.
• a set of service providers are permitted shared access to the stored service requests based on each provider's capability to satisfy a service request reflected in stored information associated with each of the providers.
• the stored information includes at least an identification of types of legal services associated with each service provider.
• Responses to the service requests are received from service providers. Each requester is permitted access to responses associated with the requester's service request.
• Fig. 1 is a flow chart of a process used to transact business in a manner consistent with the principles of the present invention
• Fig. 2 is an exemplary diagram of a system in which systems and methods consistent with the present invention may be implemented
• Fig. 3 is a detailed diagram of an exemplary service manager of Fig. 2 configured to manage a forum for the purchase of legal services in a manner consistent with the principles of the present invention
• Figs. 4-8 are flow charts of a forum operator program of the service manager of Fig. 3 consistent with one implementation of the present invention.
• Figs. 9-11 include three web pages that display three examples of views of information provided users in a manner consistent with the principles of the present invention.
• OVERVIEW Systems and methods consistent with the present invention provide a forum through which buyers and sellers of items, such as products and services (including, for example, legal services) interact.
• the buyers specify the types of items desired and the sellers submit proposals for providing the items.
• the buyers select the proposals that meet their requirements and contract with the particular sellers to provide the desired services and/or additional services.
• the forum is operated using conventional hardware, such as the
• Fig. 1 is a flow chart of a process 100 for managing a forum through which buyers and sellers transact business in a manner consistent with the principles of the present invention.
• a buyer authorized to engage in transactions using the forum creates a Request for Proposal (RFP) (step 105).
• RFP Request for Proposal
• Software operating on a data processing system accessible via a web server enables the forum and provides an interface, for example, a web page, for the buyer to specify the terms of the RFP.
• the RFP may include information on the item for which the buyer seeks a seller and qualifications of a seller. Certain information on the buyer, such as identifying information, may also be included in the RFP.
• the software may obtain this buyer information for the RFP from a repository that contains profile information, including buyer identifying information for each buyer permitted to create RFPs. Buyers may provide this profile information using a separate registration process.
• the data processing system notifies selected sellers of the RFP (step 110).
• Sellers are selected to receive notification of RFPs based on stored information associated with each seller. For example, only sellers qualified to provide a specific service specified in an RFP will be notified of that RFP. Buyers may also specify in the RFP the names of specific sellers to be notified of the RFP or to be excluded from the list of sellers to be notified. Buyers have access to the stored information associated with each seller for the purpose of selecting potential sellers for an RFP.
• sellers may provide profile information, including identifying information and qualifications using a separate registration process. Because the seller may represent multiple individuals (e.g., lawyers in a law firm) and the qualifications of each individual may be stored with the seller's qualification information, sellers may also be selected based on the qualifications of its associated individuals.
• individuals e.g., lawyers in a law firm
• sellers may also be selected based on the qualifications of its associated individuals.
• a conceptual matching algorithm may be applied for this purpose.
• Conceptual matching refers to extracting conceptual phrases from a source material (e.g., an RFP) and using the phrases as well as the individual words of the source text in locating possible matches for the source text.
• a taxonomic methodology used in conceptual indexing which provides a solution to the problems of keyword indexing, is discussed in W. Woods and J. Schmolze, "The KL-ONE Family,” Harvard University, Aiken Computation Laboratory, August 3, 1990, and W. Woods, “Understanding Subsumption and Taxonomy: A Framework for Progress," Harvard University, Aiken Computation Laboratory, August 15, 1990, both of which are incorporated herein by reference.
• the data processing system provides a mechanism through which potential sellers can communicate with the buyer using private or public communications (step 115). Private communications are between the buyer and each potential seller interested in responding to the buyer's RFP, whereas public communications are accessible to all of the potential sellers. This way a buyer may answer a specific question and make the answer available to all potential sellers, including the seller that posed the question. Also, the buyer may limit the time period for this Q&A period and, for example, depending upon the questions the buyer may extend the period as needed to respond to questions or concerns about an RFP.
• any interested sellers from the selected group submit bids to the buyer via the data processing system (step 120).
• the data processing system then notifies the buyer of the bid(s) (step 125) and enables a mechanism through which the buyer can now communicate directly with each bidder (i.e., selected seller that responded to an RFP) (step 130).
• the buyer notifies the data processing system of this selection (step 135), after which the data processing system notifies all of the bidders, including the successful bidder of the completion of the business transaction, i.e., award of the RFP (step 140).
• the data processing system may notify buyers and sellers of relevant communications (e.g., new RFPs, new bids, questions, answers, etc.) using electronic mail messages. Other communication mechanisms are also within the scope of the invention, including faxes, audio messages, telephone calls, etc.
• the notification may include details of the communication, a link to a web page accessible via the data processing system where the details of the communication can be accessed, or simply a message to access the data processing system for new communications.
• a forum operator associated with the data processing system may collect a commission for the service provided by the forum from either the buyer or seller based on the estimated total cost of the item involved in the transaction. Alternatively, the commission may be based on the actual cost of the service.
• the commission may be 2% of the fixed fee. If the fee arrangement is an hourly or other rate over the life of the transaction, then the commission may be 2% of the actual amount charged by the law firm each time it invoices the client. The commission may be collected using a credit card or other payment method.
• Other mechanisms may be used to remit payment for the commission. For example, it may be possible to debit an account associated with the requester for an amount of money equivalent to the commission that the requester committed to compensate the service provider associated with the accepted response.
• the account may be with a financial institution or with the forum operator.
• the forum operator may also notify the requester of the commission that the requester committed to compensate the forum operator associated with the accepted response.
• the forum represents a data processing system that assists corporations in retaining legal counsel. Corporations, as buyers, register with the system to submit RFPs. Law firms, as sellers, register to be eligible to respond to RFPs with bids. Although this description refers to corporations and law firms, one skilled in the art will recognize that individuals, partnerships or other entities may be buyers or sellers.
• a corporation registers by providing identification and contact information, naming one or more people authorized to post RFPs and receive and accept bids.
• Law firms register by providing identification and contact information, naming one or more people authorized to provide proposals or bids in response to RFPs. Law firms can provide information on practice areas, firm and/or individual expertise, firm size, geographical location, technological capability and other descriptive information, for use to notify them of RFPs of potential interest and for display to potential corporations. Fees are paid to the forum operator after the corporation retains a firm using the service of the forum. Those skilled in the art will recognize that this financial arrangement is appealing to corporations and law firms. Other financial arrangements for compensating the forum operator may also be employed. For example, the operator may obtain posting fees for RFPs and proposals, as well as advertising fees from law firms or other entities advertising through the forum.
• Corporations post RFPs each of which may include a title, a summary, a detailed project description, and backup documents and exhibits.
• Corporations list or check off mandatory or preferred qualifications for law firms, including any or all of the following: firm size, years in existence, practice areas, location, references, and the names and experience of the attorneys and other staff who will be assigned to the project. Corporations may also provide the maximum fee they will consider, their budget for the project, and other fee structure requirements.
• Corporations set the opening and closing dates of an optional "question and answer" (Q&A) period and the opening and closing dates for the law firms' submission of bids. All dates can be changed at the corporation's discretion. Corporations may cancel an RFP at any time.
• Q&A "question and answer"
• All RFPs are posted and open to all registered law firms, unless specifically excluded by the corporation by name, geographic area, practice area, and other selected criteria. Accordingly, the corporation can exclude certain firms from an RFP. Registered law firms are notified by, for example, e-mail notification of RFPs in their practice areas as shown in their registration information. This is accomplished by matching keywords, phrases and concepts in the text of RFPs to the information supplied by law firms. If a corporation develops a list of law firms and lawyers that suits its needs, it can request that only those "preferred firms" be notified of a particular RFP(s). The preferred list may be provided at registration or for each RFP. Corporations may also exclude firms by specifying at registration, firms to be excluded from viewing that corporation's RFPs.
• Corporations may also specify firms to be excluded from viewing only certain RFPs by providing a list of excluded firms when submitting RFPs. Alternatively, corporations may permit all or selected firms to view its RFPs but simply ignore a firm's bid, effectively excluding that firm from providing services to the corporation.
• the law firm will not be able to determine if, when or why it was excluded from an RFP.
• the forum has significant flexibility for open or closed RFPs and bidding. All or part of the information in an RFP may be available to all or selected firms, or to all or selected corporations; all or part of the information in bids may be available to all or selected corporations, or to all or selected firms. Depending on the situation, for example, a firm may prevent or allow competitors to see pricing information in a bid.
• the Q&A period enables corporations and law firms to refine their
• RFPs and proposals respectively. Law firms can ask questions about or suggest changes in RFPs. Law firms sign their questions or requests for changes or may remain anonymous. Corporations are not obligated to respond. Corporations may answer questions by responding directly to individual lawyers in the law firms or may post questions and/or answers for viewing by all registered law firms. Throughout the Q&A period, corporations can modify their RFPs. At the end of the Q&A period, the RFP includes any answers posted on the site by the corporation available to all participating law firms, are the basis for proposals. Each law firm's proposal must include the information requested in the
• RFP including the name of the submitting law firm and contact information, and may include any further information the law firm desires to submit.
• RFPs may require law firms to submit rates on other than an hourly basis (e.g. a fixed-fee or success fee proposal), the names of the partners, associates and other staff who will be working on the matter and their expertise in the area, and an estimate of the amount of partner, associate and other staff hours involved for the work requested.
• Each proposal will include the law firm's narrative response, approach to the problem and qualifications.
• Corporations may open a dialog with law firms and their authorized representatives at any time and, in doing so, may remain anonymous or may reveal their identity. This allows corporations to ask for revised cost proposals, clarify qualifications, and so forth, and when corporations reveal their identity, allows law firms to start their conflict checks.
• Fig. 2 is an exemplary diagram of a system 200 in which systems and methods consistent with the present invention may be implemented.
• the system 200 includes a buyer terminal 210 connected to several seller terminals 220 via a network 230.
• the system also includes a service manager (SM) 240 connected to the buyer and seller terminals 210 and 220, respectively, via the network 230.
• SM service manager
• the buyer terminal 210 may include a personal computer, such as an IBM-compatible computer, or the like, with a connection to the network 230.
• a single buyer terminal 210 has been shown for simplicity.
• the seller terminals 220 may also include personal computers with connections to the network 230.
• the network 230 may include the Internet, an intranet, or some equivalent data network.
• the terminals 210 and 220 may be operating a browser software application such as "Navigator" from Netscape Communications Corp. Those skilled in the art will be familiar with the operation of such browser applications and the manner in which they are used to access computers, such as servers, accessible via the Internet, an intranet, or some equivalent data network.
• each of the terminals may be specially equipped with communications software used to communicate via network 230 with SM 240.
• SM 240 includes a central processing unit (CPU) 245, random access memory (RAM) 250, read-only memory (ROM) 255, at least one data input device 260, data storage device 265, and a network interface 280.
• CPU central processing unit
• RAM random access memory
• ROM read-only memory
• CPU 245 is directly coupled to each of the other elements of SM 240, although, in an alternative configuration, network interface 280 may be coupled to CPU 245 via a communication port.
• CPU 245 executes program code (not shown) stored in one or more of RAM 250, ROM 255, and data storage device 265 to carry out the functions and acts described in connection with SM 240.
• CPU 245 comprises at least one highspeed digital data processor adequate to execute program modules consistent with the invention, such as operating a forum for processing business transactions between buyers and sellers.
• CPU 245 interacts with RAM 250, ROM 255, and storage device 265 to execute stored program code according to conventional data processing techniques.
• Data input device 260 permits SM 240 to receive information and, although shown as a single device, may comprise one or more data input devices of various types, such as an alphanumeric keyboard, a numeric keypad, a bar code scanner, a credit card reader, a disk drive, a memory, an electronic communication line, and a wireless transceiver. Input device 260 transmits received information to CPU 245 for storage in data storage device 265.
• Data storage device 265 preferably comprises a large capacity memory capable of maintaining a program, such as forum operator program 270, and at least one database 272.
• SM 240 is depicted as a single device in the figure, it may be made up of multiple devices, for example, a web server and a separate data processing system. In this configuration the web server would enable communications with SM 240 over the Internet and, in particular, the World Wide Web, and the data processing system would execute forum operator program 270.
• program 270 represents program instructions that provide functionality used to operate a forum for enabling corporations as the buyers and law firms as the sellers to transact business, including selecting and contracting with law firms to provide specific legal services. Details on the functionality of the forum operator program 270 are described below.
• Database 272 includes a set of tables 272A-272O that forum operator program 270 uses to run the forum, including: a member table 272A that contains information about individuals from corporations and law firms permitted to access to SM 240; a client table 272B that contains information on corporations; a firm table 272C that contains information on law firms; an address table 272D that contains address information for corporations and law firms; a phone table 272E that contains contact information such as telephone numbers or email addresses for corporation and law firm contacts; a RFP table 272F that contains information on requests for proposals (RFPs); an attachments table 272G that contains information on attachments or files associated with RFPs; a download table 272H that contains information on any downloaded attachments to RFP; a question/response table 2721 that contains information on questions and answers exchanged during the Q&A period associated with each RFP; an active RFP table 272J that contains information on any RFPs on which a law firm seeks additional information; a bid table 272K that contains information on
• database 272 may be replaced or augmented by an object oriented database architecture. Additionally, a different arrangement of tables and relations may be adopted.
• Member Table 272A is also within the scope of the invention as claimed.
• Member table 272A contains information about individuals associated with corporations and law firms permitted to gain access to SM 240. Each entry in table 272A includes a field for storing the following information: Memberld, MemberName, MemberPassword, MemberRole, FirstName, LastName, Email, PrevLoginTime, LoglnTime, and Transactionld.
• the Memberld represents a unique symbol, which may be a numeric or alphanumeric code, assigned by the system to each member.
• the "MemberName” represents a login name that a member has assigned, and "MemberPassword” is the password associated with that member. The member may assign a password when registering with the system, or change the password at any time. Alternatively, the system may assign passwords.
• the member's role after having successfully logging into the system, is determined from information associated with the "MemberRole" field.
• the roles are divided into two basic categories: corporations and law firms.
• the member who is the chief representative of the corporation is assigned the "superclient” role which permits him or her to register other members for the corporation, and reassign roles to members associated with the corporation.
• Only corporation members assigned the "RFPbidding" role may submit RFPs; these members act as the primary client contact for an RFP and are the only corporation members that may change information associated with that particular RFP. Otherwise, corporation members may read all information associated with any RFP submitted for the client.
• the member who is the chief representative of the law firm is assigned the "superlawyer” role which permits him or her to register other members of the law firm, and reassign roles to "lawyer,” “biddinglawyer,” or the "superlawyer” (when assigning the "superlawyer” role, the assigner gives up the role of "superlawyer” to the assignee).
• Only lawyer members assigned the "biddinglawyer” role may submit bids; these members act as the primary firm contact for a bid and are the only lawyer members that may change information associated with that particular bid. Otherwise, lawyer members may read all information associated with any bid submitted for the firm.
• Non-registered visitors may view a list of registered law firms and corporations. Alternatively, the service may hide information on either according to instructions from the firm or corporation. These visitors may register as either a corporation or a law firm.
• a member of a registered law firm may view a list of all RFPs that are available to that firm for bid. This list may include all RFPs, or it may be filtered to reveal only those RFPs that match the firms stated qualifications. No corporation information is visible in these descriptions.
• Client Table 272B is comprised of three relations: (1 ) a corporation relation that provides descriptions of corporations; (2) a member corporation relation that associates members with a particular corporation; and (3) a superclient relation that identifies the member who has the administrative permissions for the corporation.
• Each entry of a corporation relation reflects a ClientlD, which represents an identifier for the corporation, a ClientName, which represents the name of the corporation, a DUNSnumber, which represents a DUNS number identifying the corporation, a ClientEmail, which represents an email address for the corporation, a WebURL, which represents a Web site URL for the corporation, and a Transactionld, which represents an identifier to track any changes to this record type.
• the second relation in client table 272B is the MemberClient relation. Each entry in this relation includes the Clientld, Memberld, and Transactionld.
• the third relation in client table 272B is the SuperClient relation. Each entry in the SuperClient relation includes the Clientld, Memberld, and Transactionld.
• This table 272B may also include account information used to collect a commission when corporations award firms contracts for services, such as credit card or similar payment information.
• the commission may be computed based on the total value of contracts, for example, a percentage of the value.
• Firm table 272C is comprised of four relations: (1 ) a firm relation, (2) a member firm relation, a super lawyer relation, and an area firm relation.
• the firm relation describes a particular firm associating some of the attributes of that firm that will be used to qualify a firm to respond to a particular RFP, including information of the firm's practice areas, specialties, and the like, as well as information on specific individuals associated with the firm (e.g., partners, associates, counsel, etc.).
• Each entry in the firm relation includes a Firmld, which represents an assigned identifier for the firm, a FirmName, which represents the name of the firm, a FirmEmail, which represents the email address for the firm, an MHListing, which represents a Martindale Hubble listing identifier for the firm, a WebURL, which represents the Web site URL for the firm, a StartYear, which represents the year when the firm began practice, a Size, which represents the number of lawyers in firm, a StatePractice indicator, which represents states where the firm practices, a CountryPractice indicator which represents countries outside the US where the firm practices, and a Transactionld to track any changes to this record type.
• Martindale Hubble is the name of a directory of law firms.
• the Martindale Hubble is available on the Internet at http://www.martindale.com.
• the stored Martindale Hubble listing identifier may be a link or URL for the listing of a firm in the Martindale Hubble directory.
• ISIAS&_md5 c07e6dfacb819494159e69869ab11750, which may be stored as the Martindale Hubble listing identifier in firm table 272C.
• the member firm relation associates members with a particular firm. Each entry in this relation includes the Firmld, Memberld, and a Tansactionld, all of which were explained above.
• the super lawyer relation identifies the member who has the administrative permissions for the firm.
• Each entry in this relation includes the Firmld, Memberld, and a Tansactionld, all of which were explained above.
• the areas of practice for a firm are elements of the area firm relation.
• Each entry in this relation includes the Firmld, a PracticeAreald, and a TransactionlD.
• the PracticeAreald is an identifier that represents a firm's speciality or specialities. For example, CADWALADER, WICKERSHAM & TAFT specializes in "Capital Markets, Securitization, Corporate Law, Real Estate, Securities, Mergers, Acquisitions and Divestitures, Litigation, Finance, Project Finance, Bankruptcy, Banks and Banking, Taxation, Trusts and
• Each entry in this table includes an Addressld, which represents an Address identifier, a Purpose field, which is a code identifying purpose, such as "C” for corporation, “F” for firm, etc., Linkld, which is a linking identifier (Clientld or Firmld), multiple address fields for street and/or post office box number, city, state, and zip code, and a Transactionld.
• Addressld represents an Address identifier
• Purpose field which is a code identifying purpose, such as "C” for corporation, "F” for firm, etc.
• Linkld which is a linking identifier (Clientld or Firmld)
• multiple address fields for street and/or post office box number, city, state, and zip code
• a Transactionld Phone Table 272E
• Phone table 272E stores the telephone number data for members. Each entry in this table includes a Phoneld, a Memberld, a Purpose, PurposeNumber, and a Transactionld.
• the PhonelD represents an identifier for each entry in the table, and the Memberld, as explained above, represents a unique symbol for each member.
• the Purpose field is used to indicate the type of telephone number provided in the PurposeNumber field. Types of "Purposes" include home, office, fax, mobile, pager, etc., and each reflects the type of number provided in the PurposeNumber field.
• RFP table 272F contains the information for each RFP and is made up of three relations: RFP relation, FirmAccept relation, and FirmReject relation.
• Each entry in the RFP relation includes: an RFPId, which represents a unique identifier for each RFP; a Clientld, which represents the ClientlD of RFP poster (i.e., corporation); a Title, which represents a title of the RFP selected by the poster; a Clientldentification, which represents how the corporation is identified to bidding firms (e.g., by name or without a name if the corporation chooses to be anonymous); a Summary, which represents a brief description of the RFP; a URL for a detailed description of the RFP; a QuesOpenDate, which represents an opening date for the Q&A period (when this field is blank the corporation does not permit a Q&A period); a QuesClosingDate, which represents the closing date for Q&A period; an OpeningDate, which is when bidding may begin; a
• a BidAccepted field for indicating the posting corporation's preference for accepting responsive bids (e.g., "0" for "accept any bid” or “1” for “accept only bids from firms satisfying mandatory requirements”); a PostingDateTime for the Date/time when RFP was originally created; a ModifiedDateTime for the Date/time when RFP was last modified; a Status field for status information associated with the RFP (e.g., "C” for creation stage; "B” for bidding stage; “W” for withdrawn; “D” for deleted; “S” for successful bid accepted; "F” for fee bid accepted); a Bidld, which represents the identifier of a successful bid; a ComputedFee for the computed fee for the successful bid; a PaymentMethod field for information on how the poster will pay for the services (e.g., Visa, MasterCard, Amex, Bill), a PaymentRe
• the summary field is displayed along with the opening and closing dates for bids and questions, and the requirements for qualifying firms.
• the FirmAccept relation lists the firms that are permitted to bid. If this list exists for the RFP, only those firms will be notified of the RFP posting. Each entry in this relation includes an RFP Id, which represents the identifier of an RFP; a Firmld, which represents an identifier of firm requested for bid; and a Transactionld.
• the FirmReject relation lists the firms that will not be permitted to bid.
• Attachments Table 272G contains information that further explain an
• RFP or bid in response to an RFP.
• the attachment name string is employed which can be a phrase that identifies the attachment.
• the size of the file is also present in the relation.
• Each entry in this table includes an Attachmentld, which represents an identifier for an attachment; an AttachmentType, which represents the type of attachment (e.g., "C” for corporation attachment to RFP; “F” for firm attachment to bid); an RFP Id or Bidld; and AttachmentName, which represents an external name for an attachment; an AttachmentSize, which is the size (e.g., bytes) of an attachment; and a Transactionld. Download Table 272H
• Download table 272H is used when either a company downloads attachments to an RFP or a firm downloads attachments to a bid. In particular, this table is used to record all download events. A corporation that has posted an RFP can find out how many times the supporting documentation for that RFP has been downloaded.
• Each entry in this table includes a Download Id; a DownloadType, which represents the type of download (e.g., "C” for corporation download of bid; "F” for firm download of RFP); a Linkld, which is either an RFP Id or Bidld; a ClientFirmld, which is an identifier for either a corporation or firm; a Memberld, which is an identifier of the member requesting the download; a DateTime for when information was downloaded; a DownloadType for information on data downloaded (e.g., RFP, Bid, Question, Response); and a Transactionld.
• a corporation may open a question and answer session to be held while law firms consider an RFP. Questions can then be posed by any law firm. Initially the question is viewable only by the corporation posting the RFP and the questioning firm. At the discretion of the corporation, all firms may view the question.
• a response made by the corporation can be captured by the response relation.
• the response will be private to the requesting law firm unless the corporation expressly permits all firms to view the answer. There may be more than one response posted to a particular question.
• Anonymity of the questioning firm may be protected when a question/answer is made available to other members.
• Each entry of the Question relation includes: a Questionld, which represent a unique identifier for each question; an RFP Id, which represents the RFP associated with the posted question; a Firmld, which represents firm posting a question; a Memberld, which identifies the member posting the question; a Viewable code for distinguishing between users permitted to view a question (e.g., "0" for viewable to all, no restriction; "1" for not viewable to other than corporation and posting firm); a DateTime to record the date/time when the question was posted; the text of the question; and a Transactionld.
• a Questionld which represent a unique identifier for each question
• an RFP Id which represents the RFP associated with the posted question
• a Firmld which represents firm posting a question
• a Memberld which identifies the member posting the question
• a Viewable code for distinguishing between users permitted to view a question (e.g., "0" for viewable to all, no restriction; "1
• Each entry of the Response relation includes a Responseld, which represents a unique identifier for each response to a question; the Questionld associated with the question to which a response is provided; a DateTime to record the date/time when the response was posted; Viewable code for distinguishing between users permitted to view a question (e.g., "0" for viewable to all, no restriction; "1" for not viewable to other than corporation and posting firm); the text of the response; and a Transactionld.
• ActiveRFP Table 272J As corporations post RFPs, law firms are notified of those that are for services in their areas of practice. When a firm wishes to receive more information about an RFP, a member associated with firm will place that RFP on the firm's active RFP list. Placing the RFP there permits the firm to download all information concerning the RFP. The ActiveRFP relation maintains this information.
• Each entry includes a Memberld; an RFP Id;
• each entry in this relation contains the identifier of the RFP to which the firm is responding as well as the fee type and amount.
• each entry in this relation includes: a Bidld; an RFPId; a Firmld; a Memberld; a DateTime for when when the bid was posted; a SuccessFee to indicate whether the bid fee is contingent upon success; a Fee to indicate the total fee associated with bid when not contingent upon success; a short summary of the firms qualifications and the proposed work; a status of bid (e.g., "C” for created; "P” for posted; "A” for accepted; "E” for eliminated; “N” for Negotiating); and a Transactionld.
• Correspondence Table 272L contains the identifier of the RFP to which the firm is responding as well as the fee type and amount.
• each entry in this relation includes: a Bidld; an RFPId; a Firmld; a Memberld; a DateTime for when when the bid was posted; a SuccessF
• Correspondence table 272L captures all negotiations carried on by the corporation and firm. Each party can view all contents of the correspondence. Once the correspondence has been posted, it remains in a read-only state to both parties. Each entry includes: a Correspondenceld, which is a unique identifier for each entry, a Bidld; a Memberld; a Viewable code (e.g., "0" for anonymous; "1” for corporation name viewable); a status (e.g., "C” for created; "P” posted), a DateTime when correspondence was posted; the text of the response; and a Transactionld. Actions Table 272M
• This table is used to record the events that affect RFP and bids. These actions are recorded by the system when a significant event affecting the bidding process for a client or firm occur. Action types include events such as firm responds to an RFP with bid, firm changes contents of a bid, firm submits a question to an RFP, firm posts a correspondence to an RFP/bid, corporation changes RFP, corporation answers a question, corporation posts a correspondence to a RFP/bid; corporation accepts bid.
• Each entry in this table includes: an Actionld; a DateTime when the action was recorded; a ToWhom field information on the party affected by the action (e.g., "C” for corporation; "F” for firm); a Linkld for the Clientld or Firmld; an RFPId or Bidld (e.g., RFPId for Firm; Bidld for Client); an ActionTypeld; and a Transactionld.
• This table contains information about RFPs and bids that have been purged from the system.
• Each entry includes an Archiveld (the archive files are compressed into a container called by this identifier); a DateTime of when archive action was taken; an ArchiveType ("0" for successful bid; "1” for Expired RFP; "2” for withdrawn RFP); a Clientld for the corporation that provided the RFP; a Firmld for the firm winning the competition; a FeeType; a TotalFee amount; Service Fee paid to the system provider; and a Transactionld.
• Miscellaneous Table 2720 Miscellaneous table maintains other relations in the system.
• an AreaOfPractice relation contains information on the areas of legal practice
• a SizeOfPractice relation contains the level breakdown for the size of practices
• an ActionType relation links the ActionTypelD to a displayable string
• the Nextlds relation contains the values of the next identifiers to be assigned by the system for various relations in the system.
• Each entry in the AreaOfPractice relation includes an PracticeAreald; an identifier for area of practice; a description of the practice area; and a Transactionld.
• Each entry in the SizeOfPractice relation includes a SizeOfPracticeld for the identifier for size of practice; a LawyerCount for the maximum number of lawyers for a SizeOfPracticeld; and a Transactionld. This way the firm relations table may use identifiers to refer to areas of practice and size of the firm.
• Each entry in the ActionType relation includes an ActionTypeld for the identifier for each action type; a description field; and a Transactionld.
• FORUM PROCESSING Figs. 4-8 depict flow charts of steps embodying one implementation of forum operator program 270 executed by CPU 245 in accordance with the principles of the present invention.
• SM 240 receives an access request from a client computer, such as buyer terminal 210 associated with a corporation member or one of the seller terminals 220 associated with a law firm member (step 410).
• this request may include a request in response to a user inputting into a browser application operating on the client computer a Uniform Resource Locator (URL) associated with SM 240.
• URL Uniform Resource Locator
• SM 240 Upon receipt of an access request, SM 240 generates one or more "web pages" with various options and provides the page(s) to the client computer for display to the user using the browser (step 420).
• the "web pages" may be generated using hypertext markup language or an equivalent protocol. Also, information travels in both directions in that users can input information using web pages as forms and transmit the information to SM 240.
• Options on the initial page(s) include information request, registration, and login (440, 450, 460 respectively). Upon selection of one of these options by the user, SM 240 follows a specific set of operations illustrated in the flow charts of Figs. 4-6.
• SM 240 When the user selects the information request option (step 430, 440), SM 240 simply generates a page with any selected information and provides the page to the client computer for display (step 445). This way users can obtain additional information on the operations of SM 240 and, in particular, how to register, post RFPs, post bids, and otherwise engage in activities using SM 240.
• SM 240 When the user selects the registration option (step 430, 450), SM 240 generates a registration page and provides the page to the client computer for display (step 510, Fig. 5). The page permits the user to indicate whether he/she represents a corporation or law firm. Upon selection of one of these options (step 520), SM 240 generates a specific corporation or law firm page and provides the appropriate page to the client computer for display (steps 530 and 540, respectively). After the user completes the form with information and returns that information to SM 240, SM 240 verifies that the information is accurate and/or complete (step 550 for corporations and step 560 for law firms). This verification process ensures that only qualified corporations and law firms are permitted to use the system.
• Qualified entities provide the data required to populate the non-optional fields of client and firm tables 272B, 272C of database 272.
• Other forms of verification may be used, including making sure that only corporations or firms meeting predetermined criteria, such as size or value, use the system. These criteria may thus be used to ensure certain standards within the forum.
• SM 240 Upon verification, SM 240 updates the client or firm table 272B, 272C of database 272 (step 570 for corporations and step 580 for law firms), accordingly. Processing Login Requests
• SM 240 When the user selects the login option (step 430, 460), SM 240 generates a login page and provides the page to the client computer for display (step 610, Fig. 6).
• the login page preferably includes fields through which a user can input login information, including a member name and password.
• SM 240 will then determine whether the user is registered to use the system and, if so, permit access to the system based on the member's role (corporate member or law firm member). For corporation members SM 240 generates and display one or more pages with options available to that member's corporation (step 630). For law firm member SM 240 generates and display one or more pages with options available to that member's law firm (step 640).
• Corporation member options are represented by the steps in the flow chart of Fig. 7, whereas law firm member options are represented by the steps in the flow chart of Fig. 8. Corporation Member Processing
• the corporation member options include update profile 720, law firm search 730, and list RFPs 740, each of which corresponds to a different operation of SM 240.
• SM 240 may present the options to members in the form of button on a display screen such that when the member selects a particular button by, for example, using a mouse or other input device to point to the button and click on a mouse button, SM 240 performs operations associated with the selected option.
• SM 240 accesses client table 272B and populates a page with information associated with the member's corporation. The member may then modify the profile information and submit the information with any modifications to SM 240 to update database 272. As suggested above, SM 240 may limit the capability of members of a corporation to modify the corporation's profile to members satisfying the superclient relation.
• SM 240 When the member selects the law firm search option (step 710, 730), SM 240 generates a page for the member to input search criteria to search firm table 272C.
• search criteria e.g., text matching, or concept matching techniques.
• SM 240 accesses table 272C, applies the search criteria and algorithm, and returns a list of law firms, if any, that satisfy the criteria in accordance with the algorithm.
• SM 240 may provide the member with a page that includes specific fields and available attributes for each field using a known pull-down menu technique.
• the member completes particular fields with selected attributes and transmits that field/attribute information to SM 240.
• SM 240 in turn accesses table 272C, selects law firms that satisfy the attributes, and returns to the member a page including a list of law firms, if any, that satisfy the attributes. Entries on this list may be used as links to additional detailed information from table 272C so that if the member selects a particular link, SM 240 generates another page with information on the firm extracted from table 272C and provide this law firm detail page to the member. If no firms are found then an appropriate message may be provided to the member.
• SM 240 When the member selects the list RFP option (step 710, 740), SM 240 generates a page including a list identifying RFPs associated with the member's corporation.
• the list may be limited to RFPs that the corporation has not yet awarded or it may include all RFPs that have not yet been archived.
• An example of such a page 900 is shown in Fig. 9.
• the member may view the details of an RFP by selecting an RFP and the view option 905.
• the filled circle next to the RFP titled "Federal Court Commercial Litigation" indicates that the member has selected this RFP.
• RFP may be modified using the same procedure for viewing and selecting the modify/create option 910. If no RFP on the list has been selected but the member selected the modify/create option 910, SM 240 provides a page with a blank RFP template for the member to input information for a new RFP.
• An RFP may be deleted using a procedure similar to that used to for an viewing RFP, except the member selects the delete option 915. As suggested, the corporation may only permit certain members to create and delete RFPs.
• the bid option 920 Another option available to members of the corporation is the bid option 920.
• This option when selected, provides details to the member on any bids that law firms have submitted in response to an RFP. Bids associated with an RFP may be viewed by using a procedure similar to that used to for viewing an RFP, except the member selects the bids option 920.
• the Q&A option 925 permits the member participate in the Q&A session associated with that RFP. For example, the member may view the questions and answers, respond to new questions, or modify existing answers.
• correspondence option 930 is used for members to view the correspondence, respond to new issues posted by the law firm, or modify previous responses.
• the member can select the logout option 935 to logout of the system.
• a stage which refers to the status of the RFP.
• the listed RFP "Federal Court Commercial Litigation” has at least one bid; the listed RFP “Age Discrimination Class Action Defense” has been awarded; and the listed RFP “Copyright Infringement Defense” is in the Q&A period. Law Firm Member Processing
• Law firm member options are depicted in the flow chart of Fig. 8.
• Options available to a law firm member include update profile 820, active bids processing 830, and active RFP processing 840.
• the difference between the active bids processing 830 and the active RFPs processing 840 is mainly the stage of the listed RFPs.
• the RFPs listed on the active bids page are those that have passed any Q&A period for which the member's law firm has submitted a bid.
• the active RFPs pages lists RFPs for which the ' member's law firm has not yet submitted a bid.
• SM 240 firm table 272C and populates a page with information associated with the member's law firm. The member may then modify then profile information and submit the information with any modifications to SM 240 to update database 272. As suggested above, SM 240 may limit the capability of members of a law firm to modify the corporation's profile to members satisfying the superlawyer relation.
• SM 240 When the member selects the active bids option (step 810, 830), SM 240 generates a page with a list of the member's law firm's active bids, in particular the list includes information on RFPs for which the law firm has submitted a bid and at least a date on which each bid was submitted.
• a page 1000 An example of such a page 1000 is shown in Fig. 10.
• the member may view the details of active bids by selecting a bid by filling in the circle next to the bid on the list and selecting the view option 1005.
• the details of a bid may be modified using the same procedure for viewing and selecting option 1010.
• the same option 1010 may also be used to create a new bid by selecting the option without identifying a particular bid on the list.
• a bid may be deleted using a procedure similar to that used to for viewing a bid, except the member selects the delete option 1015.
• the law firm may only permit certain members to create, modify and delete bids.
• Option 1020 is used to submit a bid.
• communications option 1025 is used for law firm members to view the communications, respond to new issues posted by the corporation, or modify previous responses.
• the member can select the logout option 1030 to logout of the system.
• Fig. 10 next to each of the listed active bids is summary information, including fee and submission date, and a stage, which refers to the status of the bid.
• summary information including fee and submission date
• a stage which refers to the status of the bid.
• the listed bid for an "Age Discrimination Class Action Defense" matter is in the bid stage and the law firms bid for a "Copyright Infringement Defense” matter has been awarded.
• SM 240 When the member selects the active RFPs option (step 810, 840), SM 240 generates a page with a list of RFPs for which the law firm may submit a responsive bid.
• RFPs on list are filtered in the sense that the list includes only RFPs that the corporations want the law firm to view. The filter can be based on qualifications of the law firm or any of its attorneys, or it can reflect the corporation's specific selection. An example of such a page 1100 is shown in Fig. 11.
• the member may view the details of active RFPs by selecting an RFP by filling in the circle next to the RFP information on the list and selecting the view option 1105.
• a similar procedure may be used to create a bid in response to an RFP. If an RFP is selected by filling in the circle next to the RFP information on the list and the member selects the create option 1110, SM 240 provides a page with a blank bid template for the member to input information for a new bid. If the law firm is still working on its bid, it is not yet considered an active bid and, therefore, the bid still appears in page 1100.
• the member can modify the terms of such a bid by selecting the RFP by filling in the circle next to the RFP information on the list and selecting option 1110.
• a bid may be deleted using a procedure similar to that used to for viewing a bid, except the member selects the delete option 1115.
• the law firm may only permit certain members to create, modify and delete bids.
• a corporation may specify that a particular RFP will have a Q&A period during which law firms and the corporation can exchange questions and answers about the RFP. If an RFP has such a Q&A period associated with it, the member may participate in the Q&A by selecting the RFP and the Q&A option 1120.
• communications option 1125 is used for law firm members to view the communications, respond to new issues posted by the corporation, or modify previous responses.
• the member can select the logout option 1130 to logout of the system.
• the listed bid for an "Age Discrimination Class Action Defense” matter is in the bid stage, the “Copyright Infringement Defense” matter has been awarded, and the "International Joint Venture - Software Developer” RFP is available to the law firm for a bid and is in the Q&A period.
• the systems and methods consistent with the present invention provide a forum through which buyers can purchase legal services from a variety of sellers.
• the present invention levels the playing field by giving buyers more power than they presently have in the buy-sell process.
• the RFP approval process has been described as a group of sellers receiving an RFP and separately determining whether to approve or reject it.
• SM 240 may contain a database of previously generated replies from the sellers. SM 240 may query the database using the terms of the RFP and obtain one or more replies to present to the buyer.
• aspects of the present invention are described as being stored in memory, one skilled in the art will appreciate that these aspects may also be stored on or read from other computer-readable media, such as secondary storage devices, like hard disks, floppy disks, or CD-Rom; a carrier wave from the Internet; or other forms of RAM or ROM.
• aspects of the invention are described in the context of providing legal services in particular, the invention is not so limited. Other types of services may be procured using the same forum-based approach, particularly services that, conventionally, rely on personal relationships for the selection of service providers.
• the forum-based approach may be used in the mortgage banking and investment industries.

Landscapes

• Business, Economics & Management (AREA)
• Accounting & Taxation (AREA)
• Finance (AREA)
• Development Economics (AREA)
• Economics (AREA)
• Marketing (AREA)
• Strategic Management (AREA)
• Physics & Mathematics (AREA)
• General Business, Economics & Management (AREA)
• General Physics & Mathematics (AREA)
• Engineering & Computer Science (AREA)
• Theoretical Computer Science (AREA)
• Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Applications Claiming Priority (3)

Publications (1)

Family

ID=23886108

Family Applications (1)

Country Status (3)

Cited By (1)

• 2000
  • 2000-12-22 AU AU18799/01A patent/AU1879901A/en not_active Abandoned
  • 2000-12-22 EP EP00981568A patent/EP1249000A2/de not_active Withdrawn
  • 2000-12-22 WO PCT/IB2000/001965 patent/WO2001050297A2/en not_active Application Discontinuation

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events