Loading...
HomeMy WebLinkAbout2018-06-05 10:00 AM REGULAR MEETING A c: Ileivit •, BRAZOS COUNTY �' BRYAN, TEXAS NOTICE OF MEETING AND AGENDA BRAZOS COUNTY COMMISSIONERS COURT THE COMMISSIONERS COURT OF BRAZOS COUNTY WILL MEET IN REGULAR SESSION ON JUNE 5, 2018 AT 10:00 AM IN THE COMMISSIONERS COURTROOM OF THE COUNTY ADMINISTRATION BUILDING, 200 SOUTH TEXAS AVE., SUITE 106, BRYAN, TX 77803 1. Invocation and Pledge of Allegiance - U.S. and Texas Flag - Judge Peters 2. Call for Citizen input and/or concerns Consider and take action on agenda items 3-12: 3. Approval of the job description for Class Code 0832, Position 13 - Temporary Attendant, Building & Grounds for Expo. 4. Change order number two to purchase order 18001160 to Patterson Architects in the amount of $6,910.98 for additional items. 5. Memorandum of Understanding for the Texas Statewide Interoperability Channel Plan with Texas Department of Public Safety. 6. Approval of contract with Department of State Health Services(DSHS). This contract will allow the County Clerk access to the DSHS Vital Event Electronic Registration System for the purpose of issuing individual birth certificates. 7. Award of RFP # 18-089 Video Surveillance Upgrade for the Brazos County Detention Center and approval of resulting contract. Recommended award to Electra Link. 8. Expenditure Journal Entries FY 17/18 • 050124-050128 9. Tax Refund Applications for the following: • a. Hawkwood Energy Operating - Overpayment $27.85 Vol. Pg. —� • b. Hawkwood Energy Operating - Overpayment$56.20 • c. Hawkwood Energy Operating - Overpayment$78.25 10. Budget Amendments. Budget Amendments FY 17/18 35.1 - 35.6 11. Personnel Change of Status. Personnel Action Forms 12. Payment of Claims. 13. Acknowledgement of Road and Bridge Maintenance Expenditures Report FY18 from January through March. 14. Acknowledgement of the Brazos County Emergency Services District No. 3 Independent Auditors Report and Financial Statements for the fiscal year ended September 30, 2017. 15. Sheriff's report on inmate population. 16. Announcement of interest items and possible future agenda topics. 17. Call for Citizen input and/or concerns 18. Adjourn. Vol. A /el Pg -�-'— 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 submit 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. tt is not the intention of the Brazos 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 Commissioners Court can deliberate or take action only if a matter has been listed on an agenda properly posted prior to the meeting. During the public comment period, speakers may address matters not listed on the published agenda.The Open Meeting Law does not expressly 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 without 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 Section 551.042. INVOCATION My 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. Nb 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, TX 77803 is wheelchair accessible. Handicap parking spaces are available.My request for sign interpretive services must be made two working days before the meeting. To make arrangements. please call (979) 361-4102. The foregoing minutes of the Commissioners Court meeting held June 5. 2018 have been examined and are approved in open Court this 10th day of July 2018, in Bryan, Brazos County, Texas. WA_ _Sii/e./ Duane Peters Steve Aldrich County Judge Commissioner, Precinct 1 •1, : — g-� Sammy Cat. ena Nancy Berr Commissioner, Precinct 2 Commissioner, Precinct 3 "MP* �J,111 Ph .. /.4...A %. Irma auley Commissioner, Precinct 4 Attest: / I Afk l;..:.SL-- ar. McQueen County Cle k A.—_ 1I4/01'. A0 .41 Vol. ) '7t Pg. 6<5 j BRAZOS COUNTY COMMISSIONER' S COURT s';JL DAYOF 4 , 20 ip Ax oc, AM/ L:•: , itia.,3 Name Organization (PLE A;.E '-R1NT (P 7SE PRINT) eb, 'f a,9-,._ Ar Aka-a---- a .0 led,4 el c 9 II 4. ,, �, ..: .��7 , Cor �� `6,r,.. P c.it a .ii bafi4'. j EDM.N� Scene-ri !/ ►tkrrj nk_ ,eo.revt- S.(),- We e $ utd i is I z�^f .11i ,�'� I q_ A„ iz,7-- irogiv7 �y��- i .; i ,may i - „,,, - trt ,,..-ti , Juv . Svcs . vol. /7 pg. TLT ui i Pg Oma• BRAZOS COUNTY COMMISSIONER' S COURT Ltit DAY OF I - , 20/P /010 c> AMS-..' , Name Organization E SE PRINT) (PLEASE PRINT) 0 /fit E wEtc eG rJ A .Ala 0 AILAUE hut(i_JAzithj_ i�.t/4:..�IiI/,.a✓/ ! , / J1 Va. Q/' Pg. `f-Y 1 4"--E Oar •. v . . 5 ¢a p" MINUTES JUNE 5, 2018 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, June 5, 2018 with the following members of the Court present: Duane Peters, County Judge, Absent; Steve Aldrich, Commissioner of Precinct 1; Sammy Catalena, Commissioner of Precinct 2, Presiding; Nancy Berry, Commissioner of Precinct 3, Absent; 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. 1. Invocation and Pledge of Allegiance - U.S. and Texas Flag -Judge Peters Commissioner Catalena led the prayer and pledge in Judge Peters' absence. 2. Call for Citizen input and/or concerns Madison County resident Colvin Walker stated he was in Court to express opposition to the High Speed Rail. Mr. Walker said that the rail will cut his property in half. He said that there is also a historical church and cemetery that will be affected. Mr. Walker is concerned about the decrease in value to his property as well as the effect it will have on three historical properties, school bus routes and rural mail routes. He stated that there is no benefit to Madison County. [v . 2 T / Pg. Art Norann McDonnell was next to speak in opposition to the High Speed Rail. Ms. McDonnell thanked Commissioner Catalena for standing up for the residents affected by the High Speed Rail with his vote last week. She asked the Court to reconsider their support of the rail and stated that Houston and Dallas would be the only ones to benefit. Ms. McDonnell said that the ticket price is $400.00 per person and feels that families will not be using the train when they can travel by car for less money. She said that California's High Speed Rail is a disaster and that this is the wrong choice for Texas. Commissioner Catalena thanked them both for their comments and reminded them that the Court could not respond. Consider and take action on agenda items 3-12: 3. Approval of the job description for Class Code 0832, Position 13 -Temporary Attendant, Building & Grounds for Expo. A copy of the job description is attached. Motion:Approve, Moved by Commissioner Steve Aldrich, Seconded by Commissioner Irma Cauley. Passed. 3-0. Ayes: Aldrich, Catalena, Cauley. Absent: Berry, Peters. 4. Change order number two to purchase order 18001160 to Patterson Architects in the amount of$6,910.98 for additional items. A copy of the change order is attached. Motion:Approve, Moved by Commissioner Irma Cauley, Seconded by Commissioner Steve Aldrich. Passed. 3-0. Ayes: Aldrich, Catalena, Cauley. Absent: Berry, Peters. 5. Memorandum of Understanding for the Texas Statewide Interoperability Channel Plan with Texas Department of Public Safety. A copy of the agreement is attached. Motion:Approve, Moved by Commissioner Irma Cauley, Seconded by Commissioner Steve Aldrich. Passed. 3-0. Ayes:Aldrich, Catalena, Cauley. Absent: Berry, Peters. 6. Approval of contract with Department of State Health Services(DSHS). This contract will allow the County Clerk access to the DS HS Vital Event Electronic Registration System for the purpose of issuing individual birth certificates. A copy of the contract is attached. Motion:Approve, Moved by Commissioner Irma Cauley, Seconded by Commissioner Steve Aldrich. Passed. 3-0. Ayes:Aldrich, Catalena, Cauley. Absent: Berry, Peters. Vol �� Pg. g 477 1 7. Award of RFP# 18-089 Video Surveillance Upgrade for the Brazos County Detention Center and approval of resulting contract. Recommended award to Electra Link. A copy of the contract is attached. Motion:Approve, Moved by Commissioner Steve Aldrich, Seconded by Commissioner Irma Cauley. Passed. 3-0. Ayes: Aldrich, Catalena, Cauley. Absent: Berry, Peters. 8. Expenditure Journal Entries FY 17/18 • 050124-050128 A copy is attached. Motion:Approve, Moved by Commissioner Irma Cauley, Seconded by Commissioner Steve Aldrich. Passed. 3-0. Ayes: Aldrich, Catalena, Cauley. Absent: Berry, Peters. 9. Tax Refund Applications for the following: • a. Hawkwood Energy Operating - Overpayment$27.85 • b. Hawkwood Energy Operating - Overpayment$56.20 • c. Hawkwood Energy Operating - Overpayment$78.25 Motion:Approve, Moved by Commissioner Irma Cauley, Seconded by Commissioner Steve Aldrich. Passed. 3-0. Ayes: Aldrich, Catalena, Cauley. Absent: Berry, Peters. 10. Budget Amendments. Budget Amendments FY17/18 35.1 -35.6 35.1 Reallocate funds for Information Technology. 35.2 Transfer funds from Contingency Fund to Sheriff's Office. 35.3 Transfer funds from Non-Departmental to Information Technology. 35.4 Reallocate funds for Juvenile Services. 35.5 Transfer funds from Non-Departmental to Facility Services. 35.6 Transfer funds from Contingency Fund to Constable, Precinct 3. Motion:Approve, Moved by Commissioner Steve Aldrich, Seconded by Commissioner Irma Cauley. Passed. 3-0. Ayes: Aldrich, Catalena, Cauley. Absent: Berry, Peters. 11. Personnel Change of Status. Personnel Action Forms A copy of the Personnel Change of Status requests is attached. Motion:Approve, Moved by Commissioner Irma Cauley, Seconded by Commissioner Steve Aldrich. Passed. 3-0. Ayes: Aldrich, Catalena, Cauley. Absent: Berry, Peters. vs. a %tl.. pg - � 12. Payment of Claims. Claims 8004406—8004574 Motion: Approve, Moved by Commissioner Irma Cauley, Seconded by Commissioner Steve Aldrich. Passed. 3-0. Ayes:Aldrich, Catalena, Cauley. Absent: Berry, Peters. 13. Acknowledgement of Road and Bridge Maintenance Expenditures Report FY18 from January through March. The Court acknowledged receipt of the Brazos County Road and Bridge Maintenance Report for January through March of 2018. 14. Acknowledgement of the Brazos County Emergency Services District No. 3 Independent Auditors Report and Financial Statements for the fiscal year ended September 30, 2017. The Court acknowledged receipt of the Brazos County Emergency Service District No. 3 report ending September 30, 2018. 15. Sheriff's report on inmate population. Sheriff Chris Kirk stated there were 656 inmates in jail, 543 inmates are male and 113 are female, 35 have electronic monitors and 10 are pending for monitors. 16. Announcement of interest items and possible future agenda topics. Commissioner Cauley thanked the Road and Bridge Department for their work on McAllister Lane in Precinct 4. 17. Call for Citizen input and/or concerns There was no citizen's input. 18. Adjourn. 'vat. ,9 7e/ Pg. 47/7 z4;93 i. / ._.. u . ?v-`.'-`fit t ; ,,. (I2140-;',� �_ Brazos County Template Rerison 1.20a11Yt012 ;, e ,� ar Job Description Last Updated: September 2014 Class Number: 832 .. .__ Title: - Temporary Attendant, Building &Grounds(1040 hrs.) Pay Group ; 09 Department Exposition Complex FLSA Status: i Non Exempt Reports To Event Supervisor, Event Coordinator &AB Managers El 1.Approved Date: 110/01/2016 EEOC Category: i Service/Maintenance i t I. 1. Position End I ;Temporary Date: 1'09/30/2017 Employee ,k Signature General Summary Per-tenni and monRors daily operational responaitiilltles Including jennorial duties,responslbi?itie5 and maintenance'of the Brazos Co-unii Exposition Complex including setting-up,cleaning and leafing-down events. Essential Duties perate. moderate implementswith ,forklifts and skid-Steer batlers;Sets upllea7s Gown rodeo equipment horse i stalls cattle ties,panels and pens; Sets upfears down meeting and event rooms,.including stages,dance floors,tables,chairs and equipment and assists with the sound/electrical system setup and/or teardown;Cleans meeting and event rooms,including sweeping,vacuuming and taking out i trash;Cleans restrooms,Including using commercial chemicals to remove stains/odors and keeps them free of litter;Strips,waxes,buffs and scrubs i floors as needed and Instructed.Keeps all floors dusted,mopped,and vacuumed;Changes light bulbs and distributes supplies as necessary:Assists i In painting and other maintenance projects as necessary;Raises flags daily,weather permitting,takes down flags before leaving unless otherwise f' specified,Operates a vacuum cleaner and hand cleaning materials,supplies and equipment;Cleans windows,doors,floors,water fountains,and ?_ furniture;Keeps air conditioning adjusted to use requirements;Empties and cleans waste receptacles and property disposes of trash;Assists visitors in a polite manner during events at the Exposition Complex Keeps janitorial and storage areas clean and organized;Must be willing to work various i hours as needed including some nights;.weekends,holidays,etc:;Communicates with Exposition Complex administrative assistant/secretary regarding janitorial supply inventory;Assists as necessary In inventory control including equlpmenl and consumables;Assists in scheduling work,. T creating assignments and/or monitoring work as necessary for pan-time and/or temporary building attendants/staff. Other Duties as assigned (1%p) Supervision Received: Event.: Supervisor,Event Coordinator&AlfManagers - -" Given: I-This Isa non-supervisory - --- -- - -- I; ` Education �, --- .. _. _ Required High sesool k or its gee eand equivalent combination'of education and experience that provides the required knowledge,skills and abilities Preferred: : } Experience . . Required: Al least one year of related work experience. , - - — ' Preferred: Some experience In operating a tractor and/or related equipment Is preferred, - Certificates, Licenses i Registrations 1 ��_ 1 Required: iv,itie -- ._ . — i Preferred: i [VOI. ,2 7V Pg. . • - . . PhySical Demands . • . Typical: The physical demands described here are representative of those that must be met by an-•erriployee to successfully perform the essential functions of this job. Reasonable accommodations may bemade to enable individuals with disablfillesto perform the essential functions.While performing the duties of this job,the r.employee is regularly required to sfiose hand to finger,handle,or lo feel;reach with hands andarms;bend and kneel and talk and hear. The employee frequently is required to stand and walk:.The employee must frequently lift and/or move objects weighing up to 100 pounds,such as begs of mulch and rocks. Spedfic • vision abilities required for this job include close vision.dlitanoe vision,end the ability to ai,djust focus.. • ... _ Knowledge, Skills, & • _ Abilities ..„ Typical: Safe operation of custodial and maintenance equipment,including the safe use of comma rdal cleaning chemicals.Ability to foltow oral and written instructions;ability to learn the proper use of janitorial equipment • and supplies;ability to make minor repairs;ability to communicate and work effectively with ce1rvorkers;abitity to perform physical and strenuous work:and an ability to understand and follow Brazos County safety policies. r • -• • - • , -- • • -:--WotkEhitironmeht• P • " . „ . ..„. . . • - • • Tyjiloal:'C.Thelkoik environmeht•characteristIcs described here are representative of those an employee encounters ._ ir while performing the essential functions of this job. Reasonable accommodations may be made to enable Individuals with disabifitlas to perform the essential functions.The noise level in the work e nvtionmaii is frequently laud. The employee is constantly required to work closely with others as a part of a leamrlo perform multiple tasks.simultaneausly,and switch from one task to another. The employee is frequentlyhequired to work under time pressures and meet deadlines. The employee may be exposed to extreme weather conditions, • APP P • 1),„ • • 5" lb ,coy Duane Pe •rs Dai- County Judge •-• (vol. 72.779/ Pg. 37 PAT/TERSON • A CHITTS 701 South Texas Avenue Bryan, Texas 77803 Voice - 979 775 6036 CHANGE REQUEST Email — design@patarch.com b'°"g" www.pattersonarchitects.net AUTHOR I Z AT JO N PROJECT: Brazos County Courthouse Phase V • 2014-1462 TO: Brazos County Contract#(979)361-4292 200 S. Texas Avenue, Suite 352 Bryan, Texas 77803 ATTENTION: Charles Wendt Phone: (979) 361-4292 Email: cwendt@brazoscountytx.gov ADJUSTMENTS FOR CHANGES IN WORK Change Change Summary of Work Fee% A/E Fee Request it Request Date Three (3) 05/31/18 Change Order# 1 $45,480.00 10% Paid $40,825.00 Due $4,654.70 05/31/18 Change Order#2 $22,562.85 10% $2,256.28 Total Due $6,910.98 Respectfully Submittee red A. Patterson, Jr.AIA Patterson Architects • RECEIVED: MAY 312018 I31-HLUJ CUUN I Y PURCHASING Vol. 22V Pg. ,S ._... .5 a �" v a ,Y A(•,•'-':_ i 98eL® ' y 'k "" t�Y z 1% \)1x611 a,�fi' ,N 9 l i rl1 ..1„-''i- 1:',72:e-,-J-7 nt y. Texas Statewide Interoperability Channel Plan For FCC Designated Public Safety Interoperability Channels 150 MHz—800 MHz Bands Developed By Texas Statewide Interoperability Executive Committee (TSIEC), the Texas Interoperable Communications Coalition (TxICC), and the Texas Department of Public Safety (TxDPS) Revised January 2018 (Change #19) V01. �2%Gf Pg. . 2 1 RECORD OF CHANGES Texas Statewide Interoperability Channel Plan CHANGE# DATE OF CHANGE DATE ENTERED CHANGE Issued 04-1-2005 Initial Issue 04-1-2005 1 4-6-2005 Deleted "narrowband"from phrase 4-6-2005 "narrowband 800", pg. 14. 2 4-6-2005 Frequencies transposed in Figure 5, 4-6-2005 pgs. 15& 30. 3 4-6-2005 Deleted word "refarming"from 4-6-2005 "refarming order", pgs. 15&30. 4 9-7-2006 Corrected error in 700 MHz channel 9_7-2005 frequencies, pgs. 13-14, &29. General edit; simplify provision for 5 6-10-2007 encryption; add new/changed channel 6-10-2007 labels, clarify 1/1/2013 deadlines Name of plan changed to add the word "Statewide". General edit; Modified background note and text to require 6 9-25-2007 P25 NLT 1/1/2013; added tactical 10-20-2007 repeaters; dropped 700 MHz channels 1 MHz; changed 800 MHz NPSPAC channels by 15 MHz. Corrected order of frequencies used in 8TAC95D and 8TAC96D. Extended 7 01-22-2008 transition date for P25 CAI digital until 01-22-2008 1-1-2015. Changed VTAC17 and VTAC19 availability date to 7/112008. Removed Texas Government Code 8 06-09-2008 Chapter 411.0105 (Public Safety 06-09-2008 Radio Communications Council) 9 06-24-2008 Changed marine channel date due to 06-24-2008 FCC delay 10 11-05-2008 Removed Marine channels from plan 11-05-2008 due to FCC rule amendments 11 04-20-2009 Updated narrowbanding requirements 04-20-2009 for 1/1/2013 12 08-31-11 Updated MOU language 08-31-11 Updated Modulation requirements, removed Digital P25 Requirements, 13 03-06-12 Added Fed VHF Repeaters, Changed 03-06-2012 Channel Coordination to IC, Updated SW IC 14 03-22-12 • Changed Texas Law 1 to 03-22-12 TXCALL1 D and Texas Law 2 to 2 vol. . •Z 7V Pg. 57 TXCALL2D • Added 'Office of the Texas SW IC' or'TxICC'to S I EC references • Removed references to P25 compliance by 2015 • Added reference to compelling reason exception for P25 • Clarified wideband and narrowband for modulation and encryption • Added footnote about how to access additional VHF Repeater Channels in an emergency • Updated tables to ensure headings were consistent throughout • Created separator line for Repeater Base Configuration in Tables 2 and 5 • Separated Table 3 into two tables, changing the Tactical Repeater Configuration to Table 4 • Created a new Table 6 for Use within Border Area for Rebanding Border communications • Changed Emission Designator to 20K0F3E for 800 NPSPAC Interoperability Channels • Updated MOU language to clarify VFD signatures • Fixed Portable channel table on 15 1-25-13 page 19/20 to properly show 1-25-13 mobile and repeater channels • Added Mobile Satellite Talkgroup, section 8 • Updated MOU to include MSAT • Added Statewide Radio ID Plan, section 9 16 5-13-14 • Added Acronym List,section 10 5-13-14 • Removed wideband and narrowband references • Updated table numbers to align with section numbers I • Added VTAC17&17D • Added recommended short list of VHF and 700 channels for programming • Added 7CALL70 and 7CALL70D channels 17 5-27-15 • Added text that 700 MHz 5-27-15 interoperability channels must always use P25 CAI digital conventional Modulation • Removed emission designators 3 Vol. r'g. SJR 11K2G2E and 11K3F3E • Updated Station Class field in 700 MHZ and 800 MHz channel tables from FX1 T/MO to FB2T/MO and FX1T to FBT for direct channels • Indicated which 700 MHz channels should not be used within 70 miles I of the US I Mexico border • Updated Statewide Coordinated P25 Radio Unit Identification (ID) Plan guidance • Added new 700 MHz Air-to- Ground Channels • Added new UHF and VHF Federal Interoperability Channels • Added reminder: Fixed base 18 12-07-17 repeaters as secondary use—all 12-07-17 . frequencies • Updated MOU to reflect new Air- to-Ground and Federal Interop Channels • Changed section headings to match with NIFOG color shading • Updated VHF and 800 MHz CTCSS tones in compliance with the NIFOG • Updated Federal Agency table 4.4 with correct RX frequency • Updated FM emission for new Federal Agency channels from 19 1-29-18 11K25F3E to 11K2F3E (*note 1-29-18 the emission is published in the NIFOG is incorrect) • Updated Federal Agency tables 4.5 and 5.3 to list CTCSS tones. 4 Vol. ,72 7c_ Pg. Texas Statewide Interoperability Channel Plan For FCC Designated Public Safety Interoperability Channels 150 MHz— 800 MHz Table of Contents MEMORANDUM OF UNDERSTANDING 7 Purpose 7 Authority 7 Applicability 8 Background 8 Understandings 8 Agreement 11 Background Note to Users of the Texas Statewide Interoperability Channel Plan 12 1. INTRODUCTION 13 2. GENERAL CONDITIONS FOR USE OF TEXAS DEPARTMENT OF PUBLIC SAFETY LICENSED INTEROPERABILITY CHANNELS 15 2.1.Operational 15 2.2.Co-Channel and Adjacent Channel Interference 16 2.3.Calling Channels 17 2.4.CTCSS Coded Squelch for VHF, UHF, and 800 MHz 17 2.5.Modulation and Encryption 18 2.6.Temporary Base and Repeater/Mobile Relay Stations 18 2.7.Conditions for Use of VHF and UHF Federal Entity lnteroperability Channels 19 2.7.1. Requirements per the MOU between the State of Texas and the FCC 19 2.7.2. Suggestions per the National Interoperability Field Operations Guide(NIFOG) 19 3. TRUNKED RADIO SYSTEMS 21 3.1.Statewide Coordinated P25 Radio Unit ID Range Management Plan 21 Table 3.1:Statewide Coordinated P25 Radio Unit IDs—Current Range Allocations 23 4. VHF 150 MHz Channels—SPECIFIC GUIDELINES 26 Table 4.1:Recommended Short List of VHF Interoperability Channels for 28 Texas Public Safety Agencies 28 Table 4.2: Complete list of VHF 150 MHz Simplex Interoperability Channels(12.5 kHz) 29 Table 4.3: VHF 150 MHz Repeater Pair Interoperability Channel Configuration(12.5 kHz)IIII 30 NEW! Table 4.4: Federal Agency VHF Incident Response Interoperability Channels 31 NEW. Table 4.5: Federal Agency VHF Law Enforcement Interoperability Channels 31 5. UHF 450 MHz Channels—SPECIFIC GUIDELINES 33 Table 5.1: UHF 450 MHz Interoperability Channels (12.5 kHz) 34 NEW!Table 5.2: Federal Agency UHF Incident Response Interoperability Channels 35 NEW!Table 5.3:Federal Agency UHF Law Enforcement Interoperability Channels 35 6. 700 MHz Channels—SPECIFIC GUIDELINES 36 Table 6.1:Recommended SHORT List 700 MHz Interoperability Channels for Texas Public Safety Agencies 37 Table 6.2: 700 MHz Interoperability Channels (12.5 kHz) 38 Table 6.3: 700 MHz Interoperability Channels(12.5 kHz) 42 7. 800 MHz Channels—SPECIFIC GUIDELINES 45 5 [v . ;7 V ��. 17 Table 7.1:800 NPSPAC Interoperability Channels(20 kHz) 46 Table 7.2:800 NPSPAC Interoperability Channels(20 kHz) 47 8. Mobile Satellite(MSA7) Talkgroups—SPECIFIC GUIDELINES 48 Table 8.1: Mobile Satellite Talkgroups 48 9. INTEROPERABILITY CROSS-BAND SYSTEMS—SPECIFIC GUIDELINES 49 9.1 Simple Cross-band Repeater 50 9.2 Mobile Tactical Interconnect or Radio Interoperability Gateway 51 9.3 Dispatch Console Patching 52 10. LIST OF ACRONYMS 53 6 Vat ; 7y Pg. _5 MEMORANDUM OF UNDERSTANDING Texas Statewide Interoperability Channel Plan (TSICP) (Original issue,April 1, 2005) Texas Department of Public Safety and the identified Federal Agency, State Agency, Local Jurisdiction, or Emergency Service Organization Purpose This Memorandum of Understanding (MOU) establishes permissions and guidelines for use of interoperability or mutual aid radio channels by: • Local government jurisdictions and their associated emergency response agencies; • State agencies in Texas and their associated emergency response organizations; • Federal agency local units in Texas and their associated emergency response organizations, • Local agency units in Texas and their associated emergency response organizations to use designated Federal interoperability channels, and; • Private sector emergency response organizations licensed or otherwise entitled to operate in the Public Safety Pool as defined in Federal Communication Commission (FCC) Rules, Part 90 (47CFR, subpart B, paragraphs 90.15-90.20). It imposes certain protocols, procedures, and obligations upon jurisdictions hereby authorized to use state-licensed radio channels held by the Texas Department of Public Safety (TxDPS). This agreement supersedes any other previous versions of the MOU. Authority Execution of this agreement by state and local entities is authorized by Texas Government Code, Chapter 791 (local governments), Chapter 771 (state agencies), and Texas Government Code Chapter 411.0105 (Public Safety Radio Communications Council). This MOU satisfies FCC Part 90 rules for extending license privileges to others by agreement. Federal agencies are permitted access to interoperability channels as authorized by the National Communications & Information Administration (NTIA) Manual, 47 CFR, Parts 2.102(c), 2.103; and 7.12. Federal agencies may execute this MOU and shall adhere to the attached guidelines. 7 Vol. 2,2V_ pg. , cat I Applicability This MOU authorizes the use of certain radio frequencies by emergency response organizations as defined by the U.S. Department of Homeland Security's Office of Emergency Communications and the Texas Division of Emergency Management. Generally, this includes organizations in the following governmental disciplines: Emergency Management Public Safety Communications Law Enforcement Public Health Fire Service Health Care Emergency Medical Services Hazardous Materials Public Works/Transportation Governmental Administration This MOU authorizes use of state-licensed frequencies for the purpose of coordination between emergency response agencies and resources. Such coordination may occur during interagency operations, en route travel, or on-incident communications in accordance with an Incident Communications Plan. Background The 77th Legislature, in an effort to provide for effective emergency radio communications by state agencies, called for an Interagency Radio Work Group (IRWG) to develop a state agency communications network. That group developed a preliminary plan that was accepted by the state IRWG and the Sheriffs'Association of Texas on March 27, 2001. Subsequently, the IRWG determined that the state agency communications network should be expanded to include all public safety agencies in the state. This was accomplished by IRWG's development of the IRCIP of January, 2003. In response to an FCC requirement for establishment of state / regional advisory committees, the Texas Interoperable Communications Coalition (TxICC) and the Texas Statewide Interoperable Communications Plan Executive Committee (SEC) were formally established as advisory committees to TxDPS. The Texas Statewide Interoperability Channel Plan (TSICP), developed by the TxICC and included in this MOU, provides essential guidance for interoperable radio communications using VHF, UHF, 700 MHz, 800 MHz, and mobile satellite radio equipment for interagency coordination, en route travel, or on-incident communications. Understandings TxDPS will: • Manage and maintain proper licenses for the use of the interoperability frequencies identified herein; • Manage and maintain an accurate database of federal and state agencies and local government jurisdictions that have accepted and signed this MOU, and; • Issue updates and revisions to the TSICP contained herein, upon request by the TxICC and the Director of the TxDPS. Jurisdiction will: • Participate in regional communications planning (generally arranged by a regional Council of Governments) that provides for regional radio communications interoperability. 8 Vol. pg. 0 �1 • Manage use of the interoperability frequencies by its employees, ensuring compliance with the TSICP and federal/state / local laws, ordinances, and rules: • Use the interoperability frequencies authorized hereby for their intended purpose of coordination between emergency response agencies and resources. Such coordination may occur during interagency operations, en route travel, or at the scene of an incident. • Use the interoperability frequencies for operational and en route communications in accordance with local and regional policies and procedures. , • Use the interoperability frequencies for on-incident communications in accordance with the Incident Communications Plan established by the on-scene Incident Commander. • Prioritize use of the interoperability frequencies: 1. Emergency or urgent operation involving imminent danger to life or property; 2. Disaster or extreme emergency operation requiring extensive interoperability and inter- agency communications; 3. Special event, generally of a pre-planned nature; 4. Joint training exercises, and 5. Inter-agency and en route communications. • Implement radio communications procedures consistent with the National Incident Management System (NIMS) and Incident Command System (ICS) including: o Use "plain language"without 10-codes or agency-specific codes/jargon; o Use the calling protocol: "Agency-Unit #, this is Agency-Unit #", rather than "Unit # to Unit#". Examples: "Bryan EMS 1605, this is Tyler Fire 2102"or "Incident Command, this is DPS 505" • Ensure that mobile, portable, and temporary base radios intended for use by agency leadership (officers) are configured with the appropriate in-band interoperability frequencies as found in the TSICP. This means that, as a minimum, the interoperable frequencies would be added to the day-to-day frequencies used by that entity. • Ensure that interoperability calling channels are monitored at the Incident Command Post on major incidents requiring significant aid from agencies beyond routine local interoperability. Monitoring shall include one or more of the following: N;;llAICEILLING CHANNEL NAME w ., VCALLIO Analog VHF Calling Channel UCALL40 Analog UHF Calling Channel 7CALL50 Digital P25 700 MHz Calling Channel 8CALL90 Analog National Calling Channel 9 Vol. pg _6 , I Incident Command Post monitoring may be implemented using cross-band repeaters, communications operator console patching, or VHF/UHF/700/800 MHz fixed or mobile gateway. It is suggested that the band-relevant interoperable call channel listed above be included in the 'home zone' used for day-to-day operations. This will enable radio users to easily turn to the interoperable channel on their mobile or portable radio when needed. The parties mutually agree: • Jurisdiction and TxDPS agree that their mutual interests will be furthered by continued coordination between the jurisdiction and the Office of the Texas Statewide Interoperability Coordinator(SWIC). • Jurisdiction and TxDPS agree that this Memorandum of Understanding may be cancelled at any time, by written notice to the other party, or by subsequent agreements. • Only one MOU per Jurisdiction or Governing Body is required to cover the departments and/or sub-agencies of each jurisdiction, as long as each department or sub-agency is listed on an accompanying attachment. The attached TSICP (Original Issue March 25, 2005) is incorporated into this MOU in its entirety. The TSICP may be revised by TSICP Strategic Advisory Group (SAG) and TxDPS as needed, and revisions will be provided to Jurisdictions by TxDPS. Should Jurisdiction elect to withdraw from this MOU because of TSICP revisions, notice shall be given by mail to: Texas Department of Public Safety Public Safety Communications Service 5805 N. Lamar Boulevard Austin, TX 78752 10 Vol. P9 �°— I Agreement /� / This Memorandum of Understanding was agreed to ''day of DIA- n I L , 701 Please complete, sign,scan, and then email THIS PAGE ONLY as attached file to txswicedps.texas.qov. WHO SHOULD EXECUTE THIS AGREEMENT: Each jurisdiction must individually sign this agreement. • An authorized representative of a City may sign for all public safety agencies in that city. • A County may sign for volunteer fire departments (VFD) if the VFD is recognized in the county emergency management plan;however, • A County CANNOT sign for all cities or other public safety agencies in the county that are not a part of county government since they are separate legal entities. • A Council of Governments (COG) CANNOT sign for all jurisdictions within the COG. Compliance with this TSICP and the SC/P are required to receive grant funds for communications equipment. Agencies and programmers should verify the latest version of these documents are being referenced; they can be found at https://www.dps.texas.qov/LawEnforcementSupport/communications/interop/index.htm FOR JURISDICTION Jurisdiction Name: Bra • Cou Authorized Signature: 7idi.�(q Print Name: 44 a ane Peters Title: County Judge Jurisdiction Address: 300 E.26th Street f] nn,, Bryan,TX 77803 // Phone: L"l1-1)5iP1 - 11102 e-mail: c\ pctVs@ toraoscourtfijil V Indicate the NUMBER of mobile, portable, temporary base, and/or mobile relay radios to be operated under TxDPS licenses or MSAT Authorization. For Federal Entity Interop and 700 Air-to-Ground channels, please mark the appropriate box with a checkmark or"X" if these channels are programmed or if programming is planned for the future. 'ltrx<rxy :a +*`e Temporary} f tl "�*. i r5700 Atter tot Mobile Portable Base Enttty�interop 4`Ground t r . a fir+ CNantfelM4 _ C.han els.. a 150 MHz N/A 450 MHz N/A 700 MHz 168 226 N/A 800 MHz NPSPAC 168 226 N/A N/A Mobile Satellite N/A N/A (MSAT) (This information is required by TxDPS as a condition of its licenses from the FCC.) TEXAS DEPARTMENT OF PUBLIC SAFETY AUTHORIZED SIGNATURE Signature: Todd M. Early, Director Public Safety Communications Service Texas DPS Law Enforcement Support Division, 5805 N. Lamar Boulevard, Austin,TX 78752 11 • Phone: (512)424-2121 Fax: (512)424-2899 Todd.Early@dps.texas.gov Background Note to Users of the Texas Statewide Interoperability Channel Plan Nationwide, public safety communications is in a period of great change driven by FCC regulatory changes, new technology, and federal grant funding requirements. Specifically: • The Texas Interoperable Communications Coalition (TxICC) anticipates that all federal grants will soon require that grant funds be spent only for P25-compliant digital-capable equipment and advises all jurisdictions to purchase P25-compliant equipment. • Hurricane Katrina re-emphasized the need for common mutual aid/interoperability channels in public safety radios. Also highlighted was the need for all public safety radio users to have common labels for these channels. In response to the U.S. Congress and to U.S. Department of Homeland Security, a national ANSI standard has been established for use in all jurisdictions within the United States. http://www.npstc.orq/down load.jsp?table I d=37&column=217&id=17&file=11042- 2017 CommonChannelNamingDocument.pdf . These names are reflected in this document. • This Channel Plan is consistent with current regulatory requirements, technical standards, and grant guidelines as they are understood at the time of issue. • 12 f Vet 7e,/ Pg. Texas Statewide Interoperability Channel Plan For FCC Designated Public Safety Interoperability Channels 150 MHz-800 MHz INTRODUCTION This Channel Plan describes conditions and guidelines for use of state-licensed interoperability or mutual-aid radio channels by: • Local government jurisdictions and their associated emergency response agencies; • Federal agency offices in Texas and their associated emergency response organizations, and; • Private emergency response organizations licensed or eligible to operate in the Public Safety Pool as defined in the Federal Communication Commission (FCC) Rules, Part 90, (47CFR, subpart B paragraphs 90.15-90.20). For further information on FCC public safety radio pool eligibility for statewide use of interoperability channels within Texas, see http://wireless.fcc.qov/pu blicsafety/pspool.html. License privileges are extended to organizations that have executed an acceptable Memorandum of Understanding (MOU) with the Texas Department of Public Safety (TxDPS). These licenses provide for: • Operation of VHF, UHF, 700 MHz band, and 800 MHz band radio equipment on interoperability or mutual aid channels within the boundaries of Texas; • Operation of mobile, portable, temporary base, temporary repeater and temporary control station radios only. Fixed-base stations, such as dispatch points, PSAP's, etc., must be separately licensed by the jurisdiction, agency, or private emergency response organization, and • Permanently-installed standby repeaters must be licensed separately. By executing an acceptable MOU associated with this Texas Statewide Interoperability Channel Plan (TSICP), public safety entities may operate under existing FCC licenses issued to TxDPS: Channel Band FCC License 150 &450 MHz WQBC290 700MHz Narrowband WPTZ776 '700 MHz Air-to-Ground TBD; 800 MHz NPSPAC WPGV572 800 MHz Mutual Aid WQDW771 ' The 700MHz Air-to-Ground license is not yet official, thus the license information is listed as TBD. However, if an agency is reprogramming radios before the official license is obtained, they can include these channels now, but are not able to use them until the license is officially in place. 13 1VoLj7 / Fg. 4- By signing this MOU, entities agree to only use the interoperability channels for the purposes outlined herein, and are NOT to be used for routine day-to-day dispatch operations. 14 ol. --z--- Pg• G G 4GENERAL CONDITIONS FOR 'USEt0F TEXAS DEPARTMENTOF.PUBLi SAFEjTY*LICENSED INTEROPERABILITY CHANNELS ,` ,,, k . • By executing the MOU associated with this TSICP, signatories agree to abide by the following general conditions: 2.1.Operational • Interoperability calling channels and tactical channels should be programmed into all mobile, portable, and temporary base radios operated by signatory agencies and organizations. At a minimum, the channels should be programmed into all radios that can reasonably be expected to be operated by an agency or organization leadership (officers, incident commanders, etc.). • Use of the interoperability channels shall be limited to their designated purpose of coordination between emergency response agencies, dispatchers, and resources in the field. Such coordination may occur during en route travel, during exercises, or on-incident. • The interoperability channels are not to be used for routine dispatch operations, but may be used by dispatchers for communications with personnel in the field, in accordance with local and regional policies and procedures. The interoperability tactical channels may be used for day-to- day emergency operations in the absence of higher priority events. • Use of the interoperability channels shall be prioritized as follows: 1. Emergency or urgent operation involving imminent danger to life or property; 2. Disaster or extreme emergency operation requiring extensive interoperability and inter- agency communications; 3. Special event, generally of a pre-planned nature; 4. Joint training exercises; 5. Inter-agency and en route communications in accordance with local and regional policies and procedures; and 6. Day-to-day tactical communications on scene. • Use of the interoperability channels for on-incident communications shall be in accordance with an Incident Communications Plan established by the on-scene incident commander. The controlling agency for an incident shall, through its Incident Commander, assign and\or reassign interoperability channels for each operational period as required to support incident operations. 15 Vol. Tq Pg. 6 7 • Radio communications procedures on the interoperability channels must be consistent with the National Incident Management System (NIMS) and Incident Command System (ICS) and shall be implemented, specifically including: o Use "plain or commonly understood language' without 10-codes or agency-specific codes/jargon, and o Use the calling order "Agency-Unit #, this is Agency-Unit #" calling order, rather than "Unit #to Unit#". Example: "Bryan 1605 this is Tyler 2102" or"Incident Command this is DPS 505" • Interoperability channels may be used only for voice traffic with the exception of specifically- identified data-only channels (see Tables 5.1 and 5.2). Paging, alert tones, and SCADA operations are not permitted on interoperability calling or tactical channels. Mobile data operations may be conducted on 700 MHz channels labeled for data in the tables. User- initiated telephone interconnect, e.g., phone patch, is not permitted on the interoperability channels. • All mobile and portable radio equipment should employ a time-out timer set to limit transmission duration to a period of no greater than 120 seconds (2 minutes). • To alleviate confusion, the standard channel names listed in this plan shall be used in all equipment to refer to individual channels. Previously used mutual-aid channel designations (Intercity, VTAC1, etc.), are no longer valid, and shall be removed from equipment in the field. • Radios not capable of displaying alphanumeric channel labels should be placarded to indicate the channel names and their corresponding positions on the radio's channel selector switch. Z.Z.Co-Channel and Adjacent Channel Interference The statewide interoperability channels, Continuous Tone Coded Squelch System (CTCSS) tones, and Network Access Codes (NAC) are designated statewide under this plan and thus co-channel interference by/with other simultaneous incidents is possible. If effective radiated power (ERP) is limited to the minimum level required to maintain reliable communications at each incident, and given adequate geographic separation, coordinated co-channel operations at separate incidents and venues may be conducted successfully. If interference to the interoperability channels from licensed users who are signatory to this plan occurs during an incident, those licensed users should consider their communications to be secondary to emergency interoperability traffic on the interoperability channels. Co-channel and adjacent channel interference issues during an incident or event must be resolved • by the on-scene designated COM-L. TxDPS should immediately be notified of interference to the interoperability channels in order to assist in resolution of the problem. 16 •Vol. Pg. G 2.3.Calling Channels Initial radio contact during travel to or arrival at an emergency incident may be established on an appropriate interoperability calling channel. • Calling channels designated as VCALLIO, UCALL40, 7CALL50, and 8CALL90 are intended to provide for local and itinerant-user communications with local public safety dispatchers. TXCALLID is designated as a mobile-to-mobile Calling Channel. TXCALL2D is designated as a Calling Channel for state and federal aircraft to/from a base station. It also will serve as a backup to VCALLI O for other applications. • Additionally, the calling channels may be used by responding emergency resources seeking to make contact with the Incident Command Post or staging area(s) at a large-scale incident. • If a region (or an adjacent region) has jurisdictions that use VHF equipment, the channel VCALL10 should be continually monitored by appropriate dispatch points within the affected regions. • If a region (or an adjacent region) has jurisdictions that use UHF equipment, the channel UCALL40 should be continually monitored by appropriate dispatch points within the affected regions. • If a region (or an adjacent region) has jurisdictions that use 700 MHz band equipment, the channel 7CALL50 should be continually monitored by appropriate dispatch points within the affected regions. • If a region (or an adjacent region) has jurisdictions that use 800 MHz equipment, the channel 8CALL90 should be continually monitored by appropriate dispatch points within the affected regions. 2.4.CTCSS Coded Squelch for VHF, UHF, and 800 MHz CTCSS shall be used on the interoperability calling and tactical channels to mask interference, in accordance with the figures and dates listed in this plan. The CTCSS tone of 156.7 Hz shall be used for all analog operation on VHF simplex, all UHF, and 800 MHz interoperability channels (including fixed, temporary, mobile, and portable analog transmitters). For VHF repeater CTCSS and channel programming, see Table 4.4. • CTCSS tone programming for VHF, UHF, and 800 MHz must be in compliance with the NIFOG version 1.6.1 and any subsequent revisions by January 2020. • It is recommended that if the capability exists, a monitor button should be programmed to allow channel monitoring in open carrier squelch, per FCC Rules, Part 90. Only the CTCSS tones identified in this channel plan are allowed on the interoperability channels within the state. These tones and codes shall not be changed nor others added by an individual agency, communications vendor, or maintenance service provider. 17 Vol. _ P9 -L7-1-- 2.5.Modulation and Encryption This plan identifies allowable modulation and encryption on calling and tactical channels: • VHF/UHF Analog Modulation at 2.5 kHz is mandatory on all calling and tactical channels to facilitate interoperability with legacy radio equipment in the field. • 800 MHz Calling Channels: Analog Modulation at 4 kHz is mandatory on all calling and tactical channels to facilitate interoperability with legacy radio equipment in the field. • 700 MHz interoperability channels must always use P25 CAl digital conventional Modulation. o The TIA 102 standard is the Project 25 standard. The following list includes but is not all encompassing of proprietary formats that do not meet the TIA 102 P25 standard: NEXEDGE, IDAS, MOTOTRBO, TETRA, EDACS, OPENSKY, ASTRO 3600, and DMR. • For occasional pre-planned events where communications security is an issue, encrypted P25 Phase 1 CAI modes are authorized on tactical channels. Specific encryption algorithms and encryption keys shall be as defined by the event COM-L. 2.6.Temporary Base and Repeater/Mobile Relay Stations Temporary base stations and repeater/mobile relay stations are permitted by the MOU associated with this channel plan,with the following conditions or restrictions: • Temporary base stations and temporary repeater/mobile relays antennas may not exceed 13.3 meters (40 feet) above terrain or structure. • Temporary base stations and temporary repeater/mobile relays that are deployed under this plan may not exceed FCC licensed limitations: Transmitter Power Effective Radiated Power(ERP1 o VHF 50 100 o UHF 100 200 o 700 MHz P25 35 35 o 800 MHz Temp Base 35 35 o 800 MHz Repeater 75 75 • Temporary base stations and repeater/mobile relay stations must incorporate automatic station identification, using the appropriate call sign(s) per FCC Rules, Part 90. • Temporary base and repeater/mobile relay stations shall have a time-out timer limiting transmit duration to no greater than 120 seconds (2 minutes). • Temporary base and repeater/mobile relay stations, when operating in the repeater mode, shall be configured to immediately drop transmit carrier upon cessation of input signal (no "hang 18 [Vol. ,2 7 9 Pg. 7d J time"). Reasonable squelch hang time for weak received signals or signals that have achieved a critical bit error rate(BER) is permitted. • Temporary base stations, repeaters or mobile relays must utilize manual switching or dedicated RF control links, wire line, microwave, fiber, or satellite circuits as a means of primary control. Interoperability channels shall not be enabled, disabled, or muted by any over-the-air signaling device (selective or dual-tone multi-frequency signaling, etc.)as a primary means of control. • Temporary base and repeater/mobile relay stations shall not be left in permanent operation and must be disabled upon conclusion of an incident or exercise. Permanently installed Standby Repeaters, if identified in regional interoperability plans, must be separately licensed. Contact Texas DPS RF/Technical Services at 512-424-7134 for assistance. • End-of-transmission "courtesy tones" or"beeps" are not allowed on any interoperability channel. 2.7.Conditions for Use of VHF and UHF Federal Entity Interoperability Channels 2.7.1. Requirements per the MOU between the State of Texas and the FCC Consistent with Section 4.3.16 of the NTIA Manual, the Parties agree that they shall abide but the following conditions for the use of the Federal Interoperability Channels listed in tables 4.4 and 4.5 for VHF, and tables 5.2 and 5.3 for UHF of this TSICP: 1. These channels are available for use among Federal agencies and between Federal agencies and non-Federal entities with which Federal agencies have a requirement to operate. 2. These channels are available to non-Federal entities to enable joint Federal / non- Federal operations for law enforcement and incident response, subject to the condition that harmful interference will not be caused to Federal stations. 3. These channels are restricted to interoperability communications and are not authorized for routine or administrative uses as defined by the NTIA Manual. 4. Extended operations and congestion may lead to frequency conflicts. Coordination with NTIA (through sponsoring Federal agency) is required to resolve these conflicts. 5. Only narrowband emissions are to be used on the Federal Entity Interoperability Channels 6. This MOU does not authorize the provisioning or use of the frequencies listed in tables 4.4, 4.5, 5.2, and 5.3 in any permanent infrastructure. 7. Default operation should be carrier squelch receive, CTCSS 167.9 transmit. If the user can enable/disable CTCSS without reprogramming the radio, the indicated CTCSS tone also could be programmed for receive, and the user instructed on how and when to enable/disable. Federal g ncy Interoperability channels may NOTbe y�sed for State'to State;! State toalocal 'or,Local to-Local inteifiiperabihty A Federal entity_must bd involved when:;the a channels are used; 2.7.2. Suggestions per the National Interoperability Field Operations Guide (NIFOG) 1. The"VHF Incident Response (IR) Federal Interoperability Channel Plan", the"UHF Incident Response (IR) Federal Interoperability Channel Plan", the "VHF Law 19 Vol. _ 71 Pg. 7/ 1 Enforcement (LE) Federal Interoperability Channel Plan", and the "UHF Law Enforcement (LE) Federal Interoperability Channel Plan" show frequencies available for use by all Federal agencies to satisfy law enforcement and public safety incident response interoperability requirements. These frequencies will be referred to hereinafter as "Federal Interoperability Channels". 2. The Federal Interoperability Channels are available for use among Federal agencies and between Federal agencies and non-federal entities with which Federal agencies have a requirement to operate. 3. The channels are available to non-federal entities to enable joint Federal/non-federal operations for law enforcement and incident response, subject to the condition that harmful interference will not be caused to Federal stations. These channels are restricted to interoperability communications and are not authorized for routine or administrative uses. 4. Extended operations and congestion may lead to frequency conflicts. Coordination with NTIA is required to resolve these conflicts. 5. Only narrowband emissions are to be used on the Federal Interoperability Channels. 6. Equipment used (transmitters and receivers) must meet the standards established in Section 5.3.5.2 of the NTIA Manual: a. T I NE I A 603-B for narrowband analog; b. T I A TSB 102.CAAB-A for narrowband digital 7. A complete listing of conditions for use by Federal users can be found in Section 4.3.16 of the NTIA Manual. 8. Use of these frequencies within 75 miles of the Canadian border and 5 miles of the Mexican border require special coordination and in some cases will not be available for use. Law Enforcement Plans 1. Frequencies 167.0875 MHz (Channel Name: LE A) and 414.0375 MHz(Channel Name: LE B) are designated as National Calling Channels for initial contact and will be identified in the radio as indicated in the Law Enforcement Federal Interoperability Channel Plans. 2. Initial contact communications will be established using narrowband analog FM emission (11 K2F3E). 3. The interoperability channels will be identified in mobile and portable radios as indicated in the Law Enforcement Federal Interoperability Channel Plans with Continuous Tone- Controlled Squelch Systems (CTCSS)frequency 167.9 Hz and/or Network Access Code (NAC) $68F (16794 Incident Response Plans 1. Frequencies 169.5375 MHz(Channel Name: NC 1) (paired with 164.7125 MHz) and 410.2375 MHz(Channel Name: NC 2) (paired with 419.2375 MHz) are designated as the calling channels for initial contact and will be identified in the radio as indicated in the Incident Response Federal Interoperability Channel Plans. 2. Initial contact will be established using narrowband analog FM emission (11 K2F3E). 3. To ensure access by stations from outside the normal area of operation, Continuous Tone-Controlled Squelch Systems (CTCSS)will not be used on the calling channels. 4. The interoperability channels will be identified in mobile and portable radios as indicated in the"VHF Incident Response (IR) Federal Interoperability Channel Plan" and the"UHF Incident Response (IR) Federal Interoperability Channel Plan". • 20 va. 4 Z 1 Pg. 72 r ffRUNKED`RADIOSYSTEMS _ `< ,' 3.1.Statewide Coordinated P25 Radio Unit ID Range Management Plan WHAT: The Statewide Coordinated P25 Radio Unit ID2 Range Management Plan is an effort to coordinate the distribution of unique identifiers for P25 subscriber radios across the state of Texas. P25 IDs are assigned to create service for a subscriber on a P25 network. P25 subscribers come in a variety of forms, including portable handheld radios, mobile radios, consolettes, and console operator positions. The Project 25 Standard defines just over 16 million unit IDs which can be used by any one system. For proper operation, subscriber devices MUST be using a UNIQUE identifier,which functions exactly like a telephone number. The Statewide Coordination Plan pre-allocates the IDs in blocks by COG, which can then be further subdivided as desired. The Statewide Coordinated P25 Radio Unit ID Plan ONLY applies to the coordination of ID Ranges, and does not address, and is not intended to, coordinate, allocate, or otherwise control the activation or allocation of individual Radio IDs. WHY: The purpose of this initiative is to reduce duplication of IDs across the state so that each P25 subscriber and mobile ID has a unique identifier, and such that each user can use the assigned P25 Unit ID no matter where they are operating in the state. The Agencies that have implemented this approach have experienced a number of benefits: • Allows Distributed Governance and Local Control Over ID Ranges —The primary goal of this approach is to achieve both the benefits of centralized coordination, while allowing local and regional controls over range management. • Improved Disaster Response Times—This method greatly simplifies the mechanisms for enabling First Responders to operate on different systems throughout the State, saving precious time during disaster response. • One ID per Radio—System owners only need to track one Radio Unit ID per radio, which makes tracking and managing radios, users, and radio programming profiles ("codeplugs") much easier. • Reduces Duplicate Radio Unit IDs —Time and troubleshooting efforts are greatly reduced for radio system support teams. • Simplifies Management & Allocation— Helps eliminate errors in assigning IDs because they are organized into the Radio Unit ID fleetmap3 structure. • Easier to Connect Systems—For systems that are already coordinated, this approach removes one of the significant obstacles to integrating systems, which is the need to coordinate and reprogram Radio Unit IDs in order to remove duplications. • Improves Recovery of Lost or Stolen radios, Reduces Security Risk—Allows a lost, or stolen device to be disabled or inhibited across multiple networks increasing the likelihood of recovery and without worry of"disabling" an authorized local, radio subscriber unit. 2 The term"ID"is an abbreviation for"Identifier"in P25,a term rarely used and so just"ID"is used here. 3 In this instance,fleetmap refers to P25 Radio Unit ID fleetmaps. 21 Vol" _ 54 Pg. -743 • • Enables quick identification of a Home jurisdiction by ID Range—Entities are able to determine the subscriber's jurisdiction by viewing the leading numbers of the P25 Unit ID because they are allocated by COG/Tribe/Jurisdiction. HOW: Some COGs have begun allocating ID ranges from within their allocated range at the 'million level,' further dividing their range by creating ranges for counties and cities, as desired. COGs that share an allocated 'million level' range with other COGs must first coordinate to determine which COG will have which block of ID ranges within the 'million level' range. Once the COG-level ID range is known, each COG can determine how they prefer to address ID range ownership and range management. To implement the Plan, points of contact at the COG and, in many cases, county level must be identified to manage the allocation of ID ranges. Some regions may have one point of contact to own the range at the COG level and manage all IDs that are assigned to agencies across the COG. In other areas, there may be multiple range owners within the geography range of the COG—at the county, city, and agency levels. The graphic below is only an example to illustrate the concept of ID allocation beginning at the 'million level' range down to the agency level. This illustration uses a shorthand nomenclature; examples are shown at right. County X: 790—792 "7M" =7000000—7999999 -7 COG 1: 790—794 County Y: 793—794 "788"= 7880001—7889999 7M c > COG 2: 780—788 \\\»>lllCity A:715-717 COG 3: 700—779 City B:710—712 County C:700—709 While the concept of dividing and allocating an ID range seems relatively simple, there needs to be strict attention to detail and specific tracking of ID range assignments to ensure successful ID range allocations. There are numerous real world scenarios where ID range assignments were not carefully managed and extensive problems arose, from both a financial perspective and the level of effort to repair the problems. To prevent this from happening in other areas, tools are being developed to assist entities in allocating and managing ID ranges and to determine the appropriate point of contact to obtain a range of IDs. These tools will be made available at: www.dps.texas.qov/LawEnforcementSupport/communications/interop/ WHEN: The State has not established a deadline for migration to coordinated ID range management. For existing radios using uncoordinated IDs, the change requires radio reprogramming. Because it is understood that radios across the state may not be able to be reprogrammed immediately, it is strongly encouraged that entities reprogram radios with new IDs as their radios are programmed for other or additional reasons. 22 VOI. al /44 Pg. 7e As radios are reprogrammed, it is EXTREMELY important that the entity reprogramming the radios obtain the latest version of the TSICP and verify if any necessary channel programming updates must be made to be in compliance with the TSICP. Grant funding is evaluated based upon verification of radio programming compliance with the TSICP, including compliance with the Statewide Coordinated P25 Radio Unit ID Range Management Plan. The table below shows the allocation of Statewide Coordinated P25 Radio Unit IDs at the millions level or"NI" ranges.The M range indicates the leading one or two digits and are allocated as below, as of the publication date of this document. A brief description of each range and an explanation of the acronyms is provided following the table. Table 3.1: Statewide Coordinated P25 Radio Unit IDs —Current Range Allocations Range ; P25 UNIT ID RANGE Abbreviation . Allocation' Low }�HtF > Legacy (OM) 0000001 0999999 uncoordinated 1M 1000000 1999999 HGAC,TxWARN 2M 2000000 2999999 TxWARN, HGAC, BVCOG BVWACS, ETMC, MTA 3M 3000000 3999999 DETCOG, ETCOG, SETRPC 4M 4000000 4999999 Unallocated 5M 5000000 5999999 TxDPS, State,Tribal & Federal Agencies 6M 6000000 6999999 AACOG, CBCCOG 7M 7000000 7gggggg ATCOG, NCTCOG, CONNCT, TEXOMA, FWRRS 8M 8000000 8999999 LRGVDC, LCRA 9M 9000000 9999999 PBRPC, RGCG 1GATRRS, GCRPC, CAPCOG, 0M 10000000 10999999 CTCOG, HOTCOG 11M 11000000 11999999 STDC, MRGDC, GATRRS 12M 12000000 12999999 CVCOG, WTCOG, NORTEX 23 ,/ Vol. _.v2 Z91 Pg. 13M 13000000 13999999 Reserved for system level temporary usage (ISSI) 14M 14000000 14999999 PRPC, SPAG 15M 15000000 15999999 Unallocated 16M 16000000 16077700 Unallocated Range Allocation Descriptions • Legacy "OM"—This is the range used by systems prior to or instead of the unique range allocation approach. These IDs are only 7 digits in length and lead with a "0" or null characters. This range is uncoordinated. • 1M Range—These IDs are used by the Harris County TxWARN system and are allocated to cities and counties in the Harris-Galveston Area Council (HGAC) COG. The range is fully allocated and in active use on TxWARN. • 2M Range—This range is used by the Brazos Valley Council of Governments (BVCOG), the Brazos Valley Wireless Access Communications System (BVWACS), the East Texas Medical Center(ETMC) and the Metropolitan Transit Authority (MTA). Some ranges are in active use on TxWARN. • 3M Range—The 3M IDs are allocated to the East Texas COG (ETCOG), Deep Texas COG (DETCOG) and South East Texas Regional Planning Commission (SETRPC). • 5M Range—Texas DPS manages this range which is allocated to TxDPS, other Texas State Agencies, Tribal Agencies, and Federal Agencies (all). • 6M Range—The 6M Range is allocated to the Alamo Area Council of Governments (AACOG), supporting the greater San Antonio region, and Coastal Bend COG, (CBCOG), supporting a vulnerable part of the Gulf Coast. Part of this allocation geographically overlaps with LCRA range 8M. • 7M Range—The 7M Range is allocated to the North Central region surrounding the Dallas/Fort Worth area, North Central Texas COG (NCTCOG), the Ark-Tex COG (ATCOG)and the Texoma Council of Governments (TEXOMA). Primary ID range and coordination is provided by the CONNCT consortium and the Fort Worth Regional Radio System (FWRRS). • 8M Range—The 8M range is allocated to the LCRA P25 system and the Lower Rio Grande Valley Development Council (LRGVDC). • 9M Range—The Rio Grande Council of Governments (RGCG) and Permian Basin Regional Planning Commission (PBRPC) have split this range into equal parts. • 10M Range—The 10M range begins the 8-digit IDs. The range has been allocated to the Central Texas COG (CTCOG), Heart of Texas COG (HOTCOG), Capital Area COG (CAPCOG), the Greater Austin Travis Regional Radio System (GATRRS), and the Golden Crescent Regional Planning Commission (GCRPC).Two counties, Karnes and Wilson from AACOG have also been allocated to this range. • 11M Range—The 11M range is allocated to the South Texas Development Council (STDC) and the Middle Rio Grande Development Council (MRGDC)with county by county allocations. • 12M Range—Concho Valley COG (CVCOG), Nortex Regional Planning Commission (NORTEX) and West Central Texas COG (WCTCOG) 24 H 11 1 Va. 7</ Pg, O • 13M Range— For temporary system use, including ISSI roaming. • 14NI Range—The 14M range is allocated to the northern parts of the state, accommodating the Panhandle Regional Planning Commission (PRPC) and the South Plains Association of Governments (SPAG). Note: The 4M, 13M, 15M and 16M ranges remain unallocated. Coordinated P25 ID Allocations by COG iiii 4 'I Y !iISIfl ' s1Irb41 w , a alis ®a Jr: ,;,. --41111MMIllit lertv nil or tak4Est;.. daii7., B.00...aeretaketor. eiry,3.7toatsbatitovirt, 1 r_b -,../- - -intativar gar ® it Notes &Assumptions The following notes and assumptions are provided to explain the source and status of the Current Range table presented below. • Process Applies to ID Range Allocations—This process has been developed to coordinate the assignment of the ID Ranges, rather than the activation of IDs into a device for operation on P25 Network(s). o Many system owners provide and support both functions o Only system owners can authorize operation/Unit ID activations • Subject to Change—The range allocations will be updated and further defined by various stakeholder entities. Please contact the Texas SWIC Office for most current view. • Levels of Implementation Varies—Some ranges are fully implemented and support thousands of operating radios, some ranges have not been implemented beyond this allocation document. • Please Submit Corrections&Suggestions—Should you have a need for a range allocation or you have an update to this suggested approach, please contact the Texas SWIC Office. 25 IVol. _a,_2_ Pg. 77 4. VHF 150 MHz Channels —.SPECIFIC GUIDELINES I The VHF channels described in Table 4.2 are licensed for simplex or half-duplex operation as indicated. These may be used in accordance with regional interoperability plans. Table 4.1 includes the recommended "short list" of VHF interoperable channels. All channels may be used in conjunction with a temporary patch or temporary gateway connection, provided that they do not cause interference. None of the interoperability channels may be used for routine dispatch operations. Note the following: • Table 4.1 outlines the recommended short list of VHF channels that all Texas public safety agencies should program into their VHF capable radios. For radios with limited channel capacity, these channels may be the only ones programmed. For larger-capacity radios, it is recommended that these channels be programmed into the first VHF zone in the radio. o With larger channel capacity radios, where possible, it is also recommended that other VHF zones are populated in numerical order, regardless of discipline association. (e.g. VFIRE24, VFIRE25, VFIRE26, VMED28, VMED29, VLAW31, VLAW32, etc.) o Users should also be aware that even though some channels have a discipline associated with the name(LAW, FIRE, MED, etc.),ALL disciplines can still use those channels when specified by the COML or incident commander. • The VHF interoperability channels VCALL10 through TXCALL2D are identified for interoperability use within Texas. The channel VCALL10 is designated by this plan as a multi- discipline, multi-agency public safety interoperability calling channel for all public safety agencies and other signatories to the MOU associated with this channel plan. • The tactical channels, except where designed for use with state and federal aircraft ONLY, are identified by this plan as multi-discipline, multi-agency public safety interoperability tactical channels for all public safety agencies and other signatories to the MOU associated with this channel plan. The tactical channels may be used for day-to-day agency operations, secondary to users at higher priority incidents requiring interoperability. Additionally, these channels can only be used in the manner intended with this plan. Using them for local repeater inputs or outputs is not allowable. • At large incidents, all of the tactical channels including those that are identified by discipline (Law, Fire, and Med) may be assigned by the on-incident commander as needed without regard to discipline. • VFIRE26 is designated for tactical Ground-to-Air/Air-to-Ground communications with State and Federal aircraft ONLY. • VMED28, in addition to being a medical tactical and mutual aid channel, is also designated for Ground-to-Air communications with EMS helicopters and other aircraft that may be assigned to an incident or event. 26 H7229' Pg. 7,12 • • TXCALLID will be used as a calling channel for mobile-to-mobile applications. This will provide a common channel for an interagency/inter-discipline mobile to call another mobile, especially while in travel status. It is recommended for all VHF mobile radios to have this calling channel programmed into them and have the ability to be monitored while in scan mode. • TXCALL2D is designated as a Calling Channel for state and federal aircraft to/from a base station. • Mobile Command Posts (MCPs) should monitor VCALL10 at all times when in Operation. They should have equipment to transmit and receive all VHF interoperable simplex and repeater channels. • National standards for interoperability channel names have been adopted so that all public safety equipment has s a common naming convention. In accordance with APCO/NPSTC 1.104.2-2017, these labels are listed in the Tables below and all participating agencies must use these labels. • Federal agency channels identified in tables 4.4 and 4.5 should only be used per the guidelines listed in pages 18—19 of this document. 27 Vol. �,2 7 V Fig. /X Table 4.1: Recommended Short List of VHF Interoperability Channels for Texas Public Safety Agencies • To enable efficient and effective use of interoperability channels when multiple disciplines and jurisdictions respond to an incident, it is recommended that this short list of channels be the first channels programmed into VHF radios. • For agencies with radios that are limited to 16 channels, these may be the only channels programmed. • For radios with larger channel capacity, it is recommended that these 16 channels be programmed into the first VHF zone, and the channels on the following tables to be programmed in remaining available zones. Label (Channel Name RX ChTX ; Mode # ; /Trus emadio RX Freq Tone1NAC i TX Freq ToAne/N (A, , Use ystTalkgroup). • f.z1 •- 1 ; : ; tf CALL10� 4155:7525'i ,156 77 l355;7525 156 7A3 ) . < CalhhgChannel ; 2 VTAC11 151.1375 156.7 151.1375 156.7 A Generic Public Safety Tactical 3 VAC12s .'164 4525,,t 15817 i 154.4525y156 7 ),. A Genenc Public Safety Tadttcaf 2 • ... 1 ,.. 3 4 VTAC13 158.7375 156.7 158.7375 156.7 A Generic Public Safety Tactical ..5 r• 1s, VTAC14 z '.159 4725 w15fi 7 '.,159A725 X156 7 g.; A Ge ertc Public Safety.Tactical ,m � +�. �:', tr; 6 VFIRE21 154.2800 156.7 154.2800 156.7 A Fire Tactical ))).--444,r„) ,,,f'LGs x.* t�511P-k,"" ✓ .a ry -7 VFIRE22 .:;154 2650 156 7 s P.1542650' 156 7n A < Fire Tactical � tr; s+. , , .arts .", ' . .. ... ,., . i"+; _ �. ,,.2.aE , -v . , s'-:' 'S's 8 VFIRE23 154.2950 156.7 154.2950 156.7 A Fire Tactical )iiia a ' x ' 7 - '` Fire Tactical and , VFIRE264t; 154i3025a �- `156 7 '' 154 30251 t 156 7 A Atr to Ground with State& r� 10 VMED28 155.3400 156.7 155.3400 156.7 A Medical Tactical&'ir-to-Ground with Medical Aircraft 11 VMED29,k155 3475" s 156 7 155 3475: 156 7, A f Medical Tactical r „ 22, ,.. . -.3.�. ., z.isatvU.,.[z+ ,;•.c....n.:} 12 VLAW31 155.4750 156.7 155.4750 I 156.7 A Law Enforcement Tactical i 1113' t° >VL'AW32,`i'7:155.4825 r 156 7 155 4825 156 7 ` A ; -.," Law Enforce nent7Tacticat�```;e,, �.+a .. . 14 TXCALL1D 154.950 156.7 154.950 156.7 A Generic Mobile Calling Channel t ' 15 'S` x Flt ht followin andtAtr to-Ground b X16 4 X6ALLZD X156 370 156f7 `155 370,• x 156 7'*e, , ` with State/FeBeral Aircraff ONLY' 16 VTAC36 151.1375 156.7 159.4725 136.5 A Generic Public Safety Repeater(Preferred 1 VHF) Vol. ,2T' Pg. eV) Table 4.2: Complete list of VHF 150 MHz Simplex Interoperability Channels (12.5 kHz) Emission Designator 11K2F3E - alb '" }�x v xMobile and-Portable'Conflguratlon* 3 e( . i :SEr ' v ..�?'_ =a Label • Receive � Transmit8tatlon Class CTCSS RX/TX • Use I y «' VCALL10 155 7525 .155 7525 ',.�.FBT/MO '" , ,,156 7!156 7 '* Gaiting Chanel ,. „r,, VTAC11 151.1375 151.1375 FBT/MO 156.7/156.7 Tactical Channel VTAC12?; 154 4525' .-411114'742 ` 4 .156 7/1156 71` t'.. .tv./p1t111A11/.1-TactiCalfChantie144-4,4 VTAC13 158,7375 158.7375 FBT!MO 156.7/156.7 Tactical Channel r VTAC74 159 4725 159 4725, ,4 rFBTr!MO .156 7/156 7Pr- o- 2' Tactical Channel VTAC174 161.8500 157.2500 FBT/MO 156.7/156.7 Tactical Channel VTA017D5 e,,.,1618500, ;161.8500 ,`3,,FBT/MO tit,156714567'" .:4,?*1031) TTacticalChannel c ,. VFIRE21 154.2800 154.2800 FBT/MO 156.7/156.7 Tactical Channel "' VFIRE22�, 2650 ,-1/1542650 _) FBT/MO 156.7/156 7,�m y, �" TacticaI Channel 4 VFIRE23 154.2950 154.2950 FBT/MO 156.7/156.7 Tactical Channel F1tVFIRE24 `ry�1,�54 2725, X54 2725 ...'44.44, FBT/MO�4 i 1156 7/156 7 �`... t„ f, `t:,4 Tactical Cha net M1 �N .� 4 y VFIRE25 154.2875 154.2875 FBT/MO 156.7!156.7 Tactical Channel .x=- �. A :l i.' �« t YI Y #UFt,IRE26 %. ,-;,.1.154'.5025v: ,164 3025 � - FBT/M0 s r 156 71 158 7r (for Alr'ao Ground with state/federal lvrcraft VMED28 155.3400 155.3400 FBT/MO 156.7/156.7 Tactical Channel (and for Air-to-Ground use) r.V --r' c o. u .n:)xt t �. �.., y s w m p v ha n z 4r a @ ,VMED29 155 3475 ;155 3475 T FBT/MO a a 156 7!156 7 �:� SII Tactical Channel � VLAW31 155.4750 155.4750 FBT/MO 156.7/156.7 Tactical Channel rC;VLFlW32 ` 155r4825 1554825 FBTlMO ;, 1567/1567g)w �"f „Tactical Channel''. TXCALL1 D 154.9500 154.9500 FBT/MO 156.7/156.7 Mobile-to-Mobile Calling Channel Primary Flight following betweeri,,,State-4nd TXCALL2D 155 3700 ,5155 3700 FBT/MO c 156 7/156 7 : Federal;'aircraft.Secondary Gro ir-to und for: M 1;L.,...a1?5J „+s., 4 Allowable use for VTAC17 and VTAC170:Base stations:50 watts max,antenna HAAT 400 feet max.Mobile stations:20 watts max, antenna HAAT 15 feet max.These channels are for tactical use and may not be operated on board aircraft in flight.These channels use narrowband FM and are available only in certain inland areas at least 100 miles from a major waterway.These channels use the same frequencies as VHF Marine channel 25,which uses wideband FM.Use only in authorized counties listed below.In these authorized areas, interoperability communications have priority over grandfathered public coast and public safety licensees. VTAC17 and VTACI7D may ONLY be used in the following counties:Andrews Armstrong Bailey Borden Brewster Briscoe Callahan Carson Castro Childress Cochran Coke Collingsworth Concho Cottle Crane Crockett Crosby Culberson Dallam Dawson Deaf Dickens Donley Ector Edwards El Paso Fisher Floyd Gaines Garza Glasscock Gray Hale Hall Hansford Hartley Haskell Hockley Howard Hudspeth Hutchinson bion Jeff Davis Jones Kent Kimble King Kinney Knox Lamb Lipscomb Loving Lubbock Lynn Martin McCulloch Menard Midland Mitchell Moore Motley Nolan Ochiltree Oldham Parmer Pecos Potter Presidio Randall Reagan Reeves Roberts Runnels Schleicher Scurry Sherman Sterling Stonewall Sutton Swisher Taylor Terrell Terry Tom Green Upton Val Verde Ward Wheeler Winkler Yoakum(extracted from the National Interoperability Field Operations Guide https://ww.v.dhs.gov/national-interoperability-field-operations-quide) 29 vol. a-t 7$ Pg. c Table 4.3: VHF 150 MHz Repeater Pair Interoperability Channel Configuration (12.5 kHz)(6)(71 Emission Designator 11K2F3E When assigning repeater channels, be aware that the VTAC33-38 repeater pairs are made up of various combinations of the simplex channels VTAC11, VTAC12, VTAC13 and VTAC14.Attention must be given to avoid assigning overlapping repeater channels and those simplex channels on the same incident or nearby incident. CTCSS tone programming for VHF frequencies must be in compliance with the NIFOG version 1.6.1 and any subsequent revisions by January 2020. Label 'zRecerve Transmits Station Class CTCSS RX RX Use ..-s ,aTv'3M�.S . -La.. g : .rn. _ ..� ,; ,k '1 $s. s . s o R 3 r i •yes ytf t� r>i a Y*'^ 2 '-NOTE Th '71'N audibleaoneof the following'arI dd3erent from simplex programming! y ; Xr.. ... -, .._ u -_ d^-�. 1 ,, ... :r _ N & Mobile and Portable Configuration N m " > VTAC33� t.,::r }159:47251:4(1:9151‘13754, FBT%MO +`1567/1365 , Tactical Repeaters f« {n`; _. 41 ._. _: .. . .,. Secondaryl"',' ,.. VTAC34 158.7375 154.4525 FBT1 MO 156.7/136.5 Tactical Repeater Secondary 2 VC35 i =159 4725 4 '. -FBT!MO 'yi«156 71136 5 y TAp` �, TacticallRepeater rx �,: ,;parr v "`158:~ 7375 .;.a5=-±,5'5'.'":�.. t . 1'w 8 Tactical Repeater =VTAC36 151.1375 159:4725 'FBT/MO 156.7/136 5iPreferred 1I; ise . Tactical Re eater gAt,15a Ati37 aiO ,x5446254-0 . 1587375;* , tFBT/, Ow X1567/1365 s Preferred 2•.e,;as'Cjet . ,,r ,. VTAC38 158.7375 159.4725 FBT/MO 156.7/136.5 Tactical Repeater Preferred 3 VTAC33 151.1375 159.4725 FB2T 136.5/156.7 Tactical Repeater Secondary 1 'f VTAC3431 r 1 154°4525" �' 158.7375' "�"FB2T� 't 4 136.5!156 7 �`,tk ,f Tactical Repeater , ;Secondary' 2 „ VTAC35 158.7375 159.4725 FB2T 136.5/156.7 Tactical Repeater Secondary 3 sTactical Repeater ` °.VTAC36 n159.4725 151:1375 FB2T 136.51156.7 . {;Preferred'.1 VTAC37 158.7375 154.4525 FB2T 136.5/156.7 Tactical Repeater Preferred 2 '2201514725'; 158 7375 ? P82T 136:5/156 7 r£ Tactical Repeater rw N :a .. �.�.:,_. .,.�.�, .:Preferred,3,, . �.,.,. . 6 VTAC33-38 recommended for deployable tactical repeater use only(FCC Station Class FB2T).VTAC36-38 are preferred; VTAC33-35 should be used only when necessary due to interference. In an emergency,additional Department of Defense VHF Repeater Channels(below 150.8 MHz)can be made available through coordination with the Communications Coordination Group(CCG). Please contact the CCG through your local Disaster District Committee. Alternate contact information is: ccq(a'dps.texas.gov and 512-424-2755. ,VTAC36•repeater pair is the prefefred repeatef configuration forrusage in Texas; 30 vo. )- 7e-71 Pg. P2 1 NEW! Table 4.4: Federal Agency VHF Incident Response Intero.erabilit Channels en, a • R% ' , m' .�TX. • Mode �. . # : Label •RX Freq Tone/NAC TX Fre°q Tone/NAC (A,D,M) Use NC 1- 4,4 9 5375 s,yfl CSQ `� 164:71251? •16719%.1.2;,-. /.* zue. 2 IR 1 170.0125 CSQ 165.2500 167.9 A Incident Command - r t < F . <R" re 3xr 1'+> r� n x'ka r w .;Qs u e 31' IR-2 v ;.170:4125Y CSQ s,.1659625.";. 167 9 A Medical Evacuation;Control 4 IR 3 170.6875 CSQ 166.5750 167.9 A Logistics Control • 5, •..„ IR 4 173 0375 '0„CSQ w 167 3250 : 167 9 ' A Interagency Convoy 1 a,s.. .max .., .,. r3 .bxt..in, _„v 6 IR 5 169.5375 CSQ 169.5375 167.9 A Incident Calling-Direct for NC1 7 IR 6 �t %17010125 ' CSQ 170 0125 167 9 };: r A s Incident Command- Direct::9 ��4Yi>� ,_s . .c.>s?��ev.`,�;*;, �.�.tr `y�"2y3F'�.... a�; , aks"`rr`s�.".�, "..... . .�... • €'_.. ,., .. .r ,�`p'<for,R 1!,.c: rt'�.'�,°d!1 8 IR 7 170.4125 CSQ 170.4125 167.9 A Medical Evacuation Control -Direct for IR 2 470:6875:-i rs C8 170 6875 Y167 9 x+ A^ :a Logistics'Control Direct for,„ . r,.*f., . w.•IR03 ,.. `s 10 IR 9 173.0375 CSQ 173.0375 167.9 A Interagency Convoy- Direct for IR 4 Default operation should be carrier squelch receive, CTCSS 167.9 transmit. If the user can enable/disable CTCSS without reprogramming the radio, the indicated CTCSS tone also could be programmed for receive, and the user instructed how and when to enable/disable.All channels on this page are NARROWBAND only. NEW! Table 4.5: Federal Agency VHF Law Enforcement Interoperability Channels :Cn • ; h .. RX! �. • Mode :.• I! -+ ti :# Label i 'RX Freq TonefNAC L TX Frog TXTone/NAC (A A •, 'Use xyLE9rTX• ,0• 1^ e 4 ,LEA 167 0875` N'+CSQ - 167 068 75 '� 2 LE 1 167.0875 CSQ 162.0875 167.9 Tx, A Tactical CSQ Rx 3• .- $ r N. �.s 4 , 6 x l 7 h �.'D LE-2 � '16 2500 �__...�o) 2, 16 25 a $68F(16791,3)-.a4::•-•:;;; )".64FD„ l,tSf Tachcal.:. �.. > �P . 167910 � so-' '� - 4 LE 3 167.7500 $68F 162.8375 $68F(167910) D Tactical (167910) EQS;` ,LE 4 ??... x1fi8.112r..5�y r s�(1679io) , �: 163 28715 ,$68 ,(167910),:. .. D4:�s,�* .s_�. _. Tact cal - `? '. 6 LE 5 168.4625 $68F (167910) 163.4250 $68F(167910) D Tactical Ir0 7tlYks E 6 r, IA6742500 679,10) -1 v 167 25 , $68F(167910) D Tactical D rectf r LE2r+2r 8 LE 7 167.7500 $68F 167.7500 $68F(167910) D Tactical-Direct for LE3 (167910) 1681125 t'c 168 X1125 �.$68F,(46791o)t �"D;Y, t 1TacticaLr,Dlrect for LE4 x �' 10 LE 9 168.4625 $68F 168.4625 $68F(167910) D Tactical-Direct for LE5 (167910) CTCSS on receive only if user selectable; else CSQ. See "Conditions for Use of Federal Entity Interoperability Channels" on pages 18- 19 of this document.All channels on this page are NARROWBAND only. 31 Vol. 7 / Pg. I'3 1 5. UHF 450 MHz Channels - SPECIFIC GUIDELINES fl 1 The eight UHF channels described in Table 5.1 may be used in accordance with regional interoperability plans. However, users should recognize that in-coming resources from out-of- region may not yet be equipped with these channels. All channels may be used in conjunction with a temporary patch or temporary gateway connection provided they do not cause interference. None of the interoperability channels may be used for routine dispatch operations. For UHF interoperability, the four repeater channels (with direct) described in Table 5.1 below will be used. Note the following: • • The UHF interoperability channels UCALL40 through UTAC43 are identified for interoperability use within Texas. The channel UCALL40 is designated by this plan as a multi-discipline, multi-agency public safety interoperability calling channel for all public safety agencies and other signatories to the MOU associated with this channel plan. • The tactical channels UTAC41 through UTAC43 are identified by this plan as multi- discipline, multi-agency public safety interoperability tactical channels for all public safety agencies and other signatories to the MOU associated with this channel plan. The tactical . channels may be used as day-to-day emergency operations channels, secondary to users at higher priority incidents requiring interoperability. Additionally, these channels can only be used in the manner intended with this plan. Using them for local repeater inputs or outputs is not allowable. • At large incidents, all tactical channels may be assigned by the on-incident commander as needed without regard to discipline. • The channels UCALL40 and UCALL40D are designated as multi-discipline, multi-agency public safety interoperability calling channels for all public safety agencies and other signatories to the MOU associated with this channel plan. • The UCALL40 channels are designated for interoperable UHF communications between mobile/portable radios and base stations, temporary base stations and incident commander. • The tactical repeater channels UTAC41 — UTAC43 and talk-around channels UTAC41D- UTAC43D should be assigned by the incident commander. • National standards for interoperability channel names have been adopted so that all public safety equipment has s a common naming convention. In accordance with APCO/NPSTC 1.104.2-2017, these labels are listed in Table 5.1 and all participating agencies must use these labels. • • Federal agency channels identified in tables 5.2 and 5.3 should only be used per the guidelines listed in pages 18— 19 of this document. 33 I. i Table 5.1: UHF 450 MHz Interoperability Channels (12.5 kHz) Emission Designator 11K2F3E CTCSS tone programming for UHF channels must be in compliance with the NIFOG version 1.6.1 and any subsequent revisions by January 2020. t abel rc _ Receive Tra smttw s Station Clause CTCSS;RX(f,X '<'"a 1 '. *' Use r 3 ,r•ri Jfx r. -wR�..._ .4, �,i -t tt _ Mobile Mobile and Portable Configuration UCALL40 453 2125 458:2125 . P62T!MO E 156'7!156 7 x „Calling Channel(yRepeater) �r � .�., .,a_ •svta�..�. - .,.� z.f .,,, ....�. . � ,. 4F, ..�_ t ..& y t ,.:s, .Ad i.,..£ °... . c� . ..�'� UCALL4OD 453.2125 453.2125 FBT/MO 156.7/156.7 Calling Channel(Direct) kUTAC41 k 453 46251p 458.4625x' �FB2T/MO 156 4 156 7 ., Tacti• cal Repeater Channel UTAC41D 453.4625 453.4625 FBT/MO 156.7/156.7 Tactical Repeater(Direct) ,fit „eras s'UTAC42 453 7125 P 458:7125 :FB2T/MO ?; 156 7�q1 156 7 ..., Tactical Repeater Channel > UTAC42D 453.7125 453.7125 FBT/MO 156.7/156.7 Tactical Repeater(Direct) a :r 1 62 P^3f�t 7.2;k 458 8625 .iFB2T!MO 156 7:1156 7 .:h Tachcai'Repeater Channel '•' UTAC43D 453.8625 453.8625 FBT/MO 156.7/156.7 Tactical Repeater(Direct) I Rep eater/Base Configuration • x, `"'* '7x2 , =.2���` ' - ^' ^�+ Mobile'Camrn nd Post_Callm � IICALL40 s: a` `458 2125 i' + 45342125° fi C x FB2T '156 7,?/156 7 anng el8ase-`. UTAC41 458.4625 453.4625 FB2T 156.7/156.7 Incident Temporary Repeater Channels 3 "'„UTAC42 fi�t^ 1 WS 458 7125 453.71251.+' ° F62T r 15fi/156 7 ;'rilnadent Temporary Repeater? r '� �• =Chnnels _... UTAC43 458.8625 453.8625 FB2T 156.7/156.7 Incident Temporary Repeater Channels 34 Vol. 7 pg' C1'4.- NEW! Table 5.2: Federal Agency UHF Incident Response Intero-3erability Channels RX Mode C Ch# Label RX Freq Tone/NAC TX Freq TX Tone/NAC (A,D, Use M) h%.r`t t k$, ,,3='S fi° w< . s I,3.5 , +, .� ,7' w r k NC2 .`r. ,41023775CSQ ;. 4192375 .. 1679..: A . tlnctdentt,calhng 2 IR 10 410.4375 CSQ 419.4375 167.9 A Ad hoc assignment •.�3 iIR!11 s ,410116375 5• iCSQ . 419 6375 ;167 9 + A *V 1+,Ad;hoc ass gnment` ;k 4 IR 12 410.8375 CSQ 419.8375 167.9 A SAR Incident Command y 5 z'IR 13 .4113:1875,".* i r'CSQ i 413 1875 i167 9;1 t `A 'fl " Ad}hoc assign ent"n" N . .. .m..,1. > .. ..:^z •.,. ..V..,_.i�' to,.4-oke 6 IR 14 413.2125 CSQ 413.2125 167.9 A Interagency Convoy rrN , 'n �� r 'tient Calling Direct for • x a�7 xg IR 15 , 410 2376• hCSQ ,y, 410 2376'f• "4/H1'6749'•-•„ sz A ,"NC 2 Callen 3 '' p' 8 IR 16 410.4375 CSQ 410.4375 167.9 A Ad hoc assignment-Direct for IR 10 9 •.,",,274.112.17s 4106375 -x CSQ '; ( 4106375 1679 a A.� Adhoc•assignment� .Dtrect', fie. 10 IR 18 410.8375 CSQ 410,8375 167.9 A SAR Incident Command- Direct for lRl2 Default operation should be carrier squelch receive, CTCSS 167.9 transmit. If the user can enable/disable CTCSS without reprogramming the radio, the indicated CTCSS tone also could be programmed for receive, and the user instructed how and when to enable/disable.All channels on this page are NARROWBAND only. NEW! Table 5.3: Federal Agency UHF Law Enforcement Intero.erabilit Channels Mode V # It Label RX Freq Tone/NAC' TX Freq TX ToneINAC (Arn), Use ,"1 `4r4 EIB^'` t 4140375" 42:2"CSo' " 4140375'':; ^' 16791' ° s A au , ,z`tCalling s, t 2 LE 10 409.9875 CSQ 418.9875 167.9 A Tactical - :�18 a': e 7 D a =.3 LE 11 410;1875; $68F(167910).- 419 1875; $68F(167910) DaTactical .... �. ..... a., rti ,.u.... 4 LE 12 410.6125 $68F(16791o) 419.6125 $68F(1679io) D Tactical '< �„ 4;,14 0625 _$68F(1679io),: 4414 0625 $68Ft(16791o) ;D. x v m`;;aTactical, ,;. s 6 LE 14 414.3125 $68F(167910) 414.3125 $68F(1679io) D Tactical yd n . 1D , i i'^Tactical y.... r's7 "L•515',., $68F(187910) 414 3375'= $68F;(167910) • ..... _s rw .,_ .,,r_., r:a __ :u�Y.3�,, a , 8 LE 16 409.9875 $68F(167910) 409.9875 $68F(167910) D Tactical-Direct for LE 10 Analog 4 D 1875 $68F(16791o)ii M.1106187521 $68F(16791o) D '; Tactical Direct forLE 11 10 LE 18 410.6125 $68F(167910) 410.6125 $68F(167910) D Tactical-Direct for LE 12 CTCSS on receive only if user selectable; else CSQ. See "Conditions for Use of Federal Entity Interoperability Channels" on pages 18- 19 of this document.All channels on this page are NARROWBAND only. 35 Ver# ��� - Pg. 84 %TIDO z Channels `SPECIFIGGUIDELINEr. ' . Au'::E . _ _. � —..� e..✓... -..:�art ..��v..�t- a For 700 MHz interoperability, the 32 repeater channels, with their associated 32 direct channels, are described in Table 6.1 below. Table 6.1 includes the corresponding Tactical Repeater Configuration. Table 6.1 includes the recommended "short list"of 700 MHz channels. Note the following: • 700 MHz interoperability channels are identified by the FCC for interoperability use within Texas. All fixed 700 MHz interoperable channel locations must be reviewed by the Office of the Texas SWIC prior to implantation. Some of these interoperable channels may already be licensed by multiple agencies for interoperability use throughout the state. • All 700 MHz interoperability channels are to be used as multi-discipline, multi-agency public safety interoperability calling channels for all public safety agencies and other signatories to the MOU associated with this channel plan. These channels are designated for interoperable 700 MHz communications between mobile/portable radios and base stations, temporary base stations, and on-incident incident commander. • Table 6.1 outlines the recommended short list of 700 MHz channels that all Texas public safety agencies should program in their 700 MHz capable radios. For radios with limited channel capacity, these channels may be the only ones programmed. For larger-capacity radios, it is recommended that these channels be programmed into the first 700MHz zone in the radio. o Where possible, it is also recommended that additional 700MHz zones are populated in numerical order, with Direct channels following their associated repeater channel, regardless of discipline association. (E.g. 7LAW620,7FIRE63, 7FIRE63D, 7FIRE64, 7FIRE64D, 7MED65, 7MED65D) • Numerical order programming should continue through additional zones as local agencies are able and interested in programming all 700 MHz channels in their radios. o Users should also be aware that even though some channels have a discipline associated with the name (LAW, FIRE, MED, etc.), ALL disciplines can still use that channel when specified by the COML or incident commander. • The tactical repeater channels and direct channels identified in Table 6.2 should be assigned on-incident by the incident commander. • 700 MHz channels with a "+" indicated in the "Use" column should not be used within 70 miles of the US I Mexico border. • National standards for interoperability channel names have been adopted so that all public safety equipment has s a common naming convention. In accordance with APCO/NPSTC 1.104.2-2017, these labels are listed in the Tables below and all participating agencies must use these labels. 36 [V___C_4_ • 2.79_ pp 2 Table 6.1: Recommended SHORT List 700 MHz Interoperability Channels for Texas Public Safety Agencies To enable efficient use of channels when multiple disciplines and jurisdictions respond to an incident, it is recommended that this short list of channels be the first channels programmed into 700 MHz radios. For agencies with radios that are limited to 16 channels, these may be the only channels programmed. For radios with larger channel capacity, it is recommended that these 16 channels be programmed into the first 700 MHz zone, and the channels on the following tables to be programmed in remaining available zones. R .. a• - nr .'1. orbileaitdPo •bl�:Cottftgu��fton.,p. .. ,.,, ,>z,�.:,..- A'§ xis NO3 ppc-, LabelReceive Transmit Station P25 NAC <� r _ £Class � HexlDec r � Use z Temporary Calling Channel �7CALL50, w� 789 24375e79924375 s FB2T $293/659 a z7,r. `� "s ` ki . ... `:Re eater•' ; w 7CALL50D 769.24375 769.24375 FBT/MO $293/659 Calling Channel(Direct) .u7TAC51 r _.irc 76914375 iyx799r1�4375' FB2T , „$293/659 p Temorary_Tactical Repeater 7TAC51 D 769.14375 769.14375 FBT/MO $293/659 Tactical Channel(Direct) t 7TAC52 +769 64375 * 799 64375 .sFB2T $293/659 4"TemporaryTactical Repeater -“t="4 `� ;!'*;I Yr r� x v s . � @ � „3:a . .s , `` ,t ... !s G"�.. , ti L_y>� 7TAC52D 769.64375 769.64375 FBT/MO $293/659 Tactical Channel(Direct) '7TAC53,°i�.' < 770 4375 800A4375 FB2T $293/659 Temporary:Tactical Repeater s •v .,.�( .';o .:, .4 ti:moi. 's.�,.a.33 x m�+. 'ti •Nr. .;ii , .,, .. ..n ., ,n r .w. ., , Lt.; 7TAC53D 770.14375 770.14375 FBT/MO $293/659 Tactical Channel(Direct) r,-7TAC54 ," 770.643754 h $ 800.64375, .,,,�`FB2T $293/659 emporaryyTactical Repeater 7TAC54D 770.64375 770.64375 FBT/MO $293/659 Tactical Channel(Direct) sx,) 7TAC55 x ,, 76974375 • 79974375 ;s7 FB2T $293/659 +:H TemporaryTactical Repeater 7TAC55D 769.74375 769.74375 FBT/MO $293/659 Tactical Channel(Direct) N- t £ "4'L Y ax x ^3 at i "Th-W: Ni. , .€ .x;•E.. u:lS i, 71-:$ 4 „ :.: "'-7TAC56 'R 77024375 800 24375 • FB2T $293/659 t;:' Temporary Tactical Repeater 7TAC56D 770.24375 770.24375 FBT/MO $293/659 Tactical Channel(Direct) 91MYj x ,F ': °xi 7 ..�' "». .wrik e x "- y r, ..'7GTAC57 •t 77099375 800 99375 • F62T ` $293/659 TemporaryTactical Repeater 7GTAC57D 770.99375 770.99375 FBT/MO $293/659 Tactical Channel(Direct) 37 Table 6.2: 700 MHz Interoperability Channels (12.5 kHz) Emission Designator 8K10F1E ' '.ykFs'+"'.�>✓�' d t,am'. "'rte `� .:' a. t o.,. .-. ,- ntvx"n'A.�, a. '`�' "+ 4 � . Moa tie and Portable el,: •ratron ter , i �{ r 3;s a��r i+'r� r .144413.2-5.34' AC v-• Labe ,a4 !.,,,Recetue▪ pr ,TransmrUse ' ct t. rharwHeDec f j aY 3..arc1 i Sc '1, ▪ int is , 4 J' �diS.r""e z r rC r;.g1 ' .v '.<' a " ;{k,.CSI" -a 9CALL50844 v '^ 4}7769 243775a t;. 799.224375._ �FB2 M0 ' s' $ 31659x; >t, s Calling Ch8.7lannel eh 7CALL5OD 769.24375 769.24375 FBI/MO $293/659 Calling Channel(Direct) •t 7TAC5 64 y 1769]4375 %Pp,-i 7991t4375 B2Ta4 M0 + '32931/.659g1 . Tacllc es aterx�ha"cit 7TAC51 D 769.14375 769.14375 FBT/MO $293/659 Tactical Channel(Direct) ki4 't N.'s Ct4r4C t4j. ttai y.1, +T :fit t r : w 9 3.8R.Ic re a PRe e a'�r 8a1 'x Tas7TAC52 k x 769:64375'.4tL� '7799 64375',3' F62T'l MO $2931659,F^' 7,1TtWacttcal Repeater Channel 2roa .. '.�'e';>,;ah. a .i #.tlwev.;`rt lr 7TAC52D 769.64375 769.64375 ST/MO $293/659 Tactical Channel(Direct) 7TAC63 r 770 14375 a`7i 800 44375 x F62T,l MO iw $293!659 ``:4 Tactical Repeater Channel � V?�mr lua t rtU �M ,.�� �J�n}`Z».xv^.w:e_,vi� ...._7i.d -.? ° ear .. .. litrz37c,T ..t..:_..,.LR3r:a.:.. 7TAC53D 770.14375 770.14375 FBT/MO $293/659 Tactical Channel(Direct) t5 - 4er slii ;k an .,a PF WIL‘P•i;?!itit4 ' (*7TAC54-r A ,r}70 64376 a 7 *800,0 664 75,7 F82T1/MO tl 5.1'!29a41,659 is f Tactical Repeater;Channel: to 7TAC54D 770.64375 770.64375 FBT/MO $293/659 Tactical Channel(Direct) ta 7TAC55 : 769 74375,j4* '" 799 74375 y�Fr62T/bMO �,� r$293!659 o Tactical Repeater�Channel Y { T `"w. a<-.a k .,sA.ar ._> ., . x.c.. ». . .t ,,. , $11. -..,. --s MAWAt7_. `sr,$1 rat ,.a .. 7TAC55D 769.74375 769.74375 ST/MO $293/659 Tactical Channel(Direct) -t r Ftp k,^n >„ 23« r s t> Si3. Nkr}SiF :1Y *M311: *. 5 77024375i'te, 800 24375' ICY eFB2T+/:MO ,I* $293/659,1 ; dTacticallRepeaterr Channel _ :_t . t a.. ..•`xc .-. 7TAC56D 770.24375 770.24375 FBT/MO $293/659 Tactical Channel(Direct) z �"i v y t;:/t r`bt b1v ,;14. ;7G 4tt43 4.4..;18770:99375.1,'-fS7' . rfl3.4 x800 9937517.:..'„'T FB2T/�M0 .�4,�� 3 e65 4s ',-t t c.� rjapeat. ia�'c xu" 7GTAC57D 770.99375 770.99375 FBT/MO $293/659 Tactical Channel(Direct) r4 r4,7.0 r p rii . ,,Jv"�' 'yr >�, ^,a ' ? $v 'a.;.W, e,v lt1 .r'sf )-?t1 �r kM r, 4,ti 7MOB59 )1770 89375 r 80089375' FB2T¢I MO > $293/659 1 er Tactical Repeater Channel s,,: zhsv. .r,�'•<s F _..W .: s,7e�n-.... ._�' euu3_ ?t .'sem:; ,s.2 vtx . t..it.h... .`ig,7.cei ..it e., 7MOB59D 770.89375 770.89375 FBT/MO $293/659 Tactical Channel(Direct) zi 7LAW61�.,k ,a k770 393751 k"; 800 39375,- s'FB2T//MO - i,$293,/659x� TacticaltRe eater Chane `t ? 44124 cl c�5.. '.,` .-"";t It +xa n. `Yaa:.Fx ,xa^ ...�.� Cal 's'+..:°. a'c� p 7LAW61 D 770.39375 770.39375 FBT/MO $293/659 Tactical Channel(Direct) 38 vel: _-_ p�Y 'y_ I Table 6.2 (cont.) 700 MHz Interoperability Channels (12.5 kHz) Emission Designator 8K10F1E :,02,G.'M -2: i a S pre J 3'v hIVTobi e a.d Po• able Gonffgurat on "s ire p _;;.4 ; • K1 .? $ Cif i y-fh r:4 �y '�.« .q f,l 4L^�` 5"2-44.4(.4•:1-4F-i< -� i tv ( . «uJ ! r x.. .^. r Fs PP ,- , Station 4P25 NAC r ..l se �'� Label Receive tTransmlt err:. t r. Class ''.: .;. Hex/Dec ' 14 hYs •s ry - T3. = ry ' s 7LAW62 n!G„u„ 5t`770 49375 i,�t 800.49375a FB2T 1 MO ;,x,$293/659 4,� Tachc I Repeater Channel¢ t � :kii7::::2512= ?:- 7LAW62D 770.49375 770.49375 FBT/MO $293/659 Tactical Channel(Direct) r1,,7FIRE63 ¢k 3 "76989375 '+@" °79989375'' 'F82Tl MO' n $293/659 * ` TacticallRepeater Channel" r; 7FIRE63D 769.89375 769.89375 FBT/MO $293/659 Tactical Channel(Direct) tei:Ch r 7FIRE64 w:y' 769'.999375 ¶ X799 99375'.: F62T/iMO t v $293/659 Tactical,RepeaterrChannel± 7FIRE64D 769.99375 769.99375 FBT/MO $293/659 Tactical Channel(Direct) si�7MED6*53 p ". X76939373 +4 99i375 •F82T/AMO ;$2t3/6z9 , •. ,r�tTacticalF2epeater,Chay nel ; 1.7MED65D 769.39375 769.39375 FBT/MO $293/659 Tactical Channel(Direct) r ,7MED66 :�a+•-,F769`4937t5 ii - �nf�6 F62T/MO/" 29359 y,`)+Taetical Repeater Channel ... 7MED66D 769.49375 769.49375 FBT/MO $293/659 Tactical Channel(Direct) 'n7DATA69 • �77074375} t '• (-80074375` �FB2TT/MO $2931659 i 1cractieal Data Repeater Channel') k.'. �. 7DATA69D 770.74375 770.74375 FBT/MO $293/659 Tactical Data Channel(Direct) -M+e- '".`�"..;zxS r Y sx 's•.. 'g• +.moi':' 'S,*. ,s .. ;7 3.m.: r•ti�CAL'1ryL1�,. r 5625( ah£.?603"25625 FXt MO $2931659 Tactical Data Repe titer Channel lz 7CALL7OD 773.25625 773.25625 FBT/MO $293/659 Tactical Data Channel(Direct) CST: ;;us- ems. 'AS 4.. f ax.'.• " 1§ ki' r ; i 7TAC71 ` 477310625.U'�)3 8031'1I0626� M FB2T/ O x $293/659 ti,Tactical Repeater Channel+X l 7TAC71D 773.10625 773.10625 FBT/MO S $2931659 Tactical Channel(Direct) a 7TAC72 '` 773 60625 803 60625 FB2 MO `{$293'/659 x TacUcaal.Repeater Chareinel+ 7TAC72D 773.60625 773.60625 FBT/MO $293/659 Tactical Channel(Direct) { 5(�..su °h L J` x r+p t :n4 i3 f.F KFt YJ L`k Y P i 7 i 7TAC73 ' s 774 10625 'T ,;804 10625: FB2T�v/MO $293!659 Tactical Repeater Channel+ .."<". 7TAC73D 774.10625 774.10625 FBT/MO $293/659 Tactical Channel(Direct) 39 ' Vol. 7'L Pg. 7t9 Table 6.2 (cont.) 700 MHz Interoperability Channels (12.5 kHz) Emission Designator 8K10F1E and PortableContiguration ' } ' E air '4*K: t s; " sx .rF ySbY q� ;I 0 !a r { a 1 xY 'L ' ,S4 "� M4 f 4 g �. Station P25NAC Label Receive Transmit Use � r t � Hexl 774 60625 80460625 i FB2T/MO • $2931659 Tactical Repeater ,xi . .: 7TAC74D 774.60625 774.60625 FBT/MO $2931659 Tactical Channel (Direct) 1/4.17TAC75 x „77 75625 { .803.75625 t rs t' FB2T/MOS $293r//659:t TtiR actica•l Repeater �, 7TAC75D 773.75625 773.75625 FBT/MO $293/659 Tactical Channel(Direct) ret ') xF' ' , ' ° i Tactical Repeater 7TA976 , y3,77425625. 804;25625 F62T!MO $293/(659,} .�. . -.. .�.v�}, . . wxi , . . S� - �, . ,vvi� .�,,. .., ,Channel+ .. 7TAC76D 774.25625 77425625 FBT/MO $293/659 Tactical Channel(Direct) n -c°r r ny f t W• 7GTAC77. ' 77485625 804;856251 FB2T/Mer $2931659 , ,7Tactical Repeater ' • ;t=:Channel- ' 7GTAC77D 774.85625 774.85625 FBT/MO $293/659 Tactical Channel(Direct) 7M0B79 774 50625 w S.r 804 50625 x F82T/MO $2931659 r ,Tactical Repeater 7M0B79D 774.50625 774.50625 FBT/MO 22931659 Tactical Channel(Direct) , B TacticahRepeater `` ` 'k'7LAW81 7.74:00645-7c ' 80400625 i F F2T/MO,O $2939'65'01'12 `� Channel+. 7LAW81D 774.00625 774.00625 FBT/MO $293/659 Tactical Channel(Direct) -< - Tactical Re eater 7LAW82;,.� t . 774 35625 4' , 804 35625 , FB2T/MO (':$2931:659'/A p , Vii= v, v, F ...... _ tet. -rs,T} ,..,..;+ ,_ ",x. -: ,> # Channel+: 7LAW82D 774.35625 774.35625 FBT/MO $293/659 Tactical Channel(Direct) 2 Y"rit i m', /41itc" ire-sfi ;.Tac6cal'Re eater 7FIRE83 4,, * 77330625 'e 803.50625 t ^ F62T/M0 $293/;659 Channel+, 7FIRE83D 773.50625 773.50625 FBT/MO $293/659 Tactical Channel(Direct) Tactical Re eater T/ �, 7FIRE84 `,"T 773 8562S azs 803y85625 t'r FB2MO 229.37,659 .e 1r Channel 7FIRE84D 773.85625 773.85625 FBT/MO $293/659 Tactical Channel(Direct) 40 I Vol: ___al. 7� PQ. l/ Table 6.2 (cont.) 700 MHz Interoperability Channels (12.5 kHz) Emission Designator 8K10F1E •••% '.7 � ,, i _ it1✓ . .. �.. �T+ t ry «`u+d '1+ 4 1 ; n ,.M'obit�g�arit o Percept guratibn Vu xAz 't •.`3i 4"�. r ..vRxf# ` Y^� w :s ^`N rhn -a ;, t{fTyS +< ; Station P25,NAC x Label ; Receive -Transmit Use €_ p Ctass` HeiJDec yrrrr,. , M147MED86 X73 00625 60300625 F 2T/IJIO =$293!659 -'aTactical Repeater Channel+., 7MED86D 773.00625 773.00625 FBT/MO 5293/659 Tactical Channel(Direct) 80 r 7MED87 �' � 773 35625 e. 3 35625 'r F2Tt/MO $293!659 swr'`Tactical Repeater Channel+ x"`'.b he `'.,.rl a'.W` ''l=•r"+ 7MED87D 773.35625 773.35625 FBT/MO $293/659 Tactical Channel(Direct) '�7,DATA89 x'. 774 75625 nfr 4804 75625;1 FB2T/MO $293!659 Tactical Data Repeater Channel „en. .. ror-, _X u3..� ' .,,'.' .';t. z,�.gxs' '�' x , .-�,+x`-a ,. :..,.,.r : �fi,u1;..:> :'.,.. Fii 07 7DATA89D 774.75625 774.75625 FBT/MO $293/659 Tactical Data Channel(Direct) NOTE: Channels with a"+" indicated in the"Use"column should not be used within 70 miles of the US/Mexico Border. The remainder of this page is intentionally blank 41 Vw, ,. .2171 pg. 9� Table 6.3: 700 MHz Interoperability Channels (12.5 kHz) y� 'PrimaEmission Designator 8K10F1E U yr '... ,Ga gChat. - jt m orb Y ni! 'Pi aetic l kpeater(6 fh ( tion Rw ..'' _x.z. .r i W. y s a.il•. �,aY _ .! d .rnuui. ♦. • a .� x- s a •d"'(. ,�.yTM° z y . " x,�` :=rl r e yt, `" 5� Vii§ a , e Station5:41131 !4:4,9;i:'4 } Label k^ Transmit ReceiveH ` Use t x` car ti ',7CALL50 i 769 24375"'"'79924375t FB2T* Y ;$293/t659:4 Temporary Calling Channel Repeater 7TAC51 769.14375 799.14375 FB2T $293/659 Temporary Tactical Repeater ""hv 7TAC524�, t 769 64375t"�r799 64375 „ T$V"F82 }`t / x$293/659' t TemporaryTactical Repeate"r t�rr 7TAC53 770.14375 800.14375 FB2T $293/659 Temporary Tactical Repeater f�,� ., t,t ' 7TAC54 x770 64375, 800 64375 °'`-. F82T $293/659 f T��e....mporaryTactical Repeater t k,. .. _ 7TAC55 769.74375 799.74375 FB2T $293/659 Temporary Tactical Repeater 7TAC56 C 4770.243751 tr 80024375A F62T $293/659 Temporary Tactical Repeater ' nEy 7GTAC57 770,99375 800.99375 FB2T $293/659 Temporary Tactical Repeater 1'17M0659 77089375 480089375 FB2T h T" ` x } x ;$293!659 TemporaryTaetscal Repeater a ..a ...k_.,... .r.n „ 7LAW61 770.39375 800.39375 FB2T $293/659 Temporary Tactical Repeater :.:s -,., z 7LAW62 770 49375 B00 49375;,c, !$293/659 ? T mporaryTactical Repeater s a a_..=G..St^.jix .,* x ` €IP;C ilsf..,...>x. t,� ._.�e"9' °£,....ui+ _... ..., r :.. ; ..+k:” 7FIRE63 769.89375 799.89375 FB2T $293/659 Temporary Tactical Repeater 4 7FIRE64u -..!;77.69.99375,1,g1,799.99375, �.., pt,;.-14., /659,^-- ITemporarylTactical Repeater ? r 7MED65 769.39375 799.39375 FB2T $293/659 Temporary Tactical Repeater e 7MED66a B>769 4937,5 ' 79,9.49375+, FB2T'+'m,a x':$293/659; ; a -Temporary TacticalSRepeater ``" �....'" ':.� ..,.,,.�F a;'. . $..a`: a 7DATA69 770.74375 800.74375 FB2T $293/659 Temporary Tactical Data Repeater k,”x7 x 1$1,: , 7:MN k`,y AY3h T ' V w 4 1 .4 `fm S-eu ,n"Y a is 7CALL70 e-, 773 25625 803 25625 *FB2T x4 wl'A$2931/.659et"r 4Temporary ,ailing Channel 7TAC71 773.10625 803.10625 FB2T $293/659 Temporary Tactical Repeater+ ,7TAC7 ` 773 6062,5 80 60625`+ < FB2T -� s $293/559Fv Temporary Tactical Repeater-.40 , 7TAC73 , 774.10625 804.10625 FB2T $293/659 Temporary Tactical Repeater+ ;47TAG74, ;,' ,774 60625 i 804 60625;r.ter FB2T ° a $293 1659 Temporary Tactical Repeater 42 [Vol. 27 .,___ f _ Table 6.3 (cont.) 700 MHz Interoperability Channels (12.5 kHz) Emission Designator 8K1OF1E Td ernsT".,a o4 ary-rCallmg c at'•anr tnioeltig. ctPric2'af C Rep .ate'.4r C°onfi�ag.uraU"t'io,}}n.a' c ¢ aYa kr rp - r:ra # x r`, % NAC S ;i, Labe1 Transmit $r vUse ` : a • !;!a55 ;Hex/Dec,,,! • ? fid L L 3 3 7TAC75;1/42X773 75625" '803 75625`" °rFB2T c =°;.;:.$293,/.659),J34 TemporaryTactical Repeater+ , r$ 7TAC76 774.25625 804.25625 FB2T $2931 659 Temporary Tactical Repeater+ 37GTACT7 ; 774.85625804.85625 F.B2T 44$293/6593,43 mporary TeTactical Repeater • 7M0879 774.50625 804.50625 FB2T $293/659 Temporary Tactical Repeater 7LAW81 .x 774 00625 804 00625 xQ 4F82T � g ;$293 L659..1, Temporary.Tactical Repeater+ 7LAW82 774.35625 804.35625 FB2T $293/659 Temporary Tactical Repeater+ L. B3 2 “c� .506, 5)i, S s T eMpor r• ical ei- !'. �i=7FIRE834 t' f�773 50625 803 50625 . „��F.B2T 4 -$293!659?^ Temporary Tactical Repeater+ 7FIRE84 773.85625 803.85625 FB2T $293/659 Temporary Tactical Repeater+ Exs 37` na + 7MD66ss x773.006255rr803 0062541e$29$/659 . " TemporaryTacticaRepeater+ & m . . ate..@ t , r, w..T 43. .4eli ra t t3,3Wa t tY 7MED87 773.35625 803.35625 FB2T $293/659 Temporary Tactical Repeater+ 7DATA89 :'- ,774 75625w804 75625 L115293/;6594 Temporary Tactical Data Repeater NOTE: Channels with a"+" indicated in the Use column should not be used within 70 miles of the US/Mexico Border. 43 ,/ Vol, .. )7`t Pg. 9`-/ NEW! Table 6.4: 700 MHz Interoperability Channels (12.5 kHz) Alr to-Ground ..+ S x'iMobrle TX' �. �� 4$ 'ice Y ti '4`� .y ��, , Label+ Mobile RX(MHz) • } 7AG58 ,769 13125�` * 799.13125 's Ar Graund*X, }" 7AG58D 769.13125 769.13125 Air-Ground x SF7A Ot . ,°" 769.63125, * 7 h799 631x5 , X,.., '�1 t ,i+t Aire?ound r'= 8tr-z-x,;.' ! 7AG60D 769.63125 769.63125 Air-Ground "+tiler . Z3 z y 7AG67 ;i 77013125 t , -800':1.S.125 r t AirGrGround r rr 7AG67D 770.13125 770.13125 Air-Ground 7AG68a x",y�,,770 63125tu°+ -4800.63125'. Air-Ground ttsro 7AG68D 770.63125 770.63125 Air-Ground 7AG78 , 77311875 , ' 80311875 .t, AirtGroundt. �rrt.offt. 7AG78D 773.11875 773.11875 Air-Ground 7AG80, f 773 61875;lsi. - 803 61875 .4t T Air-Ground _ tr. ,;, 7AG8OD 773.61875 773.61875 Air-Ground 7AG85 774 11875 ti' 1804,1187$ Qir Ground.4 7AG85D 774.11875 774.11875 Air-Ground 7AG88 774 61875 t r 804 6,1875 Air-Ground? + a+ . : 7AG88D 774.61875 774.61875 Air-Ground Landing Zone *7AG88D is recommended for Landing Zone use. TX NAC:$293 (659 10). RX NAC$F7E (3966 10). These channels are reserved for air-ground communications to be used by low-altitude aircraft and ground based stations: See FCC rule 90.531(7). (i) Airborne use of these channels is limited to aircraft flying at or below 457 meters (1500 feet) above ground level.(ii)Aircraft are limited to 2 watts effective radiated power(ERP) when transmitting while airborne on these channels. (iii)Aircraft may transmit on either the mobile or base transmit side of the channel pair. (iv) States are responsible for the administration of these channels. These are NOT nationwide interoperability channels. 44 7' 8001MHi Gheliai f..;SPEGIFIC GUIDELINESt nn For 800 MHz interoperability,the repeater channels (with direct) described in Table 7.1 below will be used. Table 7.2 includes descriptions for use within the Border Area (rebanding). Note the following: • 800 MHz interoperability channels are identified by the FCC for interoperability use within Texas. Some of these interoperable channels may already be licensed by multiple agencies for interoperability use throughout the state. • The channel 8CALL90 is designated as a multi-discipline, multi-agency public safety interoperability calling channel for all public safety agencies and other signatories to the MOU associated with this channel plan. • The tactical repeater channels 8TAC91 - 8TAC94 and talk-around channels 8TAC91D - 8TAC94D should be assigned on-incident by the incident commander. • National standards for interoperability channel names have been adopted so that all public safety equipment has s a common naming convention. In accordance with APCO/NPSTC 1.104.2-2017, these labels are listed in Tables 7.1 and 7.2 and all participating agencies must use these labels. The remainder of this page is intentionally blank 45 Table 7.1: 800 NPSPAC Interoperability Channels (20 kHz) Emission Designator 16K0F3E CTCSS tone programming for 800 MHz channels must be in compliance with the NIFOG version 1.6.1 and any subsequent revisions by January 2020. J + Sl l P :t.":"'?" 5tiftF;t P r 1:121,41n� W S�2tiOn ' C.TC.>$ ._'7e f , ! .ari'w �-� 11l ^l'h n.: ,t rL1 'FRecerve;� Transmit y`, u.,a y'""" 1 "Jb ' �4 Use v [�1 gV�y�L4 /' WA�pt 4,,,r:si'ig d: CIas, rr • RX�,IeT�X y�'1 k 'r g ,l 7r ve.. x ?0,... :: +•X.,:e• 1 _:' 'etre..s.Ssf ,i:,,r.74i,'412:0, t'`.iaiX.e .. +A" ,., ..le.!4aLi.4 .d+-..z C .4r .,.., 8CALL90 851.0125 806.0125 FB2T/MO 156.7/156.7 Calling Channel(Repeater) Iw hkBCALL90D y86' 1MO $56�/ 6mng Charmi Table 7.2: 800 NPSPAC Interoperability Channels (20 kHz) For Use within Border Area for Rebandinq Emission Designator 16K0F3E CTCSS tone programming for 800 MHz channels must be in compliance with the NIFOG version 1.6.1 and any subsequent revisions by January 2020. 49411, s. :•1:4".4,11-P L#44 3 "garr: ^4 F" A .�y,, e`*1.f S '5" t s 4 i✓f id e0 �2 abet., Rec vi ers •rans It �S.tation4 .1;4ADICSS ,•• ,, a�„' o f NIFOG` b ; 4;17,r a ti s „' Class e,x g r i d na' §n!,:d '.'- .Grn . ,xr r. . ligcua z rn...r e:4! "",i, ';'x?e§rz .. . 8CALL/ICALL 866.0125 821.0125 FB2T/MO 156.7/156.7 Calling Channel(Repeater) 1, 4*8•CALLD h a x'866 0125. x 866 0125.5u't"3+ ^1FBT/MO x7'` X,156M/El 15&7>¢ 'it `�Rcalling Channel Direct);; �,, `". q ICALLD.,,?': `; •tm;. :. r•-.V•;'•'2,01 cti 1� . „� a y; t�«§7 8TAC1 /ITAC1 866.5125 821.5125 FB2T/MO 156.7/156.7 Incident Temporary Repeater Channel Z . ;IT-866.5125N4;;:I-1866 956 7/ 7 156 �: Tactcal Channel(Direct) � 8TAC2/ITAC2 867.0125 822.0125 FB2T/MO 156.7/156.7 Incident Temporary Repeater Channel k8 TAC2D.; :4t'•;18.,67.-.0125A1 867 0125,, FBT/MO.,c4156//156 7'.„ Tactical Channel(Direct). �y 8TAC3/ITAC3 867.5125 822.5125 FB2T/MO 156.7/156.7 Incident Temporary Repeater Channel ;867:513,5's,1,486,7:5125,/ FBT/Mat {156.7/156.7 Tactical Channel(Direct)' • ter` 8TAC4/ITAC4 868.0125 823.0125 FB2T/MO 156.7/156.7 Incident Temporary Repeater Channel 8TAC4Ds/i*"°.R , 868 0125:.< 868.0125.,E p 4FBT/MO , X156 7/156,7 ^ ,Tactical Channel(Direct)" ,r= aCt-: C-a- 4Ar" ,. ` � :,+ Ys w4 ro mp§ati7 b� 1a"..sse -rx til ..4' r °/ 1 - +,F.r^; "I* '�s - x t ,MobileCommand Post Calling Channel f ,c`BCAL1 /ICAL a1821 0125e $ 866 0125 pl FB2T T,,(, 156 7 .a?,. „ ,r a,1,#.1,. ,fig fir, .. ...'�.,+. ,.,,..._`�^ �svi.. f ..: 8TAC1 /ITAC1 821.5125 866.5125 FB2T 156.7 8TAC2/ITAC2' kr822 0125: ,867.0125 FB2T: s4,i. �1' ''�``� '''' `' ` Incident Temporary Repeater Channels 8TAC3/ITAC3 822.5125 867.5125 FB2T 156.7 8TAC4/ITAC4,.823.0125;i,' 868.0125 '' � F82T ' - 156 7 �.;e4(4( '7X naming convention preferred for Texas border region programming. 47 vol. a 7 Pg. 771' f8 Mobile'81401Iite QUISAP Talk°13 rou s;=SPEGIEIG ;GUIDEL-`INES,:i"", Table 8.1 below lists statewide, regional, and national MSAT talkgroups for use by Texas public safety agencies. Texas has two statewide mutual aid talkgroups: TXSMRT and INAGY. TXSMRT is used for communication between Texas public safety agencies and private sector partners, and INAGY is used by government agencies ONLY, The talkgroups designated as SMART/SMRT (Satellite Mutual Aid Radio Talkgroup) are for multi- agency coordination during large-scale events or disasters, potentially involving public safety agencies at the regional and national levels. Each agency should determine which talkgroups are best suited for their agency's needs and purpose. Table 8.1: Mobile Satellite Talkgroups S..%,'"40: x et E2� a ayfplii} a h.�. 4 xf' tiYa nY 3.:,i } J r .. MSAT ' P'rr cr 9 r 's a a " , r , _ v Ta kl grourol Legacy MSAT ,- s/+s 'Talkgroup t1 9 Authorizing ' , a Namezr' - « rw -k '^ sei 41 �ckAgencies Supported, pI15e r Name ,n' (77 Cha) *'. rl o) ' Agency ie' xl as f " 7-F' y'-' (5 char ,,;i:g 'sae's/x ,� _ 'r- ta,��Rad�o , . �,,:�4�r`,a:;k^ � �� � , '�;Lux,.' . �3'""'v'�.v ��z .,.., � :-, T`�r•'e"fz All Texas Public Safety and Point-to-Point 4-digit DN 00 00 DPS Operations Private Sector Partners call feature. No per-minute cost for DN calls DPS1 DPS1 DPS Operations DPS Incident Command/ Calling Channel DPS2 DPS2 DPS Operations DPS DPS Daily Use TFS1 TFSI TFS EOC TFS TFS Daily Use TEEX1 TEEX1 TEEX TTF1,TTF2,Quick Response TEEX-TTF1 Search and Force 8 Water Rescue Calling Channel STRAC1 STRC1 STRAC Comms STRAC and San Antonio Area STRAC Daily Use Calling Public Safety Channel STRAC2 STRC2 STRAC Comms STRAC Regional Regional Medical INAGY INAGY TFS EOC TFS and Texas Public Safety Interagency Coordination Agencies (Texas only) TXSMRT TXSMT DPS Operations All Texas Public Safety and Statewide Channel for Private Sector Partners Public and Private Sector LA Homeland Gulf States Public Safety G-SMART GSMRT Security and Gulf Coast Regional Agencies Mutual Aid Regional/ Emergency National Preparedness _ Contra Costa(CA) Southwest Public Safety SWSMART SWSMT Fire Protection Southwest Regional Agencies Mutual Aid District Seattle Public Critical Infrastructure I-SMART ISMRT Utilities Regional/National Agencies Mutual Aid E-SMART ESMRT KY Dept.of Public Regional/National Agencies EMS Mutual Aid Health F-SMART FSMRT Seattle Fire Dept. Regional/National Agencies Fire Service Mutual Aid 48 IVol. ol. 744 Pg _11____) , J-SMART JSMRT U.S. Dept.of Justice All Gov't and Public Safety Public Safety Mutual Aid Regional/National Agencies Regional L-SMART LSMRT U.S.Marshals All LE Regional/National LE Enforcement Mutual Aid Service Agencies U-SMART Us RT Montgomery Co. All Urban Search and Rescue Urban Search and Rescue (MD)Fire&Rescue Regional/National Agencies Mutual Aid All Health Depts.and Medical NPHST2 NPH KY Dept.for Public Facilities Public Health Mutual Aid Health Regional/National Agencies TG Abbreviated names are for older MSAT radios that have less than 7-character capacity for talkgroup names. Obtaining Access to MSAT Talkgroups To obtain access, please follow the process found at this link. http://www.txdps.state.tx.us/LawEnforcementSupport/communications/interop/ Note: Authorization letters need to be obtained before scheduling on-air programming for the radios. I x; INTEROPERABlLI ffek SSiBQNSY D STEMS SPECIFIC GUID „tai :1 ELINES Cross-band interconnection between radio equipment operating under state-licensed channels is authorized with three conditions: • Cross-band operation is authorized as may be required to interconnect channels identified in this channel plan, and interconnect to other channels that may be required on a particular incident. On incidents, tactical channels and other local channels may be interconnected at the direction of the incident commander. • Cross-band operation should conform to planning requirements, as established in a RICP, typically produced by a regional COG. • Patching to/between interoperability tactical channels and local radio systems is permitted during incidents or events involving interagency personnel, if so directed by the incident commander. This is only allowed through concurrence from the system manager/dispatch center. • 800 MHz NPSPAC (conventional) channels may be cross-banded with other interoperability channels. Caution should be used when performing in-field cross-band connections with VHF/700/800 MHz trunked channels due to potential push-to-talk (PTT) delay. • Supervised gateways, console-initiated patching or cross-band repeating of tactical channels to tactical channels in other bands is permitted under positive control of a trained dispatcher or on- incident Communications Unit Leader (COML). A dispatcher or COML who establishes such a calling channel patch must be capable of disabling the patch in the event of unexpected or unacceptable interference on any of the patched calling channels. 49 va. , 'L Pg- IGU Cross-band interconnections can be implemented in several ways: 9.1 Simple Cross-band Repeater This approach interconnects two radios "back-to-back" such that received signals on either receiver are re-transmitted by the other transmitter. FIGURE 9.1 AUDIO 8 PTT VHF vAgrariros 800 MHz Antenna Antenna iusiIN IN7. l t.t lit {* {TemporarydBase'Statwn;��o §RIu7; OUT OUT !4A, ,Radi0,4 t 'v"_' z-7 -.:,;,,:f-2?.: `# �a6TA.*.. Si.4,, Simple Cross-Band Repeater Operationally, the two channels selected will seem to be one channel, as long as all radio users are within the coverage "footprint" of the cross-band repeater and antennas. Some PTT delay should be expected. In this example, two tactical channels are interconnected to enable tactical communications between resources equipped with differing equipment. 50 Vol. �/2 7$ Pg. /0) 1 , 9.2 Mobile Tactical Interconnect or Radio Interoperability Gateway This approach interconnects several radios "back-to-back" so that received signals on any receiver are re-transmitted by all selected transmitters. Operationally, all channels selected will seem to be one channel, as long as all radio users are within the coverage "footprint" of the antennas being used. Some PTT delay should be expected. In this example, several tactical channels are interconnected to enable tactical communications between resources equipped with differing equipment. Figure 9.2 VFIRE22 AUDIO 8 PTT Antenna • 'gv-41 r' tY ))364':5` Y .ji` I' .e4 .zVHTemporaBase arm` :"' FTemporal:3r; Station Radio • VFIRE22 s h Fixed or Deployable 't i+xt `•.u�. .`i S '+` Gateway x i -i VTAGI2 Antenna tSlia ,Y,'; ':t �. VHFTemporary Base �,j.� ;t--'{';zz� $r aa� sri *'.T6 VTAcl2 s 5 to y t , �Ii ::±.7 v,. .1.1L _. S=!'�..... interconnect/Patch Switch Boz " �, UTAC43icx Antenna aki UHF TemporaryBase S • UTAC43 ✓ . 4 eTAC92 kt Received audio froth Antenna 'any receiver can be broadcast, z-4 on any or all"tr na smitters z- d ': 809 MHziNPSPAC h .� '•'" '' `i *`z t".+ emporai Ba '{.a.se Station".." Radiot:- '4%.-•/4" :-b 8TAC92 "if.r .' i, y• r��3. Ce...J.s Mobile Tactical Interconnect or Radio Interoperability Gateway 51 H2 7Y Pg. / z 1 9.3 Dispatch Console Patching Console patching utilizes dispatch point base radios and the patching capability of a common console system to accomplish the same interconnections described above. However, in the case of console patching, all radio users must be within the coverage "footprint" of the base station antenna at the dispatch point. Some PTT delay should be expected. Operationally, all channels patched by the dispatcher will seem to be one channel. Figure 9.3 VFIRE22 AUDIO&PTT Antenna C y = 'i l 3f..,.. � F4: damAS,e ,q� 4 e; i' t TrrysSation" VHF empoaa Radioli * yy 3 Y f Y.j f 1 4 SX9"` A {" t Y`F�' . ,,, VFIRE22.: ,5, g ✓ Natc 'l mV Patch Cont o.4. g a' :f+ ,tri 7a# n , irk fx,r 'f VTAC12tq'ea <.Ft xa 4. Antenna rye a,„y ># X xr , q ._v.c 1ehlt 3 o A x'tr xJ r y°" Y VHF,rTemporary Base Station t: t , g , as S41VTAC12 c?*`.t : # i `.✓' `.. &0u uTAC43xS:p:4 '�Z 3.c T"'1 nx Antenna '� ;✓ r ii 44 ' 4MA S# �k t ,i < xnaUHF Temporary Base Station ' h ,`Radio � n`:UTAC43' t{1a "t n " f ' yjiv4ck : M s. Received abdio 9TAC92 pea`k ia ? s�,hom any onrecvoc1anbaebrmoaedrca.t 4 Antenna sea ` " �t ,ki Afic'a x< Xv1.rzt s,ja �1," T, . 4 s .O MzHPSP rmoae seStadohTB1Teprryis2 �� ,. BTAc9Y " Trt�e. 4fn .12 T n :y r to n. .jiltrs . z P . Console Patch Note that console patching at fixed-site base stations is not authorized under state licenses for interoperability channels. Such installations must be licensed separately. 52 V . 7V Pg. /63 I tFittq •1+ as y, �wi 5r'.G.V:) .=LISTL,OFAGRQNYMS. 08,0 1T=,mss. . :, .. ..x. Abbre"viation ,a' t y, }, �' � Des ription Y' :' °°"� ' W .!,Amirar5Y;3tivn !x. FYv r, Tiw..4^.. AACOG Alamo Area Council of Governments ATCOG Ark-Tex Council of Governments BER Bit Error Rate BVCOG Brazos Valley Development Council BVWACS Brazos Valley Wireless Access Communications System CA California CAI Common Air Interface CAPCOG Capital Area Council of Governments CBCOG Coastal Bend Council of Governments CCG Communications Coordination Group CFR Code of Federal Regulations COG Council of Government COM-L Communications Leader CTCOG Central Council of Governments CTCSS Continuous Tone Coded Squelch System CVCOG Concho Valley Council of Governments DETCOG Deep East Texas Council of Governments DFW Dallas/ Ft.Worth DN Directory Number DPS Department of Public Safety EMS Emergency Medical Service ERP Effective Radiated Power ETCOG East Texas Council of Governments ETMC East Texas Medical Center FCC Federal Communications Commission GCRPC Golden Crescent Regional Planning Commission H-GAC Houston-Galveston Area Council HOTCOG Heart of Texas Council of Governments Hz Hertz ICS Incident Command System IRCIP Immediate Radio Communications Interoperability Plan IRWG Interagency Radio Work Group kHz Kilohertz KY Kentucky LA Louisiana LCRA Lower Colorado River Authority LE Law Enforcement LRGVDC Lower Rio Grande Valley Development Council MCPs Mobile Command Posts MHz Megahertz MD _ Maryland MOU Memorandum of Understanding MRGDC Middle Rio Grande Development Council MSAT Mobile Satellite MTA Metropolitan Transit Authority 53 Vet_ /c/ Pg. /4c1 I NAC Network Access Codes NCTCOG North Central Texas Council of Governments NIMS National Incident Management System NPSPAC National Public Safety Planning Advisory Committee NORTEX Nortex Regional Planning Commission NTIA National Telecommunications and Information Administration OPS Operations PBRPC Permian Basin Regional Planning Commission PRPC Panhandle Regional Planning Commission • PSAP Public Safety Answering Point PTT Push-To-Talk RGCOG Rio Grande Council of Governments SCADA Supervisory Control and Data Acquisition SCIP Statewide Communications Interoperability Plan SETRPC South East Texas Regional Planning Commission SMART Satellite Mutual Aid Radio Talkgroup SPAG South Plains Association of Governments STDC South Texas Development Council STRAC Southwest Texas Regional Advisory Council (Emergency Healthcare) SWIC Statewide Interoperability Coordinator TCOG Texoma Council of Governments TFS Texas A&M Forest Service TFS EOC Texas A&M Forest Service Emergency Operations Center TDEM Texas Division of Emergency Management TEEX Texas Engineering Extension Service (Training Academy) TTF Texas Task Force TG Ta(kgroup TSIEC Texas Statewide I nteroperability Executive Committee TxDPS Texas Department of Public Safety TxICC Texas Interoperable Communications Coalition UHF Ultra High Frequency VFD Volunteer Fire Department VHF Very High Frequency WCTCOG West Central Texas Council of Governments 54 6 Contract Number: HHSREV 100001010 DEPARTMENT OF STATE HEALTH SERVICES .F ri F°3 4\ . Contract number HHSREV 100001010 (the"Contract"), is entered into by Department of State Health Services ("DSHS")Vital Statistics Section and Brazos County("Contractor"). DSHS and Contractor are collectively referred to herein as the"Parties." I. Purpose of the Contract. DSHS agrees to provide access to the DSHS Vital Event Electronic Registration System for the purpose of issuing individual birth certificates. II. Term of the Contract. This Contract will begin on September 1,2018 and end on August 31,2023. III. Authority. The Parties enter into this Contract under the authority of Texas Health and Safety Code Chapter 191 and Texas Government Code Chapter 791. IV. Statement of Work. A. DSHS agrees to provide on-line computer services in support of Contractor from 7:00 a.m. to 6:00 p.m. (CST) Monday through Friday, except holidays. In the event of an emergency or computer application error, DSHS may temporarily suspend services without advance notice. • B. Contractor may search DSHS databases, locate data, and issue Certifications of Birth to authorized individuals requesting such data. The certifications will be in a format formally approved by DSHS. Contractor will take reasonable efforts to ensure use of the DSHS Vital Event Electronic Registration System is not abused by its staff. Abuse of the access to confidential information in the DSHS Vital Event Electronic Registration System may be cause for termination of this Contract in accordance with Section IX.K. C. Contractor will acquire the necessary data processing equipment, communications, hardware or software, and purchase "bank note" paper, as specified by DSHS. DSHS will assist in connection of the equipment, furnish software program and provide technical assistance, if necessary. D. Contractor will complete the DSHS Vital Event Electronic Registration System registration forms as specified by DSHS. Contractor will remain in compliance with any requirements specified by DSHS for accessing the DSHS Vital Event Electronic Registration System. Contractor will not be required to pay an additional fee pursuant to this Subsection E. Contractor acknowledges that records may not be located in the searching process instituted by Contractor, or records which are located may have errors due to: Vss Remote Birth Access Page I H02 79' Pg. /aG Contract Number: HHSREV 100001010 1. Normal key-entry errors in spellings; 2. Accidental failure on the part of the DSHS to update a file for an amendment or paternity determination; and 3. The event year does not exist on the system. F. Contractor will notify DSHS in writing, at least monthly of errors or suspected errors that exist on the database information. G. Contractor is to maintain an inventory control and account for each document produced on"bank note" paper, including voided documents. H. Contractor will issue Certificates of Birth utilizing remote access to the DSHS system in conformance with Health and Safety Code Chapters 191, 192 and 195,as well as 25 Tex. Admin. Code Chapter 181. I. The Parties are required to comply with all applicable state and federal laws relating to the privacy and confidentiality of this data and records,which includes Texas Government Code Section 552.115. J. The Parties will use confidential records and information obtained under this Contract only for purposes as described in this Contract and as otherwise allowed by law. V. Fees. Contractor agrees to pay DSHS ONE DOLLAR AND EIGHTY-THREE CENTS($1.83) for each Certification of Vital Record printed as a result of searches of the database. Contractor agrees to charge the same base search fee for a birth certificate as DSHS. Additional fees may only be charged as authorized by Texas Health and Safety Code Chapter 191 and 25 Tex. Admin. Code Chapter 181. VI. Billing. A. DSHS will send an itemized billing to Contractor on a monthly basis for each Certification of Birth printed. This billing will be sent through the U.S. Postal • Service to the Contractor at: Name: Brazos County Clerk's Office Address: 300 East 26th Street, Suite 120 Bryan,TX 77803 B. Contractor will direct any billing inquiries either by phone to 512-776-7206 or email to vsubusinessservices R,,dshs.texas.gov. V55 Remote Birth Access Page 2 • Vol. 2 7V Pg. _/o7 Contract Number: HHSREV 100001010 VII. Payment Method. A. Contractor will remit payment to DSHS within thirty days after a billing is received by them. Payment by the Contractor will be considered made on the date postmarked. B. Contractor will send payments to DSHS at: Texas Department of State Health Services Cash Receipts Branch MC 2096 P.O.Box 149347 Austin,TX 78714-9347 C. Contractor will make payment to DSHS out of its current revenues. VIII. Representatives. The following will act as the Representative authorized to administer activities under this Contract on behalf of their respective Party. Brazos County DSHS Brazos County Texas Department of State Health Services Brazos County Clerk's Office Contract Management Section Attn: Karen McQueen Attn: Carolyn DeBoer Mail Code 1990 300 East 26th Street, Suite 120 P.O. Box 149347 Bryan,TX 77803 Austin,TX 78714:9347 Phone: (979) 361-4124 Phone: (512) 776-2265 Email:kmequeen@co.brazos.tx.us Email: Carolyn.deboer@dshs.texas.gov IX. General Terms and Conditions. A. Governing Law. Regarding all issues related to this Contract's formation, performance, interpretation, and any issues that may arise in any dispute between the parties,the Contract will be governed by and construed in accordance with the laws of the State of Texas. B. Amendment. This Contract may be modified by written amendment signed by the Parties. C. Confidentiality. The Parties are required to comply with all applicable state and federal laws relating to the privacy and confidentiality of records that contain Personal Identifying Information (PII) or Personally Sensitive Information (PSI) or other information or records made confidential by law,including Tex. Bus. & Comm. Code Section 521.002. The attached Data Use Agreement(Attachment A) applies to this Contract. VSS Remote Birth Access Page 3 ( Vol. 7V Pg. /Ob - � Contract Number: HHSREV100001010 D. Exchange of Personal Identifying Information. This Contract concerns personal identifying information. Except as prohibited by other law, Contractor and DSHS may exchange NI without consent, in accordance with Chapter 191 of the Health and Safety Code. E. Records Retention. DSHS will retain records in accordance with DSHS State of Texas Records Retention Schedule at http:/hvww.dshs.texas.gov/records/schedules.shtm, Department Rules and other applicable state and federal statutes and regulations governing medical,mental health, and substance abuse information. F. Severability. If any provision of this Contract is construed to be illegal or invalid, the illegal or invalid provision will be deemed stricken and deleted to the same extent and effect as if never incorporated,but all other provisions will continue. G. Notice. Any notice required or permitted to be given under this Contract will be in writing and sent to the respective Party's Representative in Section VIII. Notice will be deemed to have been received by a Party on the third business day after the date on which it was mailed to the Party at the address specified in writing by the Party to the other Party,or, if sent by certified mail, on the date of receipt. H. Waiver. Acceptance by either Party of partial performance or failure to complain of any action, non-action or default under this Contract will not constitute a waiver of either Party's rights under the Contract. I. Assignment. Neither DSHS nor Contractor will transfer, assign,or sell its interest, in whole or in part, in this Contract without prior written consent by both Parties. J. Suspension of Services Under This Contract. In the event of an emergency or information technology system failure, DSHS may temporarily suspend services without advance notice. Use of services for purposes inconsistent with applicable law may also result in a suspension of services. K. Termination. 1. Convenience.This Contract maybe terminated by mutual agreement of the Parties. Either Party may terminate this Contract without cause by giving 30 days written notice of its intent to terminate to the non-terminating Party. 2. Cause.This Contract may be terminated for cause by either Party for breach or failure to perform an essential requirement of the Contract. Use of services for purposes inconsistent with applicable law may be cause for Contract termination. 3. Notice of Termination.Written notice may be sent by any method that provides verification of receipt, which will be calculated from the date of receipt by the non- terminating Party's Representative provided in Section VIII. VSS Remote Birth Access Page 4 I vol. 7 Pg. /c Contract Number:HHSREV 100001010 4. Equitable Settlement. At the end of the Term of this Contract or termination as provided for in this Section, the Parties will equitably settle their respective accrued interests or obligations incurred prior to termination. By signing below, the Parties agree that this Contract constitutes the entire legal and binding agreement between them. The Parties acicnowledge that they have read the Contract and agree to its terms,and that the persons whose signatures appear below have the authority to execute this Contract on behalf of their respective Party. DEPARTMENT OF STATE HEALTH SERVICES BRAZOS CO i'TY 4a I� &- M.. da Hall,M.D. Duane Peters Associate Commissioner County Judge Department of State Health Services Brazos County �� gIEo � �g 5 � Date Date THE FOLLOWING ATTACHMENTS ARE ATTACHED AND INCORPORATED AS PART OF THE CONTRACT HHSREV100001010: ATTACHMENT A-DATA USE AGREEMENT VSS Remote Birth Access Page 5 Vol, d 7 Pg. 770 F,-; • ATTACHMENT A—DATA USE AGREEMENT DATA USE AGREEMENT • BETWEEN THE TEXAS HEALTH AND HUMAN SERVICES ENTERPRISE AND BRAZOS COUNTY("CONTRACTOR") This Data Use Agreement("DUA")is incorporated into System Agency Contract No. HHSREV 100001010(the"Base Contract")between the Texas Department of State Health Services ("System Agency")and Brazos County("Contractot"). ARTICLE 1.PURPOSE; APPLICABILITY; ORDER OF PRECEDENCE ATTACHMENT 1. The purpose of this DUA is to facilitate creation, receipt, maintenance, use, disclosure or access to Confidential Information with Contractor, and describe Contractor's rights and obligations with respect to the Confidential Information and the limited purposes for which the Contractor may create, receive, maintain, use, disclose or have access to Confidential Information. 45 CFR 164.504(e)(I)-(3). This DUA also describes System Agency's remedies in the event of Contractor's noncompliance with its obligations under this DUA. This DUA applies to both Business Associates and contractors who are not Business Associates who create, receive, maintain, use, disclose or have access to Confidential Information on behalf of System Agency,its programs or clients as described in the Base Contract. As of the Effective Date of the Contract,if any provision of the Base Contract,including any General Provisions or Uniform Terms and Conditions,conflicts with this DUA,this DUA controls. ARTICLE 2. DEFINITIONS For the purposes of this DUA, capitalized, underlined terms have the meanings set forth in the following: Health Insurance Portability and Accountability Act of 1996, Public Law 104-191 (42 U.S.C. §1320d, et seq.) and regulations thereunder in 45 CFR Parts 160 and 164, including all amendments, regulations and guidance issued thereafter; The Social Security Act, including Section 1137 (42 U.S.C. §§ 1320b-7), Title XVI of the Act; The Privacy Act of 1974, as amended by the Computer Matching and Privacy Protection Act of 1988,5 U.S.C. § 552a and regulations and guidance thereunder; Internal Revenue Code,Title 26 of the United States Code and regulations and publications adopted under that code, including IRS Publication 1075; OMB Memorandum 07-18; Texas Business and Commerce Code Ch. 521; Texas Government Code, Ch. 552, and Texas Government Code §2054.1125. In addition, the following terms in this DUA are defined as follows: "Authorized Purpose"means the specific purpose or purposes described in the Scope of Work of the Base Contract for Contractor to fulfill its obligations under the Base Contract, or any other purpose expressly authorized by System Agency in writing in advance. "Authorized User"means a Person: (1) Who is authorized to create, receive, maintain, have access to, process, view, handle, examine, interpret, or analyze Confidential Information pursuant to this DUA; (2) For whom Contractor warrants and represents has a demonstrable need to create,receive, maintain,use,disclose or have access to the Confidential Information; and System Agency Data Use Agreement.V.8.3 HIPAA Omnibus Compliant April 1,2015 GOVERNMENTAL ENTITY VERSION vel. � 7 Pg. /7/ i System Agency Contract No.1-IHSRE V 100001010 (3) Who has agreed in writing to be bound by the disclosure and use limitations pertaining to the Confidential Information as required by this DUA. "Confidential Information" means any communication or record (whether oral, written, electronically stored or transmitted,or in any other form)provided to or made available to Contractor or that . Contractor may create, receive, maintain, use, disclose or have access to on behalf of System Agency that consists of or includes any or all of the following: (1) Client Information; (2) Protected Health Information in any form including without limitation, Electronic Protected Health Information or Unsecured Protected Health Information; (3) Sensitive Personal Information defined by Texas Business and Commerce Code Ch.521; (4) Federal Tax Information; (5) Personally Identifiable Information; (6) Social Security Administration Data, including, without limitation, Medicaid information; (7) All privileged work product; (8) All information designated as confidential under the constitution and laws of the State of Texas and of the United States, including the Texas Health & Safety Code and the Texas Public Information Act,Texas Government Code, Chapter 552. "Legally Authorized Representative" of the Individual, as defined by Texas law, including as provided in 45 CFR 435.923 (Medicaid); 45 CFR 164.502(g)(1) (HIPAA); Tex. Occ. Code § 151.002(6); Tex.H.&S. Code§166.164; Estates Code Ch. 752 and Texas Prob.Code§3. ARTICLE 3.CONTRACTOR'S DUTIES REGARDING CONFIDENTIAL INFORMATION Section 3.01 Obligations of Contractor Contractor agrees that: (A) Contractor will exercise reasonable care and no less than the same degree of care Contractor uses to protect its own confidential, proprietary and trade secret information to prevent any portion of the Confidential Information from being used in a manner that is not expressly an Authorized Purpose under this DUA or as Required by Law.45 CFR 164.502(b)(1);45 CFR 164.514(d) (B) Contractor will not, without System Agency's prior written consent, disclose or allow access to any portion of the Confidential Information to any Person or other entity, other than Authorized User's Workforce or Subcontractors of Contractor who have completed training in confidentiality, privacy, security and the importance of promptly reporting any Event or Breach to Contractor's management,to carry out the Authorized Purpose or as Required by Law. System Agency, at its election, may assist Contractor in training and education on specific or unique System Agency processes, systems or requirements. Contractor will produce evidence of completed training to System Agency upon request. 45 C.F.R. 164.30800(5)(i); Texas Health & Safety Code§181.101 (C) Contractor will establish, implement and maintain appropriate sanctions against any member of its Workforce or Subcontractor who fails to comply with this DUA, the Base Contract or applicable law. Contractor will maintain evidence of sanctions and produce it to System Agency upon request.45 CF.R. 164.308(a)(1)(ii)(C); 164.530(e);164.410(6);164.530(b)(1) System Agency Data Use Agreement V.8.3 HIPA.A Omnibus Compliant April 1,2015 Page 2 of I Ecit )(7/ Pg. N)- System Agency Contract No.HHSREV 100001010 (D) Contractor will not,without prior written approval of System Agency, disclose or provide access to any Confidential Information on the basis that such act is Required by Law without notifying System Agency so that System Agency may have the opportunity to object to the disclosure or access and seek appropriate relief If System Agency objects to such disclosure or access, Contractor will refrain from disclosing or providing access to the Confidential Information until System Agency has exhausted all alternatives for relief 45 CFR 164.504(e)(2)(ii)(A) (E) Contractor will not attempt to re-identify or further identify Confidential Information or De-identified Information, or attempt to contact any Individuals whose records are contained in the Confidential Information, except for an Authorized Purpose, without express written authorization from System Agency or as expressly permitted by the Base Contract. 45 CFR 164.502(d)(2)(i) and (ii) Contractor will not engage in prohibited marketing or sale of Confidential Information. 45 CFR 164.501, 164.508(a)(3)and(4); Texas Health&Safety Code Ch. 181.002 (F) Contractor will not permit, or enter into any agreement with a Subcontractor to, create, receive, maintain, use, disclose, have access to or transmit Confidential Information, on behalf of Contractor without requiring that Subcontractor first execute the Form Subcontractor Agreement, Attachment 1, which ensures that the Subcontractor will comply with the identical terms, conditions, safeguards and restrictions as contained in this DUA for PHI and any other relevant Confidential Information and which permits more strict limitations; and 45 CFR 164.502(e)(1)(1)(ii); 164.504(e)(1)(1) and(2) (G) Contractor is directly responsible for compliance with,and enforcement of,all conditions for creation,maintenance, use,disclosure,transmission and Destruction of Confidential Information and the acts or omissions of Subcontractors as may be reasonably necessary to prevent unauthorized use. 45 CFR 164.504(e)(5);42 CFR 431.300,et seq. (H) If Contractor maintains PHI in a Designated Record Set, Contractor will make PHI available to System Agency in a Designated Record Set or, as directed by System Agency, provide PHI to the Individual, or Legally Authorized Representative of the Individual who is requesting PHI in compliance with the requirements of the HIPAA Privacy Regulations. Contractor will make other Confidential Information in Contractor's possession available pursuant to the requirements of HIPAA or other applicable law upon a determination of a Breach of Unsecured PHI as defined in HIPAA. 45 CFR 164.524and 164.504(e)(2)(1i)(E) (I) Contractor will make PHI as required by HIPAA available to System Agency for amendment and incorporate any amendments to this information that System Agency directs or agrees to pursuant to the HIPAA. 45 CFR 164.504(e)(2)(ii)(E)and(F) (J) Contractor will document and make available to System Agency the PHI required to provide access, an accounting of disclosures or amendment in compliance with the requirements of the HIPAA Privacy Regulations.45 CFR 164.504(e)(2)(ii)(G) and 164.528 (K) If Contractor receives a request for access, amendment or accounting of PHI by any Individual subject to this DUA, it will promptly forward the request to System Agency; however, if it would violate HIPAA to forward the request, Contractor will promptly notify of the request and of Contractor's response. Unless Contractor is prohibited by law from forwarding a request, System Agency will respond to all such requests,unless System Agency has given prior written consent for Contractor to respond to and account for all such requests. 45 CFR 164.504(e)(2) (L) Contractor will provide, and will cause its Subcontractors and agents to provide, to System Agency periodic written certifications of compliance with controls and provisions relating to information privacy, security and breach notification, including without limitation information related to . Systcm Agency Data Use Agreement V.8.3 HIPAA Omnibus Compliant April 1,2015 Page 3 of I I {vol. 017V Pg. //3 1 System Agency Contract No.HHSREV 100001010 data transfers and the handling and disposal of Confidential Information. 45 CFR 164.308;164.530(c);1 TAC 202 (M) Except as otherwise limited by this DUA, the Base Contract, or law applicable to the Confidential Information, Contractor may use or disclose PHI for the proper management and administration of Contractor or to carry out Contractor's legal responsibilities if:45 CFR 164.504(e)(h)(1)69) (1) Disclosure is Required by Law, provided that Contractor complies with Section 3.01(D); (2) Contractor obtains reasonable assurances from the Person to whom the information is disclosed that the Person will: (a)Maintain the confidentiality of the Confidential Information in accordance with this DUA; (b) Use or further disclose the information only as Required by Law or for the Authorized Purpose for which it was disclosed to the Person; and (c) Notify Contractor in accordance with Section 4.01 of any Event or Breach of Confidential Information of which the Person discovers or should have discovered with the exercise of reasonable diligence. 45 CFR 164.504(e)(4)(r0(B) (N) Except as otherwise limited by this DUA, Contractor will, if requested by System Agency, use PHI to provide data aggregation services to System Agency, as that term is defined in the HIPAA,45 C.F.R. §164.501 and permitted by HIPAA. 45 CFR 164.504(e)(2)(1)(B) (0) Contractor will, on the termination or expiration of this DUA or the Base Contract, at its expense, return to System Agency or Destroy, at System Agency's election, and to the extent reasonably feasible and permissible by law, all Confidential Information received from System Agency or created or maintained by Contractor or any of Contractor's agents or Subcontractors on System Agency's behalf if that data contains Confidential Information. Contractor will certify in writing to System Agency that all the Confidential Information that has been created, received, maintained, used by or disclosed to Contractor, has been Destroyed or returned to System Agency, and that Contractor and its agents and Subcontractors have retained no copies thereof. Notwithstanding the foregoing,Contractor acknowledges and agrees that it may not Destroy any Confidential Information if federal or state law, or System Agency record retention policy or a litigation hold notice prohibits such Destruction. If such return or Destruction is not reasonably feasible, or is impermissible by law, Contractor will immediately notify System Agency of the reasons such return or Destruction is not feasible, and agree to extend indefinitely the protections of this DUA to the Confidential Information and limit its further uses and disclosures to the purposes that make the return of the Confidential Information not feasible for as long as Contractor maintains such Confidential Information. 45 CFR 164.504(e)(2)(ii)(J (P) Contractor will create, maintain, use, disclose, transmit or Destroy Confidential Information in a secure fashion that protects against any reasonably anticipated threats or hazards to the security or integrity of such information or unauthorized uses. 45 CFR 164.306;164.530(c) (Q) If Contractor accesses, transmits, stores, or maintains Confidential Information, Contractor will complete and return to System Agency at infosecurity@hhsc.state.tx.us the System Agency information security and privacy initial inquiry(SPI) at Attachment 2 . The SPI identifies basic privacy and security controls with which Contractor must comply to protect System Agency Confidential Information. Contractor will comply with periodic security controls compliance assessment and monitoring by System Agency as required by state and federal law, based on the type of Confidential Information Contractor creates, receives, maintains, uses, discloses or has access to and the Authorized Purpose and level of risk. Contractor's security controls will be based on the National Institute of Standards and Technology (NIST) Special Publication 800-53. Contractor will update its security controls assessment whenever there are significant changes in security controls for System Agency System Agency Data Use Agreement V.8.3 HIPAA Omnibus Compliant April 1,2015 Page 4 of 11 !v . 71). Pg. //,/ System Agency Contract No.IIHSREV 100001010 Confidential Information and will provide the updated document to System Agency. System Agency also reserves the right to request updates as needed to satisfy state and federal monitoring requirements. 45 CFR 164.306 (R) Contractor will establish, implement and maintain any and all appropriate procedural, administrative, physical and technical safeguards to preserve andmaintain the confidentiality, integrity, and availability of the Confidential Information and with respect to PHI, as described in the HIPAA Privacy and Security Regulations, or other applicable laws or regulations relating to Confidential Information to prevent any unauthorized use or disclosure of Confidential Information as long as Contractor has such Confidential Information in its actual or constructive possession. 45 CFR 164.308 (administrative safeguards); 164.310 (physical safeguards); 164.312 (technical safeguards); 164.530(c)(privacy safeguards) (S) Contractor will designate and identify, subject to System Agency approval, a Person or Persons, as Privacy Official 45 CFR 164.530(a)(1) and Information Security Official, each of whom is authorized to act on behalf of Contractor and is responsible for the development and implementation of the privacy and security requirements in this DUA. Contractor will provide name and current address, phone number and e-mail address for such designated officials to System Agency upon execution of this DUA and prior to any change. 45 CFR 164.308(a)(2) (T) Contractor represents and warrants that its Authorized Users each have a demonstrated need to lmow and have access to Confidential Information solely to the minimum extent necessary to accomplish the Authorized Purpose pursuant to this DUA and the Base Contract, and further, that each has agreed in writing to be bound by the disclosure and use limitations pertaining to the Confidential Information contained in this DUA. 45 CFR 164.502;164.514(d) (U) Contractor and its Subcontractors will maintain an updated, complete, accurate and numbered list of Authorized Users, their signatures, titles and the date they agreed to be bound by the terms of this DUA, at all times and supply it to System Agency, as directed,upon request. (V) Contractor will implement, update as necessary, and document reasonable and appropriate policies and procedures for privacy, security and Breach of Confidential Information and an incident response plan for an Event or Breach, to comply with the privacy, security and breach notice requirements of this DUA prior to conducting work under the DUA. 45 CFR 164.308; 164.316; 164.514(d);164.530(0(1) (W) Contractor will produce copies of its information security and privacy policies and procedures and records relating to the use or disclosure of Confidential Information received from, created by, or received, used or disclosed by Contractor on behalf of System Agency for System Agency's review and approval within 30 days of execution of this DUA and upon request by System Agency the following business day or other agreed upon time frame. 45 CFR 164.308;164.514(d) (X) Contractor will make available to System Agency any information System Agency requires to fulfill System Agency's obligations to provide access to, or copies of,PHI in accordance with HIPAA and other applicable laws and regulations relating to Confidential Information. Contractor will provide such information in a time and manner reasonably agreed upon or as designated by the Secretary, or other federal or state law.45 CFR 164.504(e)(2)0(1) (Y) Contractor will only conduct secure transmissions of Confidential Information whether in paper, oral or electronic form. A secure transmission of electronic Confidential Information in motion includes secure File Transfer Protocol(SFTP)or Encryption at an appropriate level or otherwise protected as required by rule, regulation or law. System Agency Confidential Information at rest requires Encryption unless there is adequate administrative, technical, and physical security, or as otherwise System Agency Data Use Agreement V.8.3 HIPAA Omnibus Compliant April 1,2015 Page 5 of 11 v01. ,� 1 Pg. /1�5�� • System Agency Contract No.HHSRE V 100001010 • protected as required by rule, regulation or law. All electronic data transfer and communications of Confidential Information will be through secure systems. Proof of system, media or device security or Encryption must be produced to System Agency no later than 48 hours after System Agency's written request in response to a compliance investigation, audit or the Discovery of an Event or Breach. Otherwise, requested production of such proof will be made as agreed upon by the parties. De- identification of System Agency Confidential Information is a means of security. With respect to de- identification of PHI, "secure" means de-identified according to HIPAA Privacy standards and regulatory guidance.45 CFR 164.312;164.530(d) (Z) Contractor will comply with the following laws and standards if applicable to the type of Confidential Information and Contractor's Authorized Purpose: • Title 1,Part 10. Chapter 202, Subchapter B,Texas Administrative Code; • The Privacy Act of 1974; • OMB Memorandum 07-16; • The Federal Information Security Management Act of 2002(FISMA); • The Health Insurance Portability and Accountability Act of 1996 (HIPAA) as defined in the DUA; • Internal Revenue Publication 1075 —Tax Information Security Guidelines for Federal, State and Local Agencies; • National Institute of Standards and Technology(NIST) Special Publication 800-66 Revision 1 — An Introductory Resource Guide for Implementing the Health Insurance Portability and Accountability Act(HIPAA)Security Rule; • NIST Special Publications 800-53 and 800-53A — Recommended Security Controls for Federal Information Systems and Organizations,as currently revised; • NIST Special Publication 800-47 — Security Guide for Interconnecting Information Technology Systems; • NIST Special Publication 800-88,Guidelines for Media Sanitization- • NIST Special Publication 800-111, Guide to Storage of Encryption Technologies for End User Devices containing PHI; and • Any other State or Federal law,regulation,or administrative rule relating to the specific System Agency program area that Contractor supports on behalf of System Agency. ARTICLE 4. BREACH NOTICE,REPORTING AND CORRECTION REQUIREMENTS Section 4.01. Breach or Event Notification to System Agency. 45 CFR 164.400-414 (A) Contractor will cooperate fully with System Agency in investigating, mitigating to the extent practicable and issuing notifications directed by System Agency, for any Event or Breach of Confidential Information to the extent and in the manner determined by System Agency. (B) Contractor'S obligation begins at the Discovery of an Event or Breach and continues as long as related activity continues, until all effects of the Event are mitigated to System Agency's satisfaction(the"incident response period"). 45 CFR 164.404 (C) Breach Notice: I. Initial Notice. System Agency Data Use Agreement V.8.3 HIPAA Omnibus Compliant April 1,2015 Page 6 of 11 VS. 02 79- Pg. //� System Agency Contract No.HHSREV 100001010 a.For federal information, including without limitation, Federal Tax Information, Social Security Administration Data, and Medicaid Client Information within the first, consecutive clock hour of Discovery, and for all other types of Confidential Information not more than 24 hours after Discovery, or in a timeframe otherwise approved by System Agency in writing,initially report to System Agency's Privacy and Security Officers via email at: privacy@System AgencvC.state.tx.us and to the System Agency division responsible for this DUA' and IRS Publication 1075; Privacy Act of 1974, as amended by the Computer Matching and Privacy Protection Act of 1988, 5 U.S.C. § 552a; OMB Memorandum 07-16 as cited in System AgencyC-CMS Contracts for information exchange. b. Report all information reasonably available to Contractor about the Event or Breach of the privacy or security of Confidential Information. 45 CFR 164.410 c. Name, and provide contact information to System Agency for, Contractor's single point of contact who will communicate with System Agency both on and off business hours during the incident response period. 2. 48-Hour Formal Notice. No later than 48 consecutive clock hours after Discovery, or a time within which Discovery reasonably should have been made by Contractor of an Event or Breach of Confidential Information, provide formal notification to the State, including all reasonably available information about the Event or Breach, and Contractor's investigation, including without limitation and to the extent available: For (a) -(m) below: 45 CFR 164.400- 414 a.The date the Event or Breach occurred; b.The date of Contractor's and, if applicable, Subcontractor's Discovery; c. A brief description of the Event or Breach; including how it occurred and who is responsible (or hypotheses, if not yet determined); d. A brief description of Contractor's investigation and the status of the investigation; e. A description of the types and amount of Confidential Information involved; f. Identification of and number of all Individuals reasonably believed to be affected, including first and last name of the individual and if applicable the, Legally authorized representative, last known address, age, telephone number, and email address if it is a preferred contact method, to the extent known or can be reasonably determined by Contractor at that time; g.Contractor's initial risk assessment of the Event or Breach demonstrating whether individual or other notices are_required by applicable law or this DUA for System Agency approval, including an analysis of whether there is a low probability of compromise of the Confidential Information or whether any legal exceptions to notification apply; h. Contractor's recommendation for System Agency's approval as to the steps Individuals or Contractor on behalf of Individuals, should take to protect the Individuals from potential harm, including without limitation Contractor's provision of notifications, credit protection, claims monitoring, and any specific protections for a Legally Authorized Representative to take on behalf of an Individual with special capacity or circumstances; i.The steps Contractor has taken to mitigate the harm or potential harm caused(including without limitation the provision of sufficient resources to mitigate); j.The steps Contractor has taken,or will take, to prevent or reduce the likelihood of recurrence of a similar Event or Breach; System Agency Data Use Agreement V.8.3 HIPAA Omnibus Compliant April 1,2015 Page 7 of 11 Vot. _a27Y Pg. //7 l� System Agency Contract No.HHSREV 100001010 k.Identify,describe or estimate of the Persons,Workforce, Subcontractor,or Individuals and any law enforcement that may be involved in the Event or Breach; 1. A reasonable schedule for Contractor to provide regular updates to the foregoing in the future for response to the Event or Breach,but no less than every three(3)business days or as otherwise directed by System Agency, including information about risk estimations, reporting, notification, if any, mitigation,corrective action, root cause analysis and when such activities are expected to be completed; and m. Any reasonably available, pertinent information, documents or reports related to an Event or Breach that System Agency requests following Discovery. Section 4.02 Investigation,Response and Mitigation. For A-F below: 45 CFR 164.308, 310 and 312;164.530 (A) Contractor will immediately conduct a full and complete investigation, respond to the Event or Breach, commit necessary and appropriate staff and resources to expeditiously respond, and report as required to and by System Agency for incident response purposes and for purposes of System Agency's compliance with report and notification requirements, to the satisfaction of System Agency. (B) Contractor will complete or participate in a risk assessment as directed by System Agency following an Event or Breach, and provide the final assessment, corrective actions and mitigations to System Agency for review and approval. (C) Contractor will fully cooperate with System Agency to respond to inquiries and proceedings by state and federal authorities,Persons and Individuals about the Event or Breach. (D) Contractor will fully cooperate with System Agency's efforts to seek appropriate injunctive relief or otherwise prevent or curtail such Event or Breach, or to recover or protect any Confidential Information, including complying with reasonable corrective action or measures, as specified by System Agency in a Corrective Action Plan if directed by System Agency under the Base Contract. Section 4.03 Breach Notification to Individuals and Reporting to Authorities. Tex. Bas. & Coaun. Code§521.053; 45 CFR 164.404(Individuals), 164.406(Media);164.408(Authorities) (A) System Agency may direct Contractor to provide Breach notification to Individuals, regulators or third-parties,as specified by System Agency following a Breach. (B) Contractor must obtain System Agency's prior written approval of the time, manner and content of any notification to Individuals, regulators or third-parties, or any notice required by other state or federal authorities. Notice letters will be in Contractor's name and on Contractor's letterhead, unless otherwise directed by System Agency, and will contain contact information, including the name and title of Contractor's representative, an email address and a toll-free telephone number, for the Individual to obtain additional information. (C) Contractor will provide System Agency with copies of distributed and approved communications. (D) Contractor will have the burden of demonstrating to the satisfaction of System Agency that any notification required by System Agency was timely made. If there are delays outside of Contractor's control, Contractor will provide written documentation of the reasons for the delay. System Agency Data Use Agreement V.83 HIPAA Omnibus Compliant April 1,2015 Page 8 of 11 Va. 2 7/ Pg. �/ System Agency Contract No.HHSREV 100001010 (E) If System Agency delegates notice requirements to Contractor, System Agency shall,in the time and manner reasonably requested by Contractor, cooperate and assist with Contractor's information requests in order to make such notifications and reports. ARTICLE S. SCOPE OF WORK Scope of Work means the services and deliverables to be performed or provided by Contractor,or on behalf of Contractor by its Subcontractors or agents for System Agency that are described in detail in the Base Contract. The Scope of Work,including any future amendments thereto, is incorporated by reference in this DUA as if set out word-for-word herein. ARTICLE 6. GENERAL PROVISIONS Section 6.01 Ownership of Confidential infonnation Contractor acknowledges and agrees that the Confidential Information is and will remain the property of System Agency. Contractor agrees it acquires no title or rights to the Confidential Information. Section 6.02 System Agency Commitment and Obligations System Agency will not request that Contractor create, maintain, transmit, use or disclose PHI in any manner that would not be permissible under applicable law if done by System Agency. Section 6.03 System Agency Right to Inspection At any time upon reasonable notice to Contractor, or if System Agency determines that Contractor has violated this DUA, System Agency, directly or through its agent, will have the right to inspect the facilities, systems,books and records of Contractor to monitor compliance with this DUA. For purposes of this subsection, System Agency's agent(s) include, without limitation, the System Agency Office of the Inspector General or the Office of the Attorney General of Texas, outside consultants or legal counsel or other designee. Section 6.04 Term; Termination of DUA;Survival This DUA will take effect with the Base Contract, and will terminate upon termination of the Base Contract and as set forth herein. If the Base Contract is extended or amended, this DUA is updated automatically concurrent with such extension or amendment. (A) System Agency may immediately terminate this DUA and Base Contract upon a material violation of this DUA. (B) Termination or Expiration of this DUA will not relieve Contractor of its obligation to return or Destroy the Confidential Information as set forth in this DUA and to continue to safeguard the Confidential Information until such time as determined by System Agency. (D) If System Agency determines that Contractor has violated a material term of this DUA; System Agency may in its sole discretion: 1. Exercise any of its rights including but not limited to reports, access and inspection under this DUA or the Base Contract;or 2. Require Contractor to submit to a corrective action plan,including a plan for monitoring and plan for reporting, as System Agency may determine necessary to maintain compliance with this DUA;or System Agency Data Use Agreement V.8.3 HIPAA Omnibus Compliant April I,2015 Page 9 of II 1Vol. c; /�f Pg. I/ y System Agency Contract No.HHSREV100001010 3. Provide Contractor with a reasonable period to cure the violation as determined by System Agency; or 4. Terminate the DUA and Base Contract immediately, and seek relief in a court of competent jurisdiction in Travis County, Texas. Before exercising any of these options, System Agency will provide written notice to Contractor describing the violation and the action it intends to take. (E) If neither termination nor cure is feasible, System Agency shall report the violation to the Secretary. (F) The duties of Contractor or its Subcontractor under this DUA survive the expiration or termination of this DUA until all the Confidential Information is Destroyed or returned to System Agency, as required by this DUA. Section 6.05 Governing Law, Venue and Lidgatian (A) The validity,construction and performance of this DUA and the legal relations among the Parties to this DUA will be governed by and construed in accordance with the laws of the State of Texas. (B) The Parties agree that the courts of Travis County,Texas, will be the exclusive venue for any litigation, special proceeding or other proceeding as between the parties that may be brought,or arise out of,or in connection with,or by reason of this DUA. Section 6.06 Injunctive Relief (A) Contractor acknowledges and agrees that System Agency may suffer irreparable injury if Contractor or its Subcontractor fails to comply with any of the terms of this DUA with respect to the Confidential Information or a provision of HIPAA or other laws or regulations applicable to Confidential Information. (B) Contractor further agrees that monetary damages may be inadequate to compensate System Agency for Contractor's or its Subcontractor's failure to comply. Accordingly, Contractor agrees that System Agency will, in addition to any other remedies available to it at law or in equity,be entitled to seek injunctive relief without posting a bond and without the necessity of demonstrating actual damages, to enforce the terms of this DUA. Section 6.07 Indemnification To the extent permitted by law,Contractor will indemnify,defend and hold harmless System Agency and its respective Executive Commissioner, employees, Subcontractors, agents (including other state agencies acting on behalf of System Agency) or other members of its Workforce (each of the foregoing hereinafter referred to as 'Indemnified Party")against all actual and direct losses suffered by the Indemnified Party and all liability to third parties arising from or in connection with any breach of this DUA or from any acts or omissions related to this DUA by Contractor or its employees, directors,officers,Subcontractors,or agents or other members of its Workforce. The duty to indemnify,defend and hold harmless is independent of the duty to insure and continues to apply even in the event insurance coverage required, if any, in the DUA or Base Contract is denied, or coverage rights are reserved by any insurance carrier. Upon demand, Contractor will reimburse System Agency for any and all losses, liabilities, lost profits, fines, penalties, costs or expenses (including reasonable attorneys' fees)which may for any reason be imposed upon any Indemnified Party by reason of any suit,claim, action, proceeding or demand by any third party to the extent caused by and which results from the Contractor's failure to meet any of its obligations under this DUA. To the extent permitted System Agency Data Use Agreement V.8.3 HIPAA Omnibus Compliant April 1,2015 Page 10 of 11 CAV Pg. �� System Agency Contract No.11HHSREV 100001010 • by law, Contractor's obligation to defend, indemnify and hold harmless any Indemnified Party will survive the expiration or termination of this DUA. Section 6.08 Insurance (A) Contractor represents and warrants that it maintains either self-insurance or commercial insurancewith policy limits sufficient to cover any liability arising from any acts or omissions by Contractor or its employees, directors, officers, Subcontractors, or agents or other members of its Workforce under this DUA. Contractor warrants that System Agency will be a loss payee and beneficiary for any such claims. .. (B) Contractor will provide System Agency with written proof that required insurance coverage is in effect,at the request of System Agency. Section 6.09 Fees and Costs Except as otherwise specified in this DUA or the Base Contract, including but not limited to requirements to insure or indemnify System Agency, if any legal action or other proceeding is brought for the enforcement of this DUA, or because of an alleged dispute, contract violation, Event, Breach, default, misrepresentation,or injunctive action, in connection with any of the provisions of this DUA,each party will bear their own legal expenses and the other cost incurred in that action or proceeding. Section 6,10 Entirety of the Contract This Data Use Agreement is incorporated by reference into the Base Contract and,together with the Base Contract, constitutes the entire agreement between the parties. No change, waiver, or discharge of obligations arising under those documents will be valid unless in writing and executed by the party against whom such change,waiver,or discharge is sought to be enforced. Section 6.11 Automatic Amendment and Interpretation Upon the effective date of any amendment or issuance of additional regulations to HIPAA, or any other law applicable to Confidential Information, this DUA will automatically be amended so that the obligations imposed on System Agency or Contractor remain in compliance with such requirements. Any ambiguity in this DUA will be resolved in favor of a meaning that permits System Agency and Contractor to comply with HIPAA or any other law applicable to Confidential Information. System Agency Data Use Agreement V.8.3 HIPAA Omnibus Compliant April I,2015 Page 11 of 11 VOL Zg Pg. /2/ System Agency Contract No.HHSREV 100001010 ATTACHMENT 1. SUBCONTRACTOR AGREEMENT FORM System Agency CONTRACT NUMBER H$SREV100001010 The DUA between System Agency and Contractor establishes the permitted and required uses and • disclosures of Confidential Information by Contractor. Contractor has subcontracted with (SUBContractor)for performance of duties on behalf of CONTACTOR which are subject to the DUA. SUBContractor acknowledges,understands and agrees to be bound by the identical terms and conditions applicable to Contractor under the DUA,incorporated by reference in this Agreement,with respect to System Agency Confidential Information. Contractor and SUBContractor agree that System Agency is a third-party beneficiary to applicable provisions of the subcontract. System Agency has the right but not the obligation to review or approve the terms and conditions of the subcontract by virtue of this Subcontractor Agreement Form. Contractor and SUBContractor assure System Agency that any Breach or Event as defined by the DUA that SUBContractor Discovers will be reported to System Agency by Contractor in the time,manner and content required by the DUA. If Contractor knows or should have known in the exercise of reasonable diligence of a pattern of activity or practice by SUBContractor that constitutes a material breach or violation of the DUA or the SUBContractor's obligations Contractor will: 1. Take reasonable steps to cure the violation or end the violation,as applicable; 2. If the steps are unsuccessful,terminate the contract or arrangement with SUBContractor, if feasible; 3. Notify System Agency immediately upon reasonably discovery of the pattern of activity or practice of SUBContractor that constitutes a material breach or violation of the DUA and keep System Agency reasonably and regularly informed about steps Contractor is taking to cure or end the violation or terminate SUBCONTACTOR's contract or arrangement. This Subcontractor Agreement Form is executed by the parties in their capacities indicated below. CONTRACTOR SUBCONTRACTOR BY: BY: NAME: NAME: TITLE: TITLE: DATE ,201 . DATE: System Agency Data Use Agreement V.8.3 HIPAA Omnibus Compliant April 1,2015 Attachment 1 Page 1of1 va. � p9. A TEXAS HHS Enterprise Data Use Agreement-Attachment 2 you Health and Human SECURITY AND PRIVACY INITIAL INQUIRY(SPI) '4 Services If you are a bidder for a new procurement/contract,in order to participate in the bidding process,you must have corrected any"No" responses in sections B and C prior to the contract award date. If you are an applicant for an open enrollment,you must have corrected any"No"answers in Sections B and C below prior to performing any work on behalf of any HHS agency. For existing contracts or renewals with"No"responses,there must be an action plan for remediation of Section B and C within 30 calendar days for HIPAA related contracts and 90 calendar days from the date the form is signed for all non-HIPAA contracts. • SECTION A:APPLICANT/BIDDER INFORMATION (To be completed by Applicant/Bidder) r, 1. Does the applicant/bidder access, create, disclose, receive, transmit, maintain, or store HHS 0 Yes Confidential Information in electronic systems (e.g.,.laptop, personal use computer, mobile 0 No device, database,server, etc.)? IF NO,STOP. THE SPI FORM IS NOT REQUIRED. 2. Entity or Applicant/Bidder Legal Name Legal Name: Akar /t,„,,,.t., ekth_ Legal Entity Tax Identification Number • (TIN) (Last Four Numbers Only): , 433 Procurement/Contract#: H H 5r€E V (DOWIII© • Address: Soo E. ZG 5F 54. 11430 City:, rrjezyt State: %K. ZIP:771(O3 Telephone#: 979-56/-4/J4 Email Address: 1Gl1cr/rcte2YL "�J7r, osco0At(1( gdy 3 .Number of Employees,at all locations, in Applicant Total Employees: pi G " d Bidder's Workforce "Workforce"means all employees,volunteers,trainees,and other Persons whose conduct is under the direct control of Applicant/Bidder,whether or not they are paid by Applicant/ Bidder.If Applicant/Bidder is a sole proprietor,the workforce may be only one employee. 4. Number of Subcontractors Total Subcontractors: (if Applicant/Bidder will not use subcontractors,enter"0") 5. Name of Information Technology Security Official A. Security Official: and Name of Privacy Official for Applicant/Bidder Legal Name: &ue. 04-tcci,u-e-a. (Privacy and Security Official may be the same person.) Address:As'ea-s}- 214- 51-- • City:Aaz) State: / K ZIP: -17Z05 Telephone#: R74 -3b 1-43/Of Email Address: eft/LULL-LA to coU A B. Privacy Official: SFFhLc' Legal Name: Address: City: State: ZIP: Telephone #: Email Address: HHS Enterprise Data Use Agreement,Attachment 2: clso-oo�-NDa(ttrls)(vz.o) p Page lofl7 SECURITY p-BLVACY INITIAL INQUIRY(SPI) Voi 7 __-.-R9: i23 6. Type(s) of HHS Confidential Information the Entity or HI PAA CJIS IRS FTI CMS SSA PII I3 Applicant/Bidder will create, receive,maintain;use, 0 0 El 0 III disclose or have access to: (Check all that apply) Other (Please List) •Health Insurance Portability and Accountability Act(HIPAA)data •Criminal Justice Information Services(015)data •Internal Revenue Service Federal Tox Information(IRS FTI)data •Centers for Medicare&Medicaid Services(CMS) •Social Security Administration(SSA) •Personally Identifiable Information(PIO) 7 Number of Storage Devices for HHS Confidential Information (as defined In the HHS Data ;Total f# Use Agreement(DUA)) Sum a d • ( ) • Cloud Services involve using a network of remote servers hosted on the Internet to store manage;and , • process data ratherthan a local server'or a personal computer ` _ S ` tx A Dat a Center is a centralized repository either physical or virtual forthe storage management and ` • :,'C',',, ` ' dissemination_Of data and mforn ation organized around a particular body of knowledge or pertainmgto a particularbuslness^ z cl a>n-� -. .. . . . .. w ,... ..,.. .. a. Devices. Number of persTrial user computers, devices or drives, including mobile devices and mobile drives. b.Servers. Number of Servers that are not in a data center or using Cloud Services. 0 c.Cloud Services. Number of Cloud Services in use. 0 d. Data Centers. Number of Data Centers in use. Q 8- Number of unduplicated Individuals for whom'Applicant/Bidder'reasonably expects to ;Select handle HHS Confidential Informationduring one year • Option a. 499 individuals or less ® a. b. 500 to 999 individuals Q b. c. 1,000 to 99,999 individuals 0 c. d. 100,000 individuals or more 0 d. 9 HIPAA.Business Associate•Agreement` ,Yes or No a. Will Applicant/Bidder use, disclose, create, receive, transmit or maintain protected ®Yes health information on behalf of a HIPAA-covered HHS agency for a HIPAA-covered o No function? b. Does Applicant/Bidder have a Privacy Notice prominently displayed on a Webpage or a ,) Yes Public Office of Applicant/Bidder's business open to or that serves the public? (This is a Q No HIPAA requirement.Answer"No" if not applicable,such as for agencies not covered by HIPAA.) 10 Subcontractors 'If the Applicant/Bidder responded "0" to Question 4'(indicating no yes or No subcontractors),check No for`both a.;and b 'to, indicate"N/A a. Does Applicant/Bidder require subcontractors to execute the DUA Attachment 1 0 Yes Subcontractor Agreement Form? © No b. Will Applicant/Bidder obtain written approval from an HHS agency before entering into 0 Yes any agreements with subcontractors to handle HHS Confidential Information on behalf ® No of Applicant/Bidder? CISO-001-NDQ(11/16)(V2.0) HHS Enterprise Data Use Agreement,Attachment 2: Page 2 of 17 SECUEdj�/ACY INITIAL INQUIRY(SPI) _21.9_____ p9. / sl- 11. Does Applicant/Bidder have any Optional Insurance currently in place? ® Yes Optional Insurance provides coverage for:(1) Network Security and Privacy;(2)Data Breach;(3)Cyber 0 No Liability(lost data,lost use or delay/suspension in business,denial of service with e-business,the Internet, networks and informational assets,such as privacy,intellectual property,virus transmission,extortion, sabotage or web activities);(4)Electronic Media Liability;(5)Crime/Theft;(6)Advertising Injury and Personal Injury Liability;and(7)Crisis Management and Notification Expense Coverage. Section B: PRIVACY:RUSK ANALYSIS'AND AssE55MESt(Tobe completed by Applicant/Bidder] '$!. ' : •-• r l. Z.. o ° t i z a " n 5 '4 - x. m -a a . - . S� For any questions answered No ; ri Action Plan for Compliance with a timeline must be documented in the ;* designated area below the question 'The timeline:for compliance withHIPAA related items.is 30 calendar r ;i days, PII related items is 90 calendar days i<�, * ` V, s i ` : +; . xr . nen . 3 '� t C aE. z ,r*x t o .: x al c7 res hfi 1 Written Policies•& Procedures Does Applicant/Bidder have?current written privacy and , Yes or No secu16y policies and procedure`s that at a!mmlm ilia µ a. Does Applicant/Bidder have current written privacy and security policies and a Yes procedures that identify Authorized Users and Authorized Purposes(as defined in the No DUA) relating to creation, receipt, maintenance, use, disclosure, access or transmission of HHS Confidential Information? Action Plan for Compliance with a Timeline: Compliance Date: b. Does Applicant/Bidder have current written privacy and security policies and t]; Yes procedures that require Applicant/Bidder and its Workforce to comply with the 0 No applicable provisions of HIPAA and other laws referenced in the DUA, relating to creation, receipt, maintenance, use, disclosure, access or transmission of HHS Confidential Information on behalf of an HHS agency? Action Plan for Compliance with a Timeline: Compliance Date: c. Does Applicant/Bidder have current written privacy and security policies and procedures r Yes that limit use or disclosure of HHS Confidential Information to the minimum that is No necessary to fulfill the Authorized Purposes? Action Plan for Compliance with a Timeline: Compliance Date: d. Does Applicant/Bidder have current written privacy and security policies and '9 Yes procedures that respond to an actual or suspected breach of HHS Confidential 0 No Information,to include at a minimum (if any responses are "No" check"No" for all three): i. Immediate breach notification to the HHS agency, regulatory authorities, and other required Individuals or Authorities, in accordance with Article 4 of the DUA; ii. Following a documented breach response plan, in accordance with the DUA and applicable law; & iii. Notifying Individuals and Reporting Authorities whose HHS Confidential Information has been breached, as directed by the HHS agency? CISO-001-NDQ(11/16)(V2.0) HHS Enterprise Data Use Agreement,Attachment 2: Page 3 of 17 SECURIry 'PRWAEN.INIIIALJNQUIRY(SPI) F I. _ pg / -1 Action Plan for Compliance with a Timeline: Compliance Date: e. Does Applicant/Bidder have current written privacy and security policies and procedures ® Yes that conduct annual workforce training and monitoring for and correction of any training delinquencies? 0 No Action Plan for Compliance with a Timeline: Compliance Date: f. Does Applicant/Bidder have current written privacy and security policies and ® Yes procedures that permit or deny individual rights of access,and amendment © No or correction,when appropriate? Action Plan for Compliance with a Timeline: Compliance Date: g. Does Applicant/Bidder have current written privacy and security policies and procedures ® Yes that permit only Authorized Users with up-to-date privacy and security training, and 0 No with a reasonable and demonstrable need to use, disclose, create, receive, maintain, access or transmit the HHS Confidential Information,to carry out an obligation under the DUA for an Authorized Purpose, unless otherwise approved in writing by an HHS agency? Action Plan for Compliance with a Timeline: Compliance Date: i h. Does Applicant/Bidder have current written privacy and security policies and procedures ® Yes that establish, implement and maintain proof of appropriate sanctions against any No Workforce or Subcontractors who fail to comply with an Authorized Purpose or who is not an Authorized User, and used or disclosed HHS Confidential Information in violation of the DUA,the Base Contract or applicable law? Action Plan for Compliance with a Timeline: Compliance Date: i. Does Applicant/Bidder have current written privacy and security policies and ® Yes procedures that require updates to policies, procedures and plans following major 0 No changes with use or disclosure of HH5 Confidential Information within 60 days of identification of a need for update? Action Plan for Compliance with a Timeline: Compliance Date: CISO-001-NDQ(11/16)(V2.0) HHS Enterprise Data Use Agreement,Attachment 2: Page 4 of 17 SECURITY AND PRIVACY INITIAL INQUIRY(SP)) 1 va. _ a-7V Pg. 1 j. Does Applicant/Bidder have current written privacy and security policies and ® Yes procedures that restrict permissions or attempts to re-identify or further identify © No de-identified HHS Confidential Information, or attempt to contact any Individuals whose records are contained in the HHS Confidential Information, except for an Authorized Purpose,without express written authorization from an HHS agency or as expressly permitted by the Base Contract? Action Plan for Compliance with a Timeline: Compliance Date: k. If Applicant/Bidder intends to use, disclose, create, maintain, store or transmit HI-IS fe. Yes Confidential Information outside of the United States of America, will Applicant/Bidder © No obtain the express prior written permission from the HHS agency and comply with the HI-IS agency conditions for safeguarding offshore HHS Confidential Information? Action Plan for Compliance with a Timeline: Compliance Date: I, Does Applicant/Bidder have current written privacy and security policies and procedures f;) Yes that require cooperation with HHS agencies' or federal regulatory inspections, audits or © No investigations related to compliance with the DUA or applicable law? Action Plan for Compliance with a Timeline: Compliance Date: m. Does Applicant/Bidder have current written privacy and security policies and -0 Yes procedures that require appropriate standards and methods to destroy or dispose of 0 No HHS Confidential Information? Action Plan for Compliance with a Timeline: Compliance Date: n. Does Applicant/Bidder have current written privacy and security policies and procedures g Yes that prohibit disclosure of Applicant/Bidder's work product done on behalf of HHS 0 No pursuant to the DUA, or to publish HHS Confidential Information without express prior approval of the HHS agency? Action Plan for Compliance with a Timeline: Compliance Date: 2. Does Applicant/Bidder have a current Workforce training program? 'ed., Yes Training of Workforce must occur at least once every year,and within 30 days of date of hiring a new Q No Workforce member who will handle HHS Confidential Information.Training must include:(1)privacy and security policies,procedures,plans and applicable requirements for handling HHS Confidential Information, (2) a requirement to complete training before access is given to HHS Confidential Information,and(3)written proof of training and a procedure for monitoring timely completion of training. • CISO-001-NDQ(11/16)(V2.0) HHS Enterprise Data Use Agreement,Attachment 2: Page S of 17 SECU R81![OGV INITIAI INQUIRY(SPS_ l Action Plan for Compliance with a Timeline: Compliance Date: 3. Does Applicant/Bidder have Privacy Safeguards to protect HHS Confidential Information in ® Yes oral, paper and/or electronic form? 0 No "Privacy Safeguards"means protection of HHS Confidential Information by establishing,implementing and maintaining required Administrative,Physical and Technical policies, procedures,processes and controls, required by the DUA,HIPAA(45 CFR 164.530),Social Security Administration, Medicaid and laws,rules or regulations,as applicable.Administrative safeguards include administrative protections,policies and procedures for matters such as training, provision of access,termination,and review of safeguards,incident management,disaster recovery plans,and contract provisions.Technical safeguards include technical protections,policies and procedures,such as passwords,logging, emergencies,how paper is faxed or mailed, and electronic protections such as encryption of data.Physical safeguards include physical protections,policies and procedures,such as locks,keys,physical access,physical storage and trash. Action Plan for Compliance with a Timeline: Compliance Date: 4. Does Applicant/Bidder and all subcontractors (if applicable) maintain a current list of (°) Yes Authorized Users who have access to HHS Confidential Information, whether oral, written 0 No or electronic? Action Plan for Compliance with a Timeline: Compliance Date: 5. Does Applicant/Bidder and all subcontractors (if applicable) monitor for and remove 9 Yes terminated employees or those no longer authorized to handle HHS Confidential 0 No Information from the list of Authorized Users? Action Plan for Compliance with a Timeline: Compliance Date: • CISO-001-NDQ(11/16)(V2.0) HHS Enterprise Data Use Agreement,Attachment 2: Page 6 of 17 SECURITY AND PRIVACY INITIAL INQUIRY(SPI) VOL 75/ _ Pg Section C:SECURITY RISK ANALYSIS AND ASSESSMENT(to be cothpleted.by""ApplicaritiBidder) ' This section is about youreile'i onic system If yourrbusiness DOES NOT,store,access, or, , r�«No ElectronicFzf' ', Y h.. H : tai 6 :� i t S :. r., v t 2,1 transmit HHS Confidential Informationan electronic systems (e g; laptop, personal use Systems . =computer, mobileldevice,database,server,etc )select the box to the an11;YES wilt" _ ,O ? t new K4+r e as ',:ft's +, � :, P t� � � ? c'^- be entered for allguestions in this section For any questions.answered ,'.Nor, an`ActionSPlan for Compliance wlth,a timelme`<must be documented in the designated area b /low the qu,etstion The timeline}for compliance with HIPPAA related Items is 30 calendarhdays, P11 related items is 90 calendar days surzf! 5. Does each member of Applicant/Bidder's Workforce who will use, disclose, create, receive, Yes transmit or maintain HHS Confidential Information have a unique user name (account) and o No private password? Action Plan for Compliance with a Timeline: - Compliance Date: 6. Does Applicant/Bidder lock the password after a certain number of failed attempts and ® Yes after 15 minutes of user inactivity in all computing devices that access or store HHS o No Confidential Information? Action Plan for Compliance with a Timeline: Compliance Date: 7. Does Applicant/Bidder secure, manage and encrypt remote access (including wireless ® Yes access)to computer systems containing HHS Confidential Information? (e.g., a formal ® No process exists for granting access and validating the need for users to remotely access HHS Confidential Information,and remote access is limited to Authorized Users). Encryption is required for all HHS Confidential Information. Additionally,FIPS 140-2 compliant encryption is required for Health Insurance Portability and Accountability Act(HIPAA)data,Criminal Justice Information Services(015)data,Internal Revenue Service Federal Tax Information(IRS PTI)data,and Centers for Medicare&Medicaid Services(CMS)data. For more information regarding FIPS 140-2 encryption products,please refer to: http://csrc.nist.gov/groups/STM/cm vp/documents/140-1/140vol-all.htm Action Plan for Compliance with a Timeline: Compliance Date: 8. Does Applicant/Bidder implement computer security configurations or settings for all ® Yes computers and systems that access or store HHS Confidential Information? (e.g., Q No non-essential features or services have been removed or disabled to reduce the threat of breach and to limit exploitation opportunities for hackers or intruders, etc.) Action Plan for Compliance with a Timeline: Comoliance Date: 9. Does Applicant/Bidder secure physical access to computer, paper, or other systems ® Yes containing HHS Confidential Information from unauthorized personnel and theft(e.g., door 0 No locks,cable locks, laptops are stored in the trunk of the car instead of the passenger area, etc.)? Action Plan for Compliance with a Timeline: Compliance Date: CISO-001-NDC)(11/16)(V2.0) HHS Enterprise Data Use Agreement,Attachment 2: Page 8 of 17 SECUR ' • .■ •• • • -- - - • Vol. 7 X _ pg. / / • • • 10. Does Applicant/Bidder use encryption products to protect HHS Confidential Information ® Yes that is transmitted over a public network(e.g.,the Internet,WiFi, etc.). 0 No If yes,upon request must provide evidence such as a screen shot or a system report. Encryption is required for all HHS Confidential Information. Additionally,FIPS 140-2 compliant encryption is required for Health Insurance Portability and Accountability Act(HIFAA)data,Criminal Justice Information Services(015)data,Internal Revenue Service Federal Tax Information(IRS FTI)data,and Centers for Medicare&Medicaid Services(CMS)data. For more information regarding FIP5 140-2 encryption products,please refer to: http://csrc.nist.pov/groups/STM/cmvp/documents/140-1/140vaI-all.htm Action Plan for Compliance with a Timeline: Compliance Date: 11. Does Applicant/Bidder use encryption products to protect HHS Confidential Information ® Yes stored on end user devices(e.g., laptops, USBs,tablets, smartphones, external hard drives, Q No desktops,etc.)? If yes, upon request must provide evidence such as a screen shot or a system report. Encryption is required for all HHS Confidential Information. Additionally,FIRS 140-2 compliant encryption is required for Health Insurance Portability and Accountability Act(HIPAA)data,Criminal Justice Information Services(015)data,Internal Revenue Service Federal Tax Information(IRS FTI)data,and Centers for Medicare&Medicaid Services(CMS)data. For more information regarding FIPS 140-2 encryption products,please refer to: http://csrc.nist.gov/croups/STM/cmvp/documents/140-1/140val-oll.htm Action Plan for Compliance with a Timeline: Compliance Date: 12. Does Applicant/Bidder require Workforce members to formally acknowledge rules ® Yes outlining their responsibilities for protecting HHS Confidential Information and associated 0 No systems containing HHS Confidential Information before their access is provided? Action Plan for Compliance with a Timeline: Compliance Date: 13. Is Applicant/Bidder willing to perform or submit to a criminal background check on ® Yes Authorized Users? 0 No Action Plan for Compliance with a Timeline: Compliance Date: 14. Does Applicant/Bidder prohibit the access, creation, disclosure, reception, transmission, %v Yes maintenance, and storage of HHS Confidential Information with a subcontractor(e.g. cloud © No services, social media, etc.) unless HHS has approved the subcontractor agreement which must include compliance and liability clauses with the same requirements as the Applicant/Bidder? Action Plan for Compliance with a Timeline: Compliance Date: CISO-001-NDQ(11/16)(V2.0) HHS Enterprise Data Use Agreement,Attachment 2: Page 9 of 17 SEC . _ . - •UIRY(SPI) vet: : . Pg. /3/ 15. Does Applicant/Bidder keep current on security updates/patches(including firmware, ® Yes software and applications)for computing systems that use, disclose, access, create, © No transmit, maintain or store HHS Confidential Information? Action Plan for Compliance with a Timeline: Compliance Date: 16. Do Applicant/Bidder's computing systems that use, disclose, access, create, transmit, ® Yes maintain or store HHS Confidential Information contain up-to-date anti-malware and o No antivirus protection? Action Plan for Compliance with a Timeline: Compliance Date: 17. Does the Applicant/Bidder review system security logs on computing systems that access ® Yes or store HHS Confidential Information for abnormal activity or security concerns on a o No regular basis? Action Plan for Compliance with a Timeline: Compliance Date: 18. Notwithstanding records retention requirements, does Applicant/Bidder's disposal ® Yes processes for HHS Confidential Information ensure that HHS Confidential Information is o No destroyed so that it is unreadable or undecipherable? Action Plan for Compliance with a Timeline: - Compliance Date: Section D:Signature and Submission ,-`,' •'.. . . '' ' L" a. x. Y Y . is Sic c �g.'s R $. ry x cr ' `( e WW 7 . x..Z ,:s_._ Please srgn fhe form drgrtally ¢pass{ble �If you can't provide a handwrrtten srgn`atare 1 hl,s 1. I certify that all of the information provided in this form is truthful and correct to the best of my knowledge. If I learn that y s ch information was not correct, I agree to notify HHS of this immediately. 2.Signat e j 3.Title 4. Date: f3intS CcuM3udg� ��5 ►� To submit the comple d,signed form: • Email the form as an attachment to the appropriate HHS Contract Manager. C1SO-001-NDQ(11/16)(V2.0) HHS Enterprise Data Use Agreement,Attachment 2: Page 10 of 17 SECURI Alrp uRv4.5P11 va, 02. 2$ Pg. /3z I Section E:To Be Completed by HHS Agency Staff: t •gency(s): Requesting Department(s): HHSC:D DADS:0 DFPS:D DSHS:D Legal Entity Tax Identification Number(TIN) (Last four Only): PO/Contract(s)#: ' 1 L414g`.Lt i gift 4"7 4' ".;jr.�(x`r•aT7 5r Sw tr Kg& Contract Manager: Contract Manager Email Address: Contract Manager Telephone#: CISO-001-NDC)(11/16)(V2.0) HHS Enterprise Data Use Agreement,Attachment 2: Page 11 of 17 tURI IYANU PRIVACY INITIAL IIVLZUIRY prl) va. '�,/7 ti P9. /33 I • INSTRUCTIONS FOR COMPLETING THE SECURITY AND PRIVACY INITIAL INQUIRY(SPI) Attachment 2 to the HHS Enterprise Data Use Agreement Below are instructions for Applicants, Bidders and Contractors for Health and Human Services requiring the Attachment 2, Security and Privacy Inquiry(SPI)to the Data Use Agreement(DUA). Instruction item numbers below correspond to sections on the SPI form. If you are a bidder for a new procurement/contract,in order to participate in the bidding process,you must have corrected any"No"responses in sections B and C prior to the contract award date.If you are an applicant for an open enrollment,you must have corrected any"No"answers in Sections B and C below prior to performing any work on behalf of any HHS agency.For existing contracts or renewals with"No" responses,there must be an action plan for remediation of Section B and C within 30 calendar days for HIPAA related contracts and 90 days for others from the date the form is signed SECTION A. APPLICANT/BIDDER INFORMATION Item#1. Only contractors that access, transmit,store, and/or maintain Confidential Information will complete and email this form as an attachment to the appropriate HHS Contract Manager. Item#2.Entity or Applicant/Bidder Legal Name. Provide the legal name of the business(the name used for legal purposes, like filing a federal or state tax form on behalf of the business, and is nota trade or assumed named "dba"),the legal tax identification number(last four numbers only)of the entity or applicant/bidder, the address of the corporate or main branch of the business,the telephone number where the business can be contacted regarding questions related to the information on this form and the website of the business,if a website exists. Item#3.Number of Employees,at all locations,in Applicant/Bidder's workforce.Provide the total number of individuals, including volunteers,subcontractors, trainees, and other persons who work for the business.If you are the only employee,please answer"1." Item#4.Number of Subcontractors. Provide the total number of subcontractors working for the business.If you have none,please answer"0"zero. Item#5. Number of unduplicated individuals for whom Applicant/Bidder reasonably expects to handle HHS Confidential Information during one year. Select the radio button that corresponds with the number of clients/consumers for whom you expect to handle HHS Confidential Information during a year. Only count clients/consumers once, no matter how many direct services the client receives during a year. Item#5.Name of Information Technology Security Official and Name of Privacy Official forApplicant/Bidder.As with all other fields on the SRI,this is a required field. This may be the same person and the owner of the business if such person has the security and privacy knowledge that is required to implement the requirements of the DUA and respond to questions related to the SPI. In 4.A.provide the name, address, telephone number, and email address of the person whom you have designated to answer any security questions found in Section C and in 4.8. provide this information for the person whom you have designated as the person to answer any privacy questions found in Section B. The business may contract out for this expertise;however, designated individual(s)must have knowledge of the business's devices,systems and methods for use, disclosure, creation,receipt, transmission and maintenance of HHS Confidential Information and be willing to be the point of contact for privacy and security . questions. Item#6. Type(s)of HH5 Confidential Information the Entity or Applicant/Bidder Will Create, Receive,Maintain, Use,Disclose or Have Access to: Provide a complete listing of all HHS Confidential Information that the Contractor will create,receive, maintain, use, disclose or have access to. The DUA section Article 2, Definitions, defines HHS Confidential Information as: "Confidential Information"means any communication or record(whether oral, written, electronically stored or transmitted, or in any other form)provided to or made available to CONTRACTOR or that CONTRACTOR may create, receive, maintain, use, disclose or have access to on behalf of HHS that consists of or includes any or all of the following: (1)Client Information; (2)Protected Health Information in any farm including without limitation, Electronic Protected Health Information or Unsecured Protected Health Information; (3)Sensitive Personal Information defined by Texas Business and Commerce Code Ch. 521; CISO-001-NDQ(11 Mb)(V2.0) HHS Enterprise Data Use Agreement,Attachment 2: Page 12 of 17 SE : I .w •; • . • . II'IRV(Sol) _. Vol. 27 ci Pg. /,3 / (4)Federal Tax Information; (5)Personally Identifiable Information; (6)Social Security Administration Data, including, without limitation,Medicaid information; (7)All privileged work product; (8)All information designated as confidential under the constitution and laws of the State of Texas and of the United States, including the Texas Health&Safety Code and the Texas Public Information Act, Texas Government Code, Chapter 552. Definitions for the following types of confidential information can be found the following sites: • Health Insurance Portability and Accountability Act(HIPAA)-http://www.hhs.gov/hipaa/index.html •Criminal ustice Information Services(CJIS)-https://www.fbi.gov/services/cjis/cjis-security-policy-resource-center •Internal Revenue Service Federal Tax Information(IRS FTI)-https://www.irs.gov/pub/irs-pdf/p1075.pdf • Centers for Medicare&Medicaid Services(CMS)-https://www.cros.gov/Regulations-and-Guidance/Regulations-and- Guidance.html •Social Security Administration(SSA)-httos://www.ssa.qov/requlations/ •Personally Identifiable Information(P11)-http://csrc.nist.clov/publications/nistpubs/800-122/sp800-122.pdf item#7.Number of Storage devices for HHS Confidential Information. The total number of devices is automatically calculated by exiting the fields in lines a-d. Use the<Tab>key when exiting the field to prompt calculation, if it doesn't otherwise sum correctly. • Item 7a.Devices.Provide the number of personal user computers,devices, and drives(including mobile devices,laptops, USB drives, and external drives)on which your business stores or will stare HHS Confidential Information. • Item 7b.Servers.Provide the number of servers not housed in a data center or"in the cloud,"on which HHS Confidential Information is stored or will be stored.A server is a dedicated computer that provides data or services to other computers. It may provide services or data to systems on a local area network(LAN)or a wide area network(WAN)over the Internet.If none,answer"0"(zero). • Item 7c.Cloud Services.Provide the number of cloud services to which HHS Confidential Information is stored. Cloud Services involve using a network of remote servers hosted on the Internet to store, manage,and process data,rather than on a local server or a personal computer. If none, answer"0"(zero.) • Item 7d.Data Centers. Provide the number of data centers in which you store HHS Confidential Information.A Data Center is a centralized repository,either physical or virtual,for the storage, management, and dissemination of data and information organized around a particular body of knowledge or pertaining to a particular business.If none, answer"0"(zero). Item#8. Number of unduplicated individuals for whom Applicant/Bidder reasonably expects to handle Confidential Information during one year.Select the radio button that corresponds with the number of clients/consumers for whom you expect to handle Confidential Information during a year. Only count clients/consumers once, no matter how many direct services the client receives during a year. Item#9.HIPAA Business Associate Agreement. • Item#9a.Answer"yes"if your business will use, disclose,create, receive, transmit or store information relating to a client/consumer's healthcare on behalf of the Department of State Health Service, the Department of Disability and Aging Services,or the Health and Human Services commission for treatment payment, or operation of Medicaid or Medicaid clients. If your contract does not include HIPAA covered information, respond"no." • Item#91).Answer"yes"if your business has a notice of privacy practices(a document that explains how you protect and use a client/consumer's healthcare information)displayed either on a website(if one exists for your business)or in your place of business(if that location is open to clients/consumers or the public). If your contract does not include HIPAA covered information,respond"no." Item#10.Subcontractors. If your business responded "0"to question 3(number of subcontractors),Answer"no"to Items 9a and 9b to indicate not applicable. • Item#10a.Answer"yes"if your business requires that all subcontractors sign Attachment 1 of the DUA. • Item#10b.Answer"yes"if your business obtains HHS approval before permitting subcontractors to handle HHS Confidential Information on your business's behalf Item#11. Optional Insurance.Answer"yes"if applicant has optional insurance in place to provide coverage for a Breach or any HHS Enter rise Data Use A reement,Attachment 2: Page 13 of 17 CISO-001-NDQ(11/16)(V2.0) SECUR -AmDA°1��^r3'itiiTini Ntrnuev(SPIT Ivor. 02 7 y Pg. /33 other situations listed in this question. If you do not have this optional coverage, answer"no." SECTION B. PRIVACY RISK ANALYSIS AND ASSESSMENT Reasonable and appropriate written Privacy and Security policies and procedures are required,even for sole proprietors who are the only employee,to demonstrate how your business will safeguard HHS Confidential Information and respond in the event of a Breach of HHS Confidential Information.To ensure that your business is prepared,all of the items below must be addressed in your written Privacy and Security policies and procedures. For any question Section B or Section C question that is answered "no",an explanation of how compliance will be corrected and a date when compliance will be complete in the designated areas below the question. Item#1.Answer"yes" if you have written policies in place for each of the areas (a-o). • Item#1a.Answer"yes" if your business has written policies and procedures that identify everyone, including subcontractors,who are authorized to use HHS Confidential Information.The policies and procedures should also identify the reason why these Authorized Users need to access the HHS Confidential Information and this reason must align with the Authorized Purpose described in the Scope of Work or description of services in the Base Contract with the HHS agency. • Item#16.Answer"yes" if your business has written policies and procedures that require your employees(including yourself),your volunteers,your trainees, and any other persons whose work you direct,to comply with the requirements of HIPAA, if applicable,and other confidentiality laws as they relate to your handling of HHS Confidential Information. Refer to the laws and rules that apply, including those referenced in the DUA and Scope of Work or description of services in the Base Contract. • Item#1c.Answer"yes"if your business has written policies and procedures that limit the HHS Confidential Information you disclose to the minimum necessary for your workforce and subcontractors(if applicable)to perform the obligations described in the Scope of Work or service description in the Base Contract. (e.g.,if a client/consumer's Social Security Number is not required for a workforce member to perform the obligations described in the Scope of Work or service description in the Base Contract,then the Social Security Number will not be given to them.) If you are the only employee for your business,policies and procedures must not include a request for,or use of,HHS Confidential Information that is not required for performance of the services. • Item#1d.Answer"yes"if your business has written policies and procedures that explain how your business would respond to an actual or a suspected breach of HHS Confidential Information.The written policies and procedures, at a minimum, must include the three items below. If any response to the three items below are no, answer"no." O Item#1di.Answer"yes" if your business has written policies and procedures that require your business to immediately notify HHS,the HHS Agency, regulatory authorities,or other required Individuals or Authorities of a Breach as described in Article 4,Section 4 of the DUA. Refer to Article 4, Section 4.01: Initial Notice of Breach must be provided in accordance with HHS and DUA requirements with as much information as possible about the Event/Breach and a name and contact who will serve as the single point of contact with HI-IS both on and off business hours. Time frames related to Initial Notice include: • within one hour of Discovery of an Event or Breach of Federal Tax Information,Social Security Administration Data, or Medicaid Client Information • within 24 hours of all other types of HHS Confidential Information 48-hour Formal Notice must be provided no later than 48 hours after Discovery for protected health information,sensitive personal information or other non- public information and must include applicable information as referenced in Section 4.01 (C)2.of the DUA. O Item#1dii.Answer yes, if.your business has written policies and procedures require you to have and follow a written breach response plan as described in Article 4 Section 4.02 of the DUA. o Item#ldiii.Answer"yes", if your business has written policies and procedures require you to notify Reporting Authorities and Individuals whose HH5 Confidential Information has been breached as described in Article 4 Section 4.03 of the DUA. • Item#1e.Answer"yes", if your business has written policies and procedures requiring annual training of your entire workforce on matters related to confidentiality,privacy, and security, stressing the importance of promptly reporting any HHS Enterprise rise Data Use Agreement,Attachment 2: CISO-001-NDO(11(16)(V2.0) P g Page 14 of 17 SEC , -.^. -PRI C111"JITIALINQUIRY(SPI) _2:24 Pg. /3e ` Event or Breach,outlines the process that you will use to require attendance and track completion for employees who failed to complete annual training. • Item#1f.Answer"yes", if your business has written policies and procedures requiring you to allow individuals (clients/consumers)to access their individual record of HHS Confidential Information,and allow them to amend or correct that information, if applicable. • Item#1g. Answer"yes",if your business has written policies and procedures restricting access to HHS Confidential Information to only persons who have been authorized and trained on how to handle HHS Confidential Information • Item#1h.Answer"yes", if your business has written policies and procedures requiring sanctioning of any subcontractor, employee,trainee,volunteer,or anyone whose work you direct when they have accessed HHS Confidential Information but are not authorized to do so,and that you have a method of proving that you have sanctioned such an individuals. If you are the only employee,you must demonstrate how you will document the noncompliance,update policies and procedures if needed,and seek additional training or education to prevent future occurrences. • Item#11.Answer"yes", if your business has written policies and procedures requiring you to update your policies within 60 days after you have made changes to how you use or disclose HHS Confidential Information. • Item#1j.Answer"yes" if your business has written policies and procedures requiring you to restrict attempts to take de- identified data and re-identify it or restrict any subcontractor,employee,trainee, volunteer,or anyone whose work you direct,from contacting any individuals for whom you have HHS Confidential Information except to perform obligations under the contract, or with written permission from NHS. • Item#1k.Answer"yes" if your business has written policies and procedures prohibiting you from using,disclosing, creating, maintaining,storing or transmitting HHS Confidential Information outside of the United States. • Item#11.Answer"yes", if your business has written policies and procedures requiring your business to cooperate with HHS agencies or federal regulatory entities for inspections,audits,or investigations related to compliance with the DUA or applicable law. • Item#1m.Answer"yes"if your business has written policies and procedures requiring your business to use appropriate standards and methods to destroy or dispose of HHS Confidential Information. Policies and procedures should comply with HHS requirements for retention of records and methods of disposal. • Item#1n.Answer"yes"if your business has written policies and procedures prohibiting the publication of the work you created or performed on behalf of HHS pursuant to the DUA, or other HHS Confidential Information,without express prior written approval of the HHS agency. Item#2.Answer"yes" if your business has a current training program that meets the requirements specified in the SPI for you,your employees,your subcontractors,your volunteers,your trainees, and any other persons under you direct supervision. Item#3.Answer"yes" if your business has privacy safeguards to protect HHS Confidential Information as described in the SPI. Item#4.Answer"yes" if your business maintains current lists of persons in your workforce, including subcontractors (if applicable),who are authorized to access HHS Confidential Information. If you are the only person with access to HHS Confidential Information, please answer"yes." Item#5.Answer"yes",if your business and subcontractors(if applicable) monitor for and remove from the list of Authorized Users, members of the workforce who are terminated or are no longer authorized to handle HHS Confidential Information. If you are the only one with access to HHS Confidential Information, please answer"yes". SECTION C. SECURITY RISK ANALYSIS AND ASSESSMENT This section is about your electronic systems. If you DO NOT store HHS Confidential Information in electronic systems (e.g., laptop, personal computer, mobile device,database,server, etc.), select the"No Electronic Systems" box and respond "yes"for all questions in this section. Item#1.Answer"yes" if your business does not"offshore" or use, disclose, create, receive,transmit or maintain HHS Confidential Information outside of the United States. If you are not certain,contact your provider of technology services (application,cloud,data center, network,etc.) and request confirmation that they do not off-shore their data. CISO-001-NDQ(11/16)(V2.0) HHS Enterprise Data Use Agreement,Attachment 2: Page 15 o'17 SECU' • . • •: I a L• : (SP11� va. <27 Pg. /,37 Item#2.Answer"yes"if your business uses a person or company who is knowledgeable in IT security to maintain or oversee the configurations of your business's computing systems and devices. You may be that person,or you may hire someone who can provide that service for you. Item#3.Answer"yes"if your business monitors and manages access to HHS Confidential Information (i.e., reviews systems to ensure that access is limited to Authorized Users; has formal processes for granting,validating,and reviews the need for remote access to Authorized Users to HHS Confidential Information, etc.). If you are the only employee, answer"yes"if you have implemented a process to periodically evaluate the need for accessing HHS Confidential Information to fulfill your Authorized Purposes. Item#4. Answer"yes" if your business has implemented a system for changing the password a system initially assigns to the user(also known as the default password), and requires users to change their passwords at least every 90 days,and prohibits the creation of weak passwords for all computer systems that access or store HHS Confidential Information (e.g., a strong password has a minimum of 8 characters with a combination of uppercase, lowercase,special characters,and numbers,where possible). If your business uses a Microsoft Windows system, refer to the Microsoft website on how to do this,see example: http://windows.microsoft.com/en-us/windows/change-password-policy-settings#1TC=windows-7 Item#5.Answer"yes" if your business assigns a unique user name and private password to each of your employees,your subcontractors,your volunteers,your trainees and any other persons under your direct control who will use,disclose, create,receive,transmit or maintain HHS Confidential Information. Item#6.Answer"yes" if your business locks the access after a certain number of failed attempts to login and after 15 minutes of user inactivity on all computing devices that access or store H H S Confidential Information. If your business uses a Microsoft Windows system, refer to the Microsoft website on how to do this,see example: http://windows.m icrosoft.com/en-u s/windows/ch a nge-passwo rd-policy-settings#1TC=windows-7 Item#7.Answer"yes", if your business secures, manages, and encrypts remote access,such as:using Virtual Private Network(VPN)software on your home computer to access HHS Confidential Information that resides on a computer system at a business location or, if you use wireless, ensuring that the wireless is secured using a password code. If you do not access systems remotely or over wireless,answer"yes." Item#8.Answer "yes" if your business updates the computer security settings for all your computers and electronic systems that access or store HHS Confidential Information to prevent hacking or breaches(e.g., non-essential features or services have been removed or disabled to reduce the threat of breach and to limit opportunities for hackers or intruders to access your system). For example, Microsoft's Windows security checklist: http://windows.m icrosoft.co m/e n-us/wi ndows7/Secu rity-checkl ist-for-Windows-7 Item#9.Answer"yes" if your business secures physical access to computer, paper,or other systems containing HHS Confidential Information from unauthorized personnel and theft(e.g.,door locks,cable locks, laptops are stored in the trunk of the car instead of the passenger area,etc.). If you are the only employee and use these practices for your business, answer"yes." Item#10. Answer"yes" if your business uses encryption products to protect HHS Confidential Information that is transmitted over a public network(e.g.,the Internet, WIFI,etc.) or that is stored on a computer system that is physically or electronically accessible to the public(FIPS 140-2 compliant encryption is required for Health Insurance Portability and Accountability Act (HIPAA)data,Criminal Justice Information Services(CJIS) data, Internal Revenue Service Federal Tax Information (IRS FTI)data, and Centers for Medicare& Medicaid Services (CMS) data.) For more information regarding FIPS 140-2 encryption products, please refer to: http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140val-all.htm). Item#11.Answer"yes" if your business stores HHS Confidential Information on encrypted end-user electronic devices (e.g., laptops, USBs,tablets,smartphones, external hard drives,desktops,etc.)and can produce evidence of the encryption, such as, a screen shot or a system report(FIPS 140-2 encryption is required for Health Insurance Portability and Accountability Act (HIPAA)data, Criminal Justice Information Services (0115)data, Internal Revenue Service Federal Tax Information (IRS FTI)data, and Centers for Medicare& Medicaid Services (CMS)data.) . For more information regarding FIPS 140-2 compliant encryption products, please refer to: http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140val-all.htm). If you do not utilize end- CISO-001-NDO(11/16)(V2.0) HHS Enterprise Data Use Agreement,Attachment 2: Page 16 of 17 SECURI � • i• " • ' L • c SPI VaL. P /g. _ 3 ' user electronic devices for storing HHS Confidential Information, answer"yes." Item#12.Answer"yes" if your business requires employees,volunteers,trainees and other workforce members to sign a document that clearly outlines their responsibilities for protecting HHS Confidential Information and associated systems containing HHS Confidential Information before they can obtain access. If you are the only employee answer"yes"if you have signed or are willing to sign the DUA, acknowledging your adherence to requirements and responsibilities. Item#13. Answer "yes" if your business is willing to perform a criminal background check on employees,subcontractors, volunteers, or trainees who access HHS Confidential Information. If you are the only employee, answer "yes" if you are willing to submit to a background check. Item#14.Answer"yes"if your business prohibits the access, creation, disclosure, reception,transmission, maintenance,and storage of HHS Confidential Information on Cloud Services or social media sites if you use such services or sites,and there is an HHS approved subcontractor agreement that includes compliance and liability clauses with the same requirements as the Applicant/Bidder. If you do not utilize Cloud Services or media sites for storing HHS Confidential Information, answer"yes." Item#15. Answer"yes" if your business keeps current on security updates/patches(including firmware, software and applications)for computing systems that use, disclose, access,create,transmit, maintain or store HHS Confidential Information. If you use a Microsoft Windows system, refer to the Microsoft website on how to ensure your system is automatically updating,see example: http://windows.microsoft.com/en-US/windows?/products/features/windows-update Item#16.Answer"yes" if your business's computing systems that use, disclose, access, create,transmit, maintain or store HHS Confidential Information contain up-to-date anti-malware and antivirus protection. If you use a Microsoft Windows system,refer to the Microsoft website on how to ensure your system is automatically updating,see example: http://windows.microsoft.com/en-US/windows7/products/features/windows-update Item #17. Answer "yes" if your business reviews system security logs on computing systems that access or store HHS Confidential Information for abnormal activity or security concerns on a regular basis. If you use a Microsoft Windows system, refer to the Microsoft website for ensuring your system is logging security events,see example: http://windows.microsoft.com/en-us/windows/what-information-event-logs-event-viewer#1TC=windows-7 Item#18. Answer"yes" if your business disposal processes for HHS Confidential Information ensures that HHS Confidential Information is destroyed so that it is unreadable or undecipherable. Simply deleting data or formatting the hard drive is not enough;ensure you use products that perform a secure disk wipe. Please see NIST SP 800-88 R1, Guidelines for Media Sanitization and the applicable laws and regulations for the information type for further guidance. SECTION D. SIGNATURE AND SUBMISSION Click on the signature area to digitally sign the document. Email the form as an attachment to the appropriate HHS Contract Manager. CISO-001-NDQ(11/16)(V2.0) HHS Enterprise Data Use Agreement,Attachment 2: Page 17 of 17 SECURIT•`.ANDiPRWAc-' lN1TlAL.lNQUIRY.(SRI)—.--.-__, � V01. _ _7 x'9. 75- - � RFP # 18-089 Video Surveillance Upgrade for BCDC Electra Link Argyle Pricing/Total Cost for Services $ 394,554.71 $ 599,964.00 Point for Cost 40 40 26.31 Install Plan/8 of Days for completion of Project 65 210 Points for Time 20 20 6.19047619 Qualifications/Experience 30 20 30 References 10 9.4415 6.9285 Total 100 .a :t°� 89nFAZTf 69 .- ..«. '' Recommended Award: Ekc & Liri K Ap• ov id : Com,i issioner's Court on this 5 day of �� {�1� 2018 • I'. �r holding the position of CQU.I�j, v1tdc t mrrc��Rlq �'na on ektic oc Vol. ,27V Pg. /5/0 SUNGARD PENTAMATION PAGE NUMBER: 1 DATE: 05/31/2018 BRAZOS COUNTY, TX BJOURN11 • TIME: 11:55:05 BATCH JOURNAL ENTRY EDIT LIST CONTROL NUMBER J E NUMBER DESCRIPTION PERIOD/YR STATUS RECORD FUND DIV/FUND ACCOUNT PROJECT ACCOUNT ITEM DESCRIPTION DEBIT AMOUNT CREDIT AMOUNT 05.31.18 050124 TRVL REIMS - M REYES 8/18 COMPLETE 347238 0100 30401100 61801000 SEGUIN 5.14-17.18 441.27 347239 0100 0100 20424500 SEGUIN 5.14-17.18 441.27 TOTAL JOURNAL ENTRY 441.27 441.27 05.31.18 050125 TRVL REIMS - C PATIN 8/18 COMPLETE 347240 0100 16500100 61801000 TRVL REIMS - C PATIN 464.78 347241 0100 0100 20123230 TRVL REIMB - C PATIN 464.78 TOTAL JOURNAL ENTRY 464.78 464.78 05.31.18 050126 TRVL REIMS - K NACHL 8/18 COMPLETE 347242 0100 16500100 61801000 TRVL REIMB - K NACHL 90.00 347243 0100 0100 20123690 TRVL REIMB - K NACHL 90.00 TOTAL JOURNAL ENTRY 90.00 90.00 05.31.18 050127 TSF 0100>3500 BA#34. 8/18 COMPLETE 347244 0100 0100 91350000 TSF 0100>3500 BA#34. 13,000.00 347245 0100 0100 11005200 TSF 0100>3500 BA#34. 13,000.00 347246 3500 3500 11005200 TSF 0100>3500 BA#34. 13,000.00 347247 3500 3500 49028000 TSF 0100>3500 BA#34. 13,000.00 TOTAL JOURNAL ENTRY 26,000.00 26,000.00 0 05.31.18 050128 MAY18 UHRIP PY2 PAYM 8/18 COMPLETE 347248 1600 34000200 73501000 MAY18 UHRIP PY2 PAYM 799,672.52 347249 1600 34000200 73502000 MAY18 UHRIP PY2 PAYM 603,971.71 'V 347250 1600 34000200 73503000 MAY18 UHRIP PY2 PAYM 1,284,600.25 347251 1600 34000200 73504000 MAY18 UHRIP PY2 PAYM 295.87 - 347252 1600 1600 11005200 MAY18 UHRIP PY2 PAYM 2,688,540.35 TOTAL JOURNAL ENTRY 2,688,540.35 2,688,540.35 ITOTAL CONTROL NUMBER 2,715,536.40 2,715,536.40 i TOTAL REPORT 2,715,536.40 2,715,536.40 -3 f 1----" 1 1 Io BRAZOS COUNTY,TEXAS BUDGET AMENDMENT(S) FOR THE 2017-2018 BUDGET YEAR NO. 17/18 35.1—35.6 On this the 5th day of June 2018 at a regular meeting of the Commissioners' Court, the following members were present: A.Duane Peters, County Judge,Presiding B. Steve Aldrich,Commissioner,Precinct 1 C. Sammy Catalena, Commissioner,Precinct 2 D.Nancy Berry, Commissioner,Precinct 3 E.Irma Cauley,Commissioner,Precinct 4 F.Karen McQueen, County Clerk The following proceedings were held: THAT WHEREAS,on 5th day of June 2018 the Court heard and approved a budget amendment for the 2016-2017 budget year for Brazos County,Texas;and WHEREAS,expenditure is necessary due to the necessity to meet unusual and unforeseen conditions which could not be reasonably included in the original budget adopted 5 September 2017, the following amendment(s)to the original budget are hereby authorized,as described on the attached page(s). ADOPTED AND APPROVED this the 5th day of June 2018. 111E COMNIISSIONERS COURT OF BRAZOS COUNTY,TEXAS. B i . Ll ��� Duane Peters. 'ounty Judge Original: County Clerk's Office and Attached to the original budget VOL 1 / GY Pg. BRAZOS COUNTY,TEXAS BUDGET AMENDMENTS No.17/18.35.1 5/512018 FUND DEPARTMENT DIVISION CATEGORY DESCRIPTION Increase Decrease General Fund Information Technology I.T.Services Contractual Services 2,740.50 General Fund Information Technology I.T.Services Departmental Support 2,790.50 t Information Technology Reallocation of funds to the correct account to cover the cost TriTech Software RIS interface for Training System. ln�'ta� Q �r x. ^,a 7* ASt�t a .:� 4A .� 1 y,.� r S _ 4 f S7 i 4, 4Tl c M s +oil Deparlmen4:APPrsyal -'x�$ i' < Date a 'e}.fts{�s.*;j + #*e44:"'tett r7 d m, a". wrnnt IDate+r ,,�),-,�C'`, 5130/20t6j _ '.J. II S 1rRR 3:45,-;;;;11 loytC Uu..'� royal rvF$}% Da . 7eg521`-J ,w..,..,. . x„S . r,;' „t. 7r:;:., er•.sc =si m< -,.1 x".- - 3-t. FodA'cconnhn,.NlrPasEs.O¢'ly mss, ...'.,,5 .t:F$ ...__{.,Zn�s,..<..7`.n Kgs,d.`:..�. w„6...._a.r.=. < m�a.,...: "I;>=.,._h<_....:t-.,._` ..+.a;=i.3. ,cY,�6.a."i s - FUND DIV ACCT DR/CR ACCOUNT NAME Increase Decrease 0100 14000200 71020000 CR Computer Contracts 2,74050 0100 14000200 60211000 DR Software-No Tag 2,740.50 Vol. _ — Pg. / __3 BRAZOS COUNTY,TEXAS BUDGET AMENDMENTS No.17118.35.2 61512018 FUND DEPARTMENT _ DIVISION CATEGORY DESCRIPTION Increase Decrease General Fund Commissioners Court Contingency Departmental Support 2.250.00 General Fund Sheriff Administration _ Departmental Support 2,250.00 Commissioners'Court and Sheriff Administration Reallocation of funds to the correct account to cover the cost of DNA analysis for a cold case. L a .' '' Ij 1 j Vis, ...p._ .tom:Sii,M. g ,� r a.^r iva .,-s," : �,OePar4menf-tinea o s�z :;Data �'S ,! IDate:6ya: 'A't iv,'+x , y` 513012018, Jud �& 51§ iti s ' z.i *iipr F telarkac , rova� -sNIrsyOa e �a r ,S J rortmcouhting Purpases.on aan. tval`+ . a, •EAAx,,..uz i.. .via-r%.''derek;1, ;,'1Oi vs,' - '. .wa.,.? 't, -?«+re iffi FUND DIV ACCT DRfCR ACCOUNT NAME Increase Decrease 0100 11001500 61130000 CR Contingency 2,250.00 0100 28000100 60400000 DR 2,740.50 Vol ' 7(/ Pg. /I I € ,: BRAZOS COUNTY,TEXAS BUDGET AMENDMENTS No.17118.35.3 6/512018 FUND DEPARTMENT DIVISION CATEGORY DESCRIPTION Increase Decrease General Fund Commissioners'Court Non-Departmental Minor Acquisitions 590.96 General Fund Information Technology Minor Acquisitions 590.96 • Commissioners'Court and Information Technology Reallocation of funds to the correct account to purchase a replacement chair. /De" stn Datteo � f��s" . .�.; .,,�.-5/30f20181l r SRT f�,trv�r f4 $ 'S :: s tounty':ilutlgr p rR-oval.v nrk .�r<iD to `c�f 'P.�'`.J vi For;Aeco6114ns P.urpase5`.Ou1y1,< ,^.c"`.w''w'S.1."%+,L4.,..:,ierim.hf`te;-.$..sr4y7;r< ;�'+''d'�..k�arx .S .<. ...rm'.{ z' 4ra .r<:"'.?'cx "'*2.,v,sINlen: t S_ FUND DIV ACCT DR/CR ACCOUNT NAME Increase Decrease 0100 11000500 67342000 CR Furniture 590.96 0100 14000100 67342000 DR Furniture 590.96 r Vr�l. _621L___ Pg. /J`5T BRAZOS COUNTY,TEXAS BUDGET AMENDMENTS No.17/18-35.4 61512018 FUND DEPARTMENT DIVISION CATEGORY DESCRIPTION [ Increase Decrease General Fund Juvenile Services 7YC Parole Contractual Services 2,47828 General Fund Juvenile Services Detention Minor Acquisitions 2,978.28 Juvenile Services — Reallocation of funds to the collect account to purchase four replacement televisions in the Juvenile Detention Center. La,w. .+.vi4t,ki: 'sz ,tt x'k`r✓.': xrtv'a` .,RR t,Deparmerit Appoval i,hic avw'aTMJ..i .';'Date ,*8•" >: td wl- 3.r' Jd nnm' Date'}.r'..`?t e4st ; It gv St Ol2pMI Vis® � G NIrP`�J lf!1 vlowl , : n f .T'.1,";.. ,'* ar 0Si - ,..., For Accounhn?Prrrposes:OalY 1,,.+ `as'p 4 .."S.:id':;.' C^r^.'.i5 7u..ttix.. i�la.t;Z‘,fAn 3 S, JW7SeV_;tn"£ .;"w'" L. »Ya,.1, w ksm. FUND DIV ACCT DR/CR _ ACCOUNT NAME Increase Decrease 0100 31010000 71500000 CR Rental Equipment 2,478.28 0100 31000200 67281000 DR Equipment-Electronic 2,478.28 H± f Pg. /e7/6 BRAZOS COUNTY,TEXAS BUDGET AMENDMENTS No.17118-35.5 61512018 FUND DEPARTMENT I DIVISION I CATEGORY DESCRIPTION Increase Decrease General Fund Commissioners'Coed Non•Departmental I Repairs&Maine 16,600.00 General Fund Facilities Services Repairs&Maint 16,600.00 Commissioner?Court&Facilities Services I Reallocation of funds to the correct account to upgrade the electrical a:the Facilities Services Buildine. a'tR4rr its i"zY"sz 1'k?'VS ' is ya 7 ,..'.anti:': I $n t SAI [Depa renal y'r :i 3x a "2Date*V e ,q iiaart e-�6f30F�018 ros z �l tr� 4:51,,: r �"� 4... nty-�ud9e`7 pproval .:P: ,r r'.:ir,.paf �v„r mite F,OcaEea0nfm,.Ptirjro's"el.Only'''''''.. -:'03 t. "'a4' L',e.., 4&.;._.? r .'f";;-`a.;fl.YO,»€+ ''' ? a wa?6'sazbe6:Xibr:rv" r"• �s,' FUND DIV ACCT DR/CR ACCOUNT NAME Increase Decrease 0100 11000500 65052000 CR Carpentry&Building Repair 16,600.00 0100 7000100 65052000 DR Carpentry&Building Repair 16,600.00 BRAZOS COUNTY,TEXAS BUDGET AMENDMENTS No.17/18-35.6 6/5/2018 FUND DEPARTMENT f DIVISION CATEGORY DESCRIPTION I Increase Decrease General Fund Commissioners'Court Contingency Departmental Support i 85000 General Fund Constable Pct.#3 Repairs&Maint 850.00 Commissioners'Court&Constable Pet#3 Reallocation of funds to the correct account cover the software maintenance cost for ticket writers. pp�aaxn t'f!tt� �ss�P ` '2v r to r ", jT'''&4444 a^ixk a ".; '1 ��;,� rYt a r.1.t A#..- i1'Sl.µ t.r e`i t.Ti:`d 4 ytiil"4V g". ,.. s t t, r Affiertrnen`t P.pproval,"•,` ;i:`tigau,.*r. fDate"aF.. k_" �l .s "kk„"'rygt:,. ty'F ar p,i nnml Date err s� .r 3n ;3'St3012* Qy,Co tr(:_ vaf ,,,.,'t'd SM .fDatea? vn>dh..� y f 4 IS FunYafCa0nfinR Purlroses�4ulY, a..� .-.-t c+,.a; ..'+ e�+�d�'iS -.:..';':`�.dklt rr<,".�: ,,,eo-'n..` .a:>Fl .�.�+m„rc _ 'aF'6 '�"R'au'',ta bc.'.;%✓.. FUND DIV ACCT DR/CR ACCOUNT NAME Increase Decrease 0100 11001500 61130000 CR Contingency 850.00 0100 30301100 65150000 DR Computer Maintenance 850.00 I PERSONNEL CHANGE OF STATUS REQUESTS Commissioner Court Date: June 05, 2018 Department Submitting Information: Human Resources Purpose of Submissions: Consider and Take Action on Change Requests Department Submitting Employee Request Requests) Action Requested Applies To Exposition Complex �— --- Henss, Parker Separation Marshall, Michael Employment Approved in Commissioners' Court: June 05 201 : County Judge's or Commissioner's Signature: >, (This Copy to be attached to minutes) VOL 7Y Pg. z7I9 • Brazos County Road&Bridge • Maintenance Report 1AN'MAR • : .. :... FY 18 .. . _ _ _ updated 5/23/18 .. • '. - • •e a Prennc[1_l 34799 Centerline Miles Preon[L 3=349.562 Centerline Mllm Pre[in¢4• - 9MeteitMIedneMilm • Item 1-P ing-Gravel RoadrM ..libod 7.'9 OIMa[e9,256 y}E9uIP2564636, "il3l15.55S"41m"mad Mal 134318:aE"v�EgNll114 .a:1 'f+_.lib 89 "1.4:..3Mate 47 .Ifi:.SEPUIP 8220.7 Grad"v$-62vet Poad Mal to an[e M[Iutlingsprudinggmvell $ - 10.293892621 5 29x15631 $ 35,09736 $ '51$10:34'!$' 23,41238 5 18,147 01 $ .- .892306 5 ::3,69552 $_. 3SID9] $. " 154,00513 : '. PaUlrineIip lip": $ 0.93531 S :-.5,15301 $ `b69L69 $ .62,94010 $'.:. 91.1)030 $ d],SM]9 5 4,BlB]] $ -_;16958 $ 3,18081 $ 2357581 $ 5019186/Pavement Maskers j. $ j $ _ $ $. • Dun Control _ FogSeal • track Seal lmdconbanl $ 'S'$ealE66Itemntenance ubTOWlteml ".:. S =x[-y29)198319:6,-;034.50933)5"' g 32,748x05 $. ' ::)8,822051$ °c 315;611.101$ 6531780 $ -':'77.776 5315,1 [:P 841394'15' ^011.43])815:. ..:309774.941. Item 2.Rea Drainage- _ --nabu6-777111_.�dMate,sl[ I _E4wpmen 3„=-, Labor"'^ )"121 nterriale -JIs Eilitiem t_ '__...]Lebo a,1,_1,. 'lMatedah, I "irqurpmroo_,$ .. Cutven Inslallatii on 5l. - 25,946.90 $.'-: 41.575,16 $ 10,092.66 - 5.80177 $ 0,346,33.5` : 4,945.61 5' • Oita - $- 21,6838E 5 '.3,0185.95 $ ' 19,79404 '8.100.39 $ 387.84.5... 5,64693 5 - / n FradonCgnUal S :]3.06080 $ 7.959 40 5 1],80593 1,761.30 $ 5,74376 5, _ 3,73107 $ 1359.81 9E1129 $ 192637 $ 45.068,74 9, - SWPPP Includingrontranl $ 5 5 - S $- $ - 5 - $ Bridge Maintenance Channel • $ $ .: $ .. 5 .5.: $ - Sublotalllfm2.' $ '61.593521 j' "52560615. " [:5169243 $ .SL 15.868461$ ')14,9])931$ ".: '991331369 5 `1::13598115'•' x980.281$• "`':1.9363] $ .-'.4224 077 25 1 '6)..._. Hem 3.ROWma ._. , Lbm"" 8a71x- aM7temi .ir-"Enupmt'] eriL.. .,bbn2 ._.Ir=f,aMdlvrol 1 Eg,_ aleneC 54. ..Lab^ . _.la-vmtl • alaI .L Es5lni00007a➢ '- Mowing bad contract) j , Dead Tree Removal ltd C4ntra[R $ 5330 $ - 5 13.01 5 2,73539 5 5 1,29074 $ - 1,51105 S 5 ].154.0$ $ 6,66935 limo Removal' S ' 6,48815 $ • $ '-2,296.04 5, ' ' 50,57945 j 5 38,2300 5 985.795 $ -391.87 5 9997379 Kereldtle Application: $ 37367 $ - $ 147.60 5 Malb8v lnDIeS 5 16865 $ $ - 041 $ -:2,03334 5 $ ''90535 5 " '-. 16069 $ - 5 ': 8655 $ _;; 34793 SubT3tal ltem3 $ s`1+13:151991$ r . $ f4<D 8915E 63.9296611$ • an Item 4.08I67 - .-.:..'_210b0r _I�:031ei131U_--.1, 1.En erliegen..c JII6'_-1". `j'.: -'Materia --al ig43IVme 1 __ a,_i.'_ab- ,I•<smal<.1a1[.. 1[Cf 6uulPme48436 • '•• Equipment Hauling - $ ],177.1] $ _ -- 5 3,501,66 $ 133),03 5 - $ 3,4150) $ - 19883' $ - 5 434511 $ 12,104.39 0 Nn6&usb "' 5 - 960 d0 $ 5 :3@.W 5 4.04225'$ $ 1,09900 $ 1)1095 $ $ . 51452 $ 9.603.83 \f Trz4514t6alonly[annOl be rp0[EY PCI. $ 1730.40 ' - Sand Brispos - l - $ 356.80 5 .50,00 $ 95.81 $ 735.01 $5 5023 5 26445 $ 22610 5 50.00.5. 11481 $ 1.68064 g FloodResponse0esnr4dm $.. ` 55670:$5 "' 3 - 95.81 $5 ]05.03 $ - - 5 267,45• 79001 5 - - 1• 5 30.19 5 7.305.70 Sobs tInalSmokes _ $ 51620 5 • 5 - $ - 5 $ • $ 2619000 $ $ $ 17.303 70 r. SubM[al t[emd. 5e .'.:".6851.231] .....502315 '6,093805. .1• ...9.7)4015./ .. . 5303 $:.._., '6BR 965:.'... _ . Total $ 10&419915 07.119.9415 - "94,955.45 $ 368693.5715 130.63911 I$''-130.55660 5 - 40767141$ 9,454.3816 ' 17.930,95 ite 4'794,501841 -- PR1 oAND TOTAL $-i ':19049021 eat GRAND TOTAL 5.. 829,19118 PRl GRAND TOTAL $ ]1,55131 PCT con PER 04515 $ 7,155e1 ea,cow yet MILE 5 3,720.16 .. '. pal COST P59 MILL $ 133.77