The URL can be used to link to this page

Home My WebLink About2016-03-22- 10:00AM REGULAR MEETINGBRAZOS COUNTY BRYAN,TEXAS NOTICE OF MEETING AND AGENDA BRAZOS COUNTY COMMISSIONERS COURT THE COMMISSIONERS COURT OF BRAZOS COUNTY WILL MEET IN REGULAR SESSION ON MARCH 22, 2016 AT 10:00 AM IN THE COMMISSIONERS COURTROOM OF THE COUNTY ADMINISTRATION BUILDING, 200 SOUTH TEXAS AVE., SUITE 106, BRYAN, TX 77803 Invocation and Pledge of Allegiance U.S. and Texas Flag - Chaplain G.H. Jones and Commissioner Cauley. 2. Call for Citizen input and/or concerns Consider and take action on agenda items 3-23: 3. Approval of Out of State Travel for Jail Administrator Wayne Dicky at attend the Large Jail Network in Aurora, Colorado; dates of travel are March 20-23, 2016. 4. Request from the Sheriffs Office for Out of State Travel for Investigator Terry Young to attend training in Maryland during the period of April 10-15, 2016. 5. Acceptance of Donated/Awarded Property Donation of unclaimed clothing and miscellaneous property left by inmates leaving the Brazos County Jail. 6. Approval of Final Judgment, Civil Action No. 4:15 -CV -00786. 7. Resolution 16-007 amending authorized representatives with Texpool. The Treasurers Office wishes to add Angie Beard as an authorized representative. 8. Approval of the following Job Descriptions: • a. Transition Training (Class Code 0213, Position 2) for County Judge • b. Sponsorship Coordinator (Class Code 0861, Position 1) for Exposition Complex • c. Administrative Service Manager (Class Code 1855, Position 1) for Juvenile Services 9. Request from the Information Technology Department to approve the contract for the TdTech Inform Records Management System. This new contract rescinds and replaces Ek 3 pg._/_--- the contract for the Tiburon Total Enforcement Records Management System approved in Commissioners Court on May 12, 2015. 10. Approval of contract with Steve Lovett or the appraisal of C. W. Henry tract, 123.6 acres of land located along Long Trussell Road at the Navasota River. 11. Approval of upgrade to the current Lexis Nexis subscription for the Law Library. This upgrade will only change the way patron are able to log into the site. 12. Award of bid # 2016-152 Equipment Lubricants. 13. Award of bid # 2016-153 Hydrated Lime. 14. Approval and award of contract for RFP # 2016-171 Installation of 8000 Gallon Vertical Storage Tanks per the recommendation of approved committee. 15. Renewal of bid contract #2016-173R for Truck Scale Maintenance with Fairbanks Scales. 16. Order No. 16-002 Approving the Installation of Traffic Control Signs on Harper's Ferry Road and a portion of Nantucket Drive. Site is located in Precinct 1. 17. The Final Plat of Indian Lakes Subdivision, Phase XXII (22); Lots 1-12, Block 33 & One Common Area; 27.830 Acres; J.M. Barrera Survey, A-69; (College Station ETJ) Brazos County, Texas. Site is located in Precinct 1. 18. Tax Refund Applications for the following: • a. Barry Grams -overpayment -$24.98 • b. Charles & Jodye Young -overpayment -$85.74 • c. Keith & Donna Moore -overpayment -$25.51 • d. Caren Cruse -overpayment -$3003.12 • e. Chris Martinez -overpayment -$310.00 • f. Kathryn Croft -overpayment -$21.19 • g. Roger Campbell -overpayment -$5.01 • h. A R Stone Investments -overpayment -$34.69 • i. City of Bryan -overpayment -$33.04 • j. Vicente Torres -overpayment -$7.02 • k. Baby Boomers -overpayment -$86.95 • I. Country Place Mortgage -overpayment -$172.37 • m. Russell Labus-overpayment-$15.07 • n. Steinmeyer Properties -overpayment -$106.05 • o. Jes & Mary Linne-overpayment-$2281.37 • p. Anseth Richards -overpayment -$50.00 • q. Teserra Venture LP -overpayment -$143.00 • r. William Wylie PLLC-overpayment-$50.88 • s. Wendell Stanford -overpayment -$30.73 • t. Festive Homes -overpayment -$51.53 19. Budget Amendments. Budget Amendments FY 15/16 26.1 - 26.10 20. Personnel Change of Status. Personnel Action Forms 21. Payment of Claims. Vol. A23 -q Pg...? 22. Convene into Executive Session pursuant to Texas Government Code 551.0785 for deliberations involving medical or psychiatric records of a county employee and Texas Government Code 551.074 to discuss personnel matters. 23. Consider and possible action on executive session. 24. Sheriffs report on inmate population. 25. Announcement of interest items and possible future agenda topics. 26. Call for Citizen input and/or concerns 27. Adjourn. Vol. 2.Tel pg._,j — PUBLIC COMMENTS Public Comment during the Commission Meeting may be for all matters, both on and off the agenda, and be limited to four minutes per person. Persons are invited to subMt comments in writing on the agenda items and/or attend and make comment at the Commission meeting. Members of the public are reminded that the Brazos County Commissioners Court is a Constitutional Court, with both Judicial and Legislative powers, created under Article V, Section 1 and Section 18 of the Texas Constitution. As a Constitutional Court, the Brazos County Commissioners Court also possesses the power to issue a Contempt of Court Citation under Section 81.024 of the Texas Local Government Code. Accordingly, members of the public in attendance at any Regular, Special and/or Emergency meeting of the Court shall conduct themselves with proper respect and decorum in speaking to, and/or addressing the Court; in participating In public discussions before the Court; and in all actions In the presence of the Court. Those members of the public who are inappropriately attired and/or who do not conduct themselves in an orderly and appropriate manner will be ordered to leave the meeting. Refusal to abide by the Court's Order and/or continued disruption of the meeting may result in a Contempt of Court Citation. it is not the intention of the Brazes County Commissioners Court to provide a public forum for the demeaning of any individual or group. Neither is It the intention of the Court to allow a member (or members) of the public to insult the honesty and/or integrity of the Court, as a body, or any member or members of the Court, or County employees, individually or collectively. Accordingly, profane, insulting or threatening language directed toward the Court and/or any person in the Court's presence and/or racial, ethnic or gender slurs or epithets will not be tolerated. Violation of these rules may result in the following sanctions: 1. cancellation of a speaker's time; 2. removal from the Commissioners Court; 3. a Contempt Citation; and/or 4. such other and/or criminal sanctions as may be authorized under the Constitution, Statutes and Codes of the State of Texas. The County Connrissioners Court can deliberate or take action only If a matter has been listed on an agenda properly posted prier to the meeting. During the public comment period, speakers may address matters not listed on the published agenda. The Open Meeting Law does not exrpressly prohibit responses to public comments by the Commissioners Court. However, responses from the County Judge or Commissioners to unlisted public comment topics could become deliberation on a matter tdthout notice to the public. To ensure the public has notice of all matters the Commissioners Court will consider, the County Judge and/or Commissioners may choose not to respond to public comments, except to correct factual inaccuracies, recite existing policy In response to an Inquiry or to ask that a matter be listed on a future agenda. See Texas Open Meetings Act ?551.042. INVOCATION Any Invocation that may be offered before the official start of the Court meeting shall be to and for the benefit of the Court. The views or beliefs expressed by the invocation speaker have not been previously reviewed or approved by the Court and do not necessarily represent the religious beliefs or views of the Court in part or as a whole. No member of the community is required to attend or participate in the invocation and such decision will have no impact on their right to actively participate in the business of the Court. The Commissioners Courtroom of the County Administration Building, 200 South Texas Ave., Suite 106, Bryan, TX77803 is wheelchair accessible. Handicap parking spaces are available. Any request for sign interpretive services must be made two working days before the meeting. To make arrangements, please call (979) 361-4102. Vol. _.� P9•-- MINUTES MARCH 22, 2016 BRAZOS COUNTY COMMISSIONERS COURT REGULAR MEETING A regular meeting of the Commissioners' Court of Brazos County, Texas was held in the Brazos County Commissioners Courtroom in the Administration Building, 200 South Texas Avenue, in Bryan, Brazos County, Texas, beginning at 10:00 a.m. on Tuesday, March 22, 2016 with the following members of the Court present: Duane Peters, County Judge, Presiding; Lloyd Wassermann, Commissioner of Precinct 1; Sammy Catalena, Commissioner of Precinct 2; Kenny Mallard, Commissioner of Precinct 3; Irma Cauley, Commissioner of Precinct 4; Karen McQueen, County Clerk. The attached sheets contain the names of the citizens and officials that were in attendance. Invocation and Pledge of Allegiance U.S. and Texas Flag - Chaplain G.H. Jones and Commissioner Cauley. 2. Call for Citizen input and/or concerns There was no citizen's input. Consider and take action on agenda items 3-23: 3. Approval of Out of State Travel for Jail Administrator Wayne Dicky at attend the Large Jail Network in Aurora, Colorado; dates of travel are March 20-23, 2016. Vol. pg._4 Motion: Approve, Moved by Commissioner Irma Cauley, Seconded by Commissioner LLoyd Wassermann. Passed. 5-0. Members voting Ayes: Catalena, Cauley, Mallard, Peters, Wassermann Request from the Sheriff's Office for Out of State Travel for Investigator Terry Young to attend training in Maryland during the period of April 10-15, 2016. Motion: Approve, Moved by Commissioner LLoyd Wassermann, Seconded by Commissioner Irma Cauley. Passed. 5-0. Members voting Ayes: Catalena, Cauley, Mallard, Peters, Wassermann 5. Acceptance of Donated/Awarded Property Donation of unclaimed clothing and miscellaneous property left by inmates leaving the Brazos County Jail. Motion: Approve, Moved by Commissioner Irma Cauley, Seconded by Commissioner Kenny Mallard. Passed. 5-0. Members voting Ayes: Catalena, Cauley, Mallard, Peters, Wassermann 6. Approval of Final Judgment, Civil Action No. 4:15 -CV -00786. Motion: Approve, Moved by Commissioner Sammy Catalena, Seconded by Commissioner Irma Cauley. Passed. 5-0. Members voting Ayes: Catalena, Cauley, Mallard, Peters, Wassermann Resolution 16-007 amending authorized representatives with Texpool. The Treasurer's Office wishes to add Angie Beard as an authorized representative. A copy is attached. Motion: Approve, Moved by Commissioner Sammy Catalena, Seconded by Commissioner Kenny Mallard. Passed. 5-0. Members voting Ayes: Catalena, Cauley, Mallard, Peters, Wassermann 8. Approval of the following Job Descriptions: • a. Transition Training (Class Code 0213, Position 2) for County Judge • b. Sponsorship Coordinator (Class Code 0861, Position 1) for Exposition Complex • c. Administrative Service Manager (Class Code 1855, Position 1) for Juvenile Services Judge Peters stated that job description "b" has been removed. A motion was made by Commissioner Wassermann to approve job descriptions "a" and "c". The motion was seconded by Commissioner Catalena and passed unanimously. Vol. _a_ Pg. A copy of the job descriptions is attached. Motion: Approve, Moved by Commissioner LLoyd Wassermann, Seconded by Commissioner Sammy Catalena. Passed. 5-0. Members voting Ayes: Catalena, Cauley, Mallard, Peters, Wassermann 9. Request from the Information Technology Department to approve the contract for the TriTech Inform Records Management System. This new contract rescinds and replaces the contract for the Tiburon Total Enforcement Records Management System approved in Commissioners Court on May 12, 2015. Information Technology Director Eric Caldwell gave an update on this new software. Mr. Caldwell stated that the new Justice software does not include a Records Management System, so there will be a delay once the software is installed. He went on to explain that he has met with the departments that will be affected by this lapse, and have come up with ideas on how to handle this until a Records Management System can be added. Mr. Caldwell also said that the new Records Management System will have some additional functions that will be beneficial to those departments using the new system. A copy of the contract is attached. Motion: Approve, Moved by Commissioner Irma Cauley, Seconded by Commissioner Sammy Catalena. Passed. 5-0. Members voting Ayes: Catalena, Cauley, Mallard, Peters, Wassermann 10. Approval of contract with Steve Lovett or the appraisal of C. W. Henry tract, 123.6 acres of land located along Long Trussell Road at the Navasota River. A copy of the contract is attached. Motion: Approve, Moved by Commissioner Sammy Catalena, Seconded by Commissioner -Loyd Wassermann. Passed. 5-0. Members voting Ayes: Catalena, Cauley, Mallard, Peters, Wassermann 11. Approval of upgrade to the current Lexis Nexis subscription for the Law Library. This upgrade will only change the way patron are able to log into the site. A copy of the contract is attached. Motion: Approve, Moved by Commissioner Sammy Catalena, Seconded by Commissioner Kenny Mallard. Passed. 5-0. Members voting Ayes: Catalena, Cauley, Mallard, Peters, Wassermann 12. Award of bid # 2016-152 Equipment Lubricants. Bid #2016-152 Equipment Lubricants was awarded to Universal Lubricants. A copy of the bid tabulation is attached. Vol. —4J P9. Motion: Approve, Moved by Commissioner LLoyd Wassermann, Seconded by Commissioner Sammy Catalena. Passed. 5-0. Members voting Ayes: Catalena, Cauley, Mallard, Peters, Wassermann 13. Award of bid # 2016-153 Hydrated Lime. Bid #2016-153 Hydrated Lime was awarded to Austin White Lime. A copy of the bid tabulation is attached. 14. Approval and award of contract for RFP # 2016-171 Installation of 8000 Gallon Vertical Storage Tanks per the recommendation of approved committee. Contract RFP #2016-171 Installation of 8000 Gallon Vertical Storage Tanks was awarded to Madison Construction. A copy of the bid tabulation is attached. Motion: Approve, Moved by Commissioner Sammy Catalena, Seconded by Commissioner -Loyd Wassermann. Passed. 5-0. Members voting Ayes: Catalena, Cauley, Mallard, Peters, Wassermann 15. Renewal of bid contract #2016-173R for Truck Scale Maintenance with Fairbanks Scales. A copy of the renewal of contract and bid tabulation for #2016-173R Truck Scale Maintenance is attached. Motion: Approve, Moved by Commissioner Kenny Mallard, Seconded by Commissioner Irma Cauley. Passed. 5-0. Members voting Ayes: Catalena, Cauley, Mallard, Peters, Wassermann 16. Order No. 16-002 Approving the Installation of Traffic Control Signs on Harper's Ferry Road and a portion of Nantucket Drive. Site is located in Precinct 1. County Auditor Katie Butler questioned the County's authority to pay for and post the signs. Civil Counsel Bill Ballard stated that the subdivision Home Owner's Association could purchase the signs and the County could agree to post them. Judge Peters questioned who would be able to enforce the signs if the County agreed to put them up. Judge Peters said he would like to have more information before voting. Marie Wolfe, who is a resident of the Nantucket subdivision said that she would like for the County to consider putting up the signs for the safety of the residents of Nantucket. She also said that she believes the HOA will pay for the signs. Ms. Wolfe stated that there are safety issues with large dump trucks and 18 -wheelers cutting through the Nantucket subdivision to get to the new development in the Indian Lakes subdivision. She stated that a number of children are in the area where these trucks are traveling. County Engineer Alan Munger stated that he has the Attorney General's opinion on this that will allow the County to post the signs. Vol, _,Z j� Pg. Ms. Wolfe asked the cost of the signs. Commissioner Wassermann said that the Road and Bridge Department could give Ms. Wolfe the amount for the signs. Commissioner Wassermann stated that the residents of Nantucket are experiencing a real safety hazard and would like to move forward. He said that he thought all of the questions on this had already been addressed. Commissioner Wassermann commented that the County has previously put up signs for Precinct 4. He said that this is a serious situation for the residents of Nantucket and he does not want it to be tabled. After the discussion a motion to rescind the approval was made and a new motion was offered by Commissioner Catalena to table this item. The motion was seconded by Commissioner Cauley and passed. Commissioner Wassermann voted against the motion to table. Motion: Table, Moved by Commissioner Sammy Catalena, Seconded by Commissioner Irma Cauley. Passed. 4-1. Members voting Ayes: Catalena, Cauley, Mallard, Peters Members voting Nays: Wassermann 17. The Final Plat of Indian Lakes Subdivision, Phase XXI1 (22); Lots 1-12, Block 33 & One Common Area; 27.830 Acres; J.M. Barrera Survey, A-69; (College Station ETJ) Brazos County, Texas. Site is located in Precinct 1. Marie Wolfe, who is a resident of the Nantucket subdivision asked that the Court not approve the plat. She stated that every time a new plat is approved it increases traffic for the residents of Nantucket. Ms. Wolfe asked the Court to reject this and any other plat for the Indian Lakes subdivision until a second entrance/exit is added and Mesa Verde is extended. She said there are already four hundred (400) homes in the Indian Lakes subdivision. She also stated her concerns for the safety of the residents who have only one way in and one way out of the subdivision. Judge Peters said that the Court does not have the authority to reject a plat on those terms. He said that if the developer has met all engineering standards and requirements, they do not have a legal reason to reject it. He stated that it would put a liability on Brazos County. Commissioner Wassermann commented that this is in the ETJ of College Station. He said that once College Station approves it, the County does not have the authority to reject it. Commissioner Wassermann went on to say that there will be a meeting on Wednesday, March 23, 2016 at 3:30 p.m. with the College Station City Manager and Engineer to address this situation. Motion: Approve, Moved by Commissioner LLoyd Wassermann, Seconded by Commissioner Sammy Catalena. Passed. 5-0. Members voting Ayes: Catalena, Cauley, Mallard, Peters, Wassermann 18. Tax Refund Applications for the following: • a. Barry Grams -overpayment -$24.98 Vol. _.�- �'9•_F • b. Charles & Jodye Young -overpayment -$85.74 • c. Keith & Donna Moore -overpayment -$25.51 • d. Caren Cruse -overpayment -$3003.12 • e. Chris Martinez -overpayment -$310.00 • f. Kathryn Croft -overpayment -$21.19 • g. Roger Campbell -overpayment -$5.01 • h. A R Stone Investments -overpayment -$34.69 • i. City of Bryan -overpayment -$33.04 • j. Vicente Torres -overpayment -$7.02 • k. Baby Boomers -overpayment -$86.95 • I. Country Place Mortgage -overpayment -$172.37 • m.• Russell Labus-overpayment-$15.07 • n. Steinmeyer Properties -overpayment -$106.05 • o. Jes & Mary Linne-overpayment-$2281.37 • p. Anseth Richards -overpayment -$50.00 • q. Teserra Venture LP -overpayment -$143.00 • r. William Wylie PLLC-overpayment-$50.88 • s. Wendell Stanford -overpayment -$30.73 • t. Festive Homes -overpayment -$51.53 Motion: Approve, Moved by Commissioner Irma Cauley, Seconded by Commissioner Sammy Catalena. Passed. 5-0. Members voting Ayes: Catalena, Cauley, Mallard, Peters, Wassermann 19. Budget Amendments. Budget Amendments FY 15/16 26.1 -26.10 26.1 Reallocate funds for Law Enforcement Officers Standards and Education. 26.2 Reallocate funds for General Capital Projects - Juvenile Services. 26.3 Reallocate funds for General Capital Projects - Sheriff's Office. 26.4 Reallocate funds for General Capital Projects - Brazos Center. 26.5 Reallocate funds for General Capital Projects - Information Technology Services 26.6 Transfer of funds from General Fund Contingency to Information Technology Services. 26.7 Transfer of funds from General Capital Projects to Constable, Precinct 4. 26.8 Transfer of funds from Road and Bridge to Greens Prairie Trail Project. 26.9 Reallocate funds for Sheriff's Office -Administration. 26.10 Reallocate funds for Justice of the Peace, Precinct 4. Motion: Approve, Moved by Commissioner Sammy Catalena, Seconded by Commissioner Kenny Mallard. Passed. 5-0. Members voting Ayes: Catalena, Cauley, Mallard, Peters, Wassermann 20. Personnel Change of Status. Personnel Action Forms Vol.Pg /� A copy of the Personnel Change of Status requests is attached. Motion: Approve, Moved by Commissioner Irma Cauley, Seconded by Commissioner LLoyd Wassermann. Passed. 5-0. Members voting Ayes: Catalena, Cauley, Mallard, Peters, Wassermann 21. Payment of Claims. Claims 7142608-7142824 Motion: Approve, Moved by Commissioner Sammy Catalena, Seconded by Commissioner Kenny Mallard. Passed. 5-0. Members voting Ayes: Catalena, Cauley, Mallard, Peters, Wassermann 22. Convene into Executive Session pursuant to Texas Government Code 551.0785 for deliberations involving medical or psychiatric records of a county employee and Texas Government Code 551.074 to discuss personnel matters. At this point, the County Judge announced the Court would consider items 24 through 26 then return to convene into Executive Session. Having considered the previously noted agenda items, at 10:42 a.m. the County Judge stated that the Court would convene into Executive Session to deliberate pursuant to Section 551.0785 and Section 551.074 as stated above. The following individuals were asked to stay for the meeting: Candy Gallego, Executive Assistant Bill Ballard, Civil Counsel Kendra Suhling, Civil Counsel Jennifer Salazar, Human Resources Director Laura Davis, County Treasurer Katie Butler, County Auditor Amy Bates, Auditor's Office 23. Consider and possible action on executive session. At 10:55 a.m. the County Judge announced the meeting open to the public and on motion by the County Judge, seconded by Commissioner Catalena, the Court voted to deny variance to the policy for a certain employee to go negative on vacation time while on FMLA. Motion: Deny, Moved by County Judge Duane Peters, Seconded by Commissioner Sammy Catalena. Passed. 5-0. Members voting Ayes: Catalena, Cauley, Mallard, Peters, Wassermann 24. Sheriff's report on inmate population. Vol. �,� Pg. —�-�-- Sheriff Chris Kirk stated there were 583 inmates in jail, 43 have electronic monitors and 14 are pending for monitors. 25. Announcement of interest items and possible future agenda topics. There were no announcements. 26. Call for Citizen input and/or concerns There was no citizen's input. 27. Adjourn. vol. ��Sl pg. �� The foregoing minutes of the Commissioners Court meeting held March 22, 2016 have been examined and are approved in open Court this J* day of County Judge &, eAf- Irma Cauley Commissioner, Precinct 4 Attest: gw,( e ` Karen McQueen County Clerk Brazos County, Texas. Lloyd VAssermarm Commissioner, Precinct 1 Kenny Mallar Commissioner, Precinct 3 Dp I C)f /- BRAZOS COUNTY COMMISSIONER'S COURT DAY OF ` 2j:g z L , 24/ Name PRNT) /V 40 iV c �A-, LZ5c)-i/ f-0 is Organization (PLE_5.�E PRD,T) pzx S &I'Yt I . n • vo L olv"� 6i'1� BRAZOS COUNTY COMMISSIONER'S COURT Name (PLEASE PRLNTT) 20/-a_ Organization (PLEASE PRLN'T) SvSci )4ctFc-1rk �( I I A)Av '-h4 C.(6?, � 1q =pg,-4�c- Please use this form to amend or designate Authorized Representatives. This document supersedes all prior Authorized Representative forms. Required Fields 1. Resolution Resolution Amending Authorized Representatives WHEREAS, (Brazos County 1 17 17 11 17171 Panieipanl Name' Location Number' ("Participant") is a local government of the State of Texas and is empowered to delegate to a public funds investment pool the authority to invest funds and to act as custodian of investments purchased with local investment funds; and WHEREAS, it is in the best interest of the Participant to invest local funds in investments that provide for the preservation and safety of principal, liquidity, and yield consistent with the Public Funds Investment Act; and WHEREAS, the Texas Local Government Investment Pool ('TexPooll Texpool Prime'), a public funds investment pool, were created on behalf of entities whose investment objective in order of priority are preservation and safety of principal, liquidity, and yield consistent with the Public Funds Investment Act. NOW THEREFORE, be it resolved as follows: A. That the Individuals, whose signatures appear in this Resolution, are Authorized Representatives of the Participant and are each hereby authorized to transmit funds for investment in TexPool / TexPool Prime and are each further authorized to withdraw funds from time to time, to issue letters of instruction, and to take all other actions deemed necessary or appropriate for the Investment of local funds. B. That an Authorized Representative of the Participant may be deleted by a written instrument signed by two remaining Authorized Representatives provided that the deleted Authorized Representative (1) is assigned job duties that no longer require access to the Participant's TexPool / TexPool Prime account or (2) is no longer employed by the Participant; and C. That the Participant may by Amending Resolution signed by the Participant add an Authorized Representative provided the additional Authorized Representative is an officer, employee, or agent of the Participant; List the Authorized Representative(s) of the Participant. Any new individuals will be issued personal identification numbers to transact business with TexPool Participant Services. (Laura Taylor -Davis I Name (Brazos County Treasurer Title 2 Terri White Name Chief Deputy Treasurer The Vol. _�•� S� Pg, � ` _ t 1. Resolution (continoed) - - Angie- r Varre Brazos County Assistant Chief Deputy Treasurer Title 979-361-4542 / 979-361-4347 / abeard@brazoscountytx.gov 4.1 Name I rlle I PhonelFaxlEmal Signature List the name of the Authorized Representative listed above that will have primary responsibility for performing transactions and receiving confirmations and monthly statements under the Participation Agreement. Terri White I Name In addition and at the option of the Participant, one additional Authorized Representative can be designated to perform only inquiry of selected information. This limited representative cannot perform transactions. If the Participant desires to designate a representative with inquiry rights only, complete the following information. Name The PhonelFax/Email D. That this Resolution and its authorization shall continue in full force and effect until amended or revoked by the Participant, and until TexPool Participant Services receives a copy of any such amendment or revocation. This Resolution is hereby introduced and adapted by the Participant at its regular/special meeting held on the 22 day March . 20 16 Note: Document is to be signed by your Board President, Mayor or County Judge and attested by your Board Secretary, City Secretary or County Clerk. Duane Peters lKaren McQueen Pnnted Name' Printed Name' (Brazos County Judge lBrazos County Clerk Title' Title 12. Mailing Instructions The completed Resolution Amending Authorized Representatives can be faxed to TexPool Participant Services at 1-866-839-3291, and mailed to: TexPool Participant Services 1001 Texas Avenue, Suite 1400 Houston, TX 77002 ORIGINAL SIGNATURE AND DOCUMENT REQUIRED TEX-REP 2 OF 2 T PoolPudcipantServices Mamtgd od Federated® 1001 Tr a Avenue, Suite 1400 • Houston, TX 77002 Serviced by Pbunc b866T11XPOOL(839-0665) • Fax: 1-866839-3291 • www.mxpooLcom 04534617(12/15) Vol. pg.—/ --Z— Cj �� `'21 T 3M .� ` F ;�ti�'� '��;�"i Brazos County isa �y�)H Job Description °w�° Last Updated: September 2012 Tanp:ato Roneion 1.208115 012 Poo, a Class Number: 213 Title: Transition Training Pay Group: 17 Department: County Judge ELSA Status: Non Exempt Reports To: County Judge Approved Date: -- - 10101!2013 -- ----- EEOC Category: Office and Clerical -Temporary -- -------- � ti �. wPosition End Date: 09!3012014 Employee Signature: -- - ---- - .._ Supervision - - -- Received: County Judge �--� Given: This Is a non -supervisory posilion. Education_ Required: Preferred: Certificates, Licenses, Registrations Required_ None. -— Preferred: — ----- ----------- r OL_.2-� ti pg. / Fla Knowledge, Skills, & Abilities Eyol:—"— A OV�D %P Duane Peters Date County Judge Brazos County Job Description Last Updated: March 22, 2016 Class Number: 1856 Title: ! Administrative Services Manager Pay Group: 122 I Department: I Juvenile Administration FLSA Status: I Exempt I Reports To: I Assistant Director Approved Date: Pending EEOC Category: I Administrative Support Template Revision 1.2 08It 512012 General Summary: erves as chierfiscal officer for the Juvenile Services Department, including supervision of support services to ensure the delivery of efficient ! secretarial, clerical, purchasing, budget and human resource services to the department. Manages departmental budget in relation to expenditures and ensures compliance with county procurement policies and procedures. Essential Duties: t_.. --------------l. Pre -------- --- -- ----zati 1 I Provide leadership and supervision for assigned clerical and secretarial personnel. Prepare departmental requisitions and payment authorizations for I I the Director's or Assistant Directors signature or approval. Obtain necessary bids for products and services. Prepare department's financial reports , and general fund reports. Assist in the preparation of department's fiscal budget. Prepare budgetary projections and cost analysis per line item I expenditures and capital assets. Prepare and distribute employee I.D. cards. Order and maintain the department's office supplies. Maintain all departments' accounts and bookkeeping. Assist with agenda items for Commissioners Court and oversee the preparation for Juvenile Board meeting packets and logistics. Prepare personnel action forms for submittal to the Commissioners Court and handle all duties relating to the human resource actions for new employees, terminations and/or resignations. Provides final approval of all departmental staff time sheets on bi-weekly basis; ensuring accurate recording of FMLA, comp, workers compensation, sick and vacation time. Monitor expenditures from all grant accounts to ensure compliance. Ensure the proper inventory of detention items needed for youth, including appropriate ordering of clothes, hygiene and detention supplies. Provides oversight for the National School Breakfast and Lunch Program (NSLP) claims submitted on a monthly basis; ensuring county is reimbursed fully and accurately. Write, develop, and update policies and procedures for all fiscal and secretarial operations as needed. Perform and submit bi-annual and annual evaluations on staff Be a member of the department audit team and assist in preparing for yearly detention, probation, JJAEP, PREA, and various fiscal audits. Follow established policies, procedures and practices of the department. Provide staff training as appropriate. Research best practices, new technologies, and national best practice trends regarding juvenile justice issues. Abide by the Texas Juvenile Justice Department's Code of Ethics. Maintain security and confidentiality of all case information, files and chronological notes as required by the Texas Family Code. The duties listed above are intended only as Illustrations of the various types of work that may be ! performed. The omission of specific statements of duties does not exclude them from the position if the work is related or a logical assignment to the Lmsition._Obtain. 80_ hours_bi-annually of -approved trainina.to—maintain_JPO and_JSO certification. Other_duties.mav_be_assioned as_deemed Other Duties as assigned. (1%) __ - --- Supervision Received: Assistant Director i j Given- This position directly supervises clerical staff assigned to the unit. This includes training of new staff, I conducting performance reviews, and recommending personnel actions. Conduct regular staff meetings regarding policies, procedures, problem salving, program planning, and in-service training. Review and i approve time sheets and time off requests. Education Required: Bachelors degree and at least five (5) years responsible secretarial, bookkeeping, adirnimi strative and management experience. Preferred: Certificates, Licenses, Registrations___ Required: To penorm this lob successfully, an Individual must be able to perorm earn essential duty salistactorlly. I be requirements listed below are representative of the knowledge, skill, and/or ability required. Reasonable accommodations may be made to enable individuals to perform the essential functions. Must be 21 years of age or older Notary public and surety bond. Valid Texas drivers license with appropriate liability auto insurance coverage (Drivers license requirements must be met within 30 days if employee recently moved from another slate). vol. Zj5/ pg.�e Preferred: Physical Demands Typical: I Knowledge, Skills, & Abilities I Duties require daily standing, walking, sitting, talking and listening; frequent use of hands and/or fingers to grasp, handle, pick-up, pinch, type or feel; frequent reaching with hands or arms and lifting of objects over 20 pounds; close vision, distance vision, ability to distinguish color, peripheral vision, depth perception and ability to adjust focus. Physical demands described here are representative of those that must be met or are encountered by an employee to successfully perform the essential functions of this job. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions. Typical: Advanced computer knowledge and competence (word, excel, etc.). Knowledge of and ability to apply correct l business English, spelling, and math; and, ability to communicate effectively orally and in writing. Ability to type. Ability to establish and maintain effective working relationships with other employees, organizations and the general public. Work Environ_m_e_n_t i Typical: I The noise level in the work environment is usually moderate. While performing the essential duties of this job, the employee is constantly required to perform multiple tasks simultaneously, to work under time pressures to meet deadlines and to work closely with others as part of a team; the employee is frequently required to do tedious exacting work. Worker is subject to physical hazards from traffic; serious hazard and infection from exposure to communicable disease; physical harm as the result of confrontation. The work environment characteristics described here are representative of those an employee encounters while performing the essential functions of this job. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions. 3 Duane Peters Date County Judge STATEMENT OF WORK City of Bryan, Texas Version 1.0 TnTech Software Systems 9477 Waples Street, Suite 100 San Diego, CA 92121 Fax: 858.799.1010 Technical Services: 1.888.VISI.CAD (847.4223) TRITECH SOFTWARE SYSTEMS Vol. —g'g f Pg. ,Z -Z C 2003-2015 TriTech Software Systems Unpublished: Rights resened under the copyright laws of the United States. All information in this document is proprietary and confidential and owned by TriTech Software Systems"'. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of TriTech Software Systems. Trademarks Microsoft, Windows, Microsoft Access, Microsoft Excel, Microsoft Exchange, and Nticrosoft Word are either registered trademarks or trademarks of Microsoft Corporation in the United States and other countries. Inform CAD, Inform Mobile, Inform CAD Browser, Inform RMS, Inform Jail, TriTech.com IQ, TriTech.com Analytics, Inform FBR, and Inform CAD GISLink are trademarks of TriTech Software Systems. ArcGIS, ArcMap and ArcCatalog are registered trademarks of Environmental Systems Research Institute (ESRI) in the United States and other countries. Document Control Date Version Details/Changes Author October 8, 2015 1M SOW Template The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to -others -without the prior written consent of TriTech Software 5 Systems. 02015 TriTech Softar we Systems Vol. ofj!T1 jig, �� Table of Contents DocumentControl.................................................................................................................... ii Tableof Contents.....................................................................................................................iii 16 1 Overview............................................................................................................................. 1 1.1 Statement of Work.........................................................................................................................................1 17 1.2 Project Implementation Definitions...............................................................................................................1 17 1.3 System Acceptance Process..........................................................................................................................2 ..... ................ ............................ ...... 18 1.3.1 Functional Acceptance Testing..............................................................................................................2 1.3.2 Integration Testing.................................................................................................................................2 1.4 General Client Responsibilities......................................................................................................................3 1.5 Project Exclus ions .........................................................................................................................................4 2 Project Deliverables........................................................................................................... 5 2.1 Overview of Project Deliverables ..................................................................................................................5 3 TriTech Project Roles and Responsibility........................................................................ 6 3.1 Overview.......................................................................................................................................................6 3.2 TriTech Project Manager...............................................................................................................................6 3.3 Systems Engineer...........................................................................................................................................7 3.4 GIS Analyst...................................................................................................................................................7 3.5 Inform RNIS Business Analyst......................................................................................................................7 3.6 Training Specialist.........................................................................................................................................7 3.7 Client Installation Services Team..................................................................................................................7 3.8 Technical Services Group..............................................................................................................................8 3.9 Account Executive... ...................................................................................................................................... 8 4 Recommended Client Roles and Responsibilities........................................................... 9 4.1 Overview.....................................................................................................................................................:.9 4.2 Project Manager.............................................................................................................................................9 4.3 System Administrator....................................................................................................................................9 4.4 Inform RMS Administrator......................................................................................................................... 10 4.5 GIS Analyst.................................................................................................................................................10 4.6 Inform RMS/ and FBR Users/Supervisors..................................................................._............................. 11 4.7 Subject Matter Experts................................................................................................................................. 11 4.8 Application Trainers.................................................................................................................................... 11 Project Controlling Processes ................................... 5.1 Overview.................................................................................. 5.1.1 TriTech Responsibilities................................................... 5.1.2 Client Responsibilities..................................................... 5.2 Change Management Process .................................................. 5.2.1 TriTcch Responsibilities.................................................. 5.2.2 Client Responsibilities..................................................... 5.3 Project Reporting..................................................................... 5.3.1 TriTech Responsibilities.................................................. 5.3.2 Client Responsibilities..................................................... 5.4 Document Review................................................................... 542 T'T 1 R 'lift' ........................................12 ................................................... 12 ...................................................13 ...................................................13 .. rt ec r esponst n t tes......................................................................................................................... 5.4.3 Client Responsibilities......................................................................................................................... 16 6 Project Initiation and Planning.........................................................................................17 6.1 Overview..................................................................................................................................................... 17 6.1.1 TriTech Responsibilities................................................................................_.................................... 17 6.1.2 Project Kick Off.............................................. ......... ..................... ..... ................ ............................ ...... 18 7 Project Execution..............................................................................................................19 The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems. 02015 TriTech Software Systems Vol. pg, .� �' 7.1 Overview..................................................................................................................................................... 19 7.2 System Installation (Inform RNIS and Interfaces)....................................................................................... 19 7.2.1 Review Hardware Specifications......................................................................................................... 19 7.2 .2 Hardware and Equipment Procurement Process.................................................................................. 19 7.2.3 hardware Staging and Preparation for Installation..............................................................................20 7.2.4 TriTech Responsibilities......................................................................................................................20 7.2.5 Basic Server preparation and Network Services..................................................................................21 7.2.6 System Installation...............................................................................................................................22 7.3 Implementation of Inform RMS..................................................................................................................24 7.3.1 Inform RNIS System Orientation.........................................................................................................24 7.3.2 Inform RMS Base System Code File Entry .........................................................................................26 7.3.3 Inform RNIS Administration and Review Training.............................................................................26 7.3.4 Inform RMS Demonstration of Licensed Functionality (DOLF)........................................................27 7.3.5 Inform RNISWorkshop.......................................................................................................................28 7.3.6 Inform RMS Functional Acceptance Testing (FAT)...........................................................................29 7.3.7 Inform RMS Training..........................................................................................................................30 7.3.8 Inform RNIS Integration Testing.........................................................................................................31 7.4 Implementation of System Interfaces..........................................................................................................32 7.4.1 Inform Standard Interfaces' Requirement Gathering and Configuration ............................................. 35 7.4.2 Custom Interfaces' Requirement Gathering and Configuration..........................................................36 7.4.3 Interface Functional Acceptance Testing (FAT) ................... .................... ........................ ....._...... .... 38 7.5 Inform RMS Legacy Data Conversion (Bryan PD Tiburon RMS)..............................................................39 7.5.1 Phase 1 —Mapping Plan.......................................................................................................................40 7.5.2 Phase If — Initial Data Load.................................................................................................................40 7.5.3 Phase III — Final Data Load.................................................................................................................40 7.5.4 TriTech Responsibilities......................................................................................................................40 7.5.5 Client Responsibilities.........................................................................................................................41 7.5.6 Completion Criteria.............................................................................................................................41 7.6 System and Subsystem Go Live..................................................................................................................41 7.6.1 Inform RMS Go Live...........................................................................................................................41 Project Closure............................................................... 8.1 System Transition........................................................................ 9 Appendix A - Required Inform CAD DOLF Code File build ..........................42 .................................42 ..........................44 10 Appendix B - Contracted Modifications to Standard TriTech Software Products ........45 11 Appendix C - Standard TriTech Interfaces......................................................................46 12 Appendix D - Custom TriTech Interfaces........................................................................46 13 Appendix E - Subcontractor(s) Statement(s) of Work ..... ......................51 The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software iv Systems. 02015 TriTech Software Systems vol. ,Z.?c/ pg, ,?� 'Che contents of this material are confidential and proprietary to Tri Tech Software Systems and may not he reproduced, published or disclosed to others without the prior written consent of TriTech Software v Systems. ©2015 Tri Tech Software Systems ----1 Vc1. d9 .-7 Sl pg, .Z A, I OVERVIEW 1.1 Statement of Work In accordance with the terms and conditions of the System Purchase Agreement (the "Agreement") between TriTech Software Systems (1'rffech) and the City of Bryan, Texas ("Client"), this Statement of Work (SOW) defines the services and deliverables that TriTech will be providing under the Agreement. This project description includes the services and Deliverables specified by the Purchase Agreement, including if applicable, TriTech Software and services, Subcontractor activities, Third Party products and services for the implementation of the System and Subsystems specified in the Purchase Agreement (collectively the "Project"), Statement(s) of Work for applicable 'I ri'tech Subcontractor(s) are presented in Appendix E - Subcontractor(s) Statement(s) of Work. In some cases, the framework of Deliverables documented by this SOW for this Project is further defined through additional documents such as: Operational Scenario Documents (OSD); Interface Requirements Documents (IRD); User and Administrator Documentation and Training Materials. The number and type of software licenses, products, or services provided by TriTech or its Subcontractors are specifically listed in the Purchase Agreement and any reference within this document as well as Subcontractors' SOWS (if applicable) does not imply or convey a software, license, or services that are not explicitly listed in the Purchase Agreement. 1.2 Project Implementation Definitions Unless otherwise defined herein, capitalized terms within this document have the meanings described in the Definitions section of the Purchase Agreement and where applicable Software Support Agreement. The following terms are used in this document. Since these terms may be used differently in other settings, these definitions are provided for clarity. • Project Schedule means the schedule providing dates and timeframes for completion of tasks and Deliverables during the course of this Project. The Project Schedule is subject to change at the mutual agreement of TriTech and the Client as further described in this SOW. • Project Management Plan means collectively the Communications Management Plan; Risk Management Plan; and Change Management Plan that provide the criteria for managing those tasks within the Project. • The OSD provides an operational description of a capability or feature within the applicable TriTech solution in sufficient detail that both Client and TriTech team mutually agree to the expected deliverable. The OSD provides the "what", "how," and the information Flow (including data flow and data elements, when appropriate) of the capability or feature. The OSD does not provide the technical or internal design of how TriTech's Development team will accomplish the requested feature. An OSD wit[ be provided for each contracted product customization to be developed. Once approved by the Client, the OSD becomes the basis for TriTech's development. Once approved, any further changes requested by the Client to the OSD and/or design may incur additional costs to the Client. • Standard Interface Requirement Document (IRD) defines the functionality of the Standard Interfaces. These documents are standard, published TriTech documents, and are not specific to a Client. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems. 02015 TriTech Software Systems vol. _a_,�5� i'g._.Z7 ii! I Overview 1.3 System Acceptance Process TriTech has created a standard Acceptance Test methodology which is designed to allow our clients to thoroughly evaluate and verify the functionality, performance, and reliability of TriTech System and Subsystems. These procedures include several steps that are described in later sections of this SOW. Upon successful completion of these procedures the system is deemed Accepted. 1.3.1 Functional Acceptance Testing Functional Acceptance Testing (FAT) is conducted on each of the Subsystems prior to conducting the User Training on these applications and staging them for Go Live. The focus of these tests to verify that each Subsystem meets the functions as described in TriTech's standard FAT documents, which have been created based on TriTech's standard product specifications. The Functional Acceptance Tests are performed based upon standard TriTech FAT documents that have a standard content and format. These standard FAT documents will be submitted to the Client for review prior to testing. During the scheduled FAT and according to the FAT documents, TriTech and Client project personnel will work to identify any errors where the Subsystem does not conform materially to the FAT documents. Any such errors will be documented by TriTech on the FAT exceptions list. Frrors listed on the FAT exception list will be classified as follows: 1) Pre -Go Live Issues: Issues in the Subsystem that prevent the Client from performing normal daily and monthly operations and therefore must be corrected prior to Go Live. 2) Post Go Live Issues: Issues identified in the FAT testing that do not prevent the Client from performing normal daily and monthly processes and therefore can be corrected after the Subsystem Go Live. These issues will not be used as part of the criteria for Acceptance. In the event that the Client chooses not to follow the Acceptance Test processes defined in the Statement of Work, the Client's cutover to live production status (i.e., productive use) of any TriTech supplied Subsystem constitutes the Client's acceptance of the Subsystem. 1.3.2 Integration Testing Once the FAT is successfully concluded for all subsystems that are scheduled to go live together and in preparation for Go Live, TriTech and the Client will conduct a one day Integration Test. Typically Inform RMS along with their associated Interfaces may go live together or separately. The Integration Testing for Inform RMS and its subsystems will be conducted based on a number of scenarios that test the records management process. These scenarios include FBR and Interfaces that can be tested in the pre -production environment and are scheduled to go live at the same time. A small group of the Client staff (1-2 Records Clerks and 1-2 Field Officers) will participate in this test with TriTech. TriTech will work with the Client to define a set of test scenarios that test the Records Management System based on the Client's practices. It is recommended that the Client utilize sample incident, arrests, field interviews, citations, and crash reports from their legacy system. Integration Test scenarios must be signed off prior to commencement of Integration Testing. At the successful completion of Integration Testing, without any issues that prevent the System to be taken Live, the Client shall provide written approval that the System is ready for Go Live. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software 2 Systems. 02015 TriTech Software Systems Vol. �-3 S� pg. '7� Overview 1.4 General Client Responsibilities In addition to those Client responsibilities stated elsewhere in this SOW, the Client is responsible for: 1) Electrical facilities (e.g., outlets, generator and other electrical infrastructure facilities) required for this project, including necessary maintenance. 2) Cabling (e.g., power, network, interface and other electrical and data transmission lines) required for this project, including necessary maintenance. 3) Network/communications connections (e.g., LAN/WAN, commercial wireless, telephone, VPN, and other voice/data connections), or ongoing network/communications charges associated with installation, operation or support of the proposed system including the establishment and maintenance of security accounts. 4) Configuration and/or programming of network routers, switches and bridges— this includes providing information to TriTech staff on any firewalls within the overall network that the system will operate and necessary port access for the system to operate in accordance with TriTech documentation. 5) The installation, configuration, maintenance (including patch management and upgrades of Microsoft software required by the System. 6) The installation of servers into racks and the connection of such servers to network switches. 7) The assignment of machine names and IP addresses for servers to be utilized by the System. This includesjoining the servers to the network and the assignment of security accounts as specified by TriTech documentation. 8) Any hardware and third party software or services necessary for implementing the System that is not listed in the Purchase Agreement as a TriTech Deliverable (not listed as a line item in the Price and Payment section of the Purchase Agreement). This includes workstations, server hardware, network equipment, telephone or TDD equipment, performance test software, Microsoft licenses, Disaster Recovery Software, and services required to extract legacy data and convert into acceptable data formats. 9) Configuration, maintenance, testing, and supporting the Third Party Systems that the Client operates and which will be interfaced with as a part of this project. Specifically, the Client operates and supports Brazos Citation, TxDOT Crash Reporting, Tyler Technology Odyssey Jail Manager, Tyler Technology Protective Order, Tyler Technology Odyssey Warrant, and Tiburon Total Command CAD. The Client is responsible for maintaining and supporting these systems in good working order. The Client is responsible for providing Application Programming Interface (API) documentation to these systems that document the integration process for the level of interface integration defined by the Interface IRD and approved OSDs. The Client is also responsible for any cost associated with the development, or configuration of the Third Party System Vendor side of the Interfaces. 10) Consoles, furniture or fixtures as well as any modifications to install equipment used for Systems or Subsystems specified by the Purchase Agreement into existing consoles, furniture, vehicles or existing facilities. Installation of Workstations into consoles, furniture, vehicles or like items, is the responsibility of the Client. 11) Active participation of the appropriate personnel with the necessary background knowledge and availability in the Project implementation meetings and working sessions during the course of the Project. Examples of such implementation sessions are System Orientation, DOLF, Acceptance Testing, Training, regular Project meetings, discussion regarding Interfaces, system installation planning, and the like. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software 3 Systems. f 02015 TriTech Software Systems Overview 12) The provision of Code Files and GIS data as requested by TriTech staff. This information must be provided on a timely basis in order to meet the project timelines. This information will be provided in a format requested by TriTech staff in accordance with TriTech Documentation. 13) The timely review and approval of Functional Acceptance Testing (FAT) documents, OSDs, IRDS, Task Completion Reports (TCR) and/or other project documentation as further defined in this SOW. 14) Provide a facility with the required computer and audio-visual equipment for training. 15) Timely completion of acceptance testing for each of the TriTech Subsystems. 16) TriTech pricing for this Project assumes that all Client supplied products and services required to support the project will be delivered according to this agreed to Statement of Work, based upon a mutually agreed upon project schedule. This timeline will require a commitment by Client staff to attend project meetings, attend training, and execute action items in a timely fashion. Should the Client find that it is unable to support the agreed to schedule, "TriTech reserves the right to execute a mutually agreed to Project Change Order. The Change Order will make the necessary modifications to schedule and/or scope of the project and, if applicable, allow TriTech to recoup any additional costs which may be incurred by TriTech as a result of Client delays. 17) The Client is responsible for providing remote connectivity to TriTech for the purpose of installation, configuration, testing, and troubleshooting of TriTech's applications at the Client site. TriTech's approved remote connectivity methods are described in the System Planning Document. 18) Connect and configure any Third Party hardware (such as Bar Code Scanners, Bar Code Printers, Biometric Fingerprint Scanners, and Signature Pads) to Client workstations, if these services are not explicitly sold in the System Purchase Agreement. 1.5 Proiect Exclusions 1) TriTech Software Systems provides software applications that it develops. These applications are sold as and are considered to be "Commercial Off the Shelf' (COTS) software packages. The functionality of these products will be based on TriTcch's current design and functionality of these COTS products, unless otherwise indicated in the Purchase Agreement, or if applicable, TriTech's responses to the RFP. 2) Work, software, services, hardware, Systems, Subsystems, product/software modifications, or any other deliverables not explicitly stated in the Purchase Agreement will not be included in the Project. 3) Any modification to TriTech standard products or customizations to such products that are not explicitly stated in the Purchase Agreement are excluded from the scope of this Project. 4) Changes in scope will only be executed through a mutually agreed upon Change Management Process, as described in the Project Management Plan. 5) TriTech is not responsible for the deficiencies in the Client's internal or contracted network to support remote Inform RMS or other subsystem workstations. 6) TriTech is not responsible for the deficiencies in a Client's internal or contracted network to support some of the extended features of Inform Mobile and Inform Field Based Reporting products due to bandwidth or limitations in wireless coverage. 7) TriTech is not responsible for the removal of the old (legacy) equipment, hardware, furniture, consoles, cabling, as part of the Project implementation unless specifically stated in the Purchase Agreement and this SOW. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems. --'— ©2015 TriTech Software Systems 6 2 PROJECT DELIVERABLES 2.1 Overview of Project Deliverables This project will provide a combination of software and services that comprise the System for use by the Client's Public Safety Organization(s). The individual Subsystems to be provided comprise the overall System. The Purchase Agreement specifies the software licenses included in this Project by the quantity and environment in which licensed. This includes all Server and User Licenses, Standard and Custom Interfaces, as well as other TriTech tools and utilities. The Purchase Agreement for this project incorporates the following major Subsystems: 1) Inform RMS (Production, Test/ Training) 2) System Interfaces as listed in the Appendices to this SOW Implementation of different components of the System is performed in a series of interrelated processes. Some processes can be performed concurrently while others are sequential in nature. TriTech has implemented process gates to ensure successful completion of tasks in the optimal order before a subsequent activity begins. The only reference for the number and type of software licenses is the Purchase Agreement. Any reference within this document to services associated with a specific software product does not imply or convey a software license for products that are not listed in the Purchase Agreement. 2.1.1.1 Standard TriTech Software Deliverables The functionality provided by Standard TriTech Software Products, including Interfaces (the core TriTech Soft♦vare and Interfaces without any Modifications) is defined by TriTech Standard documentation such as User and Administration Guides for Tri Tech's major Subsystems such as Inform RMS, and other Standard Software products. Standard Interface Requirement Documents (IRD) define the functionality of the Standard Interfaces. These documents are standard, published TriTech documents, and are not specific to a Client. Standard TriTech Interface Software to be delivered through this Project is identified as software licenses in the Purchase Agreement. The functionality provided by Standard TriTech Interface Software is defined by TriTech IRDS. Any Modification to the functionality of Standard TriTech Software within the System, or Subsystems, shall follow the Change Management Process as described in Section 5.2, Change Management Process. The scope of the Modification will be described in an OSD. Release of all Modifications to TriTech's Standard Interfaces will follow Subsystem release cycles (i.e., Inform CAD, Inform RMS, and the like). 2.1.1.2 Contracted Modifications to Standard TriTech Software Products Any Modifications to Standard TriTech Software Products including Inform RMS, and Standard System Interfaces that are to be delivered through this Project are listed in the Purchase Agreement. The functional scope of any Modification procured through the Purchase Agreement will be summarized in this Statement of Work and defined by an OSD for ell items listed under Appendix 13 - Contracted Modifications to Standard TriTech Sohware Products for Inform RIMS and other major TriTech Subsystems; and under Appendix C - Standard TriTech Interfaces, for modifications to Standard Interfaces. Any and all modifications or enhancements that are not explicitly listed in the Purchase Agreement are not within the scope of this Project. Any changes in the requirements documented in the System OSDs, post approval of the OSDs are subject to formal Change Order. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems. -- C2015 TriTech Software Systems Vol. _�,��_- Pg. TriTech Project Roles and Responsibility Note: All enhancements and modifications to any of TriTeelt's Standard products (including the Interfaces) will only be released with a major version of the applicable subsystem (i.e., Inform CAD, Inform Mobile,,Inform RMS, and the like) based upon the relevance and dependency to these products. ;Note: Software versioning is the process of assigning either unique version names or unique version numbers to unique states of computer software while a service pack or patch is a piece of software designed to fix problems with, or update a computer program or its supporting data. This includes fixing security vulnerabilities and other bugs. 2.1.1.3 Contracted Custom Interface Software Custom Interfaces to be created by TriTech are identified as individual software licenses in the Purchase Agreement. A high level description of the intended functionality and scope is attached as part of Appendix D - Custom TriTech Interfaces to this SOW. The detailed functional scope of any custom interface procured through the Purchase Agreement will be defined by an OSD, which will be developed and delivered to the Client during the project. Any changes in the requirements documented in the System OSDs, post approval of the OSDs are subject to formal Change Order, 3.1 Overview TriTech will appoint a team of specialized personnel that will implement the Project under the direction of TriTech's Project Manager. The team will be multi -disciplinary and the team members may specialize in different products or Subsystems. Team members may be engaged in different phases of the Project as necessary and in some cases are involved in the Project for a limited timeframe. Any personnel changes by TriTech will be discussed with and agreed upon by the Client in advance. Such agreement will not be unreasonably withheld. The descriptions of personnel roles noted below provide an overview of typical Project team members. Other personnel may be involved under the direction of the TriTech Project Manager in order to complete the requirements of the Project. 3.2 TriTech Project Manager TriTech has appointed a TriTech Project Manager as the principal TriTech contact who will be responsible for managing TriTech's responsibilities related to the implementation of the Project, as described in this SOW and within the scope of the Purchase Agreement. The Project Manager utilizes a standardized methodology for project implementation, project management, and risk identification and management. TriTech's Project Manager is responsible for Project scheduling and management of TriTech Project personnel and applicable Subcontractor/supplier resources, budget management, identification and management of Project risks, and communication with the Client's Project team. The TriTech Project Manager will be responsible for the collaborative coordination of Client resources in an effort to ensure that avoidable Project delays will be minimized. The Project Manager is involved in the Project beginning with the SOW development and continuing through post Go Live Project closure activities. The Project Manager will be an active participant in many of the milestone events through the course of the Project including System Orientation, DOLF, and Go Live. The contents of this material are confidential and proprietary to TriTech Software Systems and may not,�� be reproduced, published or disclosed to others. without theprior_written consent of TriTech_ Software 6 Systems. c ' ` 7 i ©2015 TriTech Software Systems VOL � �///./" p�,_ 3.0 TriTech Project Roles and Responsibility The Project Manager will organize a bi-weekly Project status call with the Client and necessary Project team members. Additionally, the Project Manager will provide the Client with a written Project status report on a monthly basis, as further defined in this SOW. 3.3 Systems Engineer The Systems Engineer is responsible for two primary functions, within the scope of the Project: 1) configuration of Standard TriTech Interfaces (including configuration documentation); and 2) development of software requirements documentation for Custom Interfaces. The Systems Engineer will additionally participate in testing of each of these Subsystems- In some cases, Development Engineers may perform the role of the Systems Engineer for specialized interfaces, particularly for Inform RMS interfaces. 3.4 GIS Analyst As part of the implementation team, TriTech utilizes a GIS Analyst that specializes in geographical Information technology. The GIS Analyst is responsible for: 1) performing an analysis and preparing a report regarding the Client's GIS source data including street centerline data, routability, and response area polygon data based on TriTech specified requirements for Inform RMS; 2) consultation services regarding converting the GIS source data for use in Inform RMS; and 3) providing training for applicable TriTech GIS tools. These GIS activities are intended to provide information that will allow the Client to optimize the accuracy and quality of Client GIS data during Project implementation. 3.5 Inform RMS Business Analyst Inform RMS Business Analyst (s) participate in various activities throughout the implementation of each of these Subsystems. They are primarily responsible for conducting the System Orientation with the Client to observe and evaluate the Client's current business practices and make recommendations for improving efficiency and areas that need to be reviewed. They also conduct the Demonstration of Licensed Functionality (DOLF) or Administration Training, performing the Acceptance Testing and providing consulting support throughout the Project implementation life cycle. After the completion of the DOLF session, ownership for continued Code File configuration and maintenance transfers to the Client. At this stage, the Business Analyst will serve as a consultant for the Client's further configuration of the Client's system until the Client's System is in live operation. These activities are described in later sections of this SOW. The Business Analyst will be an active participant in many of the milestone events through the course of the Project and will participate in bi-weekly Project status calls, as needed. 3.6 Training Specialist Training for TriTech applications is provided by Trn l'ech Training Specialists. Training staff for other products and functions will vary by the type of product and training proposed. This process is described in greater detail in the training sections of this document, related to each of these products. 3.7 Client Installation Services Team TriTech's Client Installation Services (CIS) team is responsible for installation and integration of TriTech Software onto the system hardware that is identified for this Project. This team works closely with the The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software 7 Systems. �J 02015 TriTech Software Systems I vol. O` �(/ —_ 1 o �' 3 TriTech Project Roles and Responsibility Client's staff to coordinate IP and network addressing, security accounts, network connections, and remote access to the System. This process is described in greater detail in Section 7.2, System Installation of the SOW. 3.8 Technical Services Group Customer service functions and technical support for the Client's System during the Project is coordinated by the TriTech Project Manager. After Go Live, TriTech's Technical Services Group is responsible for providing on-going support for the Client's System as defined in the Purchase Agreement and the Software Support Agreement. 3.9 Account Executive The Account Executive is an important resource to the Client throughout the life of their System. The Account Executive will be the primary contact and liaison for non-technical support issues, system changes and billing questions. They provide support for general customer service requests, manage requests for new software and services, and provide assistance with planning technology upgrades post System Go Live. Having the Account Executive participate as a key Project member provides an enhanced level of continuity for the Client as they continue their relationship with TriTech. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others -without -the prior written consent of TriTech Software 8 Systems. 0201 ®2015 TriTech Software Systems IV 0I Recommended Client Roles and Responsibilities 4 RECOMMENDED CLIENT ROLES AND RESPONSIBILITIES 4.1 Overview Implementation of the Subsystems in a manner that meets the Client's operational needs requires collaboration with the Client's team. In general, the Client's Project team should include staff experienced in the operation and administration of the Client's current public safety technology systems as applicable to the scope of this project. Such teams may include representatives from the Inform RMS and FBR users and stakeholders. These "subject matter experts" need to be engaged through the course of the Project from initiation until live operations, and may be involved in the support and maintenance of the System and Subsystems after Go Live. These recommendations do not speak to specific positions. Rather, this information defines specific responsibilities and estimated time commitment. 'the Client may elect to create individual positions, combine responsibilities, and/or assign responsibilities within their current organizational structure. The Client needs to periodically assess its staffing needs based on changes in the Client's operational use of this technology. Often, there is overlap with these core responsibilities - therefore, the team can generally be kept to a small group, dependent upon the complexity of the system being implemented and the number of Subsystems. In addition, it is recommended that the Client, early within the implementation process, identify those persons that will be responsible for the ongoing maintenance of the Client's System to include the technical and business processes. The application Administrators (Inform RMS), as well as the System Administrator, are very key to the success of the Project. It is paramount that the Client develops this team during the implementation process so that the Client successfully achieves a degree of self-reliance with the understanding of each of the Systems in addition to the generalized technical responsibilities. 4.2 Project Manager The Client's Project Manager is the principal Client contact who will manage a team of Client Project personnel. The Client's Project Manager manages and coordinates Client's resources responsible for completing assigned Project tasks and activities. Activities include facilitating Project Schedules and meetings, timely approval and processing of invoices, review and approval of Task Completion Reports ("TCRs"), Project management plans, applicable configuration sheets, OSDs and IRDS, approval of the Project documentation and FAT, and management of the Client's staff. Additionally the Client's Project Manager is responsible for coordinating the efforts, activities, and communications between TriTech and third party vendors that are not TriTech Subcontractors, as well as any deliverables from these vendors to the Project. 4.3 System Administrator The Client's System Administrator is the individual primarily responsible for managing the technical back- end of the System including Windows, SQL Server, network, hardware, data back-ups and log management. This individual is the primary technical point of contact representing the Client. As identified in the Purchase Agreement and the Software Support Agreement, following the initial system installation, administration, and support for hardware (including the software operating system) and network components are the responsibility of the Client. The Client needs to plan for support and maintenance The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems. �—� .____ 02015 TriTech Software Systems pg. 3.s" Recommended Client Roles and Responsibilities through the development of Client resources, other departments within the Client's organization, or by contracting for such services. The Client should establish procedures for managing warranty service of hardware. Activities for this position include 1) management of Microsoft Windows Operating System including patches and service packs; 2) management of Microsoft SQL Server including patches and service packs; 3) implementation of software prerequisites (in accordance with TriTech Documentation) on computers as needed for current operations and System upgrades; 4) monitoring, management and maintenance of the Client's network including LANs, WANs, wireless networks, security accounts and support connectivity (in accordance with TriTech Documentation); and 5) hardware maintenance and troubleshooting; file and data back-ups and software and error log management. Time commitment will vary with the number of computers on the system, the complexity of the network (including the use of a WAN) and the number of personnel to be managed in network access. If the System LAN is connected to the Client's administrative LAN/WAN', coordination will be important to avoid problems with the Client's network traffic. Personnel involved in System Administration should attend the applicable TriTech System Administrator Course(s). Where a large team is involved, a core team should attend a System Administrator Course and then the Client's System Administration team should conduct a smaller version of the training for local staff. 4.4 Inform RIVIS Administrator The Inform RMS Administrator will have the responsibilities for the implementation, configuration, and maintenance of Tri fech's inform RNIS and FBR. This person or persons will be engaged in the implementation of the TriTech's Inform RMS, and will participate in making decisions as it relates to implementing the Tri,rech's Inform RMS. Inform RMS Administrator will attend the Inform RMS DOLF during the course of the Project. This person should have a comprehensive understanding of the internal structure and workflow of Inform RNIS and FBR users, departmental policies and procedures as well as how the records department interacts with dispatch and field operations personnel. The Inform RMS Administrator will be responsible for building and maintaining the RMS Code Files. Additional activities include TriTech software setup, assignment, and management of the agency specific Code Files, evaluation and implementation of version updates, reporting, prioritization, and management of support issues. Within the Multi -Agency environment, separate local RMS administration staff may be required to manage the components used by each Agency - under the direction of an overall Central RMS Administrator. Any personnel involved in RMS administration should participate in the DOLF session so they are prepared to maintain the RMS Code Files post DOLF. 4.5 GIS Ana The GIS Analyst is responsible for the mapping components required for Inform CAD, Inform Mobile, Inform RMS. Activities include providing the initial GIS files for use within Inform CAD, Inform Mobile, Inform RMS. The GIS Analyst will be responsible for updating the Inform CAD and Inform Mobile Streets The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written conseut of TriTech Software 10 Systems. 02015 TriTech Software Systems VOA a 3� pg �� Recommended Client Roles and Responsibilities data using GIS Link, and working with Tri fech's GIS Analyst to implement mapping components for Inform RMS. During scheduled activities, the Client should have a fully dedicated person or persons. Post implementation workload will be based upon the number and type of GIS data edits that will be necessary for the local operations. This person should participate in portions of the System Orientations and DOLF. Additionally, this person (or group of people) should attend GISLink training. 4.6 Inform RMS/ and FBR Users/Supervisors Input from the Users/Supervisors is important to ensure that the configuration settings approved by the Client's team will be perceived as usable by users of the each of the Subsystems. These Users/Supervisors should participate in meetings defining and evaluating the requirements and configuration of their respective products, such as System Orientation and Administration Training. During scheduled activities, the Client should have a fully dedicated person or persons. Post implementation should be maintenance only. These personnel should attend the applicable User trainings. 4.7 Subject Matter Experts Input from subject matter experts in all applicable areas (Inform RMS/FBR, and each of the Interfaces and external Systems that integrate with TriTech Systems) is essential to successful implementation of the system. The subject matter expert(s) in each area are the individuals who are knowledgeable about the current operational and technical specifications of the system, the data flow between and among different applications, and any limitations associated with each application. For Standard and Custom Interfaces, subject matter experts may be from the Client Agency, and third party vendors. If the vendors are not TriTech Subcontractors, the Client will be responsible for engaging them in necessary discussions and documentation of the requirements. The Client should involve a fully dedicated person or persons during the scheduled activities, such as requirements analysis, demonstration of the applications (if applicable), review of requirements documentation, the testing process, and other events that are described in later sections of this SOW. Post implementation, the involvement of the subject matter experts should be limited to maintenance only. 4.8 Application Trainers A team of trainers is needed for training the Client staff on TriTech Software on an on-going basis. Trainers will be responsible for reading TriTech Software release notes and maintaining an understanding of new and existing features. The Client should involve a fully dedicated person or persons during scheduled activities such as training sessions. Post implementation, the involvement of the subject matter experts should be limited to maintenance only. These personnel should attend the applicable product specific training courses. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others withoutthe.prior written consent of TriTech Sofrware Systems. 3 02015 TriTech Software Systems .VOL _0�,7 Pg 9-, 5 PROJECT CONTROLLING PROCESSES 5.1 Overview Project Controlling Processes are established early in the Project life cycle during the Planning Phase and described within the Project Management plans. Project Control is the process that includes completing regularly scheduled Project progress meetings and the use of regularly delivered Project progress reports, as well as implementing the processes needed for Communication Management, Risk Management, and Change Management. The process begins during the initiation process and concludes at the end of the Project. The establishment of defined processes for Client communication (contact persons and reporting methods) provides a basis for effective and regular communication. This supports the previously noted processes necessary for successful Project outcome. As part of the Controlling Processes, TriTech utilizes a series of measurements and management reviews to mitigate the effect of these variances. Checkpoints or milestones are planned into each phase of the Project to measure performance and determine if the Project is ready for the next phase. Checkpoints are key tasks that act as gates to the next phase of a project. A delay in a milestone may cause a delay in starting or completing subsequent tasks; in effect creating a risk to the overall Project. Therefore, TriTech's Project staff closely monitors checkpoint tasks and milestones and promptly notifies the Project Manager of any delay or failure with a milestone task. Milestone delays on the part of either parry will trigger an overall review of Project activities so that risks can be assessed and properly managed. In the event that either party becomes aware of a delay, notification shall be provided to the other party as soon as reasonably possible. Evaluation of overall Project status at each checkpoint is essential to ensure that the Project is effectively progressing toward completion and that new risks are not being introduced. In many cases, Project activities leading to a checkpoint are interrelated to later scheduled tasks. Success at checkpoints diminishes the risk to the Project going forward. Incomplete actions at a checkpoint may prompt delays and a rescheduling of the Project. For example, delays in completing or approving Custom Interface OSDs will delay the start and completion of the Interface development work, which may ultimately have an impact on the projected Go Live date. Depending upon the importance of the Deliverable, these kinds of delays can have a cascading effect upon the Project Schedule including training and Go Live Task Completion Reports As part of the Project controlling process, upon completion of significant milestones and or tasks, TriTech will submit a Task Completion Report ("TCR") to the Client. The TCR serves as a formal tool for the purpose of verifying with the Client that the work has been performed, services rendered, and products delivered according to the requirements specified within the SOW and/or related documents. TCRs are presented to the Client by TriTech's Project Manager for signature. Some TCRs may trigger a Project payment, in accordance with the payment terms within the Purchase Agreement. Upon execution of a TCR that is tied to a Project payment milestone, the Client will receive an invoice from'Pri ITch's accounting department which must be paid based on the terms and conditions of the Purchase Agreement. The TCR will include the following information: 1. Description of Work performed and products delivered. 2. Comments noting any special circumstances. 3. Product/Service deliverables listing the contract line items that are being recognized as delivered and will be invoiced. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech So ftware� 12 Systems. 02015 TriTech Software Systems , J� � pg.if � Project Controlling Processes 4. Related Payment Terms in accordance with the Purchase Agreement, for contract line items that will be invoiced relative to the TCR. 5.1.1 TriTech Responsibilities a) TriTech will prepare and submit TCRs for Client's signature upon completion of the applicable task. b) The TCR will cite the appropriate SOW reference. c) TCRs that trigger a payment will include the payment amount in accordance with the Purchase Agreement payment schedule. 5.1.2 Client Responsibilities a) Client will review and approve TCRs within a five (5) business day period from the time of receipt less any challenges to the validity of the report. b) In the event that Client disagrees with a TCR, Client shall submit to TriTech a written explanation detailing why the Client believes that the subject of the "PCR and/or tasks have not been completed in accordance with the Purchase Agreement or this SOW. Such notification from the Client shall be provided to the TriTech Project Manager within five (5) business days of receipt of the TCR. 5.2 Change Management Process Either party can request changes to the scope of the project at any time. Since a change may affect the price, project deliverables, this SOW, the supporting project schedule, and/or the terms of the Purchase Agreement for this SOW, both parties must approve each change in writing and agree on the impact each change may have on the Purchase Agreement and related attachments. The purpose of the Change Management Process is to manage any significant changes to the Project as described in this SOW or related documents as referenced within the SOW. These changes may include, but are not limited to a modification to Project scope, Standard or Custom products' functionality, TriTech and Client's identified roles and responsibilities, Project payment terms, and modifications to the scope or delivery location of services within the Project. All significant changes must be documented through the Change Management Process. The type of documentation needed will depend on the nature and significance of the change. A Project Change Order will be the vehicle for communicating and approval of the changes. Whether initiated by the Client or TriTech, all Change Orders will be documented by the TriTech Project Manager. The Change Order shall describe the requested change, the party requesting the change, and the effect the change will have on the project, including the price, project deliverables, this SOW, the supporting project schedule, and/or the terms of the Purchase Agreement for this SOW. All Change Orders must go through the TriTech's internal approval process before they can be presented to the Client for review and approval. Once the Change Order is generated, the Client Project Manager and TriTech Project Manager will review the proposed change and communicate as necessary to answer any questions, and/or work to resolve any issues preventing acceptance of the Change Order by both parties. Upon the approval by both parties the Change Order will be authorized for implementation. The creation of some Change Orders may, depending upon the scope of the requested change, require fees in order for TriTech to properly investigate and scope of the requested change. If additional fees are required by TriTech to create a Change Order, those fees will be identified and communicated to the Client Project Manager prior to TriTech's investigation of the requested change. In such situations, TriTech will only proceed with the investigation required to create the Change Order if the Client has agreed to pay the additional fees associated with creation of the Change Order. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the -prior written_ consent of TriTech Software 13 Systems. 02015 TriTech Software Systems Vol. Project Controlling Processes Additional deliverables or Project deletions in terms of Software and services will require a mutually agreed upon Change Order. It must be noted that the later in the Project that a change is requested, the greater the likely impact in terms of costs, risks, and timescale. It is recommended that the Client not delay any review activity as it is a best practice to discover potential changes as early as possible. In some cases, it may be more appropriate to plan modifications for post Go Live delivery. 5.21 TriTech Responsibilities a) Change Orders will be prepared for submission to the Client when required. b) Where Project changes require Engineering -level modifications, TriTech will perform requirements capture necessary to prepare required documentation including a high level description of the change for Client review and approval. e) Where Project changes require Engineering -level modifications, Client will be informed of the delivery mechanism (version and schedule). 5.2.2 Client Responsibilities a) When applicable, the Client will identify the services or deliverables that will be subject to a Change Order, per the Purchase Agreement between both parties. b) When applicable, the Client will identify changes to features or functionality related to CAD, Mobile, Interfaces or any other Subsystems that will require a change order. This process may also include participation with the requirements process. c) Client will approve and process Change Orders as in a timely manner. 5.3 Project Reporting TriTech will provide Monthly Status Reports advising the Client Project Manager and key Client Project Stakeholders of the progress and status of project activities. This report will include the significant accomplishments, planned activities, issues, and potential risks associated with TriTech and TriTech's Subcontractors' Deliverables. The Project Status Reports will include the following: a) Accomplishments during the Reporting Period. b) Planned upcoming activities. C) Issues. d) Risks. e) Key Action Items. In addition, the TriTech Project Manager will hold bi-weekly status meetings/conference calls to update the Client on the status of the Project and key action items and deliverables. During the course of the Project, one or more Projectjournals will be created to document Project issues and action items. These journals are generally product specific and are used by the Project Manager and other team members to facilitate successful Project completion. Projectjournals are reviewed with the Client during bi-weekly Project status calls and on an as needed basis through the course of the Project. The Project Manager is responsible for periodically providing copies of updated journals. TriTech will provide an updated Project Schedule advising the Client Project Manager of the progress of project activities. The Project Schedule may be lacking the detailed tasks for the Client team, and the Client may add such tasks, owners, and durations to the Project in collaboration with TriTech Project Manager. The Project Schedule will consist of the following: The contents of this material are confidential and proprietary to TriTech Software Systems and may not a be reproduced, published or disclosed to others without the prior written consent of TriTech Software 14 Systems. 02015 TriTech Sofivare Systems Vol Z /2 e/ ^ Pg S/D Project Controlling Processes a) Major Tasks. b) Task Responsibility. c) Task Duration. d) Major Milestones. e) Tasks Completed. f) Tasks in Progress. 5.3.1 TriTech Responsibilities a) Provide a written report of Project status once a month. b) Track issues and action items to closure through product specific journals. The Client will be periodically provided with updated copies Ofthejoumal. c) Conduct status meetings/conference calls every two weeks. d) Maintain an up-to-date Project Schedule. 5.3.2 Client Responsibilities a) Review the written report of Project status and provide feedback within five (5) business days in order to ensure that the documentation is correct. b) Participate in Project status meetings. c) Ensure participation of personnel in tasks and meetings. 5.4 Document Review In the course of the Project, TriTech will deliver several documents to the Client for review. These documents will include but are not limited to the Acceptance Test Procedure, Project Schedule, DOLF report, OSD, and Interface Requirement Documents for the Project. Approved documents are returned to the TriTech Project Manager. For paper documents, the TriTech Project Manager will retain the original copy and will provide an unbound copy suitable for reproduction. For soft copy documents, the TriTech Project Manager will retain a copy and provide Client with a copy. Should the Client find any document unacceptable, the Client must provide specific reasons in writing to the TriTech Project Manager. TriTech can then assess any required corrective measures and make revisions or modifications to provide acceptable documents within a mutually satisfactory timeframe. Status Reports are not subject to approval. In order to ensure compliance with the Project Implementation Schedule, the Client is responsible for the review of such documents and providing any comments to TriTech within five (5) business days. 5.4.1.1 Documents Subject to Client Approval a) Change Orders b) Operational Scenario Documents (OSD) c) Application Configuration Sheet (l) Functional Acceptance Test Procedure documents e) Task Completion Reports The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software 15 Systems. "" --- — ---"" 02015 TriTech Software Systems IV 01. l' . / pg_ 41 Project Controlling Processes 5.4.1.2 Documents Subject to Client Review not Requiring Approval a) Project Schedule Note: The Project Schedule and any changes hereto are to be mutually agreed upon between the Client and TriTcch. b) Project Status Reports c) DOLP Reports for Inform RMS d) Project Journals e) Interface Requirements Documents (IRD) 5.4.2 TriTech Responsibilities a) Distribute the documents to the Client. b) Coordinate the process to consolidate comments and edit documents. c) Manage the signoff process for applicable documents and the distribution of originals to the Client and TriTech for tiling. 5.4.3 Client Responsibilities a) Review the documents presented and provide the appropriate information back to TriTech within five (5) business days for configuration sheets, Change Orders and/or Sales Orders. b) Review the documents presented and provide the appropriate information back to TriTech within ten (10) business days for requirements documents defined above. Unless unanticipated changes to the Project Schedule would warrant a shortened turn around. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software 16 Systems. 02015 TriTech Software Systems vol '^9 �Pg �Z 6 PROJECT INITIATION AND PLANNING 6.1 Overview Project Initiation and Planning involves gathering the necessary Project specific information in order to produce a Project Management Plan and a Project Schedule. In short, Project Planning consists of those processes designated to establish when and how the Project will be implemented while further elaborating on Project Deliverables. Most of the information exchange between the Client and TriTech during this process is at a high level and consists of interaction between both Project Managers and a small group of Project stakeholders. Major Deliverables for the Project Planning phase are the specific Project Management Plans, and a baseline Project Schedule. The project must be managed in a manner that will allow for the adjusting the Project Management Plan and Project Schedule to address the circumstances that affect a project during Project Execution. As a result of these changes during the Project life cycle, Project Planning will overlap each subsequent process during the Project. Typically, Project Planning tasks will decrease in frequency as checkpoints are successfully completed and as the Project nears Go Live and Project completion. :Note: The Project Schedule is a living document, subject to change during the course of the Project I due to several factors such aschange in Project scope, scheduling conflicts, delay in approving i project documents, resource availability, etc. All changes to the Project Schedule will be discussed between both parties and will be incorporated within a published schedule upon approval from the Client and TriTech.. 6.1.1 TriTech Responsibilities a) Assign a Project Manager to the Project to participate in Initiation phase activities. b) Produce required documentation to support Initiation activities (such as Standard IRDS, System Planning Document, etc.) c) Review and finalize the SOW with the Client. d) identify and engage the TriTech Project team responsible for carrying out Project Execution. e) In collaboration with the Client, develop the Project Management Plan (includes the Communication Management Plan, Risk Management Plan, and Change Management Plan). t) Baseline the Project Schedule. g) Prepare and submit the TCRs for Client acceptance of the Project Management Plan as defined above. h) Develop and submit invoice for payment due at execution of the Purchase Agreement. 6.1.1.1 Client Responsibilities a) Assign a Project Manager for the Project to participate in Initiation phase activities. b) Identify and engage the Client's Project team. e) Review and comment on the TriTech Project Management Plan and the Project Schedule. d) Review and comment on TriTech provided documentation to support Initiation activities. e) Finalize and approve the SOW with TriTech. f) Approve the TCRs for the Project Management Plan within 5 business days. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software 17 Systems. 02015 TriTech Software Systems qq Project Initiation and Planning 6.1.2 Project Kick Off During the planning phase, the TriTech Project Manager will hold a Kick -Off meeting with the Client's Project team. During the Kick -Off meeting, the TriTech Project Manager will provide an overview of the following: 1. The TriTech Execution Process. 2. A high level description of Project Deliverables. 3. Roles and responsibilities for the Project team members. 4. A high level review of the preliminary Project Schedule including projected Project milestones and checkpoints. 5. Describe the work that has been either completed, is in progress or is due to begin within the immediate future. 6. Review any project related questions from the Client's team. 6.1.2.1 TriTech Responsibilities a) Prepare the agenda and set a date for the Kick -Off that is convenient to the Client and TriTech Team. b) Distribute any documents that the Client should review in advance of the Kick -Off meeting. c) Conduct the Kick -Off meeting. 6.1.2.2 Client Responsibilities a) Work with the TriTech Project Manager to facilitate scheduling a date for the Kick -Off meeting. b) Schedule the appropriate personnel from the Client's team to attend. This should also include key stakeholders that may not participate routinely in Project operations, but who have authority or responsibility over the Project. c) Provide adequate accommodations to include adequate seating and audio-visual equipment including a projector(s), screen, and whiteboard. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software 18 Systems. 1-- ©2015 TriTech Software Systems vOl+ �� [/ Pg. � 7 PROJECT EXECUTION 7.1 Overview Project Execution focuses on the development and delivery of Project Deliverables. Processes will be iterative and consist of: 1) a review of Deliverable documents; 2) Development, configuration, Installation and testing of software and hardware deliverables, and 3) Delivery of Project related services such as Project related training. These processes are iterative in nature with a number of checkpoints to evaluate Project progress and where applicable, to initiate Change Management processes. Each Deliverable has a closing process which consists of specific completion criteria. These Deliverable closing processes are independent from the closing process of the Project. 7.2 System Installation (Inform RMS and Interfaces) System installation is one of the early processes in the Project implementation phase, and has a great impact on and critical dependency on a number of key activities. All tasks and activities related to System Installation are included in this section and will occur in the order presented. Note that other project activities can occur concurrently or between these steps. 7.2.1 Review Hardware Specifications TriTech and Client will review the specifications to ensure that the correct hardware and third party software components are procured and installed. TriTech will only be responsible for procurement of the hardware and third party software that is explicitly listed under the Agreement, as TriTech Deliverables, or Deliverables of TriTech's Subcontractors. 7.2.1.1 TriTech Responsibilities 1) Provide hardware and Third Party specifications to Client. 7.2.1.2 Client Responsibilities 1) Review and validate hardware and Third Party specifications. 7.2.2 Hardware and Equipment Procurement Process TriTech and Client will procure hardware, third party software, and equipment per TriTech's recommended Specifications. TriTech is only responsible for procurement of the hardware and third party software that is identified as TriTech Deliverables in the Purchase Agreement. If the hardware and third party software is procured by the Client, it is the Client's responsibility to procure the required equipment based on TriTech approved specifications, and to ensure the timely delivery of the hardware and third party software to the site to allow timely implementation of the System and Subsystems. Where the Client is responsible for procuring the server hardware, the Client will be responsible for completing the following steps: 1) Fully configuring the servers with memory and disks. 2) Loading Microsoft Windows or VMware. 3) Partitioning the disk drives and implementing applicable Raid level based upon TriTech documentation. 4) Assigning the computer name and 1P address based upon TriTech documentation. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software 19 Systems. F------ 02015 -- _02015 TriTech Software Systems Vol. Pg„ mss' Project Execution 7.2.3 Hardware Staging and Preparation for Installation The Client will be performing basic server integration for all servers. Basic server integration includes placing the servers in the racks, joining them to the existing domain, with the Domain Controller in place, and establishing remote connectivity capability (VPN and Remote Desktop) for authorized TriTech personnel to perform configuration. These activities will be coordinated between TriTech and the Client 11' staff. Guidance will be provided by TriTech's Client Installation Services (CIS) team as required. If the Client is not willing to complete the basic server integration, this task may be performed by TriTech or TriTech's Subcontractors at additional cost. In order to start configuration, the Client must provide remote connectivity to TriTech. The Client must also provide the server names, IP addresses, Administrator Account Information (User Name, Password), Services Account Information, and the location of 3rd Party Software media (such as SQL). An Installation Service Request (ISR) will be provided to the Client that organizes this information in to the TriTech preferred format. The Client is responsible for providing the completed ISR to TriTech no later than two (2) weeks prior to the installation activities. The Client is responsible for ensuring that the site is prepared and ready for the installation of hardware, third party software, and TriTech software as detailed in TriTech's documentation including the System Planning Document no later than two (2) weeks prior to the scheduled Installation date. Delay in providing this information in its complete form will result in a delay in the Installation and the activities that follow installation of the System. At least one (1) week prior to installation, a member of the TriTech CIS team will verify: (i) connectivity to the Client site via VPN, (ii) connectivity to each of the servers, and (iii) access to all required security accounts. If the servers, accounts and connectivity are not ready the Project may be rescheduled, which may have an impact on the overall Project timelines. 7.2.4 TriTech Responsibilities a) Provide the System Planning Document. b) Facilitate a hardware review prior to hardware/OS procurement. e) Procure equipment and third party software if included in the Purchase Agreement as a TriTech deliverable. d) Provide guidance and assistance as necessary if the system equipment is procured by the Client. e) Distribute the Installation Service Request (ISR) document to the Client. f) Assist the Client in completing the ISR. g) Assist the Client with the preparation of a network diagram. h) Review the completed ISR prior to the installation. i) Test the remote connectivity to the site prior to installation of the hardware and software. j) Install the Microsoft SQL software. k) Prepare and submit a TCR for Client review and approval upon completion of these activities. 7.2.4.1 Client Responsibilities a) Complete the Installation Service Request (ISR) document and provide to TriTech. b) Prepare a network diagram and provide to TriTech. c) Perform site preparation, as specified in the System Planning Document and ISR. The cmrtents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software 20 Systems. q� t- ©2015 "I7iPech Software Systems F-VO 77, J j� n9 .C�6 Project Execution d) Assign the computer name(s) and IP address(es) based upon TriTech documentation. e) Establish remote connectivity capability (VPN and Remote Desktop) for authorized TriTech personnel to perform software installation and configuration. n Run TriTech Pre -Requisite DVD on all applicable Inform servers prior to any installation work being performed. g) Provide all horizontal and vertical cable runs, pathways, coring, access points, floor cutting or drilling, and related tasks related to cable and equipment installation. h) Provide all Client -supplied telephone, external interface connection points, electrical power and other receptacles within manufacturer recommended distance of the equipment and all peripheral components. i) Provide and install all data communication lines, modems, hubs and routers, cabling, equipment and other components necessary for system operation and maintenance and for remote sites and connection to other systems. All lines will be clearly identified and tested. j) Provide TCP/IP communications and connection to the hub equipment provided in support for any existing networks, workstations and printers that are to have access to the TriTech applications. k) Obtain all necessary IP addresses and schemes. 1) Allow remote access to TriTech to all development and system "root" accounts on all servers running TriTech licensed Software. m) Procure equipment and third party software if it is the responsibility of the Client according to the Purchase Agreement. n) Install operating system software for Client procured hardware unless the service is specified as a TriTech responsibility in the Purchase Agreement. o) Perform basic server integration including, but not limited to: i. Installation of servers in applicable racks. ii. Joining servers to the existing domain with the domain controller in place. iii. If applicable, install and setup of the VM environment. p) Provide "TriTech with all necessary configuration documentation which includes machine naming, IP addresses, Administrator Account information, Service(s) Account information, naming convention, and connectivity as prescribed. q) Provide TriTech with a high level network diagram. The diagram should be provided prior to TriTech Software installation. r) Install all peripheral equipment, including scanners, printers, barcode readers, etc. s) Approve the applicable TCR. 7.2.5 Basic Server preparation and Network Services Performing the services listed in this section is a responsibility of the Client. If these services are explicitly included in the Purchase Agreement, TriTech or a TriTech Subcontractor will implement 3`d party software and/or hardware solutions based upon the following task list. These solutions can include but is not limited to, SAN, Citrix, VMware, and Domain Controller configurations. These services can be performed on site or remotely via a VPN connection. These services will be performed at additional cost to the Client and are not included in Tri'Tech's standard installation services. 7.2.5.1 Client Responsibilities a) Provide the facility suitable to house Server hardware and network infrastructure. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software 21 Systems. 02015 TriTech Software Systems V. O j52— p y, it Project Execution b) Have a member of the Client's IT staff available while software/network configuration is being performed. a) When deploying a SAN, configure the applicable RAID configuration, create the LUN(s) and present them to the physical or virtual servers. b) if the VM servers are not procured through TriTech, the Client is responsible for building individual servers. c) When deploying a VMware solution, install the VMware operating system, connect physical host servers to a SAN if applicable, configure vCenter, create a VM Template for Interfaces and business servers, configure vMotion and High Availability (HA) if applicable. The Client is also responsible for building individual VM servers. d) If required, deploy the Domain Controller by adding the member server to an existing Domain or create a new Domain, promote the member server to Domain Controller, enable and configure DNS, enable and configure DHCP if required. c) Create domain account(s) for TriTech's remote support connectivity and access so that TriTech can assist Client with installation and ongoing maintenance t) Perform all necessary network configurations, to include but not limited to determining the network design routing protocols, subnet mask, redundancy, router and switch configuration. g) Create Networking/Server documentation to illustrate intended configuration. VMware, vMotion and HA require a SAN or a way to present shared storage to the physical host servers in a VMware virtual farm. Network and Server security are always a: responsibility of the client. 7.2.6 System Installation Once TriTech and the Client have prepared the site based on TriTech documentation, to include the System Planning Document and the applicable ISR form is completed, a TriTech Client Installation Services specialist will perform the TriTech installation services. These services will be performed remotely, unless otherwise specified in the Purchase Agreement, and include installation of the contracted TriTech Software products on the quantity of servers and workstations as specified in the Purchase Agreement. These installation activities will be coordinated between TriTech and the Client. Note 1: All SQL server licenses will be installed by TriTech. The Client is responsible for making that media and license keys available to TriTech for the installation. +Note 2: The Installation services for different components of the System may be performed at i different times, based on the implementation and deployment timelines for each Subsystem. ; ;Note 3: The scope of installation services and the number of servers and workstations to be installed and configured by TriTech is. limited to the servers and workstations that have been explicitly'. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software 22 Systems. --- ©2015 TriTech Software Systems VOI pg Project Execution listed in the'Purchase Agreement. If -the Client has been granted Site Licensing for — TriTech Software, TriTech is only responsible for the initial installation services, and installation of additional servers will be subject to additional charges. 'Note 4: If Client does not follow the processes and procedures detailed in the TriTech System , Planning Document and this results in a need for reinstallation of the hardware or software, the reinstallation effort will be performed at additional cost to the Client. Note 5: At TriTech's discretion, TriTech may perform installation activities for certain components of the system on-site. The following pre -requisites must be in place prior to the start of TriTech Software installation: a) Site preparation is complete as outlined in the sections above. b) Hardware has been installed at Client site. e) Client has provided TriTech with remote connectivity to all applicable servers. d) Client had provided TriTech all relevant documentation as outlined in the sections above to include licensing keys, IP addresses, usemame/passwords, and the completed ISR. 7.2.6.1 TriTech Responsibilities a) Install and configure Microsoft SQL to operate with each of the applicable'rriTech product(s). b) Configure the System servers in the applicable environments (Production, Test, Training, and Disaster Backup environments, if provisioned by the Purchase Agreement). c) Install and configure the applicable TriTech system(s), such as Inform CAD, Inform RMS, and Inform Mobile on the designated servers and applicable environments as specified in the Purchase Agreement. d) Provide verbal support to the Client with self -installation procedures for the workstations using the TriTech provided Prerequisite Installation DVD and applicable Launch configurations. e) If applicable, create data dumps for Microsoft SQL database backups (as a backup for Inform RMS database). f) Prepare and submit a TCR upon completion of the installation tasks and activities. 7.2.6.2 Client Responsibilities a) Allocate appropriate onsite Project personnel to support TriTech personnel during configuration tasks as necessary and designate a primary point of contact to be available to address and answer questions that arise during the installation of the baseline application software. Appropriate Client personnel include the necessary IT personnel and database administrator(s) as needed during installation. b) Complete the configuration of workstations (after the installation of the limited number of workstations by TriTech) using the Prerequisite Installation DVD and applicable Launch configurations. c) Put in place TriTech's recommended backup procedures as outlined in the System Planning Document and ensure backup procedures are consistently follow beginning at the completion of this task. d) Install and configure virus scanning software as outlined in the System Planning Document. e) Provide Web Security Certificates for all TriTech web -enabled applications that require a certificate. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software 23 Systems. ------- ©2015 TriTech Software Systems Pg. �� Project Execution t) After completion of the initial installation and configuration of System servers, the Client will be responsible for maintaining the System based on TriTech System Document, and the technical hand-off from TriTech Technical Services department. Specifically, the Client's IT staff is responsible for completing the following activates related to Inform Subsystem servers: o Updating Training/Test Systems with fresh data (from Production) as heeded o Continued updating and monitoring of virtis scan software o Application of Windows updates o Following the procedures for System Upgrade o Managing/Reviewing system logs (SQL and Event Logs) o Management of Microsoft and other Third Party Software include patch applications and upgrades as needed for new Subsystem versions. o Deployment and use of the Prerequisite Installation DVD for Subsystem upgrades as required. g) Review and approve the applicable TCRs. 7.3 Implementation of Inform RMS Inform RMS (to include FBR) is implemented through a series of standard steps and process gates. These steps are designed to ensure that the operational needs of the Client are identified, the configurations are verified, and the system is tested to validate the proper functionality of the system prior to deployment. The following sections describe the implementation process for Inform RMS. 7.3.1 Inform RMS System Orientation The Inform RMS System Orientation is conducted at the Client's site and led by a 17iTech Business Analyst. The duration of the Inform RMS System Orientation is up to 6 days and includes a Business Process Review of the Client's operations. Some key discovery points for the Inform RMS System Orientation are as follows: a) Work Flow — Understanding the setup for work flow processes from the field report to the State Submission. This may include time observing Departmental Divisions (such as Records Staff, Investigation, Property and Evidence, and the like) and Ride-Alongs with field units. b) Review reporting requirements (reporting segmentation and the like). c) Event numbering (Incidents) including master incident numbers and case numbers. It is recommended that the number of attendees in the System Orientation is limited to 10-15 to allow for more effective communication during the session. Based on the key discovery points during this session, it is necessary that the attendees include individuals who can properly address these key points and make configuration decisions. During the System Orientation session the Business Analyst will facilitate an operational review of Inforin RMS (to include FBR) by demonstrating various System functionality and start gathering the configuration information. A System Module Setup worksheet (SMS) and other reference material will be provided to the Client to assist in gathering the required Code Files. Information that cannot be produced during the meeting must be sent to TriTech as specified by the mutually agreed upon schedule. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software 24 Systems. --- l` O2015 TriTech Software Systems Vol. �� pg. i Project Execution .Note: The Client's provision of Code File information is an early Project checkpoint. Remote Web sessions will be scheduled as a follow up to System Orientation to guide the Client through the i Code File data collection process. This information is needed to prepare the DOLF and incomplete, inaccurate or delayed Code File inforniation can have a cascading effect on the Project Schedule. 7.3.1.1 TriTech Responsibilities a) Schedule the System Orientation meeting in accordance with the Client's availability and the Project Schedule. b) Prepare and distribute the meeting agendas and documents for Client review or completion two weeks prior to each meeting. c) Conduct the meetings based on the distributed agenda. d) Document the Client's requirements and configuration specifications resulting from the System Orientation discussions. e) Send the System Module Setup worksheet (SMS) and other reference material to the Client. f) Document and assign owners and due dates to any action items and track all action items to closure. g) Document any gaps between the standard functionality of the System and functionality required by the Purchase Agreement for further analysis and discussion and/or facilitate the change control process. Client requested changes for changes beyond the scope of the Purchase Agreement will be evaluated at this phase, but will have to be evaluated for the potential impact on the Project Schedule and for additional project charges to be paid by the Client. It) Schedule one or more Remote Web sessions as a follow up to System Orientation to guide the Client through the Code File data collection process. i) Produce a System Orientation Report with the key decisions and configuration points as a result of the System Orientation. j) Prepare and submit a TCR upon completion of relevant activities. 7.3.1.2 Client Responsibilities a) Provide adequate facilities to comfortably hold the System Orientation to include a computer projector, whiteboards, and adequate seating. Two projectors are preferred. b) Ensure participation of key stakeholders and decision -makers in the System Orientation process. c) Provide subject matter experts that can explain the agency's current work flow and application processes. These persons should have the ability to make decisions regarding any changes in work flow that may arise through the use of the new Inform RMS System. d) Provide subject matter experts with the ability to gather and provide the data elements used to build Code Files to TriTech. e) Provide subject matter experts that will be the RMS super users, as well as a person or persons that will be responsible for the ongoing maintenance of the RMS Code Files and configuration (RMS Administrator). f) Provide subject matter experts that will be responsible for translating the geopolitical/operational boundaries into data (ESRI shape files) suitable for use within the RMS. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software �I 25 Systems. 02015 TriTech Software Systems—— -----� Project Execution g) Provide subject matter experts that will be responsible for the maintenance of the agency's street centerline data. It) Provide subject matter experts that can provide information on technical Systems (Interfaces and Hardware/Network/Applications). i) Review and approve applicable TCRs. 7.3.2 Inform RMS Base System Code File Entry After completion of the Inform RMS System Orientation and receiving requested pre-DOLF data from the Client, the assigned TriTech Business Analyst will work with the Client to start and supervise the initial Code File building process. The Business Analyst will configure the Inform RMS Central Configuration as defined in the System Orientation. The Client will be actively involved and responsible for the Code File configuration process throughout the project. TriTech will deliver the Inform RMS System with the base NCIC Codes. The Client is responsible for building and maintaining the System Codes, Personnel, Property Locations, and Violation Codes (including local ordinances). The TriTech Business Analyst will begin the System Build with a base of 50 personnel entered into the system. The Client is responsible for the remaining Personnel data being entered and maintained. Note: 1t is the responsibility of the Client to complete the UCR mapping to the violation codes. Validation through the DOLE process allows for the initial Code File setup while limiting the risk of rework. This task is considered to have been completed when the Business Analyst has demonstrated the setup of RMS User Personnel, Property Locations, and Violation Codes. 7.3.2.1 TriTech Responsibilities a) Monitor and evaluate Code File submitted by the Client and provide guidance as needed. b) Conduct one or more web meetings to validate the completeness and applicability of Client submitted Code File information, prior to initiating the Code file entry. e) Facilitate updates to the System Module Setup (SMS) building sheet. (l) Prepare and submit a TCR to confirm the delivery of the SiNIS worksheet by the Client. 7.3.2.2 Client Responsibilities a) Provide timely input and updates to the SMS sheet to support the Code File building timelines. b) Participate in the Code File validation conference call. c) Continue building the System Code Files (those not built by TriTech) after DOLF. (1) Review and approve applicable TCRs. 7.3.3 Inform RMS Administration and Review Training The Inform RMS Administration and Review Training is a hands-on course for Inform RMS System Administrators. During the course students will learn how to create users, assign roles, create FBR templates and assign workflows, create and maintain system code tables, and map UCR codes. During the training the Business Analyst will review the Inform RMS system defaults. Students also learn overall administration responsibilities for implementation, configuration, and maintenance of Inform RMS. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others -without the.prior.written.consent of.TriTech_Software 26 Systems. _ / 02015 TriTech Software Systems Vol. ofq �Cf Project Execution Participants include key members ofl'riTech's implementation team and should not generally exceed ten (10) core members of the Client's implementation team. The Client's team should include RMS Central and Local Administrators. The Inform RMS Administration and Review Training will be up to four (4) days onsite 7.3.3.1 TriTech Responsibilities a) Schedule the Inform RMS Administration and Review Training in accordance with the Client's availability and the Project Schedule. b) Prepare and distribute the meeting agenda and documents for Client review or completion to all required attendees two weeks prior to the training. c) Conduct the meetings based on the distributed agenda. d) Prepare and submit a TCR upon completion of the training. 7.3.3.2 Client Responsibilities a) Provide adequate facilities to comfortably hold the training activities. b) Ensure participation of the appropriate personnel. c) Continue the code file building activities after completion of this training. d) Review and approve the applicable TCR. 7.3.4 Inform RMS Demonstration of Licensed Functionality (DOLF) Once the initial Code File and configuration phase is complete and RMS is installed at the Client site, a Demonstration of Licensed Functionality (DOLF) is conducted. This working meeting includes a review of the preliminary Code Files and configuration and hands-on training on software utilities for completing the Code File build and on-going Code File management. The DOLF for Inform RMS is up to three-four (3-4) days and will be held at the Client's facilities, and on the Client's system hardware, after it has been configured by TriTech. Client will be responsible for supplying the requested data to TriTech no later than four (4) weeks prior to DOLF to allow sufficient configuration time. The data will be requested as a follow up to the System Orientation for Inform RMS. The configuration of some RMS modules may be delayed based on the Client's decision, and consultation with TriTech Business Analyst. Participants include key members of TriTech's implementation team and should not generally exceed ten (10) core members of the Client's implementation team. The Client's team should include RMS Central and Local Administrators. At the conclusion of the session, a DOLF report is produced which documents the core software configuration, Code Files, and activities to be completed by the Client. Any issues that require follow-up action, including any outstanding Go Live issues will be documented in the applicable Project journal. Any issue that is determined to be outside the scope of this Project, as defined herein, requiring a modification or enhancement to the TriTech Software will be addressed through the Change Control process. Guidance on configuring additional Code Files will be provided during the DOLF. Following the DOLF process, ownership of Code Files transfers to the Client. Post DOLF, the Client will enter the balance of the Code Files (not built by TriTech). The Client also becomes responsible for maintaining Code Files (personnel, Violation Codes, Property Locations, and the like) that must be continuously updated to keep the Code Files in GO -Live ready status. During this phase, the assigned TriTech Business Analyst will provide consultation services. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without.the.prior-written consent of TriTech Software 27 Systems. 'f , / 02015 TriTech Software Systems Vol. O1 U t pg, S3 n Project Execution Note: Inform RMS DOLF is an event applicable to Inform RMS only. No other Systems or Subsystems will be demonstrated during ttris session. 7.3.4.1 TriTech Responsibilities a) Schedule the DOLF meeting in accordance with the Client's availability and the Project Schedule. b) Prepare and distribute the meeting agendas to all required attendees a week prior to each meeting. c) Conduct the meetings based on the distributed agenda. d) Provide initial hands on training on the applicable system and introduction to different modules and their configurations. 'Note: This training is not meant to be comprehensive for end user understanding ofthe Subsystem. I i The purpose is to give the participant an understanding of the configuration and administration' of Inform RMS. e) Introduce the Client to, and begin documentation within the Subsystem Journal. f) Document and assign owners and due dates for any action items and track all action items to closure. g) Develop and deliver the DOLF Trip report. h) Handoff the management of the Code Files to the Client. i) Provide the Client team with a copy of the Inform RMS User and Administration Guides. j) Prepare and submit a TCR upon completion of the DOLF, and upon delivery of the DOLF Trip report to the Client. 7.3.4.2 Client Responsibilities a) Provide adequate facilities to comfortably hold the DOLF to include an overhead projector. Two projectors are preferred. DOLF also requires workstations for each participant. b) Ensure complete participation of Central and Local Inform RMS Administrators for the purposes of reviewing the RMS configuration as -built. c) Provide participants that are versed with the ability to continue the configurations, or Code File build once ownership transfers. d) Assume ownership for the continued build and maintenance of the system under the guidance of the TriTech project team. e) Ensure participation of key stakeholders and decision -makers in the DOLF process. f) Observe the change control process for any requested software changes. g) Review and approve the applicable TCRs. 7.3.5 Inform RMS Workshop After the Inform RMS DOLF has been completed, the TriTech project team will conduct one or more Inform RMS workshops at the Client site. This session is intended to be an extension to the Inform RMS DOLF for more complex implementations and multi jurisdictional agencies as specified in the contract. Each Inform RMS workshop will be up to three (3) days onsite. If the Project includes multiple Workshops, they may or may not be scheduled to occur over consecutive weeks. The Project includes: Four (4) Inform RMS Workshops The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software 28 Systems. --- - 02015 TriTech Software Systems Vol.'rel Pg..SV Project Execution 7.3.5.1 TriTech Responsibilities a) Schedule the Inform RMS Workshop in accordance with the Client's availability and the Project Schedule. b) Prepare and distribute the meeting agendas and documents for Client review or completion to all required attendees two weeks prior to each meeting. c) Conduct the meetings based on the distributed agenda. d) Prepare and submit a TCR upon completion of the workshop. 7.3.5.2 Client Responsibilities a) Provide adequate facilities to comfortably hold the training activities. b) Ensure participation of the appropriate personnel. c) Continue the code file building activities after completion of this training. d) Review and approve the applicable TCR. 7.3.6 Inform RMS Functional Acceptance Testing (FAT) Inform RMS Functional Acceptance Testing follows a standard content, approach and format. An Inform WMS Business Analyst performs the acceptance testing with the Client, prior to the start of End User Training. This process will be based on the standard TriTech FAT documents. The FAT documents have a standard content and format. The standard TriTech FAT documents will be sent to the Client for review prior to conducting the tests. The FAT results are documented in a TCR for verification and approval by the Client. Upon completion of FAT, the Client and TriTech will review the list of FAT failures (if any), and perform an assessment of the errors and determine the timeline for remedying the issues (pre versus post Go Live). TriTech will repeat any specific failed FAT tests following the correction of any issues which has caused the test to fail. This process will not include a repeat of the entire tests. 7.3.6.1 TriTech Responsibilities a) Deliver TriTech's standard FAT documents to the Client no later than two weeks prior to conducting the FAT. b) Provide a TCR to the Client to approve the receipt of the FAT documents. e) Assist the Client in conducting the FAT in accordance with FAT documents. d) Identify and document any issues discovered during the FAT. e) Upon completion of FAT prepare and submit a TCR to the Client, including a list of any exceptions to FAT. 7.3.6.2 Client Responsibilities a) Work toward the timely completion of all predecessor tasks to include the base code table entry and configuration. h) Provide adequate facilities to execute the FAT. C) Participate in the FAT by providing operational subject matter experts. d) Assist Tri"Poch in documenting FAT findings and results. e) Review and approve the appropriate TCRs. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software 29 Systems. -' 02015 TriTech Software Systems Ej(� p JI S� Project Execution 7.3.7 Inform RMS Training ;Note: Training classes are conducted based on the quantities that are specified in the Purchase Agreement. The appearance of a course description in this Statement of Work does not mean a' course will be conducted — it must be listed in the Purchase Agreement. j Inform RMS Training classes are conducted on consecutive weekdays (Tuesday -Friday) daring business hours. Alternate training schedules (multiple classes per day, evening, and weekend classes) will be subject to additional charge. Training classes will only be delivered after the FAT has been completed and the results are documented. A detailed description of these classes is provided below: 7.3.7.1 TriTech Responsibilities (for all Inform RMS Classes) a) Conduct a training orientation via conference call between the assigned TriTech Training personnel and the designated Client representative. The objective of this session is to define the Training Schedule, based on the configurations of the Subsystem. b) Schedule the Inform RNIS Training class(es) in accordance with the Client's availability and the Project Schedule. c) Prepare and distribute the meeting agendas and documents for Client review or completion to all required attendees two weeks prior to each meeting. d) Develop and provide the Inform RMS Training Plan for all licensed product options to the Client. e) Conduct the training session(s) for the licensed product options on a mutually agreed to schedule. t) Prepare and submit a TCR upon completion of each class, or a group of consecutive classes. 7.3.7.2 Client Responsibilities (for all Inform RMS Classes) a) Participate with the training orientation by providing a decision maker that can articulate the specific business practices that have been used in guiding the build of the Client's System. b) Provide adequate facilities for the execution of the training to include adequate seating for each workstation and an overhead projector. e) Provide a Local RMS Administrator for each class that can answer agency specific questions as related to the build of the Client's system. d) Review and approve the applicable TCRs. 7.3.7.3 Inform RMS End UserTraining— Records The Inform RMS End User Training for Records is a hands-on course that prepares the students to add, edit, and modify Incident, Arrest, Custody, Crash, Citation, Field Interviews, Pawn, Permits and Licensing, and other Event reports. This class also instructs users on how to search crime report records easily and efficiently. Students learn how to maintain State -reportable UCR/NIBRS reports. This class is recommended for all personnel responsible for the day-to-day records data entry and maintenance of all departmental reports. This three-day course prepares a core set of end users to use Inform RMS. Training classes are conducted between Tuesday and Friday, witha maximum of ten (10) students per class. Prerequisites: 1) Basic understanding of computers and the Microsoft Windows Environment. 2) A comprehensive understanding of the internal structure of the Records Department and departmental policies and procedures. 3) An understanding of how the Records Department interacts with Dispatch and Patrol. 'I lie contents of this material are confidential and proprietary to Tri Tech Software Systems and may not be reproduced, published or disclosed to others without .the .prior -written consent of TriTech Software 30 Systems. +J j _ 02015 TriTech Software Systems VOL s5 .ly Pgs t Project Execution 7.3.7.4 Inform RMS End User Training — Field Officers The Inform RMS End User Training for Field Officers session is a hands-on three-day course. This course trains students to use Inform RIvIS and includes instructions on how to create and submit htcident, Arrest, Field Interview, Citation, and Crash reports through the workflow process. For the train -the -trainer portion of the class, TriTech prepares selected Client personnel to train other end users on Inform RMS. The goal is to prepare these personnel to apply TriTech's training concepts to train field users on Inform RMS. Training classes are conducted between Tuesday and Friday, with a maximum of ten (10) students per class. Prerequisites: 1) Basic understanding of computers and the Microsoft Windows Environment. 2) A comprehensive understanding of the departmental policies and reporting procedures. 3) An understanding of how Patrol interacts with the Records Department and Dispatch. 7.3.7.5 Inform RMS Property and Evidence Training The Inform RMS Property and Evidence training is a hands-on three-day course for personnel responsible for entering, updating, and maintaining evidence records, tracking tow/impounds, and providing written notification for property or impounds. Students learn how to search evidence records, manage evidence items, create item Barcodes, and use barcoding for inventory evidence. Training should be conducted directly with the Evidence Technicians at the agency's Evidence room. Training classes are conducted between Tuesday and Friday, with a maximum of ten (10) students per class. Prerequisites: 1) Basic understanding of computers and the Microsoft Windows Environment. 2) A comprehensive understanding of the departmental policies and procedures associated to maintaining Evidence. 3) A thorough understanding of how each of the Agency's Evidence locations are laid out and used. 7.3.7.6 7.3.7.7 Inform RMS Investigations Training The Inform RMS Investigations training is a hands-on three-day course for Case Managers, Investigative Supervisors, and Investigators (Detectives). Students learn how to assign cases for investigation and track their progress, add case supplements/case materials, create incident supplements, arrests, and update cases as needed. Students will also learn how to add, edit, and search intelligence records, create an RMS case from intelligence data (if applicable), and use the Intelligence Master Index. Training should be conducted directly with detectives that can train other detectives at their agency; this helps ensure proper workflows are discussed and configured. Training classes are conducted between Tuesday and Friday, with a maximum of ten (10) students per class. Prerequisites: 1) Basic understanding of computers and the Microsoft Windows Environment. 2) A comprehensive understanding of the departmental policies and procedures associated to Case Management, Investigations, and the management of Intelligence data (if applicable). 7.3.8 Inform RMS Integration Testing Once the FAT is concluded for Inform RMS, Subsystems, and Interfaces that are scheduled to Go Live with Inform RMS and in preparation for Go Live, TriTech and the Client will conduct a one day Integration Testing. The Integration testing will be conducted based on a number of scenarios that test the records management process. These scenarios involve the Subsystems and Interfaces that are scheduled to Go Live with Inform RMS and can be tested in the pre -production environment. A small group of the Client staff (1-2 Records staff and field users) should participate in this test with TriTech. TriTech will work with the Client on defining a set of test scenarios that test the system based on the Client's practices. It is recommended that the Client utilizes sample calls from their legacy System. These scenarios must be signed off prior to The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software 31 Systems. I _� O2015 TriTech Software Systems Project Execution commencement of the integration testing. At the successful completion of Integration Testing without any issues that prevent the System to be taken Live the Client shall provide written approval that the System is ready for Go Live. 7.3.8.1 TriTech Responsibilities a) Schedule Integration Testing with the Client. b) Assist the Client in preparing test scenarios that can be used during this test and closely simulates the normal Client's call (low. e) Prepare and submit it TCR to the Client documenting the tests that will be used for Integration Testing. d) Participate in the Integration Testing with the Client. e) Prepare and submit TCRs upon successful completion of the Integration Testing. 7.3.8.2 Client Responsibilities a) Provide test scenarios that closely simulate the Client's normal call flow. b) Participate in conducting the Integration Testing. c) Review and approve the applicable TCRs. 7.4 Implementation of TriTech.com IQ and Analytics TriTech.com IQ and Analytics are implemented through a series of standard steps and process gates. These steps are designed to ensure that the operational needs of the Client are identified, the configurations are verified, and the system is tested to validate the proper functionality of the system prior to deployment. The following sections describe the implementation process for TriTech.com IQ and Analytics. 7.4.1 TriTech.com IQ Administration Training (Remote) This TriTech instructor led class is designed for those individuals who will be responsible for the administration of TriTech.com IQ. Participants will be instructed on how to configure, administer, and operate TriTech.com IQ in an administration role. The recommended class size for this training is up to 9 participants. This training is up to 4 hours and is delivered in one remote session. At the completion of the training, participants will be able to perform the following: • Access and successfully login to IQ • Understand the TriTech.com IQ site • Understand the management console for TriTech.com IQ • Create and manage roles • Create anti manage users 7.4.1.1 TriTech Responsibilities a) Schedule the Administration training in accordance with the Client's availability and the Project Schedule. b) Provide standard Administration training sessions for Client personnel e) Prepare and submit TCRs upon completion of the training. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent ofTriTechSoftware 32 02015 TriTech Software Systems VOA. _. q Project Execution 7.4.1.2 Client Responsibilities a) Schedule appropriate personnel to attend Administration training. b) Ensure participation of the appropriate personnel. c) Review and approve the applicable TCRs. 7.4.2 TriTech.com IQ Core End User Training (Remote) This TriTech instructor led class is designed for the end users of TriTech.com IQ. End users include roles such as officers, records clerks, dispatchers, dispatch supervisors, managers, and agency administrators. This class may be attended by the end users, or trainers who will be training the end users within the agency(ies). The recommended class size for this training is up to 12 participants. This training is up to 4 hours and is delivered in one remote session. At completion of this training, participants will be able to perform the following: • Access and successfully login to IQ • Understand the TriTech.com IQ site • Use links within the site • Use Online Help • Use Search Filters • Save searches and manage saved searches • View Search History • View Search Details • Set up Search Alerts and manage alerts • Create and access reports These half day courses are conducted remotely and trains a core set of end users on the TriTech.com IQ System. Typically, the remaining end users will be trained via Client delivered training sessions. The number of students attending the User Training course will be limited to no more than ten (10) students per class. :Note: All remaining TriTech.com IQ end users must complete Client provided end user training. 7.4.2.1 TriTech Responsibilities a) Schedule the TriTech.com IQ Core End User Training class(es) in accordance with the Client's availability and the Project Schedule. b) Conduct the training session(s) on a mutually agreed to schedule. c) Prepare and submit a TCR to the Client upon completion of the training. 7.4.2.2 Client Responsibilities a) Provide adequate facilities to comfortably hold the training activities. b) Ensure participation of the appropriate personnel. c) Ensure that all TriTech.com IQ core end-users attend the end-user training provided by TriTech. d) Provide TriTech.com IQ training to all other end users. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software 33 Systems. ------ - 02015 TriTech Software Systems IV cl. Project Execution e) Ensure that each TriTech.com IQ end-user completes relevant training before assigning the end-user a username and password to access the TriTech.com IQ. i] Review and approve the appropriate TCR. 7.4.3 TriTech.com IQ Analytics End User Dashboard Training (Remote) This TriTech instructor led class is designed for individuals who will be using Analytics Dashboard. The recommended class size for this training is up to 9 participants. This training is up to 8 hours and is delivered in one remote session. At completion of this course, participants will be able to perform the following: • Access Analytics Dashboard • Successfully Login to Analytics Dashboard • Filter Data • Use Analytical Combo Controls • Use interactive data selection to identify trends and key relationships • Perform operational trending and historical analysis • Expedite and enhance reporting activities • Measure performance against work plan or work productivity levels This course is conducted remotely and trains a core set of end users on the TriTech.com Dashboard System. Typically, the remaining end users will be trained via Client delivered training sessions. (Note: All remaining TriTech.com Analytics Dashboard end users must complete Client provided end i. user training. 7.4.3.1 TriTech Responsibilities a) Schedule the TriTech.com IQ Core Analytics Dashboard Training class(es) in accordance with the Client's availability and the Project Schedule. b) Conduct the training session(s) on a mutually agreed to schedule. c) Prepare and submit a TCR to the Client upon completion of the training. 7.4.3.2 Client Responsibilities a) Provide adequate facilities to comfortably hold the training activities. b) Ensure participation of the appropriate personnel. c) Ensure that all TriTech.cont Analytics Dashboard core end-users attend the end-user training provided by TriTech. d) Provide TriTech.com Analytics Dashboard training to all other end users. e) Ensure that each TriTech.com Analytics Dashboard end-user completes relevant training before assigning the end-user a username and password to access the TriTech.com Analytics Dashboard. I) Review and approve the appropriate TCR. 7.4.4 TriTech.com Analytics End User Report Training (Remote) This TriTech instructor led class is designed for individuals who will be using TriTech.com IQ reporting. The recommended class size for this training is up to 9 participants. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without -the prior -written consent of TriT_ec_h Software 34 Systems. 1 02015 TriTech Software Systems p `Q Project Execution Typical time length for this training is up to 4 hours and is delivered in one remote session. At completion of this course, participants will be able to perform the following: • Access IQ Reports • View reports • Edit reports • Copy reports • Export reports • Use the Report Writer (if applicable) • Use filtering options • Sort, Group, and generate Total Counts • Share reports This course is conducted remotely and trains a core set of end users on the TriTech.com Analytics Report System. Typically, the remaining end users will be trained via Client delivered training sessions. ;Note: All remaining TriTech.coht Analytics Report end users must complete Client provided end i usertrainine. 7.4.4.1 TriTech Responsibilities a) Schedule the TriTech.com IQ Core Analytics Report Training class(es) in accordance with the Client's availability and the Project Schedule. b) Conduct the training session(s) on a mutually agreed to schedule. e) Prepare and submit a TCR to the Client upon completion of the training. 7.4.4.2 Client Responsibilities a) Provide adequate facilities to comfortably hold the training activities. b) Ensure participation of the appropriate personnel. c) Ensure that all'friTech.com Analytics Report core end-users attend the end-user training provided by TriTech. d) Provide TriTech.com Analytics Report training to all other end users. e) Ensure that each TriTech.com Analytics Report end-user completes relevant training before assigning the end-user a username and password to access the TriTech.com Analytics Report. f) Review and approve the appropriate TCR. 7.5 Implementation of System Interfaces 7.5.1 Inform Standard Interfaces' Requirement Gathering and Configuration The functionality and applicable configuration options for each of the TriTech Standard Interfaces are described in the Interface Requirements Documents (IRD). A TriTech Systems Engineer will review the IRDS for each of the applicable Standard Interfaces with the Client's subject matter experts and prepare a configuration worksheet (ICD) detailing the parameters that will be set to meet the desired functionality for the Interface. This process may be performed for different interfaces at different times. This process will be performed remotely via phone conference. The Client is The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software 35 Systems. 02015 TriTech Software Systems jVoL_,z3y_ Project Execution responsible for engaging the third party vendors whose systems are being interfaced with, so that an end to end Flow of the data is discussed. TriTech Systems Engineer will configure and install the Standard interfaces on Client's system hardware. IRDs are not Client specific documents, and trot subject to edits, changes, or approval. Client specific configurations for Standard Interfaces are documented in configuration worksheets (ICD) and must be approved prior to configuration of the interface. Installation and configuration of Standard Interfaces can only be performed by qualified members of TriTech System Engineering or Engineering teams, using proprietary tools. Any changes to the requirements of the Records Check interface from the approved Configuration worksheet will be subject to additional cost and configuration time. Once each of the Standard Interfaces are installed and configured, they can be staged for FAT. TriTech is not responsible for coordination, management, or covering the cost of any software, work, customization, coding or testing that is required to be performed by the third party vendors engaged in the implementation of the standard or custom interfaces, unless the work is defined under a subcontract with TriTech within the scope of this Purchase Agreement. Note 1: Standard Interfaces are developed and enhanced within the TriTech product version process ifor TriTech software products (such as Inform CAD). Changes to standard Interfaces will require adherence to the development life cycle therein. Changes to standard Interfaces that are delivered within this life cycle will require the Client's system to be on a compatible version. (Note 2: The Client's provision of Interface Requirements for Standard Interfaces is an early Project ' checkpoint. This information is needed to prepare the configurationsheets for Standard Interfaces. Incomplete, inaccurate or delayed information can have a cascading effect on the Project Schedule, and may result in a significant delay in completion of the project, since modification to Standard Interfaces are only released with a major version of Inform CAD. Note 3: Any changes to the configuration of Standard Interfaces made by the Client makes the Interface non -supportable, and all,troubleshooting efforts resulted.by such changes will be subject to,additiohal cost. Note 4: The Client is responsible for any services or software needed from such Third Party Systems to allow for interaction with the Third Party System or for connecting to TriTech Interfaces Software.in the absence of a Third Party API. TriTech is ,not responsible for any cost associated for the API, arty required third party lab or certification testing, cost'associated 1,, with required programming or custom work by the third party vendors, or any license fees that may. be required by the third party vendors. 7.5.2 Custom Interfaces' Requirement Gathering and Configuration A TriTech Systems Engineer will review requirements specified by the Purchase Agreement applicable to Custom Interfaces, and lead gathering detailed operational requirements within the scope of the Purchase Agreement. This process may be performed for different interfaces at different times. This process will be performed remotely via phone conference. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software 36 Systems. x ©2015 TriTech Software Systems Eo l.. a J pg-74i�j Project Execution Once sufficient information has been gathered to describe the operational functionality of the Interface, the Systems Engineer will create Operational Scenario Documents (OSD) detailing the operation of the Interface. Client's input in detailing all relevant information regarding the operations of these interfaces and interactions with the external systems are essential to timely and accurate development of the OSDs. The completed OSDs will be provided for Client's review. This document must be approved by both the Client and TriTech prior to development. The Client will be given a TCR that the document was provided, meets the requirements and has been reviewed with the Client. The Client must review the OSD within 10 days from delivery by TriTech, and provide comments and questions back to TriTech or provide approval if no changes or edits is necessary. The Client is responsible for obtaining the API for each of the third party vendors that TriTech applications are interfacing with. The ANI must be for the version of the third party software that TriTech will be interfacing with. The timclincs for providing these documents to "TriTech is concurrent with development of the OSD, so that any limitations associated with the level of integration with the third party application can be taken into consideration. Delays in review and approval of the OSDs can impact timely development of the interfaces, and ultimately delay the Go Live of the system. All requirement changes for Custom Interfaces after approval of the OSD shall follow the Change Management process, and may be subject to additional cost and development time. Upon approval of the OSD the custom interfaces are developed by TriTech engineering team. Once developed, these interfaces will be installed on Client equipment and go through testing with the Client and applicable third party vendors who own and administer the vendor side of the interface. The Client is also responsible for coordinating execution of a mutual Non -Disclosure Agreement (NDA) between the third party vendors and TriTech before any technical information or documentation can be exchanged or testing can commence. TriTech is not responsible for coordination, management, or covering the cost of any software, work, customization, coding or testing that is required to be performed by the third party vendors engaged in the implementation of the standard or custom interfaces, unless the work is defined under a subcontract with TriTech within the scope of this Purchase Agreement. Note 1: The Client's provision of,Interface requirements for each of the Custom Interfaces is an early Project checkpoint. This information is needed to develop the OSDs for Custom Interfaces. Incomplete, inaccurate, or delayed, information can have a cascading effect on the Project Schedule, and may result in a significant delay in completion of the project. Note 2: The Client is responsible for providing Application Programming interface (API) documentation for the Third Party Systems..The API must document the integration process for the level of interface integration defined by TriTech's response to the RFP. The Client is responsible for any services or software needed from such Third Party Systems to allow for integration with the third party system. j jNote 3: The scope of functionality for the custom interfaces is limited to 1) the capability of the TriTech System being interfaced and 2) the Application Programming Interface (API) capabilities of the external system beintz interfaced. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of'1'riTech Software 37 Systems. 02015 TriTech Software Systems Vol. P9.`_/ 2 Project Execution Note 4: High level descriptions of each of the custom interfaces in Appendix D - Custom 'TriTech Interfaces, will become the basis for the scope of detailed requirements, described in the I OSD: Any changes in the requirements documented in the System OSDs, post approval of the OSDs are subject to formal Change Order. jNote 5: The Client is responsible for coordinating the development of the vendor side of all interfaces to the third party applications for the interfaces that the vendor is not a TriTech Subcontractor, based on the Purchase Agreement. 'Note 6: 'TriTech is not responsible for any cost associated for the API, any required third party labor certification testing, cost associated with required programming or custom work by the third party vendors, or any license fees that may be required by the third party vendors. 7.5.3 Interface Functional Acceptance Testing (FAT) All Standard and Custom Interfaces are subject to Functional Acceptance Testing (FAT). FAT for Standard Interfaces is based on a standard set of TriTech FAT documents for each interface, as they are applicable to Client's configurations. FAT for Custom Interfaces are based on the functionality described in the approved OSD for the interface. This process will be based on an FAT document developed by the Systems Engineer. The test source will be the provided IRDS; therefore all Standard Interfaces will be tested against standard, predefined TriTech FAT documents. These tests have a standard format and will be sent to the Client for review prior to conducting the FAT. TriTech will repeat any failed FAT test following the correction of any issues which has caused the test to fail. 7.5.3.1 TriTech Responsibilities a) Provide the IRD to the Client for review for each of the Standard Interfaces. b) Prepare and submit a TCR to the Client, documenting the delivery of the IRDS to the Client for Standard Interfaces. c) Review the IRD with the Client for each of the Standard Interfaces and gather and document the configuration options for the Interface. (1) Install and Configure the Standard Interfaces based on the agreed upon configurations. e) Gather the operational requirements for each of the Custom Interfaces and develop and OSD. f) Provide the OSD to the Client for review and approval. (for custom interfaces only) g) Prepare and submit a TCR to the Client, documenting Client's approval of the OSD for each of the Custom Interfaces. It) Develop the Custom Interfaces based on the approved OSD. i) Install and configure the Custom Interfaces. j) Prepare and submit TCRs upon installation of the Interfaces. Ic) Develop FAT documents reflecting feature descriptions found within the provided and applicable OSDs. 1) Provide the FAT documents to the Client for review prior to conducting the FAT for each interface. in) Provide a TCR to the Client to approve the receipt of the FAT documents. The contents of this material are confidential and proprietary to TriTech Software Systems and may not V6 be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems. ©2015 TriTcch Software Systems EOI p9 /'! Project Execution n) Assist the Client in conducting Acceptance Testing in accordance with FAT documents. o) Prepare and Submit a TCR, documenting completion of FAT including any exceptions to FAT. p) Resolve FAT issues and re -run tests as required. 7.5.3.2 Client Responsibilities a) Participate in the review of the IRDS and provide the configuration information to TriTech in a timely manner. b) Provide the information that are necessary for development of the OSD for each Custom Interface. c) Obtain the API for each of the third party applications that TriTech interfaces with and provide the document to TriTech. d) Review and approve the OSDs based on the required timelines. e) Engage the third party vendors in the requirement gathering, development, testing and other interface development activities. I) Review and approve the FAT documents. g) Participate in the FAT. h) Assist TriTech in documenting FAT findings and results. i) Review and approve the applicable TCRs. 7.6 Inform RMS Legacy Data Conversion (Bryan PD Tiburon RMS) TriTech has engineered a solution that incorporates Client legacy data into Inform RMS in a way that retains its historical accuracy while ensuring the integrity of the Inform RMS System. TriTech's Integrated Solution Department will work with the Client throughout this phased process. Prior to any final conversion of legacy data, TriTech will provide a Functional Specification Document (PSD) that will identify all of the data to be converted, mappings to Inform RMS, conversion rules, and code table transformations. The FSD must be approved by the Client prior to TriTech developing the scripts for the Data Conversion. The scope of the data conversion will be limited to a one-way import of Inform RMS data for the following application entities (with indication of whether the data is transferred to IQ or not from Inform RMS): • Master Person Indices (MPI) Tiburon Total Command RMS o All Master Persons to IQ -yes • Master Vehicle Indices (MVI) Tiburon Total Command RMS o All Master Vehicles associated to imported entities listed below to IQ -yes • Master Property Indices (MPI) Tiburon Total Command RMS o All Master Property associated to imported entities listed below to IQ -yes • Master Location Indices (MLI) Tiburon Total Command RMS o All Master Locations associated to imported entities listed below to IQ -yes • Arrest Tiburon Total Command RMS (to IQ -yes) • Case Tiburon Total Command RMS (to IQ -yes) • Incidents Tiburon Total Command RMS (to IQ -yes) • Warrants Tiburon Total Command RMS (to IQ -yes) The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software 39 Systems. 02015 TriTech Software Systems Project Execution • Evidence Tiburon Total Command RMS (to IQ -no) • Accident Tiburon Total Command RMS (to IQ -no) • Images and Objects Tiburon Total Command RMS (to IQ -yes) • Field Interview Tiburon Total Command RMS (to IQ -yes) • Personnel Tiburon Total Command RMS (to IQ -no) • Special Flags Tiburon Total Command RMS. All Special Flags associated to Master Name, Master Vehicle, Master Property and/or Master Location. (to IQ -no) 7.6.1 Phase 1 —Mapping Plan Phase I of the Data Conversion project begins with the Client extracting a complete set of data and providing the data to TriTech in a Microsoft SQL format. The Client will provide at least one intermediate extract of RMS data for TriTech testing purposes, plus one final extract. The Client will supply a data dictionary and relationship diagrams defining all of the data items that are to be included the data conversions. This must be in a machine-readable format that can be included as a part of the Operational Scenario Document (OSD) that TriTech will generate. Note: The Client will provide an initial, complete export of all of the legacy data to TriTech within 60 business days of project signing to enable TriTech to develop the appropriate data conversions.' Note: In the event that the Client makes any modification to their original data in order to include it in an Inform RMS record, they must fully document the transformation process used. All transformations so supplied must be able to be implemented via scripts vs. "human - interpretive" processes. These include, but are not limited to names and addresses. Note: No additional modifications to existing TriTech products or database fields are required. 'Note: No images or objects will be converted. "TriTech will perform a data analysis to determine the actual usage of individual tables and fields within the client -provided legacy database. The results of this analysis will be formatted into an Excel worksheet that will be used as the framework of the legacy data Mapping Plan. Interpretation of the meaning of the individual tables and fields pertaining to the legacy system will be derived from information supplied by the Client. TriTech will create a proposed snapping of this data into the 'friTeuh application. Once the client has reviewed and approved the proposed Mapping Plan, a copy ofthe final Mapping Plan will be delivered to the Client for sign -off as the first deliverable of the conversion. 7.6.2 Phase II — Initial Data Load Phase It of the Data Conversion will be for TriTech to develop mapping scripts and design non-standard reports (Comprehensive Narratives). The second deliverable will be for TriTech to deliver the initial load for client review. Depending on the amount of data involved, TriTech may limit it to a representative subset of the records in the legacy database. 7.6.3 Phase III — Final Data Load The third phase will occur prior to Go Live of the Inform RMS application. TriTech will remotely load the converted data on to the Client production server. 7.6.4 TriTech Responsibilities a) TriTech will provide a set of templates that will include all data elements that are included in the Inform RMS data conversion. The template includes the most widely used fields and provides the greatest value for Inform RMS users. b) TriTech will map the RMS data to the available Inform RMS fields at time of implementation. c) TriTech will set up an Inform RMS Test Server and workstation at TriTech. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software 40 Systems. '—'--- ©2015 TriTech Software Systems vol. �J j' / Pg• ` Project Execution d) TriTech will test and debug the complete RMS Import on the Test Server using the intermediate data set delivered to TriTech by the Client. c) TriTech will schedule a remote GoToAssist session to allow the Client to review and approve the conversion completed on the Test Server. f) TriTech will pre-process the data as required for the conversion. TriTech will use GoToAssist to remotely perform the conversion on the Client's production Server. g) TriTech is responsible for creating the necessary scripts for the data transfer. h) TriTech is responsible for completing the remote installation. 7.6.5 Client Responsibilities a) The Client will extract a complete set of data for analysis, and provide it to TriTech into the templates provided in a compatible Microsoft SQL Database format. b) The Client will supply a data dictionary and relationship diagrams defining all of the data items that are to be included the data conversions. c) The Client must provide a SME and make them available for consulting throughout the project. (1) The Client will manually enter a minimum of 10 representative records into each module to be included as part of the Data Conversion. The data used for entry must be included and identified in the initial data extraction supplied to TriTech. e) Prior to go -live, The Client will provide TriTech a final backup of legacy data. t) Acquaint themselves with the modules included in the Data Conversion. g) The Client is responsible for identifying and documenting all data elements to be imported. h) The Client is responsible for providing access to requested data for importing. 7.6.6 Completion Criteria This section will be considered complete when the final conversions has been populated within the production system and validated by the Client as complying with the Data Conversion Planning Document. 7.7 System and Subsystem Go Live The "cut over" of each of the Inform RMS and Interfaces into the production environment is a highly orchestrated activity that will require a number of resources from both the Client and TriTech teams. 7.7.1 Inform RMS Go Live Once end-user training has been completed and Inform RMS is ready to be placed into production, TriTech will assist the Client in placing the system into operation. In preparation for Go Live, "TriTech will assist the Client in cleaning the training data from the Inform RMS System. TriTech will provide the Client with a standard Go hive authorization letter that must be approved by the Client no later than 3 weeks prior to Go Live. This letter will list all the Subsystems that are scheduled for the Go Live, and any exceptions to Go Live applications. It also memorializes the date and time of Go Live, as well as the Client's confirmation that the System and staff are ready for Go Live. At Go Live, the TriTech and Client implementation teams will support the users in the transition to the new System. Any issues are logged and resolved through TriTech Technical Services. A more detailed Go Live plan will be provided with adequate lead time. The duration of the Go Live support for Inform RMS and its subsystems for this project will be 2 days (to include pre and post cutover) by 2 people. Go Lives are conducted on consecutive weekdays (Monday - Friday). Go Lives that require TriTech support that begins before or extends beyond weekdays will be subject to additional charge. The breakdown of onsite Go Live Services is as follows: Inform RMS Go Live Coverage: The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTcch Software 41 Systems. " pg G ;7©2015 TriTech Software Systems Vol. 1j Project Closure 2 persons for 2 days covering a single shift and a single agency during normal business hours (additional services will be required to include additional agencies). 7.7.1.1 TriTech Responsibilities a) Prepare and submit a Go Live authorization letter to the Client. a) Identify the participants for the Go Live in accordance with the terms of the Purchase Agreement. b) Have specified personnel onsite in advance of the Go Live date to begin the final inspection of the Client's system as pat of the Go Live preparations. c) Be on-site to assist the Client in placing the system into production status. d) Assist Client staff in using the system and assist the computer operations staff in supporting the system. e) Provide System monitoring following the actual System cut over as specified within the Purchase Agreement. i) Prepare and submit a TCR upon first Live operation of Inform RMS. 7.7.1.2 Client Responsibilities a) Complete Inform RMS roll out to support the Go Live date. h) Review and approve the Go Live authorization letter no later than 3 weeks prior to each scheduled Go Live. c) Complete all relevant end user training to support the Go Live of the Subsystems. d) Place the software into production and.begin operational use in consultation with TriTech and in accordance with the project schedule. e) Provide adequate persons for the supervision and assisting the end users beyond the participation of the TriTech staff. f) Provide dedicated workstations for TriTech support staff during Go Live support period. g) Provide Client fl' support to cover all Client end user and TriTech staff hours of operation. h) Develop a process for the reporting and resolution of issues. i) Review and approve the applicable 'I'CR. 8 PROJECT CLOSURE When all pre and post go live project deliverables have been completed, Project Closure activities will take place. Support of the System and Subsystems are transitioned to TriTech's Technical Services Group. Any remaining Project related administrative tasks are completed by TriTech and Client. Project documentation is archived and primary Client interaction is officially handed over from the TriTech Project Manager to the TriTech Account Executive. 8.1 System Transition Following Go Live, there is a transition period where the Client moves from the implementation team to the support team. This transition will change the Client's primary point of contact from the Project Manager back to the Account Executive. Sofbvare support will be handled through the Technical Services Group. The Client's issues will be entered, tracked, and managed via a computerized and web -enabled issues tracking system. This tracking system will become available to the Client at system installation. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without-the-prior_written.consent.of_Trffech Software 42 Systems. I 02015 TriTech Software Systems Vol. pq, V Project Closure 8.1.1.1 TriTech Responsibilities a) Provide payment reconciliation, final TCRs and final invoices. b) Transition the TriTech point of contact from the Project Manager to the Account Executive and Technical Support Department. c) Provide continued support based on terms of Purchase Agreement. 8.1.1.2 Client Responsibilities a) Provide approval of Project TCRs within five (5) business days. b) Provide payment reconciliation and payment of final invoices. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software 43 Systems. ©2015 TriTech Software Systems J Vol., ✓ � _ P9-, N. 9 APPENDIX A - REQUIRED INFORM CAD DOLF CODE FILE BUILD Not Applicable. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software 44 Systems. 02015 TriTech Software Systems'/ Vol. a.��= Pg,% Appendix B - Contracted Modifications to Standard TriTech Software Products 10APPENDIX E - CONTRACTED MODIFICATIONS TO STANDARD TRITECH SOFTWARE PRODUCTS Note: Any changes in the requirements documented in the System OSDs, post approval of the OSDs are subject to formal Change Order. There are no product modifications proposed for this project. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software 45 Systems. 02015 TriTech Software Systems Appendix C - Standard TriTech Interfaces 11 APPENDIX C - STANDARD TRITECH INTERFACES (Note: The scope of functionality for these Standard interfaces is limited to 1) the capability of the TriTech System being interfaced and 2) the capabilities of the external system being interfaced.' Note:.High level descriptions of each of the custom interfaces below will become the basis for the scope.of detailed requirements, described in the OSD. Any changes in the requirements i documented in the System OSDs, post approval of the OSDs are subjec6to formal Change Order. (Note: The Client is responsible for coordinating the development of the vendor side of all interfaces C to the third party applications for the interfaces that the vendor is not a TriTech Subcontractor, based on the Purchase Agreement. List of Project's Standard Interface: Production Environment: a) One (1) Standard CAD to RMS Data Transfer Interface 12APPENDIX D - CUSTOM TRITECH INTERFACES Note: The Client is responsible for providing Application Programming Interface (API) documentation to these Third Party Systems that document the integration process for the level I of interface integration defined by TriTech's response to the RFP. The Client is responsible for any services or software needed from such Third Party Systems to -allow for interaction with the Third Party System API or for connecting to TriTech Interfaces Software in the absence of a Third Party API. (Note: The scope of functionality for these custom interfaces is limited to 1) the capability of the - TriTech System being interfaced and 2) the Application Programming Interface (API) capabilities of the external system being interfaced. j High level. descriptions of each ofthe,interfaces belowwill become the basis for the scope of detailed requirements, described in the.OSD. Any changes in the requirements documented in the System OSDs, post approval of the OSDs are subject to formal Change The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software 46 Systems. / 02015 TriTech Software Systems `rot. _� I �[ P . — - ./ / g �2 _. Appendix D - Custom TriTech Interfaces iNote: The Client is responsible for coordinating the development of the vendor side of all interfaces ; to the third party applications for the interfaces that the vendor is not a TriTech Subcontractor, based on the Purchase Agreement. ! List of Project's Custom Interfaces (OSDs to be provided): a) Brazos Citation Import citation related data into TriTech Inform RMS. The following form(s) are included as part of this effort: • Traffic Ticket • Traffic Ticket Warning Citation Note: Any additional form(s) support, will need to be reviewed and scoped and is not part of this effort. TriTech's Automated Brazos Citation Importer is a Windows Service providing one-way data transfer from the Brazos system to Inform RMS. TriTech's Automated Brazos Citation Data Importer Interface will monitor a shared network directory for new submissions. Once detected the data will be transformed for import into Inform RMS. Citation data is to be published by Brazos system to files in a shared network directory where the data is available for import by Inform RMS. The data is to be provided in fully documented, machine-readable XML. As proposed, the TriTech Automated Brazos Citation Importer supports data imports in a single format. PDF files can be part of the import. A single style sheet is configured to map the relevant data elements from the Brazos system output file to the Inform RMS Citation data structure. Data not supported by the Inform RMS data model will not be imported. The TriTech Automated Brazos Citation Importer provides master indices resolution for Citation data imported into Inform RMS. The citation data imported from the Brazos system is available to access through the Inform RMS client upon successful import into Inform RMS. The Automated Brazos Citation Importer supports a multi jurisdiction environment. It is assumed that all agencies utilizing the Brazos system are sharing the same Inform server as the Client and utilizing the same version and format of the Brazos software. The Brazos Citation Importer can look for two folders, one folder for the County and another folder for the City as long as the files are in the same format and are on the same RMS server. Deployment and operation of the TriTech Brazos Citation Importer, as described here, does not require modifications to existing TriTech products and no product modifications are proposed. The TriTech Automated Brazos Citation importer and associated data store reside on a conventional or virtualized server platform compliant with TriTech's approved hardware and software specifications. TriTech's planned scope of work assumes the shared directory used by the Brazos system for depositing exported files will be on the same local area network as Inform RMS or will be accessible from the Inform RMS network. The TriTech Cost Proposal assumes the client will support any component and/or integration testing required to facilitate the timely delivery of the TriTech Automated Brazos Citation Importer. TriTech's Cost Proposal does not include any products, services, or other fees that might be assessed by any third -party for enabling the TriTech Automated Citation Importer as described. The contents of this material are confidential and proprietary to TriTech Software Systems and may not 11 be reproduced, published or disclosed to others without the prior written consent of TriTech Software 47 Systems. n 02015 TriTech Software Systems Vol. Appendix D - Custom TriTech Interfaces b) TxDOT Crash Reporting TriTech's Cost Proposal includes licensing, deployment, initial configuration and maintenance support of a unidirectional import utility that ingests motor vehicle crash data captured using TxDOT Crash system to the Inform RMS database. The import feature is designed to eliminate redundant data entry at the RMS for crash information captured while using TxDOT Crash system. TriTech's Automated Motor Vehicle Crash Data Importer is a Windows Service providing one-way data transfer from the TxDOT Crash system to Inform RMS. TriTech's Automated Motor Vehicle Crash Data Importer Interface will monitor a shared network directory for new submissions. Once detected the data will be transformed for import into Inform RIMS. Crash data is to be published by TxDOT Crash system to files in a shared network directory where the data is available for import by Inform RMS. The data is to be provided in fully documented XML file format. As proposed, the TriTech Automated Crash Data Importer supports data imports in a single format. A single style sheet is configured to map the relevant data elements from the TxDOT Crash system output file to the Inform RMS DMV data structure. Data not supported by the Inform RMS data model will not be imported. Updates from TxDOT to existing records in Inform RMS is not included as part of this proposal. If updates are desired, further conversation needs to occur for documenting and scoping that functionality. The TriTech Automated Motor Vehicle Crash Data Importer provides master indices resolution for crash data programmatically imported into Inform RMS. The crash data imported from the TxDOT Crash system is available to access through the Inform RMS client upon successful import into Inform RMS. Deployment and operation of the TriTech Automated Crash Data Importer, as described here, does not require modifications to existing TriTech products and no product modifications are proposed. The TriTech Automated Crash Data Importer and associated data store reside on a conventional or virtualized server platform compliant with TriTech's approved hardware and software specifications. TriTech's planned scope of work assumes the shared directory used by the TxDOT Crash system for depositing exported files will be on the same local area network as Inform RMS or will be accessible from the Inform RMS network. The TriTech Cost Proposal assumes the Client will support any component and/or integration testing required to facilitate the timely delivery of the TriTech Automated Crash Data Importer. The proposed TriTech Automated Crash Data Importer assumes that all data entry occurs in the TxDOT Crash system. Timely approval of interface documentation, support of remote deployment tasks (to include providing secure and reliable remote network access for installation, training and support) and execution of any acceptance testing will be incorporated as part of any resulting contract with TriTech. TriTech's Cost Proposal does not include any products, services, or other fees that might be assessed by any third -party for enabling the TriTech Automated Crash Data Importer as described. The TriTech Automated Crash Data Importer is compatible with the version of Inform RMS proposed in TriTech's cost proposal. Assumptions: TriTech will create a Functional Specifications document that must be approved by the Client and TxDOT prior to beginning any development on the utility. No modifications to any existing TriTech product or database will be required for this utility. All installation and any associated training will be performed remotely by a TriTech technician. TriTech will only provide documentation sufficient for a TriTech technician to install and configure the application remotely. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others -without -the prior-writtemconsent•of-TriTech. Software', 48 Systems. ©2015 TriTech Software Systems Vol. Pg._/_`�� Appendix D - Custom TriTech Interfaces The TxDOT crash system will supply data formatted as fully documented XML files that are loaded to a file share; Integrated Solution Framework will be used. c) Protective Order A unidirectional interface that imports Warrant information for Protective Orders captured in Tyler Technologies, Odyssey application. TriTeclis Automated Warrant Importer is a Windows Service providing one-way data transfer from Tyler Technologies to Inform RMS. TriTech's Automated Warrant Data Importer Interface will monitor a FTP directory for new and updated submissions. Once detected the data will be transformed for import into Inform RMS. The data is to be provided in fully documented XML file format. As proposed, the TriTech Automated Warrant Importer supports data imports in a single format. A single style sheet is configured to map the relevant data elements from Tyler Technologies output file to the Inform RMS Warrant data structure. Data not supported by the Inform RMS data model will not be imported. The TriTech Automated Warrant Importer provides master indices resolution for Warrant data imported into Inform RMS. The Warrant data imported from Tyler Technologies is available to access through the Inform RMS client upon successful import into Inform R S. Additionally, the interface will support Disposition Status, Date Issued, and Expiration Date warrant updates to the Inform RMS. Updates being submitted must contain a unique identifier in order to update the existing record in Inform RMS. Deployment and operation of the TriTech Warrant Importer, as described here, does not require modifications to existing TriTech products and no product modifications are proposed. The TriTech Automated Warrant Importer and associated data store reside on a conventional or virtualized server platform compliant with Tri fech's approved hardware and software specifications. TriTech's planned scope of work assumes the shared directory used by the third party system for depositing exported files will be on the same local area network as Inform RMS or will be accessible from the Inform RMS network. The TriTech Cost Proposal assumes the client will support any component and/or integration testing required to facilitate the timely delivery of the TriTech Automated Warrant Importer. TriTech's Cost Proposal does not include any products, services, or other fees that might be assessed by any third -party for enabling the TriTech Automated Warrant Importer as described. d) Warrant A unidirectional interface that imports Warrant information for Class A, B, C, and felony warrants captured in Tyler Technologies, Odyssey application. TriTech's Automated Warrant Importer is a Windows Service providing one-way data transfer from Tyler Technologies to Inform RMS. TriTech's Automated Warrant Data Importer Interface will monitor a FTP directory for new and updated submissions. Once detected the data will be transformed for import into Inform RMS. The data is to be provided in fully documented XML file format. As proposed, the Tri Tech Automated Warrant Importer supports data imports in a single format. A single style sheet is configured to map the relevant data elements from Tyler Technologies output file to the Inform RMS Warrant data structure. Data not supported by the inform RMS data model will not be imported. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software 49 Systems. ®2015 TriTech Software Systems I vol, l -g. -1 i Appendix D - Custom TriTech Interfaces The TriTech Automated Warrant Importer provides master indices resolution for Warrant data imported into Inform RMS. The Warrant data imported from Tyler Technologies is available to access through the Inform RMS client upon successful import into Inform RMS. Additionally, the interface will support Warrant Status and Status Date and Time warrant updates to the Inform RMS. Updates being submitted must contain a unique identifier in order to update the existing record in Inform RMS. Deployment and operation of the TriTech Warrant Importer, as described here, does not require modifications to existing TriTech products and no product modifications are proposed. The TriTech Automated Warrant Importer and associated data store reside on a conventional or virtualized server platform compliant with TriTech's approved hardware and software specifications. TriTech's planned scope of work assumes the shared directory used by the third party system for depositing exported files will be on the same local area network as Inform RMS or will be accessible from the Inform RMS network. TriTech's Cost Proposal does not include any products, services, or other fees that might be assessed by any third -party for enabling the TriTech Automated Warrant Importer as described. c) Two -Way Interface with Tyler Technology Odyssey Jail Manager A bidirectional interface that will share arrest information with Tyler Technologies, Odyssey Jail Manager. In order to provide that integration, TriTech will develop an arrest publisher and an arrest importer. Arrest Publisher: The Publisher will provide a defined set of data Upon user initiated action. Once a record is ready for submission to Tyler Technologies, the user will perform an action to indicate that the record is to be sent to Tyler Technologies. The published data will be placed on a FIT site for consumption by Tyler Technologies in an XML file format. Each record published will contain both a record type and a unique source record identifier that is based on the primary key of the parent record in Inform RMS. TriTech will re -send the entire record following modification to the record. The Publisher utility will maintain a log file that will identify any file 1!0 errors encountered during its operation. Arrest Importer: The Automated Arrest Importer is a Windows Service providing one-way data transfer from Tyler Technologies to Inform RMS Arrest module. TriTech's Automated Arrest Data Importer Interface will monitor a FTP directory for new submissions. Once detected the data will be transformed for import into Inform RMS. Arrest data is to be published by Tyler Technologies to an FTP directory where the data is available for import by Inform RMS. The data is to be provided in fully documented XML file format. As proposed, the TriTech Automated Arrest Importer supports data imports in a single format. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software 50 Systems. 02015 TriTech Software Systems vol. 1 f / Appendix E - Subcontractor(s) Statement(s) of Work A single style sheet is configured to map the relevant data elements from Tyler Technologies output file to the Inform RMS Arrest data structure. Data not supported by the Inform RMS data model will not be imported. The TriTech Automated Arrest Importer provides master indices resolution for Arrest data imported into Inform RMS. The Arrest data imported from Tyler Technologies is available to access through the Inform RNIS client upon successful import into Inform RMS. General: Deployment and operation of the TriTech Arrest Interface, as described here, does not require modifications to existing TriTech products and no product modifications are proposed. The TriTech Arrest Interface and associated data store reside on a conventional or virtualized server platform compliant with TriTech's approved hardware and software specifications. Tri fech's Cost Proposal assumes the client will support any component and/or integration testing required to facilitate the timely delivery of the interface. Tri fech's Cost Proposal does not include any products, services or other fees that might be assessed by any other third -party for enabling the integration as described- 13APPENDIXE - SUBCONTRACTOR(S) STATEMENT(S) OF WORK Not applicable. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTcch Software 51 Systems. — — 02015 TriTech Software Systems Lvol. to AGREEMENT BETWEEN COUNTY AND APPRAISER THIS DOCUMENT HAS IMPORTANT LEGAL CONSEQUENCES; CONSULTATION WITH AN ATTORNEY IS ENCOURAGED WITH RESPECT TO ITS COMPLETION OR MODIFICATION. THIS AGREEMENT is made on the 15'u day of March, 2016. Between the COUNTY: BRAZOS COUNTY, TEXAS c/o Brazos County Commissioners' Court Attention: County Judge 200 South Texas Ave., Ste. 332 Bryan, Texas 77803 and the APPRAISER: Steve Lovett %0VE+}" w ne II e for the following PROJECT: Conduct a market value appraisal of C. W. Henry tract, 123.6 acres of land located along Long Trussell Road at the Navasota River The COUNTY and APPRAISER agree as set forth below. ARTICLE I APPRAISER'S RESPONSIBILITY 1.1 APPRAISER'S SERVICE 1.1.1 The APPRAISER'S services consist of those services performed by the APPRAISER, APPRAISER'S employees and the APPRAISER'S consultants as enumerated in Articles 2 and 3 of this Agreement. 1.1.2 The APPRAISER'S services shall be performed as expeditiously as is consistent with professional skill and care and the orderly progress of the Work. The APPRAISER shall submit for the COUNTY'S approval a schedule for the performance of the APPRAISER'S services which may be adjusted as the Project proceeds and shall include allowances for periods of time required for the COUNTY'S review and for approval of submissions by authorities having jurisdiction over the Project. Time limits established by this schedule approved by the COUNTY shall not, except for reasonable cause, be exceeded by the APPRAISER or the COUNTY. Agreement Between County and APPRAISER V V 1. _ trj �` Page I of 5 ARTICLE II SCOPE OF APPRAISER'S BASIC SERVICES 2.1 DEFINITION 2.1.1 The APPRAISER'S Basic Services consist of conducting a market value appraisal of C. W. Henry tract, 123.6 acres of land located along Long Trussell Road at the Navasota River ARTICLE III ADDITIONAL SERVICES DELETED INTENTIONALLY ARTICLE IV COUNTY'S RESPONSIBILITY 4.1 The COUNTY shall provide full information regarding requirements for the Project. 4.2 The COUNTY shall designate a representative authorized to act on the COUNTY'S behalf with respect to the Project. The COUNTY, or such authorized representative, shall render decisions in a timely manner pertaining to documents submitted by the APPRAISER in order to avoid unreasonable delay in the orderly and sequential progress of the APPRAISER'S service. 4.3 The COUNTY shall give prompt written notice to the APPRAISER if the COUNTY becomes aware of any fault or defect in the Project or non-conformance with the contract documents. Any delay by the COUNTY in providing said notice shall not constitute a waiver, a bar or act to estop the COUNTY from exercising any of its rights under this contract. 4.4 Examine all studies, reports, sketches, drawings, specifications, proposals and other documents presented by the APPRAISER, obtain advice of an attorney, insurance counselor and other consultants as the COUNTY deems appropriate for such examination and render in writing decisions pertaining thereto within a reasonable time so as not to delay the services of the APPRAISER. 4.5 The proposed language of certificates or certifications requested of the APPRAISER or the APPRAISER'S consultants shall be submitted to the APPRAISER for review and approval at least 14 days prior to execution. The COUNTY shall not request certifications that would require knowledge or services beyond the scope of this Agreement. ARTICLE V INTENTIONALLY DELETED. ARTICLE VI USE OF APPRAISER'S DRAWINGS, SPECIFICATIONS AND OTHER DOCUMENTS 6.1 The COUNTY shall be the absolute and unqualified owner of documents prepared pursuant to this Agreement by the APPRAISER with the same force and effect as if the COUNTY prepared same. Agreement Between County and APPRAISER Pg. Page 2 of 5 ��ol. ARTICLE V11 TERMINATION, SUSPENSION OR ABANDONMENT 7.1 This Agreement may be terminated by either party upon not less than fourteen (14) days written notice should the other party fail to substantially perform in accordance with the terms of this Agreement through no fault of the party initiating the termination. 7.2 If the COUNTY suspends the Project for more than thirty (30) consecutive days, the APPRAISER shall be compensated for services performed prior to notice of such suspension. 7.3 This Agreement may be terminated by the COUNTY upon not less than fourteen (14) days written notice to the APPRAISER in the event that the Project is permanently abandoned. If the COUNTY abandons the Project for more than ninety (90) consecutive days, the APPRAISER may terminate this Agreement by giving written notice. 7.4 If the COUNTY fails to give prompt written authorization to proceed with any phase of services after completion of the immediately preceding phase, the APPRAISER may, after giving seven (7) days written notice to the COUNTY, suspend services under this Agreement. 7.5 In the event of termination that is not the fault of the APPRAISER, the APPRAISER shall be compensated for services performed prior to termination, together with Reimbursable Expenses, if any, then due. 7.6 APPRAISER shall bill and collect all fees and costs for C. W. Henry tract, 123.6 acres of land located along Long Trussell Road at the Navasota River.; however, APPRAISER acknowledges that COUNTY is the client and all privity of contract exists between APPRAISER and COUNTY, and no third parties. ARTICLE VIII MISCELLANEOUS PROVISIONS 8.1 Unless otherwise provided, this Agreement shall be governed by the law of the principal place of business of the COUNTY. Venue for any dispute or disagreement regarding the terms of this Agreement shall be in Brazos County, Texas. 8.2 Causes of action between the parties to this Agreement pertaining to acts or failures to act shall be deemed to have accrued and the applicable statutes of limitation shall commence to run not later than either the date of Substantial Completion, or the date of issuance of the final Certificate for Payment for acts or failures to act occurring after Substantial Completion. 8.3 The COUNTY and the APPRAISER, respectively, bind themselves, their partners, successors, assigns and legal representatives to the other party to this Agreement and to the partners, successors, assigns and legal representative of such other party with respect to all covenants of this Agreement. Neither the COUNTY nor the APPRAISER shall assign this Agreement without the express written consent of the other party. 8.4 This Agreement represents the entire integrated agreement between the COUNTY and the APPRAISER and supersedes all prior negotiations, representations or agreements, either written or oral. This Agreement may be amended only by written instrument signed by both the COUNTY and the APPRAISER. Agreement Between County and APPRAISHR 3 i Page 3 or 8.5 Nothing contained in this Agreement shall create a contractual relationship with or a cause of action in favor of a third party against either the COUNTY or the APPRAISER. 8.6 COMPLIANCE AND STANDARDS. The APPRAISER agrees to perform the work hereunder in accordance with generally accepted standards applicable thereto, and shall use that degree of care and skill commensurate with the profession to comply with all applicable state, federal and local laws, ordinances, rules and regulations relating to the work to be performed hereunder and the APPRAISER'S performance. 8.7 INDEMNIFICATION: APPRAISER shall save and hold harmless the COUNTY from and against any and all claims and liability due to activities of the APPRAISER, its agents or employees, performed under this Agreement and which result from any negligent act, error, or omission of the APPRAISER, or of any person employed by the APPRAISER. The APPRAISER shall also save harmless the COUNTY from and against any and all expenses, including attorney's fees which might be incurred by the COUNTY in litigation, or otherwise, resisting said claims or liabilities which might be imposed on the COUNTY as the result of such activities by the APPRAISER, its agents or employees. ARTICLE IX PAYMENTS TO THE APPRAISER 9.1 APPRAISER SHALL INVOICE FOR ALL SERVICES, COSTS AND FEES ASSOCIATED WITH THE PROJECT. ARTICLE X OTHER CONDITIONS OR SERVICES 10.1 INSURANCE 10.1.1 The APPRAISER shall file with the COUNTY a Certificate of Errors and Omissions Insurance having minimum limits of One Million and No/100 Dollars ($1,000,000.00) for each occurrence and annual One Million and No/100 Dollars ($1,000,000.00) aggregate. Such Errors and Omissions Insurance shall have a deductible not in excess of Two Hundred Thousand and No/100 Dollars ($200,000.00) self-insured. Such Certificate shall bear the endorsement "Not to be canceled without thirty (30) days prior notice to BRAZOS COUNTY, TEXAS." The APPRAISER shall maintain the Errors and Omissions Insurance at all times this Agreement is in effect and for a period of five (5) years after completion of the Project. Failure to maintain the required insurance shall be deemed to be a material breach of this Agreement. 10.1.2 The APPRAISER shall also provide Worker's Compensation, automobile and comprehensive general liability policies. The APPRAISER shall deliver the insurance certificates to the COUNTY. The coverage provided herein shall contain an endorsement providing thirty (30) days notice to the COUNTY prior to any cancellation of coverage. Said coverage shall be written by an insurer acceptable to the COUNTY and shall be in a form acceptable to the COUNTY. If the APPRAISER has canceled or allowed to lapse any of these insurance policies then the COUNTY may pay for such insurance and may hold the amount of such payment out of the APPRAISER's fees or be otherwise reimbursed. Failure to maintain the required insurance shall be deemed to be a material breach of this Agreement. Agreement Between County and APPRAISER .�O I— 1 — Pg j� Page 4 of 5 This Agreement entered into as of the day and year first written above. The undersigned officers and/or agents of the parties hereto are the properly authorized officials and have the necessary authority to execute this Agreement on behalf of the parties hereto, and each party hereby certifies to the other that any necessary resolution extending said authority have been duly passed and arc now in force and effect. BRAZOS COUNTY, TEXAS APPRAISAL FIRM Duane Peters, County Judge by: Steve Lovett Principal Acting by and through the authority of the Brazos County Commissioners Court Attest: County Clerk Approved as to Form: Assistant County Attorney Agreement Between County and APPRAISER SJ;��, t-lg _�� Page 5 of 5 _'"'t' VETT &ASSOCIATES APPRAISALS, BROKERAGE & RIGHT-OF-WAY ACQUISITIONS Wednesday, March 9th, 2016 Mr. Darrell Kolwes Via Email Land Agent Brazos County 2716 State Highway 21 West Bryan, Texas 77803 Re: Long Trussell Bridge project, Brazos County, Texas Dear Mr. Kolwes: Upon your authorization, I will prepare an appraisal of the C. W. Henry tract, BCAD#14712, being 123.61 acres of land located along Long Trussell Road at the Navasota River. The purpose of the appraisal will be to estimate the total compensation due the property owner for the fee rights to be acquired by Brazos County for the Long Trussell Road Bridge project. You will be the client and intended user. The appraisal will be an independent estimate of market value; and, the payment of the fee shall not be contingent upon any value estimate reported. The appraisal will be prepared in compliance with the Uniform Standards of Professional Appraisal Practice (USPAP). It is understood the fee for the appraisal will be $2,250, and will be due upon delivery of three copies of the report addressed to you. Delivery of the appraisal will be within 21 days of receipt of the parcel plat(s). Thank you for the opportunity to be of service. Sincerely yours, Steve Lovett State Certified General Real Estate Appraiser Certificate No. TX -1322517-G 3600 Lovett Lane, College Station, Texas 77845 • Tele: 979.774.8943 • Fax: 979.774.7133 • Email: stevelovett@verizon.net Fo - pg. �3 `� 2 o LexisNexis ® Lexis Advance® Subscription Amendment for State/Local Government—with Library Patron Access "Subscriber" Name: BRAZOS COUNTY Account Number: 127WVD "LN": LexisNexis, a division of RELX Inc. 1. Amendment This Amendment ("Amendment") amends and supplements the terms of the Lexis Advance Subscription Agreement previously entered into between LexisNexis, a division of RELX Inc. ("LN") and Subscriber (the "Subscription Agreement"). This Amendment shall also serve as Subscriber's acceptance of the new General Terms and Conditions for Use of the Online Services effective September 1, 2010 set forth at www.lexisnexis.com/terms/general. 2. Certification of Use of Lexis Advance by Librarians/Library Staff 2.1 Subscriber certifies that the number of government professionals in Subscriber's organization who will have access to Lexis Advance is as set forth below. A "Government Professional User' Is defined as a librarian or researcher who is employed by the Subscriber Number of Government Professional Users: 1 2.2 Each LN ID is issued for the individual use of the Government Professional User to whom it is assigned. 2.3 If Subscriber, at the time of signing this Amendment has 11 or more Government Professional Users, then Subscriber is required to notify LN if the number of Government Professional Users falls below 11. Subscriber shall, within 30 days of the staffing change, notify LN in writing. 2.4 Subscriber acknowledges that the pricing and menus provided to Subscriber in this Amendment depend in part on the number of Government Professional Users in Subscriber's organization. Subscriber certifies that as of the date Subscriber signs this Amendment there are the number of Government Professional Users in Subscriber's organization (the "Reference Number) as Subscriber has specified above. (i) At LN's request from time to time, Subscriber will certify in writing the then -current Reference Number. (ii) If there is a change in the Reference Number during the Term, LN may, in its sole discretion on at least 30 days prior written notice to Subscriber, increase or decrease the Monthly Commitment by an amount that does not exceed, on a percentage basis, the change in the Reference Number 3. Use of Lexis Advance by Library Patrons 3.1 In addition to use of Lexis Advance by Subscriber's Government Professional Users, Subscribers "Authorized Users" may also include Subscribers library patrons who are accessing Lexis Advance through the use of on-site library terminals (up to the specified number on Schedule 1) at Subscriber's location(s) listed below (each a "Patron").Non-Patrons of the library or any other persons who are not Government Professional Users are prohibited from receiving access to or use of Lexis Advance under this Amendment. Remote access to Lexis Advance (e.g., via dial-up or other remote connection) is strictly prohibited. 300 E 26TH ST BRYAN,TX 3.2 Subscriber acknowledges and agrees that each Patron may access Lexis Advance only from a library terminal that includes an acceptance screen (as the same is provided by LN) which requires the Patron to accept the LexisNexis General Vol. _�y. Pg, opv__. Terns and Conditions of Use. Each Patron must activate an "I Accept" button following the terms and conditions before the Patron will be permitted to access Lexis Advance. If the Patron clicks on "Do Not Accept", "Cancel" or otherwise fails to click "I Accept", then the Patron will not have access to Lexis Advance. 3.3 Subscriber's contact and technical information for its library terminals is set forth in the attached Schedule I. 4. Lexis Advance Product and Charges 4.1 This Section 4 amends the Subscription Agreement with respect to the Lexis Advance product offering described below. The term of Subscriber's commitment for the Lexis Advance product offering will begin upon the date Subscribers billing account ("Account Number) is activated ("Activation") and will continue for the last period set forth in Section 4.2 below (the "Committed Term'). Subscriber may not terminate this Amendment under Section 5.2 of the General Terms during the Committed Term. In addition, Subscriber may terminate this Amendment during the Committed Term for a material breach by LN that remains uncured for more than 30 days after LN receives written notice from Subscriber identifying a specific breach. If Subscriber terminates this Amendment pursuant to this Section, then Subscriber will pay all charges incurred up to the date of termination. Upon the expiration of the Committed Term, all access to and use of Lexis Advance by Subscriber will be billed in accordance with the applicable then -current Price Schedule. �r-�..r.'u�tr'�P'`s: 3r<`.-v:�:,.'�'. ;.:�.� rt".z Lexis AGvan2c1Content& Fcaturc Ii&r Ilse t Product SKU Number Number of Users mirror patron content 1 ❑ See attached Rider No. 1 for additional Content & Features .-�*«kms, %� v_•r° Lex is°Advance.content &.Feat&es'IF& Use by Llbril6 Patrons _."V t ' � .� ( "('1viH '. } %i ii •.S L « . r Monthl�Coniml�=tmYe`rit'. ,�, 'k+§`"' "'>~• 4/1/2016 - 4/30/2016 Product SKU Number 730.96 Number of Users National Primary Plus 1011510 2 TX Practice Library 1010629 2 TX Family Law Practice & Procedure 1010481 2 ❑ See attached Rider No. 1 for additional Content & Features 4.2 In exchange for access to the Lexis Advance Content, Feature and/or Service set forth in Section 4.1 above, Subscriber will pay to LN the following amount (the "Monthly Commitment") during the periods set forth below. y _±wr ! 3 S 1.f,- Y : f R uT.t 1�{<a I. rj� b�r�: •Commlttbtl Term �' ' t ' � .� ( "('1viH '. } %i ii •.S L « . r Monthl�Coniml�=tmYe`rit'. ,�, 'k+§`"' "'>~• 4/1/2016 - 4/30/2016 709.67 5/1/2016 - 4/30/2017 730.96 4.3 During the Term, LN may make content and features available to Subscriber that are not included in the Lexis Advance Content described above which will be offered to Subscriber at an additional charge ("Alternate Materials"). Subscriber will be under no obligation to access and use the Alternate Materials, or to incur additional fees beyond the Monthly Installment. If Subscriber elects to access the Alternate Materials by initialing below, Subscriber will be notified that additional charges will apply before the Alternate Materials is displayed. If Subscriber proceeds to access the Alternate Materials, Subscriber will pay the then current, transactional charge(s) for the Alternate Materials that is displayed at the time of access. (Initial) Subscriber elects access to the Alternate Materials Vol. _t�W Pg._r%5�_ 4.4 LN may temporarily suspend access to Lexis Advance until all unpaid amounts are paid in full. No claims directly or indirectly related to this Amendment with respect to amounts billed or payments made under this Amendment may be initiated by Subscriber more than 6 months after such amounts were first billed to Subscriber. 5. Closed Offer The prices and other terms are subject to change if Subscriber has not submitted a signed original or copy on or before 3/28/2016. 6. Confidential Information Subject to any state open records or freedom of information statutes, this Amendment contains confidential pricing information of LN. Subscriber understands that disclosure of the pricing information contained herein could cause competitive harm to LN, and will receive and maintain this Amendment in trust and confidence and take reasonable precautions against such disclosure to any third person. This Section 5 will survive the termination or expiration of this Amendment. 7. Support and Training During the Term, Subscriber, with the support of LN, agrees to encourage the effective use of Lexis Advance through: (a) Mandatory basic training in the use of Lexis Advance by LN for all Authorized Users; (b) Meaningful participation in additional ongoing programs presented by LN to update and train Authorized Users, (c) Authorize the periodic distribution of memos or other communications by LN and/or Subscriber to Authorized Users, and (d) The periodic review with LN of Subscribers Authorized User's use of materials and training under this Agreement. 8. Miscellaneous 8.1 This Amendment does not bind either party until it has been accepted by both parties. Subscriber may accept this Amendment by signing below. LN will accept this Amendment by providing Subscriber with access to Lexis Advance or by signing below. 8.2 If Subscriber issues a purchase order in connection with the Agreement, Subscriber acknowledges and agrees that the purchase order shall be for Subscribers internal purposes only and shall not modify or affect any of the other terms or conditions for access to the Online Services. LEXISNEXIS WILL NOT ACCEPT ANY CHANGES, CORRECTIONS OR ADDITIONS TO THIS AMENDMENT UNLESS SUCH CHANGES ARE EXPRESSLY ACCEPTED BY LN IN WRITING. SUCH CHANGES WILL HAVE NO LEGAL EFFECT. Vol. �23 y pg _� AGREED TO AND ACCEPTED BY: Subscriber: BRAZOS COUNTY TBE COMPLETED BY SUBSCRIBER] Authorized Subscriber Signature. Printed Name: ( e cc, Job Title: O 1 l� Date: '% 22 1 LexisNexis, a division of RELX Inc. BY Authorized Signature: Name: Job Title: Date: N D: SLGov-LexisAdv ncePatroMocess-Sept2015 ID#4841-7360-3879 02015 LebsNeris. All lights reserved. �.. Page 4 of 7 Ivol. _. Pg. �� CUSTOMERINFORMATION;(PleasetypeorprI Organization Name: (Full Legal Name BRAZOS COUNTY Billing Frequency: ® Monthly ❑ Annually Physical Address Invoice Address Street Address: 300 E 26TH ST City: BRYAN State: TX Zip: 77803 County: BRAZOS COUNTY Telephone: 979-492-3190 Fax: Parent Company: (if applicable) Type of Organization: Library Law Library Employer Identification Number Organization Web Address: Tax Exempt: Yes (attach Sales Tax Exemption Certificate) ❑ No MSA. ❑ Yes ® No Tax ID No: State Contract No: (If applicable) PO No: (If applicable) Contacts: Name Telephone Email Installation: Bryce Ratcliffe 979-3614161 BRatcliffe@brazoscountytx.gov Billing: Beverly Murph 979-361-4350 bmurph@brazoscountytx.gov Policy/Legal LESLIE CONTRERAS 979-361-4294 LCONTRERAS@BRAZOSCOUNTYTX.GOV Notification: SchedulinglTraining: LESLIE CONTRERAS 979-361-4294 LCONTRERAS@BRAZOSCOUNTYTX.GOV Name Telephone Super Admin: Bryce Ratcliffe 979-361-4161 Email IP Address BRatcliffe@brazoscountytx.gov J ND: SLGovt-LedsAdvaneePatronAcrosaSep@015 100 4841-7360.3879 �- ® 2015 LedsNeris. All nghts reserved. Page 5 0/f Val., SI Pg ��'_ ID HOLDERS' NAMES ID HOLDERS' ID HOLDERS' EMAIL ADDRESSES LOCATION/ADDRESS (additional Sheet attached El) I TITLE SIPOSITIONS Vol./q, pg.— �� I SCHEDULEI LN requires accurate IP information from the library. The technical contact at the library will need to set up static IP addresses on the patron access machines. Information needed to set up Patron Access: 1. Law LibraryName: BRAZOS COUNTY 2. Name of Technical Contact at Law Library Bryce Ratcliffe 3. Phone Number, email and availability of Technical Contact at Library 979-361-4161 BRatcliffe(cDbrazoscountvtx.gov Number of terminals in contract: 2 Terminal 1 Terminal 4 Static IP Address: 209.189.241.234 Static IP Address: Terminal 2 Terminal 5 Static IP Address: 209.189.241.234 Static IP Address: Terminal 3 Terminal 6 Static IP Address: Static IP Address: For additional terminal locations check here ❑ All rights reserved. Page 7 of 7 Vol, 'Uel _ Pg.—f0 05 Lexi s N exi sQ; SUBSCRIPTION PLAN AMENDMENT FOR PATRON ACCESS (Electronic Consent — Option Version) "Subscriber": Brazos County "LN": LexisNexis, a division of Reed Elsevier Inc. This Subscription Plan Amendment ("Amendment") amends and supplements the terms of the Subscription Agreement either previously entered into or executed simultaneously herewith between LN and Subscriber (the "Agreement'). This Amendment shall also serve as Subscriber's acceptance of the new General Terms & Conditions for Use of the Online Services effective September 1, 2010 set forth at www lexisnexis.com/terms! eq neral. 1. TERM The term of this Amendment will begin (a) on the date Subscribers billing account (a "Billgrcup") is activated ("Activation") if Subscriber is a new LN customer, or (b) subject to Section 5, on the first day of the calendar month immediately following the execution of this Amendment and delivery of it to LN if Subscriber is an existing LN customer, and will continue until the last day of the final Commitment Period referenced in Section 4.1 (the "Term"). 2. AUTHORIZED USERS; LOCATION This Amendment relates only to the Subscribers Billgroups and locations (the "Participating Billgroups") set forth below and the Authorized Users under the Participating Billgroups. "Authorized User" shall have the meaning set forth in the Agreement. In addition, the librarian will provide patrons access to the Preferred Pricing Materials (defined below). All access shall be limited to patrons using terminals (up to the specified number) at the location(s) listed below. Non -patrons of the library and inmates are prohibited from receiving access to and use of the Online Services under this Amendment. Remote access (e.g., via dial-up or other remote connection) is strictly prohibited. Subscriber is obligated to ensure that identification numbers are not disclosed to the patrons or other third parties. PARTICIPATING 13ILLGROUP # LOCATION ADDRESS, CITY ANO,STATE #OF TEREI1NALs 127 W V D 300 E 26"' St. 2 Bryan, TX 77803 CDI'000 Pull (b) 3. MONTHLY SUBSCRIPTION CHARGE During the Term, the Monthly Subscription Charge in Section 3 of the then -current applicable price schedule (the "Price Schedule") will be waived. 4. PREFERRED PRICING MATERIALS AND CHARGES 4.1 In consideration of Subscribers payment to LN of the monthly commitment amounts specified below (the "Monthly Commitment"), and subject to Section 4.3 below, the Participating Billgroups will be provided access to and use of certain Materials, products, services and features, identified below by source/menu number (the "Preferred Pricing Materials"), available in the lexis.comW service or the LN Online Services accessed via proprietary software (the "Classic Online Services") At no additional charge, the Participating Billgroups may do offline printing and online printing of the Preferred Pricing Materials. If your subscription includes Research Advantage, then your access to and use of Research Advantage shall be subject to and governed by the additional terms and conditions set forth in the software media at the time of its installation. NO: SLGov1SubscriptionPlanAmd PatronAccesS-EleotrcniCConsent-Option-OCt2010 D 2010, LexisNexis, a division of Reed Elsevier Inc. All rights reserved. IDp 4835.3095.9367 — Page l of 4 PREFERRED PRICING -MATERIALS SOURCE/MENU SHEPARDS NUMBER (a) kalionai Primary CDI'000 Pull (b) Matlhow 11ender Tcxm GuiJcS M'f IXOi (C) Matthew' uenAer T2XM Pa1Ii1V 1%n"Tx1 t (d) to $ (e) to $ NO: SLGov1SubscriptionPlanAmd PatronAccesS-EleotrcniCConsent-Option-OCt2010 D 2010, LexisNexis, a division of Reed Elsevier Inc. All rights reserved. IDp 4835.3095.9367 — Page l of 4 COMMITMENT PERICD S MONTHLY COMMITMENT Beginning 5/1/2014 to 4/30/2015 $ $ 689.01) Beginning 5/1/20[5 to 4/30/2016 $ 709.67 Beginning 5!1!2016 to 413012017 $ 730.96 Beginning to $ Beginning to $ NO: SLGov1SubscriptionPlanAmd PatronAccesS-EleotrcniCConsent-Option-OCt2010 D 2010, LexisNexis, a division of Reed Elsevier Inc. All rights reserved. IDp 4835.3095.9367 — Page l of 4 4.2 The Monthly Commitment may include a multi -media discount based on Subscriber's current print and/or CD-ROM subscriptions. In the event Subscriber discontinues any of its existing print or CD-ROM subscriptions, LN reserves the right to eliminate the multi -media discount and increase the Monthly Commitment. 4.3 During the Term, LN will review Subscriber's actual monthly use of the Preferred Pricing Materials calculated in accordance with the Price Schedule ("Actual Use"). In the event the Actual Use exceeds 15 times the Monthly Commitment for three consecutive months, LN reserves the right to increase the Monthly Commitment upon 30 days prior written notice to Subscriber. In the event of an increase pursuant to this Section 4.3, Subscriber's sole and exclusive remedy shall be termination of this Amendment upon 10 days prior written notice to LN. Subscriber must exercise the foregoing right of termination within 90 days of receipt of such notice of increase. 4.4 During the Term, the Monthly Commitment will be billed in lieu of the Information Charges specified in Section 1 of the Price Schedule for all access to and use of the Preferred Pricing Materials. 4.5 In exchange for the favorable pricing set forth in this Amendment, during the Term Subscriber agrees to maintain print, CD-ROM or similar products currently licensed to or provided to Subscriber by LN or its affiliated companies, or Subscriber must maintain an equivalent spending level for those products. If Subscriber's print, CD-ROM or similar products are not maintained or the spending level for those products declines, LN reserves the right to adjust the amounts payable under this Amendment upon at least 30 days prior written notice to Subscriber. 4.6 LN will issue identification numbers to Subscriber for purposes of providing access to and use of the Preferred Pricing Materials by its patrons who agree electronically to abide by the terms and conditions of use for the LexisNexis Services. Subscriber will make available to each patron of the library the ability to agree to the LN terms and conditions via Subscriber's custom web page. 4.7 Subscriber shall set-up its system to require each patron to scroll through screens as designated by LN from time to time, which screens shall include the "Terms and Conditions of use for the LexisNexis Services". There must be an "Accept" button fallowing the terms and conditions, which the patron must activate before having access to the Preferred Pricing Materials. if the patron clicks on "Do Not Accept", "Cancel" or otherwise fails to click "Accept", then the patron shall not have access to the Preferred Pricing Materials. Subscriber shall notify LN in advance of implementation of its electronic system and provide LN with a demonstration of its operation. Subscriber will make any adjustments to its electronic system, as required by LN, if it does not meet the above requirements. 5. CLOSED OFFER The offer of LN contained herein is valid until April 29, 2014. In order to implement this Amendment by the first day of a calendar month, LN must receive this signed Amendment by the 20th day of the preceding month. 6. CONFIDENTIAL INFORMATION Subject to any state open records or freedom of information statutes, this Amendment contains confidential pricing information of LN Subscriber understands that disclosure of the pricing information contained herein could cause competitive harm to LN, and will receive and maintain this Amendment in trust and confidence and take reasonable precautions against such disclosure to any third person. This Section 6 will survive the termination or expiration of this Amendment. 7. MISCELLANEOUS 7.1 During the Term, use by and charges to the Participating Billgroups will not be eligible for other discounts or aggregation with the use of or charges for other billgroups. 7.2 During the Term, Subscriber may not terminate the Agreement. This Amendment may be terminated by Subscriber on the last day of any Commitment Period upon at least 30 days prior written notice to LN. This Amendment may also be terminated by Subscriber on 10 days prior written notice to LN in the event of any increase in the Monthly Commitment, excluding any increases listed in Section 4.1. To be effective, notice of termination pursuant to the preceding sentence must be given within 90 days of the increase. 7.3 UPON TERMINATION OR EXPIRATION OF THIS AMENDMENT, CONTINUED USE OF THE ONLINE SERVICES BY SUBSCRIBER IS GOVERNED BY THE AGREEMENT AND WILL BE BILLED IN ACCORDANCE WITH THE PRICE SCHEDULE. 7.4 All capitalized terms not defined herein will have the meanings ascribed to them in the Agreement, including the Price Schedule. 7.5 Subscriber's contact and technical information is set forth in the attached Schedule I Vol. _o_ pg.—" 7 6 Except as expressly modified by this Amendment, all other terms and conditions of the Agreement will remain in full force and effect and unaffected by this Amendment. In the event of a conflict or inconsistencies between the Agreement and this Amendment, this Amendment will control. AGREE 0 AND AC D BY: 6RA7.OS CO SUBSCRIBER Sr. �, v NAME: /1 I i1 iM1 �P_ 'U •S TITLE: "Aaej DATE: LexisNexis, a division of Reed Elsevier Inc. BY: NAME: TITLE: DATE: Pg. --V SCHEDULEI LN requires accurate IP information from the library to establish a connection to the Patron Access site (www.lexisnexis.com/patronaccess.). The technical contact at the library will need to set up static IP addresses on the patron access machines Remember, there is a 6 terminal limit for Patron Access. Information needed to set up Patron Access: 1. Law Library Name: Brazos County 2. Name of Technical Contact at Law Library 3. Phone Number, email and availability of Technical Contact at Library R-A� I ml L\UIG i �nv�u�eX�� b�a�co�n c � u�oAma�1 �usiv�e ss \Aouylf-' Number of terminals in contract: 2 For each Patron Access terminal: 1. Static IP address 2. LexisNexis at www.lexis.corn ID 3. LexisNexis at www.lexis.com password Terminal 4 a �1rTerminal 0� •�` lei Static IP Address: Static IP Address:' ID: ID: _ Password: _ Password: Terminal Terminal IP Address: 1 ° •� Static IP Address: Static ID: ID: _ Password: _ Password: Terminal 3 Terminal 6 Static IP Address: Static IP Address. ID: ID: Password: _ Password: �e'z Pg. �� taCDWW iO ib�iS2E UI Cf.�ybrlLdald Alarh 1E M16 L.M hName 158111 I"9n, --D1Yl Cm9a'n I i+rtw DeTnW,..rc Gm'vd LS/.'mv S�%rnr Geeuu, Ne YclaRct: I.N�ld ff GAL ORU45 �nf'.RWEIFAGN3Cn Wm IES 11:1 15mpMv[a i EXiixDEOCPfru511H Eii CVAVII:v lli ]%IX' i:a]:S.N IIA SI!ro FPIMWIS. GwomvPY 9FC I5NU Umyln CaM 15'0.'N CN ^.May ^wb l:rYN IY'LUCEAgr 1]IDma:nu ssn INcr:E w Cla> SUTNEPC Bt£M1D Mcr0R 00.: SN�m SS OALDRUu u;TY.EPERC%i^.0 3]iw 3EAr ] !`+Wpb\ iOrNEA; EVGm Lq]:114)HESr LWNT III, YOW M IIl1r5m 3'IAW"u4E tlwnm &onn U. S/n^vbm SH'A ib'LI�c P;•':J (ECD.. Ecc U gm6HM8 Dmmoalm Mn Ireti< xocda+ SdI.�NEM 3LEV0 u0rCP 0E' EW.m b 0>Ism UW MYCE:"EXGAUC.Y ISx MY I:Ad MrNfxrLV'.ECfO5: L6n]E5: 'YJtVilr/ I11, SmW 1:1:'tlm llitxx &WIDIu,VE f+wmSavu ECO UT S/IBWUSWA• wICISSN]S pPuu LFpg; Imwuwnmq !X:IIF roCIKq iMtt00.1f!DRIUIIC RUb' E.:E IBW SS JALOPU4 .a MUCEPfAG11LY um nv nl6 , lsm wRv. roiu E4lErnomsr ud:xG[sl cu++nn ummm nelmm ]I))wm aumxA4x ICr»mrxF:aw Ilrw.ar ;Sw IWaw LPL4LEPoSTIWLx1 Iimmu[.'m*WF M1GIf 4']vp IMCiCRNYDPAUIIC FIUp: SAEIOW S4ALPM E3� '•'T. Wf{%3PAL bN Itl9i PY 1 tOrH E.trEXLED5C6 r'J8NGE5I CJAnI:Y IaW.W 41.Y %9 Y. 3iIW 144E IL`e l:w Vrtvnl (I,WyU iIXY pin]Yav AP ECUVYEYr NIO.MWCiLL'M: IpDFLPPDe&E ES OA DFL DRLN IYYr MCE,EP64LCN IA9] ilb IIIA 0 ISx itlM'.. rOiu FMENCECCL]i'J$!IGFSr WAxrltt ]I!9'HW II1 ttfW IIf i15.m MN9.uI¢: _Qenme. WY.N ?n LL Fm 150,6 ieJ N DEroa; IlmmaWs wr:[ wcrs} TR ILUx5HI6SCx ttUID: DIPELMPNE W'NE1GNi Cw UGAL LD DPUN WiMWEM1-P L4llOx iib N9 U:a • i5E0 y4(na E%R\50' ,4'1 FT CWNIIM1 IIIE]r3W 11150.W tIEEUW .0 a0.A\VUF. Crwmmin Pp,.ly!K.ti Dm Pa tIC iL, Y+I iai Cwi,T AC 50 CR.x FfWH: 4Lm Mx INJNE PofA'p UA'NFASAI GEAR LUSRICAN(: S.SF SSI.iWOLS .m 0, lB. giUN UbrMWEFG P31xD 1]I: Iri 1131 a ImoPw iou DDENrcomfiuMrw n]c:Anmm unom {Lmm naem maw 44N: Icl..�a....m�v«Im Llw«,oP a3.N:+f ie. rlv{r, as:a aP.4 [tpoar i{mwapY. -avMa Ix W= xocwA. YNr1ER SGE dSDCW Ctf IGPLPedi 9 EKRFRLLDRIC>rvi' 4VIiMWERRiW 4pW rarer snEvcm cwr zxc[dr owmn uasx Iwm unW dR„CNuh Cn'. d5wlm uwvrR.lNeEWlm ree n..«n:m Fuu srurHEr'.c oE.w weRKAxr srN.w mote osuv Lam. unrt.mLEE.Rcutox 45 e5 ilv 4m I$ Ipw,w4m rarKr4iEwmcwlvs.HFsr carlrr luds,x udmm 45mm SP+NDxuaE. Gx+u+L,wirc rcuuxla roPo=]IC sr.uJ l:W lu rW SNAP ^,e f4rtl pL4GEi0A: ]2lwapcl =SaN IKY: bUy ADIC WEK iP.W S41S51LA flllM: DERRCM E{YERLGN}ri f3 WL0PUY vTr FKEr4iGµycll µa] 1r 31 I1W :I Ym9maa iarILERFNIIECLWiU4YGF5: WWIIrY 1}Aplx ]]l]]'A 4L'!W e=.,W wS: Raves A:, W.I =COUnwPTF Iw:5a1'4N) CRLamaei 1mx M nanE xocMp EiIC SYYMAU1aMApC iRM'SN:]5.'aN iWM. rf9 mf1 i1= LNa Ia GAL FE05 6 I.IR RYEPFR SVIGI Illai W:i i]1pl IP ]W SYF ia(ALrXrfn4EC LW]JS.ND E9r PiuRI1T IISaadm 11pZ.Mm S]19W PWHM4E CI,mmC.n9)n A:=rY �Me=11[NGA� DPAxvn E3 ra xPLmr NMq WYE W' -1+P IN]Li1YfNKlE SULL SYNTHETIC: AIE Ia 04LMFOS Ptl,b 4'SE 111 a5 1! bl pWn IIU:,4, TPu2 T f'K rVttnLSCCiruEsr tt'M7In tl Yyx 32Wm t1SYm oi dun.uE In+..a.u,N-'+v=.A;E umarcmN}rP iYd A:6 wxw +i9 fAas: rCxE .rGk b:Mv. d. MLV.NUPVOSE OPEASES>RIN W E LUBE NIIiMUT [FP Gy iM.W 1$I Iib IONeoIN Nb.I 11 d5� lia3llflfi\:EDCQtt U&gEdi I4 WW:Ir1"..Itrlp 5y 4"Yu MIM UII!m IWKESiP:uQE lu II, ttLHfl Ci NEE9'.-ASE Im IC W minro+>KL 1^ "y ' x 9. EdVIGVfli dl NMPLLYG lux IS ryy.+y�q SICm xa:v� 11)W �HI'_'MhM n0]t KCnA+ nEm _ '� A.. CMry d. Nvbal tlPm wati- I2m 15 f b' IIw0.frE 0LL PE4O4AL9KX aP AF'LPip\') µ,^. Y. �p 4YES.N) TANELGSir .W 3N 3%m541M P9PY4a9n f2fAm FrgYlIHOgMII'iwWT. h4rpy F% G 3 i5! WCx�i'ms NNI TAu bb Vj°+p ?1 ' HImm G\[(IFAgEMOVA{ryI4N9P AN Ne op as Yes r � W YR..13 NF WSi) WBq I f_c D]peg Y$qy C9yn F#Ia FtiTI 1W1 15111]86 is $I]106fm 51:9.6!0.]] W6d TxarC ❑mua\ ILubrcmu ro� b e � CUD11 i aio is Of/ JNy of �mL{iraly p16 b)' holding Llan poOd"D of .y (l7 l� 1 .5 J(,1do^� M - o - ri _ c F •n. z C - z o c � - - _ - � c L s 0 ID - o c O L — Z_ y — G L. L• J h _ C C N Z Z , h Vs N i Z z s JH `yes " N m C a 0 0 O m ID Ir ✓i Vol. _.�.� Sl Py+ 1�1 v `u c U O O O O O m E c Z C O �n in O m * N pp pj tp iF �--I l0 " N m C a 0 0 O m ID Ir ✓i Vol. _.�.� Sl Py+ 1�1 Brazos County Installation of 8000 Gallon Vertical Tanks Request for Proposal # 2016-171 Bryan,Texas ■ ■■ Er MADISON CONSTRUCTION, L.P. pg. Original Madison Construction, L.P. Installation of 8000 Galton Vertical Tanks Request for Proposals # 2016-171 BRAZOS COUNTY PURCHASING OFFICE Brazos County Administration Building 200 South Texas Ave., Ste. 352 Bid No.2016-171 Bryan, Texas 77803 Page 1 of 19 pages Telephone (979)361-4292 Proposals will be received, publicly opened, and acknowledged at 2:00 P.M., Thursdav, March 10. 2015 in the Brazos County Purchasing Department, Suite 352, Brazos County Administration Building, 200 South Texas Ave., Bryan, Texas. There will be a Pre -Proposal Conference at the Brazos County Road and Bride Department located 2617 HWY 21 West Bryan Texas 77803 at 2:00 p.m. on Tuesday, March 1, 2016. Release of RFP..................................................................Friday, February 19, 2016 Advertisement Dates............................................................. Friday, February 19, 2016 Friday, February 26, 2016 Pre -Proposal Conference..........................................Tuesday, March 1, 2016 @ 2:00 CST Deadline for Questions.................................................................Thursday, March 3, 2016 Proposal Submission Deadline.............................Thursday, March 10, 2016 @ 2:00pm CST Review/ Contract Evaluations/ Negotiations...........................................................March Anticipated Award..............................................................................March/April Anticipated Construction Start ........................... . ................................................April A. PROCUREMENT DELIVERY Brazos County will follow the Texas Local Government Code, Chapter 262.030 for this RFP process. The proposals will be opened on the date and time mentioned above and only the names of the proposers will be read aloud. The proposals will be distributed to the evaluation committee and this committee will evaluate each proposal according to the criteria set forth in this RFP. The committee will determine how many of the top evaluated firms will be negotiated with depending on the scores and other factors at the discretion of Brazos County. If the County chooses, these top scoring firms will be given an opportunity to present potential value engineering or cost saving suggestions to the County. The County will consider each of these suggestions and select those that the County believes present the best `value" to the project. The County will then send the selected value engineering/ cost saving prospects to each of the top evaluated firms for consideration and pricing. This process may be repeated depending on the project and its complexity. All firms will be accorded fair and equal treatment with respect to any opportunity for discussion and revision of proposals and no pricing will be shared with any of the firms at any time until after an award is made and contract is approved by Commissioners' Court. A best and final offer will be requested including any revisions and allowing for a revision of the completion timeframe for inclusion into the final contract. vol. _ j5�_ �Jg -y 9 Madison Construction, L.P. B. SUMMARY OF WORK This project consists of the construction of site work, 2 concrete pads and installation of two(2) vertical storage tanks for Brazos County. C. ALTERNATES See the plans and specifications for additional information No alternates exist for this project. D. CONDITIONS OF RFP The following instructions apply to all proposals and become a part of terms and conditions of any bid submitted to the Brazos County Purchasing Department, unless otherwise specified elsewhere in this Proposal. All Contractors are required to be informed of these Terms and Conditions and will be held responsible for having done so: Definitions: In order to simplify the language throughout this proposal, the following definitions shall apply: a BRAZOS COUNTY - Same as County. b. COMMISSIONERS' COURT - The elected officials of Brazos County, Texas given the authority to exercise such powers and jurisdiction of all county business as conferred by the State Constitution and Laws. C. CONTRACT - An agreement between the County and a Vendor to furnish supplies and/or services over a designated period of time during which repeated purchases are made of the commodity specified. d. CONTRACTOR - The successful Contractor(s) of this proposal request. e. COUNTY - The government of Brazos County, Texas and its authorized representatives. f. SUB -CONTRACTOR - Any contractor hired by the Contractor or Supplier to furnish materials and services specified in this proposal request. g. SUPPLIER - Same as Contractor 2. Upon acceptance and approval by the Commissioners' Court, this proposal will be made part of the contract between Brazos County and the successful Contractor for the period designated. 3. Proposals must be received by the Purchasing Department prior to the time and date specified. 4. The County reserves the right to accept or reject in part or in whole, any proposals submitted, and to waive any technicalities for the best interest of the County. 2Page Vcl. _1.354 pg. /Oo Madison Construction, L.P. 5. Brazos County shall not be responsible for any verbal communication between any employee of the County and any potential Contractor. Only written specifications and written price quotations will be considered. 6. Brazos County reserves the right to reject any proposals that do not fully respond to each specified item. 7. Should there be a change in ownership or management; the contract shall be canceled unless a mutual agreement is reached with the new owner to continue the contract with its present provisions and prices. This contract is nontransferable and non -assignable by either party. 8. The County may cancel this contract at any time for any reason, provided a thirty - day written notice is given. 9. The proposal award shall be based on, but not necessarily limited to, the following factors: a. Total cost including the alternates and addenda 40% b. Experience of subcontractors on similar projects 15% c. Proposer's reputation with similar projects 25% d. Ability to perform contract 20% 10. Although the cost is an essential part of the proposal, Brazos County is not obligated to award a contract on the sole basis of cost. 11. Acceptance of work provided shall be made by the County at the sole discretion of the Commissioner's Court when all terms and conditions of the contract and specifications have been met to its satisfaction, including the submission to the County of any and all documentation as may be required. 12. Title and Risk of Loss of the goods shall not pass to Brazos County until the County actually accepts and takes possession of the goods at the point or points of delivery. 13. This agreement shall be governed by the Uniform Commercial Code as adopted in the State of Texas as effective and in force on the date of this agreement. 14. No proposal may be withdrawn after opening time without acceptable reason and with the approval of Commissioner's Court. 15. Proposals will not be considered if submitted by telephone, fax or any other means of rapid dispatch, nor will a proposal be considered if submitted to any other person or department other than specifically instructed. 16. All proposals shall be submitted in accordance with the instructions contained herein. Brazos County will not be liable for any information received through other websites or sources of information. It is the sole responsibility of the 3JPage Vol. ,2,�SL Pe -/o % 1 Madison Construction, L.P. vendor to verify the accuracy of information received from sources other than Brazos County. It is recommended that the vendor check the Brazos Valley Bidding System for addenda prior to submitting their proposal. 17. There is no expressed or implied obligation for Brazos County to reimburse responding service providers for any expenses incurred in preparing proposals in response to this request. 18. Proposals must show full company name, mailing address and telephone number and be manually signed by an authorized sales or quotation representative of the Contractor. Company name and authorized signature shall appear in each space provided. The Contractor must include Employer Tax Identification Number or Social Security Number and signature for the proposal to be valid 19. It is our policy not to disclose proposal results over the phone. Proposal results will be available only after a contract is awarded by Commissioners Court. 20. The Contractor shall be responsible for following all provisions of Chapter 2258 of the Government Code relating to the payment of prevailing wages. The wage rates to be used are included in Exhibit A attached. A contractor or subcontractor who violates this section shall pay to Brazos County $60 for each worker employed for each calendar day or part of the day that the worker is paid less than the wage rates stipulated on Exhibit A. 21. Proposers must comply with the number of consecutive calendar days required to reach substantial completion of the project under normal conditions. Failure to comply with completion time will be considered reason enough to cancel the contract. 22. Bids must be submitted on units of quantity specified. In the event of errors in extended prices the unit price shall govern. In the event of a discrepancy between the numbers given for the price and the word form of the price, the word form shall govern. Any suggested change in quantity on the part of the bidder to secure better price or delivery is welcomed and may be given consideration provided that the bidder also bids on the quantity specified. 23. It is our policy not to furnish proposal results over the phone. Proposal results and tabulation sheets will be posted on Brazos County website after it is awarded by Commissioners Court. 24. This Proposal will be made part of any resulting contract the County may enter into. The terms and conditions of the County, contained in this RFP or the plans for this RFP shall supersede those of the vendor in the event of a conflict. 25. If any provision of this contract shall be held to be invalid or unenforceable for any reason, the remaining provisions shall continue to be valid and enforceable. If a court of competent jurisdiction finds that any provision of this contract is 41 Page Madison Construction, L.P. invalid or unenforceable, but that by limiting such provision it may become valid and enforceable, then such provision shall be deemed to be written, construed, and enforced as so limited. 26. No oral statements of any person shall modify or otherwise change or affect the terms, conditions or specifications. All change orders to this agreement shall be made in writing and shall not be effective unless signed by an authorized representative of Brazos County. E. SPECIAL PROVISIONS Contractors with questions regarding the proposal should submit them in writing via the Brazos Valley Online Bidding System at https://btazosbid.cstx.gov. 2. Fill out the proposal completely, identify the proposal name and number on the outside and return it to the Brazos County Purchasing Department, Administration Building, 200 South Texas Ave., Suite 352, Bryan, Texas 77803 by 2:00 p.m., Tuesday June 2, 2015. The proposal is invalid if it is not deposited at the designated location prior to the time and date advertised, or prior extension issued by the County. 3. All proposals shall be prepared on the bid forms located on the Brazos County web site https:Arazosbid.cstx.gov' The proposer must put the proposal number and name on the front of the envelope before mailing it to the Purchasing Department 4. In addition to the County's proposal form, all proposals shall be accompanied by a Contractor's Qualification Statement (AIA Document A-305 or equal) listing no more than five (5) similar representative projects with the project's owner and architect contact information. A Contractor's Qualification Statement (AIA Document A-305 or equal) listing no more than five (5) similar representative projects with the project's owner and architect contact information should also be included for the metal building erector and one for the site work contractor. 5. During the evaluation process, Brazos County reserves the right, in the best interest of the County, to request additional information or clarification from Contractors. 6. The contract shall be awarded to the responsible Contractor whose proposal is determined to be the best evaluated offer. 7. Your response to this proposal should be clear and concise addressing all requirements listed above and any other factors not specifically mentioned which would be advantageous to Brazos County. 8. Performance Standards: Vol. 'g 'g /O j 5Page Madison Construction, L.P. a. All services contracted herein shall be done in a courteous and orderly manner. All Contractor personnel shall be appropriately dressed at all times while on the property. b. The personnel performing the services contracted herein shall be under the sole responsibility and the employ of the Contractor. C. All materials and equipment brought to the site are the full responsibility and liability of the Contractor until removed from the site as required. d. Unless otherwise specifically noted, the Contractor shall provide and pay for all labor, materials, equipment, tools, transportation, and other facilities and services necessary for the proper execution and completion of the work herein contracted to be done. C. The Contractor shall give all notices and comply with all laws, ordinances, rules, regulations, and order of any public authority in connection with the performance of the work herein to be done. f. The Contractor shall be responsible for initiating, maintaining and supervising appropriate safety precautions and programs in connection with the work herein contracted to be done. The Contractor shall take all reasonable precautions for safety of, and shall provide all reasonable protection to prevent damage, injury or loss to: (1) all employees on the project and other persons who may be affected thereby, (2) the project and all materials and equipment to be incorporated therein, and (3) other property at the site or adjacent thereto. g. Contractor will be responsible for immediate notification of all damage to the property by the Contractor or its representative(s). F. Trade Secrets, Confidential Information and the Texas Public Information Act Brazos County, Texas is subject to the Texas Publication Information Act, Chapter 552, Texas Government Code. Proposals submitted to Brazos County, Texas in response to this RPP are subject to release by the County as public information. If the Proposer believes that the Proposal response, or part of it are confidential, as proprietary information, (s)he must specify that either all or part is excepted, and provide specific and detailed justification for its claim of confidentiality. Vague and general claims to confidentiality are not acceptable. All Proposals or parts of the Proposals which are not marked as confidential will be considered public information after a contract has been awarded. The successful Proposal may be considered public information even though parts are marked confidential. 6 1 Page Madison Construction, L.P. 2. Brazos County, Texas assumes no responsibility for asserting legal arguments on behalf of Proposers. Proposers are advised to consult with their legal counsel concerning disclosure issues resulting from this proposal process and to take precautions to safeguard trade secrets and other proprietary information. Marking your entire Proposal CONFIDENTIAL/PROPRIETARY is not in conformance with the Texas Public Information Act. G. Conflict of Interest The Proposer shall not offer or accept gifts or anything of value nor enter into any business arrangement with any employee, official or agent of Brazos County. 2. By signing and executing this Proposal, the Proposer certifies and represents to the County the Proposer has not offered, conferred or agreed to confer any pecuniary benefit or other thing of value for the receipt of special treatment, advantage, information, recipient's decision, lopinion, recommendation, vote or any other exercise of discretion concerning this Proposal. with the exception of interviews and other contacts initiated by Brazos County relevant to the selection process. Proposers, their emplovees or representatives, are prohibited from contacting any official or employee of Brazos County. except the Purchasing Agent, in regard to this RFP from the issuing date of the RFP until the date the Brazos County Commissioner's Court meets to consider award of the Proposal. Anv such contact will be grounds for rejection of the vendor's proposal. H. Addenda and Modifications Any changes, additions or clarifications to the RFP will be made by numbered addenda and must be acknowledged in the Proposal. 2. Any firm in doubt as to the meaning of any part of these requirements may request an interpretation thereof from the Purchasing Agent. At the request of the Proposer, or in the event the Purchasing Agent deems the interpretation to be substantive, the interpretation will be made by written addendum issued by the Purchasing Department. Such addendum will be posted on the Brazos Valley Online Bidding System and will become a part of the Proposal package, having the same binding effect as provisions of the original Proposal. No verbal explanation or interpretations will be binding. In order to have a request of interpretation considered, the request must be submitted in writing and must be received by the Purchasing Department no later than the question deadline. 3. All addenda, amendments and interpretations of this solicitation shall be in writing. Brazos County shall not be legally bound by any amendment or 71Page Madison Construction, L.P. interpretation that is not in writing. Only information supplied by the County in writing or in this RFP should be used in preparing Proposal responses. 4. The County does not assume responsibility for receipt of any addendum sent to Proposers. 5. All addenda must be acknowledged on this form. 1. Examination of Documents and Requirements 1. Each Proposer shall carefully examine all RFP documents and be thoroughly familiar with all requirements prior to submitting a Proposal. 2. Before submitting a Proposal, each Proposer shall be responsible for making all investigations and examinations that are necessary to ascertain conditions and requirements affecting the requirements of the RFP. Failure to make such investigations and examinations shall not relieve the Proposer of the obligation to comply, in every detail, with all provisions and requirements of the RFP. J. TAXES Brazos County is tax exempt. Tax exemption certificates will be executed by the County upon request. X. INSURANCE The Contractor shall procure and maintain at its sole cost and expense for the duration of this Agreement insurance against claims for injuries to persons or damages to property that may arise from or in connection with the performance of the work hereunder by the Contractor, its agents, representatives, volunteers, employees or subcontractors. The Contractor's insurance coverage shall be primary insurance with respect to the County, its officials, employees and volunteers. Any insurance or self-insurance maintained by the County, its officials, employees or volunteers shall be considered in excess of the Contractor's insurance and shall not contribute to it. Further, the Contractor shall include all subcontractors as additional insured under its policies or shall furnish separate certificates and endorsements for each subcontractor. All coverage for subcontractors shall be subject to all of the requirements stated herein. All Certificates of Insurance and endorsements shall be furnished to the County's Representative and approved by the County before work commences. Standard Insurance Policies Required: a Commercial General Liability Policy 8 1 Page --------------- vOo. .2 sC pg. Madison Construction, L.P. b. Automobile Liability Policy C. Worker's Compensation Policy General Requirements applicable to all policies: a. Only insurance carriers licensed and admitted to do business in the State of Texas will be accepted. b. Deductibles shall be listed on the Certificate of Insurance and are acceptable only on a per occurrence basis for property damage only. C. "Claims Made" policies will not be accepted. d. Each insurance policy shall be endorsed to state that coverage shall not be suspended, voided, canceled, reduced in coverage or in limits except after thirty (30) days prior written notice by certified mail, return receipt requested, has been given to Brazos County. e. All insurance policies shall be furnished to Brazos County upon request. I�KIIt� Ivf�Z�/•\ 11lyBJi;1�1:7\ I�iF �LRY_�� a. General Liability insurance shall be written by carrier with an A:VIII or better rating in accordance with the current Best Key Rating guide. b. Minimum Combined Single Limit of $1,000,000.00 per occurrence for bodily injury and property damage. C. No coverage shall be deleted from the standard policy without notification of individual exclusions being attached for review and acceptance. d. Excess Liability Umbrella Policy in the amount of not less than $2,000,000.00 will be provided at the Contractors expense. 2. AUTOMOBILE LIABILITY a. General Liability Insurance shall be written by a tamer with an A:VIII or better rating in accordance with the current Best Key Rating Guide. b. Minimum Combined Single Limit of $600,000.00 per occurrence for bodily injury and property damage. 3. WORKER'S COMPENSATION INSURANCE Pursuant to the requirements set forth in Title 28, Section 110.110 of the Texas compensation insurance policy; either directly through their employer's policy (the Contractor's or subcontractor's policy) or through an executed coverage agreement on an approved TWCC form. Accordingly, if a subcontractor does not have his or her own policy and a coverage agreement is used, Contractors and subcontractors must use that portion of the form whereby the hiring contractor agrees to provide coverage to the employees of the subcontractor. The portion of the form that would otherwise allow them not to provide coverage for the employees of an independent contractor may not be used. The worker's compensation insurance shall include the following terms 9 1 Page Madison Construction, L.P. a. Employer's Liability limits of $500,000.00 for each accident is required. b. "Texas Waiver of Our Right to Recover From Others Endorsement" shall be included in this policy. (Waiver of Subrogation) Pursuant to the explicit terms of Title 28, Section 110.110 ( c ) (7) of the Texas Administrative Code, the bid specifications, this Agreement, and all subcontracts on this Project must include the following terms and conditions in the following language, without any additional words or changes, except those required to accommodate the specific document in which they are contained or to impose stricter standards of documentation: A. Definitions: Certificate of coverage ("certificate'? - A copy of a certificate of insurance, a certificate of authority to self -insure issued by the Texas Worker's Compensation Commission, or a coverage agreement )TWCC-81), TWCC-83, or TWCC-84), showing statutory worker's compensation insurance coverage for the person's or entity's employees providing services an a project, for the duration of the project. Duration o the project - includes the time from the beginning of the work on the project until the Contractor's/person's work on the project has been completed and accepted by the governmental entity. Persons providing services on the project ("subcontractors" in section 406.096 (o( the Texas Labor Code)) - includes all persons or entities performing all or part of the services the Contractor has undertaken to perform on the project, regardless of whether that person has employees. This includes, without limitation, independent Contractors, subcontractors, leasing companies, motor carriers, owner -operators, employees of any such entity or employees of any entity which furnishes persons to provide services on the project. "Services" include, without limitation, providing, hauling, or delivering equipment or materials, or providing labor, transportation, or other service related to a project. "Services" does not include activities unrelated to the project, such as food/beverage vendors, office supply deliveries, and delivery of portable toilets. B. The Contractor shall provide coverage, based on the proper reporting of classification codes and payroll amounts and filing of any coverage agreements, that meets the statutory requirements of Texas Labor Code, Section 401.011 (44) for all employees of the Contractor providing services on the project, for the duration of the project. C The Contractor must provide a certificate of coverage to the governmental entity prior to being awarded the contract. D. It the coverage period shown on the Contractor's current certificate of coverage ends during the duration of the project, the Contractor must, prior to the end of the coverage period, file a new certificate of coverage with the governmental entity showing that coverage has been extended. - 10 Page Vol. C.Z pg. lD Madison Construction, L.P. E. The Contractor shall obtain from each person providing services on a project, and provide to the governmental entity: (1) a certificate of coverage, prior to that person beginning work on the project, so the governmental entity will have on file providing servicer on the project, and certificates of coverage showing coverage for all person; and (2) no later than seven calendar days after receipt by the Contractor, a new certificate of coverage showing extension of coverage, if the coverage period shown on the current certificate of coverage ends during the duration of the project. F. The Contractor shall retain all required certificates of coverage for the duration of the project and -for one year thereafter. G. The Contractor shall notify the governmental entity in writing by certified mail or personal delivery, within 10 calendar days after the Contractor knew or should have known, or any change that materially affects the provision of coverage of any person providing services on the project. K The Contractor shall post on each project site a notice, in the text, form and manner prescribed by the Texas Workers' Compensation commission, informing all persons providing services on the project that they are required to be covered, and stating how a person may verify coverage and report lack of coverage. The Contractor shall contractually require each person with whom it contracts to provide services on a project, to: (1) provide coverage, based on proper reporting of classification codes and payroll amounts and filing of any coverage agreement, that meets the statutory requirements of Texas Labor Code, Section 401.011 (44) for all of its employees providing services on the project, for the duration of the project; (2) provide to the Contractor, prior to that person beginning work on the project, a certificate of coverage showing that coverage is being provided for all employees of the person providing services on the project, for the duration of the project; (3) provide the Contractor, prior to the end of the coverage period, a new certificate of coverage .showing extension of coverage, if the coverage period shown on the current certificate of coverage ends during the duration of the project. (4) obtain from each other person with whom it contracts, and provide to the Contractor: (a) a certificate of coverage, prior to the other person beginning work on the project; and 11�Page Madison Construction, L.P. (b) a new certificate of coverage showing extension of coverage, prior to the end of the coverage period, if the coverage period shown on the current certificate of coverage ends during the duration of the project; (S) retain all required certificates of coverage on file for the duration of the project and for one year thereafter; (6) notify the governmental entity in writing by certified mail or personal delivery, within 10 calendar days after the person know or should have known, of any change that materially affects the provision of coverage of any person providing services on the project; and (7) contractually require each person with whom it contracts, to perform as required by paragraphs (a) -(g), with the certificates of coverage to be provided to the person for whom they are providing servicer. J By signing this contract, or providing, or causing to be provided a certificate of coverage, the Contractor who will provide services on the project will be covered by workers' compensation coverage for the duration of the project, that the coverage will be based on proper reporting of classification codes and payroll amounts, and that all coverage agreements will be filed with the appropriate insurance carrier, or, in the case of a self -insures, with the commission's Division of Self -Insurance regulation. Providing false or misleading information: may subject the Contractor to administrative penalties, criminal penalties, civil penalties, or other civil actions. 4. CERTIFICATES OF INSURANCE certificates shall be prepared and executed by the insurance company or its authorized agent, and shall contain the following provisions and warranties: a. The company is licensed and admitted to do business in the State of Texas. b. The insurance policies provided by the insurance company are underwritten on forms that have been provided by the Texas State Board of Insurance or ISO. C. All endorsements and insurance coverage according to requirements and instructions contained herein. d. The form of the notice of cancellation, termination, or change in coverage provisions to Brazos County. e. Original endorsements affecting coverage required by the section shall be furnished with the certificates of insurance. L. COMPLL4,NCE WITH LAW The Contractor's work and materials shall comply with all state and federal laws, municipal ordinances, regulations, and directions of inspectors appointed by proper authorities having jurisdiction. 121 Page Vol. Madison Construction, L.P. The Contractor shall perform and require all subcontractors to perform the work in accordance with applicable laws, codes, ordinances, and regulations of the State of Texas and the United States and in compliance with OSHA and other laws as they apply to its employees. In the event any of the conditions of the specifications violate the code for any industry, then such code conditions shall prevail. The Contractor shall follow all applicable state and federal laws, municipal ordinances, and guidelines concerning soil erosion and sediment control throughout the Project and warranty term. M. SAFETY PRECAUTIONS Safety precautions at the site are a part of the construction techniques and processes for which the Contractor shall be solely responsible. The Contractor is solely responsible for handling and use of hazardous materials or waste, and informing employees of any such hazardous materials or waste. The Contractor shall provide copies of all hazardous materials and waste data sheets to the Bryan Fire Department marked "Attn.: Assistant Chief'. The Contractor has the sole obligation to protect or wam any individual of potential hazards created by the performance of the work set forth herein. The Contractor shall, at its own expense, take such precautionary measures for the protection of persons, property, and the work as may be necessary. The Contractor shall be held responsible for all damages to property, personal injuries and/or death due to failure of safety devices of any type or nature that may be required to protect or warn any individual of potential hazards created by the performance of the work set forth herein; and when any property damage is incurred, the damaged portion shall immediately be replaced or compensated for by the Contractor at its own cost and expense. N. INDEMNITY To the fullest extent permitted by law, the Contractor agrees to and shall indemnify, hold harmless, and defend the County, its officers, agents, and employees from and against any and all claims, losses, damages, causes of action, suits, and liability of every kind, including all expenses of litigation, court costs, and attorney's fees for injury to or death of any person, for damage to any property, or for any breach of contract, arising out of or in connection with the work done by the Contractor under this Contract, provided that any such claim, loss, damage, cause of action, suit or liability is caused in whole or in part by an act or omission of the Contractor, any subcontractor, or any person, 13 1 Page Madison Construction, L.P. organization directly or indirectly employed by any of them to perform or furnish work on the Project. This indemnity shall apply regardless of whether such injuries, death, damages, or breach are caused in part by the negligence or omission of the County, any other party indemnified hereunder, the Contractor, or a third party. The indemnification shall include but not be limited to the following specific instances: a. In the event the County is damaged due to the act, omission, mistake, fault or default of the Contractor, then the Contractor shall indemnify and hold harmless and defend the County for such damage. b. The Contractor shall indemnify and hold harmless and defend the County from any claims for payment for goods or services brought by any material suppliers, mechanics, laborers, or other subcontractors. C. The Contractor shall indemnify and hold harmless and defend the County from any and all injuries to or claims to adjacent property owners caused by the Contractor, its agents, employees and representatives. d. The Contractor shall be responsible for any damage to the floor, walls, etc., caused by the Contractor's personnel or equipment. e. The Contractor shall also be responsible for the removal of all related debris. f. The Contractor shall also be responsible for subcontractors hired. g. The Contractor shall indemnify, hold harmless, and defend the County from any liability caused by the Contractor's failure to comply with applicable federal, state, or local regulations, that touch upon or concern the maintenance of a safe and protected working environment and the safe use and operation of machinery and equipment in that working environment, no matter where fault or responsibility Hes. The indemnification obligations of the Contractor under this section shall not extend to include the liability of any architect, their consultants, and agents or employees of any of them arising out of (1) the preparation or approval of maps, drawings, opinions, reports, surveys, change orders, designs or specifications, or (2) the giving of or the failure to give directions or instructions by the architect, their consultants, and agents and employees of any of them, provided such giving or failure to give is the primary cause of the injury or damage. O. RELEASE The Contractor assumes full responsibility for the work to be performed hereunder, and hereby releases, relinquishes, and discharges the County, its officers, agents, and employees from all claims, demands, and causes of action of every kind and character, including the cost of defense thereof, for any injury to or death of any person (whether 14 1 Page Madison Construction, L.P. employees of either party or other third parties) and any loss of or damage to any property (whether property of either of the parties hereto, their employees, or of third parties) that is caused by or alleged to be caused by, arising out of, or in connection with the Contractor's work to be performed hereunder. This release shall apply regardless of whether said claims, demands, and causes of action are covered in whole or in part by insurance, and in the event of injury, death, property damage, or loss suffered by the Contractor, any subcontractor, or any person or organization directly or indirectly employed by any of them to perform or furnish work on the project, this release shall apply regardless of whether such injury, death, loss, or damage was caused in whole or in part by the negligence of the County. P. BONDING REOUIREMENTS L All bidders must submit, with proposal, a cashier's check or certified check for at least five percent (5%) of the total bid price, payable to the order of Brazos County or a Bid Bond in the same amount issued by a surety, acceptable to Brazos County, authorized to do business in the State of Texas, as a guarantee that the Bidder will do the work described herein at the rates stated herein. Unsuccessful bidder's Cashier's Check or Certified Check will be returned after a written request to do so has been received by the Purchasing Agent. 2. The successful bidder must provide to the Purchasing Department, a performance bond and a payment bond, each in the amount of 100% of the total contract sum within ten (10) calendar days after receipt of notification of bid award. Such bonds shall be executed by a corporate surety duly authorized and admitted to do business in the State of Texas and licensed in the State of Texas to issue surety bonds with a Best Rating "A" or better. BRAZOS COUNTY RESERVES THE RIGHT TO ACCEPT OR REJECT ANY SURETY COMPANY PROPOSED BY THE BIDDER. IN THE EVENT BRAZOS REJECTS THE PROPOSED SURETY COMPANY THE BIDDER WILL BE AFFORDED FIVE (5) ADDITIONAL DAYS TO SUBMIT THE REQUIRED BONDS ISSUED BY A SURETY COMPANY ACCEPTABLE TO BRAZOS COUNTY. Q. PROPOSAL SUBMITTAL 1. The Contractor shall submit the proposal on the forms enclosed on the Brazos County web site. All blank spaces in forms shall be correctly fitted in by typewriter or manually in ink and the bidder shall state the prices. 2. If a proposal is submitted by an individual, their name must be signed by them or their duly authorized agent. If the proposal is submitted by a firm, association, or partnership, the name arid address of each member must be given, and the proposal must be signed by an official or duly authorized agent. 151Page Madison Constriction, L.P. 3. The Contractor roust submit an original and six (6) copies of the proposal to Brazos County. 4. The complete proposal should include the following: a. Completed and signed RFP. b. Contractor's Qualification Statement (AIA Document A-305 or equal) L One contractor's qualification statement should also be submitted for the metal building erector and one for the site work subcontractor. c. Bid bond, certified check or cashier's check for 5% of the total bid amount d. Completed Bid Proposal Form 5. By signing the certification below, the vendor verifies that all plans, special conditions and specifications have been reviewed and are considered in the pricing attached. R Scope of Work Brazos County will provide the following: a. All weather work site located at 2617 HWY 21 West b. Two (2) 8000 gallon emulsion storage tanks and stands c. 208-3 phase, 200 amp power to contractor furnished meter pole 2. Contractor shall provide the following: a. Ground work and foundation preparation required prior to construction of pads b. two (2) concrete pads as per Exhibit B attached together with a 2" tall, 10" wide concrete retaining wall with two (2) mats of rebar on 12" centers each way around perimeter. c. Minimum of a 40 ton crane with 30' reach for unloading delivery truck and then erection of stands and tanks. Both the crane and operator shall be certified. (Tanks weigh approximately 10,000 lbs. each. d. Welder and welding machine to weld tank and stand mounting legs to the weld flanges installed in the concrete. e. Installation of meter pole as per Exhibit C, 2-50 amp services in conduit run to each tank and wired into control box provided on tank. f Provide all equipment, labor and materials required for the installation of concrete pads and tanks. g. Set tanks and secure them to the concrete pads and make ready for operation. h. All permits and fees required or needed for this project. 3. Pad/Slab Specifications a. 12" thick slab with bottom reinforcing of #6 rebar at 9" spacing in both directions, and top reinforcing or # 5 mbar at 5" spacing both directions. Clear cover of 2.25" should be provided to top rebar layer and 2.5" to bottom layer rebar. 16 1 Page vel. _.�Sl P9 // Madison Construction, L.P. b. %" thick 14" x 14" lag plates anchored to the slab via four (4) #4 rebar per plate, embedded into slab. Due to the slab being 12" thick, put a 90 degree bend at approximately 9.5" down and extend past the bend 4" minimum into slab. c. 2' diameter by 3' deep drilled shafts placed beneath the slab at each of the four (4) legs to provide lateral supports and extra dead load to resist potential uplift. 2' diameter shaft consists of eight (8) # 7 rebar vertically enclosed with in a #3 spiral at 6" pitch. Vertical rebar should extend 6" minimum into slab. d. See Exhibit B for plans 4. Project Timeline EL Contractor shall start the project ten (10) days after full execution of the contract is complete. Project should be completed within thirty (30) days of the project start date. S. LIST OF SUB -CONTRACTORS: 1. Site Work Madison Construction, L.P. 2. Concrete Pads Cross Roads Concrete Services 3. Electrical Britt Rice Electric, L.P. T. Pricin A complete cost breakdown should be included in the proposal submitted by Contractor. Site Work -- $1,000.00 Concrete Foundation -- $34,800.00 Tank Erection --$7,500.00 Electrical -- $15,700.00 Total Base Bid -- fifty-nine thousand and no/100 dollars. $59,000.00 U. Proposal Evaluation Waiver By submitting a proposal or response, each Proposer/offeror indicated below agrees to waive any claim it has or may have against Brazos County (the Owner), Architect, Engineers, Consultants and their respective Commissioners, directors, employees, or agents arising out of or in connection with (1) the administration, evaluation, or recommendation of any proposal or response (2) any requirement under the Request for Qualification or related documents; (3) the rejection of any proposal or response or any part of any proposal or response; and/or (4) the award of a Contract, if any. The Proposer further agrees the Owner reserves the right to waive any requirements under the proposal documents or the Contract Documents, with regards to acceptance or rejection of any proposals, and recommendation or award of the contract. - - 17Page Note: The Statement of Affirmation Must be Notarized. STATEMENT OF AFFIRMATION "The undersigned affirms that he/she is duly authorized to execute this waiver by the person(s) or business entity making the proposal. Firm's Name: Madison Construction. L.P. Address: 1640 Briarcrest Drive, Suite 125, Bryan, TX 77802 Proposer's Name Proposer's Date: Marcu iv, auio President Subscribed and sworn to me on this loth day of March in the year 2016 SHARON -POLAK Notary Public Expires March 19,2020 My Commission expires march 19, 2020 V. ADDENDA The undersigned acknowledges receipt of the following addenda issued during the time of Bidding and includes the several changes therein in this Proposal. No. Date Date W. CERTIFICATION OF PROPOSAL No. Date 181Page Vol... Pg _//� The undersigned affirms that they are duly authorized to execute this contract, that this bid has not been prepared in collusion with any other Contractor, and that the contents of this bid have not been communicated to any other, Co tractor prior to the official opening. i9 Signed By: fide: President Typed Name: Michael R. (ones Company Name: Madison Construction L.P. Phone No. r9791268-5520 Mailing Address: PO Box 3787 Brvan _ TX 77805-3787 P. O. Box or Street City State Zip Employer Identification Number: 74-2743961 CORPORATE SEAL IF SUBMITTED BY A.CORPORATION END OF RFP NO. 2016-171 By signing below, Brazos County agrees that this RFP 2016-171 will be awarded to the vendor whose name appears above and both artier agr o the to and conditions contained herein. By: Brazos County /Commissioner's Court Date �I��/ I t, i Attest: Brazos County Clerk 7�(/ L? �' Xl(e 19Page THE AMERICAN INSTITUTE OF ARCHITECTS AIA Document A310 Bid Boni KNOW ALLMEN BY THESE PRESENTS, that we Madison Construction, L.P. 1640 Brlarcrest Dr Suite 125 B_wn,, TX 77802 ' as Principal, Hereinafter called Principal, and WashingtonInternational Insurance Company 475 North MartIirigale Road, Suite 850 Schaumburg, It. 6-01,73 a corporation duly organized under the laws of the State of New Hampshire as Surety, hereinafter called Surety, are held and firmly bound unto as Obligee, hereinafter called Obligee, in the sum of.Five Percent (5% of Total Amount Bid _ Dollars for the payment of which sum well and truly to be made, the said Principal and the said Surety, bind ourselves; our heirs, executors, adni!nistrators, successors and assigns, Jointly and severally; firmly by these presents. WHEREAS,"the Principal has submitted a bid for (Here insert full name, address and description of project) Installation of WOO Gallon Vertical Tanks 'NOW, THEREFORE, if the Obligee: shall accept the bid of the Principal and the Principal shall enter Into. a Contract .with Obligee in accordance with the terms of such bid, and give such bond or bonds as may be speclfted in the bidding or Cont 'Documents with good and sufficient surety for the faithful performance of such Contract and for the prorrpt_payment of labor. .material funilshed In the prosecution thereof, or in'the ,event of the failure of the Principal to enter such Contract and give s bond.or bonds,.lf the 'Principal shall pay to the Obligee the difference not to exceed the penalty hereof between the am( specified lmsaid bid and such larger amount for which the Obligee me in good faith:contract with another party to perform Work covered by said bid. then this obligation shall be null and void, otherwise to remain in full force and effect. Signed and sealed this loth day of March zo16 f 1. - I (n ial)(S (w;mess) < .(TjM Michael R. Jones (Surety). (Sea!) , (Witte E. Tauer, VOL 9Sl Pg. 2 J. ;at;t LIMITED PARTNERSHIP ACKNOWLEDGMENT State of TEXAS as. County of -5'C k-7 w s On this loth day of March , 2016, before me personally appeared Michael R Jones to me known who being by me duly sworn, that he/sheds the President of the Madison Constnlcnoh. L . the Limited Partnership described in and which executed the foregoing instrument, and that he/she signed hiAer name thereto by order of the Board of Governors of said Limited, Partnership. - 'K SHARON K. POIAK ono NotaryPublic�tai.�"s County, I2xes Pdy c:r'y ID # 10472874 Expires March 19, 2020 I NIy commission expires 516 2a r t ACKNOWLEDGMENT'OF CORPORATE SURETY State of. MINNESOTA) as. Jl( County of ]iENNEPIN On this10th day of . March , 2016;,before meziapeared John E. Tauer to me personally' known, who being by.me duly sworn, did'say that �he is the Attomey-in-Fact'of Washington International Insurance Company corporation, that the seal affixed to the foregoing .instrument is the corporate seal of said corporation and that said instrument was executed hr behalf of said corporation by.authority of its Board of Directors; and that said.. Jolm E. Tauer ... acknowledged said instrument to be the free act and deed of said corporation. ..... ., ,VVy�gAv ". n rT"'v � Notary / � -Cou - ... TP LINDAK. FRENCH NOTARYPUOUC-MINNESOTA 'My commissions ''es y ZO=. My Commission Expues �y l''' `��` January 31,. 2020 3 n NAS SURETY GROUP NORTH AMERICAN SPECIALTY INSURANCE COMPANY WASHINGTON INTERNATIONAL INSURANCE COMPANY GENERAL POWER OF ATTORNEY KNOW ALL MEN BY THESE PRESENTS, THAT North American Specialty Insurance Company, a corporation duly organized and existing under laws of the State of New Hampshire, and having its principal office in the City of Manchester, New Hampshire, and Washington International Insurance Company, a corporation organized and existing under the laws of the State of New Hampshire and having its principal office in the City of Schaumburg, Illinois, each does hereby make, constitute and appoint: R. W. FRANK, R. SCOTT EGGINTON, JOHN E. TAUER, CRAIG REMICK, JOSHUA R. LOFTIS, TINA L DOMASK, ROSS S. SQUIRES, LINDA K, FRENCH, RACHEL THOMAS, NICOLE STR.LINGS. SANDRA M. DOZE; JOHN W. WALSH, BETSY WRIGHT. JEROME T. OUIMET. KURT C. LUNDBLAD. JACK CEDARLEAF IL D.R.DOUGI6 .BRIANI.OESTRHCKUNULVEN,F JILYKEISER' JORGENSEN,MBLWDAC.BLODGM.and RC.BOWMAN JOINTLYORSEVFRALLY Its true and lawful Attomey(s)-in-Fact, to make, execute, seat and deliver, for and on its behalf and as its act and deed, bonds or other writings obligatory in the nature of a bond on behalf of each of said Companies, as surety, on contracts of suretyship as are or may he required or permitted by law, regulation, contract or otherwise, provided that no bond or undertaking or contract or suretyship executed under this authority shall exceed the amount of: FIFTY MILLION ($50,000,000.00) DOLLARS This Power of Attorney is granted and is signed by facsimile under and by the authority of the following Resolutions adopted by the Boards of Directors of both North American Specialty Insurance Company and Washington International Insurance Company at meetings duly called and held on the 9" of May, 2012: "RESOLVED, that any two of the Presidents, any Managing Director, any Senior Vice President, any Vice President, any Assistant Vice President, the Secretary or any Assistant Secretary be, and each or any of them hereby is authorized to execute a Power of Attorney qualifying the attorney named in the given Power of Attorney to execute on behalf of the Company bonds, undertakings and all contracts of surety, and that each or any of them hereby is authorized to attest to the execution of any such Power of Attorney and to attach therein the seal of the Company; and it is FURTHER RESOLVED, that the signature of such officers and the seal of the Company may be affixed to any Such Power of Attorney or to any certificate relating thereto by facsimile, and any such Power of Attorney or certificate bearing such facsimile signatures or facsimile seal shall be binding upon the Company when so affixed and in the future with regard to any bond, undertaking or contract of surety to which ij.is �tiit`9ch11 -ed," pJS`1�OVaN1rY�4r/� /f 3 p..E e'dJ SUtLa= Sven P. Atdmon, Scnlar VltePrtaldent of Waahlapta In tamallanA Inaarnee CaraPnny 9vt 1B1a pWf bac &Sm ler Via Pread eat afNoah Amerlean Specially In Saranac CompIDr 4MP�O� be0 L �iy�BON �i �aPP� �lal/aIIIlO\ill a MkIcdA. IBi%TeeJoFVa mento ,upon nttmv ova Tamywy & Senlne Vin Pretldeut erNaah A tedean 51eda111 Inaunnee Company IN WITNESS WHEREOF, North American Specialty Insurance Company and Washington International Insurance Company have caused their official seals to be hereunto affixed, and these presents to be signed by their authorized officers this 12di day of May 2015 , North American Specialty Insurance Company Washington International Insurance Company State of Illinois County of Cook IS; On this 12th day of May , 201.5 before me, a Notary Public personally appeared Steven P. Anderson , Senior Vice President of Washington International Insurance Company and Senior Vice President of North American Specialty Insurance Company and Michael A. Ito Senior Vice President of Washington International Insurance Company and Senior Vice President of North American Specialty Insurance Company, personally known to me, who being by me duly swom, acknowledged that they signed the above Power of Attorney as officers of and acknowledged said instrument to be the voluntary act and deed of their respective companies. OFM HEIJNY t [NOTARYMPIUBU¢.SCLALTATEOF IWNOIS,No,ary PublicCOMSSION EXPIRES 1 2/042 01 7 I, Jeffrey Goldberg .the duly elected Assistant Secremry of North American Specialty Insurance Company and Washington International Insurance Company, do hereby certify that the above and foregoing is a true and correct copy of a Power of Attorney given by said North American Specialty Insurance Company and Washington International Insurance Company, which is still in full force and effect. IN WITNESS WHEREOF, I have set Iffy hand and affixed the seals of the Companies this 70th day of /March , 201 Jeffery Ge101N. Vice PraWene&Avimn, Se"care f Wmhiag.n Wmaational aaata,ea Company&Nv,N M,aicv, 5,cibly lorvnnce Company pg,�,Zd Qualification Statement Owner/Architect References Mr. James Deatherage PRODUCERS COOPERATIVE ASSOCIATION (979) 778-6000; Fax (979) 778-0243 jwd@producerscooperative.com Mr. Niels Jensen (979) 571-3420; no fax number niels.jensen@aggienetwork.com Mr. John Duncum (979) 204-1491; no fax number Johndu8207@gmail.com Mr. Craig Blum BURLESON HOLDINGS, LTD (979) 567-3212; (979) 567-7061 cblum@woodsonlumber.com Mr. Mike Record THE ARKITEX STUDIO (979) 821-2635; (979) 775-8224 msr@arkitex.com REFERENCES Credit References American Momentum Bank One Momentum Blvd. College Station, TX 77845 Mr. Frank Varisco (979) 774-1111; Fax (979) 599-9375 fvarisco@americanmomentumbank.com Woodson Lumber Company PO Box 3950 Bryan, TX 77805 Ms. Linda Gaas (979) 567-3212; Fax (979) 567-7061 Igaas@woodsonlumber.com CMC Construction Services PO Box 844573 Dallas, TX 75284-4573 Ms. Mabel Coleman (972) 308-4101 Mabel.coleman@cmc.com Praxair (fka Botco) 812 South Bryan St. Bryan, TX 77806 Ms. Maureen (979) 779-7154; Fax (979) 822-5316 No email address We -Rent -It PO Box 5449 Bryan, TX 77805 Ms. Sherry (979) 823-0085; Fax (979) 779-8351 No email address MADISON CONSTRUCTION, L.P. j Vol. S pg. =111 -AIA Document A305r" —1986 Contractor's Qualification Statement The Undersigned certifies under oath that the information provided herein is true and sufficiently complete so as not to be misleading. SUBMITTED TO: Brazos County Purchasing ADDRESS: 200 South Texas Ave., Ste. 352 Bryan, TX 7781)3 SUBMITTED BY: Madison Construction, L.P. NAME: Michael R. Jones ADDRESS: PO Box 3787 Bryan, TX 77805-3787 PRINCIPAL OFFICE: 1640 Briarcrest Drive, Suite 125 Bryan, TX 77802 [ ] Corporation [ X ] Partnership [ ] Individual [ ] Joint Venture [ ] Other NAME OF PROJECT: (j applicable) Installation of 8000 Gallon Vertical Tanks TYPE OF WORK: Nle separate fornr for each Classification of Work) [ X ] General Construction [ ] HVAC [ ] Electrical [ ] Plumbing [ ] Other: (Specify) § I ORGANIZATION § 1.1 How many years has your organization been in business as a Contractor? 20 § 1.2 How many years has your organization been in business under its present business name? 11 § 1.2.1 Under what other or former names has your organization operated? Madison Construction, L.P. § 1.3 If your organization is a corporation, answer the following: § 1.3.1 Date of incorporation: § 1.3.2 State of incorporation: § 1.3.3 President's name: § 1.3.4 Vice-president's name(s) ADDITIONS AND DELETIONS: The author of this document has added information needed for its completion. The author may also have revised the text of the anginal AIA standard form. An Additions and Deletions Report that notes added information as well as revisions to the standard form text is available from the author and should be reviewed. A vertical line in the left margin of this document indicates where the author has added necessary information and where the author has added to or deleted from the original AIA text. This document has important legal consequences. Consultation with an attorney is encouraged with respect to its completion or modification. This form is approved and recommended by the American Institute of Architects (AIA) and The Associated General Contractors of America (AGC) for use in evaluating the qualifications of contractors. No endorsement of the submitting party or verification of the information is made by AIA or AGC. AIA Document A305--1986. Copyright O 1964, 1869, 1979 and 1986 byThe Amenwn In s[tule of Architects. All rights reserved. WARNING: This AIA° Document Is protected by U.S. Copyright Law and International Treaties. Unauthorized reproduction or distribution of this AIAO Document, or any portion of It, may result in severe civil and criminal penalties, and will be prosecuted to the maximum extent possible under the law. This document was produced by AIA software at 09:31:34 on 03/10/2016 under Order No. 5438904678 which expires on 031102017, and is not for resale. User Notes: _ (3B9ADA39) § 1.3.5 Secretary's name: § 1.3.6 Treasurer's name: § 1.4 If your organization is a partnership, answer the following: § 1.4.1 Date of organization: January 1, 2004 § 1.4.2 Type of partnership (if applicable): limited partnership § 1.4.3 Name(s) of general parmer(s) TAC Holdings, L.P. § 1.5 If your organization is individually owned, answer the following: § 1.5.1 Date of organization: § 1.5.2 Name of owner: § 1.6 If the form of your organization is other than those listed above, describe it and name the principals: § 2 LICENSING § 2.1 List jurisdictions and trade categories in which your organization is legally qualified to do business, and indicate registration or license numbers, if applicable. State of Colorado § 2.2 Listjurisdictions in which your organization's partnership or trade name is filed. State of Colorado § 3 EXPERIENCE § 3.1 List the categories of work that your organization normally performs with its own forces. concrete; sttvetural earthwork; carpentry; miscellaneous steel work; drywall § 3.2 Claims and Suits. (If the answer to any of the questions below is yes, please attach details.) § 3.2.1 Has your organization ever failed to complete any work awarded to it? No § 3.2.2 Are there any judgments, claims, arbitration proceedings or suits pending or outstanding against your organization or its officers? No § 3.2.3 Has your organization filed any law suits or requested arbitration with regard to construction contracts within the last five years? No § 3.3 Within the last five years, has any officer or principal of your organization ever been an officer or principal of another organization when it failed to complete a construction contract? (If the answer is yes, please attach details.) No AIA Dacument A305r" —1986. Copyright O 1964, 1969, 1979 and 1986 byThe Amenwn Instituto of Architects. All rights reserved. WARNING: This AIA® Document Is protected by U.S. Copyright Law and Iutemational Treaties. Unauthorized reproduction or distribution of this AIA° Document, or any portion of It, may result in severe civli and criminal penalties, and will be prosecuted to the maximum extant possible under the law. This document was produced by AIA software at 09:31:34 on 03/10/2016 under Order No. 5438904878 which expires on 03110/2017, and is not for resale. User Notes: __. (3139ADA39) § 3.4 On a separate sheet, list major construction projects your organization has in progress, giving the name of project, owner, architect, contract amount, percent complete and scheduled completion date. See attached § 3.4.1 State total worth of work in progress and under contract: $30,644,000 § 3.5 On a separate sheet, list the major projects your organization has completed in the past five years, giving the name of project, owner, architect, contract amount, date of completion and percentage of the cost of the work performed with your own forces. See attached § 3.5.1 State average annual amount of construction work performed during the past five years: $12,979,075 § 3.6 On a separate sheet, list the construction experience and present commitments of the key individuals of your organization. See attached § 4 REFERENCES § 4.1 Trade References: Woodson Lumber Company (979) 567-3212; Fax (979) 567-7061; lgaas@woodsonlumber.com CMC Construction Services (972) 308-4101; mabel.coleman@cme.com We -Rent -It (979) 823-0085; Fax (979) 779-8351 § 4.2 Bank References: American Momentum Dank 4830 W. Kennedy Blvd., Suite 200 Tampa, FL 33609 (813)282-3160 Maureen Gallagher § 4.3 Surety: § 4.3.1 Name of bonding company: Washington International Insurance Group 475 North Martingale Road, Suite 850 Schaumburg, IL 60173 § 4.3.2 Name and address of agent: .Joshua R. Loftis Cobb Strecker Dunphy & Zimmerman 150 South Fifth Street, Suite 2800 Minneapolis, MN 55402 (612)349-2467 § 5 FINANCING § 5.1 Financial Statement. AIA Document A305'"-1906. Copydght C 1964 1969, 1979 and 19a6 byThe American In statute of Architects. All rights reserved. WARNING: This AIA° Document is protected by U.S. Copyright Law and Intemational Treaties. Unauthorized reproduction or distribution of this AIAe Document, or any portion of it, may result in severe civil and criminal pen allies, and will be prosecuted to the maximum extent possible under the law. This document was produced by AIA software at 09-31:34 on 03/10/2016 under Order No. 5438904879 which expires on 03/10/2017, and is not for resale. User Notes: _ (359ADA39) Vol, -;?S� . Pg, /.?V § 5.1.1 Attach a financial statement, preferably audited, including your organization's latest balance sheet and income statement showing the following items: Current Assets (e.g., cash, joint venture accounts, accounts receivable, notes receivable, accrued income, deposits, materials inventory and prepaid expenses); Net Fixed Assets; Other Assets; Current Liabilities (e.g., accounts payable, notes payable, accrued expenses, provision for income taxes, advances, accrued salaries and accrued payroll taxes); Other Liabilities (e.g., capital, capital stock, authorized and outstanding shares par values, earned surplus and retained earnings). § 5.1.2 Name and address of firm preparing attached financial statement, and date thereof: Attached is an interim Unaudited Balance Sheet dated September 31, 2015. Madison Construction, L.P. does not have Audited Financial Statement. § 5.1.3 Is the attached financial statement for the identical organization named on page one? § 5.1.4 If not, explain the relationship and financial responsibility of the organization whose financial statement is provided (e.g., parent -subsidiary). Madison Construction, L.P. is a subsidiary of TAC Moldings, L.P. More financial information is available from'JAC Holdings, L.P. should Madison be considered for this project. § 5.2 Will the organization whose financial statement is attached act as guarantor of the contract for construction? § 6 SIGNATURE § 6.1 Dated at this I Oth day of March 2016 Naive of Organization: Madison Construction, L.P, By: Michael R. Jones Title: President j� §6.21'/ M Michael R. Jones being duly sworn deposes and says that the information provided herein is true and sufficiently complete so as not to be misleading. Subscribed and swom before me this 10th day of March 2016 Notary Public: Sharon K. Polak My Commission Expires: March 19, 2020 AIA Document A306^1-1986. Ce pyright01964, 1969, 1979 and 1986 byThe American Institute of Architects. All rights reserved. WARNING: This AIA* Document is protected by U.S. Copyright Law and IntemationaI Treaties. Unauthorized rep rod notion or distribution of this AIA° Document, or any portion of it, may result In severe civil and criminal penalties, and will be prosecuted to the maximum extent possible under the law. This document was produced by AIA software at 09:31:34 on 03/10/2016 under Order No. 5438904878 which, expires on 03/10/2017, and is not for resale. User Notes: �-- ____ pg._��._.� (389ADA39) V�� Additions and Deletions Report for AIA® Document A305"' - 1986 This Additions and Deletions Report, as defined on page 1 of the associated document, reproduces below all text the author has added to the standard farm AIA document in order to complete it, as well as any text the author may have added to or deleted from the original AIA text. Added text is shown underlined. Deleted text is indicated with a horizontal line through the original AIA text. Note: This Additions and Deletions Report is provided for information purposes only and is not incorporated into or constitute any part of the associated AIA document. This Additions and Deletions Report and its associated document were generated simultaneously by AIA software at 09:31:34 on 03110/2015. PAGE SUBMITTED TO: Brazos County Purchasing ADDRESS: 200 South Texas Ave.. Ste. 352 Bryan TX 77803 SUBMITTED BY: Madison Construction. L.P. NAME: Michael R. Jones ADDRESS: PO Box 3787 Brvan. TX 77805-3787 PRINCIPAL OFFICE: 1640 Briarcrest Drive, Suite 125 Brvan, TX 77802 [ X I Partnership NAME OF PROJECT: (if applicable) Installation of 8000 Gallon Vertical Tanks Additions and Deletions Report for AIA Document AIIOS "-1986. Copyright® 1964, 1969, 1979 and 1986 byThe American Institute cf Architects. All rights reserved. WARNING: This AIA® Document Is protected by U.S. Copyright Law and International Treaties. Unauthorized reproduction or distribution of this AIA® Document, or any portion of it, may result In severe civil and criminal penalties, and will be prosecuted to the maximum extent posslhla undertha law. This document was Produced by AIA software at 09:31:34 on 03/10/2016 under Order No. 543890487e which expires on 03/10/2017, and is not for resale. �f User Notes: Pg --6j (3139ADA3M) [ X ] General Construction § 1.1 How many years has your organization been in business as a Contractor? 20 § 1.2 How many years has your organization been in business under its present business name? l 1 PAGE2 Madison Construction, L.P, § 1.4.1 Date of organization: January I. 2004 § 1.4.2 Type of partnership (if applicable): limited narmershig, TAC Holdings. L.P. State of Colorado State of Colorado concrete: structural earthwork: camentry: miscellaneous steel work: drywall No No No No Additions and Deletions Report for AIA Document A3057" —1986. Copynght©1964, 1969, 1979 and 1986 byThe American Insfitute of Architects. All rights reserved. WARNING: This AIA- Document is protected by U.S. Copyright Law and International Treaties. Unauthorized reproduction or distribution of 2 this AIAO Document, or any portion of it, may result In severe civil and criminal penalties, and will be prosecuted to the maximum extent possible under the law. This dondmeatwas produced by Alk software a109t31 34 on M1012016 under Order No. 5438904878 which expires on 03110)2017, and is not for resale .__ User Nates: Vol. J ; + /1� (3U9AnA39) V T ,) PAGE 3 See attached $30.644.000 See attached $12-979,075 'See attached American Momentum Bank 4830 W. Kennedv Blvd., Suite 200 Tama. FL 33609 (813) 282w3160 Maureen Gallacher PAGE Washington International Insurance Group 475 North Martingale Road. Suite 850 Schaumburg. IL 60173 Joshua R. Loftis Cobb Strecker Dunphv & Zimmerman 150 South Fifth Street. Suite 2800 Minneapolis, MN 55402 (612)349-2467 Attached is an interim Unaudited Balance Sheet dated September 31, 2015. Madison Construction. L.P. does not have Audited Financial Statement. Madison Construction L.P. is a subsidiary of TAC Holdings L.P. More financial information is available from TAC Holdings, L.P. should Madison be considered for this project. Additions and Deletions Report for AIA Document A305--1986. Copyright®1964, 1969, 1979 and 1986 byTne American Institute of Architects. All rights reserved. WARNING: Thls AIA® Document Is protected by U.S. Copyright Law and International Treaties. Unauthorized reproduction or distribution of this AIA- Document, or any portion of it, may result In severe civil and criminal penalties, and will be prosecuted to the maximum extent possible under the law. This document was produced by AIA software at 09'31:34 on 03/101201G under Order No. 5438904878 which expires on 0 311 012 017, and is not for resale. User Notes: r ' -- (389ADA39) Vol. ,? �s� Pg. 2ge § 6.1 Dated at this I Oth day of March 2016 Name of Organization: Madison Construction L.P. By: Michael R. Jones Title: President M Michael R. Jones being duly sworn deposes and says that the information provided herein is true and sufficiently complete so ac not to be misleading. Subscribed and sworn bbeffor—eft me this 10th day of March 2016 El ry Expires March 19, 2020 Nly Commission Expires: March 19 2020 Additions and Deletions Report for AIA Document A305"— 1986. Copyight m 1954, 1969, 1979 antl 1986 byThe American Institute of Architects. All rig his reserved. WARNING: This AIA° Document Is protected by U.S. Copyright Law and International Treaties. Unauthorized reproduction or distribution of 4 this AIA° Document, or any portion of it, may result In severe civil and criminal penalties, and will be prosecuted to them a.! mum extent possible under the law. This document was produced by AIA software at 09:31:34 on 03/1012016 under Order No: 5438904878 which expires on 031102017, and is not for resale. I I User Notes: Vol. 7 Pry, (3B9ADA39) ___dam%_ m Q 7`- v o n � L L V N X Uf v V O Q K Q U 0 � U � v N Z � m` 7`- ✓1 to Ill ri O O O O N Ill m DJ m O O O O O O N O O O O O O O ti N N O m £ E E E E E > > 0 0 >> o u v u v u v v p v Z Z Z ❑ ❑ ❑ yl ❑ m m u n O 00 c0 m ri v f -i ri m U U1 VY V/ U U N V1 V} 1/T Vf V! H Y In In C U 0A v Y ° a J Y d d Y C L In C C C C J V m C7 a+ Y C p a m m m s a a ❑ R a Z c Y c c a E E E o U O O — a v a ? v R p c > > v > m R F O ❑ ❑ a > o u LL J n. JEI > Y J > I m a m N O v R C LL J J v J o v 0� O V m x v m w E 2 a u v U � _'^ U K m E C Y C N Y C E a R v v p v a O O O O ` C U o C N c C LL a o ,o o u a R o R V m R v O C H— O R vvi O m C pXj Ol J p cCo C O' R a _ N E m v ,C E X R N E a m E E3 u 3 m l7 a i c ° u « u m ° u 61 v O I O E O E"—U—mv-R v ❑ a Vol.�.� Pg._/_, 911 t _�. 1 o o c o m m O1 l0 r N ti a pN ti N 0 ti 0 O N O N O N O 0 O p O N O N N N N N N L N a N S] v ❑ a O u O u > o ° ° z to l0 O O N O O N h ifl N Ci N N m ri O n n m m w M W N h N Ol Ol O O O L6 Ol CT O r- m 0 o 0 O m tR N N N V1 m 4/1 N VY m V� Ifl UY G Vf lD VT "1 VI N N N U C C UO U0 O O U C O V U ❑ O 00 a ❑ VI N O C y U N N N N 'a' ` u � N a O Q Y L u L m= Q Q Q O y C G Ql a � _ a > J 0 h O C C J f0 X H m O ❑ cG u C - N u O N E Y v O 9 a > '= v a W i o '^ °' N w E N N v N O N C 5 L N > u a Qb x o a 2 a 0 o 'o ° w ° X Q u° u Q0 F a v O m o O O v L v v H H H v y � C U v v J V O C E m V L a :2 O v m v x d v m y W m m .n o v m ?� C6o Q> O O Z O s N vol,mr'y V I. General Proposer's Qualifications 3. Key Personnel Key Individuals Donald A. Adam Chief Executive Officer Principal adam(@adamcorporation.com Businessman, banker developer, and entrepreneur, Mr. Adam established Madison Construction, L.P. in 1995. Mr. Adam sought experienced construction industry executives to establish a lasting construction business committed to providing the industry and its clients with project performance, quality and lasting value. Mr. Adam is involved in the financial aspects of the company and is committed to leading Madison into the future. Michael R. Jones President mrjones0madisnn-construction.com Mr. Jones graduated from Texas A&M University in 1976 with a Bachelor of Science in Building Construction. His 39 years of construction experience provides Madison Construction, L.P. the ability and confidence to build any construction project Mr. Jones is involved in general oversight during all phases of Madison Construction's projects. He believes the best projects are constructed with a team of individuals including the owner, designers, and contractors. He is dedicated to providing projects with experienced individuals. Communication with clients and their architects and listening to understand their needs results in the best construction product Matt Nash Executive Vice President matt(o) m a diso n -co nstructi o n. co m A professional construction manager with a broad spectrum of experience, Matt Nash graduated from Texas A&M University in 1997 in Agricultural Systems Management, followed with a Master's Degree in Construction Management at Texas A&M University in 1999. He is an organized and seasoned manager having completed multiple projects for Madison Construction, L.P. Mr. Nash has an exceptional ability to manage the construction process and the people involved. He also has experience in mechanical contracting and is a great resource for Madison Construction and its clients concerning mechanical systems. He is dedicated to providing the highest quality construction on his projects for the client and for Madison Construction. Marq Synwolt Vice President- Field Operations m vs n w o l t@ m a d i s o n -m n st r u c t i o n. c o m Mr. Synwolt's 36 years of experience in construction industry coordination and management places Madison in the position to provide its clients with timely and quality construction. A 1979 graduate of Texas A&M University, he has completed numerous projects in the Bryan -College Station and Houston areas. His ability to manage the construction process and the people involved is excellent. Jody Quimby Vice President - Senior Estimator i o dy0 m a d i so n -co nstru ctio n.co m Graduating from Texas A&M University in 1977, Mr. Quimby has spent the last 38 years in all facets of the construction business including cost estimating, conceptual estimating, project management, and property quality control. Because of his multiple construction discipline experiences, Mr. Quimby is invaluable to understanding and determining construction cost. MADISON CONSTRUCTION, L.P. vol- x.351.. pg. /,!?2 c m E O U W J > - W C O O O U V ¢ O � O Z C O Y n J O Q pA C J O U O m O a N c d O O a cum ao �v N L m E� O m v o L w m �, o c c v O U a Z am O V N y m O c a > 0 U N o @ YLO U W _ m N(.7 O 7 V1 i6 W W Q lD 1� C N (a lO a Lfl d r O Q1 N G1 E m C m z N V C C 011 v v •� � � oD 09 L J a a C W C m m [) O Y f0 N z w N N lO O 1� U CON m my a O v m o N 2 a) m w o w a a N a• N n vmi v m � m c v � z o m E m C) 'c° m m m � c m E O U W J > - W C O O O U V ¢ O � O Z C O Y n J O Q pA C J O U O m O O � N d a N i y a C U Y J N L m Y = — U c C C a L y J Ca C C E �n y a J O E L J o c c v O U a Z am O V N y m O c a > 0 U N o @ s County Urchasift Department 26o, SOUTHTEXAS AVE SUITE 352 BRYAN,T%77803 j614296 -4293 PHONE (.979) FAX (979) 361 Febivary 16, 2016 :* Fairlbanki S61es Phone: 281-821-5173 8331`FM 1960 pypqss Fax: Hpmblc,TX11338 Email: gchristlansen�a�fzirbanksxom Atm.` :,Grcj Christiansen Re: Renewal of Cant , ractfor Truck Scale Maintenance -2016.173R, previously known as 2015468 and. Aruzos County iplamciates the quality iwrk your company has provided and would like to exercise the renewal option . . for Truck Scale -MainiAF;anCc— 2016-173R, previously knownus 2015-46R and 2017-49. All terms, 'conditions ,and pricingShull remain thcsaibd. This renewal will be for one year starting May 14, 2016 through May -To accept the renewal option,; please fill out the information and sign below. Return the signed documents by email ,to,cti6ifon,,abrazoscoufib,Lk.g6v or fix to (979) 361-4293: Please then submit the original signed documents and n undated Ciftiricate of Insurance i6v mail to (headdress listed ahovL.Piease return acceibtarue�as soon k'sible If 6 hquestions;I rriiy be reached at (979) 3614291. 'you, ave ny. I vol.—,,U5,� Pg- [Vor�/:=�| LO to °Ip v § _ §■ LL§� 20[ ,; �!© d ® ) ) ~ ` 0 - ( m ~ }\ \ \ ��» c6 6 ±" /y Vim`© 2 �) 2� t « \ 2mA / ] m q ) 2 i _ f ~ ~ Eƒ/ C G _ ^ _ 2 ) - G I to / \ / ® ? L Jf - 0 \ \\\\\\_ 00 \ \\ ® 0 §}{},°— CZ/® ': 0 /] ,rye — \ o = (D [\/a z a §�2*{)/=r/2«y/{JJ k t e ■ 'uEka"« *&�0a)2- IL / RLLI 2f{s®CL »/j[30caF-O [Vor�/:=�| BRAZOS COUNTY COMMISSIONERS' COURT ACTION FORM DEPARTMENT Road and Bridge DEPT. NUMBER 56001000 DATE OF COURT MEETING: March 22, 2016 ITEM: Consider and take action on the Final Plat of Indian Lakes Subdivision. Phase XXII (22): Lots 1-12. Block 33 & One Common Area: 27.830 Acres; J.M.Barrera Survey A-69• (College Station ETJ) Brazos County, Texas. Site is located in Precinct 1. SOURCE OF FUNDS: N/A NOTES/REQUIREMENTS: • Owner: Smiling Mallard Development, Ltd. • Engineer/Surveyor: McClure & Browne Engineering/Surveying, Inc. SUBMITTED BY: I� ( �)E- R. Alan Munger, E. County Engineer ACKNOWLEDGED BY: Commissioner Lloyd Wassermann Precinct 1 This Request is ROV ioners' Court E. Duane Peters, County Judge Date Vol. _�� Pg. �� vu u. GL NUJ J. GJ1m UI .IVa V V U 11ly W U V l% UI Ingd Application for Development Brazos County Subdivision and Development Regulations Brazos County Engineering Department 2617 Hwy 21 West, Bryan, Texas 77803 (979) 822-2127 NO. U7io r. L Office Use Only. Master Plan _ :;.i.: ;i :Final Plat ✓ Re,Plat _ Amending Plat Property Description: ; Road Locafion:_ `• oi-ra of &-rCKS£CT1-,j JF rt44Co CRINY-„1 £ kinAVA Legal Description: At. eY PNASE 2, 6WCV,, 33 f Lo -TS t=/ - Subdivision Description Subdivision Name: I tJAi An/ LAVE 5 PNA 5 C a 2L Total number of lots: /. Total Acreage: ;t,74 30 Property Owner Ownername(s): SY+rrLrNC- /SIALLAft%) hEL) Et.oP ir�l7 L7i) Current mailing address: .oP E 0291 S7. t?Er i�j f1CyA" iN Phone number(s): 009) R 46 — y3Y i Applicant or Authorized Agent, Engineer or Surveyo'i• NamoandAddress;7RA✓r 1 2%/ t ✓. r ,SA/hC fAAh9cSJ- /IT 1jls'a,)4F Phonenumber(s): (c, 1) d 5'6- V78,4 Name and Address: Phone number(s): Application is for Residential (AKMobile Home Park O Commercial ( ) Other ( ) Is any of the property located in a Floodplain or Flood Hazard areal )UL) Cyes/no) Aoi;nowledgrnent: no flood harard beuadray maps and othv flood dam used by Brazos County in evaluazing Bond haaards fo p,opwd developments are considered reasonable And rAwle for regulatory purposes and one based on rhe best available scientific ad enginetring data On rare o tom greeter floods can and will occur and flood heights may be increased by man-made or natural causes. Issuance of a Floodplain Permit in accordance with Bre Brawl County Flood Damage Prevention Ordinance docs not imply dat develop mem outside the arm ofspecial food ba d will be free from flooding or flood damage issuance ofa permit shall not create liability on the pert of Brazos County or my ofEcer or employee of Brazos County in the event flooding or good damage does carr. Is pari oral] of the property within an ETJ ofa City? `IES' (yes/no) Villany construction occur in. TxDOTright-of-ways4 A,'O (yes/no) Application Check List: Copies of finished plat with corrections (if any): V 9 copies to Brazos County 9! One (1) copy to Brazos County Health Dept, 9�' One (1) copy to Brazos County 911 H]/ One (1) copy to local Water District or Company Letters ofapproval (to be sent by the approving institution directly to Brazos County Engineer ng): U Letter from Brazos County Health DepL — For onsite sewage evaluation. ❑ Letter from Brazos County 911—For road names. ❑ Lent:rfrom Water District orCompany. — Swing water availability, etc., [f property is within an ETJ ofa city: ❑ Approval notification from appropriate city. Applicant attest that they have signed this application in the capacity designated, if any, and fiirihrr attests That they bave read document and the statement contained herein and any attached are true and factual. All applicants are encouraged to review the County Regulations prior to any plat submittal. It is understood that this application is not finished or dated until all documents listed above are filed at the Brazos County Engineering Office and all applicable blanks'are filled in the application above. Applicant's Signature Date County Witness Vel. Pg._ /8'_. i- Co.);4T oj_ V u n. Lt. GuuJ J. ui"i .. u.. v, wuu.r i%uau a of i u g t NO. UJg0 r. J Engineer/Surveyor Check List for Plat Pre -Approval 0-" 1) Property located within a City Extra Territorial. Jurisdiction (M), contact with that City, isrequired before plat app"aral. Q 2) Drawn on 24" x 36" sheet to scale of 100' per.inch or larger. If mots than one sheet, an index sheet showing entire subdivision at a $cale of 500 feet per inch or larger. E;-- 3) Include the words; "MASTER DEVELOPMENT PLAN—NOT FOR RECORD" or "FINAL PLAT" or "RB -PLAT" or "AMENDING PLAT' in letters Y." high. 9�-' 4) Vieiniiy map which includes enough ofsurrounding area to show general location of subject property in relation to major roads and any city limits and county boundaries, No scale required but include north arrow. OX 5) Title Block with tho following information; 9' Name and address of subdivider, recorded owner, planner, engineer and surveyor. 1D/ Proposed name of Subdivision. (Subdivision ttamc & Sheet names will be approved through the Rims County 911.) (Replats need to retain original subdivision name.) 1=1 Date ofprepatadon. (Include the date ofany revisions on the plat.) U,'- Engineer's scale in feet. W Total area intended to be developed. 2 Re -plat or Amending Plat, existing lot and block description or Abstract name and number. NY 6) North Arrow. 7) Location of any current city or county limit lines, ifapplicable. D- 8) Subdivision boundary indicated by heavy lines. Boundary must include all of parent tract. 0/ 9) Descriptions by metes and bounds of the subdivision which shall close within accepted land surveying standards. (Shown on drawing; not separate description) B*'� 10) Primary control points or descriptions and ties to such control points, to which, later, all dimensions, angles, bearings, block numbers, and similar data shall be referred. The plat shall be located with respect to a comer of the survey or tract, or an original comer of the original survey of which it is a part. Cr 11) Name of contiguous subdivisions and names of owners of contiguous parcels of unsubdivided land, and an indication whether or not contiguous properties are platted, 1K 12) Location of the 100 Year Floodplain and Floodway, if applicable, according to the most recent available data. 8� 13) Note the FEMA FIRM Map panel number and revision date on plat. 5"' 14) , Topographic information, including contours at two foot (2 ft.) intervals, ftowline elevation and flow direction. tl� 15) Proposed drainage concept shown on plan, showing now paths to primary system. Vol.. 5 . Pg. /31�' �. c,. cvvv vc-r„,. ,.v, vvuuiy nv¢a Vf uI IV C IVU. 1/M r, 4 16) Locate and Describe, with accurate dimensions, bearings or deflectign angles and radii, area, centerangle, degree of curvature, tangent distance and length of all curves; show existing items that are intersecting or contiguous with the boundary of or forming a boundary with the subdivision, as wellas, those within the subdivision; for the 61lowing: Existing Proposed Streets: continuous or end in a cul-de-sac, stubbed out streets must and into a temp, tum around unless they are shorter that 100 feet. IY M� Public and private R.O.W. locations, width(s) and names. (All existing and proposed R-O W.'s sufficient to meet County and City Regulations, if applicable.) V P-1 Street offsets and/or intersection angles meet ordinance. tY tY Alloys Ca— t7/ Reserve tracts. CY Well site locations. !Y W- Pipelines: label company with volume and page. ?� 0� Utility Services. (water, wastewater, electrical, natural gas, cable, phone, etc.) 6Y 13' Easements. CY P� Drainage Structures and improvements per engineering analysis. d] lt" A number or letter to identify each lot or site and each block. 9 @-� Public areas. Cf� Other Public improvements, including but not limited to parks, schools and other public facilities. 17) All off-site easements for infrastructure const[uetien must be shown on the final plat with a volume and page listed to indicate where the separate instrument easements were filed. Separate instrument easements must be filed prior or concurrently with final plat. Z� IS) Proposed phasing. The Master Plan and each phase must be able, to stand alone to meet ordinance requirements. Infrastructure costs should be separate for each phase of the subdivision. ' 13— 19) Bring this check list with one copy of plat forpre•approval to meeting; date and time set by County Engineer or Planner. Meeting location set at County Engineering office. Brazos County Engbacetvtg Road & Bridge Depattrnent. 2617 Hwy 21. West Bryan, Texas 77803 (979)822-2127 , - �.11. <,v. JJLU, wu„iy nuau a Driuge NO. MO r. 7 Brazos County Pre-Appliestion For Plat ApproVal Date: $ 3 )S Mas[er.'Plan Final Plat Re -Plat Amending Plat_ 'Date& Timcassigned for Application and Plat Review witt,County Engln=.or Planhet: ri Description of Propet'(y; Subdivision Name: _)AN bi rA A/ LAV ES ?445'E AZ PropettyLocation; So.-7ii ol= /// —EK5Ec7ior✓ of Cc/A(0 cAr Yo J 6 9,At�Ac,EL (, ZT Legal Description: _)NO,6,J LAu£S , YDuASE e?�r BLocK 33 cr,-rS Applicant or Authorized Agent: -- 9,hUlS Phone Number (s): CS -)9 J J, y 6— '> 5Ay This is a notification to Arms County that a plan for development exists for this noted piece of property, This is not the official Application for Development. This also does not commit the Applicant listed above to file an Application for Development or to file any type of plat for Record. All properties within the County of Brazos are submitted to the rules and regulations set up by the Brazos County Commissioners Court. Copies of the Brazos County Subdivision and Development Regulations and the Brazos County Flood Damage Prevention Ordinance are available from the Brazos County Engineering and Planning Departments. All applicants are encouraged to review the regulations prior to any plat submittal. Attached is a general check list to be used by a Registered Engineer or Registered Professional Land Surveyor, licensed by the State of Texas, for the sole purpose ofsammarizing the needs of finished plat. All County and City Ordinances and Regulations must he met. This is not a short list of details of said regulations. Details of the idems listed are hr said ordinances, and said ordinances take precedence over this check list. Applicants Date of Signature _/94 BRAZOS COUNTY, TEXAS BUDGET ANIENDMENT(S) FOR THE 2015-2016 BUDGET YEAR NO. 15/16 26.1-26.10 On this the 22nd day of March 2016 at a regular meeting of the Commissioners' Court, the following members were present: A. Duane Peters, County Judge, Presiding B. Lloyd Wassermann, Commissioner, Precinct 1 C. Sammy Catalena, Commissioner, Precinct 2 D. Kenny Mallard, Commissioner, Precinct 3 E. Irma Caulcy, Commissioner, Precinct 4 F. Karen McQueen, County Clerk The following proceedings were held: THAT WHEREAS, on 22nd day of March 2016 the Court heard and approved a budget amendment for the 2014-2015 budget year for Brazos County, Texas; and WHEREAS, expenditure is necessary due to the necessity to meet unusual andunforeseen conditions which could not be reasonably included in the original budget adopted 8 September 2015, the following amendment(s) to the original budget are hereby authorized, as described on the attached page(s). ADOPTED AND APPROVED this the 22nd day of March 2016. THE COMINIISSIONERS COURT OF BRAZOS COUNTY, TEXAS. By: Duane Peters, County Judge Original: County Clerk's Office and Attached to the original budget BRAZOS COUNTY, TEXAS BUDGET AMENDMENTS No. 15116 - 26.1 s122nn16 FUNDI DIV ACCT PROJ I DR/CR ACCOUNT NAME Increase I Decrease 1500 30000100 61151100 UR LEOSE Constable Pct I S.32 IS00 1 30000100 61151200 I CR ILEOSE Constable Pct 2 II 555 IS00 30000100 I 61151300 1 DR ILEOSE Constable Pct 3 I 2.761 1 IS00 30000100 1 61151400 I DR LEOSE Constable Pct 4 SS.47 I 1500 30000100 61151500 I DR LEOSECountvAaorncv 43.171 IS00 I :0000100 1 61151900 1 DR I LEOSE District Attorney 2591 IS00 30000100 1 61152500 IE ILEOSESheriffOffice 909.66 IS00 45063000 DR LEOSE Training, 625.12 IS00 47030000 DR Restricted Futtd Balance 147.21 I I I I I I I I I I i I I I I I I i I I i I I I I I I I I I I I I i I i I I I i I I I I I 1 I I I I I I I I 1 Lmc Enforcement Officers Standards and Education (LEOSE) To inodifv the hudg,et of LEOSE Fund to reflect the LEOSE funding, available to various law enforcement departments for fiscal year 2016. I I I I I I I I I I I I 1 I 1 I I I I i I I I I I I I I I I I I I I I 1 Vol.= r3 V Pct. A'o BRAZOS COUNTY, TEXAS BUDGET AMENDMENTS No. 15116 - 26.2 3/2 212 01 6 PFUND DIV ACCT PROJ DR/CRI ACCOUNT NAME Increase I Decrease I i00 63000=00 50257000 CR Eeui meat -Radios 212.91500 6300000 60357000 I DR I E ui ment - Radios 212.91 I I I I I I I I I I I I I I I I I I I i I I I I I I I I I I I I I I I I I I I I I General Capital Projects- Juvenile Reallocation of funds to the proper accol-mt clue to picins of radios for the Juvenile De• attment. I I I I I I I I I BRAZOS COUNTY. TEXAS BUDGET AMENDMENTS No. 15116 - 26.3 3122/2016 FUND DIV ACCTPROJ DR1CR ACCOUNT NAME Increase Decrease I 4500 630005001 808900001 CR lVehicles !.314.62 4500 63000500 ,0392800 DR Vehicles - SO 1.314.62 I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I 1 I I I I I I I I I I Gcnarnl Cn pita{ Projects - SO i Reallocation Cf funds for the purchae cf tintins and the uninsralllinstall of ec ui ment for Unit 154. I I I I I ( I I I I i I I I I I I I I I I I L_W�_ BRAZOS COUNTY, TEXAS BUDGET AMENDMENTS No. 15/16 - 26.4 3122/2016 FUNDI DIV ACCT I PROJ DR/CRI ACCOUNT NAME Increase Decrease 4500 1 63000500 60360000 CR. Furniture I I 5.0504_7 45001 630005001 69342000 1 1 DR IFumiture 5.050.371 I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I General Capital Project,- Brazos Center Reallocation or fund, to the proper account due to ricin; of the concourse seatino at the Brazos Ce:iter. I I I I I I I I I I I I I I I BRAZOS COUNTY, TEXAS BUDGET AMENDMENTS No. 15116 - 26.5 FUND DIV ACCT PROS DRICRI ACCOUNT NAME f Increase Decrease 4500 630005001 67670000 j CR Printers 223.291 4500 1 63000500 60500000 1 DR F Ui Ment fi IT Ertlrancements 22,.29 ly I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I 1 I I I I I I L i I I I I I I I I 1 I I I General Capital Projects - IT Reallocation of fund; to the proper account dire to ricin_ of a re placement printer. 1 I I I I I I I I I I I I I I I I I 5z pg� AW] BRAZOS COUNTY, TEXAS BUDGET AMENDMENTS No. 15/16 - 26.6 3/22/2016 FUNDI DIV ACCT PROJ DRICRI ACCOUNT NAME Increase Decrease 0100 1 11001500 1 61130000 1 CR Contim enc% 33.SSS.00 0100 140002001 50211000 1 DR Com urer-Software 33.55S.00 I I I I I I I I I I I I I I I I I I I I I I I I 1 I I I i I I I I I I I I I I General Fund Contin2encv and 1.T. Services Reallocation of funds to the pro ter division and account for the additional lieensinu and implementation for the PLVIS system. I I I I I I I I I I I I I I I I f I I I L I VOL _02 pg,---/ T BRA70S COUNTY, TEXAS BUDGET AMENDMENTS No. 15116 • 26.7 3/2212016 FUND DIV ACCTPROD 1 DR/CRI ACCOUNT NAME Increase Decrease 4500 630005001 50590000 Tj I CR lVehicics 2.140.00 4500 P3560100 HS93040 DR Vehicle - Constable Pct. 4 ?.140.00 I I I I I I I I I I I I I I I i I I I I I I I I I I I I I I I I I I I I I I I I I I i I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I i I I I I I I I i I I I I General Capital Projects - Constable Pel.4 Reallocation of funds for the purchase of tinting and the wtinstall/install of e ui mem for Unit 505. I i I I I I I i 1 I I I I I I I I I I I I I I I I Vol. _�. v P9.-/-/-y-I. BRAZOS COUNTY, TEXAS BUDGET AMENDMENTS No. 15116 - 26.8 3122/2016 FUNDJ DIV l ACCT - PROJ DR/CR ACCOUNT NAME Increase Decrease 01001 56001000 611=0000 CR Conlingenc 350.000.00 0100 9l l 10000 DR 11 ransfer to Capital Improvement Fund 350,000.001 4500 I 49020000 1 CR ITransfer from General Fund I 350,000.001 4500 63560100 I /1025000 1 DR (Contract Services 350.000.001 I I I I I I I I I I 1 I I I 1 1 I i I I I 1 I I I I I I I I I I _ I I I I I I I I 12 C B 13rid�e and Greens Prairie Trail 1 Reallocation of funds for Green fh'airie Trail extension at FNI 2154. I I I 1 I I I I I I 1 I I I I I I I I I I I I I I vol_ I g. / ja Now Sheriff Reallocation of funds BRAZOS COUNTY, TEXAS BUDGET AMENDMENTS No. 15/16 - 26.9 3/22/2016 Vol. 351 pg—/✓�� BRAZOS COUNTY, TEXAS BUDGET AMENDMENTS No. 15116 • 26.10 3122/2016 FUNDI DIV ACCT PROJ DR/CRI ACCOUNTNAME Increase Decrease oloo I zvaouoo 60050000 CR 350.00 0100 2440il00 65320000 DR 350.00 I I I I I I I i I I I I I I I I I I i I I I I I I I I I I I I I i I I I I I I I I I I i I I I I I I I I I I I I I I I I I i I I I I I I Justice of the Peace. Pct. =a Reallocation of funds to 2urchase a motor for a time clock. I I I I I I I I I I I I I I I I I PERSONNEL CHANGE OF STATUS REQUESTS Commissioner Court Date: March 22, 2016 Department Submitting Information: Human Resources Purpose of Submissions: Consider and Take Action on Change Requests Page: 1 of 2 Department Submitting Employee Request Action Requested Request(s) Applies To Facility Services — Landscape Crew Green Jr., Leonard New Hire Johnston, Samuel Resignation Justice of the Peace Pct. 4 Gamboa, Patricia Resignation Walker, Janetta New Hire Juvenile Services — Administration Roberts, Bobbie Transfer w/in Dept. Juvenile Services — Detention Canales, Mayela Step Increase Mireles, Romeo Step Increase Pequeno, Deeanna Promotion Juvenile Services — TJPC State Aid Desir, Raymond Promotion Road & Bridge Sheriffs Office —Administration DeJesus, Andres Hines, Scott House, Garrett Sheriffs Office — Detention Bowser, Melvin Collins, Shantell Hyney, Vincent Transfer w/in Dept. Transfer w/in Dept. Group & Step Change Transfer Win Dept. Step Increase Transfer Win Dept. Vol. _.�.j Pg._/ 33 ! El PERSONNEL CHANGE OF STATUS REQUESTS Commissioner Court Date: March 22, 2016 Department Submitting Information: Human Resources Purpose of Submissions: Consider and Take Action on Change Requests Page: 2 of 2 Department Submitting Employee Request Action Requested Request(s) Applies To Treasurer's Office Candelaria, Jamie Step Increase Glidwell, Lana Step Increase Gonzalez, Melissa Step Increase Morgan, Ashley Step Increase Approved in Commissioners' Court: March 22, 2016 County Judge's or Commissioner's Signa e: LL2k::—� (This Copy to be attached to minutes) EV01-19--:57-v- i'g!