030ADV24R0016 QA 3.xlsx
XLSX spreadsheet 11 KB Posted
- Solicitation number
- 030ADV24R0016
- Issued by
-
Library of Congress
About this file
This document contains a solicitation for a federal contract opportunity along with related questions and responses. The Library of Congress requires a range of Microsoft cloud services delivered through an Indefinite Delivery/Indefinite Quantity contract, including Azure cloud computing, storage, software and services. This will cover the Library's information technology needs currently and for future growth, including development on Microsoft Azure. Services will include Microsoft Software as a Service subscriptions and Azure and Microsoft 365 support offerings. Questions are due by February 8, 2024 and award is expected on or around March 1, 2024. Pricing will consist of passing through Azure and support costs from Microsoft.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 030ADV24R0016 0001 Final.pdf | ||
| 030ADV24R0016 QA 2.xlsx | XLSX spreadsheet | |
| 030ADV24R0016 QA 1.xlsx | XLSX spreadsheet | |
| 030ADV24R0016 Brand-name Cloud Services Solicitation.pdf | ||
| Attachment J1 - Microsoft Cloud Services Pricing and Requirements Matrix.xlsx | XLSX spreadsheet | |
| Brand Name Justification Microsoft Azure Cloud Services Redacted.pdf |
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
Sheet1
| Question # | Reference | Question | Library Response |
| 1 | B.1 | The LOC is requesting bundled CLINs for a base plus 4 Option year IDIQ, Microsoft will only provide a quote to LSPs for 3 yrs for the LOC’s anticipated EA requirements and Unified Support. Microsoft must get internal approval to quote beyond the standard 3 yr EA/Unified support and based on conversations with MS they did not appear to get approval for the LOC in advance of this RFQ. | It is understood that MS will facilitate/ be amendable to this. |
| 2 | Section B.2 and C.2 | The LOC’s intent appears to be consolidating their disparate Microsoft EAs into one single enrollment account, this effort would establishing a new Enterprise Agreement with Microsoft and LOC would have to commit to new license agreements, metrics, and T+Cs with Microsoft, which appears to contradict the language in B.2 | Yes that is our intent. B.2 is standard clause language now being evaluated for possible tailoring or removal. |
| 3 | Section C.3.2 | Support SLAs cannot be guaranteed by Microsoft or [contractor] for one hour response time. | Microsoft’s SLA for support tickets for P1 is one hour to acknowledge (pick Up) the ticket and assign to an engineer. Note that some task orders are subject to negotiated terms when guarantees cannot be met (task order specific). |
| 4 | C.3.6 | Microsoft and [contractor] cannot bill monthly for anything beyond Azure consumption, EA licenses can be trued up (increased) at any point over the PoP of the Contract but they cannot be trued down (decreased) or removed until the anniversary of the EA renewal. EA annual payments and Unified Support are renewed annually and not monthly. | No issue with this |
| 5 | C.3.6 | When does the LOC existing EA’s notated in Attachment J2 expire? We have no idea how or what licenses/metrics the LOC wants to keep or migrate into a master Enterprise Agreement and Microsoft was not able to provide [Contractor's name redacted] with clear consolidation or migration timeframes. [Redacted] suggest the LOC conduct a SAM assessment to determine licenses quantities, metrics, and business requirements to ensure a master EA is created correctly. Based on the limited information we have from the J2, it is not clear on expiration, current PoP or quantity or pricing. There are license minimum requirements for an EA that must be met at inception of the agreement. | The minimum license agreement is the current EA for M365 that is in place. We are not accounting for any additional subscriptions that will migrate since other EAs are academic and the transition is not clear at this time. Indefinite nature of the contract. |
| 6 | C.3.7 | [contractor] would need to perform application rationalization for the LOE for the lift and shift of the on-premises applications destined to be re-platformed for Azure, we would conduct this effort through a services engagement, but without the current scope of the anticipated IaaS needs in Azure we cannot assume the LCATs or cost of Azure resources until the application rationalization would be performed, so cannot price out IaaS costs for MS Azure consumption at this juncture. | The Library is not seeking assistance for the LOE for application migrations in to Azure. The Library will estimate the initial cost for their Azure services using the public pricing portal. The vendor is essentially passing through Azure services and support to Microsoft and acting at the Billing agent. Additional discounts on top of pass-throughs are understood to likely, but not necessarily be, zero percent / not applied. Mark (if any) discounts on the discount pricing tab. |
| 7 | |||
| 8 | |||
| 9 | |||
| 10 | |||
| 11 | |||
| 12 | |||
| 13 | |||
| 14 | |||
| 15 | |||
| 16 | |||
| 17 | |||
| 18 | |||
| 19 | |||
| 20 | |||
| 21 | |||
| 22 | |||
| 23 | |||
| 24 | |||
| 25 | |||
| 26 |
File details come from the government source that posted it. Updated .