Attachment_1_Statement_of_Requirement.pdf

Statement of Requirements – Computer Assisted Legal Research Subscription

1.0. INTRODUCTION.

1.1. Organization.

1.1.1. Identification. Air Force Legal Operations Agency, Legal Information Services (AFLOA/JAS), 551 East Maxwell Blvd., Bldg. 500, Maxwell AFB AL 36112-6418.

1.1.2. Mission. The mission of JAS is to provide a broad range of computer and software products to the AF and Department of Defense (DoD) legal communities. JAS is the information technology office for the Air Force Judge Advocate General’s Corps (AFJAGC) and the Executive Agent for legal research for the DoD. In this capacity, AFLOA/JAS provides online legal research capabilities and routine and emergency legal support functions through technology to approximately 15,000 users throughout the federal government. As part of these functions, AFLOA/JAS also maintains over 60 different applications, many of which were developed in-house. We develop, test, and deploy enterprise IT applications supporting the AFJAGC core business processes.

1.2. Background and Objective.

As DoD Executive Agent, AFLOA/JAS provides computer-assisted legal research capability, both through its own Federal Legal Information Through Electronics (FLITE) system and through commercial database subscriptions. The purpose of this acquisition is to obtain online legal information sources; an interface between Government systems and the vendor databases for access; issuing user IDs and customized database usage reports; and related customer support services, such as training and telephone and online assistance for the legal personnel in the Air Force, Army, Marine Corps, Navy, Defense Logistics Agency (DLA) and Defense Contract Management Agency (DCMA). The primary requirement is for commercial items, primarily access to the required legal databases; the services are in support of these commodities. See the separate files in Appendices 5a and 5b for information on the amounts and types of commercial research activities performed during a month and during a 12-month period, respectively, under the current Air Force contract. Similar information on research activity for the Army is provided in Appendix 8a. This data is for informational purposes only. The Government does not represent that future research activity will remain the same as current activity.

1.3. Definitions.

See Appendix 1 for definitions of terms, including various groupings of users that are used to specify the scope of performance items, specifically AF Legal, AFLOA, Army Legal, Defense Contracts Management Agency (DCMA), Defense Logistics Agency (DLA), Electronic Clipping Service, FLITE, JAS, NonAF, SAF/GC, TJAGLCS, Navy Legal, United States, Users, USMC Legal, and Web.

1.4. Variation in Number of Users.

Estimated number of users for respective access to the various database offerings under this requirement are listed in the respective subparagraphs of paragraph 2.1 and summarized in Appendix 15. The government reserves the right to make minor adjustments in the final number of users for all CLINs (except CLINs X006, X009 and X012), not to exceed a 20% increase over the life of the contract, at no additional cost to the government.

2.0. DESCRIPTION OF SUBSCRIPTION PRODUCTS.

2.1. Required Database Offerings. The following database offerings shall be provided.

2.1.1. All Databases Menu.

Includes all databases that the Contractor provides on an all-inclusive, monthly basis, per user, or per classes of users or organizations, covering unlimited searching, browsing, printing, downloading, images, and electronic clipping service, as well as research software, training and support. These databases shall include the following:

Federal trial and appellate court decisions and rules; federal arbitration awards; military appellate court decisions and rules inclusive of Court of Appeal for the Armed Forces, Air Force Court of Criminal Appeals, Army Court of Criminal Appeals, Navy-Marine Corps Court of Criminal Appeals, Coast Guard Commandant Decisions on Appeal, the United States Coast Guard Court of Criminal Appeals and the Uniform Code of Military Justice;

Federal Appellate Court briefs, state appellate court decisions and state court rules; annotated United States Code;

Federal Register and Code of Federal Regulations; state statutory codes and administrative codes; legislative history including the Congressional Record; Federal administrative agency decisions including those of the Comptroller General, the Merit Systems Protection Board, the Equal Employment Opportunity Commission, the Federal Labor Relations Authority, the Office of Personnel Management Compensation and Leave Decisions, all of the Boards of Contract Appeals and Employee Benefits Security Administration; opinions of the U.S. Attorney General and the Office of Legal Counsel; state agency and attorney general opinions; admiralty and maritime resources including United States and United Kingdom cases and arbitration decisions; litigation materials including jury instructions; international law materials including United Nations documents, international treaties and agreements, legislation and court decisions of other countries, and European Union (EU) documents and publications; legal citators; secondary sources such as treatises, legal encyclopedias, law reviews, journals, and commentaries with focus on government procurement and military and federal procedures, foundations, evidence and techniques; images from U. S. patent and trademark applications; bill tracking; Internal Revenue Service issuances; current and archived major newspapers, journals, magazines, and wire services; public records and filings, including real property ownership records, tax, judgment, and Uniform Commercial Code (UCC) filings, professional and driver’s licenses, motor vehicle, boat, and aircraft information, and credit header information; corporate, partnership, Dunn & Bradstreet and (DBA)/fictitious business name filings; Social Security number files; people locator databases including address and phone number files; financial; medical (including medical journals); and other materials. This Menu shall include all databases described by the vendor as premier or premium, or exclusive to that vendor, its parent or subsidiaries, if offered to other United States federal government agencies for unlimited usage at a fixed price. If during the term of this contract, databases are added to the Contractor’s most inclusive fixed-price, unlimited usage database subscription offered to other Federal agencies, they shall automatically be added to this “All Databases Menu” portion of the contract at no additional cost to the Government. List the Database titles and descriptions in Exhibit A.

