VI. SYSTEM REQUIREMENTS SPECIFICATION

 

A.      Introduction

This System Requirements Specification Section is used to define CA SFIS requirements between the State and the successful CA SFIS Bidder. This section includes the non-administrative and technical specifications for the California Statewide Fingerprint Imaging System (CA SFIS).

1.         Scope

The requirements identified in this section apply to primary functions, major supporting functions, processes, and operations of the CA SFIS.

2.         Organization

This Section VI is organized as follows:

Subsection A

Introduction: Identifies the purpose, scope, document format, and applicable standards for this specification

Subsection B

CA SFIS Design Requirements

Subsection C

Specific Remote Workstation Requirements

Subsection D

Specific Central Site Requirements

Subsection E

Database Capacity

Subsection F

Workload & Response Time Requirements

Subsection G

System Accuracy Requirements

Subsection H

Use of the State’s Communication Network

Subsection I

Back Up & Recovery Requirements

Subsection J

System Reliability Requirements.

Subsection K

System Installation

3.         Applicable References

The following sources were used to compile the requirements contained in this specification:

o        American National Standard ANSI/NIST-CSL 1-1993 (or latest version)

o        FBI/CJIS Fingerprint Image Transmission Specification 1995 (or latest version)

o        ISO 9000 Development & Documentation Standards (latest version)

o        Wavelets WSQ Compression Algorithm (latest version)

o        American Association of Motor Vehicle Administrators (AAMVA) standards for resolution of photo images (latest version)

o        Federal Information Processing Standard (FIPS) 4-1

o        Underwriters Laboratory (UL) Standards for Operator Safety

o        Americans with Disabilities Act (ADA) Regulations for Accessibility

4.         Work Requirements

[Mandatory] Bidder shall furnish all equipment, software, material, services, cabling, wiring and install and maintain an operational Statewide Fingerprint Imaging System (CA SFIS) in accordance with the requirements of this RFP.

B.      Design Requirements

1.         General Design Requirements

1.         [Mandatory] The proposed system must already be successfully established and in production in another location although not necessarily in a welfare or social services environment. The Bidder will be required to perform pre-contract Demonstrations.

2.         [Mandatory] The proposed system’s basic design must follow the principles of an OPEN SYSTEMS design.

3.         The proposed system should not rely on proprietary hardware, software, or procedures. Wherever possible, Commercial-Off-The -Shelf (COTS) products should be incorporated into the design of the system (e.g., RDBMS, operating system, etc.).

4.         [Mandatory] The CA SFIS design must provide Workstations to collect, store, print, transmit and access stored fingerprint images and defined associated client and control information as well as photo images.

5.         [Mandatory] The primary index number for every record in the CA SFIS database will be the CIN (Statewide Client Index Number). In addition, every search transaction input at one of the remote workstations must be tracked by a unique Process Control Number (PCN). The PCN must be assigned by the workstation. The system must track all PCN’s associated with a CIN number. Additionally, each CA SFIS record will have multiple Social Security Number (SSN) fields and Local Identification Number (LIN) fields; one CA SFIS record may have more than one SSN and/or more than one LIN associated with the record. The SSN and LIN fields must be indexed within the relational database manager system (RDBMS) used in the CA SFIS. The CA SFIS must retrieve any CA SFIS record based solely on a CIN, PCN, SSN, or LIN search; in the case of a SSN or LIN search, more than one record may be returned per SSN or LIN. Only the CIN and, as designed by the Contractor, the PCN are guaranteed to be unique numbers. A particular SSN and/or LIN may be duplicated within more than one CA SFIS record; therefore, if a record search is made using SSN or LIN, there is the possibility that more than one CA SFIS record can be returned as a result of the search.

6.         [Mandatory] The CA SFIS design must provide both an OPEN and a CLOSED search capability.

7.         Search Delimiters

7.a.       For the purposes of expediting match/no-match reporting and reducing the business hour transaction processing load, the CA SFIS design should allow the capability of executing parameter driven fingerprint image searches.

7.b.       [Mandatory] If the Bidder elects to use demographic parameters and/or fingerprint image-related parameters to narrow any given search to a specific subset or subsets of the CA SFIS finger image database, the Bidder shall be limited to

o        the use of Sex, and/or

o        any data that the Bidders proposed system can derive directly from the fingerprint image(s) by either automatic and/or manual methods.

7.c.       [Mandatory] If the Bidder elects to use sex as a database delimiter, the Bidder must assume that:

o        in 99% of all transactions, the sex of the client will be known; and,

o        in 1% of all transactions, the sex of the client will be unknown.

7.d.       [Mandatory] If sex is used to determine database penetration, the Bidder must assume that 59.5% of the searched database is female, 39.5% male, and 1% unknown sex. In addition, the Bidder must assume that each search will be conducted against the same-sex records in the database plus all unknown sex records in the database.

7.e.       If data derived from the fingerprint image(s) is used to determine database penetration, the Bidder may use any data that the Bidder’s proposed system can derive directly from the fingerprint image(s) by either automatic and/or manual methods.

7.f.        [Mandatory] Bidders must not assume that the County or State workstation operator will have any role whatsoever in the determination and/or assignment of fingerprint image data.

7.g.       [Mandatory] If the Bidder elects to use any combination of sex and/or fingerprint image-derived data to limit the number of records actually matched per search the Bidder must

o        describe how the proposed system is in compliance with the search accuracy and response time requirements of this RFP (Requirements VI.G. and VI.F.);

o        specify the average penetration rate that is expected to be used by their proposed system; and,

o        fully describe all calculations that were made to arrive at the penetration rate specified.

8.         [Mandatory] The CA SFIS system must record the parameters selected (and/or derived from the image) to execute each search; this information must be compiled, stored, and made available for audit trail purposes and system reports.

9.         [Mandatory] If the Bidder elects to use Sex as a search delimiter, the proposed CA SFIS must have the capability to automatically search all records of one sex against records of the other sex for all records input during a given day; this CROSS-GENDER SEARCH operation may occur at any time except when the operation conflicts with the normal workflow of the system (i.e., "Daily Application" input and /or "Existing Caseload" input). All records input on any given day must be CROSS-GENDER SEARCHed by 7AM of the next business day. If the CROSS-GENDER SEARCH operation results in a "Hit," the system must automatically change the sex of the retained record to "Unknown."

10.        Deleted.

11.        [Mandatory] The proposed system must exchange information electronically with the State’s Statewide Automated Welfare System Technical Architecture (SAWS TA) database.

12.        [Mandatory] The system must provide for an expansion to at least twice the number of transactions per day (as defined in Table IV.E.1., Month 65) and an expansion to at least twice the number of records stored in it’s database (as defined in Table IV.E.1., Month 65) without affecting performance in terms of system accuracy or the capability of handling progressively increasing volumes of transactions, stored records, and additional workstations.

13.        [Mandatory] The proposed system must include appropriate internal controls, quality assurance, indexing, security and other features so that it can be demonstrated that the CA SFIS fingerprint images and photographs represent an accurate facsimile of the originals, and that rigid security criteria have been met in their capture, storage and reproduction.

14.        [Mandatory] Data Integrity: The CA SFIS must ensure that all data elements of each client record (e.g., the two fingerprint images, the photo, the CIN, control information, and demographics) are properly linked. The Bidder’s Proposal must include a description of the method to be used to ensure record synchronization.

15.        [Mandatory] In addition to performing the new application record transactions, the system must be capable of on-line update, inquiry, and match verification transactions of existing client record and control information. Update, inquiry, and match verification functions will be processed via the workstations by key identifier(s) to be determined during system design (e.g., CIN number). The system must also process a delete transaction received from the Statewide Automated Welfare System Technical Architecture (SAWS TA) system via a CA SFIS-SAWS TA link.

16.        [Mandatory] The CA SFIS must perform data validation checks at the character, field, and transaction levels.

17.        [Mandatory] The CA SFIS design must provide the ability to trace all transactions from the point of inception, through intermediate processing stages, to final disposition. The current state of any operator-initiated transaction must be available on-line for a real time display of the transaction state. Once initiated and for as long as the operator leaves the display on-screen, the display must reflect the real-time status of the transaction. In addition, the processing history of all transactions (including current or final overall processing time, queues entered, time that transaction entered and was removed from each queue, etc.) must be tracked by the CA SFIS relational database engine; all data must be available for use in State-defined reports. Details of the data tracked and the design of associated reports will be defined and approved by the State during the System design phase of the CA SFIS project.

18.        [Mandatory] The CA SFIS design must provide file backup and recovery capabilities to restore damaged files. See Section VI.I.

19.        [Mandatory] The CA SFIS design must provide System restart procedures which ensure no loss of data entered.

20.        [Mandatory] The CA SFIS must maintain transaction logs to assist in recovery of data files.

21.        [Mandatory] The CA SFIS must provide for periodic changes to user passwords.

22.        [Mandatory] The CA SFIS must provide the ability to define an access category relating to groups of users (e.g., Terminal Operator, System Monitor, Auditor, etc.).

23.        [Mandatory] The CA SFIS must provide audit trail reports as to terminal operator ID, time, date, data input, data revised, and transactions (as performed).

24.        [Mandatory (all paragraphs)] Data Collection Requirements: Data will be captured for each client consisting of client identifying and control information, both right hand and left hand fingerprint images via direct live scan readers, and a color photo. Each client record will consist of:

a.         A Client Index Number (CIN); the CIN will be the primary index number to all CA SFIS records. The CA SFIS will also keep (when available) Social Security Numbers (SSNs) and Local Identification Numbers (LINs) for each record; the SSN and LIN fields must be indexed for fast retrieval of records based on a SSN or LIN search. Additionally, each record will contain a list of Process Control Numbers (PCNs) associated with the client; the PCN field must be indexed for fast retrieval of records based on a PCN search.

b.         A flat (not rolled, not nail-to-nail) fingerprint image of each index finger will be captured. The print definition must at least meet current ANSI/NIST - CSL 1-1993 standards for a high resolution image. All fingerprint images will be entered via a direct read of untreated and reasonably clean fingers. The Live Scan equipment used to capture the fingerprint image must meet requirement VI.B.4. (Live Scan Requirements).

c.         A color photo image of the applicant/client will be captured by equipment integrated into or connected to the workstation, so that a digitized photo image of the applicant/client can be incorporated into the CA SFIS data base.

d.         Color photos will be captured by the operator, automatically digitized, with no requirement for special conversion operations by the operator.

e.         The system must provide the capability to input client record and control information (name, DOB, sex, etc.) by keyboard via the CA SFIS workstation. For purposes of this RFP, it should be assumed that the record will contain up to 30 fields containing no more than a total of 600 characters (plus a "free text" field of up to 200 characters as specified in paragraph g., below). The final record description will be determined by the State during system design.

f.          Upon operator acceptance of input, the workstation must automatically generate additional control information (date, time, workstation, id, etc.). This information will construct a unique system-wide record identifier (PCN). Automatically generated information will be specified during the system design.

g.         The system must provide the capability to input a "free text" field attached to each client record. This text field will be used to record operator comments. The text field must be sized to accommodate up to 200 ASCII characters (in addition to the requirement stated in paragraph e., above). The "free text" field must be capable of being updated at any time.

25.        [Mandatory] The CA SFIS must automatically replace poor quality fingerprint images with fingerprint images of better quality when a match between the search record and a database record is detected and validated. In addition, when the fingerprint images in the database record are from the converted AFIRM database, the CA SFIS must automatically replace the AFIRM fingerprint images with the search record fingerprint images if the quality of the search images are above a certain (to be determined) quality threshold. In either case, the system must log the replacement transaction and provide the capability to report all replacement transactions. All replaced fingerprint images will be written to off-line storage.

26.        [Mandatory] The CA SFIS must automatically store the most recent photo image of an individual (unless overridden by the operator). The operator must also have the capability of making an on-screen indication that the photo image must be retaken at a later date.

27.        [Mandatory] The CA SFIS must provide the capability to restrict the CA SFIS transactions which can be performed at any specified workstation, group of workstations, operator, or operator classification. The transaction-type permission table must be controlled by the State CA SFIS Project Manager or designated representative from a central point with a minimum of difficulty (Bidders must describe how this will be accomplished). Access to the transaction-type permission table must be limited to the State CA SFIS Project Manager or designated representative.

28.        [Mandatory] The system shall use queues for temporary storage of records and images during processing. Transactions shall be queued according to priority and released for processing automatically as required by the transaction controller. The system shall process transactions when they are entered, and shall handle each request on a first-in, first-out basis within each priority level. The priority of an individual transaction must be modifiable while the system is running. The capability to effect a priority modification must be restricted to any County or State operator who has the appropriate permission level.

29.        [Mandatory] The system shall provide inquiry information about any queue’s status; this information shall be provided for all transactions in the queue, and/or for all transactions within the queue that pertain to a particular site, and/or for all transactions within the queue that pertain to a particular operator.

30.        [Mandatory] The system shall provide the feature whereby the authority to assign any given priority level can be restricted to certain operators. Operators invested with the authority to assign a particular priority level shall be assigned by the State CA SFIS Project Manager.

