Addendum-III-Questions&Answers-GO-SEMIConnectivityPortal-RFP.pdf

ADDENDUM III

Questions & Answers

Request for Proposals GO-SEMI Connectivity Portal: Strategic Advisory and Owners’ Representative Services

Release Date: July 21, 2026

The following is a list of responses to questions submitted by prospective respondents to the GO-SEMI Connectivity Portal: Strategic Advisory and Owners’ Representative Services, RFP. A copy of the RFP is available at: https://esd.ny.gov/doing-business-ny/requests-proposals/go-semi-connectivity-portal-strategic-advisory-and-owners

No. Question Answer

Where is ESD’s existing baseline analysis data available? (Page 2, Section II. Overview)

The baseline analysis data is not publicly posted prior to proposal submission. The completed research and foundational data will be provided directly to the selected Consultant upon contract award and project kickoff to ingest and leverage for execution.

Is there an estimated timeline for work completion, even if the Contract Start Date is still TBD? (Page 2, Section V.

Schedule of Dates)

ESD has not defined fixed completion dates for the milestones, as exact schedules will be finalized during contract negotiations. Respondents should propose a realistic work plan and project schedule in their

Technical Proposal that logically distributes effort across the three sequential milestones outlined in the

Scope of Work.

Is there an estimated budget for this contract?

ESD has not published an estimated budget or spending cap for this engagement. Respondents are expected to propose a competitive cost schedule based on their proposed methodology, staffing allocation, and blended hourly rates.

https://esd.ny.gov/doing-business-ny/requests-proposals/go-semi-connectivity-portal-strategic-advisory-and-owners https://esd.ny.gov/doing-business-ny/requests-proposals/go-semi-connectivity-portal-strategic-advisory-and-owners

What specific deliverables will be made available from the previously completed baseline analysis referenced in the RFP?

1. Research reports

2. Stakeholder interviews

3. Process maps

4. User journeys

5. Technical assessments

6. Data inventories

7. Other documents/materials

The baseline analysis includes foundational research and data mapping the operational constraints, capacity gaps (e.g., bonding, working capital, operational infrastructure), and procurement barriers faced by local SBEs, MWBEs, SDVOBs, DBEs, and SEDIs. All relevant findings, data points, and reports will be made available to the selected Consultant upon project commencement.

Has ESD already identified a target operating model or conceptual vision that should be considered as a starting point?

ESD’s foundational vision is a hybrid support model combining targeted, in-person operational leadership with a centralized digital infrastructure.

The selected Consultant will build upon this concept to evaluate alternatives and explicitly define the specific target operating model, governance framework, and technology strategy.

Is ESD currently invested in specific enterprise platforms such as Microsoft Power Platform, Salesforce, ServiceNow, AWS, Azure, or Google Cloud that should be evaluated as preferred solution candidates?

ESD expects the selected Consultant to independently evaluate technology alternatives, platform capabilities, and architectural options during

Milestones 1 and 2. While ESD maintains standard IT environments and security policies (outlined in

Appendix A), the Consultant is expected to recommend a platform based on functional fit, scalability, security, and cost-effectiveness without bias toward a pre-selected vendor.

Does ESD expect the future portal to integrate with existing state or ESD systems? If so, can ESD identify the systems currently known?

Yes, evaluating integration requirements with existing ESD and New York State systems (such as

MWBE certification databases, the NYS Contract

System, and identity/data repositories) is a core component of the Scope of Work. Specific system inventories and access will be provided to the selected Consultant during Milestone 1 discovery.

Are there existing CRM, case management, identity management, document management, or analytics platforms currently in use by ESD that should be evaluated for reuse?

The Consultant will review ESD’s current software landscape and enterprise tools during Milestone 1 to identify opportunities for system reuse, integration, or alignment with the target portal architecture.

Does ESD currently maintain datasets related to MWBE, SDVOB, DBE, SEDI, or SBE participants that may serve as the foundation for the future solution?

Yes, ESD maintains participant datasets, including certified MWBE directories and related economic development records, which will be made available to the awarded Consultant to inform data architecture and strategy.

Has ESD identified specific program KPIs, success measures, or reporting requirements for the future portal?

ESD’s overarching objective is to eliminate systemic barriers and transform emerging small businesses into prime-ready subcontractors. Defining specific, measurable program KPIs, reporting metrics, and evaluation frameworks is an explicit deliverable for the Consultant under Milestone 2.

Will development of a target data model and reporting framework be considered in scope?

Yes, developing the target data strategy, data models, and reporting frameworks to measure program performance and portal adoption is fully within the Scope of Work.

Does ESD anticipate a single implementation vendor for software design, development, deployment, and support, or separate procurements for these functions?

The selected Consultant will advise ESD on the overall procurement strategy as part of Milestone

2, recommending whether a single turnkey implementation partner or separate procurements best fit the implementation roadmap.

Does ESD have a target implementation budget range that should inform platform evaluations and roadmap recommendations?

Target implementation budget parameters will be established in collaboration with ESD leadership during the strategy and roadmap phase (Milestone 2) to ensure vendor RFP specifications and platform choices are financially viable.

Are there anticipated cybersecurity, privacy, or compliance frameworks that must be addressed in the proposed solution?

Yes, all technical architecture recommendations must comply with ESD’s IT Security Standard Brief (Appendix A), NYS Office of Information Technology Services (ITS) policies, and applicable state/federal data privacy laws.

Can ESD share the primary stakeholder groups that will participate in discovery and requirements gathering?

Primary stakeholder groups include ESD program leadership, regional/in-person center leadership, Small Business Enterprises (MWBEs, SDVOBs, DBEs, SEDIs), prime contractors, trade associations, and technical assistance providers.

Approximately how many stakeholder interviews, workshops, or focus groups does ESD anticipate during the engagement?

ESD has not set a fixed number of stakeholder engagements. Respondents should propose a structured stakeholder engagement strategy and estimate a sufficient number of interviews, workshops, and focus groups in their Technical Proposal methodology to satisfy Milestone 1 objectives.

Will ESD facilitate stakeholder access and scheduling?

ESD will assist the selected Consultant in identifying and connecting with internal state leadership and key ecosystem partners. The Consultant will be responsible for preparing meeting agendas, facilitating the sessions, and managing logistics.

What is ESD's current estimate of the number of participating businesses that may use the platform during years 1, 3, and 5?

Specific user projection targets for years 1, 3, and 5 will be defined as a deliverable during the strategy and roadmap development phase in Milestone 2. The platform is intended to scale across New York State to support all emerging SBEs, MWBEs, SDVOBs, DBEs, and SEDIs.

RFP Section II. Overview Page No. 2.00

ESD states that an initial baseline analysis has been completed and that the selected Consultant must ingest and leverage the existing data. Please confirm which baseline materials will be provided and when the selected Consultant will receive them.

Please refer to the responses for Question 1 and Question 4.

RFP Section II. Overview

Please provide any available estimates for the anticipated number and types of portal users at launch and at full scale, including ESD users, in-person center staff, small businesses, prime contractors, and other external users.

User personas and target capacity metrics—including ESD administrators, physical center leadership, small business participants, and prime contractors—will be determined as part of the operational and technical requirement analysis in Milestones 1 and 2.

RFP Section II. Overview & RFP Section IV. Scope of Work Pages 2; 3-4

Please clarify the required level of detail for the technology strategy, technical architecture, operating model, governance framework, implementation roadmap, and procurement-ready requirements.

Deliverables must be highly technical, operational blueprints and procurement-ready requirements. The work must be sufficiently detailed to produce a complete, publication-ready software development RFP, complete with logical system architecture, functional/non-functional specifications, governance frameworks, and cost models.

RFP Section II. Overview Page No. 2

Does ESD have any required or preferred technology platforms, cloud environments, hosting models, identity solutions, data standards, or enterprise architecture standards that Respondents should address in their proposals?

Please refer to the response for Question 6.

RFP Section II. Overview Page No. 2

Please identify the existing ESD systems, data repositories, data sources, and external systems that may need to be reviewed or considered for integration, and confirm the access that will be provided to the selected Consultant.

Please refer to the responses for Question 7 and Question 8.

RFP Section IV. Scope of Work

For Milestone 1, please provide any available guidance on the expected discovery activities, including stakeholder interviews, workshops, requirements sessions, document reviews, and validation sessions.

Please refer to the responses for Question 16 and Question 17.

RFP Section IV. Scope of Work Page No. 3

Approximately how many ESD stakeholder groups, portal user groups, external ecosystem participants, and leadership workshops should Respondents assume for proposal planning and pricing?

Please refer to the response for Question 17. ESD has not set a fixed number of stakeholder groups or workshops; Respondents should propose their recommended engagement structure and workshop counts within their Technical Proposal methodology.

RFP Section IV. Scope of Work Page No. 3

Should Respondents assume that stakeholder engagement and project meetings will be primarily virtual, in person within New York State, or hybrid?

Respondents should assume a hybrid approach, leveraging virtual meetings for routine working sessions and in-person meetings within New York State for major leadership workshops, strategy alignment sessions, or key stakeholder engagements.

RFP Section IV. Scope of Work Page No. 3

If in-person work is expected, please provide the anticipated number and locations of in-person meetings, workshops, or site visits.

ESD has not mandated a specific number or location for in-person meetings. Respondents should outline their proposed travel plan and location assumptions within their Technical Proposal, ensuring all out-of-pocket travel expenses remain within the 10% reimbursable fee cap specified in Section VI.D.

RFP Section IV. Scope of Work Page No. 3-4

Can ESD clarify whether the deliverables should include working prototypes, wireframes, or configured demonstrations of portal functions, or only recommendations, requirements, process designs, architecture, and procurement documentation?

The engagement scope covers strategic recommendations, target operating models, technical architecture, functional/non-functional requirements, and a procurement-ready RFP. Fully configured demonstrations or working software code are excluded, as development will be handled under a separate contract. However, low-fidelity wireframes or conceptual diagrams may be included to illustrate architectural recommendations.

RFP Section II. Overview; RFP Section VI.C. Project Plan / Approach Page Nos. 2; 6

Please confirm whether the procurement-ready RFP deliverable must follow a specific ESD template, procurement format, or required technology RFP structure.

The selected vendor will work with ESD to generate an RFP that complies with New York State law, ESD’s adopted procurement procedures and utilizes ESD’s template(s) as a starting point.

RFP Section II. Overview RFP Section IV. Scope of Work Page Nos. 2-4

For Milestone 3, please provide additional information regarding the anticipated duration, level of effort, and specific responsibilities associated with Procurement Advisory, including support during vendor evaluation, contract award, onboarding, and implementation oversight activities.

Under Milestone 3, the Consultant acts as an Owner's Representative and strategic advisor. Responsibilities include assisting with vendor evaluation, clarifying technical specifications, aiding in vendor onboarding, and conducting implementation oversight to verify that the chosen developer adheres to the approved architecture and design. Detailed effort levels depend on the implementation timeline and should be estimated in the proposed work plan.

RFP Section V. Schedule of Dates Page No. 4

Please confirm the anticipated contract start date, overall contract term, target project duration, and desired completion timeframe for each of the three milestones.

Please refer to the response for Question 2.

RFP Section V. Schedule of Dates Page No. 4

Can ESD provide its anticipated timeline for Respondent interviews, announcement of the successful Respondent, contract execution, notice to proceed, and project kickoff?

As indicated in Section V (Schedule of Dates), dates for interviews, selection announcement, contract execution, and project start are currently listed as To

Be Determined (TBD). ESD reserves the right to adjust procurement dates as necessary.

RFP Section V. Schedule of Dates RFP Section VI.C. Project Plan/Approach Page Nos. 4-6

What review and approval periods should Respondents assume for draft deliverables, milestone acceptance, and the procurement-ready RFP?

Specific review and approval timelines for draft deliverables, milestone acceptance, and the procurement-ready RFP are not fixed in the RFP and will be formally established upon contract award and project kickoff. For proposal planning, Respondents should outline reasonable review windows in their proposed project schedule and explicitly state their assumed turnaround times.

RFP Section VI.A. Firm Experience and Qualifications Page No. 5

Please confirm if an ongoing project be used as one of the three required project profiles if substantial relevant work and outcomes have been completed within the last five years, Yes, an ongoing engagement can be submitted as one of the three required project profiles, provided that significant, measurable deliverables and relevant scope have been completed within the past five years.

RFP Section VI.B. Staff Experience and Qualifications Page No. 5

For the required resource allocation narrative, should each person's percentage represent their share of total project effort, their percentage of available work time, or their allocation within each milestone?

In accordance with Section VI.B, Respondents must provide a breakdown indicating the estimated percentage of time each key team member will dedicate to each of the three sequential milestones.

RFP Section VI.D. Cost of Services Page No. 6

The RFP provides a Cost Schedule Summary Table but no editable pricing file. Please confirm that Respondents may recreate the table, as shown in "Cost of Services - Cost Schedule Summary Table", and identify any supporting pricing details or assumptions that must accompany it.

Yes, Respondents may recreate the Cost Schedule

Summary Table in their Technical Proposal under

Section F. Respondents should ensure all required fields—estimated man-hours, blended hourly rates, milestone costs, management fees, and reimbursables—are fully detailed along with any supporting pricing assumptions.

RFP Section VI.D Cost of Services Page No. 6

Please clarify if the milestone amounts should be proposed as fixed fees, not-to-exceed amounts billed using actual hours, or estimated costs subject to adjustment.

Proposed amounts must be submitted using the Cost

Schedule Summary Table in Section VI.D. Specific billing mechanisms and contract payment terms will be finalized during contract negotiations with the selected Respondent.

RFP Section No. VI.D Cost of Services Page No. 6

Please advise if ESD has established a budget, not-to-exceed amount, or expected cost range for this engagement?

Please refer to the response for Question 3.

RFP Section VI.D Cost of Services Page No. 6

Please confirm whether the 10% cap on out-of-pocket reimbursables is calculated against total professional fees, total proposed cost, or another amount.

The 10% cap on out-of-pocket reimbursable expenses is calculated relative to total proposed professional fees.

RFP Section VI.D Cost of Services Page No. 6

Please confirm whether estimated out-of-pocket reimbursables must be included in the Total Proposed Cost.

Yes, estimated out-of-pocket reimbursables must be included in the Cost Schedule Summary Table and factored into the final Total Proposed Cost.

RFP Section VI.D Cost of Services Page No. 6

If management fees or multipliers are not applicable, please advise if we should enter $0, N/A, or explanatory text in that row of the Cost Schedule Summary Table?

If management fees or multipliers do not apply to your proposed pricing structure, Respondents should enter "$0" or "N/A" in that row of the table.

RFP Section VI.D Cost of Services RFP Section IX General Provisions Page Nos. 6; 10-11

Should Respondents provide labor category rates or other billing rates for additional services and contract changes, and if so, where should those rates be included?

Yes, Respondents should include a rate card of labor categories and standard hourly billing rates in their

Cost of Services section (Technical Proposal Section

F). These rates will serve as the basis for any potential contract adjustments or additional services requested pursuant to Section IX.

RFP Section VI. D Cost of Services Page No. 6

Does ESD anticipate payment based on milestone acceptance, monthly actual hours, deliverable completion, or another invoicing structure?

