ESBD_371873_1724963370608_BLC020_QA ADDENDUM1.pdf

ADDENDUM #1

DATE: 8/29/2024

RFP No.: 452-24-BLC020

TITLE: Legacy Systems Replacement Project

OFFER DEADLINE: 09/16/2024 at 2:00 PM CZT

ADDENDUM ITEM #1: Question and Answer Response Darryl Gaona, CTCM/CTCD Contract Administrator

Texas Department of Licensing and Regulation Contracting and Procurement Services P.O. Box 12157 Austin, TX 78711 Email: bids@tdlr.texas.gov

Below are the answers to Offerors’ questions received as part of the 452-24-BLC020, Legacy Systems Replacement Project.

NBR

RFO Section and Paragraph Offeror Question Answer

1 Section - 4.2.2.8.10

Is there going to be a need for ongoing call center labor or service desk personnel as part of the overall procurement?

Offers must include the level of support they propose as part of their Solution for business hours and outside of business hours.

2 4.2.2.7.3 Section 7C:

Security

Is TDLR going to require the solution to be CJIS compliant, and if so, will the solution need to be deployed in a Government Cloud environment?

RFP Reference: 4.2.2.7.3 Section 7C: Security:

Offeror must describe how it has the experience appropriate to protect confidential information including PII and CJIS, and how it will meet all Texas security standards and requirements (such as Chapter 202 of the Texas Administrative Code and Chapter 2054 of the Texas Government Code).

The scope of CJIS compliance will be dependent on the proposed solution.

Please see Section 2.1.1.9.1 Hosting of the RFO.

3 Section 4.2.2.7.6

Approximately how many merge letters or other outputs need to be in the new system?

This information is not currently available.

4 Section 4.2.2.7.6

Will TDLR consider a joint approach to developing letters similar to their suggestion around reports?

RFP reference: Section 4.2.2.7.6 Section 7F:

Reporting

Yes.

5 Section 1.2.1 Is there a preference for project structure/approach? (e.g. Phased approach or Big Bang approach)?

a. If phased, which systems/programs would be the priority?

b. Are there any deadlines or timelines to have certain programs moved over to a new system?

For project structure/approach, please see Section 1.2.1, Project Objectives for preferences.

TDLR has not defined priority of systems/programs, nor defined deadlines or timelines.

6 Section 2.1.1.9.1

Does TDLR have a preference for an on-prem or cloud solution?

No. Please refer to Section 2.1.1.9.1, Hosting of the RFO.

7 Section 2.1.1 Does TDLR have a target date to have all license types moved into the new system?

Please see response to Question #5.

8 1.3.1:

Schedule of Events

Due to this project's complexity, may we request an extension of 2 weeks for the RFO response date?

No.

9 Section 1.2.3 Table 1 - item

What specific functionalities from JO are required in the new system?

Please refer to Attachments C, General Operation, and Attachment D, Technical Requirements Response Workbook, of the RFO.

10 Section 1.2.3 Table 1 - item

Are there any additional features or customizations needed beyond what JO currently offers?

TDLR will discuss system features and customizations across all license types with the Contractor after contract award.

11 Section 1.2.3 Table 1 - item

Will historical data need to be migrated?

a. If yes, what is the volume of data that needs to be migrated from the existing system?

b. Are there any data quality issues that need to be addressed before migration?

c. Where is the data stored today and in what format?

Please refer to Sections 2.1.1.5, Data Conversion/Migration and 4.2.2.7.5, Section 7E: Data Conversion/Migration of the

RFO.

12 Section 1.2.3 Table 1 - item

What external systems does the JO integrate with (e.g., payment gateways, other state systems, third-party applications)?

a. Are there existing APIs or connectors that can be leveraged, or will custom integration be required?

JO does integrate with Texas.gov for payments. TDLR will discuss all other integrations during the requirements phase of this project with Contractor after contract award.

13 Section 1.2.3 Table 1 - item

Are there any specific dashboards and reports for JO?

a. How many dashboards and reports are currently being used in JO?

Please refer to Attachment C, General Operation, and Attachment D, Enabling Technology tab and Reporting tab of the RFO for requirements.

The information about quantity of dashboards and reports is not currently available.

14 Section 1.2.3 Table 1 - item

How many different user roles and access levels currently supported by JO?

There are multiple roles to access functions within JO.

