Statement of Work for Treasury Management Implementation ...... · Statement of Work for Treasury...

Statement of Work forTreasury Management Implementation Services (RFP 10536)Project Name: Treasury Management – Order No. __________ Contract No.

IT Implementation Services of 21 Rev. 2_12/27/2011Contract #__________

1. Representatives:

LCRA Project Manager James ChurchillClient Relationship [email protected] Lake Austin Blvd, Austin 78749512.578.2094

LCRA Technical Lead/SME Tommie BushongSupervisor, Solution [email protected] Lake Austin Blvd., Austin 78749512.578.2333

LCRA Agent Tayo SokaleCategory Manager Sr.3700 Lake Austin Blvd., Austin, TX [email protected]

Supplier [Name][Title][Address][Tel. No.][email]

2. Project Background: Treasury management workstations are used to perform a wide rangeof functions related to managing cash accounts, investment and debt portfolios, financial risk,bank reconciliations account analysis, and reporting of positions and forecasts for anorganization. Typically systems of this nature perform functions such as daily cashtransactions, electronic funds transfers, account analysis for banking services, and otherfunctions.

LCRA has implemented PeopleSoft for most of its financial operations. There is the optionof submitting proposal for the implementation of the PeopleSoft Cash Management, DealManagement and Risk Management modules only. Any other software, for which proposalis being submitted, must be able to integrate with PeopleSoft.

3. Description of Services and Deliverables: LCRA is seeking an experienced supplier to provideand implement a Treasury Management tool with capabilities to perform treasury and cashmanagement functions in accordance with the requirements provided in the RFP document.Supplier services shall also include testing, training and post production support. Services willbe performed for development, test and production environments.



3.1. Cash Management:3.1.1 Manage cash accounts; add/inactivate accounts – Set-up accounts within the TMS

and associate the account to a Demand Deposit Account (DDA) and GeneralLedger account. Must be able tag accounts inactive or closed

3.1.2. Unattended pulling of bank information reports (currently manually uploading BAIfiles) – Receive a Bank Administration Institute (BAI) from bank (JP Morgan Chase)multiple times a day and automatically load to TMS without staff logging into JPMorgan.

3.1.3. Set Daily Cash Position - LCRA currently monitors 33 accounts held at JP MorganChase bank. These accounts make up 28 commercial DDAs and 5 ControlledDisbursement Accounts (CDA). Previous day ending account balances (this BAI fileis available by 7:30 am next day) and controlled disbursement balances (this BAIfile is available by 10:15 am current day) shall load automatically. Daily CashPosition process shall have the ability to enter pending items and automaticallygenerate entries for Debt and Investment activity (example: investment maturityor P/I payment for Debt). Target balance should be assigned to each account andeasily updated. A position report shall reflect if any of the accounts require aninvestment trade for excess or deficit funds. Excess or deficit funds are determinedby subtracting the current balance from the target balance.

3.1.4. Workflow daily cash position for review and approval processes – Within TMShave different levels of review and approval for workflow processes. The differentworkflow level need to be user access limited. All approvals should be stored inthe TMS for later audit.

3.1.5. Process and track electronic funds transfers: wires, credit/debit ACH – Transmita flat file to JPM Morgan Chase bank to process a bulk ACH debit.

3.1.6. Monitor and forecast cash requirements – TMS should be able to forecast at leastthe next 12 months. TMS should be able to forecast from data categories coming

over from bank historical information as well as user defined categories. It shouldbe able to generate forecast activity based on historical bank data for bank definedcategories. Additionally, TMS should accept manual inputs either directly or via flatfile to all categories.

3.1.7 Ability to research historical cash information and preform trending analysis -Accept a BIA file from JP Morgan with 1 year of historical cash transactions.

3.2. Account analysis for banking service fees – Retain bank contact pricing with theflexibility to add or delete services with ease. Then accept a BAI file monthly andreconcile billed services to contract pricing.

3.3. Investments:3.3.1. Manage investment accounts; add/inactivate accounts - Set-up custody accounts

and money market accounts within the TMS. Each custody account will need theability to be associate to corresponding General Ledger account and a settlement



