Questions_and_Answers_02-19-2016_.docx
DOCX document 21 KB Posted
- Attached to
- RFI FTB-1516-Data Archive Solution
- Solicitation number
- 0000000398
- Issued by
- California
About this file
This is a Question and Answer document for a Data Archive Solution RFI (FTB-1516) issued by the State of California's Franchise Tax Board (FTB). The RFI seeks information about solutions for archiving approximately 1 TB of structured data from AIX DB2 and Sybase ASE databases on HP-UX systems. The solution must be on-premise and run on distributed server platforms (UNIX, Linux, or Windows). The data retention requirement is 13 years, and the solution must support DB2 on AIX or SQL Server relational database formats. While no specific procurement timeline is provided, respondents are asked to provide pricing estimates for three fiscal years: July 1, 2016 through June 30, 2019.
There is currently no incumbent vendor or existing archiving solution in place. The primary purpose is to free up space and enhance performance in legacy systems. The solution requires both data in transit and at rest encryption, must maintain system data for audit purposes, and have data integrity compliance. The solution must be scalable to accommodate future unstructured data types, though current requirements only involve structured data. Offshore services are not permitted, and while disaster recovery and replication are not required, they may be considered as additional features. The solution does not need to support Hadoop Distributed File System or Big Data requirements.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| RFI_Attachment_2.docx | DOCX document | |
| Data_Archiving_RFI__2-11-16.docx | DOCX document | |
| RFI_Attachment_1.docx | DOCX document | |
| RFI_Attachment_3.docx | DOCX document |
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
RFI FTB-1516-Data Archive Solution Questions and Answers
1. What database types does the data reside in (i.e. DB2, Oracle, SQL Server, etc)?
The data to be archived resides in AIX DB2 and Sybase ASE on HP-UX. See Section C. FTB Existing Infrastructure for additional information contained in the RFI. Attachment 2, Identifier 2.8, provides that the data archive solution must support DB2 on AIX or SQL Server relational database format.
1. Is there an incumbent vendor or company providing these products/services for the State of California? And if there is, which vendor is it?
There is no archiving solution at this time.
1. Does this agency of the State of California own a specific SQL gateway or connector to accomplish the tasks specified?
See Section C. FTB Existing Infrastructure for additional information contained in the RFI.
4) What is the timeframe for procuring the product and services to accomplish this task?
There is no timeframe for procuring the product and services to accomplish this task. However, for purposes of completing Attachment 2, RFI Response Format/Additional Information, Question #1, assume that the Non-binding Budgetary Pricing Table commences July 1, 2016 through June 30, 2017 for “Year 1”; July 1, 2017 through June 30, 2018 for “Year 2”; and July 1, 2018 through June 30, 2019 for “Year 3”.
5) Would offshore services be considered to accomplish these tasks or must they be on the premises of the State of California?
No, the data solution must be on premise.
6) Is the data to be archived located on tape primarily or on other media? Could you give us a percentage on tape?
No, this data will not be on tape. It will be from the databases.
7) Is there unstructured data that will be part of the data to be archived? Or is it all data structured in existing applications?
There is no unstructured data that will be part of the data to be archived. The data is structured in existing applications.
8) Could the State of California provide prospective responders with an existing data model that would help define how the data is to be archived?
No, this information is proprietary.
9) We understand your request for a budgetary price quote for our software to archive 1 TB of data. Can you please clarify whether the 1TB of data should be assumed to reside on your mainframe server, or on your distributed servers, or on a combination of the two?
The data is not on the mainframe server. The data will either reside on a Windows server or an AIX server.
10) How many different databases should we assume contain the estimated 1 TB of data to be archived? Of these databases, how many reside on the mainframe, and how many on distributed servers?
The data to be archived resides in AIX DB2 and Sybase ASE on HP-UX.
11) Our software runs on both mainframe and distributed servers, with a modest footprint. Can we assume that there is room on your existing mainframe and/or on existing distributed servers for our software to be installed?
The Solution needs to run on distributed server platform (UNIX, Linux, or Windows). If you do not provide hardware costs, please provide compute requirements of your solution.
12) Is there any archiving solution in place at this time, or is all content currently in production use?
No, there is no archiving solution in place at this time.
13) Is the purpose of archiving primarily to decommission legacy systems, or to free up space and enhance performance on existing systems? Or both?
Yes, the purpose is to free up space and enhance performance in our legacy systems.
14) What is the Current Tax System?
To the extent that the RFI does not cover the current tax system, the information is proprietary.
15) Although the pricing request requests quantity 1TB pricing, how much total data does FTB foresee archiving on an annual basis?
For purposes of the data archive solution, FTB asked respondents to use 1 TB of volume for structured data. FTB requests that all responses focus on total volume of 1 TB.
16) Going forward how much data will be archived daily / weekly / monthly / quarterly or yearly?
The schedule for archiving has not been determined yet.
17) How many searches are expected per day based on the search criteria listed in the RFI?
The searches would be infrequent.
18) Is data at rest encryption required?
For purposes of this RFI, encryption of data in transit and encryption of data at rest are required. For more information, please review RFI FTB-1516 Data Archive Solution, Attachment 3, and the following links:
Internal Revenue Service Publication 1075 Tax Information Security Guidelines for Federal, State, and local Agencies and Entities <http://www.irs.gov/pub/irs-pdf/p1075.pdf>
Federal Information Processing Standards (FIPS) <http://www.itl.nist.gov/fipspubs/>
Federal Information Processing Standards (FIPS) Publication 200 Minimum Security Requirements for Federal Information and Information Systems <http://csrc.nist.gov/publications/fips/fips200/FIPS-200-final-march.pdf>
Federal Information Processing Standards (FIPS) Publication 140 Security Requirements for Cryptographic Modules <http://csrc.nist.gov/publications/fips/fips140-2/fips1402.pdf>
National Institute of Standards and Technology (NIST) Publication 199 http://csrc.nist.gov/publications/fips/fips199/FIPS-PUB-199-final.pdf
National Institute of Standards and Technology (NIST) - http://csrc.nist.gov/publications/nistpubs/800-53-rev4/sp800-53r4_summary.pdf National Institute of Standards and Technology (NIST) - http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf
19) Is there a requirement to maintain system data such as “date created”, “date modified”, “user name”, “last accessed” information – in addition to the metadata itself – as part of the system? i.e. Chain of Custody information for audit purposes?
Yes, there is a requirement to maintain system data. See Attachment 1, Identifier 2.18, 2.24, and 2.25
20) Is there any requirement now, or in the perceivable future for the archiving of unstructured data/content (scanned images, PDFs, etc)? Ensuring the proper relationships between the structured and unstructured data is maintained?
In terms of unstructured data, the only requirement is that it be scalable to allow for other types of data in the future.
21) Does the Data Archive solution have a data integrity compliance requirement such as Erasure Encoding?
Yes, the Data Archive Solution should have a data integrity compliance requirement.
22) What is the data retention requirement? Similarly, is there a WORM requirement?
The data retention requirement would be for 13 years.
No, there isn’t a WORM requirement.
23) What are the data protection requirements for replication and disaster recovery?
For RFI purposes, the data protection replication and disaster recovery are not requirements; but, may be considered as an additional feature.
24) Does the Data Archive solution need to support Hadoop Distributed File System (HDFS) protocol? Is there a Big Data requirement?
No, the Data Archive solution does not need to support the Hadoop Distributed File System (HDFS) protocol and there is no requirement for Big Data.
File details come from the government source that posted it. Updated .