Amendment 0001_030ADV24R0004 0001.pdf

5. PROJECT NUMBER (if applicable)

CODE7. ADMINISTERED BY

2. AMENDMENT/MODIFICATION NUMBER

CODE

6. ISSUED BY

8. NAME AND ADDRESS OF CONTRACTOR

4. REQUISITION/PURCHASE REQ. NUMBER3. EFFECTIVE DATE

9A. AMENDMENT OF SOLICITATION NUMBER

9B. DATED

PAGE OF PAGES

10A. MODIFICATION OF CONTRACT/ORDER NUMBER

10B. DATED

BPA NO. 1. CONTRACT ID CODE

FACILITY CODECODE

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers

E. IMPORTANT:

is extended,

(a) By completing Items 8 and 15, and returning __________ copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or (c) By separate letter or electronic communication which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY is not extended.

12. ACCOUNTING AND APPROPRIATION DATA

(REV. 11/2016)

is required to sign this document and return ___________ copies to the issuing office.is not, A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER NO. IN ITEM 10A.

15C. DATE SIGNED

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by letter or electronic communication, provided each letter or electronic communication makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER

Contractor

16C. DATE SIGNED

14. DESCRIPTION OF AMENDMENT/MODIFICATION

16B. UNITED STATES OF AMERICA

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER 16A. NAME AND TITLE OF CONTRACTING OFFICER

15B. CONTRACTOR/OFFEROR

STANDARD FORM 30 PREVIOUS EDITION NOT USABLE

Prescribed by GSA - FAR (48 CFR) 53.243

(Type or print) (Type or print)

(Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

(Number, street, county, State and ZIP Code)

(If other than Item 6)

(Specify type of modification and authority)

(such as changes in paying office, appropriation date, etc.)

(If required)

(SEE ITEM 11)

(SEE ITEM 13)

(X)

CHECK

ONE

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS,

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

(Signature of person authorized to sign) (Signature of Contracting Officer)

1 15

Contracts and Grants Directorate Library of Congress

101 Independence Ave. SE LA 325 Washington DC 20540-9411

Contracts & Grants Directorate Library of Congress

LA 325

101 Independence Av SE Washington DC 20540-9411

To all Offerors/Bidders

030ADV24R0004

12-19-2023

X

See CONTINUATION Page x 1

See page 2.

Price, Veronica

BLOCK 14 ADDENDUM

The purpose of this Amendment 0001 is to respond to questions submitted via revised J4 attachment, and revise Section C Statement of Work, and Section L, clause LC52.215-1. All other documents and conditions remain the same.

030ADV24R0004 0001 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 maintenance activities involve in bug fixing of current apps, updating the app to adopt to new versions and API levels of the underlaying OS (such as iOS, Android, FireOS, and Windows), adapting the apps to use new frameworks if current framework become obsolete or deprecated, and adding new features to the current apps. 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 prototype or proof-of-concept applications created for the platform and chosen for release by NLS.

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 prototype or proof-of-concept applications created for the platform and chosen for release by NLS.

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 prototype or proof-of-concept applications created for the platform and chosen for release by NLS.

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 prototype or proof-of-concept applications created for the platform and chosen for release by NLS.

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)

030ADV24R0004 0001 Section J

PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

SECTION J - LIST OF ATTACHMENTS

Identifier Title Date Number of Pages

Attachment J1 NLS Agile Methodology Guide 11/30/2023 47 Pages

Attachment J2 QASP 11/30/2023 1 Sheet

Attachment J3 Pricing Schedule 11/30/2023 4 Sheets

Attachment J4 Questions and Answers 01/03/2024 1 sheet

Attachment J5 Initial Task Order 1 iOS 11/30/2023 2 Sheets

Attachment J6 Initial Task Order 2 Android 11/30/2023 2 Sheets

Attachment J7 Initial Task Order 3 Fire iOS 11/30/2023 2 Sheets

030ADV24R0004 0001 Section L

SECTION L - INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

LC52.215-1 PROPOSAL SUBMISSION INSTRUCTIONS - BEST VALUE TRADE-OFF (JUL 2016)

L1. General Instructions to Offerors

This section discusses general proposal submission instructions, proposal requirements, and information regarding the formatting of proposals. Three (3) potential Task orders will be awarded at the same time as the IDIQ contract(s). Any IDIQ contractor not receiving a Task Order will have the minimum guarantee obligated at time of award.

