This is a Requirements Document (Attachment 1) from the Franchise Tax Board (FTB) detailing the business and technical requirements for a Data Archive Solution. The document outlines comprehensive specifications for a system that must be capable of searching, retrieving, viewing, and printing archived taxpayer data using various search criteria including Taxpayer ID, Social Security Number, Individual Taxpayer ID Number, name, address, and Payment Document Locator Number. The system must interface with FTB's existing infrastructure, support DB2 on AIX or SQL Server relational databases, and provide one-second response times for simple data retrievals.
The technical requirements specify that the system must maintain data referential integrity, guard against data loss, adhere to FTB's Data Management Policies, and meet various security standards including NIST SP 800-53 and FTB Information Security Standards. The solution must be ADA compliant, scalable, and customizable. Key operational features include the ability to archive data both individually and in batch processes, create reports, implement special holds on data purging, and add metadata annotations. The system must also enforce attribute-based access controls and comply with State Administrative Manual Chapter 5300 requirements.
The file's text, extracted by GovTribe without its formatting.
ATTACHMENT 1
FRANCHISE TAX BOARD
DATA ARCHIVE SOLUTION
BUSINESS AND TECHNICAL REQUIREMENTS
Identifier
General Questions
Information Provided
Yes
No
1
Data Archive Solution Documentation
1.1
Provide the name and version of the system (hardware/software) being described in the response to this RFI.
|_|
|_|
1.2
Describe any minimum facility requirements that must be met prior to installation.
|_|
|_|
1.3
Describe your typical implementation plan? Include the length of time your engineers would be onsite and the scope of work they would perform.
|_|
|_|
1.4
Describe any system and training materials to be provided and in what format.
|_|
|_|
1.5
Provide any other documentation that would distinguish your products and services in this market and would be relevant to this RFI.
|_|
|_|
Identifier
Requirement Description
Meets Req.?
Yes
No
2
Business and Technical Requirements of the data archive solution
2.1
The data archive solution must include the following alternatives of search criteria, from which a user could select one or more to locate a taxpayer's archived data:
· The taxpayer's Taxpayer Identification Number (TPID)
|_|
|_|
· The taxpayer's Social Security Number (SSN),
|_|
|_|
· The taxpayer' s Individual Taxpayer Identification Number (ITIN),
|_|
|_|
· The taxpayer's name,
|_|
|_|
· The taxpayer's address.
|_|
|_|
· Payment Document Locator Number (DLN)
|_|
|_|
2.2
Once a taxpayer's search criterion is entered, the data archive solution must allow the user to identify the specific tax year's data to be viewed.
|_|
|_|
2.3
The data archive solution must have the ability for the user to view and print the archived data by each taxpayer and each individual tax year.
|_|
|_|
2.4
The data archive solution must have export capability in a file format compatible with a Windows based computer.
|_|
|_|
2.5
The data archive solution must have the ability to directly interface with FTB's existing infrastructure.
|_|
|_|
2.6
The data archive solution must move data from a production database to a separate database.
|_|
|_|
2.7
The data archive solution must support the separate database as the archive repository.
|_|
|_|
2.8
The data archive solution must support DB2 on AIX or SQL Server relational database format.
|_|
|_|
2.9
The data archive solution must maintain data referential integrity and must utilize constraints, triggers, rules, and defaults to enforce such data referential integrity.
|_|
|_|
2.10
The data archive solution must receive and maintain data that is identical to the data existing in the source systems from which the data was received.
|_|
|_|
2.11
The data archive solution must guard against loss of accuracy, support validation rules, and produce validation reports that can be used for compliance and auditing.
|_|
|_|
2.12
The data archive solution must adhere to FTB's Data Management Policies, Procedures, and Guidelines.
|_|
|_|
2.13
The data archive solution must be capable of receiving data from its existing source to the archive database based on predefined rules and predefined schedules.
|_|
|_|
2.14
The data archive solution must purge the archived data from the data archive solution based on predefined rules and predefined schedules.
|_|
|_|
2.15
The data archive solution must provide users access to simple retrievals of data within one second of the request.
|_|
|_|
2.16
The data archive solution must allow for the ability to archive data on a one-to-one account or through batch processing.
|_|
|_|
2.17
The data archive solution must allow the users the ability to search, query, and create reports from the archived data.
|_|
|_|
2.18
The data archive solution must produce reports showing the status of jobs, current application status, and historical archiving activity.
|_|
|_|
2.19
The data archive solution must allow for a "special hold" that suspends the purging process of the archived data from the archive solution.
|_|
|_|
2.20
The data archive solution must allow for the ability to add metadata (annotations or tags) that explains the basis for the "special hold" that suspends the purging process.
|_|
|_|
2.21
The data archive solution must be ADA (American Disabilities Act) compliant.
|_|
|_|
2.22
The data archive solution must be scalable and customizable to other types of data
|_|
|_|
2.23
The data archive solution must allow for attribute and/or rules based access (authorization process) specified by FTB.
|_|
|_|
2.24
The data archive solution must meet FTB's System Access Security Requirements. (Refer to Attachment 3, Links to Security Guidelines and Standards Manuals.)
|_|
|_|
2.25
The data archive solution must meet FTB's Security Audit Requirements as described in the Department's Information Security Policy File (ISP), section 9500. (Refer to Attachment 3.)
|_|
|_|
2.26
The data archive solution must comply with applicable State Policy found in the State Administrative Manual, Chapter 5300. (Refer to Attachment 3.)
|_|
|_|
2.27
The data archive solution must adhere to the National Institute of Standards and Technology Special Publication (SP) 800-53 (Moderate Controls), NIST SP 800-144. (Refer to Attachment 3.)
|_|
|_|
2.28
The data archive solution must comply with all applicable policies and standards in the FTB ISP and the FTB Information Security Standards. (Refer to Attachment 3.)
|_|
|_|
File details come from the government source that posted it.
Updated .