31.        [Mandatory] The system shall provide a dynamic, real-time display of the transaction activity of the system queues. Once initiated and for as long as the operator leaves the display on-screen, the system queue transaction activity display shall be automatically updated by the system at (a minimum of) 5 second intervals. The system queue transaction activity display shall be available for display at any time on any workstation in the system.

32.        [Mandatory] The CA SFIS must provide the capability to perform a CLOSED SEARCH comparison of any two records in the CA SFIS database that are specified by the workstation operator; the results of this match request must be displayed at the workstation that requested the match and must be printed on the printer assigned to that workstation.

33.        [Mandatory] The CA SFIS must provide the capability to perform a CLOSED SEARCH comparison of an input record captured at the workstation and any operator-specified record in the CA SFIS database; the results of this match request must be displayed at the workstation that requested the match and must be printed on the printer assigned to that workstation.

34.        [Mandatory] The CA SFIS must provide the capability to perform two types of OPEN SEARCH requests; Inquire Only and Inquire Plus Store. The Inquire Plus Store request will conclude with an automatic ADD to the CA SFIS database if the search results in a "No-Hit." If the Inquire Only request is used, the operator must be given the option of either adding the record to the database after a "No-Hit" search verification result or ending the transaction without adding the record to the database. Normally, the Inquire Plus Store OPEN SEARCH will be performed by the system as a default option; the Inquire Only OPEN SEARCH will be performed only if specifically requested by the workstation operator. The results of either type of transaction must be made available for display at the workstation that initiated the transaction and must be printed on the printer assigned to that workstation.

35.        [Mandatory] The proposed CA SFIS must be Year 2000 compliant as per the Federal Information Processing Standard (FIPS) 4-1 and international standard ISO 8601:1988.

36.        [Mandatory] The Bidder will be required to provide additional workstations, if necessary, so that the entire current caseload of clients can be finger imaged and photographed and the data loaded into the database (See Section IV for information on "Existing Caseload" requirements). At the end of the database load of existing clients, the additional equipment shall be removed by the contractor at no cost to the State.

 

37.        [Mandatory] The design of the system must incorporate a relational database management system (RDBMS) that will track all records in the CA SFIS. In addition, the RDBMS must record all transactions, and the parameters and data contained within each transaction. The RDBMS must produce reports (to be determined by the State during the Detailed Design phase of the CA SFIS project) based on data contained in the client records and the transaction records. The RDBMS must produce SQL-compliant database tables that can be used by any (external) SQL-compliant RDBMS application.

38.        [Mandatory] The Bidder must describe the design and architecture of the proposed CA SFIS. Each major component and subsystem of the proposed CA SFIS must be fully described (where applicable) with respect to the following: integration of the subsystem and/or component into the overall design of the CA SFIS; number of each component used in the configuration; input, output, and throughput capabilities of the system; system limitations; effect on the operation of the overall CA SFIS in the case of component and/or subsystem failure; data backup; transaction management and transaction logging; queue management; etc.

The State is especially interested in additional aspects of the following system components and subsystems:

o        Digital Image Retrieval Subsystem (DIRS) -- The Bidder must describe how the DIRS is designed to meet the response time and workload requirements of this RFP. The Bidder must provide MTBF (Mean Time Between Failure) and MTTR (Mean Time To Repair) calculations for the DIRS. The State desires that the proposed CA SFIS use RAID (Redundant Array of Independent Disks) technology in the DIRS for improved reliability of the CA SFIS.

o        Relational Database Management System (RDBMS) -- The Bidder must describe how the RDBMS is incorporated into the design of the CA SFIS. The Bidder must also describe how the RDBMS data tables are designed to meet the report generation requirements defined in this RFP.

o        Matching Subsystem(s) -- The Bidder must describe how the Matching Subsystem(s) is incorporated into the design of the system. The Bidder must fully describe how the Matching Subsystem(s) has been designed to meet the workload requirements of this RFP. In addition, the Bidder must fully describe the Matching Subsystem database design and the procedures for, and frequency of, database reorganization (if applicable).

o        HWDC Wide Area Network (WAN) -- The Bidder must describe the requirements for the architecture of the WAN and how the WAN must be configured to meet the CA SFIS throughput, response time and workload requirements of this RFP.

39.        [Mandatory] If the result of a CLOSED SEARCH match is a "Miss" (i.e., the system determines that two records are not the same as determined by a CLOSED SEARCH match process), the CA SFIS must provide the capability to automatically perform a CLOSED SEARCH comparison of the two records with the finger images in one of the records reversed. For example, if the system performs a CLOSED SEARCH match on Record A and Record B and the result is a "Miss," the system must automatically perform another CLOSED SEARCH comparing the right hand index finger of Record A with the left hand index finger of Record B and the left hand index finger of Record A with the right hand index finger of Record B. If the second (automatic) CLOSED SEARCH match is a "Hit," the system must report a "Hit" and also report the exceptional circumstances of the match. The purpose of this requirement is to detect those instances when the left and right index finger images have been captured out of sequence.

40.        [Mandatory] The CA SFIS must provide the capability to merge two (or more) records under one CIN. The command to make the merge will come from the CA SFIS-SAWS TA interface. A MERGE command will consist of (at least) the CIN’s to be merged and the CIN that will be assigned to the resulting record. When a MERGE command is given, the CA SFIS must ensure that all records referred to in the command relate to the same individual by initiating a CLOSED SEARCH for every pair of records in the MERGE command. If all CLOSED searches do not result in a "Hit," the MERGE command must be aborted with an error indication. If all CLOSED searches are successful, the system will complete the MERGE transaction and return an indication that the MERGE command was successfully completed.7 As part of the MERGE process, the CA SFIS must automatically identify the highest quality fingerprint images (i.e., highest quality right hand fingerprint images and highest quality left hand fingerprint images) out of the right and left hand set of all records that are to be merged; the final, merged record will contain the highest quality fingerprint images from each hand. In addition, if one (or more) of the merged records contains fingerprint images from the converted AFIRM database and (at least) one of the merged records contains fingerprint images that are not from the AFIRM database, the CA SFIS must automatically use the highest quality non-AFIRM fingerprint images in the final, merged data record if the quality of the search images are above a certain (to be determined) quality threshold.

41.        [Mandatory] The CA SFIS must provide the capability to change the CIN of any record within the CA SFIS database. This operation will be initiated by a transaction made by SAWS TA through the CA SFIS-SAWS TA interface (see Section IV.F.). It is anticipated that SAWS TA will supply two CINs in the CHANGE CIN transaction; the CIN of the record in the CA SFIS database that must be modified (CIN A), and the new CIN (CIN B). When this transaction is received by CA CFIS, CA SFIS will copy all data from CIN A to a new record identified as CIN B. The new (CIN B) record will also record the old CIN (CIN A) and the date that the record was modified. When the CIN B record has been successfully created, the CA SFIS will purge the CIN A record and send a "transaction complete" message to SAWS TA.

42.        [Mandatory] The CA SFIS must provide the capability to track all processing steps for all OPEN SEARCH and CLOSED SEARCH transactions. At least the following minimum data elements will be tracked:

OPEN SEARCH

o        ID of operator who submitted the search

o        time transaction was entered into the output queue of the Input Workstation (tracked at both the workstation and at the Central Site)

o        time transaction was entered into the input queue at the Central Site

o        time match process began

o        time match process ended

o        demographics used in the search

o        matcher subsystem result of the OPEN SEARCH (candidate CIN’s and match scores for at least the top 50 matches regardless of the "NO CANDIDATE" threshold)

o        ID of operator who performed the verification (unless there is a "NO CANDIDATE FOUND" match result)

o        verification result (CIN[s] of candidate[s] marked as "Hit")

o        details of fingerprint image update (if automatically performed by system)

o        time match result was transmitted to input site (tracked at both the workstation and at the Central Site)

CLOSED SEARCH

o        ID of operator who submitted the search

o        time transaction was entered into the output queue of the Input Workstation (tracked at both the workstation and at the Central Site)

o        time transaction was entered into the input queue at the Central Site

o        time match process began

o        time match process ended

o        demographics used in the search

o        result of the CLOSED SEARCH (CIN’s compared and match result [i.e., "Hit" or "No-Hit"])

o        ID of operator who performed the verification

o        verification result (i.e., "Hit" or "No-Hit")

o        details of fingerprint image update (if automatically performed by system)

o        time match result was transmitted to input site (tracked at both the workstation and at the Central Site)

43.        [Mandatory] The CA SFIS must provide the capability to maintain separate and distinct verification queues for CLOSED SEARCH "Hit" results, CLOSED SEARCH "No-Hit" search results, and OPEN SEARCH results. The purpose for this requirement is that the State wishes to monitor the workload and result of verifications; having separate queues for these three types of match results will facilitate the State’s monitoring effort.

44.        [Mandatory] The CA SFIS must provide the capability to produce a report listing all records that: 1., have fingerprint image data below a given image quality rating; 2., that are missing one or both fingerprints; 3., that are marked as bandaged; or 4., that have photo images marked as "retake" by the input operator. In addition, the CA SFIS must provide the capability to produce a report listing all records that have fingerprint images derived from the converted AFIRM data. The report will include at least the following data elements:

o        CIN of record

o        date record was created

o        site that submitted the record (or the designation "AFIRM" if the images were originally converted from AFIRM data)

o        CA SFIS input operator who submitted the record

o        quality rating of fingerprints or, if fingerprint is missing (e.g., bandaged), an indication as why the record is missing

o        rating of photo image ("acceptable" or "retake")

45.        [Mandatory] The CA SFIS must have the capability to measure response time at each CA SFIS workstation (see Section VI.F. for Response Time Requirements). Response times will be measured during system acceptance testing and regularly thereafter.

46.        [Mandatory] Every CA SFIS workstation must have a unique identification number that identifies it’s location for security, reporting, and troubleshooting purposes; this number must be physically marked on the workstation in such a manner as to be immediately visible to the workstation operator.

47.        [Mandatory] The search verification data (i.e., demographics, photo images, and fingerprint images for both the search record and candidate[s] record[s]) of every OPEN SEARCH match request that results in a "HIT" must be stored in an on-line WFPI QUEUE; the WFPI QUEUE must be available for access by authorized operators (e.g., fraud investigators) for a period of not less than six (6) calendar months. At the end of the six month period, the data held in the WFPI QUEUE will be written onto a mass storage media (e.g., tape or optical disk). The CA SFIS must be capable of re-instating the purged verification data back into the WFPI QUEUE from the off-line storage within twenty four (24) hours after a request by the State System Administrator.

48.        [Mandatory] Each CA SFIS workstation must be configured with an RDBMS that can be configured as clients of the RDBMS server configured on the Program Management Workstation/Server (see requirement VI.B.9.2.). The State will use this software to support it’s own trouble reporting application.

49.        [Mandatory] The CA SFIS must have the capability (as an option that the State may elect to implement at some point in the future) to produce an identity card from data obtained during the application process (demographics, fingerprint images, and photo image). It is anticipated that the identity card will show (at least) client name, CIN, issue date, date of birth, photo image (in color), and a 2D barcode representation of fingerprint image data (two fingers). The 2D bar code must be compliant with the AAMVA standard PDF417 symbology. The CA SFIS must have the capability to perform a one-to-one (CLOSED SEARCH) match of fingerprint data read from the 2D barcode on the identity card and a ‘live read’ of the client’s index fingers. The Bidder must describe how the proposed CA SFIS can accomodate these capabilities if the State choses to incorporate the functionality at some point in the future.

50.        [Mandatory] Every search request must result in a search result printout at the site that submitted the search. Search result printouts will be of two types; 1., Text Only; and, 2., Text Plus Images. Each site will specify the default type of search result printout expected at that site (refer to requirement VI.B.3.3.); the system must allow the search printout type to be changed by the input operator from the default type to the alternate type for a particular search request at the time the search is initiated.

"Text Only" search printouts will consist of demographic text of the search record and demographic text of the candidate record(s) that were determined as a "Hit" by Central Site Validation operators.

"Text Plus Images" search printouts will consist of (at least) the photo image, left and right finger images, and demographics of the search record as well as the photo image(s), left and right finger images, and demographics of each candidate record. Each candidate photo image will be printed side-by-side with the search photo image. Each set of left and right candidate images will be printed side-by-side with the search finger images. Photo images shall be transmitted from the Central Site to the workstation that supports the search result printout at the resolution specified for photo images in Section VI.B.3. of this RFP. Finger images shall be transmitted from the Central Site to the workstation that supports the search result printout at a resolution of 500 pixels/inch, plus or minus 5 pixels per inch, and each pixel shall be gray level quantized to 1 bit (i.e., the finger images sent to the workstation for search result printing will be binary images).

Bidders must assume that for the purpose of responding to this RFP, all search result printouts will be of the "Text Plus Images" type.

2.         Fingerprint Image Requirements

1.       [Mandatory] Fingerprint images displayed during match verification or image acquisition shall be displayed on-screen with a physical size of at least ten (10) times the original size; in addition, displayed images must map (at least) the resolution specified in the Type 4 image standard set out in the ANSI/NIST-CSL 1-1993 document onto the physical area of the image displayed on screen.

2.       [Mandatory] The brightness and contrast of images displayed during acquisition shall be controlled by on-screen controls.

3.       [Mandatory] Fingerprint images stored in the CA SFIS database must be stored as compressed files using the FBI-approved Wavelets Image Compression (WSQ) algorithm using the 15:1 compression ratio.

4.       [Mandatory] The Bidder must describe the safeguards that will be put into place to ensure that fingerprint images cannot be altered and/or assigned with incorrect demographic or biographical data.

5.       [Mandatory] The Bidder must state in their proposal that they acknowledge that all CA SFIS photo and fingerprint imaging data shall be the exclusive property of the State and that this data will not be used for any purpose without the written permission of the State.

3.         Photograph Image Requirements

1.       [Mandatory] The color photo image must be digitized and stored with a resolution that is at least the resolution specified in the standards of the American Association of Motor Vehicle Administrators (AAMVA).

2.       [Mandatory] Photo images stored in the CA SFIS database must be stored as compressed files using the JPEG compression algorithm.

3.       [Mandatory] Printing of photo or fingerprint images at a specific Remote Workstation must be controlled as a County option. Some Counties in the CA SFIS may not wish to automatically print photo images and/or fingerprint images as part of the search response.

4.         Live Scan Requirements

1.         [Mandatory] Live Scan equipment and software provided for the electronic exchange of fingerprint images and other match data with the CA SFIS Central Site shall be in full compliance with the American National Standard ANSI/NIST-CSL 1-1993 (as defined in the National Institute of Standards and Technology document NIST-CSL 1-921201, "Data Format for the Interchange of Fingerprint Information"), and, during the term of the contract including any extensions, shall be modified at no cost to the State to comply in a timely manner with subsequent approved revisions to this standard. Live-scanned fingerprint images must comply with the Type 4 image standard set out in the ANSI/NIST-CSL 1-1993 document and must substantially comply with the image quality specifications as set forth in the Criminal Justice Information Services (CJIS) Electronic Fingerprint Transmission Specification, dated August 24, 1995, Appendix G - Interim IAFIS Image Quality Specifications For Scanners plus all non-conflicting requirements given in Appendix F - IAFIS Image Quality Specifications, developed by NIST in conjunction with the Federal Bureau of Investigation and the Department of Justice, document CJIS-RS-0010 (V4). As stated in Appendix F, the Live Scan equipment "shall capture fingerprints at a minimum resolution in both the detector row and detector column directions (also known as ‘along-scan’ and ‘cross-scan’ directions) of 500 pixels/inch, plus or minus 5 pixels per inch. The final output delivered image from the [Live Scan equipment] shall have a resolution of 500 pixels/inch, plus or minus 5 pixels per inch, and each pixel shall be gray level quantized to 8 bits."

2.         Mandatory] The Live Scan equipment/software must capture "flat impressions" of fingerprint images.

3.         [Mandatory] The Contractor must furnish all consumable items used by all Live Scan devices used in the CA SFIS for the life of the CA SFIS contract at no additional cost.

4.         Live scan Operational Requirements

a.         [Mandatory] Repeatability

The Live scan reader must be capable of repeatedly scanning a test target and producing results consistent with the requirements listed in VI.B.4.3.

b.         [Mandatory] Warm Up and Continuous Operation

The Live scan reader must be capable of obtaining the performance requirements listed in VI.B.4.3. within five (5) minutes from powering on and must be capable of maintaining that performance without maintenance or calibration for a period of ten (10) hours.

5.         Quality Control of the Live Scan Reader and Related Equipment

a.         [Mandatory] Quality Control Testing

The Live scan reader and/or attached Input Workstation must be capable of exercising various reader subsystems to determine with reasonable certainty that these subsystems are properly operating, and, if performed by the reader itself, to convey the result of the testing back to the Input Workstation. Further, the testing must be capable of being performed in an automatic fashion by the attached Input Workstation; special test targets may be used in testing as long as the operator is not required to perform any function other than placement of the test target in the device and initiation of the test(s). At a minimum, the following subsystems must be capable of being tested:

o        the image acquisition sensor

o        digital memories

o        digital to analog converters

o        all data paths

b.         [Mandatory] Quality Control Testing Time Limit

A complete diagnostic of the Live Scan reader and all of it’s subsystems must be able to be invoked by the Input Workstation and the results returned to the Input Workstation within a maximum of five (5) minutes.

5.         Printer Requirements

1.         [Mandatory] One (1) high-resolution printer will be required for each CA SFIS workstation. The Bidder must state any limitations on placement.

2.         [Mandatory] Each workstation printer must be capable of printing textual data as well as photo and fingerprint images. The printed resolution of photo and fingerprint images must be such that an operator can make an accurate visual comparison of two images printed side by side. The Bidder must submit examples of text, fingerprint image, and photo image printouts with their proposal.

3.         [Mandatory] The Central Site system shall have a minimum of one (1) high speed (1200 lines per minute or greater), alpha/numeric printer capable of letter quality printing.

 

6.         Interface Requirements To The Statewide Automated Welfare System Technical Architecture (SAWS TA) Database

1.         [Mandatory] The Bidder must develop a CA SFIS-SAWS TA Interface Specification document; this document is due one (1) month after final signature of the Contract by the State. The CA SFIS-SAWS TA Interface Specification will specify all transactions between the Statewide Automated Welfare System Technical Architecture (SAWS TA) system and CA SFIS. The State will support the Bidder in this effort by supplying information.

2.             [Mandatory] The State will be responsible for all programming of the Statewide Automated Welfare System Technical Architecture application according to a CA SFIS-SAWS TA Interface Specification provided by the Bidder and agreed upon by the State. The Bidder is responsible for all programming on the CA SFIS side of the interface; additionally, the Bidder must provide all networking equipment necessary to establish communications between the SAWS TA and the CA SFIS; all networking equipment must be approved by the HWDC Telecommunications Division prior to installation.

3.         [Mandatory] The CA SFIS must support the capability to initiate a FILE CLEARANCE TRANSACTION on the SAWS TA from any CA SFIS workstation via a CA SFIS-SAWS TA interface. If the Statewide Automated Welfare System Technical Architecture system does produce FILE CLEARANCE candidates, the CA SFIS must fetch and then queue the match record photo and fingerprint images of the candidates and display these images as requested via either a search verification image display function or a "photo lineup" display function at the requesting workstation. It must be possible to use this function as a stand-alone function that is not connected to a fingerprint image search process.

4.         Image Server Capability

[Mandatory] The CA SFIS must support the capability to perform the functions of an Image Server on the HWDC network. The CA SFIS Image Server function must perform as follows: The Statewide Automated Welfare System Technical Architecture will submit a list of CIN’s to the CA SFIS through the HWDC network; the CA SFIS must fetch and then queue the photo images of each CIN in the list; the CA SFIS will then transmit the list of photo records to the SAWS TA. The photo images transmitted to SAWS TA must be either compressed or uncompressed as specified in the request for images made by the SAWS TA. If the CA SFIS images are compressed using a proprietary photo image compression technique, the Bidder must furnish the State with appropriate, royalty-free photo image decompression software that can be run on an Intel-based PC running under MS WindowsÔ ; in this case, the State agrees to use this software only on State-owned workstations for the purpose of decompressing photo images received from the CA SFIS Image Server function.

5.         [Mandatory] The CA SFIS must support the capability to download demographic data from the Statewide Automated Welfare System Technical Architecture (SAWS TA) system via the CA SFIS-SAWS TA interface when a CIN number is input at the Remote Workstation.

The operator will input the CIN number for the client. The CA SFIS must automatically "populate" the CA SFIS demographic input fields with demographic data downloaded from the SAWS TA system that corresponds to the CIN input by the CA SFIS operator.

6.         [Mandatory] Bidder’s will describe in their proposal how the CA SFIS-SAWS TA interface will be designed to support both OPEN SEARCH transactions and CLOSED SEARCH transactions with an appropriate sequence of interface transactions between the CA SFIS and the Statewide Automated Welfare System Technical Architecture (refer to Diagram IV.B.1. in Section IV of this RFP).

 

7.         [Mandatory] The CA SFIS must support all functions and capabilities listed in Section IV.F. (CA SFIS Interaction With The Statewide Automated Welfare System Technical Architecture [SAWS TA]).

 

7.         Conversion of Existing AFIRM Data

All AFIRM databases will be made available to the successful Bidder. The AFIRM data will consist of approximately 510,000+ records; each record will consist of an individual’s demographics and the 8-bit gray scale images of the individual’s two index fingers. Each finger has been scanned at a resolution of 512x512 pixels over a 1" x 1" area with 8 bits of gray per pixel. Each image has subsequently been "cropped" to 384x384 pixels. The images are stored uncompressed.

AFIRM records will be made available on 4mm DAT tape in TAR format.

1.         [Mandatory] If selected as the winning Bidder, the Bidder must convert all two-finger records from all California AFIRM systems (currently installed in the counties of Los Angeles, Alameda, Contra Costa, San Francisco, and Orange) to a format that can be used on the Bidder’s proposed system. The conversion process must be completed within one month after contract signature. If additional counties come on-line with an AFIRM system after the initial conversion process, the Bidder must convert records from these counties to a format that can be used on the Bidder’s proposed system. For the purpose of this RFP, the term "AFIRM" refers to all California AFIRM counties.

2.         [Mandatory] The successful Bidder must conduct and successfully complete a Benchmark Accuracy Test within two months of Contract Award..

3.         [Mandatory] Before the beginning of the Phase 1, 2, and 3 Acceptance Tests, the converted AFIRM database must be updated with the current state of the AFIRM databases (deleted records must be purged, new records must be added, and old records must be updated as necessary).

4.         [Mandatory] Once loaded into the CA SFIS database, every AFIRM record must be matched against every other AFIRM record; this process must be completed before the beginning of the Phase 1, 2, and 3 Acceptance Tests. All searches will be "cold" searches; i.e., every record will be matched against every other record in the database regardless of sex or any other database delimiter. In addition, all subsequent AFIRM records added to the database must be matched against all existing CA SFIS records.

8.         Data Analysis Workstation

[Mandatory] Bidders must propose a high performance Data Analysis Workstation to be used by the State to analyze the data files produced in VI.B.1.37. The Data Analysis Workstation must be a high-performance workstation that has at least 4 gigabyte of hard disk capacity, a 19" Super VGA monitor with a resolution of 1024 by 768 pixels, a 3.5" floppy drive, an 8x CDROM, and keyboard. The Data Analysis Workstation must be configured with an RDBMS application that is the same as the RDBMS application resident on each Remote Input Workstation. The Data Analysis station must have a communications link to the CA SFIS Central Site RDBMS data to be analyzed.

9.         Program Management and Error Reporting Workstation/Server

1.         [Mandatory] Bidders must propose a high performance workstation that will be used to:

o        support the Systems Administrator functions of CA SFIS;

o        perform all the functions of a Data Analysis Workstation; and,

o        perform the functions of an RDBMS server.

2.         [Mandatory] The Program Management Workstation/Server must be connected (through the CA SFIS data communications network) to all CA SFIS Remote Input Workstations located in County Welfare Offices in the State. The State intends to use the Program Management Workstation/Server as an RDBMS server connected to Remote Input Workstation clients. The State will develop and maintain an RDBMS database that will be used to log system problem reports from Remote Input Workstation operators. The system error reporting facility supported by the Program Management Workstation/Server will be completely separate and apart from the error reporting system and/or Help Desk facility maintained by the Contractor.

3.         [Mandatory] The Program Management Workstation/Server must be a high-performance workstation that has at least 4 gigabyte of hard disk capacity, a 19" Super VGA monitor with a resolution of 1024 by 768 pixels, a 3.5" floppy drive, an 8x CDROM, and keyboard. The Program Management Workstation must be configured as an RDBMS server that is linked to an equivalent RDBMS application resident on each Remote Input Workstation.

 

C.      Specific Remote Input Workstation Requirements

1.         Functionality

1.       [Mandatory] The workstations' user interface must be easy to learn and easy to use. The Bidder must provide a detailed description of each user interface with examples.

2.       [Mandatory] Each proposed remote input workstation must be configured as a fully functional CA SFIS workstation with the capability to input, collect, store, transmit, access and display fingerprint images and other associated client and control information.

3.       [Mandatory] Each workstation must be capable of printing (in gray scale) photo images stored on the CA SFIS database. In addition, each workstation must be capable of printing (as binary images) all fingerprint images stored on the CA SFIS database.

4.       [Mandatory] The CA SFIS must provide the workstation operator with access to an on-line help capability as well as a simple on-line tutorial for using the CA SFIS workstation-accessible features.

5.       [Mandatory] Each workstation must comply with the security requirements described in this RFP.

6.       [Mandatory] Inactive workstations must be automatically logged-out after a predetermined period (set by the System Administrator). This log-out must occur in a controlled manner so that no work in progress is lost.

