50011-ULLAF26010-1.pdf

Solicitation No. 26010 Addendum No. 1

26010 Addendum 1 Page 1 of 3

Addendum to Request for Proposals for

Electronic Research Administration (eRA) System Implementation and Support Services RFP

The following clauses/alterations shall be made part of the original solicitation as though issued at the same time and shall be incorporated integrally therewith.

Addendum Provisions:

Item 1

Add to RFP:

Add list of vendors submitted questions and University response to vendor submitted questions:

Question Answer

1) Does the University expect to received: Only one original print of the financial proposal? Yes.

2) Does the University expect to received: One original print and six copies of the financial proposal packaged separately

Yes. The Financial Proposal is to be packaged separately from Technical Proposal copies. All separate packaging may be grouped together in a larger outer shipping package, as long as internal separation and labeling requirements are maintained.

3) If the University wants multiple printed copies of the financial proposal, can all print copies be submitted in a single sealed envelope labeled FINANCIAL PROPOSAL?

Yes.

4) Does the University expect to receive: Does the "original" proposal require a wet signature or will an electronic signature suNice?

A wet signature is not required; an electronic signature is acceptable.

5) Should the electronic copies of the proposal (stored on USB drives) include or exclude the financial proposal?

The RFP does not include a requirement for the financial proposal to be included in the USB drives.

26010 Addendum 1 Page 2 of 3

6) Does the University intend to implement all modules at the same time, or is there a preferred order of delivery for the system components?

The University's preference is to implement all system components at the same time.

However, that is not required, and as outlined in Section 1.8(H) of the RFO, proposers are asked to provide a detailed implementation schedule.

7) Does the University intend to use FDP Sub Clearinghouse functionality?

Use of the FDP Sub Clearinghouse is preferred.

8) Aside from the integrations disclosed in the RFP, what other third-party systems (IRB, IACUC, IBC, Export Control, etc.) will the solution need to integrate with?

No additional third-party systems have been identified at this time. However, the system should be capable of import/export data, such as via csv formats or RESTful APIs.

9) Does the University have a preferred/required go-live date?

Preferred go live is July 1, 2026 including data migration (as applicable) and integration with Banner.

10) With regard to proposal and award data migration, can the University characterize the current set of data it would like migrated into the chosen solution? (e.g., the last X years of proposal data, the last X years of awarded proposals only, the last X years of award data, including/excluding budget data, including/excluding attachments, all existing proposal/award data, including/excluding HR data and/or legacy HR data, including/excluding sponsor data, etc.)

The University intends to migrate the past 5 years of proposal submissions and awards;

including award data, budgets and attached documents. The data migration should also include all existing proposal and award data, including HR data, sponsor data, among others.

26010 Addendum 1 Page 3 of 3

11) With regard to COI data migration: Will the University want existing COI data migrated? If so, can the University characterize the COI data it would like migrated into the chosen solution? (e.g., all current disclosures, all disclosures from the last X years, The University intends to migrate all current COI disclosures, along with past 5 years of COI data need to be migrated.

12) Does Louisiana Lafayette require researcher profiles to be searchable by collaborators?

Researcher profile searchability by collaborators is desirable if included as part of the default solution with no added coast or implementation effort.

13) Is Louisiana Lafayette looking to include a Technology Transfer software solution as part of the bid response?

Yes. Please provide as an add-on in the response.

14) Would Louisiana Lafayette consider altering the response method to include emailed responses if submitted prior to the state due date and time?

No.

ACKNOWLEDGEMENT: If you have already submitted your proposal, and this Addendum creates a need to revise your proposal, you must indicate any change(s) below, identify your business name and sign where shown. Revisions shall be submitted/delivered PRIOR to proposal due date and time, by email. Proposal revisions received after proposal due date and time cannot be considered, whereupon the proposer must either honor or withdraw its original proposal. If you have already submitted your proposal and this addendum does not cause you to revise your proposal, acknowledge receipt of this addendum by signing below and returning it to the Purchasing Department prior to proposal due date.

Kristi Montet, NIGP-CPP Director of Procurement and Travel University of Louisiana at Lafayette Department of Purchasing

Firm Name: _________________________________ Signature: ________________________________________________