L2. Proposal Submission/Delivery Instructions

Offerors shall submit their proposals to Cristina Vega, Contract Specialist, at crvega@loc.gov, with a carbon copy (cc:) to Veronica Price, Contracting Officer, at vprice@loc.gov. Proposals are due no later than the date and time shown in Box 8 on the first page of this solicitation. Offerors must not submit zipped files. The email containing your offer proposal must have the RFP number in the subject line (030ADV24R0004). The total maximum file size of all attached files cannot exceed 20MB due to restrictions on the LOC’s email system. If needed, offerors may submit multiple emails and ensure they are clearly identified. Proposals must include the solicitation number, business name, mailing address, telephone number, and SAM Unique Entity Identifier (UEI) number.

L3. Questions

Offerors shall submit their questions regarding this work to Cristina Vega, Contract Specialist, at crvega@loc.gov with a carbon copy (cc) to Veronica Price, Contracting Officer, at vprice@loc.gov. Questions are due no later than 12/28/2023 at 3:00 PM, Eastern Time. It is the Library’s intention to award without engaging in discussions/clarifications if possible, so questions regarding all aspects are highly encouraged. All questions and answers shall be provided to all potential offerors, but it shall not be revealed which offeror asked which questions. The Library reserves the right to ignore questions received after this due date. However, it also reserves the right to answer pressing and pertinent questions received after this date.

L4. Proposal Contents:

Offerors must propose on one or more of the Performance areas, preference will be given for Offerors who are able perform in multiple performance areas. All Offerors must submit a Corporate Experience and Technical Approach volume for the

IDIQ.

Offerors may submit proposals for the initial task orders in which case, an Offeror must submit Corporate Experience and a Technical Approach/Staffing volume for the applicable task order. All submitted proposals must contain the following separate volumes, in the stated order, as indicated below:

Volume 1). Corporate Experience

a) IDIQ Corporate Experience.

Offerors shall submit information regarding their corporate experience in performing work substantively similar to the requirements of the IDIQ Statement of Work. Proposals shall include:

A maximum of three (3) examples of work experience in performing each of the six (6) Performance Areas in the IDIQ Statement of Work for which they would like to be considered, including the dates of contract performance, a project summary, and results/outcomes of the project.

Information for the performance areas proposed, in addition to any optional performance area(s) identified in the IDIQ Statement of Work. Preference will be given to offerors that have BARD Mobile experience (iOS, Android, FireOS, and Express).

If subcontracting is proposed, offerors must explain the means for ensuring quality and timeliness of all proposed subcontractors’ performance. Preference will be given to offerors who can execute across all proposed platform performance areas without subcontracting.

The page limit for this section is 10 pages per performance area.

b) Task Order Corporate Experience.

Offerors may submit proposals for the initial task orders for which they would like to be consider, in which case an Offeror must submit a separate Corporate Experience for the applicable task order(s).

Offerors must submit Corporate Experience in performing work substantively similar to the Statement of Work of the applicable task order(s) in Attachment J5 [iOS], J6 [Fire] or J7 [Android] for the PA(s) for which the Offeror is proposing. This information shall be provided as a separate addendum section in the IDIQ Volume 1 submission.