Please refer to Attachment C, General Operation, and Attachment D, Technical Requirements Response Workbook, of the RFO for requirements. TDLR will discuss specific role-based access needs with Contractor after contract award.

15 Section 1.2.3 Table 1 - item

Are there any specific security requirements and access controls for JO which will be different from the rest of the system?

Please refer to Attachments C, General Operation, and Attachment D, Technical Requirements Response Workbook of the RFO for requirements.

16 RFO 1.3.1

Table 4

RFO 1.3.1 Table 4 – Due to the complexity of the RFO, would TDLR please consider a 30-day extension to the submission deadline?

Please see response to Question #8.

17 RFO 1.2.3

Table 1

RFO 1.2.3 Table 1 contains an overview of TDLR’s seven core systems. However, while WXM is listed in Table 1, it is not listed in Attachment K. In addition, Attachment K lists “Other” associated with Customer Services, but no other information is provided.

a. Since Table 7 indicates this Legacy System is to be replaced and the data migrated, can TDLR add the information for WXM to Attachment K?

b. If in scope, can TDLR add “Other” to Table 1, and also complete the information associated with “Other” in Attachment K?

The Solution must include the Weather Modification (WXM) regulatory program. However, this regulatory program is currently being processed manually. There are less than 15 active licenses.

18 RFO 1.2.3

Table 1

RFO 1.2.3 Table 1 includes JO as one of TDLR’s seven core systems. Since Table 7 indicates this Legacy System is to be replaced and the data migrated, can TDLR update Attachment K with complete information about this third-party application?

TDLR will discuss additional information with Contractor after contract award.

19 Attachment K Attachment K lists IHB, but none of the other information is provided. Since Table 7 indicates this Legacy System is to be replaced and the data migrated, can TDLR update Attachment K with complete information about this application?

This information is not currently available for third-party systems including IHB Decals.

20 Attachment P Attachment P: Can TDLR clarify if this attachment needs to be included in the submission? If so, in what section should it be placed?

Attachment P, Vendor Compliance Checklist, is informational and not required to be submitted.

21 Attachment F Attachment F references RFP 452-24-BLC010.

Can TDLR confirm it should reference RFO

452-24-BLC020?

Confirmed.

22 Attachment G Attachment G is to be filed online. Can TDLR confirm that a copy does not need to be included in the submission? If a copy does need to be provided, please indicate in what section it is to be placed.

Vendors must submit a current Attachment G, Certificate of Interested Parties, with their response and meet the requirements of the RFO.

23 RFO 4.1.1.6 RFO 4.1.1.6 indicates a copy of the Joint- Venture Agreement must be included in the submission. Can TDLR confirm this can be included as an appendix item?

Yes.

24 1.3.1:

Schedule of Events

Given the magnitude of this RFO and the time allocated between issuance of TDLRs written response to questions and the deadline for submission, will the State consider, at a minimum, a 2 week extension?

Please see response to Question #8.

25 General Can the State clarify why the initial RFO was cancelled?

No.

26 General Can the State distinguish the major differences between the cancelled RFO and the current

RFO?

Please see response to Question #25.

27 Section

2.1.1.9.1 – Hosting

Can the State clarify the requirements around TX-RAMP or the equivalent thereof? On page 36, under Section 2.1.1.9.1 – Hosting, the State says a TX-RAMP- Level 2 certification is required, or an equivalent under the Fast Track certification program. It’s understood a SOC 2 Type 2 meets the equivalency requirements, what is not understood is if this satisfies TX- RAMP indefinitely or does the vendor need to secure TX-RAMP certification? If so, when?

Prior to contract or within an appropriate timeframe after award?

TDLR requires the Solution offered to be TX-RAMP Level 2 certified.

A Solution with a TX-RAMP Level 2 Provisional Certification may be submitted with an Offer.

Questions related to TX-RAMP Certification requirements must be directed to tx-ramp@dir.texas.gov.

28 Section

4.2.2.12 - HUB

In terms of the HUB Goal outlined on page 74, Section 4.2.2.12 – Section 12, the State notes “It has been determined by TDLR that there are probable subcontracting opportunities in the scope of the work for this RFO. The HUB Goal for this procurement is twenty-six percent (26.00%) for all other services contracts. The key word here is “probable”, while it is understood the HSP document needs to be submitted, what is not understood is if a HUB needs to be a participant or if the Offeror needs to act in good faith, particularly because the Offeror will provide all services identified within the RFO. Can the State clarify if the 26% HUB partnership is mandatory or voluntary?

Regardless of the State’s answer, please elaborate on the appropriate steps to avoid a non-responsive submittal.

The HUB Goal is not mandatory.

Offerors must demonstrate good faith, as required by 34 TAC sec. 20.285(d).

29 Section 2.2.1.2.1, Table 21:

Integration

The State identifies six systems to replace and two outside of scope. Table 21 identifies 12 interfaces. Can the State confirm the two systems outside of scope need to interface with the new solution as well, for a total of 14 and not 16?

Please refer to Table 7, TDLR Licensing Systems, and Table 21, Systems Targeted for Integration, of the RFO.

30 Section 2.1.1.5

- Migration / Cutover

The State identifies the Number of Records/Data Conversion Scope. Can the State provide the size of each database?

Please refer to Attachment K, TDLR Application List.

31 General What is the budget for this RFO? If all cost proposals come in above a certain amount, would this RFO be cancelled? Did the legislature allocate any funds specifically for this project? If so, what is the amount allocated, and when does it need to be used?

This information is not currently available.

32 Section 2.1.1 - Implementation Services

The State identifies 40 Programs under the umbrella of TDLR, while a brief mention to the Agile approach is noted, does the State have a preferred implementation approach, i.e.

waterfall vs agile? Are there priority Programs to implement first? Does the State expect all 40 to Go-Live at once?

Please see response to Question #7.

33 Data Migration Can the State clarify the number of data sources expected to be converted to the new system? Does each program have its own database? What are the sizes of the data sources? What type of format will the State provide these data sources in, e.g., Excel, pdf, etc.?

Please refer to Attachment K, TDLR Application List, of the

RFO.

34 Evaluation Could the State provide insight into how the evaluation committee reviews the RFO?

Specifically, does each reviewer examine the entire RFO, or is it divided into sections for individual review? Understanding this will help us structure the RFO to facilitate the most efficient review process.

Please refer to Section 1.3.10, Evaluation Process, and Section 4.2, Offer Instructions, of the RFO.

35 4.2.1, Section

Does Section 17: Glossary of Terms need to be part of the RFO?

Offerors should provide a Glossary of Terms that defines any language that the Offeror uses that is unique or specific to their solution or that may lead to a better understanding of the Offer.

36 Section 4.1.1.4

- Concise Offers

Is there a maximum page number? Please refer to Section 4.1.1.4, Concise Offers, of the RFO.

37 Section 4.2.2.4

SLA/ SLR

Is there room to redline the SLA/SLR? If so, does the State expect redlines to be provided in Attachment B or in the body of the Proposal?

Please refer to Section 4.2.2.14, Section 14 – Service Level Agreements (SLAs)/Service Level Requirements (SLRs), of the

RFO.

38 Section

2.2.1.2.1 - Applications for Integration, Table 21

Table 21 identifies 13 interfaces. Can the State clarify if these interfaces are single or bi-directional?

TDLR will share this information with Contractor after contract award. However, Offerors may refer to Section 4.2.2.16, Assumptions and Exceptions, of the RFO.

39 General How many field inspectors would need access to the new solution?

Please refer to Table 7, Scope Overview, of the RFO for the number of users.

40 Section 2.2.1.2.2.

What type of AI functionalities does the State desire for the new solution?

Please refer to Section 2.2.1.2.2, Technical Capabilities Summary, of the RFO. No preferences have been established at this time.

41 Attachment K Document:

ESBD_371873_1723662817266_Attachment K.

TDLR Applications List v1.1 identifies 49 application types. Can the State confirm this number? How many of these application types require renewals?

Attachment K, TDLR Application List, is a list of Systems and their associated Applications that support TDLR's current functionality and are in scope for this Project.

Attachment J, TDLR License Inventory, contains TDLR’s Regulatory Programs and License Types.

Please refer to Table 34, Terms and Definitions and Section 2.1, Project Scope, of the RFO.

42 Attachment J Can the State confirm, per document ESBD_371873_1723662798202_Attachment J - TDLR License Inventory, there are 204 unique license types?

Please refer to Table 7, Scope Overview and Attachment J, TDLR License Inventory, of the

RFO.

