Pro_Forma-34901-01651_Final.pdf

PDF 562 KB Posted

Attached to
Tennessee Integrated Traffic Analysis Network ("Titan") System Maintenance and Support
Solicitation number
RFP 34901-01651
Issued by
Davidson County, Tennessee

About this file

This is a pro forma contract between the State of Tennessee, Department of Safety and Homeland Security, and a contractor for maintenance, support services, enhancements, and upgrades to the Tennessee Integrated Traffic Analysis Network (TITAN) system. The contract was awarded through a competitive Request for Proposals (RFP #34901-01651) and has an effective date of February 1, 2027, extending for sixty months. The scope encompasses comprehensive system maintenance and support services to ensure TITAN operates at 99.99% availability on a 24/7/365 basis, including enhancements to existing applications (eCrash, eCrime, eCitation, Trooper Activity), database optimization, server environment upgrades, and development of new applications (DUI Tracker, Checkpoint Activity, Ticket Accountability, Fatality Tracking System, and Facilities Protection Officer Activity modules). The contractor must provide on-site project management, user acceptance testing support, knowledge transfer, and technical documentation, with a minimum of four full-time technical resources required on-site and up to two remote positions permitted.

The contract compensation is structured as a monthly fee for services including six full-time technical resources (one database administrator and five senior-level developers with minimum seven years' experience), dedicated on-site project leadership, and approved software solutions for IT service management, code quality measurement, and system alerts; change order work is limited to seven percent of the base compensation amount. The contractor is responsible for all support and maintenance costs based in the United States, including help desk support with defined severity-level response times (Critical: 8-hour resolution, High: 24-hour resolution, Medium: 2-business-day resolution, Low: 2-3 business-day resolution), and service credits apply for SLA non-compliance. The contract is subject to fund availability and includes standard state compliance requirements including nondiscrimination provisions, prohibition of illegal immigrants, HIPAA compliance where applicable, debarment and suspension certification, and compliance with Tennessee and federal laws. No minimum purchase guarantee is provided to the contractor, and the State retains all ownership rights to data, source code, and deliverables produced under the contract.

View the file

Other files

File Type Posted
RFP_34901-01651-TITAN_Maintenance_RFP_Final.pdf PDF

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

12-18-25 FA

C O N T R A C T (fee-for-goods or services contract with an individual, business, non-profit, or governmental entity of another state)

Begin Date End Date Agency Tracking # Edison Record ID

February 01, 2027 January 31, 2032

Contractor Legal Entity Name Edison Vendor ID

Goods or Services Caption (one line only)

Maintenance, support services, enhancements and upgrades of the Tennessee Integrated Traffic Analysis Network (TITAN) system

Contractor CFDA #

Contractor

Funding —

FY State Federal Interdepartmental Other TOTAL Contract Amount

TOTAL:

Selection Method & Process Summary (mark the correct response to confirm the associated summary)

Competitive Selection This Contract was awarded through a competitive Request for Proposals solicitation (RFP #34901-01651)

Other

Budget Officer Confirmation: There is a balance in the appropriation from which obligations hereunder are required to be paid that is not already encumbered to pay other obligations.

Speed Chart (optional) Account Code (optional)

CONTRACT

BETWEEN THE STATE OF TENNESSEE,

DEPARTMENT OF SAFETY AND HOMELAND SECURITY

AND

CONTRACTOR NAME

This Contract, by and between the State of Tennessee, Department of Safety and Homeland Security (“State”) and Contractor Legal Entity Name (“Contractor”), is for the provision of maintenance, support services, enhancements and upgrades of the Tennessee Integrated Traffic Analysis Network (“TITAN”) system, as further defined in the "SCOPE." State and Contractor may be referred to individually as a “Party” or collectively as the “Parties” to this Contract.

The Contractor is a/an Individual, For-Profit Corporation, Non-Profit Corporation, Special Purpose Corporation Or Association, Partnership, Joint Venture, Or Limited Liability Company.

Contractor Place of Incorporation or Organization: Location Contractor Edison Registration ID # Number

A. SCOPE:

A.1. The Contractor shall provide all goods or services and deliverables as required, described, and detailed below and shall meet all service and delivery timelines as specified by this Contract.

A.2. Definitions and Acronyms. For purposes of this Contract, definitions shall be as follows and as set forth in the Contract:

a. Application Programming Interface (“API”) means a set of rules and protocols that allows different software applications to communicate and exchange data with one another.

b. Canned Report means a report generated from a saved query with predetermined data fields. These reports are typically distributed across a wide audience, utilizing polished formatting. These reports are brief and succinct containing batched and scripted data using weekly or monthly metrics.

c. Drivers Privacy Protection Act of 1994 (“DPPA”) means a United States federal statute

(Title 18 United States Code (USC) §§ 2721 et seq.) governing the privacy and disclosure of personal information gathered by state Departments of Motor Vehicles (“DMVs”) and contained in a person's motor vehicle record.

d. FMCSA means Federal Motor Carrier Safety Administration.

e. Global Justice XML Data Model (“GJXDM” or Global “JXDM”) means a data reference model for the exchange of information within the justice and public safety communities.

f. International Association of Chief of Police (“IACP”) means a 501(c)(3) nonprofit organization whose mission is to advance the science and art of police services; develop and disseminate improved administrative, technical and operational practices and promote their use in law enforcement; foster police cooperation and the exchange of information among police administrators throughout the world; bring about recruitment and training in the police profession of qualified persons; and encourage adherence of all police officers to high professional standards of performance and conduct.

g. Law Enforcement Information Technology Standards Council (“LEITC”) means a council established to provide advice and leadership to the nation’s law enforcement community on information technology standards; share practical solutions; and educate the public safety community on the merits and technical aspects of information system integration.

h. Model Minimum Uniform Crash Criteria (“MMUCC”) means a minimum, standardized data set for describing motor vehicle crashes and the vehicles, persons and environment involved. The information generated by this data set is necessary to improve highway safety within each state and nationally.

i. NCIC means National Crime Information Center.

j. National Information Exchange Model (“NIEM”) means an XML-based information exchange framework from the U.S. that represents a collaborative partnership of agencies and organizations across all levels of government and with private industry.

k. Release Notes means documents that are distributed with software products, sometimes when the product is still in the development or test state (e.g., beta release). For products that have already been in use, the release notes are delivered when an update is released.

l. Tennessee Incident Based Reporting System (“TIBRS”) means a database into which law enforcement officers and colleges and universities are required to report crimes to the Federal Bureau of Investigation (“FBI”) or the Tennessee Bureau of Investigation (“TBI”) (T.C.A. §§ 38-10-101 et. Seq) and (T.C.A. §§ 49-7-2201 et seq.).

m. TITAN means Tennessee Integrated Traffic Analysis Network, a customized records management system utilized by the State that manages records to include but not be limited to the following: citations, crashes, arrests, DUIs, incident offenses, trooper activity, and is a suite of applications developed for the electronic collection, submission and management of all traffic safety related data in Tennessee.

n. TITAN Thick Client means a client-server architecture which provides TITAN reporting functionality independent of the central server.

o. TITAN Unit means State designated personnel who manage projects, grant-related activities, and statistical reporting related to the Tennessee Integrated Traffic Analysis Network.

p. Tennessee Roadway Inventory Management System (“TRIMS”) means a system operated by the Tennessee Department of Transportation that is used by engineers and transportation professionals statewide for roadway safety analysis.

q. Tennessee Fusion Center (“TFC”) means a collaborative effort of two or more law enforcement agencies in Tennessee, in cooperation with the citizens of the state of Tennessee, which provides resources, expertise, and information to the center with the goal of maximizing the ability to detect, prevent, investigate, and respond to criminal and terrorism activity.

r. TITAN SQL Database means a collection of schemas, tables, queries, reports, views and other elements.

s. Third Party Vendors means outside vendors who provide other law enforcement agencies with a records management system other than the TITAN system. These Third Party Vendors must adhere to the requirements contained in Tenn. Code Ann. § 55-10- 111 for crash reporting to the State.

t. Traffic Records Program Assessment Advisory means a report published by the U.S.

National Highway Traffic Safety Administration (“NHTSA”) that gives states information on the contents, capabilities, and data quality of an effective traffic records system by describing an ideal system that supports high-quality decisions and leads to cost-effective improvements in highway and traffic safety.

u. Traffic Records Strategic Plan means a multi-year plan addressing the State’s traffic safety data and processing deficiencies, integrating State data needs and goals with the State’s highway safety plan, identifying performance-based measures for measuring progress, and indicating how funds shall be used and what progress the State has made to date. This plan is a component of the 405(c) Grant Application.

v. User Acceptance Testing (“UAT”) means the execution of a series of defined steps using pre-defined data—the objective of which is to determine whether the actual outcome consistently, repeatedly, and accurately equals the expected result. User acceptance testing is a deliberate process that requires preparation of test scenarios, test cases, test data, and expected outcomes, which are known in advance of test execution.

w. Web Service means any piece of software that makes itself available over the internet and uses a standardized extensible markup language (“XML”) messaging system.

A.3. General Understandings:

a. The State's Tennessee Highway Patrol (“THP”) is responsible for enforcing federal and State laws relating to traffic on Tennessee's federal and state highways. The mission of the THP is to ensure safe and efficient transportation while promoting highway safety through enforcement and education. One way of accomplishing this mission is to provide access to the TITAN system to law enforcement agencies throughout Tennessee.

b. The State’s history of working on traffic data issues supports the plan to develop new functions and improve old ones for a complete unified statewide public safety network.

The overall goal is to have a unified records network that enables seamless collection and dissemination of information throughout the state of Tennessee, promoting public safety

c. The TITAN system is a suite of applications developed for the electronic collection, submission, and management of traffic safety related data in Tennessee. The TITAN system has been designed to accept reports submitted by law enforcement agencies, validate the data contained within the reports for completion and accuracy, and then store statistically valid information. The TITAN system's repository also creates document images of submitted reports and stores them for future access and records retention requirements. This information is used to make data-driven decisions and help make Tennessee a safe and secure place in which to live, work, and travel.

d. In aligning with the advancements of modern technology, the Contractor shall enhance and upgrade the TITAN system to increase the accuracy, timeliness, completeness, uniformity, integration, and accessibility of the information used to form Highway Safety Plans for Tennessee. The users, owners, and operators of the various State current record management systems have come together with the goal of upgrading the systems in a coordinated manner to take advantage of advances in technology. During the Term of the Contract, at the State’s discretion, the State will pursue migration to the State’s cloud-hosted environment and consider platform-as-a-service (PAAS) or infrastructure-as-a-service (IAAS).The Contractor shall be responsible for the operational support throughout the migration and upon its conclusion to ensure the TITAN system remains fully operational in accordance with the new hosting environment.

d.

A.4. Contractor’s Responsibilities. The Contractor shall meet the following requirements:

(1) All services, along with any duties incidental or necessary to the TITAN system, shall be carried out diligently, thoroughly, and in full compliance with recognized professional standards of conduct and performance. These standards include adherence to ethical principles, technical competence, accountability, and respectful workplace behavior, ensuring that all work meets or exceeds industry best practices and organizational requirements;

(2) The Contractor shall ensure all components and applications shall be operational in an electronic environment, unless otherwise noted;

(3) The Contractor shall ensure TITAN’s components and applications shall be available 99.99% of the time calculated on a 24 hours a day, 7 days a week, 365 days a year (24/7/365) basis;

(4) The Contractor shall comply with CJIS security requirements as determined by the TBI;

(5) The Contractor shall fully document the functionality of TITAN in order to allow third party developers to interface with the software without the Contractor’s involvement. This shall include database schema, data dictionaries, Web Service interface or API instructions, process flow charts, and business and validation rules;

(6) The Contractor shall make sure TITAN complies with the State’s Enterprise

Information Security Policies as amended periodically (The State’s Enterprise Information Security Policy documents are found at the following URL:

https://www.tn.gov/finance/strategic-technology-solutions/strategic-technology-solutions/sts-security-policies.html. The integrity of the information within TITAN shall be maintained at all times;

(7) The Contractor shall make TITAN accept, ingest, and process computer-generated reports originating from external systems without manual re-entry through APIs. This includes maintenance of transfer, validation, storage, acknowledgment, and error handling for electronic submissions;

(8) The Contractor shall implement and maintain secure submission channels to ensure interoperability with agency and vendor systems, including but not limited to, RESTful API (HTTPS/TLS 1.2+) with authenticated endpoints for programmatic submission and status retrieval; XML conforming to agency-published schemas (e.g., citation/crime/crash report schemas); JSON using agency-defined JSON Schemas for structured data interchange; and PDF/A-1b or higher for immutable, non-editable report renditions accompanying structured data; and

(9) The Contractor shall make TITAN interface with the TFC’s record management system, as well as providing the ability to provide cross-jurisdictional information resources for local law enforcement entities (agencies, departments, offices) as directed by the State.

A.5. TITAN System Requirements:

a. TITAN’s components shall continue to be hardware agnostic, utilizing IACP's best practices. TITAN shall continue to utilize and support all available and emerging standards as proposed by the IACP. These include, at a minimum, Global Justice XML and the Global Justice XML data model, the NIEM's current standards, and the LEITC for the continuation of effectively sharing data and information with other law enforcement and public safety agencies as required. All new development and or enhancements outlined in this Contract shall be implemented into the production environment.

b. TITAN shall continue to receive periodic updates as required for operational readiness.

These updates may originate from the Contractor or the State.

c. TITAN shall continue to support a fully scalable architecture designed to allow incremental changes in capacity to meet changing usage.

d. TITAN shall continue to provide a web based service-oriented architecture and support documentation that shall allow third party client applications to access RMS functionality.

A.6. TITAN System Architecture:

a. TITAN shall continue to consist of multiple operating environments that shall allow users to have different permission levels and/or permissions. TITAN consists of the following operating environments:

(1) Development: Used for the development of new modules and applications or existing modules and applications within TITAN . It is similar to the production environment, but is smaller in scale;

(2) Test-Training: Used to simulate the actual production environment for verification of new code modifications and accurately represent the production environment. This environment shall be used to reproduce error conditions and testing with real production data without making changes to the database of record. This environment shall be a scaled mock-up of the production environment. In addition, this environment shall be used for user-training;

(3) Production: The official system of record. The production environment shall be sized to handle any expected demand. The production environment shall operate in accordance with the State’s standards. Changes shall only be made through documented change control procedures; and

(4) SQL Server Reporting Services (“SSRS”) server environments.

b. The State at its discretion may conduct code review penetration testing and other security reviews prior to or after code releases in the production environment. The Contractor shall fix any discrepancies identified by the State within an allotted time to be determined by the State.

c. The Contractor shall update all technical data flow diagrams and system documentation within thirty (30) calendar days of the completion of any enhancements or upgrades.

This documentation should include the following:

(1) The Contractor shall provide comprehensive technical documentation for all components of TITAN. . Documentation shall be accurate, complete, and maintained throughout the Term. All deliverables shall be version-controlled, delivered in both human-readable (PDF) and machine-readable formats, and updated promptly upon any system change;

(2) The Contractor shall deliver a complete data dictionary for all TITAN data elements, including but not limited to:

i. Field-Level Details: Field name, data type, length, format, default values, nullability, and constraints;

ii. Semantic Definitions: Business meaning and usage context for each field;

iii. Allowed Values: Enumerations, reference tables, and code sets;

iv. Relationships: Mapping of fields to tables and associated business rules;

v. Version Control: Each update shall include a detailed change log; and

vi. Delivery Format: Machine-readable (CSV or XML) for integration purposes and human-readable (PDF) for review and audit;

(3) The Contractor shall provide a comprehensive catalog of all edit checks and validation rules implemented at the user interface, API, and database levels.

Documentation shall include:

i. Rule Identification: Unique ID, description, and category (e.g., structural, business logic);

ii. Logic Definition: Full specification of conditions, thresholds, and dependencies;

iii. Severity Classification: Error, warning, or informational;

iv. Business Rule Mapping: Linkage to statutory, regulatory, or policy requirements;

v. Test Cases: Sample inputs and expected outputs for each rule; and

vi. Update Policy: Initial delivery at system acceptance and updated documentation with each release or rule modification; and

(4) The Contractor shall deliver complete logical and physical database schemas, including:

i. Entity-Relationship Diagrams (ERDs): Showing tables, keys, and relationships using industry-standard notation;

ii. Physical Schema Details: Indexes, constraints, storage parameters, and partitioning;

iii. Data Flow Diagrams: Illustrating interactions between major components and external systems;

iv. Delivery Format: PDF for review and compliance and native format (e.g., ERWin, DbSchema) for technical teams; and

v. Update Policy: Updated diagrams and schema documentation shall accompany any schema modification or system upgrade.

A.7. Hardware, Software, and Network Requirements:

a. Hardware Requirements:

(1) TITAN system Location: The TITAN system shall continue to be hosted on State standard hardware within the State’s data center or State cloud-hosted solution.

(2) Responsibility for Hardware: The State shall be responsible for providing the hardware used by TITAN. The Contractor shall provide clear specifications of all hardware needed. The State reserves the right to add, change, reconfigure, consolidate, or eliminate hardware at any time to meet the best interests of the State.

(3) Use of Virtual Server Environment:

i. The State requires the TITAN system to operate in the State’s virtual environment or State cloud-hosted solution;

ii. TITAN shall be compatible with the State Storage Area Network (“SAN”) or Network Attached Storage (“NAS”);

iii. TITAN shall be compatible with FileNet or the State’s chosen Enterprise

Content Management (ECM) platform for document management; and

iv. The Contractor shall provide advisory services, guidance and assistance with respect to the installation of all TITAN and related software in all environments.

b. Software Requirements:

(1) Development Languages: any new developments, enhancements, and upgrades to TITAN shall be developed using a programming language supported by the Microsoft .NET platform (currently .NET Core 9.0 or later), or any future successor framework released by Microsoft;

(2) Client: The remaining client-based applications will be supported until which time they are rewritten and the client applications are sunset;

(3) Browser Based Applications: Any new browser-based applications shall be fully compatible with the latest stable versions of major browsers, including Google Chrome and Microsoft Edge or other State-standard browsers, and shall support all subsequent updates and versions;

(4) Database Technology: TITAN shall utilize Microsoft SQL 2019, or its successor;

and

(5) Componentized Functionality: Any new software elements shall be developed to be extendable components, allowing the State to add increased functionality without requiring redevelopment of the other components.

c. Network Requirements: The State shall provide network resources used by TITAN. The

Contractor shall provide clear specifications of all network resources needed. The Contractor shall utilize network resources sufficient to meet the business need but not exceed what the State considers a reasonable amount of capacity. The State reserves the right to add, change, reconfigure, consolidate, or eliminate network resources at any time to meet the best interests of the State.

A.8. System Documentation.

a. The Contractor, in conjunction with State designated personnel, shall work together to gather, define, or determine the State’s business requirements. All State business requirements shall be documented and agreed upon by the State:

(1) The Contractor shall use a State-approved software tool to assist with code quality monitoring for the current source code and any future enhancements or releases; the State shall provide designated Contractor personnel with access to TITAN in order to utilize the software tool.

b. The Contractor shall create documentation for proper maintenance and support of TITAN. This documentation shall aid knowledge transfer to future State designated personnel who support TITAN. Documentation shall cover all modules within the TITAN system, all interfaces, and all supporting code. Documentation shall include up-to-date data dictionaries, edit checks and validation rules, and end-user reference materials.

A.9. Development of New and/or Enhancement of Existing Applications. The following requirements shall be met for all items in Sections A.10. through A.11. as well as projects completed through the Change Requests/Orders process described in Section A.12.:

a. Training. The Contractor shall provide on-site training concerning the functionality and use of any new and/or enhanced module or application as requested by the State.

b. Updating Applications. The Contractor shall update any thick client or web-based applications in accordance with legislative changes, departmental policies, and/or new departmental reporting requirements. A detailed scope of work with business requirements should be created for enhancements that are approved by the State prior to commencement of development.

c. Acceptance/Final Sign-Off by State. Any development of new and/or enhancement of existing modules or applications shall not be considered delivered and accepted until final sign-off by State designated personnel. It is agreed that UAT sign-off by the State shall be treated as the State’s approval for this work as well as projects completed through the Change Requests/Orders process described in Section A.12.

d. The Contractor shall implement and maintain a formal version control system for all

TITAN application releases, updates, patches, and hotfixes. Each release shall be uniquely identified by a version number and include a corresponding change log detailing all modifications, enhancements, and fixes.

e. For every release, the Contractor shall provide:

(1) A Release Notes Document summarizing new features, bug fixes, and known issues;

(2) A change log identifying impacted components, configuration changes, and dependencies; and

(3) A rollback procedure as specified below in Section A.9.f.

f. The Contractor shall ensure that all future software releases, updates, and patches for the TITAN Application include a fully functional rollback mechanism. This mechanism shall allow the State to revert the application to the most recent stable version without loss of data or system integrity.

g. Artificial Intelligence (AI) Integration : The Contractor shall provide and implement

Generative and/or Agentic AI technologies as part of TITAN software applications (e.g.

Trooper Activity) to streamline data collection. This includes delivering AI-powered tools and solutions that enhance functionality, automation, and user experience within TITAN applications. In addition to ensuring seamless integration of AI capabilities into existing customized TITAN software applications without disrupting current workflows or data integrity. The Contractor shall:

(1) Assess current TITAN architecture and propose an AI integration plan aligned with business objectives;

(2) Provide APIs, SDKs, or other integration mechanisms to enable AI functionality within TITAN applications;

(3) Ensure compliance with all applicable security, privacy, and data governance standards during AI implementation;

(4) Offer training and documentation for internal teams on AI-enabled features;

(5) Ensure AI solutions meet agreed-upon performance benchmarks and support scalability for future enhancements;

(6) Maintain transparency in AI model usage, including data sources, limitations, and ethical considerations;

(7) Comply with all enterprise security protocols and regulatory requirements related to AI deployment;

(8) Provide ongoing support for AI components, including updates, bug fixes, and performance optimization; and

(9) Ensure compatibility with future TITAN software updates and enhancements.

A.10. Enhancements, or Upgrades, of Existing Applications.

a. TITAN Trooper Activity Enhancement

(1) The Contractor shall complete ongoing enhancements that includes updating the web based user interface (“UI”) screens to capture data related to the daily activities of Troopers by meeting the following requirements:

i. Auto-populate Trooper Activity database fields with data from the THP

Computer-Aided Dispatch (CAD) system, including modifications required when the THP CAD system is upgraded, modified, or replaced;

ii. Auto-populate Trooper Activity database fields with data from THP scheduling software applications relating to shifts scheduled, shifts, worked, grant, and overtime shifts; and

iii. Auto-populate Trooper Activity database fields with data from other

TITAN modules (e.g., Crash, Citation, Crime, and other relevant TITAN applications).

b. TITAN SQL Database (“the Database”) Enhancements

(1) Enhancement: The Contractor shall provide ongoing enhancements for optimal

TITAN system performance, ease of support and maintenance, access to simplified and better structured data tables for ease of reporting and data collection, as well as, provide a data schema that allows for the continuous growth and scaling out the business and operational demands of the Database statewide by performing the following enhancements:

i. Enhance the Database to the most recent State supported version of

Microsoft SQL;

ii. Re-architect the Database to meet the demands of the TITAN system and end users;

iii. Modify TITAN applications to be able to use the new Database schema;

iv. Ensure that data collection is not interrupted.

c. TITAN eCrash Enhancements and MMUCC Standards Enhancement

(1) Functionality: The TITAN system currently includes a web-based eCrash application. The eCrash application allows for a set of data elements to be captured at the scene of a motor vehicle crash to be transmitted to the State.

(2) The Contractor shall perform the following enhancements:

i. Update the eCrash application in accordance with legislative changes and/or new departmental reporting requirements.

(3) Enhancement: The TITAN eCrash 2.0 web based application and associated printable crash reports (Levels 1 through 3) shall be modified to adhere to current MMUCC 6th Edition Standards and any future updates to MMUCC guidelines.

Removal and addition of data fields within the web-based application, as well as, on the printed crash reports shall be updated to adhere to the new standards.

(4) The Contractor shall do the following:

i. Modify existing eCrash 2.0 application screens and database to adhere to current MMUCC data elements;

ii. Modify existing eCrash printed reports to reflect the newly collected

MMUCC data elements; and

iii. Modify existing data extract request jobs to reflect the newly collected

MMUCC data elements.

d. TITAN Server Environment Enhancement

(1) Enhancement: The Contractor shall upgrade the Operating System, as defined in Section D.37, to the latest State supported version as follows (currently SQL Server 2019). All TITAN hosted environments shall be enhanced, to include the development, training, production, and the SQL server reporting services (“SSRS”) server environments. For each of the environments there are three (3) servers (web, Application, and TITAN SQL database), and three (3) environments (Production, Test/Training, and Development) that shall be enhanced, with the exception of the SSRS server which is a single server, for a total of ten (10) servers; and

(2) The Contractor shall assist the State in the scheduling and upgrading of the Microsoft Operating System in all environments.

e. TITAN eCrime Redesign and Enhancements

(1) Functionality: TITAN currently includes an “Arrest / Criminal Interdiction Form” that currently exists within the TITAN Thick Client. This form provides law enforcement personnel with a report that is used to document arrests and the circumstances regarding the arrest. It establishes uniform procedures for the processes involved for an arrest. Access to this module that contains CJIS data is controlled through role-based security measures.

i. Create a new web-based eCrime application to replace the current TITAN Thick client version. The new application should function on any web browser. Additionally, an iOS app that mirrors the web-based functionality should be created for eCrime;

ii. Update the TIBRS flat file in accordance with the published business rules from the TBI;

iii. Update the eCrime data collection form and business rules annually or bi-annually when new requirements as set forth by the TBI for TIBRS reporting, on an agreed upon time frame as determined by the State;

iv. Add help descriptions, such as pop-up boxes that shall assist the end user in determining the proper manner in which to complete a given field, to the key areas of the eCrime module; and

v. Help files shall consist of text descriptions or images illustrating certain functionality, or meaning, within the eCrime module.

f. TITAN eCitation Application and Web Portal Enhancements

(1) Functionality: TITAN currently includes a web-based eCitation Application and iOS eCitation application. The eCitation application is customized and is used to create citations in the field and transmit the citation to the court system.

Reporting and tracking functionality exist within the TITAN web portal. This allows seamless query and reporting access to citation data submitted to the central repository by participating agencies. This may include development of an Android-based eCitation application, which mirrors the current iOS application functionality.

i. Update the web-based and iOS eCitation application in accordance with legislative changes and/or new departmental reporting requirements;

ii. If allowable under State law, and at the direction of the State, create an eWarrant module to function in tandem with the eCitation for arrestable offenses; and

iii. Maintain and enhance existing web services and APIs for transmission of citation data and images to court systems and local law enforcement agencies.

g. TITAN Thick Client Transition from a Windows 11 installation package to Browser-based software applications.:

(1) Current Functionality: The TITAN Thick Client application currently provides the ability for law enforcement officers from across Tennessee to enter information pertaining to crashes, arrests, citations, and other activities that occur in Tennessee. Entry screens drive the data sets to be collected, transmitted, and stored in the State’s TITAN SQL Database;

(2) The Contractor shall utilize the latest version of .NET and use the newer technology and code to extend content options that shall enhance, fix, and rewrite certain areas of the TITAN system to provide a more stable, maintainable, and more user-friendly interface. These applications include: eCrime, Overweight Assessment, Implied Consent, and Incident/Offense forms; and

(3) The Contractor shall meet the following requirements:

i. Track and fix bugs in the new version;

ii. Maintain continuity of collecting and transmitting current information captured in all Thick Client Applications, including validation rules and edit checks within each respective module;

iii. Completely test each unit of development, prior to deployment;

iv. Use the latest version of .NET;

v. Provide a more user-friendly interface that is adaptable and optimized for use on tablets and mobile devices including day and night viewing modes; and

vi. Reorganize and simplify (where applicable) the fields captured for all current Thick Client Applications.

h. TITAN Thick Client Install/Uninstall Processes

(1) The Contractor shall maintain and update installation and uninstallation processes for the TITAN Thick Client application to ensure compatibility with currently supported Windows Operating Systems, including Windows 11, and all future Windows releases as required by the State. The Contractor shall provide complete installation and removal capabilities for end users, including automated and silent installation options where applicable. Updates to installation packages and related processes shall be delivered promptly upon State request or as necessary to maintain compliance with State standards and Operating System changes.

i Enhancements to Barcode Scanning and Image Capture Capabilities. The Contractor shall:

(1) Maintain all existing barcode/QR scanning and image capture functionality across modules; and

(2) incorporate barcode/QR scanning and image capture functionality in any new applications and enhancements, as required and designated by the State.

Currently Dynamsoft bar code scanning software is utilized.

j. Enhancements to Quick Capture Module

(1) The Contractor shall maintain all existing functionality for the Quick Capture module, which shares driver, vehicle, and person-level data across TITAN modules, eliminating the need for end users to enter the same information separately across TITAN applications. This includes the web-based application and the iOS application.

k. New DUI Tracker application. The Contractor shall:

(1) Replace existing web-based DUI Tracker application with a new modernized web-based application in the TITAN 2.0 web portal;

(2) integrate the DUI Tracker application with Driver and Vehicle systems to auto-populate data into the form for end users;

(3) create new canned reports based on business requirements as designated by the State; and

(4) maintain and migrate historical data to the new application and database.

l. New Checkpoint Activity Application. The Contractor shall:

(1) Replace existing web-based Checkpoint Activity application, which includes three

(03) forms for collecting checkpoint activity (Checkpoint Site form, Checkpoint Authorization form, and Checkpoint Activity form), with a new web-based modernized application in the TITAN 2.0 web portal.

m. New Ticket Accountability Application. The Contractor shall:

(1) Replace existing web-based Ticket Accountability application, which tracks ownership and responsibility for paper-based ticket books, with a new web-based

n. New Fatality Tracking System (“FTS”) Application.

(1) Replace existing web-based Fatality Tracking System (“FTS”) application, which tracks traffic fatality and fatal crash data and documentation, with a new web-based modernized application in the TITAN 2.0 web portal.

o. New Facilities Protection Officer (“FPO”) Activity Application

(1) Replace existing web-based Facilities Protection Officer (“FPO”) Activity application, which tracks traffic activity of facilities protection officers, with a new web-based modernized application in the TITAN 2.0 web portal.

p. New Homemade Trailer Inspection Application

(1) Replace existing web-based Homemade Trailer Inspection application, which tracks inspection and certification of homemade trailers, with a new web-based

A.11. New Applications or Modules and Associated Enhancements

a. TITAN New System Interfaces

(1) Interface: The TITAN Thick Client and web-based applications shall be adaptable to interface to other Traffic Records Systems' (“TRS'”) components to support the following functions:

i. Verification and import of Driver and Vehicle data, including auto-population of Driver and Vehicle data from the State’s Driver and Vehicle Systems into the TITAN System applications, shall be used to validate the driver and vehicle information during data entry;

ii. Verification and import of Roadway data, including auto-population of

Roadway data from the State’s Roadway System into the TITAN System applications, shall be used to validate roadway information during data entry; and

iii. Have the ability to be captured and imported into the TITAN Thick Client and web-based applications for purposes of auto-populating fields in TITAN eCrash, eCitation, eCrime, TOW, and other TITAN applications as identified by the State; and

(2) The Contractor shall ensure that the TITAN system interfaces with the following:

i. State Driver History file;

ii. Tennessee Court Clerk reporting systems;

iii. Local law enforcement agency RMS;

iv. TIBRS;

v. State Vehicle Systems;

vi. State Health Systems;

vii. State Roadway Systems;

viii. TIES/NCIC;

ix. TRIMS;

x. State-hosted PurchaseTNCrash.gov system;

xi. Tennessee Fusion Center; and

xii. Other systems as determined by the State.

A.12. Change Requests/Orders

The State may, at its sole discretion and with written notice to the Contractor, request changes in the Scope that are necessary but were inadvertently unspecified in this Contract.

a. Change Order Creation — After receipt of a written request for additional services from the State, the Contractor shall respond to the State, within a maximum of ten (10) business days, with a written proposal for completing the service. Contractor’s proposal must specify:

(1) the effect, if any, of implementing the requested change(s) on all other services required under this Contract;

(2) the specific effort involved in completing the change(s);

(3) the expected schedule for completing the change(s);

(4) the maximum number of person hours required for the change(s); and

(5) the maximum cost for the change(s) — this maximum cost shall in no instance exceed the product of the person hours required multiplied by the appropriate payment rate proposed for such work.

The Contractor shall not perform any additional service until the State has approved the proposal. If approved, the State shall sign the proposal, and it shall constitute a Change Order between the Contract Parties pertaining to the specified change(s) and shall be incorporated, hereby, as a part of this Contract.

b. Change Order Performance — Subsequent to creation of a Change Order, the Contractor shall complete the required services. The State shall be the sole judge of the acceptable completion of work and, upon such determination, shall provide the Contractor written approval.

c. Change Order Remuneration — The State shall remunerate the Contractor only for acceptable work. All acceptable work performed pursuant to an approved Change Order, without a formal amendment of this Contract, shall be remunerated in accordance with and further limited by Contract Section C.3.c., PROVIDED THAT, the State shall be liable to the Contractor only for the cost of the actual goods or services provided to complete the necessary work, not to exceed the maximum cost for the change detailed in the Change Order. In no instance shall the State be liable to the Contractor for any amount exceeding the maximum cost specified by the Change Order authorizing the goods or services. Upon State approval of the work, the Contractor shall invoice the State in accordance with the relevant provisions of this Contract.

A.13. Support and Maintenance Services

a. Support Services and Maintenance:

(1) All Contractor provided maintenance and support shall be based in the United States.

(2) The Contractor shall provide maintenance and support for all existing and future TITAN components.

(3) The following support services shall be provided by the Contractor:

i. RMS Support Services: The Contractor shall provide support services for TITANto ensure its availability 99.99% of the time calculated on a 24 hours a day, 7 days a week, 365 days a year (24/7/365) basis (“Service Level Agreement” or “SLA”);

ii. Contractor’s compliance with the SLA shall be calculated on a monthly basis by totaling the amount of time that Contractor exceeds on a per incident basis, the resolution targets for Critical and High Severity Levels expressed in the table below. For example, a resolution of a Critical Severity Level incident in ten (10) hours shall result in two (2) hours of time that exceeded the resolution target;

iii. Failure to meet this SLA shall result in a service credit by the Contractor on the next invoice submitted to the State. This service credit shall be proportionate to the total length of time the incidents exceeded the resolution targets compared with the total amount of time that the TITAN system was to be available during the month. The service credits shall be calculated as follows:

(a). For each hour in excess of the Critical and High Severity Level resolution target, the Contractor will provide two (2) additional hours for a Developer as the service credit;

(b). The service credits shall not exceed forty (40) hours per month;

(c). The service credit shall be due in the current month if a service level default occurred in the previous month;

iv. The Contractor is not responsible for any service credit or outage where the root cause analysis identifies the root cause was not as a result of an act or omission by the Contractor under this Contract, including:

(a). Planned outages agreed to by the State and any outages resulting from Force Majeure events shall not constitute failure to meet resolution targets for Critical and High Severity Levels;

(b). As a result of any action or inaction by the State or its subcontractors;

(c). As a result of any issues with out-of-support third-party software that has not been upgraded at the State’s request; and

(d). Where the Contractor proposes a resolution to a known problem inside the State’s environment and State does not allow the Contractor to implement the resolution, or delays the resolution, within the weekly change window process, then the Contractor will not be responsible for any service credit or outage, where the failure is a direct result of the prevention or delay in implementing the resolution.

v. If the State reduces the capacity or changes any of the support requirements, then the Parties may mutually agree to adjust the service levels;

vi. The Contractor shall provide off-hours support for handling Critical and High Severity Level or scheduled activities that must be performed off-hours as required;

vii. The Contractor shall provide a ticketing system to be used to log the TITAN system incidents, including Tier 1 support requests, (e.g., Zendesk, Jira, etc); and

viii. Delivery of Support Services: The State reserves the right to determine and assign levels of severity for the issue and support problems. The severity of the issue and support problem shall determine the problem resolution response time as follows:

Severity Level Response

Critical: Situations where the State's system is down and the State is unable to use the TITAN system, or when failure causes loss of function or data and there is not a mutually agreed-upon workaround.

The Contractor's technical support staff shall accept the call for assistance at the time the State places the initial call;

however if such staff is not immediately available, the Contractor shall return the call within one (1) hour. The Contractor shall resolve Critical Level problems as quickly as possible, with resolution not to exceed eight (8) hours unless mutually agreed upon between the Contractor and the State.

High: Where critical TITAN system component(s) have significant outages and/or failure precluding its successful operation, or possibly endangering the State's environment. The TITAN system may operate but is severely restricted. Failure causes a loss of function or data, but there is a mutually agreed upon workaround.

The Contractor's technical support staff shall accept the State's call for assistance at the time the State places the initial call; however if such staff is not immediately available, the Contractor shall return the State's call within four (4) hours. The Contractor shall resolve High Level problems as quickly as possible, which shall not exceed twenty four (24) hours, unless mutually agreed upon between the Contractor and the State.

Medium: A problem that exists with the TITAN system, but the majority of the functions is still usable and some circumvention may be required to provide service. Failure causes a partial loss of function, but users can accomplish tasks with a mutually agreed upon workaround.

The Contractor's technical support staff shall accept the State's call for assistance at the time the State places the initial call; however if such staff is not immediately available, the Contractor shall return the State's call within eight (8) hours. The Contractor shall resolve Medium Level problems as quickly as possible, which shall not exceed two (2) business days, unless mutually agreed upon between the Contractor and the State.

Severity Level Response

Low: Minor problem that exists with the Application, components, or TITAN system but all operational functions are working. All other ‘bugs’ that are determined by State designated staff to be an issue that requires attention but is not immediate to the operational stability of the TITAN system.

The Contractor's technical support staff shall accept the State's call for assistance at the time the State places the initial call; however if such staff is not immediately available, the Contractor shall return the State's call within twenty four (24) hours. The Contractor shall resolve Low Level problems as quickly as possible, which shall not exceed two to three (2-3) business days, unless mutually agreed upon between the Contractor and the

(4) State Provided Help Desk Support — Level One Help Desk Support

i. The State shall provide Level One Help Desk support. The list of authorized State personnel to call the Contractor’s help desk shall be provided to the Contractor. The Contractor’s help desk, or technical support personnel, shall be knowledgeable and technically trained to answer/resolve TITAN system technical support problems;

ii. When authorized State personnel call the Contractor’s help desk, or technical support, the Contractor's technical support staff shall not place the State caller on hold for more than five (5) minutes;

iii. If investigation and research is required by the Contractor’s technical staff and the problem cannot be resolved or question answered immediately, then the Contractor’s help desk, or technical support staff, shall call back within two (2) hours to report progress on the problem's resolution. The Contractor’s help desk staff shall, on a daily basis, or other basis agreed upon between the State and Contractor, to keep the State designated personnel informed on the progress of the problem's resolution; and

iv. The Contractor shall keep a log of all maintenance and technical support calls made to the Contractor’s help desk, or technical support, personnel.

The log shall document the complaints and problems reported to the Contractor’s help desk system by the State.

(5) Maintenance

i. The Contractor shall provide TITAN system maintenance (e.g.

enhancements, new releases, etc.) and technical support for all products and services provided. This maintenance shall include ongoing unlimited telephone technical support problem determination and resolution;

ii. The Contractor shall provide to the State all improvements and additions to the functionality, as well as new functions, of the TITAN and provide maintenance services;

iii. TITAN System Maintenance shall also include all services necessary to assist the State in maintaining the TITAN system’s operational uptime and recovery from failures;

iv. The Contractor, at a minimum, shall also be responsible for the detection and correction of TITAN system errors according to the specifications described herein and in the Contractor's documentation of the software and the implementation of all program changes, TITAN system configuration, new releases/updates, upgrades, enhancements, new versions, and implementation of additional programs provided under this Contract discovered by the State or otherwise made known to the Contractor. The Contractor agrees to respond to the State inquiries regarding the use and functionality of the solution as issues are encountered by TITAN users;

v. The Contractor shall be proactive in monitoring the TITAN system and not rely solely on the State to notify the Contractor of systematic problems, including implementation of automated system alerts to monitor for system outages, failed processes or jobs, and other server activities;

vi. The Contractor shall provide diagnostic support working within the

State’s security guidelines;

vii. Performance Monitoring and Tuning Utilities: TITAN shall continue to…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .