19AQMM26Q0271 QandA FINAL.pdf

# Solicitation Reference Section/Exhibit Question Answer

1 Evaluation Factor 1 Section L, Factor 1 requires the offeror or its subcontractor/teaming partner to be licensed and incorporated to do business in Mexico. Please confirm this requirement is met when a named Mexican-incorporated subcontractor or teaming partner holds that status, rather than the prime offeror itself.

Yes; That is acceptable as the arrangement is consistent with Mexican law.

SICAS integration (SOW 4.6; Attachment 2, Item 015).

The brand-name justification confirms SICAS uses a web-services API with Google Meet integration. Will the Government provide the SICAS API documentation, credentials, and a non-production test environment to the awardee to perform the integration? And is SICAS a single uniform system across the candidate states, or does each state judiciary run a different version?

Yes, the required API documentation will be provided to the selected vendor upon contract award. SICAS is a uniform system; however, the management model is handled individually on a state-by-state basis.

3 Attachment A, Item 005

Does "150 MB dedicated" require a clear-channel circuit with a committed information rate, or is a business-grade symmetric service acceptable?

The requirement should be understood as a guaranteed bandwidth capacity for the service, preferably expressed as dedicated symmetric 150 Mbps, with enterprise-grade quality conditions. A "clear-channel" or point-to-point circuit is not strictly required; a business-grade symmetric service is acceptable, provided the carrier guarantees a committed information rate (CIR), link stability, low latency, low jitter, minimal packet loss, and service levels through a Service Level Agreement (SLA).

4 Attachment A, Item 005 For remote penitentiary sites without terrestrial fiber, is satellite service (for example, Starlink Business/Priority) acceptable to meet this requirement?

The acceptability of satellite service will depend on the outcomes of the working group sessions, which will determine the specific penitentiary facilities where the system is to be installed.

5 Attachment A, Item 005 Given the sensitivity of the judicial data, does the Government require in-country or terrestrial data routing, or is satellite routing acceptable?

The data routing requirements will depend on the outcomes of the working group sessions, which will determine the specific penitentiary facilities where the system is to be installed.

6 Place of Performance Place of performance. Which states does the Government anticipate for the base year, and roughly how many penitentiary and courtroom sites per state should offerors plan to equip and connect?

The selected contractor will be informed of the two specific states for the base year upon contract award.

The number of penitentiary facilities per state may vary, however will not exceed five (5) per state. Each state will only have one judiciary site. The total equipment per state will not exceed the equipment specified on Attachment A.

7 Attachment 6 Secure Software Development Attestation (Attachment 6). Should the attestation come from the software producer (e.g., Google, Microsoft), or from the offeror as the integrator/reseller of those commercial products?

The form should be filled out by the software producer per the form instructions:

"Software Producer Information Please provide a description of the software and information about the software producer. All fields in the attestation form are required to be appropriately completed by the software producer. Incomplete forms will not be accepted.

The form must be signed by the Chief Executive Officer (CEO) of the software producer or their designee, who must be an employee of the software producer and have the authority to bind the corporation. "

8 SOW 8.2.1.1

Equipment consolidation and inspection location. SOW 8.2.1.1 specifies a contractor warehouse in Mexico City for initial inventory and inspection. Since the place of performance is the northern border states, may the contractor consolidate and stage equipment closer to the awarded sites (for example, in Sonora), with the Government's physical inspection and Receiving Report conducted there rather than in Mexico City?

For security and logistical reasons, and to facilitate physical inventory inspections by INL, equipment consolidation and inventory must be conducted in Mexico City (CDMX).

9 Teaming, Set-Aside Structure & Eligibility To satisfy the Factor 1 threshold (“licensed and incorporated to do business in Mexico”), does the Government confirm that this requirement may be met by the prime’s Mexican-incorporated subcontractor or teaming partner, rather than by the prime offeror itself?

Yes, see Answer #1.

10 Teaming, Set-Aside Structure & Eligibility Under FAR 52.219-14 (Limitations on Subcontracting), what percentage of the contract amount must be performed by the prime and similarly situated entities, and how will the Government treat work performed by Mexican subcontractors in that calculation?

Contractors should apply the clause as they would for any other procurement conducted in the U.S. Mexican subcontractors could be considered a U.S. small businesses if they qualify as such based on the SBA government contracting size rules.

11 Teaming, Set-Aside Structure & Eligibility Will a Mexican-incorporated subcontractor be treated as a “similarly situated entity” for purposes of the limitations-on-subcontracting analysis? No special adjustments to the application of the clause will be made. See question and answer 10.

12 Teaming, Set-Aside Structure & Eligibility Are formal teaming arrangements or SBA-approved joint ventures permitted for this requirement, and is either structure preferred by the Government?

The government has no preference as long as the offeror complies with small business set-aside requirements.

13 Teaming, Set-Aside Structure & Eligibility Must all proposed subcontractors hold an active SAM.gov registration at the time of quote submission, or only at the time of award?

As this is a small business set aside, at a minimum the prime contractor must be registered in SAM as a small business under the correct NAICS code at the time the quote is submitted.

14 Technical Capacity & Scope Can the Government confirm the exact number of courts and penitentiary facilities to be equipped per state, and identify which two states constitute the base year versus the option year?

The places of performance will be in border states as described in the SOW; the selected contractor will be informed of the 2 specific base year states upon contract award. The number of penitentiary facilities per state may vary, but will not exceed five per state. Only one judiciary site is required per state. Regardless of the number of total sites per state, equipment in excess of what is specified on Attachment A is not required.

15 Technical Capacity & Scope Will the Government provide a baseline inventory of existing network, endpoint, and audiovisual infrastructure at each site, or arrange pre-award or post-award site surveys?

As specified in Attachment 1 (SOW), the selected contractor shall conduct initial workshop sessions with the designated Government of Mexico (GOM) partners at each project location following contract award. These sessions will ensure that all sites provide the necessary support and infrastructure for successful project implementation.

16 Technical Capacity & Scope For the dedicated 150 MB communication links, is the contractor responsible for procuring and maintaining these from Mexican carriers, and are the recurring monthly costs to be borne by the contractor throughout the period of performance?

Yes, the contractor is responsible for procuring and maintaining the dedicated 150 Mbps communication links through carriers operating in Mexico. The recurring costs associated with these links shall be covered by the contractor for the entire period of performance on a per-state basis.

17 Technical Capacity & Scope For the brand-name items (Microsoft Office, Google Workspace Enterprise, Google Cloud), must the contractor procure the licenses, and should they be provisioned under a Government of Mexico tenant or under the contractor’s tenant? Please confirm the required number of seats.

Yes, the contractor is responsible for procuring all brand-name licenses (Microsoft Office, Google Workspace Enterprise, and Google Cloud). All licenses shall be provisioned under a Government of Mexico tenant. The required number of seats for each license is specified in Attachment A.

18 Technical Capacity & Scope Does the Government require that recorded hearings and associated data reside within Mexico (data residency), or is a U.S. or global Google Cloud region acceptable?

All recorded hearings and associated data shall reside within Mexican territory. A U.S. or global Google Cloud region is not acceptable for this requirement.

19 Technical Capacity & Scope Will the Government of Mexico provide SICAS API documentation, a test environment, and a technical point of contact to enable the required scheduling and video-delivery integration?

Yes, the required API documentation and corresponding technical POC will be provided to the selected vendor upon contract award.

20 Technical Capacity & Scope What is the required retention period and storage volume for recorded hearings, and please confirm any WORM, legal-hold, or chain-of-custody requirements and who holds ownership of the data.

The required storage workflow and retention specifications, including WORM, legal-hold, and chain-of-custody requirements, will be provided to the selected contractor upon contract award. Ownership of all data shall remain with the Judicial Branch and the Penitentiary System of the corresponding beneficiary state.

21 Technical Capacity & Scope Is any U.S. security accreditation (e.g., FedRAMP, FISMA, NIST SP 800-53, or an ATO) required for the cloud and recording environment, or is information assurance the responsibility of the Government of Mexico?

For cloud security requirements and information assurance specifications, please refer to Attachment A, Attachment 5, and Attachment 6.

19AQMM26Q0271 Mexican Criminal Courts Telepresence (INL Mexico): Solicitation Q&A

22 Technical Capacity & Scope For non-brand-name hardware, are specific OEMs or models mandated, or will “or-equal” substitutions meeting the stated specifications be accepted?

Yes, brand name of equal alternative products that meet the salient characteristics/ specifications will be accepted

Implementation, Judicial Environment, Security & Anti-Corruption

Will INL or the U.S. Embassy provide formal letters of introduction and identify the authorizing official at each state judiciary and penitentiary to legitimize the contractor’s access and coordination?

Yes, the U.S. Government and the selected contractor will conduct a kick-off meeting with the corresponding Government of Mexico counterparts. Access and coordination will be overseen by the U.S. Government to ensure the contractor's accessibility to all relevant state judiciary and penitentiary locations.

Implementation, Judicial Environment, Security & Anti-Corruption

Who bears responsibility for the physical security of contractor personnel and equipment during installation in the northern border states, and will INL provide threat briefings or security coordination?

