Sol RFQ 05GA0A21Q0072 - Taxonomy final 9-8-2021.pdf

PDF 213 KB Posted Sep 9, 2021

Attached to: Taxonomy Replacement System
Solicitation number: 05GA0A21Q0072
Issued by: Government Accountability Office Acquisition Management

View the file

On GovTribe

Work with this file

Download the original file
Contacts named in this file
Similar government files
Ask GovTribe AI about this file

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

1 : :

Document Number: 05GA0A21Q0072 Page 1 of 37

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24 & 30

1. REQUISITION NUMBER

GAO2112030007

PAGE 1 OF

5. SOLICITATION NUMBER

05GA0A21Q0072

2. CONTRACT NO. 3. AWARD/EFFECTIVE DATE 4. ORDER NUMBER 6. SOLICITATION ISSUE

DATE

09/09/2021

7. FOR SOLICITATION INFORMATION

CALL:

a. NAME

HILL, LAVONNE Y

b. TELEPHONE NUMBER (No collect calls) 202-512-6125

8. OFFER DUE DATE / LOCAL

TIME

09/17/2021

12:00 ET

CODE 05GA0A

HILL, LAVONNE Y

ACQUISITION MANAGEMENT

441 G STREET, N.W.

ROOM 7N14U

ATTENTION:

WASHINGTON, DC 20548

9. ISSUED BY X UNRESTRICTED OR SET ASIDE: % FOR

SMALL BUSINESS

HUBZONE SMALL

BUSINESS

SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

WOMEN-OWNED SMALL BUSINESS (WOSB)

ELIGIBLE UNDER THE WOMEN-OWNED

SMALL BUSINESS PROGRAM

EDWOSB

8(A)

NAICS:

SIZE STANDARD:

10. THE ACQUISITION IS

SEE

SCHEDULE

11. DELIVERY FOR FOB DESTINATION

UNLESS BLOCK IS MARKED 0 Days: 0.00 %

0 Days: 0.00 % 0 Days: 0.00 % 0 Days: 0.00 %

12. DISCOUNT TERMS

13a. THIS CONTRACT IS

RATED ORDER UNDER DPAS

(15 CFR 700)

13b. RATING

X RFQ IFB RFP

14. METHOD OF SOLICITATION

CODE15. DELIVER TO CODE 05GA0A16. ADMINISTERED BY

HILL, LAVONNE Y

ACQUISITION MANAGEMENT

441 G STREET, N.W.

ROOM 7N14U

ATTENTION:

WASHINGTON, DC 20548

FACILITY

CODE

Telephone No.

17a. CONTRACTOR/

OFFEROR

05GA0ACODE18a. PAYMENT WILL BE MADE BY

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT SUCH ADDRESS IN

OFFER X SEE ADDENDUM

18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a UNLESS BLOCK BELOW IS

CHECKED

19. ITEM NO. 20. SCHEDULE OF SUPPLIES/SERVICES

(Use Reverse and/or Attach Additional Sheets as Necessary)

21. QUANTITY 22. UNIT 23. UNIT PRICE 24. AMOUNT

Request for Quotations (RFQ) This RFQ is to request for Taxonomy System

Replacement.

25. ACCOUNTING AND APPROPRIATION DATA

GAO-2021-0107A21DA0-1185BAA000-B03010002-31071-996151-2021

26. TOTAL AWARD AMOUNT (For Govt. Use Only)

X 27a. SOLICITATION INCORPORATES BY REFERENCE FAR 52.212-1, 52.212-4. FAR 52.212-3 AND 52.212-5 ARE ATTACHED. ADDENDA X ARE ARE NOT ATTACHED

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED. ADDENDA ARE ARE NOT ATTACHED

X 28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN 1 COPIES TO

ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND DELIVER ALL ITEMS SET FORTH

OR OTHERWISE IDENTIFIED ABOVE AND ON ANY ADDITIONAL SHEETS SUBJECT TO THE

TERMS AND CONDITIONS SPECIFIED.

29. AWARD OF CONTRACT: REF. _____________________________ OFFER

DATED _________________ . YOUR OFFER ON SOLICITATION (BLOCK 5)

INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE SET FORTH HEREIN,

IS ACCEPTED AS TO ITEMS:

30a. SIGNATURE OF OFFEROR/CONTRACTOR 31a. UNITED STATES OF AMERICA (SIGNATURE OF CONTRACTING OFFICER)

30b. NAME AND TITLE OF SIGNER (TYPE OR PRINT) 30c. DATE SIGNED 31b. NAME OF THE CONTRACTING OFFICER (TYPE OR PRINT) La Vonne Y. Hill

31c. DATE SIGNED

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

STANDARD FORM 1449 (REV. 02/2012)

Prescribed by GSA - FAR (48 CFR) 53.212

09/09/2021

Document Number: 05GA0A21Q0072 Page 2 of 37

19.

ITEM NO.

20.

SCHEDULE OF SUPPLIES/SERVICES

21.

QUANTITY

22.

UNIT

23.

UNIT PRICE

24.

AMOUNT

32a. QUANTITY IN COLUMN 21 HAS BEEN

RECEIVED INSPECTED ACCEPTED, AND CONFORMS TO THE CONTRACT, EXCEPT AS NOTED: _________________________________

