33500 Van Born Road Stacey Shaw

Wayne, Michigan 48184-2497 Purchasing Consultant www.RESA.net purchasing@resa.net

Addendum #2

RFP #WRESA-50-2026-2027-07

SMART ENTERPRISE INTEGRATION AND API SERVICES

Questions and Answers

Q.1. Section 1.1, Minimum Mandatory Requirements. Quoted language: "The proposer must have a minimum of five (5) years of experience providing API Services."

Does experience delivered as a subcontractor to a prime contractor count toward the five-year minimum, provided the proposer performed the API and integration work itself?

A.1. Wayne RESA is interested in the years of experience of the people who would be working on the project, not the longevity of the company.

Q.2. Section 2.2, References, read together with Section 3.6, Adherence to Minimum Mandatory Requirements. Quoted language: "Provide a minimum of three (3) customer references for commodities and/or services of similar scope dating within the past five (5) years." and "Wayne RESA Administrator or designee shall review Section 2.2 References and determine if the Proposer meets the minimum mandatory requirements as outlined in this RFP."

Where work was performed under a prime contractor, may the reference identify the end agency for whom the work was delivered, with the prime contractor's project executive named as the contact? Relatedly, may more than one reference share a contact person where that person supervised distinct engagements at different agencies?

A.2. Wayne RESA is interested in the years of experience of the people who would be working on the project. If your company worked on a project as a subcontractor, you may list the prime contractor as the contact. More than one reference may share a contact person as long as each referenced project was/is for different clients.

Q.3. Quoted language: "commodities and/or services of similar scope" For the purpose of the pass/fail determination, does "similar scope" require API design and integration work specifically, or does it also admit broader enterprise software engineering and systems integration delivery?

A.3. Enterprise software engineering and systems integration experience may be considered similar in scope where the work included substantial API development, application integration, data exchange, or comparable integration services. References will be evaluated based on their overall similarity in size, scope, and complexity to the services required by this RFP.

Q.4. Attachment A, Pricing Schedule, "Pricing Assumptions (Required Disclosure)".

Quoted language: the required disclosures for "Environments included," "Integrations included," "Endpoints included," and "API volume assumptions."

https://wcresa-my.sharepoint.com/personal/ewertj_resa_net/Documents/RESOURCES/Board%20and%20RESA%20Docs/RFP%20Wayne%20RESA%20Templates/1-Templates-To%20be%20reviewed/www.RESA.net https://d.docs.live.net/d2b329ada6768eb0/Desktop/STACEY/WAYNE%20RESA/TEMPLATES/purchasing@resa.net

The RFP does not specify a target endpoint count, the number of non-production environments, or the expected API call volume. So that pricing is comparable across proposers rather than resting on differing assumptions, will Wayne RESA provide: (a) the approximate number of SMART entities or database tables to be exposed, (b) the number of non-production environments to be delivered, and (c) an anticipated peak and average API request volume?

A.4. Wayne RESA has not established final endpoint counts, exposed-table counts, non-production environment counts beyond those identified in the RFP, or quantitative API volume assumptions for proposal pricing. Proposers should state the assumptions used for endpoint count, integrations, environments, webhook events, and expected volumes. Final scope, priorities, and performance baselines will be confirmed during discovery and reflected in the approved implementation plan.

Q.5. Section 1.3.1, Scope of Work. Quoted language: "The contractor will design and deploy a comprehensive catalog of data access vectors mapping to the SMART .NET MVC database schema."

Will Wayne RESA make the SMART database schema, existing technical documentation, and source code access available to the awarded contractor at project start? Will current SMART development staff be available to support discovery, and does any partial API or integration layer exist today that the contractor would extend rather than build new?

A.5. Wayne RESA will make available relevant SMART database information, existing technical documentation, source code access, and appropriate non-production environment access to the awarded contractor as needed for the project. Wayne RESA SMART development staff will be available during discovery to support knowledge transfer and technical questions. There is not an API or integration layer currently in place for the contractor to extend; the selected contractor should assume the API layer will be designed and built as part of this engagement, while leveraging existing SMART architecture and business logic where appropriate.

Q.6. Section 1.3.1, Scope of Work, Phase 3. Quoted language: "Phase 3: Security Layer &

Target Integrations (December 2026)." Given a contract start of October 2026, is the December

2026 milestone a fixed date, or does it move with the actual contract execution date?

A.6. Section 1.3.1, Scope of Work, F. Implementation & Project Management, 1. – The time frames listed within each Phase will be adjusted based on the Contract award date.

Q.7. Please confirm whether a vendor may participate directly from outside the United States, or whether a U.S.-based prime/partner arrangement would be more appropriate for this solicitation?

A.7. This RFP requires the proposer to be in good standing in Michigan (see Section 2.0 –

Proposer Information and Acceptance, 5.) and requires assigned personnel to be legally authorized to work in the United States (see Section 2.3 Assurances and Certifications).

https://wcresa-my.sharepoint.com/personal/ewertj_resa_net/Documents/RESOURCES/Board%20and%20RESA%20Docs/RFP%20Wayne%20RESA%20Templates/1-Templates-To%20be%20reviewed/www.RESA.net

Q.8. Can Wayne RESA confirm the specific commercial product or platform underlying the in-house 'SMART' ERP system (vendor name, version, and whether it is COTS, customized

COTS, or fully custom-built), and identify the current system integrator or vendor of record who maintains it, if any?

A.8. Wayne RESA maintains and develops SMART. It is a fully custom-built application.

Q.9. What are the specific third-party applications, cloud services, and partner systems that the new API layer must integrate with (e.g., state SIS/education data systems, financial systems, HR/payroll platforms), and are any of those integration specifications available before the pre-proposal conference?

A.9. Initial target integrations will be confirmed during discovery. Proposers should assume the

API layer may support integrations across HR/financial systems, AWS-related services, document-storage platforms, and other business systems identified by Wayne RESA. Available specifications for third-party systems will be provided to the selected contractor where available.

Proposers should identify integration assumptions, dependencies, sandbox/API access needs, and any limitations in their proposals.

Q.10. Since SMART appears to be an education-sector ERP, will the API layer handle FERPA-protected student data or other regulated data (financial, HR/PII), and if so, what compliance frameworks (FERPA, state data privacy statutes, NIST 800-53/171) must the proposed architecture demonstrate adherence to?

A.10. Please see Section 1.3.1, E., 1., f. Regulatory Compliance.

Q.11. What authentication, authorization, and API security standards are required or preferred (e.g., OAuth 2.0, SAML, mTLS, API gateway/rate-limiting requirements), and does Wayne RESA have an existing API management platform or gateway the solution must integrate with or replace?

A.11. Wayne RESA expects the solution to support modern API security practices, including OAuth 2.0, JWT-based authentication/authorization, role-based access control, scopes, secure secrets management, encryption in transit, logging, monitoring, and rate limiting where appropriate. Wayne RESA does not currently require proposers to assume an existing API management platform or gateway; proposers should identify any recommended API gateway, management, or security platform and any related licensing or hosting assumptions in their proposal.

Q.12. Will the evaluation be conducted using a weighted scoring methodology, and if so, can Wayne RESA disclose the relative weighting of technical approach, past performance, price, and small/local business participation in the award decision?

https://wcresa-my.sharepoint.com/personal/ewertj_resa_net/Documents/RESOURCES/Board%20and%20RESA%20Docs/RFP%20Wayne%20RESA%20Templates/1-Templates-To%20be%20reviewed/www.RESA.net

A.12. Yes. Please refer to Section 3.8, Evaluation Criteria, for the evaluation criteria and corresponding point values. The total points possible are 100. No separate points are assigned for small/local business participation.

Q.13. Is attendance at the virtual pre-proposal conference on September 2, 2026, mandatory for proposal eligibility, or is it informational only for prospective offerors?

A.13. No, the pre-proposal meeting on September 2, 2026, was not mandatory. Please see page 2 of the RFP.

Q.14. Given the 'Onshore (USA Organization Only)' eligibility restriction, does this requirement extend to all subcontractor personnel and any offshore development, QA, or support resources, or does it apply solely to the prime contractor's corporate registration?

A.14. The onshore eligibility requirement applies to the proposer and to the personnel assigned to perform work under the contract. Wayne RESA requires assigned personnel to be legally authorized to work in the United States and expects project work involving Wayne RESA systems, data, source code, credentials, or protected information to be performed using Wayne RESA-approved access and security controls. Any proposed subcontracting or non-U.S.

resourcing must be clearly disclosed and is subject to Wayne RESA’s prior written approval.

Q.15. Are there specific page limits, required sections or formats, or a mandatory response template for this solicitation? If so, where can offerors obtain that template before the submission deadline of September 16, 2026?

A.15. There are no page limits and no mandatory response template that must be used for a proposal to be accepted. You may use the proposer response boxes within the RFP and/or your own formatting. Please note, however, all responses MUST clearly state each section, subsection, etc.

Q.16. Does this engagement anticipate a fixed period of performance only, or are option years, phased rollout gates (e.g., discovery/design phase followed by a separate build/implementation phase), or renewal terms contemplated in the resulting contract?

A.16. Wayne RESA anticipates a phased engagement consistent with the RFP schedule and deliverables. The contract may include discovery, design, development, testing, launch, knowledge transfer, warranty, and any optional post-warranty support services proposed and accepted by Wayne RESA. Proposers should clearly identify assumptions regarding phase gates, option years, renewals, and any ongoing services priced separately from the base implementation.

Q.17. Is bonding, insurance (e.g., cyber liability, E&O), or specific data processing/BAA agreements required as a condition of contract award, and if so, what are the minimum coverage thresholds?

A.17. Wayne RESA Minimum Insurance Requirements – Smart Enterprise Integration and API Services:

https://wcresa-my.sharepoint.com/personal/ewertj_resa_net/Documents/RESOURCES/Board%20and%20RESA%20Docs/RFP%20Wayne%20RESA%20Templates/1-Templates-To%20be%20reviewed/www.RESA.net

Commercial General Liability Insurance

Minimum Limits:

$1,000,000 Per Occurrence

Contractor must have their policy endorsed to add: “Wayne RESA, its departments, divisions, agencies, offices, commissions, officers, employees, and agents” as additional insureds.

Workers’ Compensation Insurance

Applicable laws governing work activities

Employers Liability Insurance

$500,000 Each accident; $500,000 disease-policy limit; $500,000 disease-each employee

Automobile Liability Insurance

$1,000,000 Combined single limit each occurrence

Contractor must have their policy endorsed to add: “Wayne RESA, its departments, divisions, agencies, offices, commissions, officers, employees, and agents” as additional insureds.

Umbrella or Excess Liability Insurance

$2,000,000 Each occurrence and aggregate

Technology Errors & Omissions or Professional Liability Insurance

$2,000,000 Per claim; $2,000,000 aggregate

Coverage should include errors, omissions, negligent acts and failure of technology /professional services associated with API development, integration, implementation, configuration and related services.

Cyber or Network Security & Privacy Liability Insurance https://wcresa-my.sharepoint.com/personal/ewertj_resa_net/Documents/RESOURCES/Board%20and%20RESA%20Docs/RFP%20Wayne%20RESA%20Templates/1-Templates-To%20be%20reviewed/www.RESA.net

$2,000,000 Per claim; $2,000,000 aggregate

Include privacy liability, network security liability, unauthorized access /use /disclosure, malware /malicious code, denial-of-service events, data breach response /notification and regulatory defense where insurable.

Q.18. Section 1.1 / Section 2.2 – References. Quoted language: “The proposer must provide a minimum of three (3) references from current or former clients.”

May projects performed by the owner/principal or proposed key personnel before formation of the bidding entity qualify toward the three mandatory references, provided the customer can independently verify the individual’s role and the work performed?

A.18. Yes, Wayne RESA is interested in the years of experience of the people who would be working on the project, not the longevity of the company.

Q.19. Section 2.3 – Contractor’s Employment Eligibility. Quoted language: “Contractor shall ensure that all individuals assigned to perform work under this Contract are legally authorized to work in the United States.”

Does this requirement prohibit a contractor from assigning personnel who lawfully perform services remotely from outside the United States, or does it apply only to personnel physically performing work within the United States?

A.19. Wayne RESA interprets this requirement to mean that all individuals assigned to perform work under the contract must be legally authorized to work in the United States. Proposers should not assume offshore performance is acceptable for work involving Wayne RESA systems, data, source code, credentials, or protected information unless specifically disclosed and approved in writing by Wayne RESA. Wayne RESA may impose additional access, security, privacy, or location restrictions based on the final scope of work.

Q.20. Section 2.0 – Proposer Information and Acceptance. Quoted language: “The undersigned acknowledges that proposer will be in good standing in the State of Michigan.”

May a non-Michigan or foreign business submit a proposal and obtain any required Michigan registration/good-standing status before contract award, or must that status already exist at the time of proposal submission?

A.20. Proposers should be able to demonstrate that they are eligible to do business and in good standing as required by the RFP and applicable law. If a proposer is not currently registered in Michigan, the proposer should disclose its status and proposed path to compliance. Wayne RESA may require Michigan registration/good-standing status before contract award or contract execution, as applicable.

https://wcresa-my.sharepoint.com/personal/ewertj_resa_net/Documents/RESOURCES/Board%20and%20RESA%20Docs/RFP%20Wayne%20RESA%20Templates/1-Templates-To%20be%20reviewed/www.RESA.net

Q.21. Section 1.3.1.F – Implementation & Project Management. The RFP states that the API system must be fully developed and functional in production by the end of 2026, while Phase 4 is listed as “QA, Security Audit & Production Launch (January 2027).” The Bid Summary also lists the anticipated contract start as October 2026, while Phase 1 is shown as September 2026.

Please confirm the authoritative project start date and required production launch deadline.

A.21. The anticipated contract start date is October 2026, subject to completion of the procurement and award process. The phase dates in the RFP will be adjusted as needed based on the actual contract award and execution date. Wayne RESA’s intended production launch timeline will be finalized with the selected contractor during discovery, with the milestone schedule adjusted to reflect the final approved implementation plan.

Q.22. Section 1.3.1 – Scope of Work / Attachment A – Pricing Schedule For comparable fixed-price proposals, can Wayne RESA provide the estimated numbers of initial API endpoints, webhook event types, expected transaction/request volumes, and anticipated environments?

A.22. Wayne RESA has not finalized the number of initial API endpoints, webhook event types, transaction volumes, or required environments beyond the requirements stated in the RFP.

Proposers should provide a clear fixed-price basis using stated assumptions for endpoints, integrations, webhooks, environments, testing, and expected usage. Final quantities and priorities will be validated during discovery.

Q.23. Section 1.3.1.C – Required Business Integrations If known, please identify the specific HR/financial platform(s), AWS services, and document-storage platform(s) expected for the initial production integrations.

A.23. Wayne RESA has not finalized the specific HR/financial platforms, AWS services, or document-storage platforms for the initial production integrations. These platforms and the related business processes will be confirmed during discovery. Proposers should describe their recommended integration approach and identify assumptions regarding available APIs, sandbox access, credentials, data objects, synchronization frequency, and third-party limitations.

Q.24. Attachment A – Pricing Schedule What quantities or assumptions will Wayne RESA use when evaluating the optional-unit-price basket (additional endpoints, webhooks, integrations, environments, training, penetration testing, emergency support, etc.) for total evaluated price?

A.24. Wayne RESA has not established a specific evaluated optional-unit-price basket quantity at this time. Proposers should complete all requested unit pricing and clearly state assumptions, inclusions, and exclusions. Wayne RESA may use the unit pricing for evaluation, future scope changes, cooperative purchasing, or comparison of optional services, but final quantities will depend on approved project scope and participating-agency needs.

Q.25. Section 1.3.1.E – Security, Governance, and Performance Requirements.

https://wcresa-my.sharepoint.com/personal/ewertj_resa_net/Documents/RESOURCES/Board%20and%20RESA%20Docs/RFP%20Wayne%20RESA%20Templates/1-Templates-To%20be%20reviewed/www.RESA.net

Quoted language: the solution must “demonstrate alignment with enterprise-grade security structures like SOC 2 Type II or ISO 27001.”

Does this require the proposer itself to hold SOC 2 Type II or ISO 27001 certification currently, or is documented architectural/control alignment sufficient?

A.25. Wayne RESA is not requiring the proposer to currently hold SOC 2 Type II or ISO 27001 certification as a minimum eligibility requirement. The proposed solution, implementation approach, security controls, and development practices should demonstrate alignment with enterprise-grade security principles such as SOC 2 Type II or ISO 27001. Proposers should disclose any current certifications, audits, control frameworks, or security practices that support their response.

Q.26. Section 1.3.1.H – Subcontracting. Quoted language: “No portion of the awarded work will be subcontracted to another firm without the express, written consent of Wayne RESA.”

May a proposer identify proposed subcontractors in its proposal and obtain Wayne RESA’s written approval as part of the award process? If so, may their technical capabilities be considered as part of the technical evaluation?

A.26. Yes. A proposer may identify proposed subcontractors in its proposal and request Wayne RESA’s written approval as part of the award or contracting process. Subcontractor qualifications and technical capabilities may be considered as part of the overall proposed project team; however, the prime contractor remains responsible for all contract performance, deliverables, security obligations, and subcontractor compliance. No subcontracting may occur without Wayne RESA’s express written consent.

Q.27. Please confirm whether a Pakistan-based software company may submit as the prime proposer, and whether any U.S. registration, Michigan presence, insurance, or local subcontracting requirement applies? Are international references acceptable?

A.27. Please see the RFP requirements regarding onshore eligibility, Michigan good standing, proposer information, employment eligibility, insurance, and subcontracting. A non-U.S.-based company should not assume it may serve as prime proposer unless it can meet all RFP requirements and applicable legal requirements. International references may be submitted if they are relevant, verifiable, and demonstrate services of similar size, scope, and complexity;

however, Wayne RESA reserves the right to evaluate whether each reference satisfies the RFP requirements.

Q.28. Is Wayne RESA currently working with an incumbent vendor, contractor, or partner supporting SMART ERP integrations, API development, middleware, database services, or related modernization efforts? If yes, please provide details regarding the incumbent’s scope of services and whether they intend to participate in this solicitation.

A.28. No, Wayne RESA is not currently working with a vendor.

Q.29. Since SMART ERP is a Wayne RESA-developed proprietary system, will the selected vendor receive access to the complete technical environment, including .NET MVC source https://wcresa-my.sharepoint.com/personal/ewertj_resa_net/Documents/RESOURCES/Board%20and%20RESA%20Docs/RFP%20Wayne%20RESA%20Templates/1-Templates-To%20be%20reviewed/www.RESA.net code, SQL Server database schema, stored procedures, business logic, existing documentation, and development/test environments required for API development?

A.29. The selected vendor will be provided access to the technical information and environments necessary to perform the contracted API development work, including relevant SMART source code, SQL Server database schema, stored procedures, business logic, documentation, and development/test environments. Access will be limited to the scope necessary for the project and will be coordinated through Wayne RESA’s technical team.

Q.30. Does Wayne RESA currently maintain architecture diagrams, data models, entity relationship diagrams, integration documentation, business process documentation, or API specifications that will be provided during the discovery phase?

A.30. Wayne RESA will provide existing documentation that is available and relevant to the API scope during the discovery phase. This may include database schema information, data models, architecture information, integration notes, and business process documentation where such materials exist. The proposer should assume that some documentation may need to be validated, supplemented, or created during discovery as part of the project's deliverables.

Q.31. Could Wayne RESA provide a prioritized list of SMART ERP modules, entities, workflows, and business processes that should be exposed through APIs during the initial implementation phase?

A.31. Wayne RESA has not finalized a prioritized list of SMART modules, entities, workflows, or business processes for the initial API implementation. The selected contractor will work with Wayne RESA during discovery to identify and prioritize the initial endpoint inventory, exposed entities, business rules, and integration use cases. Proposers should state their assumptions and describe how they will support prioritization during discovery.

Q.32. Could Wayne RESA provide details regarding the external systems expected to consume the APIs, including system names, vendors, current integration methods, data exchanged, and expected synchronization frequency?

A.32. Wayne RESA will identify the external systems expected to consume or exchange data with the API during discovery. Proposers should assume that integrations may include inbound and outbound data flows with HR/financial systems, AWS-related services, document storage, and other approved business systems. Current integration methods, data exchanged, and synchronization frequency will be reviewed during discovery where available.