The Department of State does not designated Mexico as a High Threat/High Risk post. The contractor assumes full responsibility for the physical security of its personnel and equipment during installation and operations in the northern border states. USG will not provide threat briefings, as all installation and configuration activities will take place within secure, surveilled Government of Mexico facilities. Prior to project execution, the USG and GOM will formalize their commitment through a Memorandum of Understanding (MOU), consistent with the established framework used in similar joint projects. GOM security personnel will be informed and will facilitate the appropriate conditions to ensure safe and unobstructed access within GOM facilities.

Implementation, Judicial Environment, Security & Anti-Corruption

If a local official solicits an improper payment or conditions site access on one, what is the Government’s prescribed reporting channel, and will any resulting access delays be treated as excusable for schedule purposes?

Any access delays resulting from improper payment solicitations or conditioned site access by a local official shall be treated as excusable delays.

Implementation, Judicial Environment, Security & Anti-Corruption

Will the Government provide guidance on permissible interactions with Mexican officials so that contractor personnel remain in compliance with the U.S. Foreign Corrupt Practices Act and applicable Mexican anti-corruption law?

Compliance with U.S. and Mexican law, including the U.S. Foreign Corrupt Practices Act and applicable Mexican anti-corruption regulations, is the sole responsibility of the contractor.

Implementation, Judicial Environment, Security & Anti-Corruption

What force majeure or excusable-delay provisions apply if deployment at a site is obstructed by organized-crime activity or by an official’s refusal to cooperate?

Any deployment delays resulting from organized-crime activity or an official's refusal to cooperate shall be treated as excusable delays under the terms of the contract.

Implementation, Judicial Environment, Security & Anti-Corruption

The SOW references evacuation due to injury — please clarify how personnel security incidents, medical evacuation, and associated costs are coordinated and allocated between the parties.

The SOW does not reference evacuation due to injury, and clause 52.225-19 is removed from the RFQ.

Implementation, Judicial Environment, Security & Anti-Corruption

Are contractor personnel subject to background vetting, credentialing, or site-badging by the Government of Mexico or the USG, and what lead time should be assumed for such clearances?

Contractor personnel are not expected to be subject to background vetting, credentialing, or site-badging requirements under this contract. Names, license plate numbers, and other information to facilitate access during installation may be required.

Implementation, Judicial Environment, Security & Anti-Corruption

Given that the detainees are TCO-related, what handling, classification, and access-control rules apply to recordings and personally identifiable information, and are there any restrictions on the nationality of contractor personnel with system access?

All installation and configuration activities will take place within secure, surveilled Government of Mexico facilities. Prior to project execution, the USG and GOM will formalize their commitment through a Memorandum of Understanding (MOU). GOM security personnel will be informed and will facilitate the appropriate conditions to ensure safe and controlled access within GOM facilities. There are no nationality restrictions on contractor personnel with system access under this contract.

31 Schedule, Period of Performance & Importation Please confirm the anticipated award date and the date of Notice to Proceed, and whether the September 1, 2026 start of performance is firm regardless of the actual award date.

No, the anticipated award and period of performance start dates will be adjusted based on the timing of the actual award.

32 Schedule, Period of Performance & Importation Will INL or the Embassy assist with customs clearance and importation through diplomatic channels, or is importation — including duties and IVA — entirely the contractor’s responsibility?

Customs clearance and importation, if required, including all applicable duties and IVA, are entirely the contractor's responsibility. Offerors are expected to demonstrate full command of this process through relevant past performance.

33 Schedule, Period of Performance & Importation May equipment be imported under an Embassy or diplomatic duty-and-tax exemption, or must the contractor pay and absorb Mexican import duties and IVA?

The contractor is responsible for all Mexican import duties and IVA associated with equipment importation.

However, Value Added Tax (VAT) (called IVA in Mexico) may be subject to reimbursement. All other import-related costs shall be absorbed by the contractor.

34 Schedule, Period of Performance & Importation Are partial, site-by-site deliveries and acceptances permitted, or must all base-year sites be commissioned and accepted simultaneously?

Partial, site-by-site deliveries and acceptances are permitted. All base-year sites are not required to be commissioned and accepted simultaneously.

35 Schedule, Period of Performance & Importation What is the anticipated decision date and the criteria for exercising the option year?

DOS will comply with the timelines stated in 52.217-9, however, if an earlier decision is made, that may be communicated to the contractor in advance of the deadlines stipulated in the clause.

36 Pricing, Payment & Financial Terms Is this requirement to be awarded as a single firm-fixed-price contract, or as a combination of fixed-price and recurring or subscription line items? Please confirm the contract type.

Everything is excepted to be firm-fixed price, but subscription services can be paid on a monthly basis (in arrears) consistent with customary commercial practice. CLIN 006 and CLIN 007 are direct reimbursements

37 Pricing, Payment & Financial Terms What are the payment terms — specifically, the invoicing cadence and the number of days for payment under the Prompt Payment Act from receipt of a proper invoice?