2.1.2. Docket Database.

Docket research capability includes the ability to search docket information on cases in pending state and Federal courts, obtain automatic notification of new cases that meet particular criteria, obtain automatic notification of changes in the status of particular cases being tracked, and print and download court documents filed electronically in such cases. Such access shall be unlimited for identified users. List included databases and services in Exhibit B.

2.1.3. Fully Accredited ABA Law School Package.

The Contractor shall provide any additional databases and services that it currently makes available to other ABA-accredited law schools that are not included in the "All Databases Menu" to the staff, faculty, and students at The Army Judge Advocate General's Legal Center and School (TJAGLCS). The Contractor will coordinate with the TJAGLCS to ensure access to these additional databases and services under this section in addition to the package provided to Army Legal. List these databases and services in Exhibit C.

2.1.4. United Kingdom Databases

The Contractor shall offer to the Air Force, United Kingdom specific databases that the Contractor or its parent company or subsidiaries provides on an all-inclusive, monthly basis, per user or per classes of users or organizations, covering unlimited searching, browsing, printing, downloading, images, and electronic clipping service, as well as research software, training and support. UK Practice areas that must be covered include employment law, contract law, health and safety, criminal law, civil litigation and procedure, real property law including leases and landlord tenant law, tort law, personal injury and international law and conflict of laws.

Databases shall include at a minimum access to current UK and EU legislation; UK case law including Industrial Relations Law Reports and All England Law Reports; forms and precedents for drafting employment policies, contracts and leases such as the Encyclopedia of Forms and Precedents and Harvey on Industrial Relations and Employment Law; access to authoritative works including but not limited to Harvey on Industrial Relations and Employment Law, Tolley’s Employment Law Service, Encyclopedia of Forms and Precedents, Butterworth’s Employment Law Handbook, Harvey Employment Precedents, Halsbury’s Laws of England, Hill and Redman’s Law of Landlord and Tenant, The Civil Court Practice (the green book), Butterworth’s Property Law Service, Tolley’s Employment Law Service, Blackstone’s Criminal Practice, Redgrave’s Health and Safety, and Stone’s Justice Manuel; access to legal journals such as the New Law Journal. These databases, will be provided to a maximum of 5 AFJAGC users located within the United States Air Force Europe Major Command (USAFE).

This set of databases shall be ordered as a separate option for each year of the contract. List these databases and services in Exhibit D.

2.1.5. Medical Malpractice Databases.

The Contractor shall offer access to databases and services focused on the assessment, adjudication, litigation and settlement of medical malpractice claims. Such access shall include at a minimum secondary titles focused on legal, medical & scientific information tied to verdicts & settlements; full text medical & scientific journals, medical/injury images, expert witness information by jurisdiction & topical area, clinical medical key, standards of care analysis to a claim, case value assessment by medical claim, injury specific verdicts & settlements, expert witness CVs, and medical claims trial transcripts. List these databases and services in Exhibit E.

2.1.6. Insurance and Claims Databases.

The Contractor shall offer access to databases and services focused on information relevant to medical claims and insurance recovery programs and general tort claims processing and adjudication. These databases shall be in addition to the general people search databases described in paragraph 2.1.1. Such databases shall include at a minimum access to police, accident and moving violations reports, driver’s licenses and motor vehicle registration, car accident history, court filings prior and current medical and carrier recovery claims filed by claimants. List these databases and services in Exhibit F.

2.1.7. Transaction Priced Databases.

The Contractor shall offer all other databases currently included in the Contractor’s system or added at any time during the contract period at either a standard or discounted per-search rate. This per search rate shall include access to the databases, searching, browsing, printing, and downloading. List these databases in Exhibit G.

2.1.8. Database Change Report.

The Contractor shall provide, by e-mail, to the User Primary and Alternate POCs (see paragraph 4.5) a report, at least quarterly, in Excel spreadsheet format, indicating all files that have been added to or removed from the “All DataBases Menu,” “Docket Databases,” “United Kingdom databases,” “Medical Malpractice Databases,” “Insurance and Claims Databases” and “Transaction Priced Databases” file groupings.

2.2. Specialized User Groupings. Throughout the period of performance, minor variances in user numbers and/or locations may occur through customer reorganization, including opening, closure, or transfer of offices and personnel.

2.2.1. AF Legal.

AFLOA/JAS shall establish offices for usage reporting, and User IDs shall be issued according to the procedures described in paragraph 2.5.1.

2.2.1.1. All AF Legal users shall have unlimited access to the All Databases Menu described in paragraph 2.1.1 and access with approval of AFLOA/JAS to the Transaction Priced Databases Menu described in paragraph 2.1.7. Approximate number of users is 4,500.

