Record Series Abstract
Documents relating to Pavement Design for projects processed through the Pavement Design Office of the Roadway Design Division. The Pavement Design records will include the following: Pavement Design Request Form, Traffic, Soils & Field Data, Pavement Design, and related correspondence (emails, letters, and scanned copies of designer notes) and other related documents.
Record Series Active
Cut Off at End of
If Other, Explain
Until Structure is destroyed or replaced.
Total Retention Years
Total Retention Months
Retention End Action
After Cut-off: Designer shall place all electronic files containing the Pavement Design records into Filenet. After files are added to Filenet, paper copies will be destroyed. Maintain five years after cut off and then destroy by state approved methods.
Roadway Design Division, Suite 1300, James K. Polk Building Nashville, TN 37243
1917 - current (approximate begin date)
45 cu ft., 4 GB
182 cu ft., 686 GB
Information Shared Outside the State
Federal Highway Administration & Consultant Engineers (When Requested)
Essential Record Stored
Essential Record Media Type
Does this Record Series Contain Sensitive Information?
Retention Legal Citation
Filenet - TDOT Roadway Design
Roadway Design files are on the FileNet server which is housed in a Clustered Enterprise SQL 2008 Environment utilizing these devices: Filenet Content Engines - HP DL580G7 32Proc 128 GIG Ram X 3 boxes Filenet Process Engines - 2 farmed VM boxes against the F5 load balancer FileNet Application Engines - 2 farmed VM boxes against the F5 load balancer with a Hitachi HDI/HCAP Content Platform for data replication to the South Data Center.
Roadway Design files are on the FileNet servers which run Windows Server 2008 Enterprise 64-Bit R2 or later with these software packages for each portion of the enterprise software application: FileNet Content Engine 4.5.1 Fix pack 7 FileNet Process Engine 4.5.1 Fix Pack 2 FileNet Application Engine/WorkplaceXT 115.2 FileNet InfoSphere Enterprise Records 4.5.1 Fix pack 2 IBM Websphere 7.0 Fix Pack 27 IBM HTTP Server 7.0.
OIR's South Data Center, located in Smyrna Tennessee, hosts the servers that will be utilized for the storage to comply with both the Statewide and TDOT Electronic Records Policy.
OIR will conduct backup procedures. These procedures consist of daily incremental backups and weekly total backups on the weekend. The back-up servers are Hitachi and EMC SANs. The process for Backing Up the data from OIR's South Data Center is to mirror the information at OIR's North Data Center, and then create a weekly backup tape that is currently stored by the Vendor: Iron Mountain Incorporated Iron Mountain Nashville 6005 Dana Way Nashville, TN 37013 800-899-4766.
OIR conducts disaster recovery. This procedure is a prioritized process of enabling critical and essential applications first and then continuing through the priority list to less significant applications. Disaster Recovery begins with the utilization of the OIR's North Data Center for both operations and data. If both OIR's South Data Center and OIR's North Data Center are out of operation, new operations will begin by acquiring appropriate hardware and software from a third party supplier, and restoring data from the offline tape backups stored with the current vendor: Iron Mountain Incorporated.
Data Migration Description
Data Migration will occur when support for the existing file format moves from Current to Twilight or Obsolete, or when software or hardware systems changes require the movement of RDA electronic data from a specified format to a different file format. Annual reviews will be conducted by the TDOT Records Officer and the TDOT IT Director in accordance with the Section 3 of the TDOT ERP. Additionally, the TDOT IT Director will provide information and guidance to the TDOT Records Officer at the time of discovery regarding functional and operational performance of software and hardware that will change the status of file formats from Current to Twilight or Obsolete. The annual review process of file formats status and the level of in those file formats confidence, with regards to specific RDA retention requirements, will result in the generation of a File Type Confidence Report. Time for measuring the required three year limit for migration completion of affected data will begin at the time of discovery of the file format status change to Twilight or Obsolete, even if it is outside the annual review where it is reported with time remaining. The TDOT IT Director will advise and develop a solution to move the data to a Current file format that is appropriate to the RDA retention requirement for the specific data. This may include translation of the data to a Current file format, conversion to an acceptable Current File format to preserve the integrity of the information of the data, or movement of the data to a legacy architecture that maintains the environment where the file format is considered Current as long as this effort has full functional and operational support.
Legacy Revision UUID