Prompt Payment Act applies per 31 U.S.C. 3903 which governs the timeline for payments and interest accrual. Commercial contracts under FAR Part 12 typically invoice no more frequently than monthly, however INL would consider more frequent invoices if advantageous and consistent with customary commercial practice.

38 Pricing, Payment & Financial Terms Through which system are invoices submitted (e.g., the Invoice Processing Platform), in what currency will payment be made (USD or MXN), and to which entity?

Invoices will be submitted through IPP in accordance with the incorporated INV-IPP clause included in the solicitation. The contract will be awarded in USD, and payments will be made in USD.

39 Pricing, Payment & Financial Terms How are recurring costs (dedicated bandwidth, cloud subscriptions, and licenses across the 12-month period) to be priced and paid — reimbursed monthly or as a fixed annual amount — and how does this carry into the option year?

The option year should be priced in isolation from the base year. Therefore, the pricing for the base year should cover the full cost of the licenses and hardware required for the base year implementation, even if license terms extend beyond the base year. As currently structured in the RFQ, a firm fixed price total is requested per state.

40 Pricing, Payment & Financial Terms Are any advance, milestone, or progress payments available to offset the upfront hardware procurement and importation outlay, or is payment made only upon delivery and acceptance?

Advance payments, milestones, or progress payments are not available as they are not customary for commercial contracts. However, the Government will accept, and make payment for all hardware procured and consolidated for Inspection at a centralized contractor controlled location in Mexico City, prior to installation at the state locations (CLINs X001). However, see amended SOW which clarifies that contractor remains responsible for the equipment through installation in the state sites.

41 Pricing, Payment & Financial Terms Regarding the Price Matrix (Attachment 2), must all line items be populated, and must quoted unit prices remain firm for the option year? Please see the instructions Tab on Attachment 2

42 Submission Mechanics & Compliance Please confirm the required submission method, any email or file-size limits and accepted formats, and confirm our understanding of the page limits and the items excluded from those limits (resumes, specification sheets, and past-performance forms).

Please review Section L.1. Quotations will only be accepted via email.

43 Submission Mechanics & Compliance For the C-SCRM requirement (Attachments 5 and 6), must each software producer (Google, Microsoft) submit its own SSDF self-attestation, or may the prime attest on the team’s behalf — and how should the contractor proceed if a producer’s attestation is pending in the CISA repository? Please also confirm that Past Performance Questionnaires (Attachment 4) returned by references directly to the Contracting Officer will be accepted up to the closing date.

See Question 7. If the software producers attestation is pending and beyond the prime contractor's control, then the contractor should explain in their technical quotation as an "exception or deviation" per section L.3(b) and provided Attachment 5 and Attachment 6 with the appropriate caveats.

44 L-0006 Questions Regarding Solicitation pg. 62 Will the Government grant a 10-day proposal submission extension to allow offerors sufficient time to evaluate the Government’s Q&A responses and finalize a compliant solution?

Extension already provided and synopsized on SAM.gov

Attachment 1 Attachment A 26Q0271

Storage Volume Sizing & Capacity Projections. The solicitation states the system must support "multiple, multi-participant video recording sessions." Please provide the following planning factors to accurately define storage infrastructure, system sizing, and cost estimation:

a) Initial Operational Capacity (Day 1): What is the estimated total data volume in Terabytes (TB) or Petabytes (PB) required to be stored upon initial system deployment/acceptance?

b) Active Data Ingestion (Standard Tier): What is the projected average monthly storage consumption for active, day-to-day case files (measured in GB/TB per month)?

c) Long-Term Storage & Archiving (Archive Tier): What is the estimated volume of data transition from active to closed/historical archive? Please specify the expected archive frequency (e.g., monthly, quarterly, or annually).

d) Scalability & Growth Projections: What is the estimated compound annual growth rate (CAGR) of your multimedia data? How does the government anticipate scaling storage over the anticipated 3year lifecycle of the contract?

e) Session Metrics: Can the government provide an estimate for the average length of a recording session and the average number of concurrent or daily sessions expected to be recorded?

The required storage workflow and capacity specifications will be provided to the selected contractor upon contract award. The USG does not require capacity in excess of what is provided via Attachment A. Storage administration and management shall be determined by the corresponding beneficiary state. If storage is needed in excess of what is specified on Attachment A, is the responsibility of the end user to procure additional solutions. See the revised Attachment A #14 which specifies a minimum storage per state of 30 terabytes for the Google Cloud Platform license.

46 Attachment A pg. 3

Operations, Data Transfer, and Cloud Usage Patterns.

The solicitation indicates that the video recording system will leverage Google Cloud infrastructure. To ensure vendors can architect a cost-effective solution and minimize operational expenses (Opex), please clarify the following workload and usage metrics:

a)Network Data Transfer (Egress) : What is the estimated volume of data (in GB/TB) projected for outbound transfer (egress) from Google Cloud per month? Please specify if this traffic remains within Google Cloud or terminates at an external destination (e.g., agency on-premise networks or public internet).

b)Archive Retrieval Pa erns (Cold Storage Lifecycle): What is the estimated retrieval frequency for archived data? Specifically, how many terabytes (TB) of data or historical cases does the government anticipate restoring from the Archive Storage class to active access on a monthly or annual basis?

c )Google Cloud Storage Class A Opera ons: What is the estimated volume of Class A operations per month? This includes data insertion, creation, and modification actions such as uploading multimedia files or listing bucket contents.

d)Google Cloud Storage Class B Opera ons : What is the estimated volume of Class B operations per month? This includes data retrieval actions such as downloading or reading video files.

The hearing cycle information is variable and depends on the case type, court, and state. Detailed operational specifications and available historical information/outlooks will be provided to the selected contractor upon contract award and during workshops specified in the SOW.

47 Attachment A pg. 3

Cryptographic Key Management and Data Security Boundaries.

The solicitation references data encryption using Google Cloud Key Management Service (Cloud KMS). To ensure compliance with federal security standards (e.g., FIPS 140-3, FedRAMP High, and CJIS) and to establish precise technical boundaries, please clarify the key management model:

a) Encryption Responsibility Model: Will the government utilize Google-owned and Google-managed encryption keys (default encryption), or does the government require a Customer-Managed Encryption Key (CMEK) architecture?

b) Key Ownership & Governance: If CMEK is required, will the government project team provision and maintain full administrative ownership of the keys within their own Google Cloud organization, or will the contractor be required to provision, rotate, and manage the CMEK environment within the solution boundary?

c) External Key Management (EKM): Does the government have a requirement for Customer-Supplied Encryption Keys (CSEK) or the integration of an External Key Manager (EKM) located outside of the Google Cloud infrastructure?

d) Hardware Security Module (HSM) Tiering: If CMEK is utilized, does the government require a specific FIPS validation tier, such as Cloud KMS HSM (FIPS 140-3 Level 3 validated), or is standard software-isolated key storage acceptable?

The cryptographic key management model, including encryption responsibility, key ownership and governance, external key management, and HSM tiering requirements, will be defined in coordination with the technical team of each beneficiary state. For additional cloud security specifications and data security boundary requirements, please refer to Attachment 5 and Attachment 6.

48 Attachment A pg. 3

a) Cloud Storage Redundancy Topology: Does the government require a Multi-region configuration (providing geographical dispersion across large geographic areas greater than 160 km apart) or a Dual-region configuration (two specific, pair-selected regions optimized for low-latency replication or to comply with localized data residency mandates)?

Please specify the exact Google Cloud region pairs preferred (e.g., us-central1 and us-east1).

b) Data Residency and Sovereignty Mandates: Are there specific data sovereignty, compliance, or regulatory boundaries that restrict data replication or storage strictly to certain geographic borders or specific federal cloud regions (e.g., FedRAMP High / GovCloud equivalents)?

c) Place of Performance Breakdown: Can the government define the exact Place of Performance for contract execution across the base period and option period?

d) Cost-of-Living / Service Location per State: Can the Government provide the number of telepresence endpoints, courtrooms, or facilities to be equipped in each participating state? Additionally, please identify the approximate deployment locations and whether installations will occur at courts, prisons, or other judicial facilities. This information is necessary to develop an accurate technical approach, staffing plan, travel estimate, and Firm-Fixed-Price proposal.

a) Cloud Storage Redundancy Topology: Offerors shall adhere to the specifications defined in the solicitation documents. It is not required that the two states for the base year have a connected configuration of their cloud storage. However, the system should be unified within all sites for each state.

b) Data Residency and Sovereignty Mandates: All data shall be stored within Mexican national territory and shall remain under the ownership of the Judicial Branch (Poder Judicial) of each corresponding beneficiary state.

c) Place of Performance Breakdown: States for implementation will be identified at award and at the time of option exercise. The exact places of performance within each state will be determined through the post-award workshop sessions conducted with the designated Government of Mexico counterparts at each project location but will not exceed one judiciary facility and five penitentiary centers per state.

d) Cost-of-Living / Service Location per State: The number of telepresence endpoints, courtrooms, and facilities to be equipped per state will be determined through the post-award workshop sessions conducted with the designated Government of Mexico counterparts at each project location. Only one judiciary site (e.g. Courtroom) will be required per state, but the equipment specified on Attachment A may be installed at more than correctional facility, but not more than 5 penitentiary centers.

49 Attachment A pg. 3 Retention Policies (Bucket Lock / WORM) and Versioning

a) How long, by law or internal policy, must a file in the Archive class remain locked so that no one (not even an administrator) can delete it?