(Example: Addendum #1 Task Order 1 iOS Corporate Experience, Addendum #2 Task Order 2 Android Corporate Experience, etc.)

Offerors shall:

Demonstrate by example previous experience performing any software/app development work similar to the requisite task order(s) and publishing to the relevant app stores.

The page limit for each task order, corporate experience section is 5 pages.

The task order information shall be provided as a separate addendum section in the IDIQ Volume 1 submission.

(Example: Addendum #1 Task Order 1 iOS Corporate Experience, Addendum #2 Task Order 2 Android Corporate Experience, etc.)

Volume 2). Technical Approach (i.e., Technical Approach/Staffing)

All Offerors must submit a Technical Capability volume for the IDIQ. Offerors must provide a Key Personnel Staffing Plan, including resumes, that demonstrate the requirements listed in Section C.5.

Offerors may submit proposals for the initial task orders, in which case an Offeror must submit Technical Capability for the applicable task order. A separate Technical Approach section and Task Order Key Personnel Staffing Plan is required for the applicable task order(s) contained in Attachment J5 [iOS], J6 [Fire], or J7 [Android] for the PA(s) that the Offeror is proposing.

The task order information shall be provided as a separate addendum section in the IDIQ Volume 2 submission.

(Example: Addendum #1 Task Order 1 iOS Technical Approach, Addendum #2 Task Order 2 Android Technical Approach, etc.)

a) IDIQ Technical Approach

The Offeror shall provide information regarding how they plan to organize, staff, and manage the IDIQ contract and the means that will be used to accomplish the requirements outlined in the Statement of Work for the IDIQ in Section C entitled Descriptions/Specifications/Statement of Work. This response must include any significant work performed in these areas over the past three (3) years and include all expertise anticipated to support the IDIQ requirements.

Offerors shall also submit resumes reflecting relevant experience of their proposed Key Personnel in the performance areas identified in the Statement of Work for which they would like to be considered. If the intent is to use subcontractors, the prime must disclose the extent to which such firms are intended to be utilized, how the offeror will manage subcontractors, and the performance areas where they may be used. Offeror shall complete clause LC52.244-1 detailing the potential dollar value to be associated with the subcontracting work.

This volume is limited to 10 pages per performance area.

b) Initial Order(s) Technical Approach/Staffing

Offerors must describe an approach or process to fulfill the requirements of the task order(s) statement of work in Attachment J5 [iOS], J6 [Fire], or J7 [Android] associated with the PA(s) that the Offeror is proposing. The Library will review the proposal for demonstrated experience in app development projects and management thereof conforming to an agile process. The Library will review the proposed contractor staff to determine if they possess experience to meet all requirements as outlined in the Initial Order(s) Statement(s) of Work. Offerors shall include resumes for their proposed key personnel, unless personnel overlap in which case offerors may just provide reference to the IDIQ resume for the respective, proposed personnel.

This volume is limited to 10 pages for each order’s response.

Volume 3). Past Performance

Offerors shall provide detailed references for a maximum of five (5) relevant current contracts and/or completed contracts (Government or commercial) performed within five (5) years from the solicitation release date that are relevant to the performance areas in this procurement that the Offeror is proposing. References may be for the prime or subcontractors; however, at least one (1) shall concern the relevant past performance of the prime. To ensure inclusion of all references in the evaluation process, the offeror is encouraged to provide the Library with the most current data on each reference. The information must be clear as to whether the work was performed by the prime contractor or a subcontractor. Offerors shall limit their response to the information requested below:

(1) Customer name, address, e-mail address and telephone number;

(2) Contract number, period of performance, and total dollar amount;

(3) Point of contact (names and telephone numbers of the CO and CO's Technical Representative);

(4) A description of:

(i) How the submitted reference demonstrates the Offeror’s performance as a prime or subcontractor for a contract of similar size and scope and the same type of services being solicited under this solicitation;

(ii) The associated service level agreements and the Offeror’s success in meeting them;

(iii) The Offeror’s overall management control of any subcontractor(s) for this contract and how this relationship provided quality service to the customer;

(iv) The quality of technical support the Offeror provided to the customers under this contract and the Offeror’s ability to face challenges resulting from such an effort; and

(v) What solutions and how the Offeror provided solutions to resolve any problems encountered for the referenced contract.

Volume 4). Pricing Volume

IDIQ Pricing Schedule:

For the IDIQ, Offerors shall submit pricing using Attachment J3 – Pricing Schedule, Tab 1. Offerors shall propose pricing for each of the performance area the offeror wishes to be considered for award. Offerors must provide pricing for the entire seven ordering period, by year, for each performance area. Sprint pricing shall be proposed on a firm-fixed price basis.

Initial Order(s) Pricing:

For the Initial Orders, Offerors shall provide a total task order price for each applicable task order by completing J-4 at Tabs 2, 3, or 4. Offerors shall provide the necessary combinations of 4 or 2 week sprints to complete the task order Statements of Work contained in Attachments J5, J6, or J7. Sprint pricing shall be proposed in accordance with the firm fixed price sprint prices identified in Tab 1 (IDIQ pricing), along with any discounts offered for the order. Initial Order rates may be less than the IDIQ offered rates, as discounts are encouraged and make an offeror’s pricing more favorable to the Government. Offerors shall clearly identify all additional pricing discounts in its accompanying pricing narrative.

Clause LC52.244-1 must be completed if any Subcontracting is expected at the IDIQ and Task Order level.

End of Document