cash account. Examples: 1) Texpool account 0001, is GL account 131001,transactions settle into JP Morgan account 101. 2) LCRA RF 7101, is GL 131000,custody account 441. Must be able to tag accounts inactive or closed.

3.3.1. Functions for investments should include, but are not limited to – LCRA and it’saffiliates are restricted by the Texas Public Funds Investment Act (TexasGovernment. Code, Chapter 2256). Within this act LCRA is limited to the types forinvestments purchased and reporting requirements. LCRA currently has the abilityto trade in 22 accounts and currently hold over 30 different cusips.a. Recording investments at the time of purchase at a premium or discount

including the accrued interest purchase.b. Amortization/accretion of premiums/discounts on investments.c. Fixed rate, Variable rate and discount note debt instruments.d. Tracking the change in fair market value.e. Gain/Loss on the sale of investments.

3.3.2. Mark to market the value of investments at month end. This process needs to beautomated. LCRA currently prices investments monthly using Bloomberg. TMS mustbe able to accept a flat file or provide a proposal for a pricing service that will havean automatic feed.

3.3.3. Reconciliation of the safekeeping report with US Bank custodian. Need to have theability to upload a flat file from US Bank and reconcile information in TMS vs all 22custody accounts.

3.3.4. Analyze risk for interest rate movements. TMS shall be able to hold various indexrates to be used for comparison reporting. These include but are not limited to; 1, 2,3, 6 month and 1yr LIOBR, SIFMA, and 6mth, 1yr, 2yr, 5yr, 10yr and 30yr US Treasuryrates.

3.3.5. Accurately tracking Money Market Fund and Investment Pool daily interest accrual.LCRA currently has 15 investment pool accounts spread between Texpool andLOGIC. Must be able to accept a flat file from Texpool or Logic or provide a proposalfor a pricing service that will have an automatic feed.

3.3.6. Ability to designate the make-up Money Market Fund and Investment Pool byinvestment type (i.e. 80% Commercial Paper, 20% Treasury Notes). This informationis used to report on composition of total investment portfolio.

3.3.7. Ability to put in forecasted investment purchases or hypothetical trades. TMS shallbe able to accept a forecasted investment purchase and then variance the impactof trade vs. current or past portfolio.

3.3.8. Investment portfolio (and every security within) should be able to be measured byits Weighted Average Maturity and Yield.

3.3.9. Each security should be able to be categorized by type for reporting and be able toreport on percentage of portfolio is in any given category.



3.4. Debt:3.4.1. Manage debt accounts; add/inactivate accounts - Set-up new bond series

accounts within the TMS. Debt accounts need to be able to roll up under bondspayable account on GL, but be able to assign at a project level. LCRA andTransmission have over 20 different bond series consisting of over 400 CUSIPS.Must be able tag accounts inactive or closed.

3.4.2. There are several different credit lines and commercial paper programs thatare used for short term debt. The system must be able to set-up theseprograms, track changes in amount and rates (both fixed and variable) andreport.

3.4.3. Functions for investments should include, but are not limited to –3.4.3.1. Recording new debt issuances including the premium or discount, the

yield to maturity and yield to call.3.4.3.2. Effective Interest Method: Amortization/accretion of

premiums/discounts on debt instruments (not Black Scholes).3.4.3.3. Calculate accrued interest expense and interest paid.3.4.3.4. Automatic mark to market value of the debt maturities. This process

needs to be automated. LCRA currently prices investments monthlyusing Bloomberg. TMS must be able to accept a flat file or provide aproposal for a pricing service that will have an automatic feed.

3.4.3.5. Defeasance and refunding of debt.3.4.3.6. Be able to flag/note if the transaction is not routine and run a report for

these items (example: if there is a defeasance that is not scheduled orfrom a refunding, it will need to be able to report on those changes inpar and amortization outside of regular scheduled changes in par andamortization).

3.4.3.7. Fixed and Variable rate debt instruments.3.4.3.8. Facilitate hedge accounting on interest rate swaps

