San Mateo County, California Request for Proposals

August 25, 2006

RFP #1178

CJIS Migration Pilot and Implementation

Proposals must be submitted to:

County of San Mateo, Purchasing Division 455 County Center, 5th Floor

Redwood City, CA 94063

No later than 3:00 P.M. (Pacific Time) on October 2, 2006 and be clearly marked

"RFP#1178 CJIS Migration - Pilot and Implementation"

i

TABLE OF CONTENTS 1. Introduction............................................................................................................................. 1

1.1. STATEMENT OF INTENT ............................................................................................... 2 1.2. SAN MATEO COUNTY.................................................................................................... 2 1.3. PROJECT BACKGROUND ............................................................................................. 2 1.4. PILOT OBJECTIVES ....................................................................................................... 3

1.4.1. Target Platform and Software ................................................................................... 3 1.5. THE PROCESS............................................................................................................... 3

1.5.1. Phase A – Initial Selection ........................................................................................ 3 1.5.2. Phase B – Pilot Conversion and Final Selection ....................................................... 4 1.5.3. Phase C – Full System Conversion / Migration ......................................................... 4

1.6. GUIDELINES................................................................................................................... 5 2. General Submission Requirements......................................................................................... 6

2.1. ISSUING AGENT............................................................................................................. 7 2.2. SUBMISSION REQUIREMENTS..................................................................................... 7 2.3. DELIVERY OF PROPOSAL ............................................................................................ 8 2.4. SUBMITTAL COSTS ....................................................................................................... 8 2.5. ACCEPTANCE OF SUBMITTAL REQUIREMENTS........................................................ 8 2.6. INTERPRETATIONS ....................................................................................................... 9 2.7. PROCUREMENT AND CONVERSION PILOT SCHEDULE ............................................ 9 2.8. PRE-PROPOSAL CONFERENCE................................................................................... 9 2.9. AWARD......................................................................................................................... 10 2.10. ORAL REPRESENTATIONS ..................................................................................... 10 2.11. CONFIDENTIAL MATTERS....................................................................................... 10 2.12. BACKGROUND CHECKS REQUIRED ...................................................................... 10 2.13. RETENTION OF RESPONDENTS' MATERIAL ......................................................... 11 2.14. PUBLIC RECORDS ACT DISCLAIMER..................................................................... 11 2.15. EQUAL BENEFITS .................................................................................................... 11 2.16. NON-DISCRIMINATION ............................................................................................ 11 2.17. JURY SERVICE ......................................................................................................... 12 2.18. COLLUSION AFFIDAVIT ........................................................................................... 12 2.19. NON-WAIVER BY ACCEPTANCE OF DEVIATION ................................................... 12 2.20. SUB-CONTRACTS .................................................................................................... 12 2.21. ASSIGNMENT OF CONTRACT AND/OR PAYMENT ................................................ 13

3. Detailed Submission Requirements ...................................................................................... 14 3.1. PROPOSAL FORMAT................................................................................................... 15 3.2. INTRODUCTORY MATERIAL ....................................................................................... 15 3.3. EXECUTIVE SUMMARY ............................................................................................... 15 3.4. SCOPE OF SERVICES ................................................................................................. 16 3.5. COMPANY BACKGROUND .......................................................................................... 16 3.6. RESPONSES TO CONVERSION / MIGRATION EXPERIENCE REQUIREMENTS...... 16 3.7. PROPOSAL DETAILS ................................................................................................... 17

3.7.1. Pilot Conversion / Migration .................................................................................... 17 3.7.2. Full Production Conversion / Migration ................................................................... 17 3.7.3. Target Platform....................................................................................................... 18

Hardware/Operating System ............................................................................................. 18 Database........................................................................................................................... 18

3.8. CONVERSION / MIGRATION PLAN ............................................................................. 19 3.9. CLIENT REFERENCES................................................................................................. 19 3.10. CONVERSION / MIGRATION SERVICES VENDORS............................................... 19 3.11. THIRD-PARTY CONVERSION / MIGRATION SERVICES FIRMS............................. 20 3.12. CONVERSION / MIGRATION TEAM ROSTER.......................................................... 20 3.13. COST PROPOSAL .................................................................................................... 20

ii

3.14. EXCEPTIONS TO THE RFP ...................................................................................... 20 3.15. REQUIRED ATTACHMENTS..................................................................................... 21

4. Pilot and Full Conversion Detail ............................................................................................ 22 4.1. CURRENT MAINFRAME CONFIGURATION ................................................................ 23 4.2. CJIS INTERNAL SECURITY ......................................................................................... 25 4.3. CONVERSION / MIGRATION EXPECTATIONS ........................................................... 25

Source Code......................................................................................................................... 26 CICS BMS Map Source ........................................................................................................ 26 Datacom/DB Database ......................................................................................................... 26 VSAM and Sequential Files .................................................................................................. 26 Batch Processing Environment ............................................................................................. 26 System Facilities................................................................................................................... 27 Database Utilities.................................................................................................................. 27 External Interfaces................................................................................................................ 27 Application Development / Maintenance ............................................................................... 27 Transaction Processor .......................................................................................................... 27 Batch Job Processing ........................................................................................................... 27 Printed Output....................................................................................................................... 27 Miscellaneous....................................................................................................................... 27

4.4. Pilot conversion / Migration............................................................................................ 28 4.4.1. Pilot Location .......................................................................................................... 28 4.4.2. Conversion and Acceptance Testing ...................................................................... 28 4.4.3. Full conversion / migration ...................................................................................... 28 4.4.4. Inventory and Metrics for the Final Conversion / Migration Proposal....................... 29

5. Evaluation of Proposals ........................................................................................................ 30 5.1. SELECTION OF PARTICIPANTS.................................................................................. 31 5.2. EVALUATION CRITERIA AND SELECTION PROCESS............................................... 31 5.3. APPEAL PROCESS ...................................................................................................... 32

6. Deliverables.......................................................................................................................... 33 6.1. PILOT CONVERSION / MIGRATION ............................................................................ 34 6.2. CONVERSION / MIGRATION........................................................................................ 34 6.3. PRESENTATIONS ........................................................................................................ 35

Required Proposal Attachments .................................................................................................. 36 REQUIRED ATTACHMENTS................................................................................................... 37 ATTACHMENTS FOR REFERENCE PURPOSES................................................................... 37

Attachment 1 — Equal Benefits Compliance Declaration Form.................................................... 38 Attachment 2 — Equal Benefits Ordinance .................................................................................. 40

ORDINANCE NO. 04026.......................................................................................................... 41 Attachment 3 — Standard County Contract ................................................................................. 44 Attachment 4 — HIPAA Business Associate Requirements......................................................... 51 Attachment 5 — § 504 Compliance.............................................................................................. 55 Attachment 6 — Conversion / Migration Reference Form ............................................................ 57 Attachment 7 — Cost Spreadsheet.............................................................................................. 60 Attachment 8 — Staffing Matrix ................................................................................................... 62 Attachment 9 — Conversion / Migration Experience Requirements ............................................. 64 Appendix A — Pilot System Inventory.......................................................................................... 66

Pilot Conversion Inventory List ................................................................................................. 67 Programs Selected for the Pilot Conversion ............................................................................. 73

Online Inquiry .................................................................................................................... 73 Online Table Inquiry .......................................................................................................... 74 Online Table Update ......................................................................................................... 75 Online Display Search Inquiry – BKDSP ........................................................................... 77 Online Display Search Inquiry – CMPDSP ........................................................................ 78 Online Display Search Inquiry – CTDSP ........................................................................... 80

iii

J22334 (DAADHOC) – DA Ad Hoc Statistics Selection Criteria ......................................... 81 Online Display Transaction Log Search – LOGSCAN ....................................................... 82

Jobs Selected for the Pilot Conversion ..................................................................................... 83 Job CJSJD505 — Inmate Release Date Change Report ...................................................... 83 Job CJDJB313 — Monthly District Attorney Domestic Violence Report by Agency............... 83 Job CJSJ5115 — TRANSMIT BENCH WARRANT DATA TO AWS ..................................... 83 Job CJSJFTP1 — Daily FTP a Warrant Status from AWS.................................................... 84 Job CJSJTXLG — DAILY TRANSACTION LOG ARCHIVE / PURGE .................................. 85 Job CJSJ517A — ONLINE TRANSACTION LOG SCAN...................................................... 85 Job CJDJA351 — DISTRICT ATTORNEY AND AD HOC CHARGE REPORT..................... 85

DataQuery Reporting ............................................................................................................... 86 List Responsible Organization Location Table (S07)............................................................. 86 Inmate (K25) Race Count ..................................................................................................... 86 List Inmate w/Booking (K25+A86)......................................................................................... 86 Find CT-EVT-UPDT-CTL (B35) cross-referenced to Court-Event-TP (B26) .......................... 87 Felony Defts. Dism Following 1st Appear.............................................................................. 87

Datacom/DB Tables ................................................................................................................. 88 Appendix B — Utility Program Functions ..................................................................................... 91

SAN MATEO COUNTY

CALIFORNIA

1. Introduction

2

1.1. STATEMENT OF INTENT

The County of San Mateo intends to migrate its Criminal Justice Information System (CJIS) off of the current mainframe platform to another platform with all business logic intact. To that end, the County intends to hire a vendor who will work with the County to convert and migrate the current CJIS system programs (a mixture of IBM COBOL, Assembler and CA's IDEAL) and database (CA's Datacom/DB) to an alternate platform and relational database.

1.2. SAN MATEO COUNTY

San Mateo County is one of 58 California counties and one of the nine San Francisco Bay Area counties. It is located on the San Francisco Peninsula which lies between the Pacific Ocean to the West, the San Francisco Bay to the East, the City/County of San Francisco to the North, and the counties of Santa Clara and Santa Cruz to the South. San Mateo County employs approximately 5,000 full-time employees at more than eighty locations with an annual budget of approximately $1.2 billion. The County's primary emphasis is on providing health and social services, criminal justice, and law enforcement services. Additionally, the County provides land use planning and regulation, parks and recreation, public works, libraries, and a wide variety of other services for its residents. A five-member elected Board of Supervisors serves as the governing body of the County, establishing policy and exercising legislative authority. A County Manager, appointed by the Board, serves as the chief executive officer of the County and is generally responsible for the County's day-to-day operations.

1.3. PROJECT BACKGROUND

The San Mateo County Criminal Justice Information System (CJIS) currently resides on an IBM 7060-H50 (Multiprise 3000) system. It provides a highly integrated system for sharing data between the Sheriff's Office, the District Attorney's Office and the Courts in three environments: Production, Test, and QA. It is also used by twenty-one local police agencies. CJIS has been the primary automated criminal justice system in San Mateo County for more than fifteen years and suffers some limitations stemming from the age of the system as well as its implementation history. Also residing on the mainframe system are Adult Probation Data System (APDS), Probation Accounting, Juvenile Probation Data System (JPDS) and Juvenile Traffic System in addition to a few other non-justice applications. The Administrative Office of the Courts (AOC) has a statewide project underway that is intended to migrate all Court Management functions to a central statewide system. The Justice agencies of the county have desired for some time to get away from the expense of the mainframe system that currently houses the County’s CJIS system. With almost all of the mainframe-based application systems removed from the mainframe, the Chief Information Officer (CIO) made the decision to eliminate the mainframe by the end of fiscal year ’07-’08. Now, plans must be made and put into action to make mainframe elimination a reality. To that end, the County has come up with a strategic plan to move CJIS off of the mainframe system

3

and onto an alternate platform with all business logic intact. The process is centered on a three-phased RFP. The three phases are as follows:

A. Select three to four vendors to perform pilot migrations using their technologies and tools, and compile a full system inventory for vendor use to properly estimate a full migration

B. Perform the pilot migrations, engage the user community to test the pilot systems, and select a full conversion vendor based on pilot results and cost among other factors

C. Perform the complete conversion / migration of CJIS to the new platform

Vendor participation begins in Phase B.

1.4. PILOT OBJECTIVES

The pilot conversion is intended to serve as a proof of concept for each participating vendor’s conversion / migration solution and methodology. This will allow the County to observe each pilot process and the software tools employed to accomplish conversion of the CJIS pilot, and select the one vendor solution it determines will best accomplish the conversion / migration of the full production CJIS system. It is extremely important that the converted / migrated CJIS system integrate with the Courts’ new system once it is installed. This integration interface is anticipated to be Tibco, WebMethods or other similar service bus from a major vendor. The vendors selected must be able to provide on-site conversion of the pilot system programs, CICS maps, jobs and data tables/files (listed in Appendix A).

1.4.1. Target Platform and Software

The County of San Mateo has not pre-selected any hardware or software platform to house the final converted / migrated CJIS system. Each responding vendor is encouraged to propose the hardware and software configuration they feel would best serve the needs of the County and the CJIS user community in particular. Vendor solutions must perform equal to, or better than, the current mainframe platform with regard to terminal transaction response times as well as batch job execution time. When formulating their proposals, vendors should consider that the proposed hardware / software platform must simultaneously support Test (development), QA (user acceptance testing) and Production environments.

1.5. THE PROCESS

1.5.1. Phase A – Initial Selection In Phase A, the County will select three to four vendors from the respondents to this RFP to participate in pilot conversions using a small set of CJIS programs and data tables that represent all of the functionality found in the full CJIS system including CICS submitted batch reporting jobs, file transfers with other county systems, and communication with state systems. The CJIS user community test group will also test the pilot systems to ensure the resulting execution is satisfactory.

4

During Phase A and the early part of Phase B, the CJIS Team will be completing a full inventory of the CJIS system that will subsequently be provided to the vendors participating in the pilot. Those vendors will use this full inventory data to revise their initial conversion estimates to determine their final proposal for the full production system conversion / migration.

1.5.2. Phase B – Pilot Conversion and Final Selection

During Phase B, the vendors selected in Phase A will perform the pilot migration in the County’s data center with CJIS Team member participation. This phase is intended to be a “proof of concept” and should reveal any potential problems / issues the County could face during the full conversion / migration. This pilot will also provide information to the participating vendors that will help them better estimate the effort required for the full conversion / migration.

During the early part of Phase B, the CJIS Team expects to complete a full system inventory that will be provided to the selected vendors. This inventory is expected to include: details on software currently in use on the mainframe, the number and type of application programs (CICS and batch) with lines of code, number of CICS maps, number of Joblib, Proclib, Parmlib and Cntllib members and number of statements, number of Datacom/DB areas, tables and files, the number of rows, growth rate, number of VSAM files, number of sequential files, number of system users and the average number of users concurrently logged on.

At the end of Phase B, the County will hold a pilot post mortem with each vendor to review their pilot experience and discuss any problems or issues that arose in the process. Using the pilot experience and the County’s full CJIS system inventory, participating vendors will revise their initial estimates for the full conversion and submit their final proposal for the full conversion / migration.

Following the vendors’ submission of final proposals, the County will select one vendor to perform the full conversion / migration. Some of the factors used to determine which vendor is selected will include: prior conversion / migration experience, success of the pilot conversion, cost, and how well the vendor’s solution fits the County’s strategic plan for CJIS.

1.5.3. Phase C – Full System Conversion / Migration

The final phase of this CJIS conversion / migration project is the full conversion and migration of CJIS onto the new platform by the single selected vendor. This final conversion / migration is to be performed ON SITE in the County’s data center. Additional details can be found in Section 3 – Detailed Submission Requirements.

5

1.6. GUIDELINES

By submitting a proposal, interested parties are acknowledging:

• This RFP is a two-part request for conversion and migration services to complete a pilot conversion / migration (proof of concept) followed by an actual, complete migration (implementation).

• Pilot conversions will be performed at the County’s facilities in Redwood City, CA.

• Vendors must keep their pricing and responses to the business requirements the same across all of the proposals they submit.

• The County reserves the right to reject any or all proposals if it determines that they are not responsive to the RFP or if the proposals are judged not to be in the best interest of the County. The County reserves the right to reconsider any proposal submitted at any phase of the procurement. It also reserves the right to meet with select respondents at any time to gather additional information.

• All third party conversion / migration services proposed as part of this package are subject to the guidelines of this RFP, unless otherwise stated. The primary pilot conversion vendor will serve as the prime contact for all work related to this RFP.

• The County expects to enter into a conversion / migration services agreement with one selected vendor. If the County is not satisfied with the qualifications, cost, or experience of any third-party vendor/contractor, it reserves the right to request that the primary vendor propose a new third-party vendor/contractor. All firms submitting proposals, by virtue of doing so, are recognizing that the County retains this option.

• All respondents submitting proposals agree that their pricing is valid for a minimum of one year after proposal submission to the County. Pricing must be submitted on a "time and materials, not-to-exceed" basis. If there is a "residual" amount at the end of the project (difference between total contract amount and actual total costs), the County will retain the difference by simply not spending the funds. By contrast, if the cost ceiling is exceeded, the vendor is to finish the work at no additional compensation. Respondents are to provide all work effort needed to meet the detailed functional requirements as part of their proposal. Finally, the County reserves the right to ask respondents to resubmit proposal pricing on either a fixed fee basis or a combination of fixed and not-to-exceed basis. All firms submitting proposals are encouraged to submit the most competitive proposal possible, as the failure to do so may eliminate them from consideration.

When responding to this RFP, please follow all instructions carefully. Please submit proposal contents according to the outline specified and submit all hard copy and electronic documents according to the instructions. Failure to follow these instructions may be considered an unresponsive proposal and may result in immediate elimination from further consideration.

SAN MATEO COUNTY

CALIFORNIA

2. General Submission Requirements

7

2.1. ISSUING AGENT

The County of San Mateo's Purchasing Division is issuing this RFP. Any questions concerning conditions and specifications must be submitted in writing and received no later than 5:00 p.m. Pacific Time, on September 15, 2006. Send all inquiries to the attention of: Mr. Peter Tocchini County of San Mateo Purchasing Division 455 County Center, EPS 129 Redwood City, CA 94063-1663 Phone: 650-363-4408 Fax: 650-599-1702 Email: ptocchini@co.sanmateo.ca.us Questions received in writing or e-mail by the time and date specified will be answered in writing and sent to all respondents. Any attempt by a vendor to influence the procurement decision at any point in the selection process will lead to immediate elimination from further consideration.

2.2. SUBMISSION REQUIREMENTS

In order to facilitate the analysis of responses to this RFP, respondents are required to prepare their proposals in accordance with the instructions outlined in this part and elsewhere in this RFP. The County of San Mateo reserves the right to change any provisions of the Request for Proposals (RFP) on or before the deadline date for proposal submission. Changes to this RFP will be made by addendum. The County has the sole right to judge the substantive and technical adequacy of proposals and has the exclusive right to evaluate proposals responding to this RFP.