2.2.1.1.i. In addition to the databases listed in paragraph 2.2.1.1, users assigned to AFLOA will also have access to the Docket Database described in paragraph 2.1.2. Approximate number of users is 550.

2.2.1.1.ii. In addition to the databases listed in paragraph 2.2.1.1, users assigned to USAFE UK and specifically designated by AFLOA/JAS will also have access to the UK databases described in paragraph

2.1.4. Approximate number of users is 5.

2.2.1.1.iii. In addition to the databases listed in paragraph 2.2.1.1, users assigned to the AFLOA Claims and Torts Division, Medical Law Branch and specifically designated by AFLOA/JAS will also have access to the Medical Malpractice Databases described in paragraph 2.1.5. Approximate number of users is 10.

2.2.1.1.iv. In addition to the databases listed in in paragraph 2.2.1.1, users assigned to the AFLOA Claims and Torts Division, General Torts Branch, Medical Cost Reimbursement Program (MCRP) Branch and MCRP Regional Offices shall have access to the Insurance and Claims Databases described in paragraph 2.1.6. Approximate number of users is 100.

2.2.1.2. SAF/GC. AFLOA/JAS shall establish the office for usage reporting, and User IDs shall be issued according to the procedures described in paragraph 2.5.1. SAF/GC users shall have unlimited access to the All Databases Menu described in paragraph 2.1.1. Approximate number of users is 100.

2.1.2.3. NonAF. AFLOA/JAS shall establish offices for usage reporting, and User IDs shall be issued according to the procedures described in paragraph 2.5.1, except that the Contractor need not provide access to a new user until the first day of the month after receipt of the electronic file containing the necessary information.

Charges for those IDs will begin to accrue on the date they have access. NonAF offices will be identified under an artificial “Major Command” and shall have unlimited access to the All Databases Menu described in paragraph 2.1.1.

2.2.2. Army Legal.

The Army shall establish offices for usage reporting, and User IDs shall be issued according to the procedures described in paragraph 2.5.2.

2.2.2.1. All Army users shall have unlimited access to the All Databases Menu described in paragraph

2.1.1 and access with approval of the Army POC to the Transaction Priced Databases Menu described in paragraph 2.1.7. Approximate number of users is 9,500.

2.2.2.1.i In addition to the access described in paragraph 2.2.2.1, Army users assigned to TJAGLCS shall also have access to the Fully Accredited ABA Law School Package described in paragraph 2.1.3.

Approximate number of users is 150 staff and faculty and 250 stationed students (OBC/Grad Course).

2.2.2.1.ii. In addition to the access described in paragraph 2.2.2.1, users designated by the Army shall also have access to the Docket Database described in paragraph 2.1.2. Approximate number of users is 60.

2.2.2.1.iii. In addition to the access described in paragraph 2.2.2.1, users designated by the Army shall also have access to the Medical Malpractice Databases described in paragraph 2.1.5. Approximate number of users is 150.

2.2.3. Marine Corps (USMC) Legal.

The Marine Corps shall establish offices for usage reporting, and User IDs shall be issued according to the procedures described in paragraph 2.5.3.

2.2.3.1. All USMC Legal users shall have unlimited access to the All Databases Menu described in paragraph 2.1.1. Approximate number of users is 1,100.

2.2.4. Navy Legal.

The Navy JAG Corps shall establish offices for usage reporting, and User IDs shall be issued according to the procedures described in paragraph 2.5.4.

2.2.4.1. All Navy Legal users shall have unlimited access to the All Databases Menu described in paragraph 2.1.1 and the Docket Database described in paragraph 2.1.2 and, with approval of Navy Legal POC, to the Transaction Priced Databases Menu described in paragraph 2.1.7. Approximate number of users is 2,400.

2.2.5. Defense Logistics Agency (DLA).

DLA shall establish offices for usage reporting, and User IDs shall be issued according to the procedures described in paragraph 2.5.5.

2.2.5.1. All DLA users shall have access to the All Databases Menu described in paragraph 2.1.1.

Approximate number of users is 200.

2.2.6. Defense Contract Management Agency (DCMA).

DCMA shall establish offices for usage reporting, and User IDs shall be issued according to the procedures described in Sec 2.5.6.

2.2.6.1. All DCMA users shall have access to the All Databases Menu described in paragraph 2.1.1.

Approximate number of users is 136.

2.2.6.1.i. In addition to the access described in paragraph 2.2.6.1, users designated by DCMA shall also have access to Docket Database described in paragraph 2.1.2. Approximate number of users is 5.

2.2.7. Defense Contract Audit Agency (DCAA).

2.2.7.1. All DCAA users shall have access to the All Databases Menu described in paragraph 2.2.1.

Approximate number of users is 90.

2.3. User Interface & Access Methods.

2.3.1. Menu Structure.

Give users access to all databases that their Specialized User Grouping is authorized to access by means of one menu or a hierarchical set of menus. When a user connects to the Contractor’s system, the Menu appropriate to that user’s access authority shall be displayed automatically. The user shall have the capability to navigate among the authorized database menus within a single online session or Web browser session.