Q.33. Could Wayne RESA clarify which existing integration methods (such as SFTP, CSV/Excel exchanges, or direct database access) are expected to be replaced or modernized through the new API layer?

A.33. Existing integration methods may include file-based exchanges, manual uploads, batch processes, SFTP/CSV workflows, direct database interactions, or other legacy approaches.

Wayne RESA has not finalized which existing methods will be replaced immediately versus https://wcresa-my.sharepoint.com/personal/ewertj_resa_net/Documents/RESOURCES/Board%20and%20RESA%20Docs/RFP%20Wayne%20RESA%20Templates/1-Templates-To%20be%20reviewed/www.RESA.net supported in parallel. The selected contractor should assess current-state integrations during discovery and recommend which processes should be modernized through the API layer.

Q.34. The RFP allows REST, GraphQL, gRPC, or hybrid API approaches. Does Wayne RESA have any preferred architecture standards, existing frameworks, API gateways, middleware platforms, or technology requirements that vendors should align with?

A.34. Wayne RESA does not require a specific API architectural style beyond meeting the RFP requirements. REST is expected to be acceptable as a baseline approach; proposers may recommend REST, GraphQL, gRPC, or a hybrid model where justified by the use case. Any proposed middleware, API gateway, management platform, or framework should be clearly identified, including costs, dependencies, licensing, hosting, maintainability, and Wayne RESA support implications.

Q.35. Could Wayne RESA provide expected API usage requirements, including anticipated API consumers, transaction volumes, peak usage periods, performance expectations, and scalability requirements?

A.35. Wayne RESA has not finalized quantitative API usage assumptions, anticipated consumer counts, peak usage periods, transaction volumes, or scalability requirements. Proposers should identify assumptions used in their technical approach and pricing and recommend measurable usage and performance baselines during discovery. The final performance expectations and scalability requirements will be approved by Wayne RESA as part of the implementation plan.

Q.36. Does Wayne RESA have existing identity management and security standards that the API solution must integrate with, such as Microsoft Entra ID/Azure AD, Active Directory, OAuth 2.0, JWT authentication, or other authentication mechanisms?

A.36. Wayne RESA expects the API solution to support integration with enterprise identity and access management standards, including OAuth 2.0, JWT, role-based access control, scopes, and secure secrets management. Any final identity provider integration, including Microsoft Entra ID/Azure AD, Active Directory, or other authentication mechanisms, will be confirmed during discovery. Proposers should describe their recommended approach and any assumptions.

Q.37. Beyond the stated security requirements, does Wayne RESA have specific cybersecurity assessments, penetration testing standards, vulnerability scanning tools, or compliance requirements that vendors must follow?

A.37. Proposers should plan to follow industry-standard secure development, vulnerability management, and testing practices appropriate for an enterprise API handling sensitive data.

Wayne RESA expects security testing to include vulnerability scanning, secure code review practices, remediation of identified deficiencies, and penetration/security testing as described in the RFP. Any specific tools, standards, or compliance requirements not already identified in the RFP will be confirmed with the selected contractor during discovery.

https://wcresa-my.sharepoint.com/personal/ewertj_resa_net/Documents/RESOURCES/Board%20and%20RESA%20Docs/RFP%20Wayne%20RESA%20Templates/1-Templates-To%20be%20reviewed/www.RESA.net

Q.38. Could Wayne RESA clarify the expected AWS integration requirements and whether cloud infrastructure provisioning, configuration, monitoring, backups, and operational management will be handled by Wayne RESA or included within the vendor’s scope?

A.38. Wayne RESA expects the selected contractor to clarify and recommend the appropriate AWS integration and infrastructure approach during discovery. Wayne RESA anticipates retaining responsibility for Wayne RESA-owned infrastructure and accounts unless otherwise agreed. Proposers should identify any cloud infrastructure, provisioning, configuration, monitoring, backup, or operational-management responsibilities they assume are included in their scope, as well as any related costs.

Q.39. The RFP requires the API solution to be production-ready by the end of 2026. Is this timeline fixed, or may adjustments be considered based on findings during discovery, architecture assessment, and technical complexity evaluation?

A.39. Wayne RESA’s goal is to move the API solution forward as quickly as practical; however, the final implementation schedule may be adjusted based on the actual contract start date, discovery findings, architecture assessment, resource availability, technical complexity, and mutually agreed project scope. Proposers should identify any schedule assumptions, risks, and dependencies in their proposals.

Q.40. Could Wayne RESA provide the expected milestone breakdown, acceptance criteria, and approval process for discovery, architecture design, development, testing, security validation, and production deployment?

A.40. Wayne RESA expects the selected contractor to work with Wayne RESA during discovery to refine the milestone breakdown, deliverables, acceptance criteria, and approval process. At a minimum, proposers should describe their proposed approach for discovery, architecture/design approval, development completion, testing, security validation, production readiness, deployment, documentation, knowledge transfer, and final acceptance.

Q.41. The RFP requires custom source code to be maintained in a client-owned Git repository and transferred to Wayne RESA upon milestone payment. Could Wayne RESA clarify whether ownership transfer applies only to project-specific API code or also includes vendor-developed reusable frameworks, libraries, and accelerators?