Respondents should ensure they have submitted their response to this RFP along with two Microsoft Word documents and three Microsoft Excel spreadsheets that contain: (1) Conversion / Migration References form (2) Third Party Contractor References form (3) Staffing Matrices (4) Cost Spreadsheets (5) Conversion / Migration requirements Two (2) copies of a CD-ROM must be submitted containing the entire contents of your proposal, and must be clearly identified with your business name and address. Please use the following checklist to ensure that you are submitting a complete proposal:

• Two (2) copies of the entire proposal submitted electronically on CD-ROM.

• Twelve (12) bound copies of the proposal (including hard copies of costs and requirement responses), presented in a professional manner.

• Contracting firm and third party contracting firm references on forms supplied in this RFP (Microsoft Word).

8

• Microsoft Excel workbook containing the staffing load matrix. This matrix should be consistent with the hours submitted in the cost estimate spreadsheets.

• Microsoft Excel workbook containing cost estimates. In addition, respondents are expected to estimate on a "time and materials, not-to-exceed" basis.

2.3. DELIVERY OF PROPOSAL

One manually signed original and eleven (11) photocopies of the proposal must be sealed in one package, clearly labeled with the RFP Number on the outside of the package, and delivered to: Mr. Peter Tocchini County of San Mateo Purchasing Division 455 County Center, EPS 129 Redwood City, CA 94063-1663 Phone: 650-363-4408 Any proposal not so packaged and marked will be rejected. All proposals must be delivered by U.S. mail or other couriers. Any electronic documents (submitted via e-mail) will not be considered. Proposals are due at 3:00 p.m. Pacific Time on October 2, 2006. It is the respondent's sole responsibility to ensure that its proposal is received by the submission deadline, whether delivered in person or sent by mail. The postmark date on a mailed proposal will not be considered with respect to timeliness of submission or receipt. Proposals received after the submission deadline will not be considered. All proposals must be signed by a corporate official authorized to obligate the organization to the commitments contained in the proposal. A proposal can be withdrawn by the vendor at any time, including after the deadline. A written request must be executed by respondent or duly authorized representative. Such a request must be submitted to: Mr. Peter Tocchini County of San Mateo Purchasing Division 455 County Center, EPS 129 Redwood City, CA 94063-1663 The withdrawal of a proposal will not prejudice your right to submit a new proposal prior to the deadline. Any proposal not withdrawn will constitute an irrevocable offer, for a period of one year, to provide the County with the services specified in the proposal.

2.4. SUBMITTAL COSTS

Costs for developing responses to the RFP are the sole responsibility of the respondents. Neither costs nor recovery of costs will be chargeable to the County in any manner.

2.5. ACCEPTANCE OF SUBMITTAL REQUIREMENTS

All terms and conditions of this RFP, any addenda, respondent's submissions and negotiated terms, are incorporated into the contract by reference as set forth herein. Submission of any

9

proposal indicates a respondent's acceptance of the conditions contained in this RFP, unless clearly and specifically noted otherwise in the proposal.

2.6. INTERPRETATIONS

Should any respondent find discrepancies, conflicts, omissions, or ambiguities in this RFP, the respondent should at once request, in writing, an interpretation from Mr. Peter Tocchini in the Purchasing Division. Required modifications or clarifications of the RFP will be made by addenda to the RFP. A written addendum is the only official method by which interpretation, clarification, or additional information will be provided by the County. Oral and other interpretations or clarifications will be without legal effect. The clarification will not divulge the source of the request. If a respondent fails to notify the County of a known error in the RFP (or one that the respondent reasonably should have known) prior to submission of their proposal, the respondent proposes at their own risk. If awarded a contract under these circumstances, the successful respondent will not be entitled to additional compensation or time due to the error or its later correction.

2.7. PROCUREMENT AND CONVERSION PILOT SCHEDULE

RFP Release Date........................................................................................... August 25, 2006 Pre-Proposal Conference (3:30 pm Pacific Time) ..................................... September 12, 2006 Due Date for All Written Questions and Inquiries (5:00 pm Pacific Time)... September 15, 2006 Responses Sent for Written Questions (5:00 pm Pacific Time).................. September 22, 2006 Proposals Due (3:00 pm Pacific Time)...............................................................October 2, 2006 Proposals Evaluated and Respondents Elevated to Pilot.................................October 17, 2006 Finalize, Approve Contracts........................................................................ November 17, 2006 Pilot Conversion Start-Up ............................................................................. December 1, 2006 Final Revised Proposals - Full Conversion/Migration (3:00 pm Pacific Time) February 22, 2007

The County of San Mateo has forecast these milestones and dates. They are subject to change at the County's sole discretion.

2.8. PRE-PROPOSAL CONFERENCE

Prospective respondents will have an opportunity to ask questions at a pre-proposal conference to be held on September 12, 2006 at 3:30 pm (Pacific Time) in Redwood City, CA. This conference will offer an opportunity to discuss the County's business needs and to clarify issues in this RFP. Respondents are strongly encouraged, but not required, to attend. County answers to questions will be documented in writing and mailed to parties who have requested copies of the RFP or have requested in writing to receive such notices. Contacts regarding the pre-proposal conference should be directed to Mr. Peter Tocchini, Purchasing Division. Pre-Proposal Conference: Date: September 12, 2006 Time: 3:30 P.M. Location: County of San Mateo 455 County Center - First Floor Conference Room 101 Redwood City, CA 94063

10

2.9. AWARD

The County reserves the right to accept or reject any or all proposals. The County reserves the right to waive any irregularities and technicalities and may, at its sole discretion, request a clarification or other information to evaluate any or all proposals. The County reserves the right, before awarding the contract, to require respondent(s) to submit evidence of qualifications or any other information the County may deem necessary. The County reserves the right to cancel the RFP in part, or in its entirety. The County reserves the right to: (1) accept the proposals of any or all of the items it deems, at its sole discretion, to be in the best interest of the County; and (2) the County reserves the right to reject any and/or all items proposed. This procurement will not be awarded solely on the basis of cost. A contract, if awarded, will be negotiated with the respondent who can best meet the County's needs. The County intends to enter into a conversion and migration services contract for the accepted proposal. Such a contract will be interpreted, construed, and given effect in all respects according to the laws of the State of California.

2.10. ORAL REPRESENTATIONS

Oral representations of vendor support, future offerings or pricing, and other material facts will not be considered by the County in the evaluation of proposals and responses to this RFP. Additionally, information, assistance, or services provided by vendors to County staff during requests for information, information research, sales presentations, and other such pre-RFP activities will not be considered during the evaluation of the proposals received in response to this RFP. The County will only act on information that is presented as written proposals and attachments to proposals submitted in accordance with the instructions specified by this RFP.

2.11. CONFIDENTIAL MATTERS

All data and information gathered by the respondent and its agents, including this RFP and all reports, recommendations, specifications, and data shall be treated by the respondent and its agents as confidential. The respondent and its agents shall not disclose, share, alter or communicate the aforesaid matters to a third party or use them in advertising, propaganda, and/or in another job or jobs, unless written consent is obtained from the County.

2.12. BACKGROUND CHECKS REQUIRED

Given that the vendor's personnel, as well as any sub-contractor's personnel, will be given access to County facilities and systems that contain sensitive information and are connected to other secured law enforcement networks and systems, all such personnel will be required to undergo a background check at the County's expense. Prior to the pilot, any employee, agent, or subcontractor of the vendors that will have access to any installation site, or to any records or information relating, pertaining to or included in the CJIS system shall be required to provide their name, date of birth and driver's license number

11

and shall submit to fingerprinting and a "California Identification Search" in order to verify the person's status and fitness to perform under this Agreement. The San Mateo County Sheriff's Office will have sole discretion on whether to approve or disapprove any such employee, agent, or subcontractor. 2.13. RETENTION OF RESPONDENTS' MATERIAL

The County reserves the right to retain all proposals regardless of which response is selected. No proposals will be returned to respondents.

2.14. PUBLIC RECORDS ACT DISCLAIMER

The California Public Records Act, Government Code Sections 6250 et. seq., defines public records as any writing containing information relating to the conduct of the public's business. This applies to proposals submitted pursuant to this RFP. The Public Records Act provides that public records shall be disclosed upon written request, and that any citizen has a right to inspect any public record, unless the document is exempt from the disclosure requirements. The County of San Mateo cannot represent or guarantee that any information submitted in response to the RFP will be confidential. If the County receives a request for any document submitted in response to this RFP, it will not assert any privileges that may exist on behalf of the person or business submitting the proposal. Rather, the County will notify the party whose proposal is being sought. In the event that a party who has submitted a proposal wishes to prevent disclosure, it is the sole responsibility of that party to assert any applicable privileges or reasons why the document should not be produced, and to obtain a court order prohibiting disclosure.

2.15. EQUAL BENEFITS

With respect to the provision of employee benefits, Contractor shall comply with the County Ordinance that prohibits contractors from discriminating in the provision of employee benefits between an employee with a domestic partner and an employee with a spouse.

2.16. NON-DISCRIMINATION

It is the County's policy that no person shall be excluded from participation in, denied benefits of, or be subject to discrimination under this Agreement on the basis of their race, color, religion, national origin, age, sex, sexual orientation, marital status, pregnancy, childbirth or related conditions, medical condition, mental or physical disability or veteran's status. Contractor shall ensure full compliance with federal, state and local laws, directives and executive orders regarding non-discrimination for all employees and subcontractors under this Agreement. A respondent doing business with the County is prohibited from discriminating against any employee, applicant, or client because of race, creed, color, national origin, religion, sex or age with regard to but not limited to the following: employment practices, rates of pay or other compensation methods, and training selection. Violation of the non-discrimination provisions shall subject the Contractor to penalties, to be determined by the County Manager, including but not limited to: i) termination of agreement between County and Contractor; ii) disqualification of the Contractor from bidding, proposing,

12

or being awarded a County contract for a period of up to 3 years; iii) liquidated damages of $2,500 per violation; iv) imposition of other appropriate contractual and civil remedies and sanctions, as determined by the County Manager. To effectuate the non-discrimination provisions, the County Manager shall have the authority to: i) examine Contractor's employment records with respect to compliance with this paragraph; ii) set off all or any portion of the amount described in this paragraph against amounts due to Contractor under the contract or any other contract between Contractor and County. Contractor shall report to the County Manager the filing by any person in any court of any complaint of discrimination or the filing by any person of any and all charges with the Equal Employment Opportunity Commission, the Fair Employment and Housing Commission, or any other entity charged with the investigation of allegations within 30 days of such filing, provided that within such 30 days such entity has not notified Contractor that such charges are dismissed or otherwise unfounded. Such notification shall include the name of the complainant, a copy of such complaint, and a description of the circumstance. Contractor shall provide County with a copy of its response to the Complaint when filed.

2.17. JURY SERVICE By submitting a proposal, each respondent shall comply with the County Ordinance with respect to provision of jury duty pay to employees and have and adhere to a written policy that provides that its employees shall receive from the respondent, on an annual basis, no less than five days of regular pay for actual jury service in San Mateo County. The policy may provide that employees deposit any fees received for such jury service with the respondent or that the respondent deduct from the employees regular pay the fees received for jury service. 2.18. COLLUSION AFFIDAVIT

By submitting a proposal, each respondent certifies that the quoted prices are genuine and not the result of collusion or any other activity that would tend to directly or indirectly influence the process.

2.19. NON-WAIVER BY ACCEPTANCE OF DEVIATION

The County's waiver of an immaterial deviation in a proposal shall in no way modify the RFP documents or excuse the vendor awarded the contract from full compliance with the specifications.

2.20. SUB-CONTRACTS

Nothing contained in this specification will be construed as establishing any contractual relationship between any sub-respondent(s) and the County. The respondent(s) will be fully responsible to the County for the acts and omissions of the sub-respondent(s) and their employees. After award of contract, any changes in subcontractors or sub-respondents requires prior written approval by the County.

13

2.21. ASSIGNMENT OF CONTRACT AND/OR PAYMENT

The respondent shall not enter into subcontracts, or assign, transfer, convey, sublet, or otherwise dispose of the ensuing contract, or any or all of its right, title or interest herein, or its power to execute such contract to any person, company, or corporation without prior written consent of the County. The respondent will be prohibited from publishing or releasing any information related to the requested services without the prior written permission of the County. All reports and other documents resulting from the ensuing contract will remain the sole property of the County.

14

SAN MATEO COUNTY

CALIFORNIA

3. Detailed Submission Requirements

15

3.1. PROPOSAL FORMAT

Respondents shall prepare their proposals in accordance with the instructions outlined in this section. Each respondent is required to submit the proposal in a sealed package. Proposals should be prepared as simply as possible and provide a straightforward, concise description of the respondent's capabilities to satisfy the requirements of the RFP. Utmost attention should be given to accuracy, completeness, and clarity of content. All parts, pages, figures, and tables should be numbered and clearly labeled. The proposal should be organized into the following major sections:

Proposal

Section Title

Title Page Letter of Transmittal Table of Contents 1. Executive Summary 2. Scope of Services 3. Company Background 4. Responses to Conversion / Migration Experience Requirements 5. Conversion / Migration Plan 6. Client References 7. Cost Proposal 8. Exceptions to the RFP 9. Sample Documents

10. Required Attachments

Instructions relative to each part of the response to this RFP are defined in the remainder of this section.

3.2. INTRODUCTORY MATERIAL

The Title Page must show the RFP number, subject, name of the respondent, address, telephone number and the date. In the Letter of Transmittal, respondents should include the names of the persons who will be authorized to make representations for the respondent, their titles, addresses, telephone numbers, and email addresses. The Table of Contents must include a clear identification of the material by section and by page number.

3.3. EXECUTIVE SUMMARY

(Proposal Section 1.0) This part of the response to the RFP should be limited to a brief narrative summarizing the respondent's proposal. The summary should contain as little technical jargon as possible and should be oriented toward non-technical personnel. This section should include cost quotations at a summary level for conversion / migration services. Please note that the executive summary should identify the primary engagement contact for the conversion / migration vendor, and the contact for any third party vendor being proposed. Contact information should include a valid e-mail address and a toll-free telephone number.

16

3.4. SCOPE OF SERVICES

(Proposal Section 2.0) This section of the respondent's proposal should include a general discussion of the respondent's overall understanding of the project and the scope of work proposed.

3.5. COMPANY BACKGROUND

(Proposal Section 3.0) Each proposal must provide the following information about the submitting respondent's company, the conversion / migration partner's company, and any third-party vendor/contractor being proposed to provide a business function, so that the County can evaluate the respondent's stability and ability to support the commitments set forth in response to the RFP. The County, at its option, may require a respondent to provide additional support or clarify requested information. Background information shall include:

• How long the company has been in business. • A brief description of the company size and organizational structure. • How long the company has been providing their conversion / migration services to

clients similar to the County. • Financial Statements that indicate the conversion / migration vendor has the financial

strength to carry out the project. • Listing of conversion / migration engagements at entities similar to the County by

name and state. The number of users, distinguished by type if relevant, should also be included.

• Any material (including letters of support or endorsement from clients) indicative of the respondent's capabilities.

• If partnering, how long the vendor has worked with the subcontractor and how many conversions / migrations the two parties have completed together.

• Evidence that the vendor is a corporation, is in good standing, and qualified to conduct business in California.

• Copies of business licenses, professional certifications, or other credentials.

3.6. RESPONSES TO CONVERSION / MIGRATION EXPERIENCE

REQUIREMENTS

(Proposal Section 4.0) Responses to the requirements listed in the Attachments to this RFP must be provided in this section of the respondent's proposal. Respondents should use the format provided and add explanatory details as necessary in a separate spreadsheet using the requirement number as a reference. The following answer key must be used when responding to the requirements:

H High level of knowledge M Medium level of knowledge L Low level of knowledge N None N/A Not Applicable

Respondents must use one code only per requirement. Any requirement that is answered in any other way will be treated as a negative/non-response. Respondents should feel free to create their own separate spreadsheet for lengthy comments on particular requirements that

17

are cross-referenced to specific requirement numbers. All requirement responses must be submitted in the format presented in the attached spreadsheet. The proposals submitted, including requirement responses, will become attached to the conversion / migration services contract. The requirements in Attachment 9 (Conversion / Migration Experience Requirements) include those that the County views as "must-have", "highly desirable", and "nice to have." It is in the County's best interest to obtain responses to this proposal from many different vendors. The County would like to know which of these numerous requirements can be met; however, vendors should not be dissuaded from submitting a proposal even if the response to many of the requirements is "not available."

3.7. PROPOSAL DETAILS

VENDOR SUBMISSIONS MUST INCLUDE TWO PROPOSALS: 1. Pilot conversion / migration 2. Final conversion / migration of the full production CJIS system

3.7.1. Pilot Conversion / Migration

The proposal for the pilot conversion is to include the costs (if any) for performing a pilot conversion using a small set of CJIS programs which are representative of all functions found in the full production CJIS system. Each vendor’s pilot conversion must:

1. Provide fully automated source code conversion to the target environment (NO MANUAL CONVERSION). Exceptions:

a) Any program using the BAIL-AMOUNT field. Since the CJIS database contains the text “NO BAIL” in a numeric field to show the subject is not to be released from jail on bail, such fields are to be converted to reflect a negative value of $10,000,000.00, and programs using this field will have to be modified manually to display the text “NO BAIL” when this negative amount is encountered.

b) Other cases on an as-required basis after review 2. Convert Datacom/DB database structure to a fully relational database

system. 3. Convert Datacom/DB database content (data) to ASCII format within a fully

relational database system. 4. Demonstrate that converted on-line, batch and utility programs function just

as the current mainframe versions do. 5. Demonstrate the converted system will concurrently support Test, QA and

Production environments. 6. Demonstrate all conversion software and tools for subsequent development,

maintenance, version control and promotion of application programs, screens etc. that the vendor intends to propose for the final full conversion.

3.7.2. Full Production Conversion / Migration

The proposal for the final conversion / migration is to include all costs for the conversion and migration of the full production CJIS system, including, but not necessarily limited to:

Specifications for required server(s)

18

Specifications for required network hardware Operating system software Relational database management system software Transaction processing system Batch execution environment including: Job scheduling system Report management and distribution

Application program/screen display development/maintenance software tools Application software version control and change management system

Vendors participating in the pilot will be given an opportunity to revise their proposal for the final production conversion / migration after completing the pilot, using the full system inventory being completed by the County Information Services staff.

3.7.3. Target Platform

Hardware/Operating System The County of San Mateo has not mandated any particular hardware or operating system platform for the target system. It should be noted though, that the County’s data center server complex currently is comprised predominantly of rack-mounted Dell Power Edge servers, and that County Information Services staff possesses the skills necessary to support Windows Server and Linux/UNIX environments. Each vendor should propose the hardware/operating system platform they feel would best serve the County’s needs keeping in mind that CJIS runs 24x7x365. The County would prefer to have a system that would be available during the time that system patches are applied as opposed to requiring a regularly scheduled system outage window as is currently done with the mainframe system. Vendors should provide two pricing options for the target hardware and operating system:

1. Detailed specifications for the target hardware and operating system configuration including number of CPUs, CPU type, memory etc. giving the County the option to purchase the hardware and operating system through its own vendors.

2. Pricing for the complete target hardware and operating system specified above, assuming such hardware and operating system will be provided by the vendor.

Database The target database for CJIS is to be a fully relational database. The County of San Mateo has designated Oracle as the database platform of preference. However, this does not preclude any vendor from proposing another relational database such as SQL Server or others if they can support such a proposal with a sound business case.

Vendors should provide two pricing options for the target database system:

1. Detailed specifications for the target database system including manufacturer, version, and any options, auxiliary modules etc. required for the database system to operate and function as tested during the pilot conversion / migration. This is to give the County the option to purchase the

19

hardware and operating system through its own vendors should it wish to do so.

2. Pricing for the complete target database system, options, auxiliary modules etc. required for the database system to operate and function as tested during the pilot conversion / migration, assuming the database system will be provided by the vendor.

See additional information in Section 4 - Pilot and Full Conversion Details

3.8. CONVERSION / MIGRATION PLAN

(Proposal Section 5.0) The respondent must provide a high-level methodology plan for the conversion / migration services to be provided. This information MUST include:

• Detailed methodology for conversion / migration services, which shall include estimated timeframe, overview of phases and milestones, assumptions, and assumed responsibilities.

• Detailed methodology for third-party conversion / migration services, which shall include estimated timeframe, overview of phases and milestones, assumptions, and assumed responsibilities.

• Work effort estimates: A "staff loading" chart listing resource utilization by each month should also be submitted on the form provided in the Attachments to this RFP. The County reserves the right to alter work effort estimates after further discussion with the vendor.

• Names, titles, and resumes of consultants/technicians who would be assigned to this project.

3.9. CLIENT REFERENCES

(Proposal Section 6.0) References for all respondents and subcontractors are integral to the County’s decision to award a contract. The County will not call respondents to tell them that their references will be contacted because all references provided will be contacted by the County during the selection process. Similarly, the County will not work through a respondent's Reference Manager to complete a reference. The names and phone numbers of the project manager for each reference must be listed. Failure to provide this information may result in the respondent being eliminated from consideration.

3.10. CONVERSION / MIGRATION SERVICES VENDORS

Using the forms attached to this RFP, respondents should provide at least five (5) client references that are similar in size and complexity to this procurement and have utilized similar systems in a comparable computing environment. Information should include at the minimum: date of conversion / migration, length of engagement, name of client reference, name of agency's project manager, jurisdiction, address, telephone and fax numbers. Please confirm that each reference is willing to participate in a 30 - 45 minute reference check call and inform references that they will be contacted by the County. All contact information must be correct and up-to-date. In addition, respondents should provide a list of their clients for the past three (3) years.

20

3.11. THIRD-PARTY CONVERSION / MIGRATION SERVICES FIRMS

Using the forms attached to this RFP, third-party conversion / migration firms addressing particular aspects of this project should provide at least five (5) client references that are similar in size and complexity to this procurement and have utilized similar systems. Submit references for fully completed engagements. Please confirm that each reference is willing to participate in a 30 - 45 minute reference check call and inform references that they will be contacted by the County. All contact information must be correct and up-to-date.

3.12. CONVERSION / MIGRATION TEAM ROSTER

Respondents must include a roster of conversion / migration team personnel to the County and assure that the proposed team will be working on the project. The selected vendors must obtain prior agreement from the County’s Project Manager with regard to replacement of any of the designated personnel on the project.

3.13. COST PROPOSAL

(Proposal Section 7.0) Respondents should submit an estimate of project costs. Pricing must be submitted on a "time and materials, not-to-exceed" basis. The respondent's cost proposal must be presented in the format provided in the Attachments to this RFP. The County reserves the right to contact respondents on cost and scope clarification at any time throughout the selection and negotiation processes. Finally, it is important that respondents use the cost format presented in this RFP and NOT their own format. Do NOT use "TBD" (to be determined) or similar annotations in the cells for cost estimates. All cells must be filled out. The County is asking respondents to estimate costs for all categories with the understanding that they may have to make assumptions. Such assumptions should be clearly stated. Failure to fully provide cost and work effort estimates will lead to elimination prior to discovery sessions (listed in Section 2.7). The County may award a conversion / migration contract, based on initial offers received without discussion of such offers. A respondent's initial offer should, therefore, be based on the most favorable terms available. The County may, in its discretion, conduct discussions with more than one respondent. It may also request revised pricing offers from such respondents, and make an award and/or conduct negotiations thereafter.

3.14. EXCEPTIONS TO THE RFP

(Proposal Section 8.0) All requested information in this RFP must be supplied. Respondents may take exception to certain requirements in this RFP or in the standard County Contract included as Attachment 3. Please note that the County Contract includes base legal terms and that the actual contract will be more specific and comprehensive to incorporate specific terms for this procurement. All exceptions shall be clearly identified in this section and a written explanation shall include the scope of the exceptions, the reasons for every exception, the ramifications of the exceptions for the County, and the description of the advantages or disadvantages to the County as a result of exceptions. The County, in its sole discretion, may reject any exceptions or specifications within the proposal. Respondents may also provide supplemental information, if necessary, to assist the County in analyzing responses to this

21

RFP. If respondents do not specifically state their exceptions to the County Contract (Attachment 3), County will assume respondent is willing and able to agree to the terms of the County Contracts, including attachments.

3.15. REQUIRED ATTACHMENTS

(Proposal Section 10.0) To establish a complete and competitive proposal, respondents must include the following attachments:

• Standard County Contract (Attachment 1)

• Equal Benefits Compliance Declaration Form (Attachment 2)

• Equal Benefits Ordinance (Attachment 3)

• Attachment H – HIPAA (Attachment 4)

• Attachment I - §504 Compliance Form (Attachment 5)

• Conversion / Migration References Form (Attachment 6)

• Cost Spreadsheet (Attachment 7)

• Staffing Matrix (Attachment 8)

• Conversion / Migration Requirements (Attachment 9)

SAN MATEO COUNTY

CALIFORNIA

4. Pilot and Full Conversion Detail

23

4.1. CURRENT MAINFRAME CONFIGURATION

For purposes of preparing proposals for both the pilot conversion / migration and the initial proposal for the full production system conversion / migration, the following mainframe system information should be used: Mainframe platform (retiring) IBM 7060-H50 Multiprise 3000 (110 MIPS)

IBM z890-2086 (88 MIPS) currently being installed Operating system z/OS 1.3 (z/OS 1.4 will run on the z890) Environments 3 – Test, QA and Production Communications IBM TCP/IP, SNA Security software CA Top Secret CJIS system internal security Program source code control IBM SCLM, CA Librarian r4.3, CA PANAPT r3.1 4GL Code generators CA Easytrieve-Plus r6.3 CA IDEAL r2.2 3GL Code generators IBM High Level Assembler 4.0 (5696-234) IBM COBOL for OS/390 & VM 2.1.0 (5648-A25) IBM REXX IBM TSO Clist IBM Language Environment (LE) Databases CA Datacom/DB r10 IBM DB2 r6 Database Tools CA DataDictionary r10 (Batch and On-Line) CA DataQuery r10 On-line Systems IBM CICS/TS 1.3 IBM ISPF v1.3 User interface development IBM CICS BMS MacKinney Systems MAPR II r4.7 Batch Job control IBM z/OS JCL IBM JES2 CA-7 CA-11 r3 Batch utilities IBM IDCAMS IBM FTP IBM IEBCOPY IBM IEBGENER IBM IEBUPDATE IBM IEFBR14 IBM IKJEFT01 IBM IKJEFT1B IBM MTPBATCH r5.2 CA SORT r7.1 CA CA7BTI CA DBUTLTY CA DRREPORT CA DQBATCH CA EZTPA00 CA IDBATCH Specialized modules1 CA SC00INIT IBM EZASOKET

24

IBM EZACIC04 IBM EZACIC05 SMC UTHSKP SMC UTPRTR SMC UTHUMI SMC UTLAST SMC UTFRST SMC UTROUT SMC UTSKED SMC PIDBATCH SMCPARM Testing / Debugging tools IBM CEDF IBM CEBR Compuware Abend-Aid CA-InterTest r5.4 CA-DBTS CA-DBUG Princeton Softech HourGlass 20001 Other 3rd-party software Landmark Systems Monitor for CICS Printer output management CA-Dispatch CA-DocView IBM IP/PrintWay (OS/390 2.5 PSF)

1

MPI Blue Server v7.001 CICS facilities in use BMS paging MRO (TOR, AOR [multiple], MUF [Datacom/DB]) Auto install terminals Pseudo conversational transactions only TS Queues Commarea Batch job spooling 3270 printing LU2 remote session Terminal models supported 3270 models 2,3,4,5 3270 Terminal emulators WRQ Reflection for IBM v10 thru 13 (primary) Attachmate Extra v8 (Jail medical staff) Web browsers MS Internet Explorer (primary)

Mozilla Firefox (alternative) External interfaces FTP (Will involve XML) California Dept. of Justice California AOC Numerous intra-county systems LU2 remote session (SNA) California Dept. of Motor Vehicles Alameda Warrant System Tape (cartridge) Social Security Administration Southwest Border Patrol Initiative CJIS CICS regions Test – Development/Maintenance (CITS5TA1)

QA - User Acceptance Testing (CITS5QA1)

Production (CITS5PA1)

CJIS CICS users 3470 and growing Average concurrent CJIS users ?? and growing

1 Refer to Appendix B for functionality

25

4.2. CJIS INTERNAL SECURITY

In addition to the mainframe system’s security provided by CA-TopSecret, CJIS has its own built-in security which is critical to the way CJIS works. This overview of CJIS internal security is provided to give vendors sufficient information to plan for potential workarounds in the conversion / migration of CJIS to another platform. Each County employee requiring access to CJIS is assigned a six (6) character user ID while police agency personnel who access CJIS are assigned eight (8) character user ID’s. To gain access to CJIS, users must first logon to the appropriate CICS region (Test, QA or Production). This logon process is controlled by CA-Top Secret. Once successfully logged on, the user types “CJIS” and presses enter to access CJIS, thus invoking the internal security process. The first step is to check if maintenance is being performed on the system. If so, a message is displayed telling the user that CJIS is not available for use. If the system is available, the sign-on program takes the user ID passed through CICS and looks for a matching user ID in the employee file. If a match is located, the process then checks to see if the user is still active. If the employee is active, the process checks to see if the terminal the user is logging on at is known to CJIS. If not, a message is displayed telling the user that the terminal is not known to CJIS. The user’s functional position assignment is checked next to see if they are permitted to logon at this particular terminal. If the terminal is associated with the user’s functional position, the process continues, otherwise a message is issued to inform the user they are not permitted to sign on at this terminal. Next, the process checks to see if the user is already signed on at another terminal. If they are, a message is issued to inform them they’re already signed on at terminal “xxxx” and the process ends. If the user is not already signed on, their sign-on is logged in the transaction log and an entry is made in a file of currently logged on users to show the user ID, date, time and terminal. Finally, the CJIS main menu of transactions authorized for the user’s functional position is displayed. This security scheme makes it possible to limit users in a particular functional position to a specific terminal should that restriction be desired. The County recognizes that a workaround for handling terminal ID’s will be necessary for any conversion / migration that implements use of a web browser for user displays due to the stateless nature of the browser environment. The association of printers to terminals for routing of CICS printer output also to be considered. CJIS allows assignment of one (1) default printer to terminals (optional) and association of any number of other printers to that same terminal.

4.3. CONVERSION / MIGRATION EXPECTATIONS

The County expects that each participating vendor will be able to perform the following conversion / migration functions and supply a target system with the capabilities specified:

26

Source Code � Convert Batch program/sub-routine COBOL source (with and without Datacom/DB

calls) using fully automated tool

� Convert CICS COBOL source (with and without Datacom/DB calls) using fully automated tool

� Convert COBOL copy members (including those having translated CICS commands) using fully automated tool

� Convert DataDictionary COPYDD database element members using fully automated tool

� Convert BMS map source (Assembler language) using fully automated tool

� Convert Assembler language program source using fully automated tool

� Convert Easytrieve program source using fully automated tool

� Convert IDEAL program source using fully automated tool

� Convert IDEAL panels using fully automated tool

� Convert IDEAL program source using fully automated tool

� Convert IDEAL data views using fully automated tool

� Convert calls to the Datacom/DB DBNTRY module to access the new Relational Data Base

� Convert VSAM and sequential file access to access the new Relational Data Base or other replacement file system

NOTE: NO MANUAL CONVERSION is to be performed except to modify program logic to look

for a negative bail amount and move ‘NO BAIL’ verbiage to screens or reports. Any others will be examined and noted case by case.

CICS BMS Map Source

� Convert CICS BMS map Assembler language source.

Datacom/DB Database

� Convert EBCDIC encoded Datacom/DB database tables to full relational, ASCII encoded, database

� “Cleanse” problem fields � Text in numeric fields (Change “NO BAIL” text to negative 10,000,000.00 value) � Others as required

VSAM and Sequential Files

� Convert VSAM files (EBCDIC to ASCII)

� Convert Sequential files (EBCDIC to ASCII), including tape datasets

� Convert GDG’s (EBCDIC to ASCII)

Batch Processing Environment

� Convert z/OS library members of the following types: � Jobs (JOBLIB) � Procedures (PROCLIB) � Parameters (PARMLIB) � Control records (CNTLLIB)

NOTE: MUST BE CAPABLE OF HANDLING EXECUTION PARAMETERS, I.E., PARM= AND CONDITIONAL JCL EXECUTION.

27

System Facilities � System Security capable of passing 8 character user id to transaction processor for CJIS

security enforcement

� Batch Job scheduling/re-run equivalent to CA-7/CA-11

Database Utilities

� CA-Data Query replacement

� CA-DataDictionary replacement External Interfaces

� Interface with Sheriff’s Message Switch system as provided by IBM Language Environment (LE) module EZASOKET

� FTP function � New State AOC Court system � Various intra-county systems

� Remote 3270 LU2 session

� Tape output � Social Security Administration

Application Development / Maintenance

� Program source code editor and compiler

� Display screen generator / compiler

� Source program compiler

� Change Management system

Transaction Processor

� Must support all CICS/TS functionality including spool to batch

� Must support multiple user environments (Test, QA and Production)

Batch Job Processing

� Must support execution parameters

� Must support conditional execution

� Must support job re-start at the step level

� Scheduler must support holiday roll forward/backward/no roll

� Must support multiple user environments (Test, QA and Production)

Printed Output

� Output (report) management equivalent to CA-Dispatch and CA-DocView

� Subpoenas must print in the same format they print when processed from the mainframe through the MPI Blue Server

� Pre-printed forms in use by user departments, particularly the Courts, must continue at print correctly

� Reports routed to data center printers must continue to print on the proper devices and in the proper orientation as specified by FORMDEF and PAGEDEF parameters in JCL

Miscellaneous Must be able to convert and migrate mainframe user PDS files to the new target “programmer” environment:

� Program source files

� JCL files

28

� Data files

4.4. PILOT CONVERSION / MIGRATION

Vendor proposals must include cost information for performing the conversion / migration of the pilot system. Each respondent selected to perform a pilot conversion will be given identical copies of the pilot system source code, JCL and data, which will be made available on the County’s web site with this RFP. An inventory of the pilot system will be found in Appendix A of this RFP.

4.4.1. Pilot Location

Prior to the pilot, vendors are free to perform their own “dry runs” in their own facilities. Vendors participating in the pilot conversion will perform their conversion / migration in County facilities in, or near, Redwood City, CA with CJIS Team members participation and monitoring.

All software used for the conversion process and any source code development / maintenance and change management software on the vendor’s system (excluding the operating system) must be installed at the County as part of the pilot conversion process. County CJIS staff will monitor and evaluate the vendor’s migration process from start to finish.

4.4.2. Conversion and Acceptance Testing

Following completion of the conversion / migration process, each vendor’s pilot system, including software used for the conversion process, as well as source code development / maintenance and change management software, will be fully tested by the CJIS user community test group and ISD’s CJIS Team which is responsible for maintaining the CJIS system.

Vendors should supply their own hardware platform, stripped to the operating system, for the pilot.

4.4.3. Full conversion / migration

At the time this RFP was prepared, a detailed inventory and metrics of the production CJIS system was not yet completed. During the period following release of the RFP and the beginning of the pilots, the County will complete the detailed inventory and metrics of the production CJIS system and will provide it to each vendor participating in the pilots. For this RFP, each responding vendor must submit a proposal for the full conversion / migration. Since a detailed inventory and metrics of the production CJIS system is not yet available, each respondent is to use the metrics presented below in this section. Those vendors participating in the pilots will subsequently revise their initial proposals for the full conversion / migration based on the detailed inventory and metrics of the production CJIS system. The final, revised proposals are to be submitted no later than 3 PM on February 22, 2007.

29

4.4.4. Inventory and Metrics for the Final Conversion / Migration Proposal

The following “ballpark” inventory and metrics are to be used for respondents’ initial proposals for the final production conversion / migration:

COBOL 2,400,000 statements CICS programs w/Datacom/DB 711 CICS programs w/o Datacom/DB 16 Batch programs w/Datacom 115 Batch programs w/o Datacom 34 Other programs/subroutines 15 Copy members 1116 COPYDD elements ? Assembler programs 24 IDEAL programs 40 BMS maps 479 Easytrieve programs 3 (in-line in JCL)

Job library members (JOBLIB) 230 Procedure library members (PROCLIB) 43 Control library members (CNTLLIB) 219 Parameter library members (PARMLIB) 44 Datacom/DB tables 599 Datacom/DB elements 2165 Datacom/DB fields 12300 VSAM KSDS files 3 Generational Datasets Undetermined Sequential files 30 Tape files 10 DataQuery queries 1739 DataDictionary program specifications Undetermined

SAN MATEO COUNTY

CALIFORNIA

5. Evaluation of Proposals

31

5.1. SELECTION OF PARTICIPANTS

Three groups of County employees will evaluate and select conversion / migration services proposals. The groups are as follows: Executive Steering Committee. The Executive Steering Committee will play the main "governance" role on the project and will make the final recommendation to the County. It will base the recommendation on the input of the Evaluation Team and its own assessment of conversion / migration demonstrations and other information. Evaluation Team. The Evaluation Team is responsible for the evaluation of the proposals and demonstrations and for conducting interviews during the optional site visits. The Evaluation Team is responsible for evaluating conversion / migration history, costs, and other selection criteria. The team's objective is to make recommendations for vendor selection to the Executive Steering Committee. End User Team. The End User Team consists of subject matter experts from County departments that have deep knowledge of specific business processes and in-depth knowledge in the use of CJIS as it relates to their departments. The End User Team's responsibility during selection is to support the Evaluation Team. Members of this team will be called as needed.

5.2. EVALUATION CRITERIA AND SELECTION PROCESS

The County will use a competitive process based upon "selection levels." For each decision point in the process, the County's Evaluation Committee will independently evaluate the proposals in accordance with specific decision factors and will elevate a certain number of respondents to compete against each other. The County recognizes that if a respondent fails to meet expectations during any part of the process, it reserves the right to proceed with the remaining respondents. The County reserves the right to determine the suitability of proposals on the basis of a proposal's ability to meet all requirements specified in this RFP, including general and detailed submittal requirements, the Evaluation Team's assessment of the proposal, and cost. The County will use the following factors to evaluate the proposals, among others:

• Conformance with RFP guidelines and submittal requirements

• Qualifications of Staff

• References

• Conversion / Migration Plan

• Responses to Conversion / Migration Requirements

• Compatibility with the County's desired terms and conditions

• Vendor Interviews

• Performance of the pilot conversion / migration

• Cost The County reserves the right to determine the suitability of proposals on the basis of some or all of these criteria.

32

5.3. APPEAL PROCESS

Unsuccessful respondents shall have five (5) calendar days from the date of the County's letter of rejection to submit a written appeal, addressed directly to CIO Chris Flatmoe, at 455 County Center, Third Floor, Redwood City, CA 94063, or by fax to (650) 363-7800. The written appeal should specifically address any irregularities in the process. The Evaluation Team will have the opportunity to review the written appeal, and to present the CIO with the reasons for the Team's recommendation. The decision of the CIO as to whether reconsideration of a vendor's proposal is warranted is final.

SAN MATEO COUNTY

CALIFORNIA

6. Deliverables

34

6.1. PILOT CONVERSION / MIGRATION

Vendors selected to participate in the pilot conversion process will be expected to deliver the following:

� Successful conversion / migration of the pilot system programs (with all business logic intact)

� Successful conversion / migration of the pilot system Datacom/DB database to a fully relational database

� Successful demonstration of the converted / migrated pilot system to show: � Each on-line application program functions correctly and all associated output is

without error � Each batch application program functions correctly and all associated output is

without error � Batch scheduling software functions in a manner consistent with the current

mainframe CA-7 / CA-11 systems � Batch JCL successfully executes with the same results as the corresponding

mainframe JCL � Printed output appears in the same format as the current mainframe CJIS system � Change management software for target system operates in a manner consistent

with the current mainframe PANAPT system and supports Test, QA and Production environments

6.2. CONVERSION / MIGRATION

One vendor will be selected from those vendors participating in the pilot conversion / migration to provide conversion and migration services for converting and migrating the CJIS application systems from the current mainframe platform onto an alternate platform leaving all current business logic intact. This conversion / migration is to include:

� All CJIS applications (both on-line and batch)

� Support for multiple environments (Production, Test and QA)

� All CJIS data files including Datacom/DB tables, VSAM, sequential, tape, and generational datasets for each environment (Test, QA and Production)

� Job scheduling and rerun facilities that include holiday roll forward/backward and step restart capabilities

� Support for batch job submission from on-line applications (spool to internal reader queue)

� Support for transmission of data to Department of Motor Vehicles (LU2), Department of Justice (FTP), Alameda Warrant System (LU2), State Administrator of the Courts (FTP) and various county systems (FTP)

� Support for electronic distribution of reports for viewing on-line (CA’s DocView)

� Support for archival of reports (similar to CA’s Dispatch)

� Support for modification and compilation of converted / migrated CJIS application programs and components (maps)

� Support for automated program migration from Test through Production status (similar to CA’s PANAPT)

� Assist County in developing system administration procedures for transitioning users to new system

� Provide training for CJIS technical staff on the use of the vendor’s software, technical tools etc.

35

6.3. PRESENTATIONS

1. Final presentation to technical and executive staff to debrief the pilot experience and outcome.

2. Presentation to CJIS committee on why the vendor should be selected to perform the final production conversion / migration.

SAN MATEO COUNTY

CALIFORNIA

Required Proposal Attachments

37

REQUIRED ATTACHMENTS The following attachments must be completed and submitted as part of a proposal:

Attachment 1: Equal Benefits Compliance Declaration Form Attachment 2: Equal Benefits Ordinance Attachment 6: Conversion / Migration Reference Form Attachment 7: Cost Spreadsheet Attachment 8: Staffing Matrix Attachment 9: Conversion / Migration Requirements Copies of documents per Section 3.11

ATTACHMENTS FOR REFERENCE PURPOSES The following attachments contain terms that will govern the content awarded as a result of this RFP. Unless exceptions are specifically noted per Section 3.14, every Respondent is agreeing to these terms by submitting a proposal

Attachment 3: Standard County Contract Attachment 4: Attachment H-HIPAA Business Associate requirements Attachment 5: Attachment I-§ 504 Compliance

38

SAN MATEO COUNTY

CALIFORNIA

Attachment 1 — Equal Benefits Compliance Declaration Form

39

COUNTY OF SAN MATEO

Equal Benefits Compliance Declaration Form I. Vendor Identification Name of Contractor:

Contact Person:

Address:

Phone Number:

Fax Number: II. Employees Does the Contractor have any employees? Yes No Does the Contractor provide benefits to spouses of employees? Yes No *If the answer to one or both of the above is no, please skip to Section IV.* III. Equal Benefits Compliance (Check one) Yes, the Contractor complies by offering equal benefits, as defined by Chapter 2.93, to its

employees with spouses and its employees with domestic partners.

Yes, the Contractor complies by offering a cash equivalent payment to eligible employees in lieu of equal benefits.

No, the Contractor does not comply.

The Contractor is under a collective bargaining agreement which began on and expires on .

IV. Declaration I declare under penalty of perjury under the laws of the State of California that the foregoing is true and correct, and that I am authorized to bind this entity contractually. Signature Name (Please Print)

Title Date

40

SAN MATEO COUNTY

CALIFORNIA

Attachment 2 — Equal Benefits Ordinance

41

ORDINANCE NO. 04026 An Ordinance Adding Chapter 2.93 to the San Mateo Ordinance Code to Provide for Non-Discrimination by County Contractors in the Provision of Employee Benefits WHEREAS, employee benefits routinely comprise a significant proportion of total employee compensation; and WHEREAS, discrimination in the provision of employee benefits between employees with domestic partners and employees with spouses results in unequal pay for equal work; and WHEREAS, County of San Mateo law prohibits discrimination based on marital status and/or sexual orientation; and WHEREAS, it is the County's intent, through the contracting practices outlined herein, to equalize the total compensation between similarly situated employees with spouses and employees with domestic partners; NOW THEREFORE, BE IT ORDAINED BY THE COUNTY OF SAN MATEO AS FOLLOWS: Section 1. There is hereby added to the Ordinance Code of the County of San Mateo a new Chapter 2. 93 to read as follows: Chapter 2. 93 County Contracts - Non-Discrimination in Benefits 2.93.010 Definitions. For the purposes of this chapter: (a) “Contract” means a legal agreement between the County and a contractor for public works, consulting, or other services, or for purchase of supplies, material or equipment for which the consideration is in excess of $5,000. (b) “Contractor” means a party who enters into a contract with the County. (c) “Contract Awarding Authority” means the Board of Supervisors or the individual authorized by the Board of Supervisors to enter into contracts on behalf of the County. (d) “Domestic partner” means any person who is registered as a domestic partner with the Secretary of State, State of California registry or the registry of the state in which the employee is a resident. (e) “Employee benefits” means the provision of any benefit other than pension and retirement benefits provided to spouses of employees or provided to an employee on account of the employee’s having a spouse, including but not limited to bereavement leave; disability, life, and other types of insurance; family medical leave; health benefits; membership or membership discounts; moving expenses; vacation; travel benefits; and any other benefits given to employees, provided that it does not include benefits to the extent that the application of the requirements of this chapter to such benefits may be preempted by federal or state law. (Ord. 4026, 02/13/01) 2.93.020 Discrimination in the provision of benefits prohibited. (a) No contractor on a County contract shall discriminate in the provision of employee benefits between an employee with a domestic partner and an employee with a spouse, subject to the following conditions: (1) In the event that the contractor’s actual cost of providing a particular benefit for the domestic partner of an employee exceeds that of providing it for the spouse of an employee, or the contractor’s actual cost of providing a particular benefit to the spouse of an employee exceeds that of providing it for the domestic partner of an employee, the contractor shall not

42

be deemed to discriminate in the provision of employee benefits if the contractor conditions providing such benefit upon the employee’s agreement to pay the excess costs. (2) The contractor shall not be deemed to discriminate in the provision of employee benefits if, despite taking reasonable measures to do so, the contractor is unable to extend a particular employee benefit to domestic partners, so long as the contractor provides the employee with a cash payment equal to the contractor’s cost of providing the benefit to an employee’s spouse. (b) The Board of Supervisors may waive the requirements of this chapter when it determines that it is in the best interests of the County. The County Manager may waive the requirements of this chapter for contracts not needing the approval of the Board of Supervisors where waiver would be in the best interests of the County for such reasons as follows: (1) Award of a contract or amendment is necessary to respond to an emergency; (2) The contractor is a sole source; (3) No complaint contractors are capable of providing goods or services that respond to the County’s requirements; (4) The requirements are inconsistent with a grant, subvention or agreement with a public agency; (5) The County is purchasing through a cooperative or joint purchasing agreement. (c) Contractors should submit requests for waivers of the terms of this chapter to the Contract Awarding Authority for that contract, or in the case of contracts approved by the Board, the County Manager. (d) The Contract Awarding Authority, or in the case of contracts approved by the Board, the County Manager, may reject an entity’s bid or proposals, or terminate a contract, if the Contract Awarding Authority determines that the entity was set up, or is being used, for the purpose of evading the intent of this chapter. (e) No Contract Awarding Authority shall execute a contract with a contractor unless such contractor has agreed that the contractor will not discriminate in the provision of employee benefits as provided for in this chapter. (Ord. 4026, 02/13/01) 2.93.030 Application of chapter. The requirements of this chapter shall only apply to those portions of a contractor’s operations that occur (a) within the County; (B) on real property outside of the County if the property is owned by the County or if the County has a right to occupy the property, and if the contractor’s presence at that location is connected to a contract with the County; and (c) elsewhere in the United States where work related to a County contract is being performed. The requirements of this chapter shall not apply to subcontracts or subcontractors of any contract or contractor. (Ord. 4026, 02/13/01) 2.93.040 Powers and duties of the County Manager. The County Manager’s office shall have the authority to: (a) Adopt rules and regulations, in accordance with this chapter and the Ordinance Code of the County of San Mateo, establishing standards and procedures for effectively carrying out this chapter; (b) Receive notification from employees of contractors regarding violations of this chapter; (c) Determine and recommend to the Board of Supervisors for final decision the imposition of appropriate sanctions for violation of this chapter by contractors including, but not limited to: (1) Disqualification of the contractor from bidding on or being awarded a County contract for a period of up to 5 years, and (2) Contractual remedies, including, but not limited to termination of contract, (3) Liquidated damages in the amount of $2,500; (d) Examine contractors’ benefit programs covered by this chapter;

43

(e) Impose other appropriate contractual and civil remedies and sanctions for violations of this chapter; (f) Allow for remedial action after a finding of noncompliance, as specified by rule; (g) Perform such other duties as may be required or which are necessary to implement the purposes of this chapter. (Ord. 4026, 02/13/01) 2.93.050 Date of application. The provisions of this chapter shall apply to any contract awarded or amended on or after July 01, 2001, provided that if the contractor is then signatory to a collective bargaining agreement, this chapter shall only apply to any contract with that contractor which is awarded or amended after the effective date of the next collective bargaining agreement. (Ord. 4026, 02/13/01)

44

SAN MATEO COUNTY

CALIFORNIA

Attachment 3 — Standard County Contract

45

AGREEMENT BETWEEN THE COUNTY OF SAN MATEO AND

[Contractor name]

THIS AGREEMENT, entered into this _____ day of _______________ , 20_____, by and between the COUNTY OF SAN MATEO, hereinafter called "County," and [Contractor name here], hereinafter called "Contractor";

W I T N E S S E T H:

WHEREAS, pursuant to Government Code Section 31000, County may contract with

independent contractors for the furnishing of such services to or for County or any Department thereof;

WHEREAS, it is necessary and desirable that Contractor be retained for the purpose of [Enter information here].

NOW, THEREFORE, IT IS HEREBY AGREED BY THE PARTIES HERETO AS FOLLOWS:

1. Exhibits. The following exhibits are attached hereto and incorporated by reference herein: Exhibit A—Services Exhibit B—Payments and rates Attachment H—HIPAA Business Associate requirements Attachment I—§ 504 Compliance RFP – Request for Proposal

2. Services to be performed by Contractor. In consideration of the payments set forth herein and in Exhibit “B,” Contractor shall perform services for County in accordance with the terms, conditions and specifications set forth herein and in Exhibit “A.” 3. Payments. In consideration of the services provided by Contractor in accordance with all terms, conditions and specifications set forth herein and in Exhibit "A," County shall make payment to Contractor based on the rates and in the manner specified in Exhibit "B." The County reserves the right to withhold payment if the County determines that the quantity or quality of the work performed is unacceptable. In no event shall the County’s total fiscal obligation under this Agreement exceed [Write out amount], [$Amount]. 4. Term and Termination.

46

Subject to compliance with all terms and conditions, the term of this Agreement shall be from [Month and day], 20[Last 2 digits of year] through [Month and day], 20[Last 2 digits of year]. This Agreement may be terminated by Contractor, the [Name of County Department Head] or his/her designee at any time without a requirement of good cause upon thirty (30) days’ written notice to the other party. In the event of termination, all finished or unfinished documents, data, studies, maps, photographs, reports, and materials (hereafter referred to as materials) prepared by Contractor under this Agreement shall become the property of the County and shall be promptly delivered to the County. Upon termination, the Contractor may make and retain a copy of such materials. Subject to availability of funding, Contractor shall be entitled to receive payment for work/services provided prior to termination of the Agreement. Such payment shall be that portion of the full payment which is determined by comparing the work/services completed to the work/services required by the Agreement. 5. Availability of Funds. The County may terminate this Agreement or a portion of the services referenced in the Attachments and Exhibits based upon unavailability of Federal, State, or County funds, by providing written notice to Contractor as soon as is reasonably possible after the county learns of said unavailability of outside funding.

6. Relationship of Parties. Contractor agrees and understands that the work/services performed under this Agreement are performed as an independent Contractor and not as an employee of the County and that Contractor acquires none of the rights, privileges, powers, or advantages of County employees. 7. Hold Harmless. Contractor shall indemnify and save harmless County, its officers, agents, employees, and servants from all claims, suits, or actions of every name, kind, and description, brought for, or on account of: (A) injuries to or death of any person, including Contractor, or (B) damage to any property of any kind whatsoever and to whomsoever belonging, (C) any sanctions, penalties, or claims of damages resulting from Contractor’s failure to comply with the requirements set forth in the Health Insurance Portability and Accountability Act of 1996 (HIPAA) and all Federal regulations promulgated thereunder, as amended, or (D) any other loss or cost, including but not limited to that caused by the concurrent active or passive negligence of County, its officers, agents, employees, or servants, resulting from the performance of any work required of Contractor or payments made pursuant to this Agreement, provided that this shall not apply to injuries or damage for which County has been found in a court of competent jurisdiction to be solely liable by reason of its own negligence or willful misconduct. The duty of Contractor to indemnify and save harmless as set forth herein, shall include the duty to defend as set forth in Section 2778 of the California Civil Code. 8. Assignability and Subcontracting. Contractor shall not assign this Agreement or any portion thereof to a third party or subcontract with a third party to provide services required by contractor under this Agreement without the prior written consent of County. Any such assignment or subcontract without the County’s prior written consent shall give County the right to automatically and immediately terminate this Agreement.

47

9. Insurance. The Contractor shall not commence work or be required to commence work under this Agreement unless and until all insurance required under this paragraph has been obtained and such insurance has been approved by Risk Management, and Contractor shall use diligence to obtain such issuance and to obtain such approval. The Contractor shall furnish the Department/Division with certificates of insurance evidencing the required coverage, and there shall be a specific contractual liability endorsement extending the Contractor's coverage to include the contractual liability assumed by the Contractor pursuant to this Agreement. These certificates shall specify or be endorsed to provide that thirty (30) days' notice must be given, in writing, to the Department/Division of any pending change in the limits of liability or of any cancellation or modification of the policy.

(1) Worker's Compensation and Employer's Liability Insurance. The Contractor shall have in effect during the entire life of this Agreement Workers' Compensation and Employer's Liability Insurance providing full statutory coverage. In signing this Agreement, the Contractor certifies, as required by Section 1861 of the California Labor Code, that it is aware of the provisions of Section 3700 of the California Labor Code which requires every employer to be insured against liability for Worker's Compensation or to undertake self-insurance in accordance with the provisions of the Code, and will comply with such provisions before commencing the performance of the work of this Agreement.

(2) Liability Insurance. The Contractor shall take out and maintain during the life of this

Agreement such Bodily Injury Liability and Property Damage Liability Insurance as shall protect him/her while performing work covered by this Agreement from any and all claims for damages for bodily injury, including accidental death, as well as any and all claims for property damage which may arise from contractors operations under this Agreement, whether such operations be by himself/herself or by any sub-contractor or by anyone directly or indirectly employed by either of them. Such insurance shall be combined single limit bodily injury and property damage for each occurrence and shall be not less than the amount specified below.

Such insurance shall include: (a) Comprehensive General Liability . . . . . . . . . . . . . . . . . . . $1,000,000 (b) Motor Vehicle Liability Insurance . . . . . . . . . . . . . . . . . . $1,000,000 (c) Professional Liability . . . . . . . . . . . . . . . . . . . . . . . . . . . . $1,000,000

County and its officers, agents, employees and servants shall be named as additional insured on any such policies of insurance, which shall also contain a provision that the insurance afforded thereby to the County, its officers, agents, employees and servants shall be primary insurance to the full limits of liability of the policy, and that if the County or its officers and employees have other insurance against the loss covered by such a policy, such other insurance shall be excess insurance only.

In the event of the breach of any provision of this section, or in the event any notice is received which indicates any required insurance coverage will be diminished or canceled, the County of San Mateo at its option, may, notwithstanding any other provision of this Agreement to the contrary, immediately declare a material breach of this Agreement and suspend all further work pursuant to this Agreement.

10. Compliance with laws; payment of Permits/Licenses.

48

All services to be performed by Contractor pursuant to this Agreement shall be performed in accordance with all applicable Federal, State, County, and municipal laws, ordinances and regulations, including, but not limited to, the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and the Federal Regulations promulgated thereunder, as amended, and will comply with the Business Associate requirements set forth in Attachment “H,” and the Americans with Disabilities Act of 1990, as amended, and Section 504 of the Rehabilitation Act of 1973, as amended and attached hereto and incorporated by reference herein as Attachment “I,” which prohibits discrimination on the basis of handicap in programs and activities receiving any Federal or County financial assistance. Such services shall also be performed in accordance with all applicable ordinances and regulations, including, but not limited to, appropriate licensure, certification regulations, provisions pertaining to confiden-tiality of records, and applicable quality assurance regulations. In the event of a conflict between the terms of this Agreement and State, Federal, County, or municipal law or regulations, the requirements of the applicable law will take precedence over the requirements set forth in this Agreement. Contractor will timely and accurately complete, sign, and submit all necessary documentation of compliance. 11. Non-Discrimination. A. Section 504 applies only to Contractors who are providing services to members of the

public. Contractor shall comply with § 504 of the Rehabilitation Act of 1973, which provides that no otherwise qualified handicapped individual shall, solely by reason of a disability, be excluded from the participation in, be denied the benefits of, or be subjected to discrimination in the performance of this Agreement.

B. General non-discrimination. No person shall, on the grounds of race, color, religion, ancestry, gender, age (over 40), national origin, medical condition (cancer), physical or mental disability, sexual orientation, pregnancy, childbirth or related medical condition, marital status, or political affiliation be denied any benefits or subject to discrimination under this Agreement.

C. Equal employment opportunity. Contractor shall ensure equal employment opportunity based on objective standards of recruitment, classification, selection, promotion, compensation, performance evaluation, and management relations for all employees under this Agreement. Contractor’s equal employment policies shall be made available to County of San Mateo upon request.

D. Violation of Non-discrimination provisions. Violation of the non-discrimination provisions of this Agreement shall be considered a breach of this Agreement and subject the Contractor to penalties, to be determined by the County Manager, including but not limited to

i) termination of this Agreement; ii) disqualification of the Contractor from bidding on or being awarded a County

contract for a period of up to 3 years; iii) liquidated damages of $2,500 per violation; iv) imposition of other appropriate contractual and civil remedies and sanctions, as

determined by the County Manager. To effectuate the provisions of this section, the County Manager shall have the authority to examine Contractor’s employment records with respect to compliance with this paragraph and/or to set off all or any portion of the amount described in this paragraph against amounts due to Contractor under the Contract or any other Contract between Contractor and County.

49

Contractor shall report to the County Manager the filing by any person in any court of any complaint of discrimination or the filing by any person of any and all charges with the Equal Employment Opportunity Commission, the Fair Employment and Housing Commission or any other entity charged with the investigation of allegations within 30 days of such filing, provided that within such 30 days such entity has not notified Contractor that such charges are dismissed or otherwise unfounded. Such notification shall include the name of the complainant, a copy of such complaint, and a description of the circumstance. Contractor shall provide County with a copy of their response to the Complaint when filed.

E. Compliance with Equal Benefits Ordinance. With respect to the provision of employee

benefits, Contractor shall comply with the County Ordinance which prohibits contractors from discriminating in the provision of employee benefits between an employee with a domestic partner and an employee with a spouse.

F. The Contractor shall comply fully with the non-discrimination requirements required by 41 CFR 60-741.5(a), which is incorporated herein as if fully set forth.

12. Retention of Records. Contractor shall maintain all required records for three (3) years after the County makes final payment and all other pending matters are closed, and shall be subject to the examination and/or audit of the County, a Federal grantor agency, and the State of California. 13. Merger Clause. This Agreement, including the Exhibits attached hereto and incorporated herein by reference, constitutes the sole Agreement of the parties hereto and correctly states the rights, duties, and obligations of each party as of this document's date. Any prior agreement, promises, negotiations, or representations between the parties not expressly stated in this document are not binding. All subsequent modifications shall be in writing and signed by the parties. 14. Controlling Law. The validity of this Agreement and of its terms or provisions, as well as the rights and duties of the parties hereunder, the interpretation, and performance of this Agreement shall be governed by the laws of the State of California. 15. Notices. Any notice, request, demand, or other communication required or permitted hereunder shall be deemed to be properly given when deposited in the United State mail, postage prepaid, or when deposited with a public telegraph company for transmittal, charges prepaid, addressed to:

In the case of County, to: In the case of Contractor, to:

IN WITNESS WHEREOF, the parties hereto, by their duly authorized representatives, have affixed their hands.

COUNTY OF SAN MATEO

By: President, Board of Supervisors, San Mateo County Date:

ATTEST:

50

By: Clerk of Said Board [Contractor Name Here] Contractor’s Signature Date:

Long Form Agreement/Business Associate

Exhibit “A” In consideration of the payments set forth in Exhibit “B”, Contractor shall provide the following services:

Exhibit “B”

In consideration of the services provided by Contractor in Exhibit “A”, County shall pay Contractor based on the following fee schedule:

51

SAN MATEO COUNTY

CALIFORNIA

Attachment 4 — HIPAA Business Associate Requirements

52

Attachment 4 Health Insurance Portability and Accountability Act (HIPAA)

Business Associate Requirements Definitions

Terms used, but not otherwise defined, in this Schedule shall have the same meaning

as those terms are defined in 45 Code of Federal Regulations section 160.103 and 164.501. (All regulatory references in this Schedule are to Title 45 of the Code of Federal Regulations unless otherwise specified.)

a. Designated Record Set. “Designated Record Set” shall have the same meaning as the

term “designated record set” in Section 164.501. b. Individual. “Individual” shall have the same meaning as the term “individual” in Section

164.501 and shall include a person who qualifies as a personal representative in accordance with Section 164.502(g).

c. Privacy Rule. “Privacy Rule” shall mean the Standards for Privacy of Individually Identifiable Health Information at 45 Code of Federal Regulations Part 160 and Part 164, Subparts A and E.

d. Protected Health Information. “Protected Health Information” shall have the same meaning as the term “protected health information” in Section 164.501 and is limited to the information created or received by Contractor from or on behalf of County.

e. Required By Law. “Required by law” shall have the same meaning as the term “required by law” in Section 164.501.

f. Secretary. “Secretary” shall mean the Secretary of the United States Department of Health and Human Services or his or her designee.

Obligations and Activities of Contractor a. Contractor agrees to not use or further disclose Protected Health Information other than as

permitted or required by the Agreement or as required by law. b. Contractor agrees to use appropriate safeguards to prevent the use or disclosure of the

Protected Health Information other than as provided for by this Agreement. c. Contractor agrees to mitigate, to the extent practicable, any harmful effect that is known to

Contractor of a use or disclosure of Protected Health Information by Contractor in violation of the requirements of this Agreement.

d. Contractor agrees to report to County any use or disclosure of the Protected Health Information not provided for by this Agreement.

e. Contractor agrees to ensure that any agent, including a subcontractor, to whom it provides Protected Health Information received from, or created or received by Contractor on behalf of County, agrees to the same restrictions and conditions that apply through this Agreement to Contractor with respect to such information.

f. If Contractor has protected health information in a designated record set, Contractor agrees to provide access, at the request of County, and in the time and manner designated by County, to Protected Health Information in a Designated Record Set, to County or, as directed by County, to an Individual in order to meet the requirements under Section 164.524.

g. If Contractor has protected health information in a designated record set, Contractor agrees to make any amendment(s) to Protected Health Information in a Designated Record Set that the County directs or agrees to make pursuant to Section 164.526 at the request of County or an Individual, and in the time and manner designed by County.

53

h. Contractor agrees to make internal practices, books, and records relating to the use and disclosure of Protected Health Information received from, or created or received by Contractor on behalf of, County available to the County, or at the request of the County to the Secretary, in a time and manner designated by the County or the Secretary, for purposes of the Secretary determining County’s compliance with the Privacy Rule.

i. Contractor agrees to document such disclosures of Protected Health Information and information related to such disclosures as would be required for County to respond to a request by an Individual for an accounting of disclosures of Protected Health Information in accordance with Section 164.528.

j. Contractor agrees to provide to County or an Individual in the time and manner designated by County, information collected in accordance with Section (i) of this Schedule, to permit County to respond to a request by an Individual for an accounting of disclosures of Protected Health Information in accordance with Section 164.528.

Permitted Uses and Disclosures by Contractor

Except as otherwise limited in this Schedule, Contractor may use or disclose Protected

Health Information to perform functions, activities, or services for, or on behalf of, County as specified in the Agreement; provided that such use or disclosure would not violate the Privacy Rule if done by County.

Obligations of County a. County shall provide Contractor with the notice of privacy practices that County produces

in accordance with Section 164.520, as well as any changes to such notice. b. County shall provide Contractor with any changes in, or revocation of, permission by

Individual to use or disclose Protected Health Information, if such changes affect Contractor’s permitted or required uses and disclosures.

c. County shall notify Contractor of any restriction to the use or disclosure of Protected Health Information that County has agreed to in accordance with Section 164.522.

Permissible Requests by County

County shall not request Contractor to use or disclose Protected Health Information in

any manner that would not be permissible under the Privacy Rule if done by County, unless the Contractor will use or disclose Protected Health Information for, and if the Agreement provides for, data aggregation or management and administrative activities of Contractor.

Duties Upon Termination of Agreement a. Upon termination of the Agreement, for any reason, Contractor shall return or destroy all

Protected Health Information received from County, or created or received by Contractor on behalf of County. This provision shall apply to Protected Health Information that is in the possession of subcontractors or agents of Contractor. Contractor shall retain no copies of the Protected Health Information.

b. In the event that Contractor determines that returning or destroying Protected Health Information is infeasible, Contractor shall provide to County notification of the conditions that make return or destruction infeasible. Upon mutual agreement of the Parties that return or destruction of Protected Health Information is infeasible, Contractor shall extend the protections of the Agreement to such Protected Health Information and limit further uses and disclosures of such Protected Health Information to those purposes that make the return or destruction infeasible, for so long as Contractor maintains such Protection Health Information.

Miscellaneous

54

a. Regulatory References. A reference in this Schedule to a section in the Privacy Rule

means the section as in effect or as amended, and for which compliance is required. b. Amendment. The Parties agree to take such action as is necessary to amend this

Schedule from time to time as is necessary for County to comply with the requirements of the Privacy Rule and the Health Insurance Portability and Accountability Act, Public Law 104-191.

c. Survival. The respective rights and obligations of Contractor under this Schedule shall survive the termination of the Agreement.

d. Interpretation. Any ambiguity in this Schedule shall be resolved in favor of a meaning that permits County to comply with the Privacy Rule.

55

SAN MATEO COUNTY

CALIFORNIA

Attachment 5 — § 504 Compliance

56

Attachment 5 Assurance of Compliance with Section 504 of the Rehabilitation Act of 1973, as Amended The undersigned (hereinafter called the "Contractor(s)") hereby agrees that it will comply with Section 504 of the Rehabilitation Act of 1973, as amended, all requirements imposed by the applicable DHHS regulation, and all guidelines and interpretations issued pursuant thereto. The Contractor(s) gives/give this assurance in consideration of for the purpose of obtaining contracts after the date of this assurance. The Contractor(s) recognizes/recognize and agrees/agree that contracts will be extended in reliance on the representations and agreements made in this assurance. This assurance is binding on the Contractor(s), its successors, transferees, and assignees, and the person or persons whose signatures appear below are authorized to sign this assurance on behalf of the Contractor(s). The Contractor(s): (Check a or b)