b) Regarding "Object versioning": How many previous versions of the same file do you wish to keep stored, and for how long before they are automatically deleted?

a) Files in the Archive class shall remain locked for a minimum period of three (3) years, in accordance with the specifications defined in the solicitation documents.

b) The number of retained file versions and their corresponding retention periods will be determined through the post-award workshop sessions conducted with the Judicial Branch (Poder Judicial) of each corresponding beneficiary state.

50 Attachment A pg. 8

SICAS API for existing judicial management system.

The solicitation requires integration with the existing SICAS judicial management system through web services APIs to support functions such as Google Meet scheduling and recording, controlled recordings, secure storage, document generation, and statistics/indicators services.

a) Can the Government provide additional information regarding the SICAS integration architecture, including available API/interface documentation, supported integration protocols, and the specific data elements and business processes that must be exchanged between SICAS and the proposed solution?

b) Additionally, will the contractor be provided access to any technical documentation or support necessary to develop, test, and validate the required interfaces?

c) Can the Government identify the owner/administrator of the SICAS system and clarify whether the contractor will be permitted to coordinate with the SICAS technical team or third-party vendor responsible for the system during design, integration, testing, and deployment?

Full API and interface documentation, including supported integration protocols and the specific data elements and business processes required for the integration between SICAS and the proposed solution, will be provided to the selected contractor upon contract award.

51 F-2 Place of Performance pg. 13

The RFP states that “Performance not occurring in the Contractor's facilities will occur in Government of Mexico courtroom and prison facilities in Mexican northern border states (i.e. Baja California Norte, Sonora, Chihuahua, Coahuila, Nuevo Leon, or Tamaulipas). Two actual states for the base year will be specified at the time of award. Two additional states for the option year will be specified if/when the option is exercised.” In order to establish an equal evaluation of proposed price from each offeror, can the Government stipulate one site only for proposal purposes, for each of the Base Year (BY) and Options, in order to ensure each offeror estimates travel costs for the same location?

Pricing must be valid in any of the border states as described in the SOW, so price evaluation will be equal in that respect.

L.1 – Quotation Preparation Instructions, Section (d) Quotation volumes and page limitation pg. 56

ii) volume II, Technical Quote A indicates 5 pages includes resumes limited to no more than 1 page each. However (2) states that Volume cover sheets, table of contents, glossary of abbreviations and acronyms, and resumes do not count towards the 5 page limitation. Could the Government please clarify if resumes are included in or excluded from the 5-page limit for Volume II?

Resumes are excluded from the 5 page limitation, but are limited to no more than 1 page each. Section L.1 has been updated for clarity.

19AQMM26Q0271 SF 1449

L-3.1 Factor 1 Relevance L-3.2 Factor 2 Past Performance pg. 59

Sections L-3.1 and L-3.2 provide conflicting limits on past performance references. Please clarify the maximum number of references permitted in total, and specify if the 5-reference limit in Factor 2 overrides the 6+ reference allowance in Factor 1.

The limitation in Factor 1 is for the offeror and each proposed subcontractor or partner. For Factor 2, if the offeror provides more than 5 examples to align with the number of relevant contracts cited for Factor 1, that is acceptable.

19AQMM26Q0271 SF 1449 L-3.2 Factor 2 Past Performance pg. 60

Will the Government accept Contractor Performance Assessment Reporting System (CPARS) reports in lieu of Past Performance Questionnaires (PPQs)? Yes, but only for projects included in the Relevant Corporate Experience that you quoted.

55 Attachment 1 pg. 3 We request information related to which states will be covered, the number of courts, prisons and their locations in order to calculate the necessary logistics. Is it possible to have this information before presenting the technical and economic proposal?

The place of performance covers the northern border states. The requirement is for one judiciary facility per state, plus one to five penitentiary centers per state. Specific site locations and details will be defined following the post-award workshop sessions, as specified in the Statement of Work (SOW).

56 Attachment 1 pg. 3 and 4

Statement: The Contractor shall develop and deliver a functional interface between the telepresence/videoconference solution and all GOM designated judicial information systems identified during workshop sessions.The interface shall demonstrate, at a minimum: successful authentication and data exchange between systems; accurate transmission of hearing scheduling data; and reliable delivery of recorded video files to GOM designated repositories.

Question: We request that you share with us the processes of the judicial process of each state involved in order to identify the effort of the interfaces that will be required for the configuration of the services and, if applicable, the system to be developed

The required API documentation and technical specifications will be provided to the selected contractor upon contract award.

57 Attachment 1 pg. 4

Statement:

4.6.The Contractor shall develop and deliver a functional integration between the videoconference platform and the SICAS (Sistema Integral de Consulta de Audiencias) system, used by Mexican judiciaries to manage court hearing schedules, demonstrating, at a minimum: automated hearing scheduling initiated from within SICAS; initiation of multiple multi-participant video recording sessions; and delivery of the recorded video file to the GOM-designated cloud repository upon conclusion of the hearings. Full AI-generated transcription linkage and analytics features shall be delivered in a subsequent remediation cycle following GOM/INL approval of the functional prototype.

Question: Since the Contractor will have to develop and deliver a functional integration between the videoconferencing platform and the SICAS system (Comprehensive Hearing Consultation System), used by the Mexican judiciary to manage hearing schedules, we require the technical interface specifications of the system currently used by the judiciary of each State involved. Is it possible to have this information prior to the delivery of the technical and economic proposal? In order to estimate the development of automated hearing scheduling initiated by SICAS

The required API documentation and technical specifications will be provided to the selected contractor upon contract award.

58 Attachment 1 pg. 4

Statement: The Contractor shall develop and deliver a functional interface between the telepresence/videoconference solution and all GOM designated judicial information systems identified during workshop sessions. The interface shall demonstrate, at a minimum: successful authentication and data exchange between systems; accurate transmission of hearing scheduling data; and reliable delivery of recorded video files to GOM designated repositories.

Question: It is mentioned that the contractor must develop an interface between the telepresence/videoconferencing system based on the information obtained as a result of work sessions. Can you share this information with us, to have more information to estimate the cost, time and complexity of the interface?

The required API documentation and technical specifications will be provided to the selected contractor upon contract award.

59 Attachment 1 pg. 5

Statement: 5.1.1 A technological tool that provides telepresence capabilities for oral hearings, including booths for experts with mobile equipment; this will improve efficiency and speed for judiciary officials, citizens and third parties that participate in the hearings.

Question: What does the requirement to provide expert booths with mobile equipment refer to? What are the technical specifications and how many booths should be considered per site? Also, how many sites should be considered by each state? Can you provide us with the physical locations of such sites by state?

Expert booths with mobile equipment refer to dedicated telepresence stations designed to enable remote participation of expert witnesses during oral hearings. Technical specifications for these booths are detailed in Attachment A, which shall serve as the basis for offerors to develop their technical and price quotes. The number of booths per site, total sites per state, and specific physical locations will be defined following the post-award workshop sessions, as specified in the Statement of Work (SOW).

60 Attachment A pg. 2

Reference:

Land2Cloud Link Bandwidth: 150 MB Service term: 3 years

Question:

Will the GOM provide internet, LAN, switches, cabling, racks, regulated power, UPS, HVAC and building permits, or should everything be included by the contractor?

The contracted services shall include internet connectivity and all components necessary for integration with the local network of the Judicial Branch (Poder Judicial) at each site.

61 Attachment 6 7 Question: What kind of evidence must be available to attend an audit and formally comply with the agreement?

Attachment 6 is an attestation form and Attachment 7 requests information from the offerors. Attachment 6 mentions audits, but should be completed by the software producer.

Attachment A

Reference:

Google Cloud Platform License

BRAND NAME ONLY

Storage classes: Standard (active data), Archive (closed cases) Features: Geographic redundancy, object versioning, Cloud KMS encryption, Bucket Lock policies (WORM compliance) Storage: Minimum (to be determined)

Service term: 3 years

Question:

We ask you to provide us with the calculation made of the storage space so that we can include it in the corresponding quote.

If you do not have the required number of terabytes, we request your support to answer the following questionnaire:

WORM Storage and Network Infrastructure Sizing Questionnaire Instructions: Please answer the following questions as accurately as possible. If you do not have an exact figure, please provide an estimate based on the current or projected operation.

Section 1: Volume and Data Generation This block is critical for calculating the total storage volume and growth rate (Intake Rate).

1.1 What is the estimated number of oral hearings that will be held per week in the state?

1.2 What is the estimated average duration of an oral hearing (in hours/minutes) per day and per month?

1.3 What is the standard projected video resolution and quality for recordings (e.g. 720p, 1080p)?

1.4 Do you have an estimate of the average file size for one hour of recording at the selected quality (e.g. 1 GB/hour)?

1.5 What is the total volume of historical recordings (previous oral hearings) that must be migrated to the new cloud solution (in TB or GB)?

Section 2: WORM Retention Parameters and Data Lifecycle This block defines immutable lock policies and the use of storage hierarchies.

2.1 According to the legislation in force in Baja California, what is the minimum legal period of forced retention of a hearing recording (e.g. 3, 5, 10, 50 years)?

2.2 Are there different types of crimes or cases that require different WORM retention periods? If so, please specify them.

2.3 For how long, after the hearing has been recorded, is the video considered to be in the "active phase" (with frequent consultations for the drafting of minutes, judgments or appeals)?