A.41. The ownership-transfer requirement applies to project-specific custom source code and custom artifacts developed specifically for Wayne RESA under this engagement. Pre-existing commercial software, vendor-developed reusable frameworks, libraries, accelerators, and other pre-existing intellectual property are not intended to transfer to Wayne RESA unless otherwise agreed in the final contract. Proposers must clearly identify any pre-existing or third-party components incorporated into the solution and any licensing, use, maintenance, or other restrictions associated with them.

https://wcresa-my.sharepoint.com/personal/ewertj_resa_net/Documents/RESOURCES/Board%20and%20RESA%20Docs/RFP%20Wayne%20RESA%20Templates/1-Templates-To%20be%20reviewed/www.RESA.net

Q.42. Does Wayne RESA anticipate requiring ongoing API maintenance, enhancements, monitoring, or support services after the required warranty period? If yes, should vendors include optional pricing for ongoing support services?

A.42. Wayne RESA may consider optional post-warranty support, maintenance, monitoring, enhancement, or emergency support services if proposed. Such services should be priced separately from the base implementation unless the proposer clearly states they are included.

Wayne RESA does not require proposers to include ongoing support in the base price unless expressly stated in the RFP or accepted as part of the final contract.

Q.43. Required Deliverables, Automated Testing: ("100% coverage enforced on ledger calculation logic" and "perfectly balanced ledger entries ($0.00 variance)"): should these financial-ledger requirements be read as applying to the SMART API scope, and if so, which SMART modules do they cover?

A.43. The financial-ledger testing requirements apply only to contractor-delivered API functionality that interfaces with or affects SMART financial/ledger business logic. They are not intended to require independent re-verification or redevelopment of the entire SMART accounting system. Where existing SMART ledger logic is exposed through the API, testing should demonstrate that API transactions preserve and produce results consistent with the existing SMART business rules. The specific modules and transactions subject to these requirements will be confirmed during discovery.

Q.44. Security and Performance: ("Minimum 99.99% operational uptime availability"): given the API layer will run on WRESA-hosted infrastructure, please confirm this commitment applies to the API software layer and excludes outages of underlying infrastructure outside the Contractor's control.

A.44. The 99.99% operational uptime expectation applies to anything outside of Wayne-RESA owned infrastructure, networks, databases, third-party platforms, planned maintenance, or other conditions outside the contractor’s control, unless expressly included in the final contracted scope.

Q.45. Will work be performed in WRESA-owned AWS accounts, with access provisioned to the Contractor?

A.45. Wayne RESA expects any work in Wayne RESA-owned accounts or cloud environments to be performed using Wayne RESA-approved access controls and procedures. Proposers should not assume unrestricted access. If the proposer recommends contractor-owned cloud resources for development, sandbox, or testing purposes, those assumptions and related costs should be clearly disclosed.

Q.46. What access will be provided to SMART documentation, database schemas, and non-production environments, and what availability will the WRESA SMART team have during Phase 1 Discovery?

https://wcresa-my.sharepoint.com/personal/ewertj_resa_net/Documents/RESOURCES/Board%20and%20RESA%20Docs/RFP%20Wayne%20RESA%20Templates/1-Templates-To%20be%20reviewed/www.RESA.net

A.46. Wayne RESA will provide access to available SMART documentation, relevant database schema information, and appropriate non-production environments for the awarded contractor.

Wayne RESA’s SMART team will be available during Phase 1 Discovery to answer questions, support technical review, and assist with understanding current SMART architecture, data structures, and business rules. Specific meeting cadence and access procedures will be established after contract award.

Q.47. In reference to Attachment A, Table B: should proposers assume WRESA procures third-party licenses, API gateway or management platforms, and hosting directly, with Table B covering only Contractor-provided items?

A.47. Wayne RESA expects to provide or procure infrastructure and software/database licensing for Wayne RESA-owned environments and approved platforms unless otherwise proposed and accepted. Table B should identify any contractor-provided software, API management platform, license, subscription, hosting, cloud service, or other third-party cost required by the proposer’s solution.

Q.48. Is there an approved budget or expected range for the implementation that can be disclosed?

A.48. Wayne RESA is unable to disclose this information.

Q.49. Implementation Timeline. Section 1.3.1 states that "the entire API system must be fully developed, security audited, and functional in production by the end of 2026," while Phase 4, "QA, Security Audit & Production Launch," is scheduled for January 2027. Should proposers plan for production go-live by December 31, 2026, or by the end of January 2027? Please also confirm whether the milestone schedule in Attachment A should align with the phase dates or with the end-of-2026 requirement.

A.49. Proposers should align their milestone schedules with the phased approach in the RFP, recognizing that specific milestone dates may be adjusted based on the actual contract execution date and approved project plan. Wayne RESA’s desired schedule is an expedited implementation; however, the final production go-live date will be confirmed with the selected contractor after discovery and approval of the implementation schedule.

Q.50. Hosting (1.3.1, Items 1.1.5, 3.1.2, 7.8.2). Item 1.1.5 states "Hosting Environment: On Prem, Client/Server, and Web Hosting," while Item 3.1.2 requires "communicating natively with AWS services" and Item 7.8.2 references failover to "an alternate cloud region." Consistent with the pre-proposal discussion, please confirm that production deployment on Wayne RESA-hosted infrastructure, with development and sandbox environments in a cloud account, is acceptable; which party bears cloud costs during development; and whether cloud-hosted production remains an option.

A.50. Production deployment on Wayne RESA-hosted infrastructure is acceptable and should be used as the baseline unless the proposer recommends an alternative approach.

Development, sandbox, or testing environments may be cloud-based if approved by Wayne https://wcresa-my.sharepoint.com/personal/ewertj_resa_net/Documents/RESOURCES/Board%20and%20RESA%20Docs/RFP%20Wayne%20RESA%20Templates/1-Templates-To%20be%20reviewed/www.RESA.net

RESA. Proposers should clearly identify which party is expected to bear any cloud costs during development and whether cloud-hosted production is included, optional, or not proposed.

Q.51. Uptime and DR scope (1.3.1, Items 5.2.1, 7.8, 7.10.1). Regarding "Minimum 99.99% operational uptime availability," please confirm whether this applies to the API services delivered by the contractor and excludes Wayne RESA-owned components (the SMART database, on-premises servers, and network), which party operates the production infrastructure after the 90-day warranty, and whether 99.99% is a design target or a contractual SLA with remedies.

A.51. The 99.99% availability expectation is intended as a design and operational target for the contractor-delivered API services and components within the contractor’s control. It does not extend to Wayne RESA-owned infrastructure, SMART database availability, on-premises servers, networks, or third-party services unless expressly included in the final contract. Wayne RESA expects to retain responsibility for operating Wayne RESA-owned production infrastructure after the warranty period unless separate support services are contracted.

Q.52. Ledger testing (1.3.1, Items 7.4, 7.1.1). Item 7.4 requires "100% coverage enforced on ledger calculation logic" and simulations maintaining "perfectly balanced ledger entries ($0.00 variance)." Consistent with the pre-proposal discussion, please confirm these requirements are satisfied by parity testing — demonstrating that API results match those produced by SMART's existing business logic — rather than independent re-verification of the ERP's internal accounting.

A.52. Yes. For the purposes of this API engagement, the ledger requirements are intended to be satisfied by testing that demonstrates API transactions and results remain consistent with SMART’s existing financial business logic and preserve required ledger integrity. The contractor is not expected to independently re-validate the accounting design of the entire existing ERP unless existing logic is modified as part of the API project.

Q.53. Base scope (1.3.1, Item 4.2; Attachment A, Milestones 5–7, Table C). Consistent with the pre-proposal discussion of approximately 50 exposed tables and candidate platforms (Red Rover, Frontline, Kronos, Amazon Business), please confirm that the Phase 1 endpoint inventory defines the base implementation scope with additional endpoints priced per Table C, and identify the intended platform and business process for each pillar's "one production integration," including whether API access and sandbox environments exist for those platforms.

A.53. The Phase 1 endpoint inventory will be used to validate and finalize the base implementation scope. Proposers may use clearly stated assumptions regarding endpoint counts, exposed tables, target integrations, and business processes for fixed-price proposals.

Any additional endpoints, integrations, environments, or materially different scope identified after discovery should be addressed through the proposal’s unit pricing, optional pricing, or agreed change-control process.

https://wcresa-my.sharepoint.com/personal/ewertj_resa_net/Documents/RESOURCES/Board%20and%20RESA%20Docs/RFP%20Wayne%20RESA%20Templates/1-Templates-To%20be%20reviewed/www.RESA.net

Q.54. Webhook latency (1.3.1, Items 4.3.1–4.3.2). The RFP requires alerts to be queued "instantly" and delivered "within a tight window of the database trigger event," but no latency figure is given. Please specify the maximum allowable time from a database change to webhook delivery or confirm that proposers should state and justify a target latency in their proposals.

A.54. Wayne RESA has not established a final quantitative webhook-latency threshold.

Proposers should state and justify the target latency assumed in their technical approach and pricing. The final measurable latency requirement and acceptance criteria will be established during discovery and incorporated into the approved implementation plan.

Q.55. Penetration testing (1.3.1, Items 8, 6.1.4; Attachment A, Milestone 8). Given that independent penetration testing is by design performed by a party other than the development team, would Wayne RESA consent to the test being performed by a specialist security firm engaged and managed by the contractor and disclosed under the Pricing Assumptions, or does Wayne RESA have a preferred provider it would engage directly?

A.55. Wayne RESA will consider penetration testing performed by a qualified independent security firm engaged by the contractor, provided the firm and scope are disclosed and approved by Wayne RESA. Proposers should clearly identify whether penetration testing is included in base pricing or listed separately in the applicable pricing assumptions. Wayne RESA reserves the right to review and approve the testing approach, scope, and final report requirements.

Q.56. Will Wayne RESA accept a commercial iPaaS and API management platform as part of the solution, or must the API layer be developed entirely as custom .NET code?

A.56. Wayne RESA does not require the API layer to be developed entirely as custom .NET code. Proposers may recommend an API management platform, middleware, or other platform component where it is integral to the proposed solution and meets the RFP requirements. Any such component must be clearly identified, including licensing, hosting, security, dependencies, maintainability, costs, and Wayne RESA support implications. Wayne RESA is not requesting unrelated optional platform-modernization components outside the API scope.