32b. SIGNATURE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32c. DATE 32d. PRINTED NAME AND TITLE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32e. MAILING ADDRESS OF AUTHORIZED GOVERNMENT REPRESENTATIVE 32f. TELEPHONE NUMBER OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32g. E-MAIL OF AUTHORIZED GOVERNMENT REPRESENTATIVE

PARTIAL FINAL

33. SHIP NUMBER 34. VOUCHER NUMBER 35. AMOUNT VERIFIED

CORRECT FOR

COMPLETE PARTIAL FINAL

36. PAYMENT 37. CHECK NUMBER

38. S/R ACCOUNT NUMBER 39. S/R VOUCHER NUMBER 40. PAID BY

41a. I CERTIFY THIS ACCOUNT IS CORRECT AND PROPER FOR PAYMENT 42a. RECEIVED BY (Print)

41b. SIGNATURE AND TITLE OF CERTIFYING OFFICER 41c. DATE

42b. RECEIVED AT (Location)

42c. DATE REC'D (YY/MM/DD) 42d. TOTAL CONTAINERS

STANDARD FORM 1449 (REV. 02/2012) BACK

Document Number: 05GA0A21Q0072 Page 3 of 37

Table of Contents

Section Description Page Number

1 Continuation Sheet 01 Submission of Quotations

02 STATEMENT OF WORK (SOW) FOR ENTERPRISE TAXONOMY SYSTEM AND

IMPLEMENTATION

03 Evaluation Factors