3.5. Principal and Interest payments tracked by series, payment dates and allocation toline of business- Principal is paid annually on May 15th. Interest is paid semi-annuallyon November 15th and May 15th. The convention for calculating interest is parmultiplied by the coupon rate divided by 2 for each CUSIP rolling up to a total interestdue for each series. The 1st coupon paid is based on actual number of days fromclosing to 1st payment for a new bond series. CUSIP numbers can change if a CUSIPis only partially defeased so TMS should allow for CUSIP numbers to be changed.Some of the series have split coupons meaning there can be 2 maturities for the samedate at different interest rates but they will have different cusips. For example, seriesXYZ could have $10 million maturing on 5/15/18 with a 5% coupon and $2 millionmaturing on 5/15/18 with a 3% coupon. There are also term bonds that will have thesame rate but different maturity dates that will all share the same CUSIP.



LCRA has an extensive debt structure of tax-exempt municipal debt (See LCRA DebtArchitecture example below). This debt structure includes ~$3.5B of debt that has beenissued through more than 400 CUSIPS. Each of these CUSIPS are issued by one of twoissuing entities (LCRA or TSC). The debt must be tracked beyond which entity issued thedebt but to which business unit originated the debt and to which asset area spent thedollars. The TMS must be able track these allocation percentages for each of the CUSIPSand be able to accept updated allocation percentages to ~400 CUSIPS via flat file. TMSshould be able to run a report based on individual business unit and bring back the debtwith associated with each unit.

3.6. LCRA Debt Architecture



Debt Architecture

Consolidated

LCRA

Business Unit

Sub-Business Unit

Asset total

Asset #1

Asset #2

Asset total

Asset #1

Asset #2

Sub-Business Unit

Asset #1

Asset #2

Business Unit

Sub-Business Unit

Asset #1

Asset #2

Sub-Business Unit

Asset #1

Asset #2

Business Unit

Business Unit

Transmission Services Corporation (TSC)

Business Unit

Sub-Business Unit

Asset #1

Asset #2

Sub-Business Unit

Asset #1

Asset #2

Business Unit

Sub-Business Unit

Asset #1

Asset #2



3.7. Forecast commercial paper and short-term debt usage –TMS must be able to tracklines by the amount of the line in use and the amount available. TMS should be ableto take variables for each credit facility and fees associated with each credit facility.Also, be able to report available liquidity of each credit facility individually and allcredit facilities in aggregate (commitment minus usage = available liquidity). TMSshould be able to accept data for forecast usage based on a flat file from LCRA’sbudgeting tool to future available liquidity.

3.8. Reporting:3.8.1. Below is a list of reports with the required reporting fields.

Cash Equivalents Report – Need current categories of Maturity based onpurchase (CE, >90, >365)

• Sec. ID

• Description

• Par

• Purchased Cost

• Sales/Maturities

• Ending Value

• Change in Fair Value

• Amortized in Period

• Ending Book Value

GASB 31 Report

• ID

• CUSIP

• Beginning Fair Value

• Original Par

• Original Cost

• Purchases

• Maturities

• Sales

• Calls

• Ending Fair Value

• Change in Fair Value

• Gain/Loss

• Period Purchased Interest

• Period Interest Earned

• Ending Accrued Interest

• Interest Paid in Period



Held with Tx Pool

• CUSIP

• Security ID

• Security type

• Par Value

• Purchase Cost

• Interest

• Book Value

• Market value

• Gain (Loss)

Safekeeping Reconciliation

• CUSIP

• Instrument type

• Par

• Portfolio ID

TopSub

• WAY

Debt Held Report

• CUSIP

• Security

• Settle Date

• Maturity Date

• Coupon

• Yield

• Par Value

• Purchase Cost

• Amort/Accr

• Interest

• BookValue

• Prem / (Disc)

• Market Value

• Gain/(Loss)

Debt Cost Report

• CUSIP

• Interest

• Period End



• Start Position

• Instrument ID

• Description

• Eff. Rate

• Maturity Date

• Int. Expense

• Amort./Accr.

• Redemption Cost

• Expense

• Paid

• Accrual

• Cash Flow