Specific invoicing terms and payment schedules will be finalized during contract execution. Respondents may propose their preferred invoicing alignment (e.g., milestone acceptance or monthly billing) as part of their proposal submission.

RFP Section VI. Selection Criteria RFP Section VII.i Technical Proposal Page Nos. 6-7

The RFP identifies the Diversity Practices Questionnaire as Appendix B, while the questionnaire itself is labeled Appendix E. Can you kindly confirm the naming for the document?

The Diversity Practices Questionnaire was inadvertently labeled “Appendix E”. The

Questionnaire is properly considered as Appendix B to the RFP. The designation “Appendix E” found in the upper right-hand corner of the document should be disregarded.

RFP Section VII.i Technical Proposal Page No. 7

May resumes, the organizational chart, project references, and other supporting materials be included as appendices to the Technical Proposal, and will those appendices be evaluated?

Resumes, organizational charts, and project profiles are explicit evaluation components under Section VI.A and VI.B. They should be integrated directly into the

Technical Proposal narrative or attached as clearly bookmarked sections/appendices within the

Technical Proposal folder.

RFP Section VII.i Technical Proposal Page No. 7

Please confirm whether a page limit applies to the Technical Proposal and, if so, which items are excluded from the page count.

There is no page limit for the Technical Proposal.

Pursuant to Section VII ("Submission of Proposals"), ESD requests that Respondents submit proposals that clearly and concisely provide all requested information. Emphasis should be placed on completeness, clarity, and full alignment with the evaluation criteria and submission requirements detailed in Sections VI and VII.

RFP Section VII.i Technical Proposal Page No. 7

Please advise if the Technical Proposal should be submitted as one bookmarked file containing Sections A through G, or may the required sections be submitted as separate clearly labeled files.

The Technical Proposal should be submitted as one bookmarked file containing Sections A through G.

RFP Section VII.ii Administrative Proposal RFP Section X.iii Contractual Requirements Page Nos. 8; 13-14

Please confirm whether any Administrative Proposal form listed in Section VII(ii) must be completed and signed separately by a proposed subcontractor.

Subcontractors are not required to complete the forms listed in Section VII(ii) except that each

Respondent and subcontractor identified in the proposal must complete an EEO Staffing Plan (Form

OCSD-2) and submit it as part of the Proposal. More information is found on the “Instructions” sheet of the Excel file.

RFP Section VII.ii Administrative Proposal Page No. 8

Are electronic signatures acceptable for all proposal forms and certifications that require a signature?

Yes.

RFP Section VII.ii Administrative Proposal RFP Section VIII Questions Page Nos. 8-9

Please advise if ESD will issue an addendum acknowledgment form, or should Respondents include their own acknowledgment of all issued addenda in the Administrative Proposal.

ESD will not issue an addendum acknowledgement form. Respondents are not required to include one.

By submitting a proposal, Respondents are indicating their acceptance of the conditions in the RFP, as well as all addenda to the RFP.

RFP Section VII.ii Administrative Proposal Page No. 8

Please advise if the Administrative Proposal should be submitted as one combined file in the listed order or as separate clearly labeled files for each required form. If separate files, please advise on the naming convention.

Respondent may submit the Administrative Proposal using either method. Should separate files be submitted, ESD prefers that each form is clearly indicated in the file name.

RFP Section VII.iii Submission of a Complete Two-Part Proposal Page No. 9

Please confirm the required electronic file formats. Should the Technical and Administrative Proposal documents be submitted as searchable PDFs, native Word or Excel files, or both?

There is no required electronic format for either the

Technical Proposal or the Administrative Proposal;

however, for ease of review, the Technical Proposal should be searchable, to the extent that is possible.

RFP Section VII.iii Submission of a Complete Two-Part Proposal Page No. 9

Please confirm whether the main proposal folder must be uploaded as an unzipped folder or whether a ZIP file containing the required folder structure is acceptable.

The main proposal folder should be an unzipped folder.

RFP Section VII.iii Submission of a Complete Two-Part Proposal Page No. 9

Please advise if there are any file size limits for the main folder or individual proposal files.

There are no specific file size limits; however, any

Respondent intending to upload a main folder with a file size exceeding 1 GB must provide notice to the designated email box (GO-

SEMIConnectivityPortal@esd.ny.gov) in advance of the submission deadline.

RFP Section VII.iii Submission of a Complete Two-Part Proposal Page No. 9

Please advise if any specific naming convention is to be followed for the Technical Proposal document.

There is no specific naming convention for the

Technical Proposal except that the file name should clearly identify the document.

mailto:GO-SEMIConnectivityPortal@esd.ny.gov mailto:GO-SEMIConnectivityPortal@esd.ny.gov

RFP Section IX General Provisions Page 9-10

Please advise if ESD requires confidential or proprietary information to be marked in a specific manner in the proposal.

Vendors wishing to request that ESD maintain certain information as confidential or proprietary may do so by clearly marking such information as “Confidential” or “Proprietary” within their submission. Vendors are advised that ESD is required to comply with lawful court orders and the New York State Freedom of

Information Law (FOIL) and is therefore required to make disclosures pursuant to the same regardless of whether a vendor marks information as confidential.

In the event of a FOIL request, ESD will conduct a trade secret review, inclusive of input from the vendor, to determine whether a statutory exemption to FOIL applies to protect the information from disclosure.