Q.57. Regarding Section 1.3.1(G)(3)(c), does the requirement to transfer 100% ownership of custom artifacts exclude preexisting commercial software, proprietary platform technology, reusable accelerators, and other preexisting intellectual property?

A.57. Yes. The requirement to transfer ownership of custom artifacts is intended to apply to project-specific custom work developed for Wayne RESA. Pre-existing commercial software, proprietary technology, reusable accelerators, libraries, frameworks, and other pre-existing intellectual property are excluded unless otherwise agreed in the final contract. Any such components incorporated into the solution must be disclosed along with applicable license or usage requirements.

https://wcresa-my.sharepoint.com/personal/ewertj_resa_net/Documents/RESOURCES/Board%20and%20RESA%20Docs/RFP%20Wayne%20RESA%20Templates/1-Templates-To%20be%20reviewed/www.RESA.net

Q.58. Approximately how many API endpoints and initial integrations are expected within the proposed scope and fixed price? If available, please identify the priority use cases or systems within the HR, AWS, and document-storage categories.

A.58. Wayne RESA has not established a final number of API endpoints or initial integrations for the fixed-price scope. Proposers should identify the endpoint and integration assumptions included in their base price, including any priority use cases assumed for HR/financial, AWS, and document-storage categories. Final priorities and scope will be validated during discovery and approved by Wayne RESA.

Q.59. Section 1.3.1(F) states that the solution must be operational by the end of 2026, while Phase 4 identifies a January 2027 production launch. Which date represents the required production deadline?

A.59. Proposers should align their milestone schedules with the phased approach in the RFP, recognizing that specific milestone dates may be adjusted based on the actual contract execution date and approved project plan. Wayne RESA’s desired schedule is an expedited implementation; however, the final production go-live date will be confirmed with the selected contractor after discovery and approval of the implementation schedule.

Q.60. What transaction volumes, concurrent-user or request levels, expected payload sizes, and measurable latency thresholds should proposers use when designing and pricing the solution?

A.60. Wayne RESA has not established final transaction volumes, concurrent-user/request levels, payload sizes, or quantitative latency thresholds. Proposers should state reasonable assumptions used for solution design and pricing and recommend measurable performance baselines. Final performance and load-testing requirements will be established during discovery and approved as part of the implementation plan.

Q.61. Does the 99.99% availability requirement apply specifically to the proposed API platform, the complete SMART application and database stack, or only the infrastructure and services controlled by the selected contractor?

A.61. The availability requirement applies to the proposed API platform and contractor-delivered components within the selected contractor’s control. It is not intended to make the contractor responsible for the full SMART application and database stack, Wayne RESA-owned infrastructure, network services, planned maintenance, or third-party outages unless those responsibilities are expressly included in the final scope of work.

Q.62. RFP Sections 1.3.1.A.1.e and 1.3.1.G.10, pages 7 and 13; Attachment A, Table B.

Please confirm that Wayne RESA will provide and operate the production hosting infrastructure, with the contractor responsible for deployment and the required 90-day warranty. If contractor-provided hosting or ongoing operational support is required, please define the expected scope and term.

https://wcresa-my.sharepoint.com/personal/ewertj_resa_net/Documents/RESOURCES/Board%20and%20RESA%20Docs/RFP%20Wayne%20RESA%20Templates/1-Templates-To%20be%20reviewed/www.RESA.net

A.62. Wayne RESA expects to provide or operate Wayne RESA-owned production hosting infrastructure unless an alternative hosting model is proposed and accepted. The contractor should assume responsibility for deployment, documentation, knowledge transfer, and the required warranty for contractor-delivered components. Any contractor-provided hosting, monitoring, maintenance, or ongoing operational support should be clearly identified and priced separately unless included in the base proposal.

Q.63. RFP Section 3.8, page 30. Under what circumstances, if any, would Wayne RESA consider paying a premium for superior results?

A.63. Wayne RESA will evaluate proposals in accordance with the evaluation criteria stated in the RFP. Price is one factor, but Wayne RESA may select the proposal or proposals determined to provide the best overall value based on qualifications, technical approach, experience, ability to meet requirements, risk, and pricing. Any premium must be supported by clearly demonstrated value, reduced risk, superior technical merit, or other benefits identified in the proposal and evaluated under the stated criteria.

Q.64. RFP Section 3.3, page 28. If a proposer does not receive acknowledgment of its submitted questions, or a question is not addressed in the addendum, what follow-up process should it use before proposals are due?

A.64. Proposers should submit questions and any follow-up inquiries through the process and contact identified in the RFP. Wayne RESA will provide official responses only through written addenda or other written procurement communications. If a submitted question is not addressed, the proposer should not rely on informal interpretations and may submit a timely follow-up request before the applicable deadline.

Q.65. Regarding Sections 1.3.1©, (D), and (G), please identify the external HR, financial, AWS, and document-storage systems prioritized for the initial implementation. Please also clarify the expected data objects and transactions, approximate number of endpoints, and anticipated API volumes.

A.65. Wayne RESA has not finalized the initial external HR, financial, AWS, or document-storage systems, data objects, transactions, endpoint counts, or anticipated API volumes.

Proposers should clearly state their assumptions for base scope and pricing. The selected contractor will work with Wayne RESA during discovery to confirm…