• Type (Premium, Discount, Neutral)

3.9. TMS should have the ability to create user generated ad-hoc reports. All attributes inside theTMS should be reportable by user. Throughout the project the Supplier is required to delivera monthly report to the LCRA Project Manager and Agent that includes but is not limited to:

• Narrative (to be provided in MS Word)o Prior period accomplishmentso Next period activitieso Risks / Issues / Resolution (proposed)o Schedule update and milestone status

• Budget Status (to be provided in MS Excel)o Report periodo Project name

• Task description Labor category assigned to task Hours expended (Period) Hours expended (Total to Date) Hours budgeted Billing rate for labor category (actual or calculated from presented information) Percent of Task Complete Estimated hours needed to complete task (actual or calculated from presented information) Projected variance from budget (hours and dollars) (actual or calculated from

presented information)

4. Dashboard/Reporting:



The solution must provide standard and configurable reports. *See exhibit tab

The solution must provide standard and configurable dashboards.

The solution must provide an audit trail of user activity.

The solution must be able to track and generate metrics.

Ad hoc reporting and analyses - create customized reports, graphs and charts *See Reportsformat tab.

Ability for multiple users to run reports from the same database at the same time.

Ability to export repots to PDF and excel

5. Integrations Required:

The solution must integrate with PeopleSoft 9.2 General Ledger for automated entries

US Bank custodian of Investments; reconcile with the custodian

JP Morgan Banking services; account balances, banking fees; ACH credit/debit, wires

Texpool / LOGIC money markets; track balances and daily rates

Pricing service for investments and debt; Bloomberg etc...

6. Accessibility/Single Sign-On

The solution must be able to provide single sign-on access to the system using Active Directory.

7. Administration

The solution must include administrator privileges.