The Menus shall indicate to the users which databases are subject to transaction pricing so that they can make informed decisions. This objective may be accomplished by placing a $ symbol before the database names or by other display attributes that clearly identify them as being subject to additional charges. Databases not included in a user’s subscription shall not be visible to the user or masked so as to make clear that the user is not entitled to that database, whether part of the All Database offerings, transactional priced offerings, or other specialized file grouping.

2.3.2. Access Methods. All web interfaces offered to any federal entity--executive, legislative or judicial—shall be available to users under this contract.

Provide access to the specialized file groupings described in paragraph 2.1, above, in accordance with the requirements as described below.

2.3.2.1. Direct Via Web Browser. Provide access through the Internet using a standard Web browser to all of the Contractor’s databases that are accessible online.

2.3.2.2. Access through the FLITE Web Server for Air Force Legal, SAF/GC, and NonAF.

(a) Provide access through the Web Server that hosts the Federal Legal Information Through Electronics (FLITE) system. Users already authenticated by the FLITE system shall not be required to enter a Contractor User ID and password (“transparent” or “single sign-on” access). With single sign-on the user authenticates to the Contractor’s Web-based system only and has direct access to the application. The Contractor will identify the single sign-on protocols that they support in their proposal. The Air Force will provide user information, including FLITE User IDs in accordance with paragraph 2.5, to facilitate single sign-on after contract award.

Once single sign-on is implemented, users shall have the same capability of setting search and display options as when authenticating directly to the Contractor’s Web-based system independently of the FLITE system. When a FLITE user selects the appropriate link in a FLITE Web page, the user will be presented with the top-level menu of the Contractor’s system. The Contractor will have this functionality in place within ninety (90) days of contract start date.

(b) Provide the technical information related to its Web-based system required by AFLOA/JAS to implement the types of retrieval described above as well as a technical point of contact. Such information will include Uniform Resource Locators (URLs), command syntax, and parameters. The Contractor shall have no responsibility for the FLITE application itself.

(c) Whenever the Contractor modifies its production Web system in a way that affects the capabilities described in Paragraphs (a)(1) above, it shall do so in a manner that supports these capabilities. At least 30 days before the modification goes into production, the Contractor shall provide to AFLOA/JAS any technical information necessary for the FLITE application to continue these capabilities.

(d) Test changes to its system to assure that the functionality of the access through the FLITE Web server is not impaired or diminished.

(e) Document the method used to provide access to its system through the FLITE web server in order to facilitate maintenance and support and provide a copy of this documentation to the AFLOA/JAS Primary POC.

2.3.2.3 Access through JAGCNet for Army Legal.

(a) Provide access through the Web Server that hosts the U. S. Army Judge Advocate General’s Corps legal information technology and knowledge management portal (JAGCNet). Users already authenticated by the JAGCNet system shall not be required to enter a Contractor User ID and password in either the standard or advanced versions of the product. The Contractor will have this functionality in place within ninety (90) days of contract start date. The Contractor shall ensure that each user’s access is uniquely authenticated in order to determine the identity of the user, provide access to the menu authorized for that user, and allocate usage to the user in the reports discussed in paragraph 2.6.2.1. Users shall have the same capability of setting search and display options as when authenticating directly to the Contractor’s Web-based system independently of JAGCNet. When a JAGCNet user selects the appropriate link in a JAGCNet Web page, the user will be presented with the top-level menu of the Contractor’s system. The Contractor shall provide to the Army technical POC (see paragraph 4.5.3) the technical information related to its Web-based system required by the Army to implement this access including Uniform Resource Locators (URLs), command syntax, and parameters.

(b) Whenever the Contractor modifies its production Web system in a way that affects the capabilities described in this Section, it shall do so in a manner that supports these capabilities. At least 30 days before the modification goes into production, the Contractor shall provide to the Army technical POC any technical information necessary for the JAGCNet application to continue these capabilities.

(c) Test changes to its system to assure that the functionality of the access through the JAGCNet is not impaired or diminished.

(d) Document the method used to provide access to its system through the JAGCNet web server in order to facilitate maintenance and support and provide a copy to the Army technical POC (see paragraph 4.5.3) at least 30 days before performance begins.

2.3.2.4. USMC access.

(a) The Contractor shall provide the ability to access databases directly via a Web browser.

(b) The Contractor shall provide to the USMC technical POC (see paragraph 4.5.4) the technical information related to its Web-based system required to implement the types of retrievals described above as well as a technical point of contact. Such information will include Uniform Resource Locators (URLs), command syntax, and parameters. Whenever the Contractor modifies its production Web system in a way that affects the capabilities described above, it shall do so in a manner that supports USMC access and shall provide to the USMC technical POC, at least 30 days in advance of the date the modification goes into production, any technical information necessary to continue these capabilities. The Contractor shall test changes to its system to assure that functionality of access is not impaired or diminished.

2.3.2.5. Navy Legal access.

(a) The Contractor shall provide the ability to access databases directly via a Web browser.

(b) The Contractor shall provide to the Navy technical POC (see paragraph 4.5.5) the technical information related to its Web-based system required to implement the types of retrievals described above as well as a technical point of contact. Such information will include Uniform Resource Locators (URLs), command syntax, and parameters. Whenever the Contractor modifies its production Web system in a way that affects the capabilities described above, it shall do so in a manner that supports Navy access and shall provide to the Navy technical POC, at least 30 days in advance of the date the modification goes into production, any technical information necessary to continue these capabilities. The Contractor shall test changes to its system to assure that functionality of access is not impaired or diminished.

2.3.2.6. DLA Access.

(a) The Contractor shall provide the ability to access databases directly via a Web browser.

(b) The Contractor shall provide to the DLA technical POC (see paragraph 4.5.6) the technical information related to its Web-based system required to implement the types of retrievals described above as well as a technical point of contact. Such information will include Uniform Resource Locators (URLs), command syntax, and parameters. Whenever the Contractor modifies its production Web system in a way that affects the capabilities described above, it shall do so in a manner that supports DLA access and shall provide to the DLA technical POC, at least 30 days in advance of the date the modification goes into production, any technical information necessary to continue these capabilities. The Contractor shall test changes to its system to assure that functionality of access is not impaired or diminished.

2.3.2.7. DCMA Access.

(a) The Contractor shall provide the ability to access databases directly via a Web browser.

(b) The Contractor shall provide to the DCMA technical POC (see paragraph 4.5.7) the technical information related to its Web-based system required to implement the types of retrievals described above as well as a technical point of contact. Such information will include Uniform Resource Locators (URLs), command syntax, and parameters. Whenever the Contractor modifies its production Web system in a way that affects the capabilities described above, it shall do so in a manner that supports DCMA access and shall provide to the DCMA technical POC, at least 30 days in advance of the date the modification goes into production, any technical information necessary to continue these capabilities. The Contractor shall test changes to its system to assure that functionality of access is not impaired or diminished.

2.3.2.8. DCAA Access.

(a) The Contractor shall provide the ability to access databases directly via a Web browser.

(b) The Contractor shall provide to the DCAA technical POC (see paragraph 4.5.8) the technical information related to its Web-based system required to implement the types of retrievals described above as well as a technical point of contact. Such information will include Uniform Resource Locators (URLs), command syntax, and parameters. Whenever the Contractor modifies its production Web system in a way that affects the capabilities described above, it shall do so in a manner that supports DCAA access and shall provide to the DCAA technical POC, at least 30 days in advance of the date the modification goes into production, any technical information necessary to continue these capabilities. The Contractor shall test changes to its system to assure that functionality of access is not impaired or diminished.

2.3.3. Search and Retrieval Capabilities.

2.3.3.1. Retrieving Documents by Citation.

Many of the databases specified in paragraph 2.1.1 are made up of documents, each with one or more standard forms of citation (e.g. 480 U.S. 102, Revenue Ruling 88-1, 5 United States Code 1). For such databases, the system shall allow the user to select directly a document for browsing and/or retrieval by specifying the document according to the citation form prescribed in the most recent edition of The Bluebook: A Uniform System of Citation; or according to any additional or different citation form required or recognized by the relevant court, agency, forum or jurisdiction.

2.3.3.2. Searching. The system shall accommodate both term and operator searching and natural language searching of the selected database(s). Additionally, irrespective of the search methodology used, the system must permit the user to modify search terms used to modify or narrow the results returned.

2.3.3.2.i. Term and Operator Searching. Term and operator searching shall permit the user to search using the following conventions:

(a) Boolean search operators equivalent to AND, OR, and AND_NOT.

(b) Proximity search operators that express the nearness of two search terms.

(c) Both infix (e.g., m*n is equivalent to man OR men) and postfix (e.g., litiga*** is equivalent to litigant or litigate) wildcard characters in search terms.

(d) The ability to restrict a search to a specified document segment/field (e.g., court, judge, opinion date, case name, or opinion in a database of court opinion documents).

(e) The ability to recall to the screen the previous search expression entered by the user, modify the expression, and execute the modified search expression, or base a search on the result of a prior search.

2.3.3.2.ii. Natural Language Searching. Users must be able to search the selected database using English language sentences or phrases.

2.3.3.3. Browsing. The system shall provide the following minimum set of document browsing facilities:

(a) The ability to display a single document retrieved by citation.

(b) The ability to display a single document from the set of documents returned in response to a search request with each occurrence of each term used in the search request highlighted for easy identification.

(c) The ability to page forward or backward through a single displayed document one screen at a time.

(d) The ability to move forward or backward through a single displayed document viewing only those screens that contain highlighted terms.

(e) The ability to display the document titles for the documents in a search result set (i.e., display a citation list).

2.3.3.4. Citators.

(a) The system shall provide at least two different types of citator facilities. At a minimum, both the case history citator and the general citator facilities described below shall be provided for all Federal court opinion databases.