7.       [Mandatory] Proposals must specify the number of workstations (see Exhibit VI-1 for the number and location of workstation sites) that will be provided, and explain why the proposed number will be sufficient both for the initial input volume while building the database with current health and welfare records and for subsequent normal operations, taking into account reliability and backup requirements. Workstation requirements must be based on the expected "Daily Applications" workload outlined in Section IV for Months 12 and 65 of CA SFIS operation (Tables IV.C.1. and IV.C.2., respectively) and on the "Existing Caseload" workload outlined in Section IV.C. (see Table IV.C.4.). Bidders must specify the following workstation totals: 1., the number of workstations needed at each site in Month 12 to process the "Daily Workload;" 2., the number of additional workstations at each site during Months 1-11 that are needed to process the "Existing Caseload" workload; and, 3., the number of workstations needed at each site in Month 65 to process the "Daily Workload.

8.       [Mandatory] Workstation resident software must perform field edit validations on client and control information entered by operator (required fields, format, alpha/numeric field content, dates, etc.). During data entry, the operator must be clearly notified on screen of fields failing edits and of corrective actions to be taken by the operator for data acceptance.

9.       [Mandatory] All workstation transactions must be selectable via menu using a single keyboard stroke and/or via a PC mouse click(s).

10.   [Mandatory] The workstation shall have the capability to capture an image from a live scan device.

11.   [Mandatory] The equipment/software shall provide a video display of captured fingerprint images to insure that the fingerprint image is acceptable (positioning, area of fingerprint captured, etc.) prior to storage of the image into local memory.

12.   Deleted.

13.   [Mandatory] The CA SFIS Remote Input Workstation must be capable of informing the operator whether or not any fingerprint image meets the system criteria for acceptability prior to completing the fingerprint image capture process. This functionality must be operational regardless of whether or not either the communications network or the Central Site is operational. On a daily basis, no more than one-half of one percent (0.5%) of all images entered into all input workstations connected to the CA SFIS may be rejected for bad quality. If more than 0.5% of the images entered into the system for any accuracy test are rejected for bad quality, that portion of the percentage of rejected fingerprints over 0.5% will be subtracted from the Contractor’s accuracy scores achieved during any accuracy test described in Section VI.G. The measurement of 0.5% rejected fingerprints includes those fingers re-scanned for quality reasons but does not include those fingers that were graded as unsatisfactory due to obvious operator error as determined by the State.

14.   [Mandatory] The CA SFIS must allow the workstation operator to reenter images and modify the demographics of any client record data prior to completing data entry at the workstation.

15.   [Mandatory] If the workstation operator has an appropriate permission level, the CA SFIS must allow the workstation operator to reenter images and modify the demographics of any client record data previously stored in the CA SFIS.

16.   [Mandatory] During data entry at the CA SFIS workstation, a client color photograph will be taken. If the photo is acceptable, a single key stroke by the operator shall freeze the image and store it into local memory.

17.        [Mandatory] During the data entry process, the client record and control input screen must appear on the terminal for the operator to perform data entry.

18.        [Mandatory] Each workstation must be capable of interacting with the CA SFIS Central Site database for the purpose of:

a.         Adding a new client record for search, match and filing [client and control data, fingerprint image(s), and color photo]

b.         Updating a client record and (optionally) re-submitting the record for CLOSED or OPEN SEARCH

c.         Inquiring on a client record

d.         Receiving a Match/ No Match Confirmation

e.         Inquiring on (full digital) fingerprint image(s) with split screen workstation display for comparison of 2 different fingerprint images

f.          Inquiring on (full digital) photo image(s) with split screen workstation display for comparison of 2 different photo images

g.         Printout of full or partial client record information (digital fingerprint image(s), client data, photographic images, etc.)

h          Verification to confirm the identity of a client based on side-by-side photo comparisons and/or side-by-side fingerprint image comparisons

19.        [Mandatory] The system shall provide a side-by-side split-screen display of

a.         the photo image of the search record and each candidate photo image for comparison by the operator (all photo images displayed on-screen must be in 24-bit color), and

b.         the fingerprint images of the search record and each candidate fingerprint images for comparison by the operator (fingerprint images displayed on-screen must be either 8-bit gray scale images,10 binary images, or skeleton images at the option of the user).

The system shall display the applicable alphanumeric data screen for each candidate photo and/or fingerprint image when the images are viewed alongside the photo and/or fingerprint images of the record.

20.        [Mandatory] The system shall provide a display at the workstation of the activity of transactions in the system queues, subject to the user’s access permission level.

21.        [Mandatory] During the input process, the workstation must perform an image to image match of the two index fingers that have been input for search; this match process must be automatic and performed as a "background" task. The match process must occur immediately after the fingerprint image capture process is complete. If the match process determines that a match exists, the workstation application must immediately notify the workstation operator of the result. This functionality must be operational regardless of whether or not either the communications network or the Central Site is operational. The purpose of this requirement is to prevent the operator from making the mistake of entering the same finger for both the left and right hand finger images during the input process.

22.        [Mandatory] The Remote Input Workstations must be capable of supporting an industry standard operating system and off-the-shelf application software packages available for microcomputer platforms.

23.        [Mandatory] The Remote Input Workstation must have the capability to analyze fingerprint images and produce minutiae data for each fingerprint image that will be used for all fingerprint image matching. The Remote Input Workstation will send all data for the record including the (compressed) fingerprint images to the Central Site over the network.

 24.       [Mandatory] The Remote Input Workstation must have the capability to accept a download of demographic data from the SAWS TA through the CA SFIS-SAWS TA interface. The Remote Input Workstation will send a request for demographic data after the Remote Input Workstation operator has keyed in the CIN of the client who is about to be entered for search into the CA SFIS.

25.        [Mandatory] Bidders must propose high performance Remote Input Workstations to be used by the State to process the client application workloads defined in Section IV. of this RFP. The Remote Input Workstations must be high-performance workstations that have

o        sufficient hard disk capacity to store the required number of client records when the Central Site system is unavailable to the Remote Input Workstation,

o        a monitor with sufficient resolution and size so that an operator can read the CA SFIS display(s) easily, and

o        and a removable media, high capacity digital recording device (to be used for activities such as transaction journalling, test record storage, backup, etc.).

Each Remote Input Workstation must be configured with an RDBMS application that is the same as the RDBMS application resident on the Central Site Data Analysis Workstation.

 

2.         Workstation Display Characteristics

1.       [Mandatory] Each workstation must be configured to display hi-resolution digital color images.

2.       [Mandatory] All workstation screens shall have sufficient resolution and contrast to reproduce a fingerprint at the ANSI/NIST-CSL 1-1993 high (Type 4 image) resolution on the display screen. The display screen must have the capability to show two fingerprint images side by side on screen. Both fingerprint images shall be displayed on-screen with a physical size of at least ten (10) times the original size; in addition, displayed fingerprint images must map (at least) the resolution specified in the Type 4 image standard set out in the ANSI/NIST-CSL 1-1993 document onto the physical area of the image displayed on screen.

3.       [Mandatory] The workstation printer must be capable of generating a printout of any image (fingerprint and/or photo) displayed on a workstation screen. Printouts shall be automatically sent to the local printer associated with the workstation. Printouts of fingerprint images will be ‘full binary’ images (full resolution images with the gray level of each pixel converted to white or black) with an ‘along-scan’ and ‘cross-scan’ direction resolution of 500 pixels/inch, plus or minus 5 pixels per inch. Fingerprint images shall be printed with a physical size of at least ten (10) times the original size. Printouts of photo images shall be in gray scale in sufficient resolution so that, in the judgment of the State, an operator can determine if two photo images printed side-by-side are or are not from the same individual.

4.       [Mandatory] The display screen must have the capability to show two photo images side by side on screen. Both photo images shall be displayed on-screen with a physical size of at least 5" by 5"; in addition, displayed images must map (at least) the resolution specified in the image standard set out by the AAMVA onto the physical area of the image displayed on screen.

5.       [Mandatory] The light intensity and display screen contrast shall be adjustable by means of on-screen controls.

3.         Physical Characteristics

1.       [Mandatory] The proposed CA SFIS workstations must be ergonomically designed and in compliance with UL (Underwriters Laboratory) standards for operator safety.

2.       [Mandatory] The proposed CA SFIS workstations must allow for reasonably comfortable seated operation of all devices involved in the image input process. Compliance with Americans with Disabilities Act (ADA) regulations is required for all CA SFIS workstations.

3.       [Mandatory] Bidder must provide an appropriate number of pre-wired workstations that are FCC Class B certified at each County Welfare Office site listed in Exhibit VI-1.

4.         Off-Line Transaction Capability & Storage

[Mandatory] Input Workstations must be capable of collecting and storing up to 300 complete client records (fingerprint images, photo, and client and control information) for future batch update to the CA SFIS Central Site in the event the CA SFIS and/or network is not available. Input Workstations must confirm receipt of updates to the Central Site database before records are removed from the local Input Workstation’s output queue; the Bidder must specify how they will meet this requirement.

5.         Portable Input Workstations

[Mandatory] The Bidder must provide an option for the State to purchase portable Remote Input Workstations; each portable workstation must have all of the functionality specified in paragraphs VI.C.1. and VI.C.2. (with the exception of requirements VI.C.2.3. and VI.C.2.4.). Each portable must have the capability to store up to 100 input records; each input record will be composed of data as specified in paragraph VI.B.1.24. The portable workstation must have the capability to establish a high-speed communications link with the Central Site over commercial telephone lines.

6.         Remote Input Workstation Security

[Mandatory] Each Remote Input Workstation must include a security system within each workstation that will limit access to authorized users of the workstation. The security system implemented on the Remote Input Workstation must include the use of a two-fingerprint match. Provision must be made to use another finger (or fingers) in those instances when an (authorized) operator’s index finger(s) is/are temporarily injured and/or bandaged (i.e., the operator may use any two of his/her fingers for the local match process as long as the operator makes an appropriate workstation entry prior to fingerprint image capture – this procedure must be part of the security process). In order to support the use of any two of the operator’s fingers used in the log-on security process; the workstation must maintain minutiae sets for all ten (10) of the operator’s fingers. The log-on security system must be available on the workstation regardless of whether the communication network is down and/or the CA SFIS Central Site is available.

On every workstation that a particular operator is authorized to use, fingerprint image data from all ten (10) fingers of the operator must be available for a local CLOSED SEARCH match associated with the log-on security function of the workstation. In addition, on every workstation that a particular operator is authorized to use, the operator’s system access permission level(s), ID/password, etc. must be available to the workstation’s security logic in order to limit the operator’s access to those functions, databases, etc. that have been authorized to that user by the State Program Manager. This information must be available to the workstation even during those times when the workstation cannot communicate with the Central Site for whatever reason.

 

7.         Connection to the HWDC Network

[Mandatory] Each Remote Input Workstation must be connected to the HWDC Wide Area Network (WAN) through local LAN networks. The HWDC WAN is connected to a Local Area Network (LAN) at each site where a Remote Input Workstation will be placed (see Section IV, Table IV.C.1. for a list of Remote Input Workstation sites). The type of LAN used at each county site will be one of two types; Token Ring or Ethernet. Remote Input Workstations installed at sites in the following counties must be connected to a Token Ring LAN: Placer, Kern, Tulare, Alameda, Kings, Merced, Santa Barbara, Monterey, San Luis Obispo, San Mateo, Santa Cruz, and Fresno. All other county Remote Input Workstation sites will be configured with Ethernet LANs. It is the Contractor’s responsibility to configure each Remote Input Workstation with the hardware and software necessary to connect the workstation to the LAN at each installation site.

 

D.      Specific Central Site Requirements

1.         Space Limitations and Costs for State Spaces

The CA SFIS Central Site equipment must be located in the computer room spaces of the HWDC. Sufficient floor space will be available at the HWDC to accommodate the CA SFIS. In the Cost Proposal, Bidders must identify the amount and type of HWDC facilities that are required for installation, maintenance, power consumption, heat load, and operation of their proposed system.

The HWDC computer spaces are of two types; office space, and raised floor space. For purposes of this RFP Bidders are required to base the ongoing monthly costs – broken out in their Cost Proposal – on the following costs:

OFFICE SPACE

$1.60 per square foot

RAISED FLOOR SPACE

$2.75 per square foot

ELECTRICITY

$0.06 per KWH

 

2.         Central Site Functionality

1.       [Mandatory] The Central Site shall have the ability to prioritize transactions within system queues. In the event of a processor malfunction all queues shall be saved and the system must automatically reinitiate the queue from the point of interruption with no loss of data.

2.       [Mandatory] The primary CA SFIS operations functionality such as system startup and shutdown, password control, and access control shall be menu-driven with clear instructions and messages presented to the user. Additional stand-alone special maintenance and monitoring utilities shall be available to access system databases. The system shall only need one operator who is knowledgeable in computer systems and CA SFIS to perform all system operations.

3.       [Mandatory] Poor fingerprint (quality control) threshold, enforced at the point of image entry, shall be adjustable system-wide from the system console. A change to the system image quality threshold must be immediately and automatically broadcast over the network to all input workstations currently connected to CA SFIS. If a workstation is disconnected from the system at the time a threshold change is made, the system must automatically reset that workstation’s threshold at the time it is re-connected to the system. The threshold level shall be set at installation at the level that optimizes search accuracy, yet yields a low image re-scan rate. Refer to Section VI.C.1.13.

4.       [Mandatory] Bidder shall provide all interfaces required to connect all system components; database subsystems, input subsystems, remote input workstations, etc.

5.       [Mandatory] The system shall guarantee delivery of a response to any transaction that has been accepted by the Central Site system, unless the transaction is deleted by an operator prior to the completion of the transaction.

6.         [Mandatory] The system must maintain a system wide display of the current system-wide status of all workstations attached to the CA SFIS; the design of the system-wide workstation status display will be determined during the System Design phase of the Contract and the design must be approved by the State. At a minimum the display will show, for each CA SFIS workstation (except portable workstations) one of the following conditions:

o        Responding, Logged On - The workstation is responding to Central Site status inquiries and an operator is logged into the system

o        Responding, Logged Off - As above, but with no operator Logged onto the system

o        Not Responding - The workstation is disconnected from the Central Site system

o        Malfunctioning, Logged On - The workstation functionality is degraded and an operator is logged into the system

o        Malfunctioning, Logged Off - As above except that an operator is not logged into the system

7.         [Mandatory] If the Central Site is not fully operational, the system must be capable of providing a system generated message to the remote operators indicating the nature of the Central Site problem and the specific workstations functions and/or Central Site functions that are affected (assuming that the network is operational).

8.         [Mandatory] All workstations in the system must have the capability to monitor the "heartbeat" of the Central Site over the network and to inform the workstation operator if it detects that the Central Site and/or the communications network is not functioning or is degraded.

9.         [Mandatory] Operational Downtime: It shall be possible to limit operational downtime during a physical relocation or computer room shutdown to only system shutdown and startup, plus time to physically relocate, set up applicable hardware, and verify hardware and operating system integrity. In-process transactions in system queues shall be re-startable after power-up.

10.        [Mandatory] End-to-End Downtime: The system shall permit complete shutdown of hardware and software and restart to full functionality within a 20 minute period of time.

11.        [Mandatory] Update Access: Each CA SFIS record must be available for update processing at only one workstation at any time.

3.         Central Site Workstation Functionality

1.         [Mandatory] Minutiae Analysis/Match Verification workstations must be proposed that allow trained operators to compare fingerprint images. An adequate number of these workstations must be provided for minutiae analysis and match verification/validation; these workstations may be located in the HWDC Data Center as well as in other locations in the State of California. These workstations must provide:

a.         The capability to retrieve minutiae as well as digital fingerprint images for side-by-side viewing on a single screen, for easier comparison and match verification. The operator must be able to mark points of comparison on the screen images of each print and print out the side-by-side marked prints for court presentations.

b.         The capability to add, delete and/or modify characteristic points of the fingerprint image identified by the system’s image encoding function.

c.         A 19" or larger high resolution, graphics capable color CRT with core and axis markers.

d.         Cursor motion by mouse or positioning keys.

e.         Operator controllable fingerprint image enlargement on the screen up to at least ten (10) times size.

f.          A laser printer shall be available to these workstations to print fingerprint images from actual size up to ten (10) times size and to print two such images in a side-by-side format with or without (at the operator’s discretion) matching characteristic points indicated within the images.

2.         [Mandatory] Side-by-side fingerprint images and/or photo images displayed at the Minutiae Analysis/Match Verification workstation shall be of clear and readable quality, so that a technical examiner is able to determine a match. The system shall also provide a zoom function to enlarge operator-specified corresponding areas of the search image and the candidate image(s).

3.         [Mandatory] During match verification, the system must provide a means by which characteristic minutiae that are common to both images displayed (side-by-side) can be marked. Each pair of common characteristics marked in this manner must be marked so as to show the correspondence between each of the minutiae pairs.

4.         [Mandatory] The Minutiae Analysis/Match Verification workstation must also have the capability to add, delete and modify minutiae characteristics identified by the system’s image encoding.

5.         [Mandatory] The Minutiae Analysis/Match Verification workstation operator must have the capability to:

a.         initiate a FILE CLEARANCE transaction on the Statewide Automated Welfare System Technical Architecture (SAWS TA) system, fetch and queue the photo and fingerprint images corresponding to the list of CIN numbers resulting from the FILE CLEARANCE, and display the images on-screen;

b.         recall the fingerprint images of any record in the CA SFIS database, make changes to the encoding of the fingerprint images of the record, and re-submit the record for a CA SFIS OPEN SEARCH or submit the record for a CLOSED search against a particular CA SFIS record (specified by CIN number).

6.         [Mandatory] During match verification, the Minutiae Analysis/Match Verification workstation must have the capability to submit the search record for a CA SFIS OPEN SEARCH or submit the search record for a CLOSED search against a particular CA SFIS record (specified by CIN number). The workstation operator must also have the option to make changes to the encoding of the fingerprint images of the record and/or the demographics of the record prior to re-submitting the record for search.

4.         Central Site Test Bed System

1.         [Mandatory] The Bidder must include a fully functional Test Bed system that shall be located at the Central Site facility. The Test Bed system shall exactly replicate all the functionality of the CA SFIS. The Test Bed system will be used to test software and/or hardware modifications and updates to the CA SFIS prior to installation on the CA SFIS. The Test Bed system may also be used to conduct off-line tests (accuracy, response time, etc.) and to perform a database reorganization, if required.

2.         [Mandatory] The Bidder must describe the physical implementation of the proposed Test Bed system. The Bidder must also describe the logical implementation of the proposed Test Bed system and explain how the test Bed system logically replicates the CA SFIS.

E.      Database Capacity

1.         The CA SFIS must be designed to potentially accommodate twice the following database record capacity:

 

Year 1

3,333,763

Year 2

4,540,784

Year 3

5,139,639

Year 4

5,621,996

Year 5

6,012,868

Year 6

5,33,828

 

Table VI.E.1. Expected Number of CA SFIS Records

 

2.         [Mandatory] The system must be designed to off-load denied/discontinued or purged client records from the CA SFIS database upon direction from the Statewide Automated Welfare System Technical Architecture (SAWS TA) system via the CA SFIS-SAWS TA interface. Discontinued or purged records will be off-loaded onto a high capacity storage media. The system must be designed so that records that have been off-loaded can be loaded back into the CA SFIS database within 24 hours. Immediately after a record has been successfully loaded back into the CA SFIS database, the CA SFIS Central Site system must automatically send a RECORD RESTORATION NOTICE to the SAWS TA (see RFP Section IV.F.10.).

 

F.      Workload & Response Time Requirements

1.         Workload Requirements

The following tables are incorporated as part of the system workload requirements:

o        Tables IV.C.1. and IV.C.2.: Number Of "Daily Applications" At Each County Office Per Hour in Months 12 and 65

o        Table IV.C.3.: Summary of "Daily Applications" Workload From All Workstations Per Hour

o        Table IV.C.4.: Existing Client Record Conversion Workload Per Hour

o        Table IV.E.1.: CA SFIS Workload and Database Size Per Month (65 Month Period)

1.         [Mandatory] The Bidder’s system shall process the number of daily search transactions defined in Tables IV.C.1. through IV.C.4. at the County Welfare Offices between the hours of 8AM and 4PM, Monday through Friday.

2.         [Mandatory] The Bidder must specify the amount and type of equipment proposed at each of the 224 County Welfare Offices (listed in Exhibit VI-1) that is required to perform the number of daily search requests -- as defined in Tables IV.C.1. through IV.C.4 -- between the hours of 8AM and 4PM, Monday through Friday. The Bidder may assume that the "Existing Caseload" (i.e., Conversion input) will be distributed evenly across all eight hours of the normal workday as shown in Table IV.C.4.

3.         [Mandatory] The Bidder’s system shall be able to process the number of OPEN SEARCH and CLOSED SEARCH transactions defined in Table IV.E.1.;

a.       all PRIORITY search transactions associated with the "Daily Applications" (40% of the "Daily Application" workload) must be completed within 15 (Option 1) or 60 minutes (Option 2 as specified in the Bidder Qualification Response) of the time that the workstation operator submits the search for processing depending on whether the State selects Response Time Option 1 or Response Time Option 2 (Response Time Options are defined in paragraph VI.F.2.4.);

b.       all ROUTINE search transactions associated with the "Daily Applications" (60% of the "Daily Application" workload) must be completed by 7AM the next day after the day that the search was received at the Central Site for processing; and,

c.       all search transactions associated with "Existing Caseload" must be completed by the 7AM the next business day one calendar week after the search was received at the Central Site for processing.

4.         [Mandatory] The system must respond to simultaneous entries from all workstations.

5.         [Mandatory] The CA SFIS must process other types of transactions (e.g., Image Retrieval, FILE CLEARANCE, etc.) in addition to and concurrently with the OPEN SEARCH and CLOSED SEARCH workloads. Bidders must describe the overall transaction throughput capabilities of their proposed system and to point out any bottlenecks and/or limits to concurrent transaction processing that may be imposed by either the system’s design and/or the configuration of the system.

2.         Response Time Requirements

1.         [Mandatory] The time required to retrieve photo or fingerprint images not associated with a search result shall be no more than five (5) seconds, excluding Wide Area Network transit time, at any workstation connected to the Central Site. Time shall be measured from the moment the operator initiates the retrieval in the workstation application to the time the image is fully displayed on the workstation screen.

2.         [Mandatory] If the Bidder elects to use Sex as a search delimiter, any "Hit" response to the CROSS-GENDER SEARCH operation must be returned to the site that entered the search request by 7AM the next day.

3.         [Mandatory] All CLOSED SEARCH match/no-match responses associated with the "Daily Application" workload shall be returned to the workstation transmitting the search data for display and/or print within fifteen (15) minutes from the time the operator selects END INPUT16 to the time the match is complete and the system has submitted the match result to the print queue at the site that has requested the search.

4.         [Mandatory] The State requires cost quotations for achieving both of the following OPEN SEARCH response times:

Option 1

40% of all OPEN SEARCH match/no-match responses* associated with the "Daily Application" workload (PRIORITY searches) shall be returned to the workstation transmitting the search data for display and print within an average of fifteen (15) minutes17 from the time the operator selects END INPUT18 to the time the match is complete and the system has submitted the match result to the print queue at the site that has requested the search.

The remainder (60%) of the OPEN SEARCH match/no-match responses* associated with the "Daily Application" workload shall be returned to the workstation transmitting the search data for display or print no later than 7AM the following day. (NOTE: The Bidder must not consider weekends; assume that every day is a business day).

All OPEN SEARCH match/no-match responses* associated with the "Existing Caseload" workload shall be returned to the workstation transmitting the search data for display or print within seven (7) calendar days from the time the operator selects END INPUT to the time the match is complete and the system has submitted the match result to the print queue at the site that has requested the search.

* The response time is measurable at the workstation and is defined as that time that elapses between the moment the operator selects END INPUT and the time that the search result is returned to the workstation and the search result is 1., fully ready for viewing at the workstation; and 2., submitted to the print queue at the workstation’s printer. Response time will be measured during Phase 1, 2, and 3 Acceptance Testing, as well as regularly thereafter, as the system expands.

Option 2

40% of all OPEN SEARCH match/no-match responses* associated with the "Daily Application" workload (PRIORITY searches) shall be returned to the workstation transmitting the search data for display and print within an average of sixty (60) minutes19 (or as specified in the Bidder’s Qualification Response) from the time the operator selects END INPUT to the time the match is complete and the system has submitted the match result to the print queue at the site that has requested the search.

The remainder (60%) of the OPEN SEARCH match/no-match responses* associated with the "Daily Application" workload shall be returned to the workstation transmitting the search data for display or print no later than 7AM the following day. (NOTE: The Bidder must not consider weekends; assume that every day is a business day).

All OPEN SEARCH match/no-match responses* associated with the "Existing Caseload" workload shall be returned to the workstation transmitting the search data for display or print within seven (7) calendar days from the time the operator selects END INPUT to the time the match is complete and the system has submitted the match result to the print queue at the site that has requested the search.

* The response time is measurable at the workstation and is defined as that time that elapses between the moment the operator selects END INPUT and the time that the search result is returned to the workstation and the search result is 1., fully ready for viewing at the workstation; and 2., submitted to the print queue at the workstation’s printer. Response time will be measured during Phase 1, 2, and 3 Acceptance Testing, as well as regularly thereafter, as the system expands.

5.         [Mandatory] The Bidder shall determine the number of fingerprint verification/validation operators needed to meet the response time requirements outlined in Section VI.F. In answering this requirement, the Bidder shall state the number of operators needed and the method by which this number was determined.

 

G.      System Accuracy Requirements

1.         Print-to-Print Search Accuracy Requirements