a. Employs fewer than 15 persons. b. Employs 15 or more persons and, pursuant to section 84.7 (a) of the regulation (45 C.F.R. 84.7 (a), has designated the following person(s) to coordinate its efforts to comply with the DHHS regulation.

_____________________________________________________ Name of 504 Person - Type or Print

_____________________________________________________ Name of Contractor(s) - Type or Print

_____________________________________________________ Street Address or P.O. Box

_____________________________________________________ City, State, Zip Code

I certify that the above information is complete and correct to the best of my knowledge. _____________________________________________________ Signature

_____________________________________________________ Title of Authorized Official

_____________________________________________________ Date

*Exception: DHHS regulations state that: "If a recipient with fewer than 15 employees finds that, after consultation with a disabled person seeking its services, there is no method of complying with (the facility accessibility regulations) other than making a significant alteration in its existing facilities, the recipient may, as an alternative, refer the handicapped person to other providers of those services that are accessible."

57

SAN MATEO COUNTY

CALIFORNIA

Attachment 6 — Conversion / Migration Reference Form

58

CONVERSION / MIGRATION REFERENCE FORM Please provide at least five (5) references that most closely reflect conversion / migration projects similar to San Mateo County's scope of work which have been completed within the past three (3) years. Please use the following format in submitting references. GENERAL BACKGROUND ...........................................................................................

Name of Client/Agency: Phone:

Address:

Project Manager: Title:

E-mail Address:

Conversion/Migration Dates:

Summary of Project:

Operating Budget: Number of Employees:

GENERAL BACKGROUND ...........................................................................................

Name of Client/Agency: Phone:

Address:

Project Manager: Title:

E-mail Address:

Conversion/Migration Dates:

Summary of Project:

Operating Budget: Number of Employees:

GENERAL BACKGROUND ...........................................................................................

Name of Client/Agency: Phone:

Address:

Project Manager: Title:

E-mail Address:

Conversion/Migration Dates:

Summary of Project:

Operating Budget: Number of Employees:

59

CONVERSION / MIGRATION REFERENCE FORM

GENERAL BACKGROUND ...........................................................................................

Name of Client/Agency: Phone:

Address:

Project Manager: Title:

E-mail Address:

Conversion/Migration Dates:

Summary of Project:

Operating Budget: Number of Employees:

GENERAL BACKGROUND ...........................................................................................

Name of Client/Agency: Phone:

Address:

Project Manager: Title:

E-mail Address:

Conversion/Migration Dates:

Summary of Project:

Operating Budget: Number of Employees:

60

SAN MATEO COUNTY

CALIFORNIA

Attachment 7 — Cost Spreadsheet

61

San Mateo County CJIS Migration CJIS Migration – Pilot Phase Summary of Professional Services and other Costs

First-Party Costs

Cost Categories Proposed Cost

in RFP Explanation/Notes (IF NECESSARY)

Professional Services Travel Other costs Total First-Party Costs

Third-Party Costs

Cost Categories Proposed Cost in RFP

Explanation/Notes (IF NECESSARY)

Professional Services Travel Other costs Total Third-Party Costs Total Project Costs

62

SAN MATEO COUNTY

CALIFORNIA

Attachment 8 — Staffing Matrix

63

Staffing Matrix Respondents are free to provide the project staffing matrices (pilot and final full conversion) in the format of their own choosing. Information included should be the team roster, assignment of duties etc. The matrix for the final full conversion may be revised at the time of final proposal revision following the pilot.

64

SAN MATEO COUNTY

CALIFORNIA

Attachment 9 — Conversion / Migration Experience Requirements

65

CONVERSION / MIGRATION EXPERIENCE REQUIREMENTS

1. Respondents to this RFP must provide a statement indicating how they meet the level of experience required in the following bullet items:

• Minimum of ten (10) years of IT experience • Minimum of five (5) years of IT project management experience • Minimum of five (5) years experience migrating applications / application systems

from mainframe platforms to non-mainframe platforms running operating systems such as Windows, Linux/UNIX, etc.

• Prior migration experience with government agencies would be considered a plus • Several years of mainframe experience (preferably with IBM mainframes running

z/OS or OS/390) • Programming knowledge:

o COBOL (additional knowledge in Assembler language is a plus) o CICS applications utilizing virtually every CICS facility o Additional experience with alternative languages such as Easytrieve,

IDEAL o Experience in redeployment of mainframe applications with web based

user interfaces • Minimum 5 years experience with, or proven knowledge of mainframe file systems

and databases including VSAM, Datacom/DB, PDS and CA Librarian source libraries

• Experience with conversion of non-relational databases to full SQL RDBMS such as DB/2 UDB, MS SQL Server, Oracle etc.

• Extensive knowledge of program source language and database conversion tools • Extensive knowledge in the area of alternative platforms

2. Respondents to this RFP must also include information regarding prior mainframe conversion / migration projects including:

• Platforms involved • Languages involved • Databases involved • Number of programs/modules/screen maps • Number of lines of source code • Number of database rows • Other file types converted / migrated • Duration of the project • Budget amount for the project • Outcome of the project

66

SAN MATEO COUNTY

CALIFORNIA

Appendix A — Pilot System Inventory

67

Pilot Conversion Inventory List Listed by Librarian Member Type and Module Name

Module Module description Nbr. of

Records Module

Type CICS

Tran id

ASSEMBLER LANGUAGE — 16 MODULES

ABENDI31 Abend Subroutine 16 ASM GREGJ31 Conv. Gregorian date to Julian 72 ASM JULDIF31 Find diff. Between two dates 82 ASM JULGR31 Conv. Julian date to Gregorian 77 ASM JULWEE31 Find Julian date day of week 54 ASM LJUST31 Left-Justify a Variable Len Field 65 ASM RJUST31 Right-Justify a Variable Len Field 77 ASM S5411431 CJIS Security - 31 bit version 165 ASM S54213 Maintain Transaction Id Number 190 ASM SMCEMPTY Determine If File Is Empty 36 ASM SMCJOBN Returns Job Name To Caller 117 ASM SMCPARM Write JCL Parm Field To Seq File 590 ASM SMCSBMT Submit Job To Internal Reader 141 ASM SBMT TBLSOR31 Table Sort Routine 191 ASM VALDA31 Edit Gregorian Date 216 ASM WEEKDA31 Find Day Of Week For Greg Date 79 ASM

BATCH COBOL WITH COPYDD — 16 MODULES

J16114 Create Warrant Issued Report 1364 CCB J16115 AWS - XMIT Rdy/Imm/Trn Warrants 2787 CCB J16116 Creates Reports For Message Sw 1351 CCB J16118 Creates Report for Message Switch 1276 CCB J16119 Reports for Prob. Msg. Switch 552 CCB J16122 Creates Reissue Report for AWS 2394 CCB J22313 DACM - Domestic Violence By Agency 1404 CCB J22351 DA Ad Hoc Stats By Type Charge 4808 CCB S53511 Spool/Purge Transaction Log Rec 1050 CCB S53512 Produce Current Day Transaction Log Statistics 1879 CCB S53517 Search On-Line Transaction Log 1131 CCB UTFRST Online Sched. - Parm Retrieval 1005 CCB UTHSKP Online Sched. - Database Purge 1162 CCB UTLAST Online Sched. - Upd8 Job Status 453 CCB UTPRTR Online Sched. - Print Online Report 524 CCB UTROUT Online Sched. - Report Router 1081 CCB UTSKED Online Sched. - CA7 Interface 611 CCB

CICS COMMAND LEVEL COBOL WITH COPYDD — 37 MODULES

J14151 Req. Display Booking Data 1469 CCC 3151 J14152 Display Person Booking Data 1665 CCC 3152 J14155 Display Booking Charges 1965 CCC 3155 J14158 Display Alias Names 911 CCC 3158 J21614 Maintain Gang Table 2038 CCC 9614 J2161A Maintain Rival Gangs 1382 CCC 961A J22131 DACM - Enter Complaint Search 2189 CCC A131

68

Module Module description Nbr. of

Records Module

Type CICS

Tran id

J22134 DACM - Search Complaint Request 4054 CCC A134 J22181 DACM - Display Complaint 5035 CCC A181 J22182 DACM - Display Complaint Charges 1744 CCC A182 J22223 DACM - Maintain/Display Case Notes 2543 CCC A223 J222A0 Dsply/Maint DA Edit Tbl Submenu 863 CCC A2A0 J222AE Dsply Police Agencies 1783 CCC A2AE J22334 DA Ad Hoc Stats Report Request 2777 CCC A334 J24141 Display Court Case Information 2704 CCC D141 J24142 Display General Court Case Info 8102 CCC D142 J24147 CJIS CMS Court Case History 3572 CCC D147 J2414D Derive Case Status 622 CCC J26232 CMS Dsply Calendar Codes 1226 CCC F232 J26233 CMS: Maintain Calendar Codes 1900 CCC F233 J26271 CMS:Display Court Table Menu 720 CCC F271 J26281 CMS:Display Court Table Maint 706 CCC F281 J5212H Maintain Offense Code Table 5240 CCC X12H J5213H Display Offense Code Table 2548 CCC X13H S52111 Common Input Data Edit Routine 3186 CCC S52311 Common Error Handler 679 CCC $311 S53222 Handle Application Printer Req 419 CCC S53519 Enter Transaction Log Search Criteria 1853 CCC $519

S54111 CJIS Signon and Security Validation 951 CCC V111 JUST

S54112 CJIS Sign-Off Program 280 CCC $112 S54211 Create Transaction Log Rec 379 CCC S54215 Obtain Starting Trans Log Record 251 CCC S54321 Format Transaction Data Dsply 549 CCC S54411 CJIS Main Menu Program 1630 CCC $411 S55111 Display Caller's Help Text 1973 CCC @111 S55112 AMS - Display Help Text 1021 CCC $112 UTSBMT Online Sched. Application Interface 968 CCC RSBT

CICS COMMAND LEVEL COBOL — 8 MODULES

S59994 Invoke IDEAL Program From CJIS 139 CIC $994 S59995 IDEAL TO CJIS AMS Interface 158 CIC $995 S59996 AMS/IDEAL Interface Commarea Create 165 CIC S59999 IDEAL/AMS Interface Commarea Create 112 CIC UTIJCL Online Sched. - IDEAL to UTOJCL 57 CIC UTISBT Online Sched. - IDEAL to UTSBMT 115 CIC UTOJCL Online Sched. - SMCSBMT/RDR Interface 414 CIC UTUSER Online Sched. - Get CICS Userid 51 CIC

TSO CLIST — 1 CLIST

UTXLDCBI Determine Report File Characteristics 52 CLI

BATCH COBOL — 11 MODULES

CALCAG31 Routine to Calculate Age Based on DOB 126 COB CNTRHD31 Centers Variable Heading in the Line 98 COB EDITAD31 AMS - Formats Two Line Address 245 COB EDITAR31 AMS - Formats One Line Address 215 COB

69

Module Module description Nbr. of

Records Module

Type CICS

Tran id

EDITNA31 Name Edit Routine 115 COB J14501 Inmate Release Date Change Rpt 355 COB J14505 Inmate Release Date Change Report 726 COB J16207 AWS - Get Assigned Service Agency 477 COB STRGTE31 Concatenate Data Strings into Area 258 COB UTHUMI Online Sched. – Determine Environment 100 COB UTXGTX31 Text Copy Utility 331 COB

CICS COBOL SUBROUTINES — 1 MODULE

J5242I31 Common Date/Time Subprogram 771 CSB

CONTROL LIBRARY (CNTLLIB) — 11 MEMBERS

CJDDB313 Parm for Domestic Violence Report 1 CTL CJSFTP3 CNTL - AWS Status Job CJSJFTP1 1 CTL CJSFTP4 CNTL - AWS Status Job CJSJFTP1 1 CTL CJSJ206D Define AWS Agency Jurisdiction File 17 CTL CJSJ505B Datacom reporter for job CJSJD505 61 CTL CJSJ505C CTL Sysin For Job CJSJD505 1 CTL UTXEROUT File Move Statements - Proc UTXROUT 5 CTL UTXUFRST Online Sched Parm Retrieval Status 2 CTL UTXULAST Online Sched Completion Status 2 CTL UTXUROUT Online Sched Router Status 2 CTL UTXUROUZ Online Sched Report Routing Completion 2 CTL

IDEAL PROGRAMS — 1 MODULE

J26920 Ad Hoc Rpt Muni Court Case Sources 587 IDL

COPY MEMBERS (INCLUDES) — 55 MEMBERS

CJSCABND Pgm Abend Message Ws Area 14 INC CJSCATRL Audit Trail Copymember 9 INC CJSCATTR CICS Field Attributes List 26 INC CJSCCHAR EDITCHAR Working Storage 34 INC CJSCCOMM Inter-Program Communication Area 605 INC CJSCD431 Procedure Code - Get Report Date 94 INC CJSCDBAS Database Function Codes 56 INC CJSCDS01 DACM FD-Parm-File Select Statement 6 INC CJSCDS02 DACM - FD-Parm-File FD Code 13 INC CJSCDS03 DACM - General Req Date Parms 15 INC CJSCDT31 Get Date/Time - CICS Asktime 8 INC CJSCEMSG Error Message Work Area 7 INC CJSCERRE Error Message Work Area 8 INC CJSCH331 Screen Header Copy Mem (CJSCHEA3) 20 INC CJSCHB31 Code for Screen Header -CJSCHEAB 22 INC CJSCHD31 Screen Header Copy Member 20 INC CJSCHIST History Date And Time Copy Mem 13 INC CJSCHS31 Screen Header Routine Copy Mem 20 INC CJSCHX31 Scrn Header Copy Mem (HEADFOOX) 22 INC CJSCIDEL CJIS/IDEAL Interface Storage 31 INC CJSCKY31 CICS Attn. Key Condition Names 38 INC

70

Module Module description Nbr. of

Records Module

Type CICS

Tran id

CJSCTIM3 Date/Time Work Areas 35 INC CJSCTIME Date & Time Copy Member 35 INC CJSCTRAN AWS Transmit Status Record 52 INC J16206R AWS Agency Jurisdiction Record 21 INC J16207V AWS Commarea-Assigned Service Agency 21 INC J22134V Search Complaint Requests Var Commarea 82 INC J22181V Complaint Dsply Variable Commarea 50 INC J22182V Dsply Comp Chrgs Variable Commarea 42 INC J22192V J22192 Variable Commarea 28 INC J22193V J22193 Variable Commarea 140 INC J22223V DACM - Maintain/Display Case Notes Var Comm 58 INC J24141V Display Court Case Program Link Area 76 INC J5242IV J5242IV Communication Area 91 INC UTXCSBMT Online Sched.- Request Commarea 27 INC UTXCTXT UTXCTXT Call Types Working Storage 60 INC

SYMBOLIC MAPS — 57 MEMBERS

J14151C Req. Dsply Bkng Data I/O Maps 90 INC J14151H Req. Dsply Bkng Data Help Map 45 INC J14152C Dsply Person Bkg Data Map I/O 388 INC J14152H Dsply Person Bkng Data Help Map 194 INC J14155C Display Bkng Chgs Map I/O Area 174 INC J14155H Display Bkng Chgs Help Map 87 INC J14158C Display Alias Names I/O Maps 104 INC J14158H Display Alias Names Help Map 52 INC J21614C Maint. Gang Table Map I/O Area 134 INC J21614H Maintain Gang Table Help Map 67 INC J2161AC Maintain Rival Gangs I/O Map 130 INC J2161AH Maintain Rival Gangs Help Map 69 INC J22131C DACM - Enter Complnt Map I/O Area 343 INC J22131H DACM - Enter Comp Help Map Area 175 INC J22134C Search Complaint Rqst Map I/O Area 161 INC J22134H Search Complaint Rqst Help Map Area 84 INC J22181C DACM - Display Complaint Map I/O Area 511 INC J22181H DACM - Display Complaint Help Map Area 259 INC J22182C DSPLY Comp Chrgs Map I/O Area 167 INC J22182H DSPLY Comp Chrgs Help Map Area 83 INC J22223C DACM - Maint/Dsply Case Notes Map I/O Area 230 INC J22223H DACM - Maint/Dsply Case Notes Help Map Area 115 INC J222A0C Dsply/Maint DA Table Map I/O Area 120 INC J222AEC Dsply Police Agencies I/O Map 134 INC J222AEH Dsply Police Agencies Help Map 67 INC J22334C Symbolic Map I/O Area 151 INC J22334H Symbolic Help Map Area 151 INC J24141C Dsply Court Case Map I/O Area 158 INC J24141H Dsply Court Case Help Map Area 79 INC J24142C Display General Court Case 556 INC J24142H Display General Court Case 278 INC J24147C Court Case Hist Map I/O Area 158 INC J24147H Court Case Hist Help Map Area 79 INC

71

Module Module description Nbr. of

Records Module

Type CICS

Tran id

J26232C Dsply Calendar Codes I/O Maps 128 INC J26232H Dsply Calendar Codes Help Map 64 INC J26233C Symbolic Map I/O Area 120 INC J26233H Symbolic Help Map Area 60 INC J26271C Symbolic Map I/O Area 79 INC J26271H Symbolic Help Map Area 39 INC J26281C Symbolic Map I/O Area 79 INC J26281H Symbolic Help Map Area 39 INC J5212HC Maintain Offense Code Table 222 INC J5212HH Maintain Offense Code Table 84 INC J5213HC Dsply Offense Code Tbl Map I/O Area 247 INC J5213HH Dsply Offense Code Tbl Help Map Area 123 INC S52311C Symbolic Map I/O Area 84 INC S52311H Symbolic Help Map Area 54 INC S53519C Enter Trans Log Search Criteria Map I/O Area 117 INC S53519H Enter Trans Log Search Criteria Help Map Area 117 INC S54111C Symbolic Map I/O Area 76 INC S54112C Symbolic Map I/O Area 76 INC S54411C CJIS Main Menu I/O Map Areas 53 INC S54411H CJIS Main Menu Help Map Area 51 INC S55111C Display Help Text I/O Map Area 612 INC S55111H Display Help Text - Help Map 306 INC S55112C Display Help Text I/O Map Area 292 INC S55112H Display Help Text - Help Map 146 INC

PROCEDURE LIBRARY (PROCLIB) — 4 MEMBERS

UTXPDONE Online Sched Termination Routine 70 JCL UTXPFRST Online Sched Parameter Retrieval 151 JCL UTXPLAST Online Sched Job Status Completion 39 JCL UTXPROUT Online Sched Report Router 200 JCL

JOB LIBRARY (JOBLIB) — 8 MEMBERS

CJDJA351 D.A. Ad Hoc Charge Report 57 JOB CJDJB313 D.A. Domestic Violence Report 26 JOB CJSJ5115 AWS Transmit Fresh Warrants 57 JOB CJSJ517A Transaction Log Search – Administrator 37 JOB CJSJC920 Ad Hoc Muni Court Case Sources 19 JOB CJSJD505 Xtract/Email Inmate Release Date Change 216 JOB CJSJFTP1 Retrieve AWS Warrant Status File 131 JOB CJSJTXLG Daily Transaction Log Archive / Purge 109 JOB

CICS BMS MAP SOURCE — 30 MEMBERS

J14151M Req. Dsply Bkng Data BMS Source 211 MAP J14152M Dsply Person Booking Data BMS Maps 348 MAP J14155M Display Bkng Charges BMS Mapset 267 MAP J14158M Dsply Alias Names BMS Map Source 163 MAP J21614M Maint. Gang Table BMS Map Source 334 MAP J2161AM Maint. Rival Gangs BMS Map Source 384 MAP J22131M Enter Complaint BMS Mapset 280 MAP

72

Module Module description Nbr. of

Records Module

Type CICS

Tran id

J22134M BMS Map Source Search Complaint 382 MAP J22181M Display Complaint BMS Map Source 396 MAP J22182M Dsply Complaint Charges BMS Map Source 312 MAP J22223M Maintain/Display Case Notes BMS Map Source 257 MAP J222A0M Dsply/Maint DA Table BMS Source 328 MAP J222AEM Dsply Police Agencies BMS Source 411 MAP J22334M Ad Hoc Sel. BMS Mapset Source 489 MAP J24141M Dsply Court Case BMS Map Source 210 MAP J24142M Display General Court Case BMS Map Source 455 MAP J24147M Court Case Hist BMS Map Source 273 MAP J26232M Dsply Calendar Codes BMS Map Source 355 MAP J26233M CICS BMS Map Source 417 MAP J26271M CICS BMS Map Source 122 MAP J26281M CICS BMS Map Source 100 MAP J5212HM CICS BMS Map Source 464 MAP J5213HM Dsply Offense Code Tbl BMS Map Source 397 MAP S52311M CICS BMS Map Source 97 MAP S53519M Enter Trans Log Search Criteria BMS Map Srce 356 MAP S54111M CICS BMS Map Source 84 MAP S54112M CICS BMS Map Source 88 MAP S54411M Main Menu BMS Map Source 324 MAP S55111M Dsply Help Text BMS Map Source 246 MAP S55112M Dsply Help Text BMS Map Source 208 MAP

PARAMETER LIBRARY (PARMLIB) — 1 MEMBER

CJSJ505E Job CJSJ505 E-mail Parm Input 8 PRM

DATAQUERIES — 5 MEMBERS Felony_Defts_Dism_Following_1st_Appear 17 Inmate_Count_By_Race_Code 5 CT-EVT-UPDT-CTL-Xrefed_to_Court-Event-Tp 16 Inmate_with_Booking 22 List_Resp_Org_Loc_Tbl 12

73

Programs Selected for the Pilot Conversion The following is a list, by function, of the modules selected for the pilot conversion / migration. Since some modules will appear multiple times, an unduplicated list of program components follows this list. All program source code is in COBOL unless otherwise noted. CJIS transaction codes and program function are provided. CICS transaction ID’s are shown for those programs requiring a transaction ID. Note that DataDictionary members for Datacom/DB data elements normally included in programs via COPYDD statements have been inserted into the program source members. In the full conversion process, the selected vendor will be expected to be able to extract all required COPYDD members for conversion. Online Inquiry

o Three main CJIS Screens/Programs � S54411 (MAINMENU); CJIS System Main Menu; (Trans ID ‘$411') � S54111 (SIGNON); CJIS System Sign-on; (Trans ID ‘V111’ and ‘JUST’)

� S54112 (SIGNOFF); CJIS System Sign-off; (Trans ID ‘$112') o Called programs

� S59994 - AMS to IDEAL Interface; (Trans ID ‘$994') � S59995 - Build Common Area for IDEAL to CJIS Menu Interface; (Trans ID ‘$995') � S59996 - CJIS Main Menu to IDEAL Interface � S59999 - IDEAL to CJIS Main Menu Interface � S54114 - Scramble password - Assembler module � S54213 - Generate CJIS transaction ID - Assembler module � S54215 - Obtain starting transaction log record ID � S54211 - Create transaction log record � S55111 - Display Help Text Data; (Trans ID ‘@111') � S55112 - Display Help Text; (Trans ID ‘$112') � S52311 - Common Error Processor; (Trans ID ‘$311') � JULGR31 - Convert Julian Date to Gregorian - Assembler module

o Copylib members � CJSCATRL - Audit trail copy member � CJSCTIME - Date and Time storage copy member � CJSCTIM3 - Date and Time work area copy member � CJSCHIST - History Date and Time copy member � CJSCATTR - 3270 Field attributes copy member � CJSCDBAS - Database function codes copy member � CJSCKY31 - 3270 Attn/PF keys copy member � CJSCCOMM - Standard communication area copy member � CJSCERRE - Error message copy member � CJSCHD31 - Screen header formatting code copy member � CJSCDT31 - Get date/time code copy member (translated CICS ASKTIME)

� CJSCH331 - Screen header formatting code copy member � CJSIDELL - IDEAL interface TS commarea copy member

o Symbolic Help Map Copy members � S54111H - System Sign-On � S54411H - System Main Menu � S54112H - System Sign-Off � S55111H - Help Information � S55112H - Display Help Text Keys � S52311H - Common Error Handler Display

o Symbolic I/O Map Copy members � S54111C - System Sign-On

74

� S54411C - System Main Menu � S54112C - System Sign-Off � S55111C - Help Information � S55112C - Display Help Text Keys � S52311C - Common Error Handler Display

o BMS Mapset Source - Assembler � S54111M - System Sign-On � S54411M - System Main Menu � S54112M - System Sign-Off � S55111M - Help Information � S55112M - Display Help Text Keys � S52311M - Common Error Handler Display

Online Table Inquiry

o CJIS Table Inquiry Screens/Programs � S54411 (MAINMENU); CJIS System Main Menu; (Trans ID ‘$411') � S54111 (SIGNON); CJIS System Sign-on; (Trans ID V111 and JUST) � S54112 (SIGNOFF); CJIS System Sign-off; (Trans ID ‘$112') � J222A0 (DADSPTBL); Maintain/Display DA Tables Submenu; (Trans ID ‘A2A0') � J26232 (CTDSPTBL); Display Calendar Codes; (Trans ID ‘F232') � J26271 (CTDSPTBL); Court Table Display Menu; (Trans ID ‘F271') � J5213H (DADSPTBL); Display Offense Code Table; (Trans ID ‘X13H') � J14151 (BKDSP); Request Display/Print Booking Data; (Trans ID ‘3151')

o Called programs � S59994 - AMS to IDEAL Interface; (Trans ID ‘$994') � S59995 - Build Common Area for IDEAL to Main Menu Interface; (Trans ID ‘$995') � S59996 - CJIS Main Menu to IDEAL Interface � S54213 - Generate CJIS transaction ID - Assembler module � S54211 - Create transaction log record � S55111 - Display Help Text Data; (Trans ID ‘@111') � S55112 - Display Help Text; (Trans ID ‘$112') � S52311 - Common Error Processor; (Trans ID ‘$311') � S54321 – Format Transaction Data Display (PF4 option) � J14158 - Display Aliases; (Trans ID ‘3158')

o Copylib members � CJSCATRL - Audit trail copy member � CJSCTIME - Date and Time storage copy member � CJSCTIM3 - Date and Time work area copy member � CJSCHIST - History Date and Time copy member � CJSCATTR - 3270 Field attributes copy member � CJSCDBAS - Database function codes copy member � CJSCKY31 - 3270 Attn/PF keys copy member � CJSCCOMM - Standard communication area copy member � CJSCERRE - Error message copy member � CJSCHD31 - Screen header formatting code copy member � CJSCDT31 - Get date/time code copy member (translated CICS ASKTIME) � CJSCH331 - Screen header formatting code copy member � CJSIDELL - IDEAL interface TS commarea copy member

o Symbolic Help Map Copy members � S54411H - System Main Menu � S54111H - System Sign-On � S54112H - System Sign-Off � S55111H - Help Information � S55112H - Display Help Text Keys

75

� S52311H - Common Error Handler Display � J14151H - Request Display Booking Data � J14158H - Display Aliases � J222A0H - Display DA Tables Submenu � J26232H - Display Calendar Codes � J26271H - Court Table Display Menu � J5213HH - Display Offense Code Table

o Symbolic I/O Map Copy members � S54411C - System Main Menu � S54111C - System Sign-On � S54112C - System Sign-Off � S55111C - Help Information � S55112C - Display Help Text Keys � S52311C - Common Error Handler Display � J14151C - Request Display Booking Data � J14158C - Display Aliases � J222A0C - Display DA Tables Submenu � J26232C - Display Calendar Codes � J26271C - Court Table Display Menu � J5213HC - Display Offense Code Table

o BMS Mapset Source - Assembler � S54411M - System Main Menu � S54111M - System Sign-On � S54112M - System Sign-Off � S55111M - Help Information � S55112M - Display Help Text Keys � S52311M - Common Error Handler Display � J14151M - Request Display Booking Data � J14158M - Display Aliases � J222A0M - Display DA Tables Submenu � J26232M - Display Calendar Codes � J26271M - Court Table Display Menu � J5213HM - Display Offense Code Table

Online Table Update

o CJIS Table Update Screens � S54411 (MAINMENU); CJIS System Main Menu; (Trans ID ‘$411') � S54111 (SIGNON); CJIS System Sign-on; (Trans ID V111 and JUST)

� S54112 (SIGNOFF); CJIS System Sign-off; (Trans ID ‘$112') � J222A0 (DAMNTTBL); Maintain/Display DA Tables Submenu; (Trans ID ‘A2A0')

� J26281 (CTMNTTBL); Court Table Maintenance Menu; (Trans ID ‘F281')

� J5212H (DAMNTTBL); Maintain Offense Code Table; (Trans ID ‘X12H')

� J222AE (DAMNTTBL); Maintain Originating Agencies; (Trans ID ‘A2AE')

� J26233 (CTMNTTBL); Maintain Calendar Codes; (Trans ID ‘F233')

� J21614 (IMMNTJGG); Maintain Gang Table; (Trans ID ‘9614')

� J2161A (IMMNTJGG); Maintain Rival Gangs; (Trans ID ‘961A')

o Called programs � S54211 - Create transaction log record � S55111 - Display Help Text Data � S55112 - Display Help Text � S52311 - Common Error Processor

o Copylib members � CJSCATRL - Audit trail copy member � CJSCTIME - Date and Time storage copy member

76

� CJSCTIM3 - Date and Time work area copy member � CJSCHIST - History Date and Time copy member � CJSCATTR - 3270 Field attributes copy member � CJSCDBAS - Database function codes copy member � CJSCKY31 - 3270 Attn/PF keys copy member � CJSCCOMM - Standard communication area copy member � CJSCERRE - Error message copy member � CJSCHD31 - Screen header formatting code copy member � CJSCDT31 - Get date/time code copy member (translated CICS ASKTIME) � CJSCH331 - Screen header formatting code copy member � CJSIDELL - IDEAL interface TS commarea copy member

o Symbolic Help Map Copy members � S54411H - System Main Menu � S54111H - System Sign-On � S54112H - System Sign-Off � S55111H - Help Information � S55112H - Display Help Text Keys � S52311H - Common Error Handler Display � J2161AH - Maintain Rival Gangs � J21614H - Maintain Gang Table � J222AEH - Maintain Originating Agencies � J222A0H - Maintain DA Tables Submenu � J26233H - Maintain Calendar Codes � J26281H - Court Table Maintenance Menu � J5212HH - Maintain Offense Code Table

o Symbolic I/O Map Copy members � S54411C - System Main Menu � S54111C - System Sign-On � S54112C - System Sign-Off � S55111C - Help Information � S55112C - Display Help Text Keys � S52311C - Common Error Handler Display � J2161AC - Maintain Rival Gangs � J21614C - Maintain Gang Table � J222AEC - Maintain Originating Agencies � J222A0C - Maintain DA Tables Submenu � J26233C - Maintain Calendar Codes � J26281C - Court Table Maintenance Menu � J5212HC - Maintain Offense Code Table

o BMS Mapset Source - Assembler � S54411M - System Main Menu � S55111M - Help Information � S54111M - System Sign-On � S54112M - System Sign-Off � S55112M - Display Help Text Keys � S52311M - Common Error Handler Display � J2161AM - Maintain Rival Gangs � J21614M - Maintain Gang Table � J222AEM - Maintain Originating Agencies � J222A0M - Maintain DA Tables Submenu � J26233M - Maintain Calendar Codes � J26281M - Court Table Maintenance Menu � J5212HM - Maintain Offense Code Table

77

Online Display Search Inquiry – BKDSP o CJIS Search Inquiry Screens/Programs

� S54411 (MAINMENU); CJIS System Main Menu; (Trans ID ‘$411') � S54111 (SIGNON); CJIS System Sign-on; (Trans ID V111 and JUST) � S54112 (SIGNOFF); CJIS System Sign-off; (Trans ID ‘$112') � J14151 (BKDSP); Request Display/Print Booking Data; (Trans ID ‘3151')

o Called programs � J14152 (BKDSP); Display Person Booking Data; (Trans ID ‘3152') � J14155 (BKDSP); Display Booking Charges; (Trans ID ‘3155’) � S59994 - AMS to IDEAL Interface; (Trans ID ‘$994') � S59995 - Build Common Area for IDEAL to Main Menu Interface; (Trans ID ‘$995') � S59996 - CJIS Main Menu to IDEAL Interface � S54213 - Generate CJIS transaction ID - Assembler module � S54211 - Create transaction log record � S55111 - Display Help Text Data; (Trans ID ‘@111') � S55112 - Display Help Text; (Trans ID ‘$112') � S52311 - Common Error Processor; (Trans ID ‘$311') � S54321 – Format Transaction Data Display (PF4 option) � J14158 - Display Aliases; (Trans ID ‘3158')

o Copylib members � CJSCATRL - Audit trail copy member � CJSCTIME - Date and Time storage copy member � CJSCTIM3 - Date and Time work area copy member � CJSCHIST - History Date and Time copy member � CJSCATTR - 3270 Field attributes copy member � CJSCDBAS - Database function codes copy member � CJSCKY31 - 3270 Attn/PF keys copy member � CJSCCOMM - Standard communication area copy member � CJSCERRE - Error message copy member � CJSCHD31 - Screen header formatting code copy member � CJSCDT31 - Get date/time code copy member (translated CICS ASKTIME) � CJSCH331 - Screen header formatting code copy member � CJSIDELL - IDEAL interface TS commarea copy member � EDITAR31 – Reformat Address

o Symbolic Help Map Copy members � S54411H - System Main Menu � J14151H - Request Display Booking Data � J14152H - Display Person Booking Data � J14155H - Display Booking Charges � J14158H - Display Aliases

o Symbolic I/O Map Copy members

� S54411C - System Main Menu � S54111C - System Sign-On � S54112C - System Sign-Off � S55111C - Help Information � S55112C - Display Help Text Keys � S52311C - Common Error Handler Display � J14151C - Request Display Booking Data � J14152C - Display Person Booking Data � J14155C - Display Booking Charges � J14158C - Display Aliases

o BMS Mapset Source - Assembler � S54411M - System Main Menu

78

� S54111M - System Sign-On � S54112M - System Sign-Off � S55111M - Help Information � S55112M - Display Help Text Keys � S52311M - Common Error Handler Display � J14151M - Request Display Booking Data � J14152M - Display Person Booking Data � J14155M - Display Booking Charges � J14158M - Display Aliases

Online Display Search Inquiry – CMPDSP

o CJIS Search Inquiry Screens/Programs � S54411 (MAINMENU); CJIS System Main Menu; (Trans ID ‘$411') � S54111 (SIGNON); CJIS System Sign-on; (Trans ID ‘V111’ and ‘JUST’) � S54112 (SIGNOFF); CJIS System Sign-off; (Trans ID ‘$112') � J22131 (CMPDSP); Enter Complaint Search Criteria; (Trans ID ‘A131’)

o Called programs � S59994 - AMS to IDEAL Interface; (Trans ID ‘$994') � S59995 - Build Common Area for IDEAL to Main Menu Interface; (Trans ID ‘$995') � S59996 - CJIS Main Menu to IDEAL Interface � S54213 - Generate CJIS transaction ID - Assembler module � S54211 - Create transaction log record � S55111 - Display Help Text Data; (Trans ID ‘@111') � S55112 - Display Help Text; (Trans ID ‘$112') � S52311 - Common Error Processor; (Trans ID ‘$311') � S54321 - Format Transaction Data Display (PF4 option) � J22134 - Display Complaint Search Candidates; (Trans ID ‘A134') � J22181 - Display Complaint/Citation; (Trans ID ‘A181’) � J22182 - Display Defendant Charges; (Trans ID ‘A182’) � J14158 - Display Aliases; (Trans ID ‘3158’) � J22223 - Display Case Notes � J24141- Display Court Case Information

• (J24141 and further called programs is contained in the CTDSP function described above. See CTDSP for further detail.)

o Copylib members � CJSCATRL - Audit trail copy member � CJSCTIME - Date and Time storage copy member � CJSCTIM3 - Date and Time work area copy member � CJSCHIST - History Date and Time copy member � CJSCATTR - 3270 Field attributes copy member � CJSCDBAS - Database function codes copy member � CJSCKY31 - 3270 Attn/PF keys copy member � CJSCCOMM - Standard communication area copy member � CJSCERRE - Error message copy member � CJSCHD31 - Screen header formatting code copy member � CJSCDT31 - Get date/time code copy member (translated CICS ASKTIME) � CJSCH331 - Screen header formatting code copy member � CJSIDELL - IDEAL interface TS commarea copy member � J5242I31 - Calculate Date � J5242IV - Calculate Date Variable Comm Area � J22181V - Display Complaint/Citation Variable Comm Area

79

� J22182V - Display Defendant Charges Variable Comm Area � J22223V - Display Case Notes Variable Comm area � CNTRHD31 - Centers Heading

o Symbolic Help Map Copy members � S54411H - System Main Menu � J22131H - Enter Complaint Search Criteria � J22134H - Display Complaint Search Candidates � J22181H - Display Complaint/Citation � J22182H - Display Defendant Charges � J22223H - Display Case Notes � J14158H - Display Aliases

o Symbolic I/O Map Copy members � S54411C - System Main Menu � S54111C - System Sign-On � S54112C - System Sign-Off � S55111C - Help Information � S55112C - Display Help Text Keys � S52311C - Common Error Handler Display � J22131C - Enter Complaint Search Criteria � J22134C - Display Complaint Search Candidates � J22181C - Display Complaint/Citation � J22182C - Display Defendant Charges � J22223C - Display Case Notes � J14158C - Display Aliases

o BMS Mapset Source - Assembler � S54411M - System Main Menu � S54111M - System Sign-On � S54112M - System Sign-Off � S55111M - Help Information � S55112M - Display Help Text Keys � S52311M - Common Error Handler Display � J22131M - Enter Complaint Search Criteria � J22134M - Display Complaint Search Candidates � J22181M - Display Complaint/Citation � J22182M - Display Defendant Charges � J22223M - Display Case Notes � J14158M - Display Aliases

80

Online Display Search Inquiry – CTDSP

o CJIS Table Inquiry Screens/Programs � S54411 (MAINMENU); CJIS System Main Menu; (Trans ID ‘$411') � S54111 (SIGNON); CJIS System Sign-on; (Trans ID ‘V111’ and ‘JUST’) � S54112 (SIGNOFF); CJIS System Sign-off; (Trans ID ‘$112') � J24141 (CTDSP); Display Court Case Information; (Trans ID ‘D141’)

o Called programs � S59994 - AMS to IDEAL Interface; (Trans ID ‘$994') � S59995 - Build Common Area for IDEAL to Main Menu Interface; (Trans ID ‘$995') � S59996 - CJIS Main Menu to IDEAL Interface � S54213 - Generate CJIS transaction ID - Assembler module � S54211 - Create transaction log record � S55111 - Display Help Text Data; (Trans ID ‘@111') � S55112 - Display Help Text; (Trans ID ‘$112') � S52311 - Common Error Processor; (Trans ID ‘$311') � S54321 – Format Transaction Data Display (PF4 option) � J24142 - Display General Court Information; (Trans ID ‘D142') � J2414D - Derive Case Status � J24147 - Display Court Case Events; (Trans ID ‘D147’)

o Copylib members � CJSCATRL - Audit trail copy member � CJSCTIME - Date and Time storage copy member � CJSCTIM3 - Date and Time work area copy member � CJSCHIST - History Date and Time copy member � CJSCATTR - 3270 Field attributes copy member � CJSCDBAS - Database function codes copy member � CJSCKY31 - 3270 Attn/PF keys copy member � CJSCCOMM - Standard communication area copy member � CJSCERRE - Error message copy member � CJSCHD31 - Screen header formatting code copy member � CJSCDT31 - Get date/time code copy member (translated CICS ASKTIME) � CJSCH331 - Screen header formatting code copy member � CJSIDELL - IDEAL interface TS commarea copy member � J24141V - Display Court Case Information Variable Comm Area � EDITAR31 - Reformat Address � STRGTE31 - String/Format Text

o Symbolic Help Map Copy members � S54411H - System Main Menu � J24141H - Display Court Case Information � J24142H - Display General Court Information � J24147H - Display Court Case Events

o Symbolic I/O Map Copy members � S54411C - System Main Menu � S54111C - System Sign-On � S54112C - System Sign-Off � S55111C - Help Information � S55112C - Display Help Text Keys � S52311C - Common Error Handler Display � J24141C - Display Court Case Information � J24142C - Display General Court Information � J24147C - Display Court Case Events

o BMS Mapset Source - Assembler

81

� S54411M - System Main Menu � S54111M - System Sign-On � S54112M - System Sign-Off � S55111M - Help Information � S55112M - Display Help Text Keys � S52311M - Common Error Handler Display � J24141M - Display Court Case Information � J24142M - Display General Court Information � J24147M - Display Court Case Events

J22334 (DAADHOC) – DA Ad Hoc Statistics Selection Criteria CICS TRANSID('A334')

� Batch Job � CJDJA351 - District Attorney Ad Hoc Charge Report

� Copylib Members � UTXPDONE - Online Scheduler Termination � UTXPFRST - Online Scheduler Parm Retrieval � UTXPLAST - Online Scheduler Update Job Status � UTXPROUT - Online Scheduler Report Router � UTXLDCBI - Determine DCB of Input File � J22334H � J22334C � J22334M

o Called Programs � S53222 - Provide PrinterID � J22351 - Statistics for AD HOC Request � J5242I31 - Common Date/Time � ABENDI31 - Assembler ABEND Subroutine � GREGJ31 - Convert Gregorian Date to Julian � JULWEE31 - Find Day of Week from Julian � LJUST31 - Left-Justify Variable Length Field � RJUST31 - Right-Justify Variable Length Field � SMCJOBN - Return a Job Name � SMCPARM - Write Contents of Parm Field � SMCSBMT - Submit JCL to Internal Reader; (TRANS ID ‘SBMT') � UTFRST - Online Scheduler/PARM Retrieval � UTHUMI - Determine Executing Environment � UTLAST - Online Scheduler/Update Job Status � UTOJCL - Online Scheduler/Build JCL � UTROUT - Online Scheduler/Report Router � UTSBMT - Online Scheduler Interface; (TRANS ID ‘RSBT') � UTXGTX31 - Shifting of Text � WEEKDA31 - Find Weekday for Gregorian Date � CJSCABND

82

Online Display Transaction Log Search – LOGSCAN

o CJIS Search Inquiry Screens/Programs � S54411 (MAINMENU); CJIS System Main Menu; (Trans ID ‘$411') � S54111 (SIGNON); CJIS System Sign-on; (Trans ID ‘V111’ and ‘JUST’) � S54112 (SIGNOFF); CJIS System Sign-off; (Trans ID ‘$112') � S53519 (LOGSCAN); CJIS Transaction Log Search; (Trans ID ‘$519’)

o Called programs � S59994 - AMS to IDEAL Interface; (Trans ID ‘$994') � S59995 - Build Common Area for IDEAL to Main Menu Interface; (Trans ID ‘$995') � S59996 - CJIS Main Menu to IDEAL Interface � S54213 - Generate CJIS transaction ID - Assembler module � S54211 - Create transaction log record � S55111 - Display Help Text Data; (Trans ID ‘@111') � S55112 - Display Help Text; (Trans ID ‘$112') � S52311 - Common Error Processor; (Trans ID ‘$311') � S54321 – Format Transaction Data Display (PF4 option)

o Copylib members � CJSCATRL - Audit trail copy member � CJSCTIME - Date and Time storage copy member � CJSCTIM3 - Date and Time work area copy member � CJSCHIST - History Date and Time copy member � CJSCATTR - 3270 Field attributes copy member � CJSCDBAS - Database function codes copy member � CJSCKY31 - 3270 Attn/PF keys copy member � CJSCCOMM - Standard communication area copy member � CJSCERRE - Error message copy member � CJSCHD31 - Screen header formatting code copy member � CJSCDT31 - Get date/time code copy member (translated CICS ASKTIME) � CJSCH331 - Screen header formatting code copy member � CJSIDELL - IDEAL interface TS commarea copy member

o Symbolic Help Map Copy members � S54411H - System Main Menu � S53519H - CJIS Transaction Log Search

o Symbolic I/O Map Copy members � S54411C - System Main Menu � S54111C - System Sign-On � S54112C - System Sign-Off � S55111C - Help Information � S55112C - Display Help Text Keys � S52311C - Common Error Handler Display � S53519C - CJIS Transaction Log Search

o BMS Mapset Source - Assembler � S54411M - System Main Menu � S54111M - System Sign-On � S54112M - System Sign-Off � S55111M - Help Information � S55112M - Display Help Text Keys � S52311M - Common Error Handler Display � S53519M - CJIS Transaction Log Search

83

Jobs Selected for the Pilot Conversion Sort/merge, E-Mail and File Backup to Tape Cartridge

Job CJSJD505 — Inmate Release Date Change Report

1. Extract today's inmate records & booking records 2. Merge both extracts into inmate release date records 3. Create daily inmate release date change report using

inmate release date records from today and prior dates 4. Merge today's inmate release date records onto accumulated

master file on tape. 5. Send inmate release date change report via mainframe

utility to GroupWise users listed in parameter CJSJ505E. Programs, Procedures, Includes

� IEFBR14 � DRREPORT � SORT � J14501 (Merge Bookings and Inmates onto Inmate Release Records) � J14505 (Daily Inmate Release Date Change Report) � PROC TSOBATCH

� IKJEFT1B, IKJEFT01 � INCLUDE IKJPROC (send e-mail via SMTP)

� IEBGENER Internal Cobol Sort with Report Output to Dispatch

Job CJDJB313 — Monthly District Attorney Domestic Violence Report by Agency 1. Report program uses COBOL internal sort 2. Report output to Dispatch

Programs, Procedures, Includes J22313: Provides statistics on domestic violence cases by agency CJDDB313: Parameter record of period begin & end dates

Transmit Bench Warrant to Alameda Warrant System

Job CJSJ5115 — TRANSMIT BENCH WARRANT DATA TO AWS Uses VSAM Agency Jurisdiction File, internal COBOL sorts

1. Connects Sheriff's Message Switch (VAX system) 2. Transmit fresh warrants via LU2 session 3. Transmit reissue warrants via LU2 session 4. AWS Acknowledgement Report to Dispatch 5. AWS Daily Issued Warrants Court Report to Dispatch 6. AWS Daily Issued Warrants Resp Org Report to Dispatch 7. AWS Daily Issued Warrants Probation Report to Dispatch

Programs, Procedures, Includes � J16115 – Connect to Message Switch and transmit fresh warrants � J16122 – Connect to Message Switch and transmit reissue warrants

Note: Both J16115 and J16122 call:

84

� J16207 to obtain Assigned Service Agency ID for the jurisdiction � LE module EZASOKET to initialize API with the Message Switch � LE Module EZACIC04 to convert EBCDIC TO ASCII (outbound

message) � LE Module EZACIC05 to convert ASCII to EBCDIC (inbound

message) � J16119 – AWS Acknowledgement Report � J16114 – Daily Issued Warrants Report for Court

� Parameter CJSDC514 � J16116 – Daily Issued Warrants Resp Org (Responsible Organization)

Report � Parameter CJSDC516

� J16118 – Daily Issued Warrants Probation Report � Parameter CJSDC518

FTP Alameda Warrant System Daily Status File to Mainframe

Job CJSJFTP1 — Daily FTP a Warrant Status from AWS 1. FTP a Warrant Status File from AWS load into Datacom/DB

table via DBUTLTY 2. Easytrieve (in-line in JCL) to create a control card renaming input FTP file

awstatus.dat to AWSTATUS_mm_dd_yy.txt where mm_dd_yy represents the current date

Programs, Procedures, Includes � IEBGENER � PROC TSOBATCH

� IKJEFT1B, IKJEFT01 � INCLUDE IKJPROC � Control member CJSFTP1

� SMCEMPTY – Routine to set return code determined by presence of incoming data. RC=0 if data exists, RC=8 if file is empty

� EZTPA00 – In-line Easytrieve code � PROC TSOBATCH

� CNTLLIB member CJSFTP2 as input to FTP to do rename in #2 above

� IKJEFT1B, IKJEFT01 � INCLUDE IKJPROC

� DBUTLTY Job CJSJC920 — AD HOC REPORT SHOWING SOURCES OF CASES FOR MUNI COURT

This job executes an IDEAL program in batch. Programs, Procedures, Includes

� PIDBATCH � J26920 – IDEAL program

85

Job CJSJTXLG — DAILY TRANSACTION LOG ARCHIVE / PURGE This job is normally scheduled to run each business day, and will do the following: Step 1) Spool CJIS transaction log records to one of two possible tape files and

purge transaction log records from the CJIS database. The tape file actually created by this step will depend on whether this is the first execution of this job of the month.

Step 2) Catalog a tape created by step 1 that contains the previous month's activity. Step 2 is executed if this is the first execution of the month.

Step 3) Catalog a tape created by step 1 that contains an accumulation of the previous month's activity. This step will always be executed except the first run of the month. For each run, either step 2 or step 3 will be executed --never both.

Step 4) Backup the monthly tape that was catalogued in step 2; this backup tape will be sent to off-site storage. Note that this step will only be executed if step 2 is executed.

Step 5) Generate transaction statistical report. To clarify the two possible processing modes of this job:

• The first time that this job is run in any calendar month, steps 1, 2, 4, and 5 are executed.

• At all other times, steps 1, 3, and 5 are executed. Programs, Procedures, Includes

� S53511 � S53512 � VALDA31 Date Validation � IEFBR14 � IEBGENER

Job CJSJ517A — ONLINE TRANSACTION LOG SCAN This job is used by the CJIS Data Administrator for transaction log searches.

Programs, Procedures, Includes

� S53517 � UTXPFRST � UTXPROUT � IEBGENER � UTXPLAST

Job CJDJA351 — DISTRICT ATTORNEY AND AD HOC CHARGE REPORT � J22351 � IEBGENER (IN PRIOR JOB) � UTXPFRST (IN PRIOR JOB) � UTXPLAST (IN PRIOR JOB)

Note: In addition to called modules listed above, many programs also have a call to ABENDI31, an Assembler subroutine, called to force an ABEND.

86

DataQuery Reporting

List Responsible Organization Location Table (S07)

FIND ALL RESP-ORG-LOC-S PRINT TITLE ‘S07 - RESP-ORG-LOC-S' RESP-ORG-LOC-CD 'ORG' NCIC-ORI-NUMBER 'ORI NUM' RESP-OGLC-WNTSV 'WNT-SRV' RESP-ORG-LOC-NM 'NAME' STR-NO 'STR#' STR-DIR ' ' STR-NAME 'STREET' STR-TYPE-CODE ' ' CITY PHONE-NO 'PHONE'

Inmate (K25) Race Count FIND ALL INMATE SET COUNT (10.0) = 1 SORT BY (RACE-CODE) PRINT TITLE 'INMATE COUNT BY RACE CODE' RACE-CODE (COUNT)

List Inmate w/Booking (K25+A86) FIND ALL INMATE WITH IP-ID-NO = 0000002319 RELATED BY BOOKING-NUMBER VIA BOOKING-NUMBER TO BOOKING PRINT TITLE 'PRODUCTION -- INMATE -- K25/122' TITLE2 'WITH BOOKING (A86) INFO FOR IP-ID# 2319' FROM INMATE IP-ID-NO 'IP-ID#' IP-NM-ID-NO 'IP-NM#' IN-CUST-IND 'I/C' DOB 'DOB' LAR-NUMBER 'SMCSO/ID' NAME-FIRST 'FIRST' NAME-MIDDLE 'MID' NAME-LAST 'LAST NAME' FROM BOOKING RESP-ORG-CD 'ORG' BOOKING-NUMBER 'BOOKING/NUMBER' BOOKING-SUFFIX 'SFX' DATE-BOOKING 'BOOKING/DATE' DT-BOOK-RLS-ACT 'RELEASE/DATE'

87

Find CT-EVT-UPDT-CTL (B35) cross-referenced to Court-Event-TP (B26)

FIND ALL CT-EVT-UPDT-CTL WITH CT-EVT-UPDT-CD = 'CWAR'

CT-EVT-PARM-NO = '02' CT-EVT-CONSTANT = 'OPN'

RELATED BY COURT-EVENT-CD VIA COURT-EVENT-CD TO COURT-EVENT-TP WITH ACTIVE-IND = 'A' SORT CT-EVT-UPDT-CTL CT-EVT-CONSTANT COURT-EVENT-CD PRINT CT-EVT-UPDT-CTL

TITLE 'COURT EVENT TYPE - PROD' FROM CT-EVT-UPDT-CTL

COURT-EVENT-CD 'EVENT/CODE' CT-EVT-CONSTANT 'WARRANT/STATUS'

FROM COURT-EVENT-TP ACTIVE-IND 'ACTIVE/INACTIVE' SC-EVENT-IND 'GENERAL/JUR'

Felony Defts. Dism Following 1st Appear

*/BRANCH-STAT-M06 (from PROD) /* FIND COURT-EVENT

WITH DT-COURT-EVENT > '19959999' AND (COURT-ID = 'NF' OR 'CF' OR 'SF') AND (COURT-EVENT-CD = 'CDDMD')

RELATED BY CRT-CASE-DEF-NO VIA HEARING-K TO FIRST HEARING WITH COURT-EVENT.DT-COURT-EVENT GT DATE-HEARING

SORT BY CRT-CASE-DEF-NO PRINT

TITLE 'Q#M06: FELONY DEFTS. DISMISSED FOLLOW 1ST APPR. IN 96' FROM COURT-EVENT CRT-CASE-DEF-NO 'CASE #' COURT-EVENT-CD 'DISM CD' DT-COURT-EVENT 'DSM DT' FROM HEARING HEARING-TYPE 'HRG TP' COURT-DEPT-NO 'DEPT'

88

Datacom/DB Tables 112 Tables: Area DB ID

A46 - HAIR-FACIAL S01 104 A48 - HAIR-STYLE S01 104 A60 - COMP-REQUEST A36 113 A61 – Comp-Req-Sub A36 113 A65 – Req-Def-Xref A36 113 A76 – Offense-Code A43 104 A77 - Offense Code Inactive A44 104 A78 – Arrest-Charges A49 108 A79 – Offense-CD-Abbr A46 104 A81 – LAR-ID A48 108 A86 - BOOKING A49 108 A98 – Complaint A55 113 AFI – AWS-FTP-Intfc AFI 112 AWS – Wnt-Serv-Event AWS 112 B07 – Complaint-Count A55 113 B08 – Complaint-Def A59 113 B10 – Comp-Def-Count A55 113 B14 – Comp-Def-Chg-En A55 113 B16 – Calendar-Type A80 114 B18 – Ct-Hearing-Type A80 114 B19 – Court-Session A80 114 B20 - COURT-HOLIDAY A80 114 B21 - CT-CS-DEF-APPR A75 117

B28 - CT-EVENT-DATA A74 116 B30 - COURT-CASE-DEF A78 118

B32DEF-CJIS-CASE A83 118 B33 - COURT-EVENT A74 116 B34 - CT-EVT-DATA-CTL A68 114

B40 - DEF-RC-SEAL-RSN A83 118 B41 – Court-Def-Count A85 118 B42 – Ct-Def-Chg-Enh A87 118 B43 - DA-CASE-NOTE-LN B43 113

B49DEF-ATTY-TYPE A83 118 B50PROSC-ATTY-APPT A83 118 B51DEF-ATTY-NAME A83 118

B53 - DEF-COUNT-DISPN A85 118 B55DEF-CUST-STATUS A83 118

B61 – Def-Warrant A83 118 B64 - WARNT-REASON-TP A76 114 B66PROBN-STATUS A83 118 B69BL-BND-BOND-TP A76 114 B70BAIL-STAT-TYPE A76 114 B71DEF-BAIL-AMOUNT A83 118 B74BAIL-BND-AMOUNT A83 118 B75HEARING A83 118 B78DEF-PRC-SUSP A83 118 B79DEF-REOPEN-RSN A83 118 B80UNDER-APPEAL A83 118 B87BAIL-BOND-STAT A83 118 C01 - JAIL-LIEU-FINE A86 118 C02 - DEF-CNT-SNT-SUS A86 118

89

C03 - DEF-RESTITUTION A84 118 C05 - DEF-COUNT-FINE A86 118 C06 - DEF-COMMIT-SENT A83 118 C07 - DEF-CNT-ADL-SNT A85 118 C08 - DEF-COUNT-SENT A86 118 C09 - HOUSED-AT A83 118 C23 - DEF-CNT-WKND-JL A86 118 C26 - CNT-DAYS-CUST A86 118 C32 - CNT-FINE-FEE A86 118 C35 - CT-CASE-ACTION A83 118 C36 - ATTY-CO-COUNSEL A83 118 C38 - DEF-SENTENCE A90 118 C39 - DEF-CNT-SENT A91 118 C43 - CASE-ACTION-TP A76 114 C55 - DEF-BAIL-FORF A83 118

CM1 – Stat-Group-Code A45 113 D79 – DA-Stat-Off-Grp A45 113 JRP – Job-Rqst-Parm JRP 086 JRQ – Job-Request JRQ 086 JRR – Job-Report JRR 086

K01 - BKNG-CUST-CHGS K01 108 K06 – Gang-Code-Tbl K06 121 K11 – Rival-Gang-Tbl K11 121 K25 – Inmate K25 122 LIN – Job-Report-Line LIN 021 M47 – MO-Agency-Code M07 104 M60 - Court A80 114

P12 - HAIR-TEXTURE-TY P01 302 P13 - HAIR-LENGTH-TY P01 302

P14 - COMPLEXION-TY P01 302 P29 - GEN-APPEAR-TY P01 302 P30 - HAND-USE-TY P01 302 P31 - DEMEANOR-TY P01 302 P32 - SPEECH-TY P01 302

S07 – Resp-Org-Loc-S S04 104 S09 - PGM-CONTROLS-S S69 104 S13 – Function-PRT-S S72 104 S15 – Employee-User-S S06 104 S16 – Employee-S S06 104 S17 – Fncl-Position-S S07 104 S18 – FPS-TERMINAL-S S08 104 S19 – FPS-ORG-LOC-C-S S19 104 S20 – FPS-TN-SECR-C-S S10 104 S21 – Tran-Code-S S11 104 S37 – Transaction-L-S S16 105 S53 – Help-Panel-TE-S S26 149 S54 – Help-Panel-FL-S S26 149 S55 – Help-PNL-TB-F-S S26 149 S68 – IP-Name-S S34 107 S69 – Term-Printer-S S37 104 S70 – Printer-S S08 104 S75 – Error-Log-S S42 104 S91 - Report Request S54 109 S94 – Help-TRAN-CHN-S S56 149

90

V01 – DA-Case-Stat-TP A45 113 V02 – DA-Case-Type A45 113

V05 - DA-CASE-ASSGN A55 113 V09 - PLEADING-TYPE A45 113 V16 – DA-Case-Unit-TP A45 113 V31 - COMPLAINT-XREF A55 113 V50 – Offense-Cd-Sum V50 104

91

SAN MATEO COUNTY

CALIFORNIA

Appendix B — Utility Program Functions

92

The information in this section is intended to provide information on the function of various utility programs utilized on the County’s mainframe system. Program names are prefixed with the supplier’s name. “SMC” indicates the utility is a County written module. Program Function

IBM EZASOKET An IBM Language Environment module used for communication with the Sheriff’s Message Switch (DEC VAX system) for transmitting warrants to the Alameda County Warrant System (AWS).

IBM EZACIC04 An IBM Language Environment module used for translating data from

EBCDIC to ASCII prior to transmission to AWS. IBM EZACIC05 An IBM Language Environment module used for translating data from

ASCII to EBCDIC upon receipt from AWS. Princeton Softech Date and time modification tool for Y2K used for testing date- HourGlass 2000 dependent situations in CJIS IBM IP/PrintWay Routes CJIS 3270 print output network printers (OS/390 2.5 PSF)

MPI Blue Server v7.00 Utility providing print overlays for formatting subpoenas prior to

routing print stream to the DA’s LaserJet printers SMCEMPTY Assembler 164 Statements Called subroutine that determines if a file contains data and sends

results back in return code. 0 = file has data, 8 = file is empty, 16 = no DD statement supplied

SMCPARM Assembler 590 Statements This program writes the contents of the JCL parameter field to a

sequential file as an 80-byte record. If parameter field length is less than 80 bytes record is padded to 80 bytes with blanks. If parameter field length is greater than 80 bytes record is truncated to 80 bytes. All alpha characters in parameter field are translated to upper case.

Condition codes: 0 - If parameter field length is non-zero and 'SYSUT2' DD

statement is present. 8 - If parameter field length is zero.

16 - If 'SYSUT2' DD statement is missing. PIDBATCH Production IDEAL procedure that executes program IDBATCH to run

IDEAL programs in the batch environment. SC00INIT A CA (Computer Associates) Datacom security module utilized in the

CICS environment. UTHSKP COBOL 990 Statements

This program purges records from the online scheduler database. Deletion is based on an input parameter. Each inactive job-request record with a ‘request date’ XXX days old or older will be deleted. The value of XXX is supplied via an input parameter ‘PURGDAYS’. Corresponding JCL follows: //PURGDAYS DD *

93

XXX

/*

UTPRTR COBOL 434 Statements

This program will execute as part of a job that is kicked off by the online scheduler. Its purpose is to read a job-report record in the online scheduler db as specified by an input parameter card. The associated line records for this report will then be read and copied into one of four possible output files. The output file will then be processed by a subsequent job step that will print the file to a network printer.

UTHUMI COBOL 99 Statements

This program sets a return-code to an input parameter that reflects the run environment being used (0 = Prod, 1 = Test, 2 = QA). This RC can then be tested by a subsequent job step that is run environment dependent.

UTLAST COBOL 403 Statements

This program runs as the last step of a job run by the online scheduler and sets the status indicator of the job-request record in the online scheduler db based on the success or failure of the job.

UTFRST COBOL 923 Statements

This program runs as the first step of a job run by the online scheduler and sets the status indicator of the job-request record in the online scheduler db to ‘running’.

UTROUT COBOL 941 Statements

This program will normally be executed as part of a production batch job that was initiated via the online scheduler. Its purpose is to accept a report file generated by an application program and either copy the report into the online scheduler DB, or, optionally, lay the groundwork that would allow the report to be routed to a network printer via a subsequent job step. Under normal circumstances executed via proc ‘UTXPROUT’.

UTSKED COBOL 560 Statements

This program will normally run as part of either production job ‘UTXJSKED’ or ‘UTXJSKDL’. Each of these jobs consists of 2 steps. The first step executes this program; the second step executes a proc that will interface with CA-7. The CA-7 step will read the external file created by this program in the first step and add each job name listed there to the production schedule.