(1) A case history citator shall provide case history, through the various appellate levels, on a case-by-case basis. The case history citator shall be updated on a daily basis so the most recent appellate action for each active case is available.

(2) A general citator shall provide a more in-depth treatment of each case/opinion than the case history citator. The general citator shall include a comprehensive list of references to each case/decision in other court opinions, law reviews, and other applicable publications. For referencing documents that are presented in a volume/page format (e.g., 315 U.S. 649), the page number on which the primary reference occurs must be presented (e.g., 315 U.S. 649 at page 656 or 315 U.S. 656).

(b) For both citators, the system shall allow the user to request a citator/case history display for a single displayed court decision or to enter the citation of the desired decision. When a citator/case history is displayed, the system shall be capable of presenting the full text of a referencing document included on the display, if that document is available in a database provided by the Contractor.

(c) The Contractor’s system shall provide both citators for all non-Federal court opinion databases for which it currently provided citators to other Federal agencies. List these databases in Exhibit H.

2.3.3.5. Printing, Downloading and E-mail. The system shall provide the following capabilities and facilities:

(a) The ability to download and print, as a single operation, one or more selected documents to a printer connected (either directly or as a shared network device) to the user’s workstation.

(b) The ability to download one or more selected documents to the user's workstation and store the documents in a user-specified disk file for later printing or manipulation through a word processing program.

(c) Unlimited printing and downloading of retrieved documents at no additional charge, including all PDF formats, subject to copyright and licensing restrictions in the final contract. Downloading formats shall at a minimum, include Microsoft Word and ASCII text.

(d) The ability to e-mail the following to one or more users (subject to any limitations of the user’s and recipient’s e-mail systems): One or more selected documents, as a single operation; multiple lists of search results; links to selected documents; and citator results.

2.3.3.6. Automatic Search and Retrieval. Provide an Electronic Clipping Service, as defined in Appendix 1, at no additional charge.

2.3.4. Availability.

(a) The Contractor's web-based legal research system shall normally be available to all users around the clock, 24 hours a day, seven days a week, every day of the year. “Available” is defined as the system allowing any authorized user to log onto the Contractor's system, search any database file(s), and retrieve and download the requested information.” The system shall be available, on a monthly basis, so that system downtime is no greater than five (5) hours of the required period of system availability per month. “System downtime” is that period of time when the system is not fully available to authorized users due to a malfunction or limitations in the Contractor's equipment, software, or telecommunications connections. Lack of system availability due to unusual, unforeseen circumstances (e.g., weather-related outages, utility system disruptions, natural disasters, or other acts of God) shall not be considered system downtime.

(b) Should the system require additional planned downtime, the Contractor will provide the Government at least five business days advance notice and schedule the downtime between the hours of 9 P.M. and 5 A.M. Eastern time Monday through Saturday or between 1 A.M. and 1 P.M. Eastern time Sunday. The Contractor shall perform all routine maintenance and updates during this time or during system downtime described in paragraph

(a) above.

(c) The Contractor will measure system downtime on a monthly basis and submit a report of such downtime via email to the User Primary and Alternate POCs (Section 4.5) no later than the date the invoice is submitted.

2.4. Customer Support.

Provide technical assistance and answer questions concerning research strategies, database fields, software usage, and other types of questions related to the use of the Contractor’s products and services. The Contractor shall provide such assistance and customer support by toll-free call to users in, at a minimum, the following countries: United States (as defined in Appendix 1), Australia, Canada, England/United Kingdom, France, Germany, Japan, Mexico, and Taiwan. In those countries not provided toll-free numbers, customers must be able to obtain customer support through collect calls or through online or e-mail requests (including instant messaging or online chats) to which the Contractor provides a response within 60 minutes.

2.5. Training.

2.5.1. In General. Provide user training at no additional cost for persons covered by this contract at locations worldwide. After initial training, the Contractor shall continue to follow up on a routine basis to keep users informed as well as to provide advanced training. This training shall include content and use of databases, search and retrieval functions (including printing and downloading functions), and effective legal research strategies. All instructors provided by the Contractor shall be experienced with the services and products furnished under this contract, and the training shall be limited to those products and services. See Appendices 2a, 7, 10, 11, 12, 13 and 14 for a list of current user locations.

Because of the inherent nature of military legal work, office locations and staffing levels will fluctuate constantly. The Contractor will accommodate such changes, including the opening or closure of offices and changes in the number of assigned personnel, at no additional cost to the government and provide training to all existing locations and covered users.

Work with users to set up mutually agreeable dates for initial training and any follow up training as needed. The frequency of training may vary by location or time of year. Where possible, the same training event should include users from different agencies.

2.5.2. The Contractor shall provide on-site training to the following locations:

2.5.2.1. Within the geographic territories of locations where the Contractor has training representatives and where at least five users are stationed. List these locations in Exhibit I.

2.5.2.2. National Capitol Region (NCR). Training shall be provided on-site for all Army, Navy, Marine, DLA, DCMA, DCAA and Air Force legal offices within the NCR (including the Pentagon, Arlington, Rosslyn, Joint Base Anacostia-Bolling, Joint Base Andrews-Naval Air Facility Washington, Ballston, Ft. Richie, Ft. Belvoir, Ft. Meade, Ft. Myer, and Ft. McNair) and, if available facilities exist, at an office of the Contractor located within the NCR.

2.5.2.3. Wright-Patterson AFB. Training shall be provided on-site or at an office of the Contractor within for all customer legal offices within the Dayton, Ohio, metropolitan area.

2.5.2.4 Schools. Provide training for the instructors at the Air Force JAG School at Maxwell AFB, Alabama; the Department of Law at the U.S. Air Force Academy in Colorado Springs, Colorado; the Department of Law and the Office of the Staff Judge Advocate at the United States Military Academy, West Point, NY; The Judge Advocate General’s Legal Center and School, U.S. Army, at Charlottesville, Virginia; for Navy and USMC users at the Naval Justice School, Newport, Rhode Island; and for all other user legal offices at these locations. Additionally, the Contractor must provide training at courses for new JAG officers entering the Air Force, Army, Navy and Marines (commonly called basic courses or schools); for paralegals in the basic, intermediate, and advanced skill level courses; for the Army’s in-resident LL.M. courses; and for other students.

2.5.2.5. AFLOA/JAS. Provide specialized onsite training for AFLOA/JAS personnel at Maxwell AFB, Alabama.

2.5.2.6. Other locations: For training in other locations or for locations with less than five users, the Contractor shall provide training either on-site, online (e.g., webinars, podcasting or other interactive method), or by telephone (including video teleconferencing).

2.5.3. Online training. Provide user training at no additional cost for persons covered by this contract. At a minimum, this training shall include content and use of databases, search and retrieval functions (including printing and downloading functions), and effective legal research strategies. A description of any additional training for no additional cost, such as topical legal subjects and Continuing Legal Education courses should be described in the proposal.

2.5.4 Conference Support. Conduct on-site training at Air Force, Army JAG, Navy JAG, Marine Legal, DLA, DCMA and DCAA legal conferences and group events when given at least two weeks’ notice and time on the conference agenda. Otherwise, the Contractor shall upon request supply copies of training literature for the event.

2.5.5. Literature. At a minimum, the Contractor shall provide updated training material to every user office location annually during each year of the contract at no additional charge. Literature shall include, at a minimum, a user’s guide, a directory of research materials, and any available handouts with research tips. Additionally, upon a user’s request, the Contractor shall provide additional training materials in any requested, available format, such as online, e-mail, regular mail, or commercial delivery service, at no additional cost. Such distribution may be by any means including download from the Web, email, mail, commercial delivery service, or by Contractor representatives at training events.

2.6. Password/User ID Management.

2.6.1. Air Force.

2.6.1.1. As instructed by the Air Force through the transmission of files described in paragraph 2.6.1.2 below, the Contractor shall issue User IDs that identify the user by name, by office, and by Major Command or Major Command equivalent.

2.6.1.2. Within 30 days after award, the Air Force shall provide the Contractor with an initial electronic file of users to be authorized access, showing the FLITE User IDs and all identification information necessary to add users. Within 30 days after award, the Air Force shall also provide the Contractor with an initial electronic file of all offices in which users are located, showing office FLITE ID, Major Command, location information, and contact information. Thereafter, on a daily basis, the Air Force shall provide the Contractor with electronic files containing information needed to add new users, to delete users who should no longer have access, and to modify information about existing users, including the offices to which the users are assigned. This type of file is referred to herein as the AF User File. Also on a daily basis, the Air Force shall provide the Contractor with electronic files containing transactions to add offices, delete offices, or modify information about existing offices.

This type of file is referred to herein as the AF Office File. Specification of the file formats is contained in Appendix 3 of this SOR. The initial files containing all users and all offices will contain the same data elements as the daily files except that the “Action” field may be omitted. All files will be transmitted via an agreed-on protocol to a server address supplied by the Contractor.

2.6.1.3. Within one business day after the receipt of an AF User or Office File, the Contractor shall take the appropriate action (add, delete, modify) within the Contractor’s system and shall return to JAS an electronic file or email message in the agreed format reflecting the actions taken and specifying any file processing errors.

An acceptable format is shown in Appendix 4a of this SOR.

2.6.1.4. There shall be three accounts/billing groups, one for AF Legal, one for SAF/GC, and one for registered FLITE users other than AF Legal personnel. A fourth account may be established if deemed necessary by the Contractor to support the menu available for NonAF offices. Users shall retain the same User IDs when they move among offices within the same account.

2.6.1.5. For Web access through FLITE, authentication into the Contractor’s system shall be automatic based on the user’s FLITE ID as discussed in paragraph 2.2.2.2

2.6.1.6. At least once per week, the Contractor shall send to AFLOA/JAS a complete file of the Contractor User IDs issued under this contract in a mutually acceptable format, such as Microsoft Excel. This file shall also show the User’s name and FLITE ID (supplied previously by AFLOA/JAS pursuant to paragraph 2.5.1.). An acceptable format is shown in Appendix 4b of this SOR.