The solution must allow multi-tenancy (i.e., one install, multiple administrators/severalgroups can access without seeing everyone's data).

The solution must provide user/group role-based permissions to access the system ordata within the system.

8. Data Migration:

Current TMS is RESIQ access database; historical data on debt and investments.

9. Project Schedule/Kickoff:



No. Deliverable

9.1

Schedule Management: The plan will describe how the schedule will bemonitored and the approaches to performance reporting that will be submittedto LCRA. The overall project schedule must be updated routinely andsufficiently detailed to provide insight into project status and task ownership.

9.2.0.Project Schedule: Project milestones to be achieved including deliverables,activities performed by LCRA and Supplier personnel outlining critical path,dependencies, work product, or outcome.

9.2.1Project Kickoff: Project kickoff meeting with LCRA sponsor(s), projectmanager, stakeholders, SMEs, technical leads to outline the project goals andapproach.

9.3. System Design: The supplier will be responsible for the system configurationdesign and documentation.

No. Deliverable

9.3.1

System Configuration Document: Document the design (as implemented) of thesystem. This document will outline how the system has been designed andconfigured, including Data Dictionary Customizations, Presentation (Screen)customizations, Business Object (Java) Customizations, Report Customizations,Workflow Automations, Integrations with 3rd party applications and LCRAbusiness process changes that were required. LCRA will use the System DesignDocument provided by the Supplier to develop functional and technicalspecifications.

9.4. Implementation: The supplier will install and configure the application based on thedefined requirements. Perform migrations from the Development environment to the TestEnvironment and from the Test Environment to the Production environment with usertesting, data validation and issue resolution after each move. The supplier will also performmigration of data from the current system.

No. Deliverables

9.4.1. Demo: Allows end users to explore the application with no customizations.



No. Deliverables

9.4.2.Development: Used to develop and configure objects before migrating into thetest environment for testing

9.4.3. Test: Used for all aspects of testing for objects from development environment

9.4.4.Training and Knowledge Transfer: Train SMEs and all other users on theapplication. Conduct knowledge transfer sessions (to be further defined in theSOW contract)

9.4.5. Production: Used for the actual production of the final solution

9.4.6. Conversion / Migration of data from Resource IQ

9.4.7. Migration from Development to Test

9.4.8.Migration from Test to Train (Level of effort to be determined in proposal andfinal contract SOW)

9.4.9. Migration from Test to Production

9.4.10. Final Go-Live Move to Production

9.4.11.

Provide the following deliverables, with assistance from LCRA as part of Supplier’sstandard construct phase technical upgrade methodology:

• Functional Design Documents

• Technical Design Documents

• Summary of Integration Changes

• Training material templates for a Upgrade

• Generic test cases for an Upgrade

• Configuration Documentation

10.0 LCRA Responsibilities: LCRA will have the following responsibilities for theimplementation of the new treasury and cash management system.

No. Responsibility

10.1. Create upgrade environments including OS, network and database.



10.2. Training: (LCRA level of effort to be determined in final contract SOW)

10.3.Backup Production: Replication of primary production environment that will actas fail over in the event the primary production environment is down.

10.4. Copy of Resource IQ production environment for reference purposes.

10.5. Validation of converted / migrated data

10.6.Migration from Test to Train (Level of effort will be determined in final contractSOW)

10.7. Implementation of SSO (single-sign on)

11. Testing: The Supplier will conduct migrations from Development to Test and fromTest to Production with user testing, data validation, and issue resolution after eachmove. Once the upgrade environments are built, the Supplier will work with LCRAto perform / support the below listed validation efforts.

No Deliverables

11.1

Quality Management Plan: Document the scope, approach, objectives, andschedule of the testing effort, including preparation of the testing instance(s) /environment(s) and categorization of defects and resolution approach. The planwill identify the items to be tested, the testing schedule, who will do the testing,and the pass/fail criteria for unit testing, performance, system integration testing,and user acceptance testing.

11.2

Test Schedule: Coordinate with LCRA to estimate how long it will take to completethe testing phase including the test milestones to be achieved and activitiesperformed by LCRA and Supplier personnel. (Level of Effort to be determined inproposal and final contract SOW)

11.3Test Scripts: Provide the generic scripts that will be used to test the systemfunctions as expected. LCRA to edit and supplement the scripts as necessary.

11.4Test Preparation: Coordinate with LCRA to ensure preparation of test participantsand LCRA test environment(s).

11.5Data Validation: Provide validation that all data converted properly. (Level ofEffort to be determined in proposal and final contract SOW)



No Deliverables

11.6Unit Testing: Complete unit testing of all retrofitted batch and onlinecustomizations.

11.7Acceptance Testing: Coordinate with LCRA to support full functional andacceptance testing to verify that the system functions as expected. (Level of Effortto be determined in proposal and final contract SOW)

11.8Performance/Load Testing: Provide support to LCRA for performance and loadtesting to verify that the new version and related hardware meets LCRAexpectations to support day-to-day operations.

11.9Integrations Testing: Coordinate with LCRA to perform and validate integrationstesting. (Level of Effort to be determined in proposal and final contract SOW)

LCRA’s Responsibilities: LCRA will have the following responsibilities for the testing phase.

No. Responsibility

11.10

Test Schedule: Coordinate with Supplier to estimate how long it will take tocomplete the testing phase including the test milestones to be achieved andactivities performed by LCRA and Supplier personnel. (Level of effort to bedetermined in final contract SOW)

11.12Data Validation: LCRA to confirm if data is accurately converted. (Level of effortto be determined in final contract SOW)

11.13Acceptance Testing: Coordinate with Supplier to support full functional andacceptance testing to verify that the system functions as expected. (Level of effortto be determined in final contract SOW)

11.14Integrations Testing: Coordinate with Supplier to perform and validateintegrations testing.

12.0. Training: The Supplier will provide a training plan, training materials, train LCRA’sdesignated SME staff members and complete the knowledge transfer.



No. Deliverables

12.1Training Materials: Provide any available documentation that containsinformation regarding changes between the current release and the new releases.

12.2System Administrator Training: Deliver system administrator training to systemadmins.

12.3 End-User Training: Deliver training to end users.

12.4

Knowledge Transfer: Provide knowledge transfer to LCRA designated personnelincluding SMEs and technical leads throughout the entire project. Knowledgetransfer will include business process, requirements, functional designs, technicaldesigns, issue logs, testing materials, train-the trainer materials and any projectmanagement details.

13.0. Production Deployment: During Go-Live Cutover, LCRA’s data will be migrated to thenew treasury system production environment. Once all issues from the implementationand data migration have been resolved, the new treasury system will be moved intoproduction. Once the technical upgrade is completed, LCRA’s functional leads and SMEwill finalize the tasks as outlined in the Cutover Plan. Finalization will include havingseveral application users access the treasury system, navigate through heavily usedpages, and submit some processes through the process scheduler. These activities willprovide the first indication as to the success of the upgrade, validate the integrity of thedata, and confirm that the treasury system is ready for use by LCRA's end usercommunity. The Supplier will provide the following:

ID Deliverables

13.1Go-live Readiness Assessment: Submit a final assessment that demonstrates allrequisite testing has been performed, the absence of any major defects, and thatall results are documented and workarounds have been accepted.

13.2

Cutover Plan: Document a Final Cutover Plan that outlines the tasks to becompleted prior to Go Live Cutover (i.e., Go-live Checklist). The Cutover Plan willoutline a comprehensive list of tasks to be completed for the Final Move toProduction, including timing of execution of such tasks and the Parties' respectiveresponsibilities with respect to each task.

13.3Post Go-Live Support: Provide post go-live support activities for sixty (60) daysto ensure all functions and transactions are happening properly. Additionalknowledge transfer/training occurs as required, any issues are being address,



ID Deliverables

major events (including monthly closing) are happening correctly. Complete thefollowing deliverables as part of the Supplier’s standard Deploy phase technicalupgrade methodology:

• Final Technical Training Documents

• Issue Resolution Summary

• Project Wrap Document (including location of all final project documents)

• Final Project Status Documentation

13.4

Final Solution Acceptance: Upon successful conclusion of the 60-day postproduction stabilization period and acceptance of all Supplier deliverables,Supplier will submit a memo to the Project Manager and Agent stating that theproduction solution and all requisite deliverables have been successfullydelivered to LCRA.

LCRA’s Responsibility: LCRA will have the following responsibilities for ProductionDeployment phase:

No. Responsibility

13.5Go Live Approval: LCRA to review the necessary information with the SteeringCommittee and provide approval to Supplier for the cutover to production.

13.6

Go-live Readiness Assessment: LCRA will produce a Go-Live ReadinessAssessment to document the results of an evaluation by the LCRA and theSupplier’s Project Manager to determine the readiness of LCRA’s staff and thesystem for Go Live Cutover and the final go-live decision. LCRA to validate that theassessment is complete.

13.7Final Solution Acceptance: LCRA will provide Written Solution Acceptance whichis the final verification activity in the project.

14.0. Project Schedule: The Supplier will provide a detailed and current project managementschedule to LCRA Project Management throughout the duration of the project.

The following schedule reflects target dates for the performance of the Services andDeliverables.



Milestone Target Start Date Target End Date %

Deliver Project Schedule TBD

Project Kick Off TBD

Implementation TBD

Testing TBD

Training (System Admins / SMEs /Trainers)

TBD

Final Go-Live Move to Production(Production Deployment)

TBD

Final Solution Acceptance TBD

15.0. Other Requirements:

15.1. Key Personnel: The Supplier will provide at a minimum, the below listed key resourcesand functions throughout the full lifecycle of this project. Should it become necessary toreplace any resources during the term of the project, LCRA expects the Supplier to provide areplacement with comparable or better skills.

Supplier is required to provide a background check for any employee or independentcontractor accessing LCRA IT systems. The background check must include acomprehensive criminal background check which includes a seven (7) yearfelony/misdemeanor search and felony criminal search in all counties/districts identifiedby the person’s social security number trace. Supplier must provide written confirmationon company letterhead that the background check was completed and on what date.

Role Responsibilities

Project Manager

Work with the LCRA Project Manager and lead the upgrade project,develop and manage the project plan, identify issues, assess risks, controlchange management, ensure communication, and monitor the progressof project tasks.

Functional Lead(s)

These resources should be subject matter experts in the treasuryapplications and perform the implementation tasks related toconfiguration and setup, perform Business Impact Analysis, assessbusiness process changes, translate functional requirements intotechnical specifications, perform testing, assist LCRA SMEs and provide



Role Responsibilities

knowledge transfer and create documentation. The resources will workon both project management and on the technology efforts and provideguidance on decisions.

Technical Team

Drive the technical effort and consult with the LCRA technical resources/ system admins to coordinate infrastructure setup and development,ensure alignment with system implementation recommendations andbest practices, demonstrate and perform the upgrade steps, and providetechnical help and expertise. Responsible for the technical design,development and testing of application configuration, customizationchanges, workflows, integrations, issue review, troubleshooting, impactanalysis.

Responsible for restoring all configurations, including the required forms,processes, integrations and reports, along with any other developmentand technical activities specific to the upgrade.

15.2. Other LCRA Responsibilities:

No. Responsibility

15.2.1LCRA will provide the Logical Architecture Diagrams that includedetails about LCRA’s current environment.

15.2.2LCRA’s Project Management will work with the Supplier regarding anyconflicts in the proposed schedule and LCRA’s Fiscal Year.

15.2.3LCRA will have the necessary ownership of system licenses for thisimplementation.

15.2.4

LCRA will acquire, install, configure and maintain an operational technicalinfrastructure with at least the minimum hardware and softwarerequired for installation and operation of system as defined by thesoftware vendor.

15.2.5

LCRA will implement any procedure(s) necessary to safeguard theintegrity and security of software and data used in this project fromaccess by unauthorized persons. The content of any data file, theselection and implementation of controls on its access and use, and thesecurity of stored data are the responsibility of LCRA.



16.0. Extended Support Services: The Supplier will provide pre-determined hourly rates forExtended Support Services for up to 80 hours beyond the Post Go-Live Support of 60 days.

17.0. Acceptance Criteria

17.1. Written acceptance of the Deliverables will be provided by the LCRA Agent.17.2. Any dispute by the Supplier regarding LCRA’s non-acceptance of a Deliverable

will be made within 10 business days after LCRA’s notice of non-acceptance.

18.0. LocationServices and Deliverables will be provided at LCRA’s General Office Complex (GOC), 3700Lake Austin Blvd, 78703; LCRA’s Dalchau Service Center Complex, 3505 Montopolis Dr.,78755 or remotely as agreed to by both parties.

19.0. Payment Schedule

For the Services and Deliverables to be provided hereunder, LCRA will pay the Supplier a firmfixed price per payment milestone in accordance with Exhibit A of this SOW. All work invoicedfor a given Deliverable must be completed and Accepted prior to the Supplier’s issuance ofan invoice.

For Extended Support Services to be provided hereunder, LCRA will pay the Supplier a fixedhourly rate per actual hours used in accordance with Exhibit B of this SOW.

20.0. Assumptions:

21.0. Supplier’s Key Person(s):

<<< List the names of specific employees of Supplier including project roles that arerequired to participate in the performance of the SOW. >>>

The following individuals are identified as Key Personnel for the delivery of services hereinand cannot be changed without prior written authorization from LCRA:

[Title/Role] [Name][Tel. No.][email]

[Title/Role] [Name][Tel. No.]



[email]

[Title/Role] [Name][Tel. No.][email]

22.0. Approval

The parties hereto have caused this Statement of Work to be executed by their respectiveduly authorized representatives, and this SOW is effective as of the date of the lastsignature below. Any changes to this SOW must be made in writing and signed by theSupplier and the LCRA Agent noted above or one appointed by LCRA Supply Managementwith appropriate delegation of authority.

Supplier Lower Colorado River Authority

By: By:

Printed Name: Printed Name:

Title: Title:

Date: Date:



EXHIBIT A – TIME AND MATERIAL PRICE NOT TO EXCEED

(See pricing tab in the Supplier Response Template)

Statement of Work for Treasury Management Implementation ...... · Statement of Work for Treasury...

Documents

Transcript of Statement of Work for Treasury Management Implementation ...... · Statement of Work for Treasury...