RFP Section IX General Provisions

If subcontractors or partners are proposed, what information must be included in the Technical Proposal in addition to the OCSD utilization forms, and must every subcontractor be identified at proposal submission?

Subcontractors should be identified at proposal submission to the fullest extent possible. The

Technical Proposal must include their firm background, key personnel resumes, organizational chart positioning, role description, and milestone time allocations. Additionally, sub-consultants must be listed on applicable administrative and diversity compliance forms.

RFP Section X.ix Diversity Requirements Page No. 16

The RFP establishes an overall 30% MWBE participation goal but does not state separate MBE and WBE subgoals.

Please confirm whether the goal may be met through any combination of New York State-certified MBE and WBE participation totaling 30%.

The overall MWBE goals may be achieved through combined MBE and WBE participation.

RFP Section Appendix A – ESD Information Security Brief Page No. 1 of Appendix A

Please confirm whether Respondents must include an Appendix A compliance narrative in the Technical Proposal and identify any security deliverables that should be included in the proposed scope and price.

Respondents should address their technical security approach and compliance with Appendix A within

Section E (Project Plan and Approach) of the Technical

Proposal. Specific security architecture and compliance requirements should be factored into the proposed methodology and pricing for Milestones 1 and 2.

RFP Section Appendix A – ESD Information Security Brief Page No. 1 of Appendix A

Is formal certification to ISO 27001, ISO 27005, and ISO 27035 required, or may Respondents demonstrate compliance through equivalent policies, procedures, and controls approved by ESD's Chief Information Security Officer?

Formal ISO certification is not strictly required as a prerequisite to submit a proposal. However, Respondents must demonstrate compliance with

ESD's IT Security Standard Brief (Appendix A) through equivalent organizational security policies, technical controls, and operational standards.

RFP Section Appendix A – ESD Information Security Brief Page No. 1 of Appendix A

Appendix A states that ESD's IT Deliverables Standard will be provided upon request. Can ESD kindly provide the current standard before proposals are due, if available.

The IT Security Standard Brief is provided in Appendix

A to govern proposal submissions. Full technical deliverable standards will be provided to the selected

Consultant at contract start to inform the development of implementation RFP specifications.

RFP Section Appendix A – ESD Information Security Brief Page No. 1 of Appendix A

Please advise if there are any policies governing the use of artificial intelligence available before proposal submission?

ESD does not have a standalone AI policy document attached to this RFP. Any proposed use of automated tools or AI methods during project execution must strictly comply with ESD's IT Security Standard Brief

(Appendix A), state confidentiality standards, and data protection guidelines.

RFP Section Appendix A – ESD Information Security Brief Page No. 1 of Appendix A

Please clarify if respondents should disclose any proposed use of artificial intelligence-enabled tools or methods in the Technical Proposal?

Yes. If a Respondent plans to utilize AI-enabled tools or automated analysis methods in delivering the

Scope of Work, this approach—along with risk mitigation and data security controls—should be disclosed within the Project Plan and Approach section.

RFP Section Appendix B – Question 8 Page No. 3 of Appendix B

Question 8 directs Respondents planning to use New York State-certified MWBEs to complete the attached Utilization Plan. Please confirm that Form 'OCSD-4' is the applicable Utilization Plan that is referenced here.

Yes. The Utilization Plan can be accessed here:

https://esd.ny.gov/sites/default/files/OCSD-

4%20Utilization%20Plan.pdf https://esd.ny.gov/sites/default/files/OCSD-4%20Utilization%20Plan.pdf https://esd.ny.gov/sites/default/files/OCSD-4%20Utilization%20Plan.pdf

RFP pp. 3–4, Section IV; p. 4, Section V

The RFP requires Respondents to propose a work plan and timeline. For purposes of developing a responsible schedule and price for Milestone 3, please clarify the anticipated duration or contractual endpoint that Respondents should assume—for example, through implementation-vendor selection, contract execution, vendor onboarding, a defined period of implementation oversight, portal launch, or final implementation acceptance.

Milestone 3 covers Procurement Advisory and

Owner's Representative services through implementation RFP issuance, vendor evaluation, selection, onboarding, and initial implementation oversight. Respondents should clearly state their assumed duration, staffing levels, and labor boundary assumptions for Milestone 3 within their proposed schedule and cost breakdown.

RFP p. 2, Section II; p. 5, Section VI.C

Please describe the approximate volume, format, age, and level of completeness of ESD’s existing baseline analysis, including the types of reports, datasets, interview records, surveys, or other source materials that the selected Consultant will be expected to review.

RFP pp. 2–3, Sections II and IV; p. 5, Section VI.C

Should Respondents assume that the selected Consultant will independently validate and supplement the baseline analysis through additional interviews, surveys, focus groups, data collection, or independent research? If so, please describe the anticipated extent of that work.

Yes. The selected Consultant is expected to ingest the existing baseline analysis and build upon it by conducting independent stakeholder discovery, user interviews, and validation sessions during Milestone 1 to form comprehensive future-state requirements.

RFP pp. 2–6, Sections II, IV, and VI.C

For purposes of preparing comparable schedules and prices, please provide the approximate number of stakeholder interviews, workshops, focus groups, steering committee meetings, executive presentations, and formal review sessions that ESD anticipates during the engagement.

Please refer to the responses for Question 17 and

Question 26.

RFP pp. 2–6, Sections II, IV, and VI.C

Please clarify whether stakeholder engagement and project meetings are expected to be conducted remotely, in person, or through a hybrid approach.

If in-person work is expected, please identify the anticipated locations or regions and the approximate number of trips Respondents should assume.

Please refer to the responses for Question 27 and

Question 28.

RFP pp. 1–3, Sections I, II, and IV

Please identify the anticipated categories of portal users and provide any available estimates of the number of external businesses, internal ESD users, service providers, prime contractors, partner organizations, and other users that the future portal is expected to support.

Please refer to the responses for Question 19 and

Question 21.

RFP pp. 2–3, Sections II and IV

Please identify any existing ESD or New York State systems, data sources, enterprise platforms, identity services, directories, procurement systems, or external services that the Consultant should assume will require integration analysis or coordination.

Question 24.

RFP pp. 2–3, Sections II and IV

Are there any existing enterprise licenses, cloud environments, technology standards, preferred platforms, or architectural constraints that ESD expects the future portal recommendations to use or prioritize?

Please refer to the responses for Question 6 and

Question 23.

RFP pp. 2–3, Section IV; pp. 5–6, Section VI.C

Please clarify the level of detail expected for the final technical and operational deliverables. Should Respondents assume that the engagement will produce implementation-ready functional requirements, nonfunctional requirements, process models, data and integration specifications, security and accessibility requirements, architecture diagrams, operating procedures, governance models, cost estimates, and implementation plans?

Please refer to the response for Question 22.

RFP pp. 2–3, Section IV; pp. 5–6, Section VI.C

Does ESD expect user-experience or service-design deliverables such as user personas, user journeys, service blueprints, information architecture, wireframes, or prototypes? If so, please identify the expected level of fidelity and user validation.

Please refer to the response for Question 29.

RFP pp. 5–6, Section VI.C

Please identify the required formats for final deliverables. Will ESD require editable native source files in addition to final PDF versions, and does ESD have prescribed templates, branding standards, architecture notations, requirements formats, or project-management tools that the selected Consultant must use?

The RFP does not prescribe rigid templates, branding tools, or architecture notation standards in advance.

Instead, Section VI.C ("Deliverable Framework") explicitly requires the Respondent to propose the format and structure for the final technical blueprints, operating models, and procurement-ready RFP in their Technical Proposal. As standard practice, final accepted deliverables should be provided in both searchable PDF format and editable native source files (e.g., MS Word, Excel, PowerPoint, Visio). Specific branding guidelines and project management tools will be finalized during project onboarding.

RFP pp. 10–11, Section IX – Performance

Please identify the anticipated ESD review and acceptance period for each major deliverable and the number of review and revision cycles Respondents should include in their proposed fees.

Please refer to the response for Question 34.

RFP pp. 2–3, Sections II and IV

Is the selected Consultant expected to prepare a complete, publication-ready implementation RFP—including administrative requirements, pricing schedules, evaluation criteria, contractual requirements, security requirements, service levels, and acceptance provisions—or primarily the technical scope of work and technology requirements for incorporation into an ESD-prepared procurement document?

The Consultant will draft the technical architecture, operational blueprints, functional/non-functional requirements, and evaluation criteria, working in close coordination with ESD procurement and legal leadership to form a complete, publication-ready implementation RFP.

RFP pp. 2–3, Sections II and IV

Is the selected Consultant expected to conduct formal vendor-market research, product demonstrations, requests for information, vendor interviews, or budgetary-quotation exercises before recommending a technology strategy and preparing the implementation RFP?

Under Milestones 1 and 2, the selected Consultant is expected to evaluate market technology alternatives, platform capabilities, and industry best practices to recommend an optimal, secure, and scalable technology strategy. While market evaluation and vendor research are within scope, conducting formal state-issued Requests for Information (RFIs) or budgetary-quotation exercises is not explicitly mandated unless determined necessary with ESD leadership. Under Milestone 3, the Consultant will provide strategic advisory support throughout the subsequent vendor evaluation and selection process, assisting with onboarding and serving as an Owner's

Representative to ensure alignment with the approved vision and implementation plan.

RFP pp. 2–3, Sections II and IV

If vendor-market research or outreach is expected, what communications restrictions or safeguards will apply to potential vendors that may later compete for the implementation contract?

Any market research or vendor discussions conducted during the advisory phase must comply with State

Finance Law §§ 139-j/139-k procurement lobbying restrictions and ESD ethics standards to ensure fair competition and prevent conflicts of interest.

RFP pp. 3–4, Section IV

Please clarify which activities ESD expects to be included in Milestone 3.

In particular, should Respondents include support for bidder questions and addenda, proposal evaluation, consensus scoring, interviews and demonstrations, reference checks, negotiations, vendor onboarding, implementation-plan review, design review, risk monitoring, change-request review, testing oversight, and implementation acceptance?

Milestone 3 (Procurement Advisory &

Implementation Oversight) includes strategic advisory support throughout the software development vendor procurement process (e.g., clarifying requirements, supporting vendor evaluation, participating in reviews) and serving as Owner's

