Questions - USCA25R0146 USCOURTS OOB Replacement Solution.xlsx
XLSX spreadsheet 23 KB Posted
- Attached to
- Out-Of-Band (OOB) Replacement Solution
- Solicitation number
- IMD240175
- Issued by
-
Administrative Office of the U.S. Courts
About this file
The document is a Q&A file for the USCA25R0146 USCOURTS Out-Of-Band (OOB) Replacement Solution solicitation. The Administrative Office of the U.S. Courts is seeking an IT Out of Band Management (OOBM) solution with specific technical requirements, including multi-factor authentication, LTE cellular modem support, and high availability capabilities across two data centers. The procurement is a Blanket Purchase Agreement (BPA) for replacing the current OOB solution, with deployment locations to be determined by future funding levels and specific call-offs.
Key technical specifications include: 100% device coverage with both in-band (Ethernet) and out-of-band (LTE) access, support for multiple cellular carriers, and a 5-minute or less cellular failover time. The solicitation includes 80 hours of professional services for solution setup and testing. Pricing will consider quantity discounts, and the solution must be hosted within U.S. Courts data centers. The procurement is not FAR-based and is specifically for the Judiciary, with potential expansion to over 500 local court locations. New judiciary locations in cities like Salt Lake City, Arlington, and Savannah are anticipated for future deployment.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Tab 14 - USCA25R0146 0001.pdf | ||
| Tab 14 - Attachment 2 - OOB Replacement Solution Requirements Workbook _20250423.xlsx | XLSX spreadsheet | |
| Tab 14 - Attachment 1 - OOB BPA PWS Final.pdf | ||
| Tab 14 - USCA25R0146 Final 20250512.pdf | ||
| Tab 14 - Attachment 3 - DCN site list.xlsx | XLSX spreadsheet |
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
| # | Document / Attachment | Location | Reference | Question | Answer |
| 1 | Attachment 2 | Tab 3 / Row 32 | The OOB management solution shall be capable of providing multi-factor authentication. | To enhance security and streamline access for the OOB management solution, does the RFQ require the 8-port console server to support multi-factor authentication (MFA) and single sign-on (SSO) directly on the device, without the need for a management server like Lighthouse or external authentication systems, ensuring robust and simplified user authentication? | Yes, MFA and SSO is required but not directly on the device. |
| 2 | Attachment 2 | Tab 3 / Row 31 | The OOB management software and devices shall have local authentication capabilities and allow for creation of local users and groups accounts. | To maximize the security of local user and group accounts for OOBM, does the RFQ require the 8-port console server to support two-factor authentication (2FA) using one-time passwords (OTP) and RSA tokens directly on the device, without the need for an external server or application, ensuring robust protection against unauthorized access? | No, MFA is not required to be stored on the device. If the device is strictly OOB, then only the local device credentials should be required. |
| 3 | Attachment 2 | Tab 3 / Row 6 | The solution shall include an LTE cellular modem capable of supporting multiple carrier networks for signal coverage flexibility. (e.g. Verizon, AT&T, T-Mobile) | To ensure long-term scalability and compatibility with both current 4G LTE and emerging 5G networks across major U.S. carriers (T-Mobile, AT&T, Verizon) without requiring hardware upgrades, does the RFQ require the 8-port console server to include a multi-carrier modem that supports both 4G and 5G connectivity, enabling seamless transitions to high-speed, low-latency 5G networks while maintaining reliable 4G failover? | 5G capability is desirable but not required. |
| 4 | Attachment 2 | Tab 3 / Row 6 | The solution shall include an LTE cellular modem capable of supporting multiple carrier networks for signal coverage flexibility. (e.g. Verizon, AT&T, T-Mobile) | Will the government provide a solution that supports Starlink in addition to an LTE modem capable of supporting multiple carrier network with a higher evaluation score than one that only supports an LTE cellular modem capability? | No |
| 5 | Attachment 2 | Tab 3 / Row 5 | Due to the lack of availability of Plain Old Telephone Service (POTS) telephone service in many locations, the OOB management devices shall support US Courts data network in-band (Ethernet) via US Courts intranet; and out-of-band (LTE) connection to management of Network devices via LTE cellular service. | What percentage of OOB management devices leverage US Courts data network in-band (Ethernet) via US Courts intranet versus out-of-band (LTE) connection to management of Network devices via LTE cellular service? | 100%. Every device will need both in-band (ethernet) and out-of-band (LTE) access. |
| 6 | Attachment 2 | Tab 3 / Row 11 | The solution shall be able to provide managed LTE services from multiple providers (ex. AT&T, Verizon) to ensure that the strongest LTE signal is being utilized at each location. | What is the acceptable latency policy/timeframe for Cellular failover from one carrier to another? For example, if we are failing over from ATT to Verizon is it accaptable to have a 30 second latency, 1 minute latency, 5 minute latency, etc? Please clarify this requirement. | If a LTE carrier goes down, 5 minutes or less is acceptable for cellular carrier failover. For the OOB solution, the priority is reliability and availability over speed. A typical practical guideline for LTE latency is an average of less than 150 ms, which is considered acceptable for OOB management operations. |
| 7 | Attachment 2 | Tab 3 / Row 13 | The OOB management software shall have high availability capability, with instances running at each of the two US Courts data centers (i.e. active standby). | If the solution proposed supports both Active/Passive AND Active/Active (Real-Time Data Sync/Replication), will the government provide a higher evaluation score than a solution that only supports Active/Passive? | No |
| 8 | Attachment 2 & Attachment 1 (PWS) | Tab 3 / Row 36 | Provide 80 hours of professional services to assist with testing, developing documentation, work instructions, and standard operating procedures (SOPs) for support and court staff | The requirement for Task 2 on Attachment 2 is not replicated in the PWS in Attachment 1. Will the government please confirm this requirment and provide clarification on its expectations for the work performed in the 80 hours? |
| Additionally, will the Government please clarify what professional services arrangement is required for this engagement - e.g. MSA, SOW, TE/TM, etc? | To clarify, the 80 hours will be used to assist with setting up the management devices and software solution in our data centers. Also to assist us as we test the solution with a couple of our pilot sites so our engineers can have familiarity with the solution. For additional clarity, the 80 hours is expected to be spread across multiple support sessions. | |||||
| 9 | Attachment 2 | Tab 4 | N/A | Will the Government consider offers that include quantity discounts? If yes, may an offeror include extra lines in the Attachment 2 / Tab 4 for evaluation? Alternatively, may an offeror provide additional Attachment 2 Tab 4 responses that include quantity-based pricing? | The GOV will consider quantity discounts. Place your discount information in Tab 5 Pricing Notes in Attachment 2. | |
| 10 | Attachment 2 | Tab 4 | N/A | Will the Government provide an anticipated deployment schedule that includes quantities for the base year and each option year? | This is a BPA, the number and locations of the instalations have been identified in Attachment 3. The number and location of the installations will be identified in each Call agaibnst this BPA. There is no deployment schedule or timeline for what locations will be installed at any particular time. The number of installs in each Call is dependent on the funding levels for this requirement. | |
| 11 | Tab+14+-+USCA25R0146+Final+20250512 | Page 17-18 | L.3.1 - Quote Format / Information: For documents, the proposal page size shall be 8.5 x 11 inches. Pages may be double or single-spaced. Except for the reproduced sections of the solicitation document, the text size shall be no less than Times New Roman 10 point. Use at least .5-inch margins on all sides of each page. |
L.3.3.2 - Volume II, Technical Volume: -The technical description shall not exceed 25 pages. 11pt. Times new Roman Font on 8½’ x 11” standard paper,
| with 1” margins. | There is a conflict between Section L.3.1 and L.3.3.2. Will the government confirm the font requirement and margin requirement for proposal submissions? | Section L. 3.1 requirements will be revised to match section L.3.3.2. | ||||
| 12 | N/A | N/A | N/A | Will the 500+ local court locations be permitted to independently procure hardware and software under this BPA for POTs use cases such as duress and elevator lines, with invoicing and billing handled separately from the Administrative Office of the US Courts? | Refer to solicitation section G.1, paragraph 5. Authorized Users | |
| 13 | N/A | N/A | N/A | Does the court require the Remote Power control as part of the RFQ? | Desirable but not mandatory. | |
| 14 | N/A | N/A | N/A | In the DCN Site List why are Salt Lake City, UT; Greenville, MS; Arlington, VA; Savannah, GA; Flagstaff, AX; and Pinehurst, NC highlighted in yellow? | These are new judiciary locations that are not occupied currently but will be within the next couple years. | |
| 15 | N/A | N/A | N/A | Can you please provide the incumbent and the previous contract award details? | This is a new requirement, there is no incumbent. | |
| 16 | N/A | N/A | N/A | Would a secure cloud hosting solution be considered to host the management software instead of a solution hosted within USCourts data centers? | No |
File details come from the government source that posted it. Updated .