The following accuracy requirements pertain to the system’s matcher accuracy. Accuracy will be measured directly from the Matcher Subsystem (or equivalent) output with no review by an operator at any stage in the match process. If the Bidder’s system utilizes a Validation stage in the overall process (see Section IV.B.4.), the accuracy will be measured at the point prior to any review by the Validation operators.

1.         [Mandatory] Two-Finger OPEN SEARCH Accuracy Requirement

For all OPEN SEARCH requests where the search request is made with two (2) fingerprint images and there are two (2) corresponding and useable finger records in the database, the CA SFIS must produce a correct "Hit" indication at least 96% of the time (or higher as specified in the Bidder’s Bidder Qualification Response [see Section V.B.]).

For all OPEN SEARCH requests where the search request is made with two (2) fingerprint images and there is not a corresponding set of finger records in the database, the CA SFIS must produce a "NO CANDIDATES FOUND" indication at least 80.0% of the time.

When an OPEN Search Transaction (using both index fingers for search) is submitted

And Client IS in Database with both corresponding finger images usable for search

Then out of 100 search attempts:

If the system is designed so that an OPEN SEARCH can produce a candidate list, At least 96 of 100 search attempts must result in a candidate list that contains at least one matching candidate. [See Candidate List Length Note below.]

Or,

If the system is designed so that an OPEN SEARCH does not produce a candidate list but does produce a "Hit" or "No-Hit" indication, At least 96 of 100 search attempts must result in a "HIT" indication.

 

If Client IS NOT in Database

Then out of 100 search attempts:

At least 80 of 100 search attempts must result in a "No Candidates Found" message to the requester.

Note: Candidate List Length

For the Benchmark Accuracy Test and Factory Acceptance Test (see RFP requirements VI.G.2.1.and VI.G.2.2., respectively), the maximum number of candidates that can be returned on any candidate list is five (5).

For the System Accuracy Test (see RFP requirement VI.G.2.3.), the maximum number of candidates that can be returned on any candidate list is five (5) non-AFIRM candidates. A "Non-AFIRM" candidate is defined as a candidate record that has been added to the CA SFIS through one of the CA SFIS Remote Entry Workstations subsequent to an OPEN SEARCH process as described in Section IV. of this RFP (see Diagram IV.B.1.). Additional AFIRM candidates (i.e., records converted from AFIRM data as described in RFP requirement VI.B.7., Conversion of Existing AFIRM Data) may be included in the candidate list. During operational use of the system, the Contractor is responsible for verification of all candidates on all candidate lists regardless of the number of AFIRM candidates included in any candidate list.

  2.       [Mandatory] Single-Finger OPEN SEARCH Accuracy Requirement

For all OPEN SEARCH requests where the search request is made with one (1) fingerprint image and there is at least one (1) corresponding and useable finger record in the database, the CA SFIS must produce a correct "Hit" indication at least 95% of the time.

For at least 50.0% of all OPEN SEARCH requests where the search request is made with one (1) fingerprint image and there is not at least one (1) corresponding and useable finger record in the database, the search request must result in either 1., a candidate list containing no more than one (1) candidate, or, 2., a "NO CANDIDATES FOUND" indication.

When an OPEN Search Transaction (using single finger - either left or right - for search) is submitted

And Client IS in Database with corresponding finger image - either left or right - usable for search

Then out of 100 search attempts:

If the system is designed so that an OPEN SEARCH can produce a candidate list, At least 95 of 100 search attempts must result in a candidate list that contains at least one matching candidate.

Or,

If the system is designed so that an OPEN SEARCH does not produce a candidate list but does produce a "Hit" or "No-Hit" indication, At least 95 of 100 search attempts must result in a match indication with at least one matching candidate.

See Candidate List Length Note below.

 

If Client IS NOT in Database

Then out of 100 search attempts:

For the Benchmark Accuracy Test and Factory Acceptance Test (see RFP requirements VI.G.2.1.and VI.G.2.2., respectively), at least 50 of 100 search attempts must result in either 1., a candidate list containing no more than one (1) candidate, or, 2., a "NO CANDIDATES FOUND" indication. The candidate list length for all other search attempts is defined in the Candidate List Length Note, below.

For the System Accuracy Test (see RFP requirement VI.G.2.3.), at least 50 of 100 search attempts must result in either 1., a candidate list containing no more than one (1) non-AFIRM candidate, or, 2., a "NO CANDIDATES FOUND" indication. The candidate list length for all other search attempts is defined in the Candidate List Length Note, below.

Note: Candidate List Length

For the Benchmark Accuracy Test and Factory Acceptance Test (see RFP requirements VI.G.2.1.and VI.G.2.2., respectively), the maximum number of candidates that can be returned on any candidate list is five (5).

For the System Accuracy Test (see RFP requirement VI.G.2.3.), the maximum number of candidates that can be returned on any candidate list is five (5) non-AFIRM candidates. A "Non-AFIRM" candidate is defined as a candidate record that has been added to the CA SFIS through one of the CA SFIS Remote Entry Workstations subsequent to an OPEN SEARCH process as described in Section IV. of this RFP (see Diagram IV.B.1.). Ad ditional AFIRM candidates (i.e., records converted from AFIRM data as described in RFP requirement VI.B.7., Conversion of Existing AFIRM Data) may be included in the candidate list. During operational use of the system, the Contractor is responsible for verification of all candidates on all candidate lists regardless of the number of AFIRM candidates included in any candidate list.

 

3.         [Mandatory] Two-Finger CLOSED SEARCH Accuracy Requirement

For all CLOSED SEARCH requests where the search request is made with two (2) fingerprint images and the correct database record is selected for the match and this record has two (2) corresponding and useable finger records in the database, the CA SFIS must produce a correct "Hit" indication at least 99.9% of the time.

For all CLOSED SEARCH requests where the search request is made with two (2) fingerprint images and the database record selected for the match does not correspond to the search record, the CA SFIS must produce a "NO CANDIDATES FOUND" indication at least 99.9% of the time.

4.         [Mandatory] Single-Finger CLOSED SEARCH Accuracy Requirement

For all CLOSED SEARCH requests where the search request is made with one (1) fingerprint image and there is at least one (1) corresponding and useable finger record in the database, the CA SFIS must produce a correct "Hit" indication at least 99.0% of the time.

For all CLOSED SEARCH requests where the search request is made with one (1) fingerprint image and there is not a corresponding set of finger records in the database, the CA SFIS must produce a "NO CANDIDATES FOUND" indication at least 99.0% of the time.

2.         Description of Accuracy Tests

CA SFIS match accuracy will be measured several times before Final Acceptance of the system. The first system matching accuracy measurement will be made during the Benchmark Accuracy Test. The Benchmark Accuracy Test will be conducted within two (2) months of final Contract signature by the State.

1.         Benchmark Accuracy Test

a.         [Mandatory] The Bidder must conduct a system accuracy test against the converted AFIRM database (see Section I, Key Action Dates, for schedule). The test will be based on a minimum of 500 two-finger records searched against a corresponding set of 500 two-finger records. The Bidder is responsible for supplying the test system and for development of the 500 sets of test images (target and search images). The Bidder must also load the AFIRM records onto the background database. The minimum acceptable search accuracy rate achieved during the Benchmark Accuracy Test is 96% (two-finger OPEN searches against corresponding two-finger records). All searches conducted during the Benchmark Accuracy Test will be run against the entire database of AFIRM records used as the background database plus the target records loaded by the Bidder; i.e., every search record will be matched against every record in the test database (background records and target records). The Bidder must demonstrate that the AFIRM records used as the background records for the test cannot be distinguished from the target records added by the Bidder.

Note:. The accuracy rate achieved during the Benchmark Accuracy Test will only be used to assure the State that the system’s matching subsystem is functional prior to initial implementation of the system. Passing the Benchmark Accuracy Test accuracy tests does not mean that the Bidder has fulfilled the accuracy requirements required for the installed system.

b.         [Mandatory] The Bidder is responsible for converting the AFIRM database and loading the CA SFIS database with fingerprint images that will be used in the Benchmark Accuracy Test.

2.         Factory Acceptance Test

a.         [Mandatory] During the Factory Acceptance Test the Bidder must conduct system throughput and accuracy tests against the converted AFIRM database of two-finger records. The test will be based on a minimum of 500 two-finger records searched against a corresponding set of 500 two-finger records. The Bidder is responsible for supplying the test system and for development of the 500 sets of test images (target and search images). The minimum acceptable search accuracy rate achieved during the Factory Acceptance Test is 96% (two-finger OPEN searches against corresponding two-finger records). All searches conducted during the Factory Acceptance Test will be run against the entire database of AFIRM records used as the background database plus the target records loaded by the Bidder; i.e., every search record will be matched against every record in the test database (background records and target records). The Bidder must demonstrate that the AFIRM records used as the background records for the test cannot be distinguished from the target records added by the Bidder.

Note:. The accuracy rate achieved during the Factory Acceptance Test will only be used to assure the State that the system’s matching subsystem is functional prior to initial implementation of the system. Passing the Factory Acceptance Test accuracy tests does not mean that the Bidder has fulfilled the accuracy requirements required for the installed system.

b.         [Mandatory] The Bidder is responsible for converting and loading the CA SFIS database with fingerprint images that will be used in the Factory Acceptance Test.

3.         Description of System Accuracy Tests

A System Accuracy Test (SAT) will be performed periodically on the system to determine if the system meets the minimum accuracy levels required of the operational CA SFIS. The first SAT will be conducted immediately after all "Existing Caseload" records have been input to the CA SFIS (see Section IV, Table IV.E.1.).

The System Accuracy Test will be conducted with a test set of six thousand (6,000) records. Using a sample size of 6,000 records, a test having a 95% Level of Confidence will have the following Confidence Intervals;

o        0.5% Confidence Interval for a system that has a predicted accuracy of 96% (Two Finger OPEN SEARCH);

o        0.55% Confidence Interval for a system that has a predicted accuracy of 95% (Single Finger OPEN SEARCH);

o        0.08% Confidence Interval for a system that has a predicted accuracy of 99.9% (Two Finger CLOSED SEARCH); and,

o        0.25% Confidence Interval for a system that has a predicted accuracy of 99% (Single Finger CLOSED SEARCH).

System Accuracy Tests will be done in four parts as follows:

a.         System Accuracy Test, Part 1

System Accuracy Test, Part 1 will be comprised of 6,000 two-finger OPEN searches against corresponding two-finger database records.

The first time a SAT is performed, 6,000 welfare recipients will be asked to return to their respective welfare offices to be re-fingerprinted and re-photographed (as per a "normal" search input transaction). Each of the welfare recipients asked to return for a fingerprint check will be individuals who have already been entered into the CA SFIS database and whose records have never been subsequently purged from the CA SFIS database.

After each of the 6,000 search records are saved locally at the Input Workstation for subsequent transmission to the Central Site system, the Input Workstation will create a copy of the search request transaction onto a high-density magnetic tape media. After all 6,000 search records are recorded onto magnetic media, all media will be collected by the State. The State will hold this data for use in future System Accuracy Tests.

When the search transaction is initiated at the Remote Input Workstation, each of the 6,000 search records will be given a special, unique CIN that has not been recorded in either the SAWS TA database or CA SFIS database; when the record is submitted to the Central Site for processing, the fact that a CIN "unknown" to the CA SFIS database has been assigned as the primary identifier for the search record will force the CA SFIS to perform an OPEN SEARCH on each of the 6,000 records (see Diagram IV.B.1., Proposed CA SFIS Workflow).

In addition to the special CIN that is assigned to the search record as the primary search identification number, the actual CIN of the welfare client (i.e., the CIN for the client that is currently in the CA SFIS database) will also be recorded within the search record in a secondary index number field. The actual CIN number (now recorded as a secondary number within the search record) will be used in the System Accuracy Test, Parts 3 & 4 (described below).

All 6,000 searches will be processed by the CA SFIS. At the conclusion of the search process for each of the 6,000 search requests (i.e., after verification of the OPEN SEARCH candidate list for each search or after the CA SFIS match response returns a "NO CANDIDATES FOUND" message), the CA SFIS will purge the transaction from the Central Site transaction queues. The search record must not be recorded in the CA SFIS database. In addition, fingerprint images from the search record must not be substituted for CA SFIS database images if the search record image is of higher quality than the CA SFIS database record (in the case of SAT search records, requirement VI.B.1.25. [Replacement of Fingerprint Images with Images of Higher Quality] must not be part of the transaction process).

After all 6,000 search requests have been processed, search results for all searches will be compiled and a Measured Accuracy rate will be determined by dividing the sum of the total number of searches performed minus the number of searches that resulted in a "No-Hit" (or "Miss" or "NO CANDIDATES FOUND") by the total number of searches performed and multiplying the result by 100 to arrive at a "Measured Accuracy."

(total number of searches - total number of "No-Hits") / (total number of searches) x 100 = Measured Accuracy (expressed as a percentage)

The search accuracy rate for the System Accuracy Test, Part 1, must be within the range

(TFOS - Confidence Interval) £ Measured Accuracy £ (TFOS + Confidence Interval)

Where

TFOS =

Two Finger OPEN SEARCH accuracy rate specified in the Bidder’s Bidder Qualification Response (see Section V.B.)

 

Confidence Interval =

0.5% (corresponding to a test with a 95% Level Of Confidence, a test size of 6,000 records, and a predicted accuracy rate of [at least] 96%)

 

Measured Accuracy =

(total number of searches - total number of "No-Hits") / (total number of searches) x 100 = Measured Accuracy (expressed as a percentage)

Since the upper limit of the range is meaningless in this case, the acceptable range for the Two-Finger OPEN SEARCH accuracy rate is

TFOS - 0.5% £ Measured Accuracy £ 100%

Part 1 of the System Accuracy Test will be considered as PASSED if the Measured Accuracy of the Two-Finger OPEN SEARCH equals or exceeds the Two-Finger OPEN SEARCH accuracy defined in the Contractor’s Bidder Qualification Response minus 0.5%.

For example, if, in their Bidder Qualification Response, the Bidder proposes a 97% Two-Finger OPEN SEARCH accuracy rate, then, in order to pass Part 1 of the System Accuracy Test, the Two-Finger OPEN SEARCH accuracy rate must be at least 96.5% (97.0% - 0.5%).

b.         System Accuracy Test, Part 2

System Accuracy Test, Part 2 will be comprised of 6,000 single-finger OPEN searches against corresponding CA SFIS database records.

The test set recorded on magnetic tape during the first time that the System Accuracy Test, Part 1 is run will be used in the System Accuracy Test, Part 2. The Contractor will copy the data onto a second set of magnetic media; the Contractor will modify this second test set copy so that all search requests have one fingerprint image per search record. The images will be randomly selected (right hand or left hand) from the original set when constructing each single-finger test set record.

The CIN that was used for the System Accuracy Test, Part 1 test will also be used in the System Accuracy Test, Part 2; this will force the CA SFIS to perform an OPEN SEARCH on each of the 6,000 records (see Diagram IV.B.1., Proposed CA SFIS Workflow).

All 6,000 searches will be processed by the CA SFIS. At the conclusion of the search process for each of the 6,000 search requests (i.e., after verification of the OPEN SEARCH candidate list for each search or after the CA SFIS match response returns a "NO CANDIDATES FOUND" message), the CA SFIS will purge the transaction from the Central Site transaction queues. The search record must not be recorded in the CA SFIS database. In addition, fingerprint images from the search record must not be substituted for CA SFIS database images if the search record image is of higher quality than the CA SFIS database record (in the case of SAT search records, requirement VI.B.1.25. [Replacement of Fingerprint Images with Images of Higher Quality] must not be part of the transaction process).

After all 6,000 search requests have been processed, search results for all searches will be compiled and a Measured Accuracy rate will be determined by dividing the sum of the total number of searches performed minus the number of searches that resulted in a "No-Hit" (or "Miss" or "NO CANDIDATES FOUND") by the total number of searches performed and multiplying the result by 100 to arrive at a "Measured Accuracy."

(total number of searches - total number of "No-Hits") / (total number of searches) x 100 = Measured Accuracy (expressed as a percentage)

The search accuracy rate for the System Accuracy Test, Part 2, must be within the range

(95% - Confidence Interval) £ Measured Accuracy £ (95% + Confidence Interval)

Where

Confidence Interval =

0.55% (corresponding to a test with a 95% Level Of Confidence, a test size of 6,000 records, and a predicted accuracy rate of [at least] 95%)

 

Measured Accuracy =

(total number of searches - total number of "No-Hits") / (total number of searches) x 100 = Measured Accuracy (expressed as a percentage)

Since the upper limit of the range is meaningless in this case, the acceptable range for the Single-Finger OPEN SEARCH accuracy rate is

94.45% £ Measured Accuracy £ 100%

Part 2 of the System Accuracy Test will be considered as PASSED if the Measured Accuracy of the Single-Finger OPEN SEARCH equals or exceeds 94.45%.

c.         System Accuracy Test, Part 3

System Accuracy Test, Part 3 will be comprised of 6,000 two-finger CLOSED searches against corresponding two-finger database records.

The test set recorded on magnetic tape during the first time that the System Accuracy Test, Part 1 is run will be used in the System Accuracy Test, Part 3. The Contractor will copy the data onto a third set of magnetic media. The Contractor will modify the third test set copy so that the CIN that was recorded within the (Part 1) search record as a secondary index number (i.e., the actual CIN of the welfare client that is currently in the CA SFIS database) will be recorded within the search record as the primary number for the search, thus replacing the "special" CIN used in Part 1.

When the each of the Part 3 test records are submitted to the Central Site for processing, the fact that the search record CIN is "known" to the CA SFIS database will force the CA SFIS to perform a CLOSED SEARCH on each of the 6,000 records (see Diagram IV.B.1., Proposed CA SFIS Workflow).

All 6,000 searches will be processed by the CA SFIS. At the conclusion of the search process for each of the 6,000 search requests (i.e., after verification of the CLOSED SEARCH), the CA SFIS will purge the transaction from the Central Site transaction queues. The search record must not be recorded in the CA SFIS database. In addition, fingerprint images from the search record must not be substituted for CA SFIS database images if the search record image is of higher quality than the CA SFIS database record (in the case of SAT search records, requirement VI.B.1.25. [Replacement of Fingerprint Images with Images of Higher Quality] must not be part of the transaction process).

After all 6,000 search requests have been processed, search results for all searches will be compiled and a Measured Accuracy rate will be determined by dividing the sum of the total number of searches performed minus the number of searches that resulted in a "No-Hit" (or "Miss" or "NO CANDIDATES FOUND") by the total number of searches performed and multiplying the result by 100 to arrive at a "Measured Accuracy."

(total number of searches - total number of "No-Hits") / (total number of searches) x 100 = Measured Accuracy (expressed as a percentage)

The search accuracy rate for the System Accuracy Test, Part 3, must be within the range

(99.9% - Confidence Interval) £ Measured Accuracy £ (99.9% + Confidence Interval)

Where

Confidence Interval =

0.08% (corresponding to a test with a 95% Level Of Confidence, a test size of 6,000 records, and a predicted accuracy rate of [at least] 99.9%)

 

Measured Accuracy =

(total number of searches - total number of "No-Hits") / (total number of searches) x 100 = Measured Accuracy (expressed as a percentage)

Since the upper limit of the range is meaningless in this case, the acceptable range for the Two-Finger CLOSED SEARCH accuracy rate is

99.82% £ Measured Accuracy £ 100%

Part 3 of the System Accuracy Test will be considered as PASSED if the Measured Accuracy of the Two-Finger CLOSED SEARCH equals or exceeds 99.82%.

 

d.         System Accuracy Test, Part 4

System Accuracy Test, Part 4 will be comprised of 6,000 single-finger CLOSED searches against corresponding CA SFIS database records.

The test set recorded on magnetic tape for the System Accuracy Test, Part 3 will be used in the System Accuracy Test, Part 4. The Contractor will copy the data onto a fourth set of magnetic media; the Contractor will modify this fourth test set copy so that all search requests have one fingerprint image per search record; the images will be randomly selected (right hand or left hand) from the original set when constructing each single-finger test set record.

When the each of the Part 3 test records are submitted to the Central Site for processing, the fact that the search record CIN is "known" to the CA SFIS database will force the CA SFIS to perform a CLOSED SEARCH on each of the 6,000 records (see Diagram IV.B.1., Proposed CA SFIS Workflow).

All 6,000 searches will be processed by the CA SFIS. At the conclusion of the search process for each of the 6,000 search requests (i.e., after verification of the CLOSED SEARCH), the CA SFIS will purge the transaction from the Central Site transaction queues. The search record must not be recorded in the CA SFIS database. In addition, fingerprint images from the search record must not be substituted for CA SFIS database images if the search record image is of higher quality than the CA SFIS database record (in the case of SAT search records, requirement VI.B.1.25. (Replacement of Fingerprint Images with Images of Higher Quality) must not be part of the transaction process).

After all 6,000 search requests have been processed, search results for all searches will be compiled and a Measured Accuracy rate will be determined by dividing the sum of the total number of searches performed minus the number of searches that resulted in a "No-Hit" (or "Miss" or "NO CANDIDATES FOUND") by the total number of searches performed and multiplying the result by 100 to arrive at a "Measured Accuracy."

(total number of searches - total number of "No-Hits") / (total number of searches) x 100 = Measured Accuracy (expressed as a percentage)

The search accuracy rate for the System Accuracy Test, Part 4, must be within the range

(99.0% - Confidence Interval) £ Measured Accuracy £ (99.0% + Confidence Interval)

Where

Confidence Interval =

0.25% (corresponding to a test with a 95% Level Of Confidence, a test size of 6,000 records, and a predicted accuracy rate of [at least] 99.0%)

 

Measured Accuracy =

(total number of searches - total number of "No-Hits") / (total number of searches) x 100 = Measured Accuracy (expressed as a percentage)

Since the upper limit of the range is meaningless in this case, the acceptable range for the Two-Finger CLOSED SEARCH accuracy rate is

98.75% £ Measured Accuracy £ 100%

Part 4 of the System Accuracy Test will be considered as PASSED if the Measured Accuracy of the Single-Finger CLOSED SEARCH equals or exceeds 98.75%.

4.         System Accuracy Test Requirements

a.         [Mandatory] The minimum acceptable search accuracy rate achieved during a System Accuracy Test Part 1 (two-finger OPEN searches against corresponding CA SFIS two-finger database records) is as specified in requirements VI.G.2.3.a. and VI.G.1.1.

b.         [Mandatory] The minimum acceptable search accuracy rate achieved during a System Accuracy Test Part 2 (single-finger OPEN searches against corresponding CA SFIS database records) is as specified in requirements VI.G.2.3.b. and VI.G.1.2.

c.         [Mandatory] The minimum acceptable search accuracy rate achieved during a System Accuracy Test Part 3 (two-finger CLOSED searches against corresponding CA SFIS two-finger database records) is as specified in requirements VI.G.2.3.c. and VI.G.1.3.

d.         [Mandatory] The minimum acceptable search accuracy rate achieved during a System Accuracy Test Part 4 (single-finger CLOSED searches against corresponding CA SFIS database records) is as specified in requirements VI.G.2.3.d. and VI.G.1.4.

e.         [Mandatory] A complete System Accuracy Test must be conducted during the Final Acceptance Test, Part 2, after all existing client records have been "converted." In addition, State reserves the right to conduct additional System Accuracy Tests at any time during the life of the contract; in this event, the State will give notice of it’s intent to conduct the test at least fifteen (15) working days prior to the start of the test.

f.          [Mandatory] Test data used in each System Accuracy Test will be image data collected at certain CA SFIS workstations (designated by the State). The search test set used in the System Accuracy Test must be no smaller than 6,000 sets of two (2) finger data records.

g.         After the System Accuracy Test has been run, all "No-Hit" results will be examined. For each test "No-Hit," the State may elect to throw the result out of consideration if, in the sole opinion of the State, that particular test result is not a fair test of the system. Search sets that are thrown out as a result of this consideration will not be counted in the overall totals for the SAT; however, in each instance, at the sole discretion of the State another set of data may be substituted for the invalidated set of data. RFP requirement VI.C.1.13. shall apply to the determination of system accuracy scores after all test results have been examined.

 h.        [Mandatory] The Contractor must save all search test set images on to a high-capacity storage medium at the Remote Input Workstation. All images must be stored as "raw" (i.e., full resolution, uncompressed) images; in addition, the Contractor may elect to store the compressed images and corresponding minutiae sets for each record. The State will store the test set images for subsequent testing; this will obviate the need to recall existing health and welfare clients into the County Welfare Office each time a System Accuracy Test must be run.

i.          [Mandatory] After the first System Accuracy Test has been run, the State intends to keep the high-capacity storage medium containing test records in it’s possession. The Bidder must propose a method to enable a batch launch of test searches from the high-capacity storage medium (containing the test data captured during the first System Acceptance Test) during subsequent System Accuracy Tests.

j.          [Mandatory] The minimum set of data returned from each System Accuracy Test search is

                                                                                 i.            Search and Target Record Numbers,

                                                                               ii.            "Match," "No-Match" indication for each search,

                                                                              iii.            demographics used to limit search extent (list demographics of search record as well as demographics of candidate record);

                                                                              iv.            "quality" scores of the search and target fingers (if the Bidder’s system produces an image quality indication), and

                                                                               v.            match score.

The data listed above will be returned for all System Accuracy Test searches; data returned from each System Accuracy Test search will include at least fifty (50) non-AFIRM target records. For example; if 1., a particular System Accuracy Test search results in a candidate list; and 2., the 50th highest-scoring non-AFIRM candidate is listed 60th in the candidate list (i.e., ten AFIRM data records had match scores higher than the 50th highest-scoring non-AFIRM candidate); then data must be returned for the top 60 candidates.

k.         After the first System Accuracy Test, subsequent System Accuracy Tests will be conducted during non-operational hours (e.g., between 7PM and 7AM weekdays and during any hour of weekends).

H.      Use of the State’s Health and Welfare Agency Data Center (HWDC) Communication Network

[Mandatory] The Bidder must use the State HWDC Communication Network in the CA SFIS project.

I.        Back Up & Recovery Requirements

1.         [Mandatory] The Contractor must provide back up databases, subsystems, and processes for each database, subsystem, and process which is critical to CA SFIS so that, in the event of a malfunction within any component or components of the Central Site system, the CA SFIS can be restored to full operational status and be fully operational within 2 hours of original system failure. In addition, the Contractor must develop a Back Up & Recovery Plan acceptable to the State that will be used to carry out the requirement specified in paragraph VI.I.1. The Back Up & Recovery Plan will include all necessary backup and recovery planning procedures so that no operator reentry of data is required to restore the system in the event of a system failure due to loss of a system database or failure of any system component or components. The Contractor must provide a copy of the Back Up & Recovery Plan to the State within sixteen (16) weeks after final signature of the Contract by the State. The Contractor must update this plan on a quarterly basis. The Contractor will be required to test the Back Up & Recovery Plan when requested by the State.

2.         [Mandatory] The Contractor must develop a Disaster Recovery Plan acceptable to the State that will be used to restore the CA SFIS to full operational status in the event of complete destruction of the Central Site facility. In this plan, the Contractor must include all necessary backup and disaster recovery planning procedures so that no operator reentry of data is required to restore the CA SFIS in the event of destruction of the Central Site system. The Disaster Recovery Plan must include the sequence of tasks that must be accomplished in order to recover from complete system destruction and the Contractor’s cost for implementing the Disaster Recovery Plan. The Contractor must address issues in the HWDC Network Disaster Recovery Plan dealing with providing service to the State and counties from a backup recovery site in the Contractor's Disaster Recovery Plan. The Contractor must provide a copy of the Disaster Recovery Plan to the State within sixteen (16) weeks after final signature of the Contract by the State. The Contractor must update this plan on a quarterly basis.

3.         [Mandatory] Logs shall contain detailed information regarding transactions being performed. Logs shall also report errors. Report generation and log review shall be accessible by the State while the system is running and shall not interrupt any ongoing logging or processing of information.

4.         [Mandatory] All transactions received by the database management system shall be journalled. The system shall have the capability to store or transfer journal data to on-line storage and to magnetic tape or any other high capacity off-line storage medium.

5.         [Mandatory] The system shall provide for the logging of operating system-generated hardware and software error reports. These reports shall be journalled to magnetic tape and shall be made available to the State System Administrator in an easy-to-read electronic and printed formats acceptable to the State that clearly state the nature and extent of the hardware and/or software problem reported.

6.         [Mandatory] On-Line Transaction Recovery and Data Backup

a.         The system must create on-line mirror (backup) copies of all dynamic portions of image and minutia databases, as well as transactions waiting in queues.

b.         After entering the system queues, transactions shall not be lost if a system anomaly occurs that requires system restart. When the system is restarted, previously queued transactions shall start with no system administrator interaction. System transaction statistics shall not be reset unless reset by the State System Administrator. During Central Site downtime, the remote operators shall be able to continue acquisition, subject to the workstation’s acquisition queue capacity.

c.         The State shall have the ability to operate the CA SFIS twenty-four (24) hours/day, seven (7) days/week; in this case, excluding scheduled downtime, Central Site availability shall be a minimum of ninety-eight percent (98%) or as specified in the Bidder’s Qualification Response.

7.         [Mandatory] Off-Line Transaction Recovery and Data Backup

a.         Off-Line Backup: Off-line backup will consist of backing up alphanumeric and minutia data from both dynamic and static magnetic databases onto high capacity off-line storage media. The image database will be backed up automatically on a duplicate high capacity off-line storage media, which will also contain an additional copy of all alphanumeric and minutia records. Duplicate high capacity off-line storage media will be stored off-site to safeguard data in the event of major system failure.

b.         Restoration: Restoration may be required when data is corrupted during processing or when a magnetic disk fails. The system must provide the capability to restore data in two ways:

                                                                                 i.            For dynamic data. If the information on a magnetic disk has become unavailable, it shall be restored by replacing the failed disk (if necessary) and copying the data from the corresponding backup volumes.

                                                                               ii.            For dynamic and static data. If the information in the master and, if applicable, the mirror volume has become unavailable, it shall be restored by copying the data from the backup tape and applying all applicable journalled transactions.

The restoration process must recreate the database by first restoring the database as it existed at the time of the last backup, and second, applying all subsequently journalled transactions.

c.         Recovery: The recovery procedure must recreate all data and minutia records since the last backup.

a.       Database Reorganization: It shall be possible to reorganize minutia databases. Reorganization must not inhibit remote workstation acquisition activities and must be performed off line. Central system downtime must be limited to no more than two (2) days for database reorganization. Database reorganization shall be limited to weekends and/or during non-business hours during weekdays.

 

8.         [Mandatory] Contractor shall provide procedures/methodologies and train State operators to backup image and minutiae databases, and recover from media and equipment failures.

9.         [Mandatory] The system shall have a process to recover minutiae database disks from mirrored secondary storage or recover the database by reprocessing previously journalled update transactions. Recovery shall not require re-reading of fingerprints.

10.        [Mandatory] Transactions in process during a system failure shall be automatically re-introduced or continued from a previous checkpoint.

11.        [Mandatory] Off-Site Storage and Restoration of System Software: Application software and operating system software must be provided to the State for off-site storage.

J.       System Reliability Requirements

1.         Workstation Reliability

1.         [Mandatory] Workstation reliability will be measured weekly (Monday through Friday) during actual in-use hours per workstation when the workstations are actually used by the State and/or counties. On a weekly basis, the system must achieve the following Workstation Reliability measurements:

a.         The Average Workstation Reliability for all State and county-operated Workstations in the CA SFIS must be 98% or as specified in the Bidder Qualification Response;

b.         No more than 5% of the State and county-operated Workstations may have an individual average Workstation Reliability of less than 95%;28 and,

c.         No single State and county-operated Workstation may have a Workstation Reliability level below 90%.

2.         [Mandatory] The following conditions will be considered as 100% of the Workstation being down and will count as one Downtime Hour or fraction thereof for each hour that the condition continues:

a.       Failure or malfunction of the workstation’s transaction log storage capability;

b.       Failure or malfunction of all disk drive storage capability;

c.       Failure or malfunction of the workstation monitor;

d.       Failure or malfunction of any functionality normally available from the workstation;

e.       Failure or malfunction of Bidder-supplied communications equipment at the remote site workstation that causes the failure of communications between the workstation and the central site;

f.         Failure or malfunction of the Live Scan device (if one is attached to the workstation; or,

g.       Failure or malfunction of the Photo capture camera (if one is attached to the workstation).

Failure or malfunction of the workstation printer will be considered as 50% of the Remote or Central Site Workstation being down and will count as one-half Downtime Hour or fraction thereof for each hour that the condition continues.

 3.        [Mandatory] Workstation Reliability will be computed as follows:

[(Total Scheduled Hours - Total Adjusted Down Time) / Total Scheduled Hours] x 100 = Workstation Reliability (expressed as a percentage)

Where

Total Scheduled Hours =

Sum of all scheduled operational hours for all State-operated CA SFIS workstations

 

Total Adjusted Down Time =

Sum of all Adjusted Down Time hours (as defined in paragraph VI.J.1.2.) for all State-operated CA SFIS workstations

Workstation Reliability requirement will be met if the Workstation Reliability equals or exceeds 98% (or higher as defined in the Contractor’s Bidder Qualification Response).

2.         Central Site Reliability

1.         [Mandatory] Central Site Reliability will be measured weekly (Monday through Friday). Between the hours of 7A.M. to 7P.M. (or actual in-use hours when the system is used by the State outside of the period between 7:00 A.M. to 7:00 P.M.), Monday through Friday, during any given week, the average uptime percentage for the CA SFIS Central Site must be 98% or as specified in the Bidder Qualification Response.

2.         [Mandatory] The following conditions will be considered as 100% of the Central Site being down and will count as one Central Site System Downtime Hour or fraction thereof for each hour that the condition continues:

a.       Failure or malfunction of the Central Site’s Contractor-supplied capability to maintain communications between the remote sites and the Central Site;

b.       Failure or malfunction of the Central Site’s transaction log storage capability;

c.       Failure or malfunction of the RDBMS capabilities of the system;

d.       Failure or malfunction of the database management capabilities of the system;

e.       Failure or malfunction of the Central Site’s capability to control the flow of transactions within the Central Site system; or

f.         Failure or malfunction of the subsystem or workstations that support match verifications at the Central Site. If the system is configured with more than one verification workstation at the Central Site and if one (or more) of these workstations fail or malfunction, one Central Site System Downtime Hour will be computed as follows:

 

(Number of Verification Workstations Failed / Total Number of Verification Workstations) x one hour = one Central Site System Downtime Hour or fraction thereof for each hour that the condition continues

3.         [Mandatory] Each of the following conditions will be considered as 50% of the Central Site being down and will count as one-half Central Site System Downtime Hour or fraction thereof for each hour that the condition continues:

a.         Failure or malfunction of Central Site’s capability to retrieve photo and/or fingerprint images; or

b.         Failure or malfunction of Central Site’s capability to perform image-to-image matching. If the system is configured with more than one matching subsystem at the Central Site and if one (or more) of these subsystems fail or malfunction, one Central Site System Downtime Hour will be computed as follows:

(Number of Matching Subsystems Failed / Total Number of Matching Subsystems) x one hour = one-half (1/2) Central Site System Downtime Hour or fraction thereof for each hour that the condition continues

 

4.         [Mandatory] Central Site Reliability will be computed as follows:

[(Total Scheduled Hours - Total Adjusted Down Time) / Total Scheduled Hours] x 100 = Central Site Reliability (expressed as a percentage)

Where

Total Scheduled Hours =

Sum of all scheduled operational hours for the Central Site

 

Total Adjusted Down Time =

Sum of all Adjusted Down Time hours (as defined in paragraphs VI.J.2.2. and VI.J.2.3.) for the Central Site

Central Site Reliability requirement will be met if the Central Site Reliability equals or exceeds 98% (or higher as defined in the Contractor’s Bidder Qualification Response).

5.         [Mandatory] Downtime Procedures: The Bidder shall develop automated and manual downtime procedures to be used to restore the system in the event of downtime.

3.         Test Bed System Reliability

1.         [Mandatory] Test Bed System reliability will be measured weekly (Monday through Sunday). The Average Uptime Percentage for the Test Bed System must be 98%.

2.         [Mandatory] Failure or malfunction of any system functionality in the Test Bed System will be considered as 100% of the Test Bed System being down and will count as one Test Bed System Downtime Hour or fraction thereof for each hour that the condition continues.

3.         [Mandatory] Test Bed System Reliability will be computed as follows:

[(Total Scheduled Hours - Test Bed System Down Time) / Total Scheduled Hours] x 100 = Test Bed System Reliability (expressed as a percentage)

 

Where

Total Scheduled Hours =

Sum of all scheduled operational hours for the Test Bed System

 

Test Bed System Down Time =

Sum of all Test Bed System Down Time Hours (as defined in paragraph VI.J.3.2.) for the Test Bed System

Test Bed System Reliability requirement will be met if the Test Bed System Reliability equals or exceeds 98%.

K.      System Installation

1.         Site Preparation

[Mandatory] Site preparation for the system shall be furnished by the State. The Contractor must furnish the State with a Site Prep Plan at least four (4) months prior to system installation. The Contractor must install the equipment in such a manner as to ensure that the equipment shall operate efficiently and be adequately protected from fire and water damage.

2.         Floor Plan

[Mandatory] Bidder shall submit a detailed floor plan with their Proposal showing equipment sizes, clearances, and suggested arrangement for equipment located at the Central Site. In addition, the Bidder will submit an installation plan which is representative of a Remote Input Workstation installation at the 224 sites listed in Exhibit VI-1. Bidders may assume that each Remote Workstation site will have a 10’x10’ area, 120vac/20 amp. power, and normal office air conditioning.

3.         Environmental Requirements

[Mandatory] Bidder shall provide all specifications for power, air conditioning, humidity, grounding, and/or elevated flooring requirements for the Central Site system and the representative CA SFIS site specified in Exhibit VI-1. All sites installations must comply with all federal, state and local law.

4.         Installation Sites

The CA SFIS Remote Workstations will be installed at the 224 sites listed in Exhibit VI-1 which is attached to this section.

The Central Site system will be installed at the HWDC Headquarters, Sacramento, California.

All Installations shall be in accordance with applicable laws, codes, ordinances and industry standards and conform to existing electrical system and wiring of the above referenced sites.

5.         System Re-Configurability

[Mandatory] The system shall minimize the extent and scope of system downtime that may be scheduled for the purpose of system maintenance such as hardware maintenance, upgrade of system components, and/or addition of system components (such as matchers).

6.         Data Storage Across Physical Storage Devices

[Mandatory] The system shall permit system database and index files to be spread across physical storage devices.