2.6.1.7. The Contractor and User Points of Contact (POC) (see paragraph 4.5.) may agree to modify the Password/User ID Management process to enhance efficiency, so long as the modification results in no change to the government’s financial obligations under this contract.

2.6.2 Army

2.6.2.1. As instructed by the Army through the transmission of files and https Post transactions described in paragraph 2.6.2.2 below, the Contractor shall issue User IDs that identify the user by name, by email address, and by Uniform Identification Code (UIC) of the office to which the user is assigned. Alternatively, should the Contractor have its own password management program that the Army finds acceptable, the Army and the Contractor may agree to use the Contractor’s program, at no additional cost to the government.

2.6.2.2. Within 30 days after award, the Army shall provide the Contractor with an initial electronic file of users to be authorized access, showing the name, prefix, suffix, email address, status, and UIC of the office to which the user is assigned. Within 30 days after award, the Army shall also provide the Contractor with an initial electronic file of all offices in which users are located, showing office name, office symbol, Uniform Identification Code (UIC), location information, and contact information. Thereafter, via xml/SOAP/https Post transactions, the Army shall submit to the Contractor transactions containing information needed to add new users, to delete users who should no longer have access, and to modify information of existing users, including the office to which the users are assigned. The Army shall also submit to the Contractor xml/SOAP transactions to add offices, delete offices, or modify information about existing offices.

2.6.2.3. Within one business day after the receipt of an Army User or Office File, the Contractor shall take the appropriate action (add, delete, modify) within the Contractor’s system. The Contractor will provide a response to each https Post transaction indicating transmission success or failure and after attempting to process transactions, shall return to the Army Technical POC (see paragraph 4.5) an email message in the agreed format reflecting the actions taken and specifying any processing errors. The Contractor may provide the https Post responses and user and office processing messages in any format acceptable to the technical POC and the Contractor.

2.6.2.4. There shall be two Army accounts/billing groups, one for The Judge Advocate General’s Legal Center and School (TJAGLCS ) and one for the rest of Army Legal. Users shall retain the same User IDs when they move among offices within the same account. Users in the TJAGLCS billing group shall have access to the Fully accredited ABA Law School Package specified in paragraph 2.1.3 in addition to the database products available to the rest of Army Legal. Specified users shall also have access to the Docket Database specified in paragraph 2.1.2, and such access shall be billed as a separate line item.

2.6.2.5. For Web access through JAGCNet, authentication into the Contractor’s system shall be automatic as discussed in paragraph 2.3.2.3.

2.6.2.6. At least once a month, the Contractor shall also send to the Army Technical POC (see paragraph 4.5) a file in a mutually acceptable format of the Contractor User ID changes made since the last file was sent. This file shall include the User information sent by the Army in the relevant xml transactions pursuant to paragraph 2.6.2.

2.6.2.7. The Contractor and Army Technical POC (see paragraph 4.5) may agree to modify the Army Password/User ID Management process to enhance efficiency at no additional cost to the government.

2.6.3. Marine Corps.

2.6.3.1. The Contractor shall provide each user with a unique identification number that in conjunction with a password will allow the authorized user access to the database.

2.6.3.2. Within 30 days after contract award, the USMC/JAD will provide the Contractor an initial list of users authorized to access the databases. Thereafter, on an as needed basis, the USMC shall provide the Contractor with an updated list as new users enter and current users exit the Marine Corps legal community.

2.6.3.3. Within one business day after the receipt of this updated list, the Contractor shall take the appropriate action (add, delete, modify) within the Contractor’s system and shall return to the USMC/JAD an electronic file or email message in an agreed-upon format reflecting the actions taken and specifying any file processing errors.

2.6.3.4. There shall be one account/billing group for the USMC legal community.

2.6.3.5. At least once per month, the Contractor shall send to USMC/JAD a complete file of the Contractor User IDs issued under this contract in a mutually acceptable format, such as Microsoft Excel.

2.6.3.6. The Contractor and User POC (see paragraph 4.5.) may agree to modify the Password/User ID Management process to enhance efficiency, so long as the modification results in no change to the government’s financial obligations under this contract.

2.6.4. Navy Legal.

2.6.4.1. The Contractor shall provide each user with a unique identification number that in conjunction with a password will allow the authorized user access to the database.

2.6.4.2. Within 30 days after contract award, the Office of the Judge Advocate General will provide the Contractor an initial list of users authorized to access the databases. Thereafter, on an as needed basis, the Navy JAG shall provide the Contractor with an updated list as new users enter and current users exit the Navy legal community.

2.6.4.3. Within one business day after the receipt of this updated list, the Contractor shall take the appropriate action (add, delete, modify) within the Contractor’s system and shall return to the Navy JAG an electronic file or email message in an agreed-upon format reflecting the actions taken and specifying any file processing errors.

2.6.4.4. There shall be one account/billing group for the Navy JAG legal community.

2.6.4.5. At least once per month, the Contractor shall send to the Navy Office of the Judge Advocate General a complete file of the Contractor User IDs issued under this contract in a mutually acceptable format, such…