Representative to oversee alignment during initial implementation activities. Detailed scope boundaries and task assumptions should be outlined in the

Respondent's proposed project plan.

RFP pp. 3–4, Section IV

For pricing purposes, approximately how many implementation proposals, evaluation meetings, vendor interviews or demonstrations, negotiation sessions, onboarding meetings, and implementation-review meetings should Respondents assume?

ESD has not set fixed limits on meeting counts or proposal volumes for Milestone 3. Respondents should state their explicit volume and staffing level assumptions within their Technical Proposal methodology and pricing structure.

RFP pp. 3–4, Section IV; p. 6, Section

VI.D

Because the duration and volume of Milestone 3 will depend on the future procurement and implementation schedule, may Respondents propose Milestone 3 as a defined not-to exceed allocation of hours and fees, supported by stated assumptions and contractual hourly rates?

Please refer to the responses for Question 38 and

Question 43.

RFP p. 6, Section VI.D

The Cost Schedule states that out-of-pocket reimbursables are capped at 10%. Please clarify whether the 10% limitation is calculated against total professional fees, the total proposed contract price, each individual milestone, or another amount.

Please refer to the response for Question 40.

RFP p. 6, Section VI.D; pp. 10–11, Section IX

Please describe the anticipated invoicing and payment structure. Will the Consultant invoice monthly based on work performed, by milestone, upon delivery, or only after written acceptance of each deliverable?

Please refer to the response for Question 44.

RFP pp. 4–5, Section VI.A

May relevant project experience completed by a proposed subcontractor or proposed key personnel be included among the three required project profiles, or must all three projects have been performed under contracts held directly by the prime Respondent? If subcontractor experience may be included, must that subcontractor be assigned a material role under the resulting contract?

Project profiles should primarily showcase the prime

Respondent’s corporate track record. However, relevant experience from key proposed subcontractors or key team members may be included to demonstrate overall team capabilities under Section VI.A and VI.B, provided the subcontractor is assigned a material role in contract performance.

RFP p. 1, Section I; pp. 11 12, Section IX

The RFP states that the winning bidder will be disqualified from competing for the subsequent software-development contract. Please clarify: (a) whether the restriction applies only to the prime Consultant or also to its subcontractors, affiliates, commonly controlled entities, and individual personnel; (b) whether it applies only to the initial software-development procurement or also to future hosting, maintenance, support, integration, enhancement, and operational procurements; and (c) how long the restriction will remain in effect.

Pursuant to Section I and Section IX (General Provisions) of the RFP, ESD clarifies the disqualification parameters as follows:

(a) Covered Entities: For the prime respondent, its affiliates, commonly controlled entities, and individual personnel, the disqualification parameters will be construed broadly, and any attempt to circumvent the restriction will result in the unilateral and summary rejection of a submission. For subcontractors, the restriction will also apply broadly if ESD determines, in its sole discretion, that the subcontractor’s role in this project creates a conflict of interest or an unfair competitive advantage.

(b) Scope of Procurements: Under Section IX, disqualification parameters are construed broadly. If a subsequent contract or operational procurement (e.g., development, integration, maintenance, or operations) arises where the consultant's advisory role creates an organizational conflict of interest or competitive advantage, the restriction applies.

(c) Duration of Restriction: The restriction remains in effect for any subsequent contract or procurement process where ESD determines that the consultant's prior involvement gives them an unfair competitive advantage or creates a conflict of interest.

Appendix A – ESD Information Security Brief, p. 1

Appendix A states that ESD’s IT Deliverables Standard will be provided to prospective vendors upon request.

Please provide the current IT Deliverables Standard applicable to this procurement.

Please refer to the response for Question 62.

Appendix A – ESD Information Security Brief, p. 1

Please clarify whether the selected Consultant may process ESD documents and data on appropriately secured contractor-controlled systems and whether prior written approval is required before using generative artificial intelligence, automated transcription, or other AI assisted analysis tools. Black Systems LLC would not transmit ESD data to an external AI service unless expressly authorized by

ESD.

Please refer to the responses for Question 63 and

Question 64.

Additionally, any processing of ESD data on contractor-controlled environments must comply strictly with ESD's IT Security Standard Brief

(Appendix A) and data protection mandates.

As a NY OGS certified Minority- and Women-owned firm, may we self-perform for the full 30% MWBE participation requirement?

To achieve credit toward the 30% MWBE goal, the vendor must be listed in the directory of New York

State-certified MWBEs, found here: Empire State

MWBE Hub.

The RFP states that the baseline analysis has been completed, how complete is the current vision versus expectation for the vendor to develop?

The completed baseline research maps specific operational constraints and procurement barriers.

The selected Consultant will translate those conceptual findings into operational blueprints, system architecture, operating models, governance frameworks, and a procurement-ready RFP.

How extensive is the existing baseline analysis that the selected vendor will be expected to review? Please refer to the responses for Question 1 and

Question 4.

Approximately how many stakeholder interviews are expected?

Please refer to the response for Question 17.

https://www.mwbe.esd.ny.gov/ https://www.mwbe.esd.ny.gov/