•Example: 30 days, 6 months, 1 year.

2.4 After the "active phase" period, how long must the video remain in the Archive storage class (under WORM lock) before it can be legally deleted?

Section 3: Access Patterns and Download Volume This block sizes the bandwidth needed for downloads and network operations costs (Class B).

3.1 How many people, on average, are estimated to view (play or download) a hearing video that is already stored?

3.2 Of these queries, what percentage occur during the first month of the file's life (active phase)?

3.3 What is the estimated total volume of video download per month being screened (in TB or GB)?

•Note: This refers to the amount of data that moves "out" of Google Cloud to the headquarters of the Judiciary or the Internet.

3 4 What is the estimated number of concurrent users (e g judges clerks) who might be playing or downloading videos simultaneously from the main venues (Tijuana Mexicali

Storage capacity specifications and hearing cycle information are variable and depend on the case type, court, and state, as well as the telepresence service selected by the contractor. Recording resolution and per-file storage estimates will likewise be determined by the telepresence solution proposed. The required storage workflow, capacity specifications, and historical data migration requirements will be provided to the selected contractor upon contract award; storage administration and management shall be defined by the corresponding beneficiary state during the post-award workshop sessions. Offerors shall adhere to the specifications defined in the solicitation documents. Also, see the amended Attachment A #14 which includes a minimum storage capacity.

Attachment 1 pg. 3

Reference:

4. RELATIONSHIPS

The Contractor shall be responsible for project assessment, design, development, implementation, testing, delivery, knowledge transfer, and support/warranties. The INL Criminal Prosecutions Team will connect the contractor with the relevant points of contact in the Government of Mexico and provide guidance regarding implementing contract requirements and coordination on contractual matters such as inspection, and delivery. The Government of Mexico (GOM) assigned to the project shall be responsible for making any necessary updates to their facilities as needed for the contractor to execute the contract, and grant access to their facilities following any required screenings.

Once we reviewed the document, we identified the functionalities that the software must comply with as a SICAS module, in order to orchestrate Google's infrastructure and meet the objectives of the project. These features are not native to Google's collaboration suite, but they are indispensable for the legal operation of the system. We ask for your confirmation regarding the following required functionalities:

1.Automa on of Judicial Agendas This functionality must allow the scheduling of hearings from a judicial or administrative workflow. The system will take the availability of judges and virtual rooms, schedule the hearing in Google Meet and automatically generate email notifications and panel notifications to all parties involved: judges, secretaries of agreements, public or private defenders, and coordinate with prison authorities to ensure the availability of the Person Deprived of Liberty (PPL) in the corresponding telepresence room.

2.Digital Chain of Custody Management of Recordings Although Google Meet records the video, specialized software must "take ownership" of that file in an automated way at the end of the session. This involves downloading the recording, recording the exact time and participants, and automatically indexing the video into the corresponding digital record within a Google Cloud Storage structure. This feature ensures that the video is not modified and that it complies with legal standards of digital evidence.

3.Digital Evidence Entry and Control Module for Hearings The software must provide a standardized portal for the Prosecutor's Office, defense attorneys, and authorized third parties to upload files of evidence (documents, images, audios, other videos) prior to the hearing. The software must classify them and make them available to the virtual courtroom. During the Google Meet session, you must allow the Judge or Clerk to "project" or share these documents in a controlled manner, ensuring that all participants view the same file from the research folder in real time.

4.Automa on of Court Transcrip ons using Genera ve AI.

This functionality must be integrated with Google Cloud AI services (such as Gemini Enterprise) to automatically process audio from Google Meet recordings. Specialized software must: 1) identify and separate the voices of the various participants (diarization), 2) generate a complete verbatim transcript of the hearing, and 3) create an automated executive summary of the key points discussed so that they can be reviewed and authorized. This transcript and summary should be automatically attached to the file for ease of reference and drafting of judgments, along with notes from the settlement clerk and the judge.

5.Automa on and Reten on Blocking WORM (Write Once, Read Many) This functionality must apply the WORM retention policies stipulated in the PDF and that must be established prior to the start of the project, in accordance with the law of each state of the GOM. Once a hearing has been digitally recorded, transcribed, and sealed, specialized software must instruct Google Cloud Storage to apply a "Bucket Lock" to the file or folder that contains it. This blocking must configure, in an automated way, that the file is impossible to modify or eliminate for a predefined legal period (e.g. 5, 10 or 50 years), guaranteeing the immutable integrity of the historical archives of the Judicial Branch.

Software management and development are the contractor's responsibility to achieve the desired outcome for each state. System customizations and configurations shall be determined in coordination with each corresponding beneficiary state during the post-award workshop sessions. Storage retention is set at a minimum of three (3) years, consistent with the contract's period of performance and support duration.