2 Contract Clauses 01 52.212-4 Contract Terms and Conditions -Commercial Items (OCT 2018) 02 52.216-1 Type of Contract (Apr 1984 03 52.217-8 Option to Extend Services (Nov 1999) 04 52.217-9 Option to Extend the Term of the Contract (Mar 2000) 05 Electronic Invoicing and Payment Requirements - Invoice Processing Platform (IPP) (OCT 2017) 06 GAO 52.233-70 Disputes—Legislative Branch Agency (APR 2008) 07 Security Clause 08 GAO 52.237-71 Technical Directions (APR 1984) 09 GAO 52.237-72 Key Personnel (APR 1984) 10 Standard of Conduct 11 GAO 52.235·71 Confidentiality of GAO Data

3 Documents, Exhibits, or Attachments 01 GAO Non-Disclosure Agreement

Document Number: 05GA0A21Q0072 Page 4 of 37

Section 1 - Continuation Sheet

Request for Quotations (RFQ) This RFQ is to request for Taxonomy System Replacement.

Number Supplies or Services Qty Unit Unit Price Total (Inc. disc., tax, and fees)

1 Service

Firm Fixed Price

PSC: D

1.000000 LOT

Period of Performance:09/16/2021 - 09/15/2022

Description:Base Year Covers vendor transition and implementation of system. (This is a One-Time Cost) Support for transition from legacy software to incumbent’s software Support for implementation of software and connection to internal GAO systems

Reference Line:GAO2112030007 - 0001

Pricing Options:

Indicator: Base

Number Supplies or Services Qty Unit Unit Price Total (Inc. disc., tax, and fees)

2 Service

Firm Fixed Price

PSC: D

1.000000 LOT

Period of Performance:09/16/2021 - 09/15/2022

Description:Software Licenses and Support– BULK (LOE)

Software access and hosting Software support and updates Training, as needed

Reference Line:GAO2112030007 - 0002

Pricing Options:

Indicator: Base

Number Supplies or Services Qty Unit Unit Price Total (Inc. disc., tax, and fees)

101 Service

Firm Fixed Price

PSC: D

0.000000 LOT

Period of Performance:09/16/2022 - 09/15/2023

Description:Software Licenses and Support– BULK (LOE) Option Year 1

Software access and hosting Software support and updates Training, as needed

Reference Line:GAO2112030007 - 0101

Pricing Options:

Indicator: Option Option Period: 1

Document Number: 05GA0A21Q0072 Page 5 of 37

Number Supplies or Services Qty Unit Unit Price Total (Inc. disc., tax, and fees)

201 Service

Firm Fixed Price

PSC: D

0.000000 LOT

Period of Performance:09/16/2023 - 09/15/2024

Description:Software Licenses and Support– BULK (LOE) Option Year 2 Software access and hosting Software support and updates Training, as needed

Reference Line:GAO2112030007 - 0201

Pricing Options:

Indicator: Option Option Period: 2

Number Supplies or Services Qty Unit Unit Price Total (Inc. disc., tax, and fees)

301 Service

Firm Fixed Price

PSC: D

0.000000 LOT

Period of Performance:09/16/2024 - 09/15/2025

Description:Software Licenses and Support– BULK (LOE) Option Year 3

Software access and hosting Software support and updates Training, as needed

Reference Line:GAO2112030007 - 0301

Pricing Options:

Indicator: Option Option Period: 3

Number Supplies or Services Qty Unit Unit Price Total (Inc. disc., tax, and fees)

401 Service

Firm Fixed Price

PSC: D

0.000000 LOT

Period of Performance:09/16/2025 - 09/15/2026

Description:Software Licenses and Support– BULK (LOE) Option Year 4

Software access and hosting Software support and updates Training, as needed

Reference Line:GAO2112030007 - 0401

Pricing Options:

Indicator: Option Option Period: 4

01 Submission of Quotations

Document Number: 05GA0A21Q0072 Page 6 of 37

Basis for Award: The Government will award a single Purchase Order from this request for quote to the responsible Vendor whose quote conforming to the RFQ will be most advantageous to the Government based on Lowest Price Technically Acceptable (LPTA) Submit signed and dated offers, at or before the exact time specified in this Request for Quotation. All vendors who submit quotes must be registered in www.sam.gov,to be considered for award.

Questions must be submitted in writing and only via email to LaVonne Y. Hill at HillL@gao.gov. Written questions due no later than September 13, 2021 at 12:00 PM EST.

All quotations shall be submitted to LaVonne Y. Hill at HillL@gao.gov. The date and time for receipt of quotations is September 17, 2021, at 10:00 AM EST

As a minimum, Vendors must show—

(1) The request for quote number;

(2) The time specified in the request for quotation for receipt of quotes;

(3) The name, address, and telephone number of the Vendor;

(4) Acknowledgment of Request for Quote Amendments;

(5) Period for acceptance of quotations. The Vendor agrees to hold the prices in its offer firm for 90 calendar days from the date specified for receipt of quotations, unless another time period is specified in an amendment to the request for quotations.

02 STATEMENT OF WORK (SOW) FOR ENTERPRISE TAXONOMY SYSTEM AND IMPLEMENTATION

Section I. Introduction

GAO is an independent agency that functions as the investigative arm of the United States Congress. As part of its investigatory function and at the request of the US Congress, GAO analyzes and evaluates executive branch agency programs.

As part of its publishing process, GAO assigns both high-level topics and more specific taxonomy terms to GAO reports and testimonies. GAO also foresees creating additional taxonomies to categorize legal products, multimedia, and internal documents, among other collections.

The Center for Library Services Science (CLS), Applied Research and Methods (ARM), Government Accountability Office (GAO), is the business owner of GAO’s taxonomy program. The Center for Library Science requires a commercial off-the-shelf (COTS) taxonomy system. This requirement also includes the need for the migration of data into the new system and then on-going support and maintenance of the COTS system.

Section II. Purpose

This Statement of Work describes the characteristics of the type of product that will provide a reliable taxonomy server to aid GAO’s taxonomy program in the implementation and management of proper taxonomies across the GAO landscape. This software will replace current infrastructure and allow for the growth, expansion and innovation of existing and new libraries. GAO anticipates a successful vendor with a compatible product can be found in the commercial market place.

Section III. Background and Operating Environment

The following is a profile of the GAO’s current taxonomy environment:

Currently, GAO’s taxonomy program supplies information to the Product Metadata Repository, which supports discoverability of GAO products on GAO.gov. Our current taxonomy server is the 2012 version of SAS Enterprise Content Categorization (ECC). The taxonomy server runs its rules against the full text of GAO products and suggests terms to GAO contract staff. Staff then assign terms to products based on those suggestions.

Updates to the rules running has not occurred for three years due to lack of product support from the vendor. The taxonomy is also in a non-WC3 standard form, which makes it difficult to export and share with W3C compliant platforms. A new taxonomy is being designed in Microsoft Excel with the intention it will be ingestible into a new taxonomy system.

Document Number: 05GA0A21Q0072 Page 7 of 37

Section IV. Required System Components and General Functions

GAO requires the following high-level components and functionality:

A. Taxonomy Server and System Components

A.1 This taxonomy server and system component must comply easily integrate with other systems as described below:

A.1.1 The system must provide REST or SOAP web services.

A.1.2 The system must provide a database level API for integration into GAO internal systems and externally facing applications.

A.1.3 The taxonomy system must have a mechanism for accepting term suggestions and revisions through another system through web-based survey forms.

A.2 The system must be compliant with ANSI/NSIO Z39.19 and/or ISO 25964.

A.3 The system must use W3C standards for creating and editing taxonomies.

A.4 The system must have the ability to model vocabularies in SKOS and/or RDF.

A.5 The system modeling of ontologies must use OWL for its standard.

A.6 The system must meet the below accessibility standards as described below:

A.6.1 ISO/IEC 40500

A.6.2 W3C Web Content Accessibility Guidelines (WCAG) 2.0 Level AA

A.6.3 W3C Web Content Accessibility Guidelines (WCAG) 2.1 Level AA

A.6.4 Applicable revised Section 508 Standards

A.7 The taxonomy system must accept and output a variety of file formats as described below:

A.7.1 Import formats must include: .csv, .txt, RDF, SKOS

A.7.2 Export formats must include: .csv and/or .txt

A.7.3 Export formats must include: RDF (RDF/XML or Turtle serialization ) and/or SKOS format

A.8 The taxonomy system must support a robust and flexible yet straight-forward system for assigning roles and permissions to staff functions as described below:

A.8.1 The system must allow creation of at least five (5) user accounts that allow for the permission levels below:

A.8.1a The system must allow permissions assignment at the term level.

A.8.1b The system must allow at least these permissions levels:

A.8.1c Read-only access

A.8.1d Comment only access

A.8.1e Editor access

A.8.1f System administrator access (control for all system permissions)

Document Number: 05GA0A21Q0072 Page 8 of 37

A.9 The taxonomy system must be flexible for various knowledge organization and representation schemes’ creation, revision, and management as described below:

A.9.1 Controlled vocabularies

A.9.2 Taxonomies

A.9.3 Thesauri

A.9.4 Named entity lists

A.10 The system must have the following features for term and concept creation and revision:

A.10.1 Creation of unique identifiers for all concepts.

A.10.2 Ability to develop a concept’s properties, labels, and relationships from a single screen.

A.10.3 Ability to edit hierarchies with drag-and-drop

A.10.4 Ability to create poly-hierarchical structures (multiple inheritance)

A.10.5 Ability to create global edits, across taxonomies, to:

A.10.5a Concept attributes

A.10.5b Concept relationships

A.10.6 Ability to browse records:

A.10.6a Alphabetically

A.10.6b Hierarchically

A.10.6c Chronologically (Date created and Date last edited)

A.10.6d Ability to search and filter records by:

A.10.6e Keywords (exact, fuzzy or phrase searching)

A.10.6f Approval/review status

A.10.6g Date created and/or modified

A.10.6h Preferred/non-preferred term status

A.11 The system must have automatic mechanisms for:

A.11.1 Prevention of term duplicates (disambiguation)

A.11.2 Reciprocal relationships

A.11.3 Prevention of circular references

A.11.4 Prevention of non-preferred terms from hierarchical and associative relationships

A.11.5 Detection of orphan terms

A.12 The system must manage the quality control, production, and archival versions of vocabularies or collections of vocabularies.

Document Number: 05GA0A21Q0072 Page 9 of 37

A.13 The taxonomy system must be integrated with an auto-categorization mechanism to classify documents with terms stored within it as described below:

A.13.1 The taxonomy module and the auto-categorization module must be preconfigured to be integrated when the software is implemented.

A.13.2 The auto-categorization module must provide relevancy scoring for terms present in the taxonomy module as follows:

A.13.1a The scoring must be provided on both an individual document and multiple document basis.

A.13.1b Users must be able to select tagging for documents based on the scoring provided.

B.Auto-Categorization Components

B.1 This auto-categorization component must meet the requirements listed below:

B.1.1 The module must have a mechanism for writing classification rules with:

B.1.1a Boolean logic (AND, OR, NOT);

B.1.1b Proximity (x within # words of y);

B.1.1c Truncation/wildcards (crim* for crime, criminal, etc.); and

B.1.1d Regular expressions.

B.2 The module should offer at least one preloaded statistical models for classification and include the following documentation:

B.2.1 How the classifier was trained;

B.2.2 Its prediction statistics;

B.2.3 The ability of the model to be retrained with additional data

Section V. Requirements for Specific Tasks and Components

A. Transition to New System

As GAO migrates from its current taxonomy server, the vendor shall provide the following to facilitate the transition:

A.1 The vendor shall supply the name and contact information for a dedicated point of contact for customer service and technical issues (Technical POC) within 2 business days of signing the contract. The Technical POC must provide a non-automated response within 1 business day after being contacted with an issue during the first 3 months of the contract or until the migration is successfully completed.

A.2 The vendor shall provide written system documentation, describing all functions of all modules included in the software as configured for GAO.

A.3 The vendor shall provide initial training to the GAO taxonomy team that will cover all aspects of the system.

B. .System Architecture and Security

The system must meet the security requirements listed below:

B.1 All information entered into the system by GAO is to be owned by GAO. GAO retains the right to export, import, alter, and back-up data while using the software.

B.2 The vendor must adhere to records requirements, as detailed by GAO Privacy Program Order, 0450.1, GAO Records Management Program Order 0410.1 and GAO’s Records Retention Schedules.

Document Number: 05GA0A21Q0072 Page 10 of 37

B.3 The vendor shall allow on-site access to the data center where the system is hosted upon request by authorized representatives of GAO in order to observe security measures in place at the data center. The system must adhere to leading privacy practices including requirements in the Privacy Act of 1974 and GAO’s Privacy Program Order, 0450.1.

B.4 All components must run at a 98.5 percent uptime (down no more than 10 hours, 57 minutes and 26 seconds monthly).

B.5 Web-based interfaces must be used for all administrative functions.

B.6 The proposed solution shall not require any software to be installed locally on GAO machines.

B.7 The system must meet security standards as described below:

B.7.1 A minimum, a FIPS 199 Moderate impact Federal Risk and Authorization Management Program (FedRAMP) certified Software-as-a-Service (SaaS) or Platform-as-a-Service (PaaS) solution with a current security assessment report (SAR) that includes a recommendation to authorize/re-authorize the system. If not FedRAMP-certified, the system shall be in compliance and in alignment with the National Institute of Standards and Technology (NIST) standardized security assessment, authorization, and continuous monitoring standards and guidelines.

B.8 The vendor shall ensure that GAO has an opportunity to review the FedRAMP or NIST artifacts, to include the vendor’s current IT security white papers/documentation, that support the solution’s overall security posture, to include its infrastructure, platform, and software components, at the time of the award. The IT security documentation should include information such as access controls, authentication, boundary protection, change management, customer segregation, encrypted data transmission capabilities, log management, restricting website access, security monitoring, among other security capabilities.

B.9 The vendor shall provide access to GAO, or their designee acting as their agent, when requested, in order to verify compliance with the requirements for an Information Technology security program. GAO reserves the right to conduct on-site inspections. The vendor shall make appropriate personnel available for interviews and provide all necessary documentation during this review.

B.10 The system shall provide an automated mechanism to collect log files (including syslogs, Apache logs, etc.) for security and other analysis purposes. The vendor shall ensure that the automated mechanism allows GAO to periodically review the logs.

B.11 The vendor shall have an incident/breach notification process that will ensure that GAO is notified within an agreed upon timeframe consistent with federal government guidance.

B.12 The vendor shall be prepared to discuss the feasibility of giving GAO the ability to monitor GAO’s hosted environment using a Cloud Management Platform service.

B.13 The vendor shall maintain all of GAO’s data, to include backup data, within the continental United States. The staff managing the data and/or systems maintaining GAO data shall be employed within and working from a system that is within the continental United States and should be United States citizens or current permanent residents.

B.14 The vendor shall implement a catastrophic/disaster failover capability to ensure that the high availability requirement of the system is achieved. The failover site shall be geographically disparate from the primary production location such that loss of the primary production location or functionality does not prohibit the use of the system. The failover site must be in the continental United States.

B.15 The vendor shall deploy strong end-to-end application layer cryptographic mechanisms that are compliant with the current Federal Information Processing Standards Security Requirements for Cryptographic Modules, level 2, at a minimum. The mechanism shall protect customer PINs, user passwords and other sensitive data in the network and data at rest.

B.16 The vendor shall encrypt customer account and transaction data which is transmitted, transported, delivered or couriered to external parties or other locations, taking into account all intermediate junctures and transit points from source to destination.

B.17 The vendor shall require all employees who will have access to GAO data, the architecture that supports GAO data, or any physical or logical devices/code to pass the appropriate background investigation required by the Government in compliance with

HSPD -12.

B.18 The system shall provide security and privacy that are consistent with the NIST Special Publication 800-144 – “Guidelines on Security and Privacy in Public Cloud Computing.”.

Document Number: 05GA0A21Q0072 Page 11 of 37

B.19 The system shall be able to support the establishment of a virtual private network between GAO and the FedRAMP-certified system.

B.20 The system shall authenticate users through single sign on (SSO) using Active Directory Federation Services (ADFS) or through an agreed upon multi-factor authentication mechanism.

B.21 The vendor shall provide access to GAO, or their designee acting as their agent, when requested, in order to verify compliance with the requirements for an Information Technology security program. GAO reserves the right to conduct on-site inspections. The vendor shall make appropriate personnel available for interviews and provide all necessary documentation during this review.

B.22 The vendor shall ensure that its environment remains compliant with the control standards of Federal Information Security Modernization Act of 2014 (FISMA), the current NIST standards in FIPS 140-2 or 140-3, FIPS 199, FIPS 200, FIPS 201 and current NIST Special Publications 800-37, 800-53, 800-60, 800-61, 800-70, 800-144, and 800-163. In addition, the Vendor must provide GAO with any documentation it requires for its security-related reporting requirements within 10 days of a request.

C. Support and Maintenance

C.1 The vendor shall provide live customer support (through telephone or real-time chat) every business day from 8:00 AM to 6:00 PM ET. This will entail intake of content errors and basic technical support issues. A ticketing process is required for tracking reported issues through the entire problem life cycle.

C.2 The vendor shall regularly enhance the products based on customer input and industry changes.

C.3 The vendor shall provide training in all aspects of the system as needed.

C.4 The vendor shall provide all updates to the system without further costs to the agency.

C.5 The vendor shall provide advance notice, of two business days, of any updates that shall require an interruption of service.

D. Implementation and Migration Services

D.1 The vendor shall provide support, for transitioning between the legacy data structures and processes and the new vendor’s data structures and processes. This support includes developing, testing and documenting of APIs or other data delivery structures for intake into GAO’s systems and developing, testing and documenting of workflow for inputting data into GAO systems.

D.2 The timeline for implementation shall be (3) months from the date of the contract signing.

Section VI. Delivery

Based on the Milestones and Schedules provided above the following delivery schedule must be met by the Contractor.

Contract Set-up Deliverables

Deliverable Description Date Completed User Accounts to System IDs and Passwords At least 1 week after contract award Bibliographic Record/Collection Evaluation Excel or Text File GAO to provide at least two weeks after contract award Training for Librarians Webinars or In-Person Start at 2 weeks before system implementation.

Load Collection Holdings from Bibliographic Records

Excel or Text File Complete at least 4 weeks from contract award

Set up and Configure ERM-type Component

Load test database holdings from KBart or Excel file

Complete at least 4 weeks from contract award

Load information about GAO users for patron records

Load GAO information from a GAO provided Excel file

Complete at least 4 weeks from contract award

Deliverables for life of contract

Document Number: 05GA0A21Q0072 Page 12 of 37

Deliverable Description Date Completed Software updates and/or patches Updates to any module and/or entire taxonomy system As needed, with 2 business day alert of installation needing service disruption

Follow-up training Additional training on system functionality As needed

Section VII. Government-Furnished Property, Material, Equipment, or Information (GFP, GFM, GFE, OR GFI)

Work shall be performed on-site at GAO Headquarters, with no travel expected. The government shall furnish a workspace and computer resources to perform the contract tasks. (If necessary) Government telephones are for official use only, with the stipulation that on-site personnel conform to existing GAO policy for personal use in the workplace. Any Government property destroyed or tampered with by the contractor’s personnel shall be the responsibility of the contractor.

Information Sources. Agency personnel shall be available for technical exchanges. GAO will provide the needed metadata and taxonomy information to populate the system.

Documentation. All applicable documentation shall be available on-site to the contractor at the start of the contract. All materials shall remain the property of the GAO and shall be returned to the Contracting Officer Representative (COR) upon request or at the completion of this task.

Section VIII. Security

All technical interaction with GAO infrastructure must be through Federal RAMP certified systems and software and/or systems compliant with ISO Standard 27001.

Physical Security:

The vendor shall be responsible for safeguarding all government equipment, information and property provided for contractor use. At the close of each work period, government facilities, equipment, and materials shall be secured.

Section IX. Place of Performance

The vendor shall provide support during GAO’s core business hours and where specified after-hours. This support shall be provided at the GAO Headquarters facility at 441 G Street NW in Washington, DC. Please note, the location of performance is subject to change during the term of this contract (e.g. a requirement for GAO teleworking).

Examples of after-hours support are listed in Section V above.

Section X. Period of Performance

The period of performance for this contract shall be one (1) Base Year of 12 months, with four (4) 12-month option years. The period of performance includes 40-day transition periods at the beginning and end of the period of performance.

Section XI. Contract Administration

GAO Contracting Points of Contact:

LaVonne Y. Hill Acquisition Management, Financial Management & Budget Office Government Accountability Office 441 G St NW, Washington, DC 20548 HillL@gao.gov

Technical Point of Contact: TBD

03 Evaluation Factors

Evaluation Factors

A. Evaluation Criteria

Document Number: 05GA0A21Q0072 Page 13 of 37

1. This is a lowest price technically acceptable (LPTA) procurement. The Government will make an award to the responsible vendor whose quotation is the technically acceptable and lowest-priced.

Quotations will be evaluated under the lowest-price technically acceptable (LPTA) source selection process.

The award will be made on the basis of the lowest price quotation meeting the acceptability standards for non-cost factors.

B.Minimum Requirements to Meet Acceptability Standards for Non-Cost Factors

1. Factor 1 – Technical Approach

Sub-factor 1 – Technical Approach to Taxonomy System

A.1 This taxonomy server and system component must comply easily integrate with other systems as described below:

A.1.1 The system must provide REST or SOAP web services.

A.1.2 The system must provide a database level API for integration into GAO internal systems and externally facing applications.

A.1.3 The taxonomy system must have a mechanism for accepting term suggestions and revisions through another system through web-based survey forms.

A.2 The system must be compliant with ANSI/NSIO Z39.19 and/or ISO 25964.

A.3 The system must use W3C standards for creating and editing taxonomies.

A.4 The system must have the ability to model vocabularies in SKOS and/or RDF.

A.5 The system modeling of ontologies must use OWL for its standard.

A.6 The system must meet the below accessibility standards as described below:

A.6.1 ISO/IEC 40500

A.6.2 W3C Web Content Accessibility Guidelines (WCAG) 2.0 Level AA

A.6.3 W3C Web Content Accessibility Guidelines (WCAG) 2.1 Level AA

A.6.4 Applicable revised Section 508 Standards

A.7 The taxonomy system must accept and output a variety of file formats as described below:

A.7.1 Import formats must include: .csv, .txt, RDF, SKOS

A.7.2 Export formats must include: .csv and/or .txt

A.7.3 Export formats must include: RDF (RDF/XML or Turtle serialization ) and/or SKOS format

A.8 The taxonomy system must support a robust and flexible yet straight-forward system for assigning roles and permissions to staff functions as described below:

A.8.1 The system must allow creation of at least five (5) user accounts that allow for the permission levels below:

A.8.1a The system must allow permissions assignment at the term level.

A.8.1b The system must allow at least these permissions levels:

A.8.1c Read-only access

A.8.1d Comment only access

A.8.1e Editor access

Document Number: 05GA0A21Q0072 Page 14 of 37

A.8.1f System administrator access (control for all system permissions)

A.9 The taxonomy system must be flexible for various knowledge organization and representation schemes’ creation, revision, and management as described below:

A.9.1 Controlled vocabularies

A.9.2 Taxonomies

A.9.3 Thesauri

A.9.4 Named entity lists

A.10 The system must have the following features for term and concept creation and revision:

A.10.1 Creation of unique identifiers for all concepts.

A.10.2 Ability to develop a concept’s properties, labels, and relationships from a single screen

A.10.3 Ability to edit hierarchies with drag-and-drop

A.10.4 Ability to create poly-hierarchical structures (multiple inheritance)

A.10.5 Ability to create global edits, across taxonomies, to:

A.10.5a Concept attributes

A.10.5b Concept relationships

A.10.6 Ability to browse records:

A.10.6a Alphabetically

A.10.6b Hierarchically

A.10.6c Chronologically (Date created and Date last edited)

A.10.6d Ability to search and filter records by:

A.10.6e Keywords (exact, fuzzy or phrase searching)

A.10.6f Approval/review status

A.10.6g Date created and/or modified

A.10.6h Preferred/non-preferred term status

A.11 The system must have automatic mechanisms for:

A.11.1 Prevention of term duplicates (disambiguation)

A.11.2 Reciprocal relationships

A.11.3 Prevention of circular references

A.11.4 Prevention of non-preferred terms from hierarchical and associative relationships

A.11.5 Detection of orphan terms

A.12 The system must manage the quality control, production, and archival versions of vocabularies or collections of vocabularies.

Document Number: 05GA0A21Q0072 Page 15 of 37

A.13 The taxonomy system must be integrated with an auto-categorization mechanism to classify documents with terms stored within it as described below:

A.13.1 The taxonomy module and the auto-categorization module must be preconfigured to be integrated when the software is implemented.

A.13.2 The auto-categorization module must provide relevancy scoring for terms present in the taxonomy module as follows:

A.13.1a The scoring must be provided on both an individual document and multiple document basis.

A.13.1b Users must be able to select tagging for documents based on the scoring provided.

Sub-factor 2 – Technical Approach to Auto-Categorization System

B.1 This auto-categorization component must meet the requirements listed below:

B.1.1 The module must have a mechanism for writing classification rules with:

B.1.1a Boolean logic (AND, OR, NOT);

B.1.1b Proximity (x within # words of y);

B.1.1c Truncation/wildcards (crim* for crime, criminal, etc.); and

B.1.1d Regular expressions.

B.2 The module should offer at least one preloaded statistical models for classification and include the following documentation:

B.2.1 How the classifier was trained;

B.2.2 Its prediction statistics;

B.2.3 The ability of the model to be retrained with additional data

Sub-factor 3 – Requirements for Specific Tasks and Components

A. Transition to New System

As GAO migrates from its current taxonomy server, the vendor shall provide the following to facilitate the transition:

A.1. The vendor shall supply the name and contact information for a dedicated point of contact for customer service and technical issues (Technical POC) within 2 business days of signing the contract. The Technical POC must provide a non-automated response within 1 business day after being contacted with an issue during the first 3 months of the contract or until the migration is successfully completed.

A.2. The vendor shall provide written system documentation, describing all functions of all modules included in the software as configured for GAO.

A.3. The vendor shall provide initial training to the GAO taxonomy team that will cover all aspects of the system.

B. System Architecture and Security

The system must meet the security requirements listed below:

B.1 All information entered into the system by GAO is to be owned by GAO. GAO retains the right to export, import, alter, and back-up data while using the software.

B.2 The vendor must adhere to records requirements, as detailed by GAO Privacy Program Order, 0450.1, GAO Records Management Program Order 0410.1 and GAO’s Records Retention Schedules.

Document Number: 05GA0A21Q0072 Page 16 of 37

B.4 All components must run at a 98.5 percent uptime (down no more than 10 hours, 57 minutes and 26 seconds monthly).

B.5 Web-based interfaces must be used for all administrative functions.

B.6 The proposed solution shall not require any software to be installed locally on GAO machines.

B.7 The system must meet security standards as described below:

A minimum, a FIPS 199 Moderate impact Federal Risk and Authorization Management Program (FedRAMP) certified Software-as-a-Service (SaaS) or Platform-as-a-Service (PaaS) solution with a current security assessment report (SAR) that includes a recommendation to authorize/re-authorize the system. If not FedRAMP-certified, the system shall be in compliance and in alignment with the National Institute of Standards and Technology (NIST) standardized security assessment, authorization, and continuous monitoring standards and guidelines.

B.11 The vendor shall have an incident/breach notification process that will ensure that GAO is notified within an agreed upon timeframe consistent with federal government guidance.

B.12 The vendor shall be prepared to discuss the feasibility of giving GAO the ability to monitor GAO’s hosted environment using a Cloud Management Platform service.

HSPD -12.

B.18 The system shall provide security and privacy that are consistent with the NIST Special Publication 800-144 – “Guidelines on Security and Privacy in Public Cloud Computing.”.

Document Number: 05GA0A21Q0072 Page 17 of 37

B.19 The system shall be able to support the establishment of a virtual private network between GAO and the FedRAMP-certified system.

B.20 The system shall authenticate users through single sign on (SSO) using Active Directory Federation Services (ADFS) or through an agreed upon multi-factor authentication mechanism.

C. Support and Maintenance

C.2 The vendor shall regularly enhance the products based on customer input and industry changes.

C.3 The vendor shall provide training in all aspects of the system as needed.

C.4 The vendor shall provide all updates to the system without further costs to the agency.

C.5 The vendor shall provide advance notice, of two business days, of any updates that shall require an interruption of service.

D. Implementation and Migration Services

D.2 The timeline for implementation shall be (3) months from the date of the contract signing.

Section 2 - Contract Clauses

01 52.212-4 Contract Terms and Conditions -Commercial Items (OCT 2018)

(a) Inspection/Acceptance. The Contractor shall only tender for acceptance those items that conform to the requirements of this con-tract. The Government reserves the right to inspect or test any supplies or services that have been tendered for acceptance. The Gov-ernment may require repair or replacement of nonconforming supplies or reperformance of nonconforming services at no increase in contract price. If repair/replacement or reperformance will not correct the defects or is not possible, the Government may seek an equitable price reduction or adequate consideration for acceptance of nonconforming supplies or services. The Government must exer-cise its post-acceptance rights--

(1) Within a reasonable time after the defect was discovered or should have been discovered; and

(2) Before any substantial change occurs in the condition of the item, unless the change is due to the defect in the item.

(b) Assignment. The Contractor or its assignee may assign its rights to receive payment due as a result of performance of this contract to a bank, trust company, or other financing institution, including any Federal lending agency in accordance with the

Document Number: 05GA0A21Q0072 Page 18 of 37

Assignment of Claims Act (31 U.S.C. 3727). However, when a third party makes payment (e.g., use of the Governmentwide commercial purchase card), the Contractor may not assign its rights to receive payment under this contract.

(d) Disputes. This contract is subject to 41 U.S.C. chapter 71, Contract Disputes. Failure of the parties to this contract to reach agree-ment on any request for equitable adjustment, claim, appeal or action arising under or relating to this contract shall be a dispute to be resolved in accordance with the clause at FAR 52.233-1, Disputes, which is incorporated herein by reference. The Contractor shall proceed diligently with performance of this contract, pending final resolution of any dispute arising under the contract.

(e) Definitions. The clause at FAR 52.202-1, Definitions, is incorporated herein by reference.

(f) [Reserved].

(g) Invoice.

(1) The Contractor shall submit an original invoice and three copies (or electronic invoice, if authorized) to the address designated in the contract to receive invoices. An invoice must include--

(i) Name and address of the Contractor;

(ii) Invoice date and number;

(iii) Contract number, line item number and, if applicable, the order number;

(iv) Description, quantity, unit of measure, unit price and extended price of the items delivered;

(v) Shipping number and date of shipment, including the bill of lading number and weight of shipment if shipped on Government bill of lading;

(vi) Terms of any discount for prompt payment offered;

(vii) Name and address of official to whom payment is to be sent;

(viii) Name, title, and phone number of person to notify in event of defective invoice; and

(ix) Taxpayer Identification Number (TIN). The Contractor shall include its TIN on the invoice only if required elsewhere in this con- tract.

(x) Electronic funds transfer (EFT) banking information.

(A) The Contractor shall include EFT banking information on the invoice only if required elsewhere in this contract.

(B) If EFT banking information is not required to be on the invoice, in order for the invoice to be a proper invoice, the Contractor shall have submitted correct EFT banking information in accordance with the applicable solicitation provision, contract clause (e.g., 52.232-33, Payment by Electronic Funds Transfer--System for Award Management, or 52.232-34, Payment by Electronic Funds Transfer--Other Than System for Award Management), or applicable agency procedures.

(2) Invoices will be handled in accordance with the Prompt Payment Act (31 U.S.C. 3903) and Office of Management and Budget (OMB) prompt payment regulations at 5 CFR Part 1315.

(h) Patent indemnity. The Contractor shall indemnify the Government and its officers, employees and agents against liability, includ- ing costs, for actual or alleged direct or contributory infringement of, or inducement to infringe, any United States or foreign patent, trademark or copyright, arising out of the performance of this contract, provided the Contractor is reasonably notified of such claims and proceedings.

(i) Payment.--

Document Number: 05GA0A21Q0072 Page 19 of 37

(1) Items accepted. Payment shall be made for items accepted by the Government that have been delivered to the delivery destinations set forth in this contract.

(2) Prompt payment. The Government will make payment in accordance with the Prompt Payment Act (31 U.S.C. 3903) and prompt payment regulations at 5 CFR Part 1315.

(3) Electronic Funds Transfer (EFT). If the Government makes payment by EFT, see 52.212-5(b) for the appropriate EFT clause.

(4) Discount. In connection with any discount offered for early payment, time shall be computed from the date of the invoice. For the purpose of computing the discount earned, payment shall be considered to have been made on the date which appears on the payment check or the specified payment date if an electronic funds transfer payment is made.

(5) Overpayments. If the Contractor becomes aware of a duplicate contract financing or invoice payment or that the Government has otherwise overpaid on a contract financing or invoice payment, the Contractor shall--

(i) Remit the overpayment amount to the payment office cited in the contract along with a description of the overpayment including the--

(A) Circumstances of the overpayment (e.g., duplicate payment, erroneous payment, liquidation errors, date(s) of overpayment);

(B) Affected contract number and delivery order number, if applicable;

(D) Contractor point of contact.

(ii) Provide a copy of the remittance and supporting documentation to the Contracting Officer.

(6) Interest.

(i) All amounts that become payable by the Contractor to the Government under this contract shall bear simple interest from the date due until paid unless paid within 30 days of becoming due. The interest rate shall be the interest rate established by the Secretary of the Treasury as provided in 41 U.S.C. 7109 , which is applicable to the period in which the amount becomes due, as provided in (i)(6)

(v) of this clause, and then at the rate applicable for each six-month period as fixed by the Secretary until the amount is paid.

(ii) The Government may issue a demand for payment to the Contractor upon finding a debt is due under the contract.

(iii) Final decisions. The Contracting Officer will issue a final decision as required by 33.211 if--

(A) The Contracting Officer and the Contractor are unable to reach agreement on the existence or amount of a debt within 30 days;

(B) The Contractor fails to liquidate a debt previously demanded by the Contracting Officer within the timeline specified in the de-mand for payment unless the amounts were not repaid because the Contractor has requested an installment payment agreement; or

(C) The Contractor requests a deferment of collection on a debt previously demanded by the Contracting Officer (see 32.607-2).

(iv) If a demand for payment was previously issued for the debt, the demand for payment included in the final decision shall identify the same due date as the original demand for payment.

(v) Amounts shall be due at the earliest of the following dates:

(A) The date fixed under this contract.

(B) The date of the first written demand for payment, including any demand for payment resulting from a default termination.

(vi) The interest charge…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated Sep 9, 2021.