030ADV24R0004.pdf
PDF 2 MB Posted
- Attached to
- BARD Mobile Development Services IDIQ
- Solicitation number
- 030ADV24R0004
- Issued by
-
Library of Congress
About this file
This is a solicitation for an indefinite delivery, indefinite quantity (IDIQ) contract to provide agile software development services for the Library of Congress' National Library Service for the Blind and Physically Handicapped (NLS). The solicitation seeks maintenance, enhancement, and development of existing and new NLS applications for searching, browsing, and reading content from the NLS collection of braille and talking books on relevant platforms. The period of performance is a seven-year ordering period from January 31, 2024 through January 30, 2031. The minimum order amount is $5,000 and the maximum aggregate amount for all task orders issued under all IDIQ contracts is $20,000,000. Task orders will be placed on a firm fixed price basis for defined requirements fulfilled in two-week or four-week sprints.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Attachment J5-TO 1 iOS SOW rev.docx | DOCX document | |
| Attachment J6-TO 2 Android SOW rev.docx | DOCX document | |
| Amendment 0001_030ADV24R0004 0001.pdf | ||
| Attachment J4 - Question and Answers.pdf | ||
| Attachment J1 - NLS Agile Methodology Guide.docx | DOCX document | |
| Attachment J5 - TO 1 iOS SOW.docx | DOCX document | |
| Attachment J2 - QASP.xlsx | XLSX spreadsheet | |
| Attachment J6 - TO 2 Android SOW.docx | DOCX document | |
| Attachment J4 - Questions_Template.xlsx | XLSX spreadsheet | |
| Attachment J7 - TO 3 FireiOS SOW.docx | DOCX document | |
| Attachment J3 - Pricing Schedule 12.18.2023.xlsx | XLSX spreadsheet |
Show all 11
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
PAGE 1 OF 1. REQUISITION NO.
2. CONTRACT NO. 3. AWARD/EFFECTIVE DATE 4. ORDER NO. 5. SOLICITATION NUMBER 6. SOLICITATION ISSUE DATE
a. NAME b. TELEPHONE NO. (No Collect Calls) 8. OFFER DUE DATE/LOCAL
TIME
9. ISSUED BY CODE 10. THIS ACQUISITION IS 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:
11. DELIVERY FOR FOB DESTINA-
TION UNLESS BLOCK IS
MARKED
SEE SCHEDULE
12. DISCOUNT TERMS
13a. THIS CONTRACT IS A
RATED ORDER UNDER
DPAS (15 CFR 700)
13b. RATING
14. METHOD OF SOLICITATION
RFQ IFB RFP
15. DELIVER TO CODE 16. ADMINISTERED BY CODE
17a. CONTRACTOR/OFFEROR CODE FACILITY CODE 18a. PAYMENT WILL BE MADE BY CODE
TELEPHONE NO. UEI: EFT:
PHONE: FAX:
17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT SUCH ADDRESS IN OFFER
18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a UNLESS BLOCK BELOW IS CHECKED
SEE ADDENDUM
19. 20. 21. 22. 23. 24.
ITEM NO. SCHEDULE OF SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT
(Use Reverse and/or Attach Additional Sheets as Necessary)
25. ACCOUNTING AND APPROPRIATION DATA 26. TOTAL AWARD AMOUNT (For Govt. Use Only)
27a. SOLICITATION INCORPORATES BY REFERENCE FAR 52.212-1, 52.212-4. FAR 52.212-3 AND 52.212-5 ARE ATTACHED. ADDENDA 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
28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN _______________ 29. AWARD OF CONTRACT: REF. ___________________________________ OFFER COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND DATED ________________________________. YOUR OFFER ON SOLICITATION DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND ON ANY (BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED 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 CONTRACTING OFFICER (TYPE OR PRINT) 31c. DATE SIGNED
AUTHORIZED FOR LOCAL REPRODUCTION (REV. NOV 2021)
PREVIOUS EDITION IS NOT USABLE Prescribed by GSA - FAR (48 CFR) 53.212
7. FOR SOLICITATION
INFORMATION CALL:
STANDARD FORM 1449
SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES
OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, & 30
See SCHEDULE
030ADV24R0004 12-19-2023
Price, Veronica (202) 707-9335 01-20-2024
3:00 PM EST
Contracts and Grants Directorate Library of Congress
101 Independence Ave. SE LA 325 Washington DC 20540-9411
X
N/A
X
DELIVERY
See Section F for delivery instructions.
Contracts & Grants Directorate Library of Congress
LA 325
101 Independence Av SE Washington DC 20540-9411
Submit Invoices through:
NLSadmin@loc.gov Washington DC 20540
See CONTINUATION Page
0.00 See CONTINUATION Page
X X
Price, Veronica
030ADV24R0004
Table of Contents
SECTION A ....................................................................................................................... Error! Bookmark not defined.
A.1 SF 1449 SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES .................................................................................................................................... Error! Bookmark not defined.
SECTION B - SUPPLIES OR SERVICES AND PRICE/COSTS
B.1 LC52.212-2 SUPPLEMENTAL LICENSE AGREEMENTS (JUL 2017)
B.2 PRICE/COST SCHEDULE
ITEM INFORMATION
SUPPLIES OR SERVICES AND PRICES
SECTION C - DESCRIPTION/SPECIFICATIONS/STATEMENT OF WORK
SECTION D - PACKAGING AND MARKING
D.1 LC52.231-1 PAYMENT OF POSTAGE FEES (MAY 2015)
SECTION E - INSPECTION AND ACCEPTANCE
SECTION F - DELIVERIES OR PERFORMANCE
F.1 LC52.215-5 PLACE AND PERIOD OF PERFORMANCE (JAN 2019)
SECTION G - CONTRACT ADMINISTRATION DATA
G.1 LC52.232-1A LIBRARY OF CONGRESS INVOICE INSTRUCTIONS (OCT 2016)
G.2 LC52.232-2 SCHEDULE OF PAYMENTS (JUN 2015)
SECTION H - SPECIAL CONTRACT REQUIREMENTS
H.1 LC52.201-1 CONTRACTING OFFICER'S REPRESENTATIVE (COR) APPOINTMENT AND AUTHORITY (JAN 2016)
H.2 LC52.203-1 CONTRACTOR PUBLICITY (OCT 2013)
H.3 LC52.204-3 INFORMATION SYSTEMS SECURITY (SEP 2018)
H.4 LC52.209-1 CONFLICTS OF INTEREST (OCT 2013)
H.5 LC52.237-1 KEY PERSONNEL (AUG 2014)
H.6 LC52.237-2 CONDUCT OF WORK (MAY 2015)
H.7 LC52.239-1 INFORMATION SECURITY (APR 2021)
H.8 LC52.239-2 SYSTEMS DEVELOPMENT LIFE CYCLE (SEP 2018)
H.9 LC52.239-3 ASSESSMENT AND AUTHORIZATION (JAN 2016)
H.10 LC52.239-3A ASSESSMENT AND AUTHORIZATION (ALT I) (JAN 2016)
H.11 LC52.239-4 SECTION 508 COMPLIANCE (JAN 2015)
H.12 LC52.239-6 ASSESSMENT AND AUTHORIZATION PRIVACY REQUIREMENTS (JUL 2016)
H.13 LC52.244-1 SUBCONTRACT NOTIFICATION (OCT 2016)
030ADV24R0004
PART II - CONTRACT CLAUSES
SECTION I - CONTRACT CLAUSES
I.1 52.252-2 CLAUSES INCORPORATED BY REFERENCE (FEB 1998)
I.2 LC52.201-2 ORDERING OFFICERS (OCT 2013)
I.3 52.204-21 BASIC SAFEGUARDING OF COVERED CONTRACTOR INFORMATION SYSTEMS (NOV 2021)
I.4 52.212-5 CONTRACT TERMS AND CONDITIONS REQUIRED TO IMPLEMENT STATUTES OR EXECUTIVE
ORDERS—COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES (NOV 2023)
I.5 52.216-18 ORDERING (AUG 2020)
I.6 52.216-19 ORDER LIMITATIONS (OCT 1995)
I.7 52.216-22 INDEFINITE QUANTITY (OCT 1995)
I.8 52.217-8 OPTION TO EXTEND SERVICES (NOV 1999)
I.9 LC52.212-4 CONTRACT TERMS AND CONDITIONS - COMMERCIAL ITEMS (DEV) (FEB 2016)
I.10 LC52.212-5 CONTRACT TERMS AND CONDITIONS REQUIRED TO IMPLEMENT STATUTES OR EXECUTIVE
ORDERS - COMMERCIAL ITEMS (DEV) (MAY 2015)
I.11 LC52.216-2 FAIR OPPORTUNITY (FEB 2020)
I.12 LC52.227-1 ASSIGNMENT OF COPYRIGHT TO THE LIBRARY OF CONGRESS (DEC 2001)
I.13 LC52.232-25 PROMPT PAYMENT (DEV) (JUL 2013)
I.14 LC52.233-1 52.233-1 (DEV) DISPUTES (MAY 2014)
PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS
SECTION J - LIST OF ATTACHMENTS
PART IV - REPRESENTATIONS AND INSTRUCTIONS
SECTION K - REPRESENTATIONS, CERTIFICATIONS AND OTHER STATEMENTS OF OFFERORS
K.1 52.204-24 REPRESENTATION REGARDING CERTAIN TELECOMMUNICATIONS AND VIDEO SURVEILLANCE
SERVICES OR EQUIPMENT (NOV 2021)
K.2 52.209-7 INFORMATION REGARDING RESPONSIBILITY MATTERS (OCT 2018)
K.3 52.212-3 OFFEROR REPRESENTATIONS AND CERTIFICATIONS—COMMERCIAL PRODUCTS AND
COMMERCIAL SERVICES (NOV 2023)
K.4 52.229-11 TAX ON CERTAIN FOREIGN PROCUREMENTS—NOTICE AND REPRESENTATION (JUN 2020)
SECTION L - INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS
L.1 LC52.233-2 PROTESTS TO THE LIBRARY OF CONGRESS (DEC 2013)
SECTION M - EVALUATION FACTORS FOR AWARD
030ADV24R0004 Section B
SECTION B - SUPPLIES OR SERVICES AND PRICE/COSTS
B.1 LC52.212-2 SUPPLEMENTAL LICENSE AGREEMENTS (JUL 2017)
The Library does not agree to licensing agreements or any other provisions that attempt to: (1) replace an order as the governing contract; (2) establish new or supplemental payment terms; or, (3) affect the legal relationships of the parties.
Notwithstanding any clauses in this contract or order, or the contractual vehicles against which the order is placed, that establish order of precedence, the rights and obligations provided by this contract or order take precedence over the rights and obligations set forth in any licensing agreements provided to the Library.
The Library’s incorporation of a licensing agreement into this contract or order excludes all terms of the licensing agreement that contravene, modify or conflict with the terms of 36 C.F.R. 701.7 available at: https://www.ecfr.gov/cgi-bin/text-idx?SID=87a865ce2bd109313a951a3d477895d8&mc=true&node=se36.3.701_17&rgn=div8.
(End of Clause)
B.2 PRICE/COST SCHEDULE
ITEM INFORMATION
ITEM
NUMBER
DESCRIPTION OF
SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT
1.00 LOT __________________ __________________
7-Year Ordering Period for BARD Mobile Contract Period: Base POP Begin: 01-31-2024 POP End: 01-30-2031 $5,000 is the contract minimum see Section B.3.4.
GRAND TOTAL __________________
SUPPLIES OR SERVICES AND PRICES
B.3.1. This is an Indefinite Delivery, Indefinite Quantity (IDIQ) contract. Orders may be placed on a Firm Fixed Price (FFP) basis. This contract is for a seven (7) year ordering period, as follows:
01/31/2024 – 01/30/2031
B.3.2. This is a multiple-award IDIQ. Awardees and associated contract numbers are:
Contractor Name Contract Number
<added at time of award>
030ADV24R0004 Section B
B.3.3. Firm fixed price orders shall be placed for defined requirements that are fulfilled utilizing the sprint prices in section J3. In the event a task order period of performance crosses ordering periods as defined in section B, task order pricing for the entire order must comply with the sprint price that is current at the time the order starts. Blending of rates across ordering years is not permitted.
B.3.4. Minimum and Maximum Amounts
a) The Library of Congress will order a minimum amount of $5,000.00 under this contract. Specific requirements will be identified in individual orders issued under this contract. During the life of this contract, the Government may order items in any quantity up to the maximum contract value specified in paragraph (b) below.
b) The maximum aggregate amount of all task orders issued under all IDIQ contracts shall not exceed the shared ceiling of $20,000,000.00 for the entire ordering period.
B.3.5. Travel
Travel costs may be included in specific task orders at the discretion of the Library of Congress contracting officer. Any authorized travel expenses shall not exceed the amounts expressed in the Federal Travel Regulation.
B.3.6. Open Market Items
Open Market Items that are incidental to a task order solution but not included in the IDIQ price schedule J3 may be included in task orders if their total price is less than $25,000.00. Inclusion of open market items may only occur pending a determination that the open market items are offered at a fair and reasonable price and that their inclusion in a task order is in the best interest of the Library in order to complete associated requirements.
B.3.7. Program/Project Management
Any contractor program/project management costs shall be included as a direct labor cost in the price of each task order, if required. PM costs shall not be authorized as an indirect cost under any order.
030ADV24R0004 Section C
SECTION C - DESCRIPTION/SPECIFICATIONS/STATEMENT OF WORK
BARD Mobile Development
Statement of Work
C.1. Background
The Library of Congress (Library) National Library Service for the Blind and Physically Handicapped (NLS) requires contract support to provide software development services to be performed using an agile development methodology.
NLS provides a suite of freely available iOS, Android, Kindle Fire, and PC software applications for eligible U.S. residents and citizens that allow a patron to search, browse, and play back items from the NLS collection of braille and talking-books. For iOS, Android, and Kindle Fire platforms these applications are known as BARD Mobile. For Windows PCs this application is known as BARD Express. BARD Mobile and BARD express have been publicly available for several years.
This contractor will be responsible for the existing “BARD” suite of software as well as future other NLS reading applications.
Link to current applications:
NLS at the Library of Congress – National Library Service for the Blind and Print Disabled (NLS) | Library of Congress (loc.gov)
BARD: BARD: Braille and Audio Reading Download National Library Service for the Blind and Print Disabled Downloadable Books and Magazines (loc.gov)
NLS reading applications are unique in that they support playback of both ANSI/NISO Z39.86 Digital Talking Books protected with the PDTB 2.0 specification and braille books in the BRF format. NLS reading applications have been specially designed to use the native accessibility features of the underlying platforms and connect with devices such as refreshable braille displays to provide a high-quality user experience for NLS patrons. NLS reading applications also support communication with the NLS BARD system to provide user authentication, searching/browsing of the NLS collection, and access to user created reading lists and preferences. The NLS collection includes books, magazines, musical scores, and even recorded musical performances performed for and at the Library of Congress. The NLS reading application software resulting from this contract must be able to serve its eligible patrons with a reliable, usable, and accessible product to allow access to NLS books, musical performances, scores and other content. The NLS reading application software resulting from this contract must be expansive in meeting the diversity of NLS eligible user types and their needs and preferences.
These information systems have a FIPS-199 classification of “Medium.”
C.2. Scope
This contract shall provide agile software development activities involving the maintenance, enhancement, and development of existing and new NLS applications for searching, browsing, and reading content from the NLS collection of braille and talking books on the relevant iOS, Linux, Android, Kindle Fire, Mac OS, Windows platforms, and other platforms. The contractor shall perform all software development work using the “SCRUM” based agile development methodology (see Attachment J1 - “NLS Agile Methodology”).
C.3. Requirements
C.3.1 General
The Library is obtaining non-personal services under this IDIQ contract and all task orders under this IDIQ contract. The Library will not direct contractor employees or assign work but instead will coordinate with the contractor’s point of contact. The IDIQ contractor will remain responsible for managing its employees.
The IDIQ contract will be divided into distinct performance areas that correlate to both Contractor specific software platform(s) (e.g. Apple iOS, Microsoft Windows) and open standards based platforms (e.g. Linux, Web Browser). Each performance area consists of requirements for maintenance and enhancement of currently or future released applications, creation of prototype/proof-of-concept software applications, and maintenance and enhancement of prototype/proof-of-concept software applications that become released products. Distinct task orders will be issued in each performance area with a potential for a sequence or combination of 2 or 4-week sprint lengths. Depending on the nature of the performance area and task, NLS anticipates the final task order price may vary based on the combination of requirements described in the task order and NLS or contractor estimates of the number of sprints necessary to complete each task order.
The contractor shall be required to provide all services involved in the software development lifecycle including:
• Project management
• Requirements analysis
• User story creation
• Software and system design
• Prototyping and Field Testing
• Coding
• Implementation
• Testing and Debugging
• Documentation (including both administration and training manuals)
• Integration
• Deployment
• Maintenance
• Accessibility standards compliance
• Provide Agile software development services in either two-week or four-week sprints
• Maintain and update software artifacts in the Library provided git repository.
• Provide dedicated resources for regression testing
• Perform parallel sprints when required to meet development time constraints.
• Review and maintain issues logged in the NLS bug/issue tracking system.
• Adhere strictly to the NLS Agile Methodology
• Implement features and enhancements defined in product requirements documents issued with specific task orders.
C.3.2 Performance Area I – Maintenance and Prototype Development for Apple iOS, iPadOS, WatchOS and MacOS platforms
1. The contractor(s) shall perform software maintenance, bug fixes and development of new features for BARD Mobile for iOS and iPadOS application.
2. The contractor(s) shall perform prototype and proof of concept software and application development for iOS, iPadOS, watchOS and MacOS platforms that encompasses but not limited to accessibility, haptic feedback, voice control commands or voice interfaces, streaming audio playback, and porting of the current bard mobile iOS application to the new platform etc.
3. The contractor(s) shall perform software maintenance, bug fixes, and development of new features for prototype or proof-of-concept applications created for the platform and chosen for release by NLS.
C.3.3 Performance Area II – Maintenance and Prototype Development for Google Android, Google Assistant and Wear OS platforms
1. The contractor(s) shall perform software maintenance, bug fixes and development of new features for BARD Mobile for Android application.
2. The contractor(s) shall perform prototype and proof of concept software and application development for Android, and WearOS platforms that encompasses but not limited to accessibility, haptic feedback, voice control commands or voice interfaces, streaming audio playback, and porting of the current bard mobile Android application to the WearOS platform etc.
3. The contractor(s) shall perform software maintenance, bug fixes, and development of new features for
C.3.4 Performance Area III – Maintenance and Prototype Development for Amazon FireOS and Amazon Alexa platforms
1. The contractor(s) shall perform software maintenance, bug fixes and development of new features for BARD Mobile for FireOS application.
2. The contractor(s) shall perform prototype and proof of concept software, application, and Alexa skill development for FireOS and Amazon Alexa supported platforms that encompasses but is not limited to accessibility, haptic feedback, voice control commands or voice interfaces, streaming audio playback, Alexa skills development etc.
3. The contractor(s) shall perform software maintenance, bug fixes, and development of new features for
C.3.5 Performance Area IV – Maintenance and Prototype Development for Microsoft Windows platform
1. The contractor(s) shall perform software maintenance, bug fixes and development of new features for BARD Express for Windows application.
2. The contractor(s) shall perform prototype and proof of concept software and application development for MS Windows OS platform that encompasses but not limited to accessibility, haptic feedback, voice control commands or voice interfaces, streaming audio playback etc.
3. The contractor(s) shall perform software maintenance, bug fixes, and development of new features for
C.3.6 Performance Area V – Maintenance and Prototype Development for Web Browser based platform
1. The contractor(s) shall perform prototype and proof of concept software and application development for Web Browser based platform that encompasses but not limited to NLS audio and braille book playback, REST API, Single Sign On, AAA, accessibility, voice control commands or voice interfaces, streaming audio playback etc.
2. The contractor(s) shall perform software maintenance, bug fixes, and development of new features for
C.3.7 Performance Area VI – Maintenance and Prototype Development for Linux based platform
1. The contractor(s) shall perform prototype and proof of concept software and application development for Linux OS based platform that encompasses but not limited to NLS audio and braille book playback, REST API, Single Sign on, AAA, accessibility, haptic feedback, voice control commands or voice interfaces, streaming audio playback etc.
2. The contractor(s) shall perform software maintenance, bug fixes, and development of new features for prototype or proof-of-concept applications created for the platform and chosen for release by NLS.
C.4. Agile Development
The development work under this IDIQ contract shall be performed using the “SCRUM” agile development methodology with sprint duration and scope identified in each task order. The contractor must follow the NLS Agile Methodology as defined in attachment J2, “NLS Agile Methodology Guide,” unless the task order requirements made explicit exemptions for research or design-based task order. Specifically, the contractor shall:
● provide Agile software development services for four-week sprints or two-week sprints (approximate hours for estimating purposes only are 170 hours for 4-week sprints and 85 hours for 2-week sprints);
● Develop the baseline artifacts (BSRS, BPBL, and BTM - see Attachment J2, section 2.5);
● Develop and release target artifacts (SRS, SRP, PBL, TM, ITTM, ATM - see Attachment J2, sections 2.5 and 2.8);
● Develop and test the software per the sprint release plan (SRP). The SRP is one of the release target artifacts created in Attachment J2, section 4.2; and
● Develop and test the software in accordance with the procedures defined Attachment J2, sections 2.5, 2.8, 3, 4, 5 and 6.
C.5. Staffing
The contractor shall provide a Project Manager who shall be responsible for the performance of the work. The name of this person and an alternate who shall act for the Contractor when the project manager is absent shall be designated in writing to the Contracting Officer. The project manager or alternate shall have full authority to act for the Contractor on all matters relating to this contract. The project manager or alternate shall be available during the hours of operation identified in Section F.
Additional key personnel shall include a Project/Scrum Master, Lead Developer and Accessibility Subject Matter Expert.
All key personnel should be named and identified. NLS must be notified of any changes in key personnel. In accordance with clause LC52.244-1, the contractor shall obtain the consent to subcontract for any work from the Contracting Officer, either at or above the simplified acquisition threshold or 5 percent of the total estimated task order price.
Minimum Qualifications for each position are listed below:
Project Manager
• Project Manager certification (example: Project Management Institute)
• Five years of experience managing complex federal IT projects.
Scrum Master
• Certified Scrum Master
Accessibility Subject Matter Expert
• Applied knowledge and skills with accessibility reporting against Section 508, WCAG 2.0 AA and 2.1 AA
• Expert understanding of Screen readers and platform specific accessibility affordances (JAWS & NVDA, Talkback, VoiceOver, VoiceView, Magnifier, Speak Screen)
• Knowledge of assistive technologies (switches, speech recognition)
• Five years experience with mobile applications
Lead Developer
Experience with one or more of the following:
● Braille and digital representations of Braille (computer, literary)
● Web Services
● APIs
● REST interfaces, and microservices approach
● Android Software Development Kit (SDK)
● Android Native Development Kit (NDK)
● Android Studio
● Talkback, Brailleback and other accessibility services and mobile settings for Android platforms
● BRLTTY (Braille TTY library)
● SOAP, REST, and JSON based web services
● Java
● Java Native Interface (JNI) and Java Native Access (JNA)
● Application development according to Android Human Interface Guidelines
● Kotlin
● Visual Studio
● iOS, and other relevant technologies
● VoiceOver and iOS accessibility technologies
● C, C++
● XCode
● Swift
● Relevant authentication and security (to include single sign on, OAuth, OpenID-connect, etc.) for mobile applications
● FireOS (Amazon)
● VoiceView (Amazon)
● Siri, SiriKit and App Intents (iOS)
● Alexa, Google Assistant (and other commercial voice integration software)
● Text-to-speech interface and implementation per each platform
● Software testing and monitoring software (Sentry, Appium, Testrails)
● Linux application development
● Platform specific encryption and cryptography best practices for data protection
● IT security best practices for target development platforms
The Lead Developer must have demonstrable development experience with the following:
● UX and UI practices (example, https://ux-guide.18f.gov/)
● Prototyping and Design Thinking
● DAISY accessible media format / DAISY standards o https://daisy.org/activities/standards/daisy/
● PDTB standard o https://daisy.org/activities/standards/pdtb/ specification
● ANSI/NISO Z39.86-2002 standard (Digital Talking Books Protected Standard) o http://www.daisy.org/z3986/specifications/Z39-86-2002.html
● WCAG 2.1 and pending 2.2 updates and implications for applications
● Section 508 and 2018 major revisions https://www.section508.gov/manage/laws-and-policies/quick-reference-guide/
● AMR-WB+ Extended Adaptive Multi-Rate Speech Codec or understanding of audio codecs (other examples include mp3, opus)
In addition, the Lead Developer must have knowledge of the following:
● At least one of the NLS Reading Applications and experience in the applicable performance area (i.e., iOS, Android, FireOS, Express, Web, and Linux). The following information is provided for reference purposes on current NLS Reading Applications and BARD systems:
▪ https://www.loc.gov/nls/braille-audio-reading-materials/bard-access/
▪ https://apps.apple.com/us/app/bard-mobile/id705229586
▪ https://play.google.com/store/apps/details?id=gov.loc.nls.dtb&hl=en_US&gl=US
▪ https://www.amazon.com/Library-of-Congress-BARD-Mobile/dp/B016760320
▪ https://www.loc.gov/nls/braille-audio-reading-materials/bard-access/welcome-to-bard-express/
C.6. Quality Control
● The contractor shall comply with the quality control requirements as specified in Attachment J1 “NLS Agile Methodology Guide”, sections 3 and 6, and sprint defect remediation procedures as specified in section 7.
● The contractor shall conform to the Quality Assurance Surveillance Plan (QASP) as outlined in the Attachment J3, “QASP”.
C.7. Government Furnished Property and Information (GFP and GFI)
All contractor personnel that will be accessing Library of Congress systems must complete Library furnished Information Security Awareness training.
The Library will identify specific GFP or GFI in each task order. Any contractor acquired materials required for performance of this contract shall become the property of the Library upon contract/order completion. The COR will provide instruction on the return of GFP and GFI at the task order level.
NLS will not guarantee provision of any hardware or equipment to the contractor. The contractor shall need to obtain manual testing equipment to support BARD applications. These include supported braille displays, Bluetooth speakers and headphones, and cross-platform mobile devices and tablets.
Depending on the task order, NLS will provide the contractor with the following:
● UML documents describing the Use cases for the business logic.
● IT security requirements (NIST SP-800 based)
● NLS accessibility best practices
● Business process models (BPMN 2.0 diagrams) associated with the current business logic.
● Business process models (BPMN 2.0 diagrams) associated with the new business logic.
● Minutes of meetings where NLS staff created the AS-IS and TO-BE process diagrams. This will provide background information as to how the TO-BE processes were created.
● User Accounts and related credentials to access the NLS BARD system
● User Accounts and related credentials to access BARD platforms (Apple Developer, Google Play, Amazon Developer)
● An introduction to the BARD system. This will provide background information as to the functionality of the BARD system and how it can be used to debug BARD mobile.
● Credentials of a GIT repository for software deliveries.
● Existing source code to BARD mobile.
● Documentation for the BARD API.
(End of Statement of Work)
SECTION D - PACKAGING AND MARKING
D.1 LC52.231-1 PAYMENT OF POSTAGE FEES (MAY 2015)
All postage and fees related to submission of information, including forms, and reports, etc., to the Contracting Officer or Contracting Officer’s Representative (COR) or other persons designated to receive, shall be paid by the Contractor.
(End of Clause)
030ADV24R0004 Section E
SECTION E - INSPECTION AND ACCEPTANCE
INSPECTION & ACCEPTANCE
Inspection and acceptance under this contract will be in accordance with FAR 52.212-4 - Contract Terms and Conditions – Commercial Items.
Additional inspection and acceptance criteria may be specified in each task order.
030ADV24R0004 Section F
SECTION F - DELIVERIES OR PERFORMANCE
FAR Number Title Date
52.242-17 GOVERNMENT DELAY OF WORK APR 1984
52.242-15 STOP-WORK ORDER AUG 1989
F.1 LC52.215-5 PLACE AND PERIOD OF PERFORMANCE (JAN 2019)
Place of Performance: Contractor Facility
The overall period of performance shall be as stated in section B.
The contractor is responsible for determining its hours of operation in fulfilling the requirements of this contract.
The Library’s standard operating hours are from 8:30 AM through 5:30 PM, Monday through Friday, excluding Federal holidays. The contractor shall coordinate with the COR for any work to be conducted at Library facilities.
030ADV24R0004 Section G
SECTION G - CONTRACT ADMINISTRATION DATA
This contract will be administered by:
Library Contracting Officer: Price, Veronica
Address: Contracts & Grants Directorate
Library of Congress
LA 325
Washington DC 20540-9411
Phone: (202) 707-9335
Email: vprice@loc.gov
Library Contract Specialist: Vega, Cristina
Address: Contracts & Grants Directorate
Library of Congress
LA 325
Washington DC 20540-9411
Phone: (202) 707-9473
Email: crvega@loc.gov
Library Contracting Officer Representative: Provided at time of award
Phone: Provided at time of award
Email: Provided at time of award
Contractor Contract Administrator: Provided at time of award
Address: Provided at time of award
Phone: Provided at time of award
Email: Provided at time of award
030ADV24R0004 Section G
G.1 LC52.232-1A LIBRARY OF CONGRESS INVOICE INSTRUCTIONS (OCT 2016)
The Contractor must prepare and submit invoices electronically to: nlsadmin@loc.gov. The Contractor may submit payment requests using other than electronic means only when alternate procedures are authorized by the contracting officer in writing.
(End of Clause)
G.2 LC52.232-2 SCHEDULE OF PAYMENTS (JUN 2015)
The contractor must submit invoices for payment upon delivery of the items or successful performance of the events identified in the orders under this contract pursuant to the standards and acceptance criteria defined in each order.
Payment will take place after each sprint or as otherwise defined in the task order.
030ADV24R0004 Section H
SECTION H - SPECIAL CONTRACT REQUIREMENTS
H.1 LC52.201-1 CONTRACTING OFFICER'S REPRESENTATIVE (COR) APPOINTMENT AND
AUTHORITY (JAN 2016)
(a) Performance of work under this contract is subject to the technical direction of the COR. The term “technical direction” includes, without limitation, direction to the contractor that directs or redirects the labor effort, shifts the work between work areas or locations, and/or fills in details and otherwise serves to ensure that tasks outlined in the contract are accomplished satisfactorily.
(b) Technical direction must be within the scope of the contract specification(s)/work statement. The COR does not have authority to issue technical direction that:
(1) Constitutes additional work outside the contract specification(s)/work statement;
(2) Constitutes a change as defined in the “Changes” clause of this contract;
(3) Causes an increase or decrease in the contract price, or the time required for contract performance;
(4) Changes any of the terms, conditions, or specification(s)/work statement of the contract;
(5) Interferes with the contractor's right to perform under the terms and conditions of the contract; or
(6) Directs, supervises or otherwise controls the actions of the contractor's employees.
(c) Technical direction may be oral or in writing. The COR must confirm oral direction in writing within five workdays, with a copy to the Contracting Officer.
(d) The Contractor shall proceed promptly with performance resulting from the technical direction issued by the COR.
If, in the opinion of the contractor, any direction of the COR or the designated representative falls within the limitations of (b) above, the contractor shall immediately notify the Contracting Officer no later than the beginning of the next Government work day.
(e) Failure of the Contractor and the Contracting Officer to agree that technical direction is within the scope of the contract shall be subject to the terms of the “Disputes” clause of this contract.
(End of Clause)
H.2 LC52.203-1 CONTRACTOR PUBLICITY (OCT 2013)
The Contractor, or any entity or representative acting on behalf of the Contractor, may not refer to the equipment or services furnished pursuant to the provisions of this contract in any news release or commercial advertising, or in connection with any news release or commercial advertising, without first obtaining explicit written consent to do so from the Contracting Officer. Should any reference to such equipment or services appear in any news release or commercial advertising issued by or on behalf of the Contractor without the required consent, the Government will consider institution of all remedies available under applicable law.
H.3 LC52.204-3 INFORMATION SYSTEMS SECURITY (SEP 2018)
(1) Computer Security Policy. The Library requires anyone using or accessing its digital assets (including networks, servers, workstations, systems, data, web pages, and email) to protect them and use them only for official business, and only in accordance with Library regulations and applicable Library bargaining agreements. Unauthorized or inappropriate use may be grounds for termination or other contractual remedy.
(2) Privacy Policy. No one has the right to privacy while using any Library computer system, including internet or email services. Usage may be monitored.
(3) Level of Access. The Host Office will determine the level of access to the Library’s IT equipment, staff and software needed to successfully perform under this Contract. Access may include, for example, email, word processing, internet, and intranet.
(4) Mandatory IT Security Training. Contractor personnel must successfully complete mandatory information systems security training prior to use of or access to any of the Library’s digital assets. The required training is available online at http://www.loc.gov/extranet/cld/. Contractor staff with access to Library digital assets shall complete the information systems security training annually. The training is available on the Library intranet at: http://www.loc.gov/staff/cld/.
(End of Clause)
H.4 LC52.209-1 CONFLICTS OF INTEREST (OCT 2013)
The services required in performance of this contract involve access to non-public information and/or services that are closely associated with the performance of inherently governmental functions that may result in conflicts of interest related to this contract, other contracts, or future contracts for which the contractor may intend to compete. Federal Acquisition Regulation subpart 9.5 describes circumstances and provides illustrative examples of circumstances that may give rise to conflicts of interest.
The Contractor must identify to the contracting officer any conflicts of interest, actual or potential, that may reasonably be expected to arise in performance of this contract. The contractor must provide a detailed written description of the conflict of interest and a plan explaining any and all steps the Contractor will undertake to avoid or mitigate the conflict.
Failure to disclose actual or potential conflicts of interest may subject the Contractor to corrective action including but not limited to termination of this contract, debarment of the contractor, and/or other appropriate civil or criminal actions.
It is solely within the discretion of the Library to determine whether or not a conflict of interest exists and whether any mitigation plan submitted by the Contractor mitigates a conflict.
The Contractor shall include this clause in all subcontracts, consultant agreements, and lower tier subcontracts unless a waiver is granted by the Contracting Officer.
(End of Clause)
H.5 LC52.237-1 KEY PERSONNEL (AUG 2014)
The personnel designated as key personnel in this contract are considered to be essential to the work being performed hereunder. At least 30 days prior to diverting any of the specified individuals to other programs or contracts or as soon as possible if an individual must be replaced, for example, as a result of leaving the employ of the contractor, the contractor shall notify the contracting officer and identify proposed substitutions. No diversion or substitution shall be made by the contractor without written consent of the contracting officer.
The following personnel have been identified as Key Personnel in the performance of this contract:
Position/Labor Category Name
Project Manager TBD
Scrum Master TBD
Lead Developer TBD
Accessibility SME TBD
H.6 LC52.237-2 CONDUCT OF WORK (MAY 2015)
The personnel employed by the Contractor shall be capable employees qualified in this type of work. The Contractor shall be responsible for all damage to Library property by the activities of his employees resulting from these operations.
The Contracting Officer may require removal from work on this contract any employee(s) that may be deemed incompetent, careless, insubordinate, unsuitable, or otherwise objectionable, or whose continued employment is deemed contrary to the public interest or inconsistent with the best interest of or the security of the Library.
(End of Clause)
H.7 LC52.239-1 INFORMATION SECURITY (APR 2021)
The work to be conducted is considered Controlled Unclassified Information (CUI) pursuant to National Institute of Standards and Technology (NIST) Special Publication (SP) 800-53 (rev 4) or current version. The Contractor shall ensure that all non-public Library information processed under this contract shall be protected from unauthorized use and mishandling by the Contractor. Information includes both hard copy (paper) formats and soft copy (stored in electronic form, e.g., hard disks, tapes, flash drives, CD-ROM/CD-R, etc.)
(a) The Contractor shall store hard copies and soft copies contained on removable media (e.g., tapes, floppy disks, flash drives, CD-ROM/CD-R, etc.) in a government-approved storage container per the direction of the Contracting Officer Representative (COR) or the Library of Congress Project Manager when not under the direct control of Contractor Key Personnel.
(b) The Contractor shall treat any information developed on security vulnerabilities and any Government provided non-public information as “CUI”.
(c) The Contractor personnel shall label and protect this information as “Security Category: Moderate”, placing this designation in the footer.
(d) The Contractor shall ensure that all documents designated “Security Category: Moderate”, “Security Category:
High” and “Limited Official Use Only” are not emailed to or from an external email system. These documents may only be emailed between Library of Congress email accounts, or within a secured corporate email network.
(e) The Contractor shall ensure that all documents designated “Security Category: Moderate”, “Security Category:
High” and “Limited Official Use Only” are shredded, burned, or otherwise destroyed before being disposed of in accordance with applicable corporate and federal records management policies.
(f) The Contractor shall dispose of all documents designated “Security Category: Moderate”, “Security Category: High” and “Limited Official Use Only” remaining in the Contractor’s possession at the end of the contract term.
(g) The Contractor shall ensure that all Contractor workstations used to process Library information utilizes anti-virus and anti-spyware utilities that are configured to continuously monitor and to automatically update as well as having automatic operating system patching in place.
(h) The Contractor shall ensure that all Contractor workstations used to process Library information employ a firewall that can either be software running on the workstation or a stand-alone firewall that protects the workstation from unauthorized access from any other devices, including devices on the Contractor’s corporate network.
(i) The Contractor shall ensure that all Library information that is labeled “Security Category: Moderate”, “Security Category: High” and “Limited Official Use Only” is encrypted using a Federal Information Processing Standards Publication (FIPS) 140-2 validated application configured in FIPS mode. This includes information stored on internal hard drives and removable devices (e.g., CD-Rs, flash drives, etc.)
(j) The Contractor must provide a written list of anti-virus, anti-spyware, firewall, encryption products, versions and proof of licenses, along with the automatic operating system patching status, MAC address (if applicable) and user name for each system being used to process Library information.
(k) In accordance with NIST SP 800-61 (rev 2, as updated), the Contractor shall report to infosec@loc.gov, the Contracting Officer, and the COR any adverse events (adverse events are currently defined as events with a negative consequence, such as system crashes, packet floods, unauthorized use of system privileges, unauthorized access to sensitive data, and execution of malware that destroys data) that are computer security related or computer security incidents (computer security incident is currently a violation or imminent threat of violation of computer security polices, acceptable use policies, or standard security practices) concerning Library CUI within 24-hours of its discovery.
The contractor shall coordinate its response to such an event or incident with the Library.
(l) The Contractor shall not provide any government-furnished non-public documents, information, or licensed material in any form to anyone other than the Contracting Officer, the COR, or the Library of Congress Project Manager without the written approval of the Contracting Officer, the COR, or the Library of Congress Project Manager during the period of this contract or at any time afterwards.
(m) The Contractor shall not release any government documents or information related to IT Security in any form without the written approval of the Library’s IT Security Group.
(n) The Contractor shall ensure that all Contractor personnel sign nondisclosure agreements (NDAs).
(o) The Contractor shall ensure that all Contractor personnel complete the Library of Congress IT Security Awareness Training on an annual basis.
(End of Clause)
H.8 LC52.239-2 SYSTEMS DEVELOPMENT LIFE CYCLE (SEP 2018)
The Information Technology to be provided under this contract is subject to the procedures established in the Library’s Systems Development Life Cycle (SDLC) as follows:
(a) Requirements: The Contractor shall gather and analyze requirements and produce a system requirements document (SRD) accordingly.
(b) Design: The Contractor shall perform design analysis and complete a Systems Design Document which satisfies the requirements in the aforementioned SRD.
(c) Development: The Contractor shall develop, customize and/or configure the system according to system requirements and design specifications.
(d) Testing: The Contractor shall test the solution to ensure it satisfies all requirements, including security requirements documented in Library of Congress Directive (LCD) 5-410.1, Information Technology Security Policy. The Contractor shall remediate any identified vulnerabilities and weaknesses in accordance with LCD 5-410.1.
(e) Implementation: The Contractor shall support implementation and deployment of the tested solution into the Library’s production environment.
(f) Documentation: The Contractor must either use the Library’s SDLC templates, which will be provided by the COR upon request, or use an alternative format which satisfies all SDLC requirements as stated in (a) through (e) above. The COR will approve all SDLC deliverables.
(End of Clause)
H.9 LC52.239-3 ASSESSMENT AND AUTHORIZATION (JAN 2016)
The information technology identified in this contract is subject to Assessment and Authorization (A&A) prior to connecting the system(s) to the Library of Congress Network, and updated prior to deploying any significant changes to the system(s).
(a) The Contractor shall perform an Initial Security Assessment.
(b) The Contractor shall perform Assessment per NIST SP 800-37.
(c) The Contractor shall complete a Risk Assessment per NIST SP 800-30
(d) The contractor shall conduct independent Security Testing & Evaluation. Evaluation. Contractor personnel conducting this evaluation shall have no stake or responsibilities concerning the system, including those who directly designed/integrated/implemented the system for any IT System categorized as Moderate or High impact. The Contractor shall perform the Security Test & Evaluation on test equipment configured per the ITS hardening guidelines for that particular platform, either in the Library of Congress lab or on a system completely isolated from the Library of Congress Data Network. The Library will provide the hardening guidelines on request from the contractor.
(e) The contractor shall prepare and submit a complete Assessment package pursuant to NIST SP 800-37. The contractor shall prepare and submit the following A&A documentation to the COR using the standard Library of Congress template available at the CGD website:
System Security Plan pursuant to NIST SP 800-18 IT Contingency Plan pursuant to NIST SP 800-34 Security Test & Evaluation Report
(f) The Contractor shall provide Authorization support to the Authorizing Official, including producing copies of the Assessment Package, drafting memorandums and assisting in the briefing of the Designated Approving Authority.
(g) The Contractor shall provide two (2) paper copies of each Assessment and Authorization deliverable. The contractor shall provide two (2) machine-readable copies each of the Assessment and Authorization deliverables in MS Word format, delivered on CD-ROM.
(h) The Contractor shall ensure that the IT system is not connected to the Library of Congress Data Network until accredited.
(End of Clause)
H.10 LC52.239-3A ASSESSMENT AND AUTHORIZATION (ALT I) (JAN 2016)
The information technology identified in this contract will be subject to review and approval of Assessment and Authorization (A&A) prior to connecting the system(s) to the Library of Congress Network.
(a) The contractor shall provide the COR with documentation demonstrating Authorization.
(b) The Library will perform a security assessment, assessment, risk assessment, and security testing & evaluation pursuant to NIST SP 800-37.
(c) The Contractor shall provide Authorization support to the Authorizing Official, including producing copies of the Assessment Package, drafting memorandums and assisting in the briefing of the Designated Approving Authority.
(d) The Contractor shall ensure that the IT system is not connected to the Library of Congress Data Network until accredited.
(End of Clause)
H.11 LC52.239-4 SECTION 508 COMPLIANCE (JAN 2015)
All contract deliverables shall comply with accessibility standards set forth in the Architectural and Transportation Barriers Compliance Board Electronic and Information Technology (EIT) Accessibility Standards (36 CFR part 1194).
(End of Clause)
H.12 LC52.239-6 ASSESSMENT AND AUTHORIZATION PRIVACY REQUIREMENTS (JUL
2016)
The contractor shall be responsible for the following privacy and security safeguards:
1. To the extent required to carry out the assessment and authorization process and continuous monitoring, to safeguard against threats and hazards to the security, integrity, and confidentiality of any non-public Library data collected and stored by the contractor, the contractor shall afford the Library access to the contractor’s facilities, installations, technical capabilities, operations, documentation, records, and databases.
2. The Library has the right to perform manual or automated audits, scans, reviews, or other inspections of the contractor’s IT environment being used to provide or facilitate services for the Library. In accordance with the Federal Acquisitions Regulations (FAR) clause 52.239-1, contractor shall be responsible for the following privacy and security safeguards:
(a) The contractor shall not publish or disclose in any manner, without the Contracting Officer’s written consent, the details of any safeguards either designed or developed by the contractor under this contract or otherwise provided by the Library.
(b) To the extent required to carry out a program of inspection to safeguard against threats and hazards to the security, integrity, and confidentiality of Library data, the contractor shall afford the Library access to the contractor’s facilities, installations, technical capabilities, operations, documentation, records, and databases within 72 hours. The program of inspection shall include:
i. Authenticated and unauthenticated operating system/network vulnerability scans
ii. Authenticated and unauthenticated web application vulnerability scans
iii. Authenticated and unauthenticated database application vulnerability scans
iv. Automated scans can be performed by Library personnel, or agents acting on behalf of the Library, using Library operated equipment, and Library specified tools.
(c) If new or unanticipated threats or hazards are discovered by either the Library or the contractor, or if existing safeguards have ceased to function, the discoverer shall immediately bring the situation to the attention of the other party.
3. If the contractor chooses to run its own automated scans or audits, results from these scans may, at the Library’s discretion, be accepted in lieu of Library performed vulnerability scans. In these cases, scanning tools and their configuration shall be approved by the Library. In addition, the results of contractor-conducted scans shall be provided, in full, to the Library.
4. SENSITIVE INFORMATION STORAGE. In addition to the requirements of LC52.239-1, Sensitive But Unclassified (SBU) information, data, and/or equipment will only be disclosed to authorized personnel on a Need-To-Know basis. The contractor shall establish appropriate administrative, technical, and physical safeguards to ensure the security and confidentiality of this information, data, and/or equipment is properly protected.
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 .