43 Section 3.6 Insurance

Are the Insurance Requirements outlined in the RFO Main Document mandatory? Do vendors have the option to provide exceptions?

Insurance Requirements are mandatory. Please refer to Section 3.6.1, Required Coverage, and Section 3.6.2, Additional Insurance Requirements, of the RFO.

44 Section 2.1.1 On page 20 of the RFO Main Document, under Section 2.1.1: “Offerors must propose a phased rollout strategy to support TDLR’s licensing programs and license types based on best practices and Offeror experience. This incremental rollout approach should deliver real benefits to TDLR…”. Can the State provide a list of the 40 prioritized licensing programs, in order of priority? Which Legacy Systems need to be replaced first?

Please see response to Question #5.

45 Section 4.2.2.13 Pricing

If a phased rollout is desired, how does the Sate prefer pricing to be presented? Per phase or as the total implementation sum?

Please refer to Section 4.2.2.13, Section 13 – Pricing Workbook, of the RFO.

46 Attachment P Does the State expect Attachment P - Vendor Compliance Checklist, to be submitted as a transmittal sheet?

Please see response to Question #20.

47 General Can TDLR provide any information as to the reason for the cancellation of the previous RFO for its Legacy Systems Replacement Project (RFO #452-24-BLC010), as well as the reason for the re-release?

Please see response to Question #25.

48 General Given the complexity of the RFO, extensive requirements, short timeline between Q&A and submission, etc., can the proposal due date be extended by at least 2-4 weeks?

Please see response to Question #8.

49 Q&A Does the Q&A for the previous RFO #452-24- BLC010, apply to this new RFO?

No.

50 Reference Would it be acceptable for reference letters submitted for the previous RFO for this project (RFO #452-24-BLC010) to be submitted for fulfilling the reference requirements for this

RFO?

No.

51 HUB Would HUB subcontracting “good faith” efforts for the previous RFO for this project (RFO #452- 24-BLC010) be applicable to this RFO as well?

No.

52 HUB What, if any, preferred HUB Vendor(s) has TDLR worked with that would be ideal for contributing to this project?

None.

53 Section 4.1.1.4 Concise Offers

Section 4.1.1.4 Concise Offers: Given the 150-page limit (not including appendices), please clarify which appendices/attachments are NOT included in this page limit.

Please refer to Section 4.1.1.4, Concise Offers, of the RFO.

54 Attachment C:

Functional Requirements

General: Assuming an offeror has a solution that is proven to support complaint processing, investigation case management, and enforcement actions, will the potential future integration of enforcement processes into the new system be performed under another procurement or contract addendum with the contracted offeror for the Legacy Systems Replacement project?

Please refer to Section 2.2.1.2.2, Technical Capabilities Summary, of the RFO.

55 4.2.2.4.3 Section 4C:

Financial Assurance of the RFO

Financial Statements section: Can TDLR explain the reasoning for differing Financial Statement requirements for Publicly Traded Entities vs. Privately Held Entities?

Please refer to Section 4.2.2.4.3, Section 4C: Financial Assurance, of the RFO.

56 Section 1.3.10.1

Section 1.3.10.1: Do the minimum qualifications outlined in Section 1.3.10.1 need to be met by the proposed team (including prime offeror and any subcontractors) or does the prime offeror need to meet those qualifications on its own (without any subcontractors)?

Please refer to Section 4.1.1.6, Multi-Contractor Solutions (Joint-Ventures) of the RFO.

57 Section 2.1 Project Scope

In section 2.1 Project Scope, the previous RFO #452-24-BLC010 reads "Subcontracts, if any, entered into by the Offeror must be in writing and be subject to the same requirements as the Contractor." This current RFO removes the phrase "subject to the same requirements as the Contractor". Can TDLR explain the reason for the removal of this phrase?

No.

58 1.2.3 Current State Overview

1.2.3 Current State Overview: In the previous

RFO #452-24-BLC010, Jurisdiction Online (JO) Permitting & Portal was not included as in-scope in the procurement, however the current RFO includes it as in-scope for replacement.

Can TDLR explain the reasoning for this being added as in-scope for this RFO?

No.

59 Section 4.2.2.10

Section 4.2.2.10 stipulates reference information. Would subcontractor references be valid to fulfill reference requirements, or would an offer be deemed unresponsive unless all references are from the prime offeror?

Please refer to Section 4.2.2.10, Section 10 – Offerors References, of the RFO.

60 Section

2.1.1.9.1 and Attachment L

Regarding hosting requirements, section

2.1.1.9.1 and Attachment L – RFO for DCS, does TDLR anticipate obtaining a DCS exemption for an Offeror’s SaaS hosted solution?

If the awarded offer proposes a SaaS Solution, TDLR will pursue an exemption.

61 HUB HUB Goal – Is the 26% HUB goal scored as part of the response evaluation? If so, in which section of the scoring criteria would this be applied?

Please see response to Question #28.

62 General General: Does TDLR have a preferred timeline for initial system implementation? When ideally does TDLR want to have this system “go live”?

Please see response to Question #5.

63 General General: Please elaborate upon any timing considerations for when specific programs / areas / functions will need to be fully transitioned to the new solution.

Please see response to Question #5.

64 General General: Can bidders assume that the portable tablets for TDLR staff and internet connectivity will be supplied by TDLR?

Portable devices and internet connectivity are out of the scope of this Solicitation.

65 General General: What costs has TDLR incurred for the initial set up, ongoing maintenance, hosting, software licensing, support, and enhancements (i.e., “change orders”) over the lifetime of the current systems to be replaced by the new solution?

This information is not currently available.

66 General General: What presentations, software demonstrations and/or estimates / quotes has TDLR programs received related to this project and from whom?

Presentations, software demonstrations and/or estimates/quotes predated this Solicitation.

67 General General: For data conversion requirements, please inventory all data sources, file formats, and size of the current data sets to be converted and migrated into the new system.

Please see Attachment K, TDLR Application List.

68 General What is TDLR’s budget for the initial system implementation?

This information is not currently available.

69 General What amount is being budgeted for ongoing support, software licensing, hosting, and support of the new system?

Please see response to Question #68.

70 General What, if any, amount of the budget is subject to expire by a certain timeframe and when? Please elaborate.

Please see response to Question #68.

71 General Does TDLR desire for its staff to be trained on application administration to make changes, updates, and add new capabilities to the system after go-live? Or is TDLR anticipating the vendor to perform future updates and changes (such as addition of new license types, form configuration, business rule changes, etc.) to the system? This will help bidders include the desired scope of services and associated costs in their bids.

Please refer to Section 2.1.1.7, Training and Knowledge Transfer, Section 2.1.1.9.2, Production Support & Transition, and Section 4.2.2.8.8, Section 8H:

Knowledge Transfer and Training Approach (Optional:

OCM), of the RFO.

72 General If TDLR desires to be trained on application administration so agency staff can make changes to the configuration of the system after go live, how many administrator users does the agency want to be trained on this capability?

This information is not currently available.

73 General Please provide an approximate number of standard email/letter templates that will be used by TDLR that are to be integrated and automated by the system.

Please see response to Question #3.

74 General How many different or distinct permit and license types will be supported in this solution?

Please provide a comprehensive list.

Please refer to Table 7, Scope Overview, of the RFO and Attachment J, TDLR Licensing Inventory.

75 General Please identify all other systems that the new solution will need to integrate with (i.e. payment processor, other systems such as financial, etc.)

along with an inventory of which interfaces will need to be wither a one-way (import or export) or two-way data exchange?

Please refer to Section 2.2.1.2.1, Applications for Integration, of the RFO.

76 General Please provide the annual number of applications / renewals processed by TDLR.

Please refer to Section 2.1, Project Scope, of the RFO.

77 General Please provide a breakdown of the number of TDLR employees that will be using the new solution by TDLR Program, role, as well as which ones will be performing mobile inspections.

Please refer to Sections 1.2.4, Project Stakeholders, and 2.1, Project Scope, of the RFO for additional information about stakeholders. TDLR is not considering inspection-related services at this time.

78 General Which vendors attended the pre-proposal conference?

TDLR will publish the list of Pre- Offer conference attendees as part of the Q&A response.

79 General Will the selected vendor have the opportunity to provide exceptions and/or alternative contract language during contract negotiations, or will vendors need to provide those within their respective proposals?

Please refer to Section 4.2.2.2, Section 2 – Cover Letter and Executive Summary, and Section 4.2.2.16, Section 16 – Assumptions and Exceptions, of the RFO.

80 General Can TDLR provide an inventory of all the reports that need to be replicated within the new system?

This information is currently unavailable. Please refer to Section 4.2.2.7.6, Section 7F:

Reporting, of the RFO for additional information.

81 Section 2.1.1.9.1

If the solution is a SaaS solution, will the ownership of licenses be on the Provider or State of Texas?

Vendors should propose a structure (ownership/license) that provides the best value for

TDLR.

82 Section 2.1.1.9.1

If the solution is a Saas solution with licensing owned by the State of Texas, should the Provider be a reseller of those licenses?

Please see response to Question #81.

83 Section 2.1.1.9.1

For the integrations listed in Table 21, are there any security restrictions which prevent direct API integrations to those systems?

Due to the sensitive nature of this question, TDLR will share this information with Contractor after contract award.

84 Section 2.1.1.9.1

For the integrations listed in Table 21 that are Batch types, are those scheduled batch transfers or on-demand batch transfers?

Due to the sensitive nature of this question, TDLR will share this information with Contractor after contract award.

85 General Is TDLR expecting third party resources from agencies like DRA to be able to log into the platform and review the applications?

Please refer to Section 2.2.1.2.2, Technical Capabilities Summary, and Attachment C, Functional Requirements Response Workbook, of the

RFO.

86 General If Jurisdiction Online Permitting Portal is not maintained by TDLR and is a third-party system is TDLR going to be able to provide information about this system upon start of the project?

Yes, TDLR will share this information with Contractor after contract award.

87 General How many TDLR SMEs will be available to provide information about each of the licensing programs?

Please refer to Section 4.2.2.8.4, Section 8D:

Implementation Approach/Deployment Strategy, of the RFO.

88 General How many business licenses do you process a year and how many individual licenses do you process a year?

Please refer to Table 7, Scope Overview, and Attachment J, TDLR License Inventory, of the RFO for additional information.

89 General How does TDLR evaluate and determine the financial and non-financial benefits of leveraging one single platform (eg: faster access to data, easier to pass work between several departments, etc.)

Please refer to Section 1.3.10, Evaluation Process, of the

RFO.

90 General How does TDLR evaluate the cost of building and maintaining 13 integrations on various cloud-based platforms? (eg: cost per transaction on the platform, future maintenance cost, etc.)

Please see response to Question # 89.

91 General Does TDLR ever have seasonal spikes in case volumes?

Yes. TDLR will share this information with Contractor after contract award.

92 General How many agents would be processing licenses and permits or managing this process? Are all 400 staff working on cases or do some only have viewing/approving needs?

Due to the sensitive nature of this question, TDLR will share this information with Contractor after contract award.

93 References Noting that any reference information is public record, will TDLR allow respondents to provide confidential references for their past performance and capabilities upon down selection, under a Non-Disclosure Agreement (NDA)? And/or would TDLR sign a Non- Disclosure Agreement (NDA), in order to protect confidential information required by section (insert RFP references section)?

Please refer to Section 4.1.1.8, Offer Integrity, of the RFO.

94 General What challenges do you face in ensuring that each team’s tasks are completed within set timeframes, and how do you currently measure performance at a granular level?

Due to the sensitive nature of this question, TDLR will share this information with Contractor after contract award.

95 General How does TDLR currently manage the breakdown and tracking of complex cases that require input from multiple teams or departments?

TDLR is unable to answer this question.

96 General How important is it for TDLR to have a unified platform that supports not just licensing and permitting, but also other middle and back-office operations?

Please refer to Section 1.2, Project Background, of the

RFO.

97 General Could TDLR identify the key differences between the April RFP and the August RFPs, so that previous respondents can ensure that the RFP is updated appropriately?

No.

98 General On a scale of 1-10, (10 being most important), how important would it be for TDLR to have a platform that can orchestrate and automate work in the system, not only tracking the work that has been done)

Please see response to Question # 96.

99 General What does TDLR's seasonal licensing and permitting transactions look like? Are there any spikes in transaction volumes to be aware of?

Please see response to Question #91.

RECEIPT OF ADDENDUM 1 OF RFO #452-24-BLC020

THE RESPONDENT’S OFFER SUBMITTAL MUST INCLUDE SIGNED COPY OF THIS

ADDENDUM AS ACKNOWLEDGEMENT OF RECEIPT.

Signature: Title:

Printed Name: Date:

Company Name: