Worksheet ID: |
1414 |
Record Location: |
James K. Polk Building, Suite 300
505 Deaderick Street
Nashville, TN 37243 |
File Arrangement: |
Chronological |
Media Format Generated: |
Electronic |
Media Format Stored: |
Electronic: Sconpreadsheet/Database |
Date Range: |
1998 to current |
Annual Accumulation: |
4 GB |
Current Volume: |
40 GB |
Record Value: |
Administrative, Fiscal |
Audit Requirements: |
State |
Reference Frequency: |
Current Year per Month: |
1 |
Past Year: |
2 |
2 - 5 Years: |
2 |
Over 5 Years:
|
0 |
|
Data Update Frequency: |
Daily |
Information Shared Outside of State: |
Yes |
If Shared, List Agencies: |
US Department of Transportation. |
Essential Record: |
Yes - Original |
Essential Record Stored: |
South Data Center - OIR |
Essential Record Media Type: |
Electronic |
Confidential: |
No |
Confidential Legal Citation: |
|
Media Recommendation: |
Current Format |
Media Recommendation Other: |
|
Agency Retention: |
5 years |
Agency Retention - Years Active: |
|
Agency Retention - Years Inactive: |
|
Records Center Retention Period: |
None |
Final Disposition after Retention Expires: |
Destroy |
Legal Citation: |
|
Record Sample: |
No Sample |
Legal Documentation: |
No Legal Documentation |
Electronic Records Plan Inventory |
System Name: |
Tennessee Oversize Overweight Permitting System (TOOPS) on the Oracle Application Server JJ01SDCWA00019 |
IT-ABC Number: |
|
Hardware Description: |
The Tennessee Oversize Overweight Permitting System is an Oracle application which is housed on The Oracle Application Server which physically resides and runs on an HP DL360 class server. |
Software Description: |
The Tennessee Oversize Overweight Permitting System is an Oracle application which is housed on The Oracle Application Server which currently runs Microsoft Server 2008 R2 as an operating system with the OAS running 11G. |
System Location: |
The Tennessee Oversize Overweight Permitting System is an Oracle application which is housed on The Oracle Application Server which resides at OIR’s South Data Center, located in Smyrna Tennessee, and hosts the servers that will be utilized for the storage to comply with both the Statewide and TDOT Electronic Records Policy. |
Backup Procedures: |
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 |
Disaster Recovery: |
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. |
Metadata Description: |
Content Subject/Title: Tennessee Overdimensional & Overweight Permits - Record of Overdimensional & Overweight
permits issued to trucking companies
transporting cargo through Tennessee.
Date Created: October 10, 1998
Format: This is a dynamic Oracle Database, and the data resides in an Oracle .dbf format.
Content Size: 40 GB
Location: South Data Center, located in Smyrna Tennessee on the Tennessee Oversize Overweight Permitting System (TOOPS) on the Oracle Application Server JJ01SDCWA00019 |