What level of architecture documentation is expected (high level, logical, detailed)? Please refer to the responses for Question 22 and

Question 74.

For Milestone 3, what is the anticipated duration and expected level of involvement for Procurement Advisory and Owner's Representative services following release of the implementation RFP?

Please refer to the responses for Question 31 and

Question 66.

Does ESD have a target date or date range for the completion of each milestone, 1, 2, and 3? (Schedule of dates, page 4)

Please refer to the response for Question 2.

Does ESD have a target budget or budget range for the completion of the strategic advisory and owner's representative services? (Cost of services, page 6)

Please refer to the response for Question 3.

What is the extent of the "previously commissioned… initial baseline analysis mapping the specific operational constraints and procurement barriers faced by local SBEs"? Has this research been fully published, or does ESD have further internal reports? (Overview, page 2)

Are you anticipating the need for a specific Project Manager, Lead Enterprise Architect, Business Analyst, and Procurement Advisor? Or are these examples of roles the consultant could assign? (Selection Criteria, page 5)

The labor titles mentioned in Section VI.B are examples of key personnel roles typically required for this type of engagement. Respondents may propose their own organizational structure and role titles, provided all required technical, strategic, and procurement capabilities are fully addressed.

Given that vendors have not been selected and issuing RFPs is part of the scope of work for the consultant, how does ESD recommend applicants complete the MWBE and SDVOB utilization plan with Firm details at this stage of the process? (Scope of work pages 3-4, Business Participation Opportunities for MWBEs pages 17-18, and SDVOB Utilization Plan pages 20 - 21)

Respondents must demonstrate Good Faith Efforts to provide meaningful participation of MWBE and

SDVOB subcontractors and suppliers in the performance of the contract. For assistance in identifying certified subcontractors, please visit the

Empire State MWBE Hub (https://www.mwbe.esd.ny.gov) and Service-

Disabled Veteran-Owned Business Directory (https://sdves.ogs.ny.gov/business-search).

If no MWBE or SDVOBs are selected to perform on the project, the Utilization Plan included with the proposal will not list any vendors.

Are there certain data analysis and/or project management tools that ESD anticipates using or prefers for data strategy and deliverables? (Tableau, Power BI, SharePoint, Dropbox, etc.)

ESD does not mandate specific data analysis or project management software for this advisory engagement. Respondents may propose standard tools (e.g., Power BI, Tableau, SharePoint, Visio) within their methodology to support requirements gathering, project management, and deliverable creation. Final collaboration tools and formats will be confirmed at project kickoff.

RFP Section II Overview; RFP Section IV Scope of Work

What existing reports, datasets, stakeholder findings, and frameworks will ESD share? Will the Consultant be required to validate this research through additional primary research?

Please refer to the responses for Question 1, Question 4, and Question 68.

RFP Section II Overview; RFP Section IV Scope of Work

Should the future state vision and phased implementation approach be semiconductor-focused initially and extensible to other industries, or sector agnostic from inception?

The primary goal of the Connectivity Portal is to address systemic capacity bottlenecks and expand participation for Small Business Enterprises (including

MWBEs, SDVOBs, DBEs, and SEDIs) in government and commercial contracting across New York State.

While aligned with strategic state growth initiatives, the target architecture, operating model, and implementation roadmap should be scalable and extensible across relevant business sectors.

RFP Section VI Selection Criteria

What expenses are considered "out-of-pocket reimbursables"?

Out-of-pocket reimbursables cover reasonable, direct project-related expenses such as travel within New

York State for required in-person meetings or stakeholder workshops. In accordance with Section

VI.D, all reimbursable expenses are subject to a strict

10% cap relative to total proposed fees.

RFP Section VI Selection Criteria

When does ESD expect the implementation vendor procurement to begin?

The exact timeline for issuing the subsequent software development RFP will be established during

Milestone 2 (Strategy, Roadmap & Procurement

Planning) upon ESD's approval of the recommended implementation roadmap.

RFP Section Selection Criteria

What ESD resources and subject matter experts will be available to work in partnership with the consulting team throughout the engagement?

ESD executive leadership, program managers, IT and security representatives, and key stakeholders from regional centers will collaborate with the selected

Consultant throughout discovery, strategy formulation, and procurement advisory phases.

RFP Section VI Selection Criteria

Who will serve as the primary decision-makers and approval authorities for future-state recommendations, technology strategy, governance design, and procurement deliverables?

Designated ESD Project Management, executive leadership, and representatives from ESD

Procurement and Legal will serve as the primary approval authorities for all milestone deliverables, architectural decisions, and procurement documents.

RFP Section II. Overview; RFP Section IV. Scope of Work

Will the scope of work include producing user personas, journey maps, or service blueprints for the portal's primary user groups (e.g., SBE owners, prime contractors, ESD staff, in-person center leadership)? Or are these expected to be addressed by the subsequent software development vendor?

The Consultant is responsible for conducting business and user requirements analysis, mapping operational workflows, and defining user needs to establish comprehensive functional and technical specifications for the implementation RFP. Full software-level UX/UI designs and software development will be executed by the subsequent development vendor. Refer also to

Question 22 and Question 29.

RFP Section IV. Scope of Work – Milestone 1

Under Milestone 1 (Discovery &…