LEADER REPLACEMENT SYSTEM
Request for Proposals
Attachment A – Statement of Work
Addendum Number Five
April 8, 2008
Department of Public Social Services
Los Angeles County
12860 Crossroads Parkway South
City of Industry, CA 91746-3411
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
NOTICE TO RFP PROPOSERS
THIS DOCUMENT DOES NOT STAND ALONE AND MUST BE READ
AND REVIEWED IN CONNECTION WITH ALL OTHER PARTS OF
THIS RFP.
LRS RFP - Attachment A (SOW) Page i April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
TABLE OF CONTENTS
1. INTRODUCTION AND OVERVIEW: ............................................................................................ 1
1.1PROJECT BACKGROUND: ............................................................................................................ 1
1.2PROJECT OBJECTIVES: ................................................................................................................ 2
1.3PROJECT SCOPE: ............................................................................................................................ 2
1.4PROJECT TIMEFRAME: ................................................................................................................ 4
1.5ORGANIZATION OF STATEMENT OF WORK: ........................................................................ 5
1.6CONSTRUCTION OF TERMS: ....................................................................................................... 5
2. GENERAL REQUIREMENTS:........................................................................................................ 6
2.1PROJECT ORGANIZATION AND GOVERNANCE: .................................................................. 7
2.1.1 COUNTY Resources. ............................................................................................................ 8
2.1.2 CONTRACTOR Resources. ................................................................................................ 9
2.2PLACE OF PERFORMANCE:....................................................................................................... 12
2.3COUNTY FURNISHED ITEMS: ................................................................................................... 12
2.4CONTRACTOR FURNISHED ITEMS: ....................................................................................... 13
2.5DELIVERABLE ACCEPTANCE CRITERIA (GENERAL): ..................................................... 13
3. SCOPE OF WORK: ......................................................................................................................... 15
3.1TASK 1: PROJECT ADMINISTRATION: .................................................................................. 15
3.1.1 Subtask 1.1: Project Initiation. ...........................................................................................16
3.1.1.1 Deliverable 1.1.1: Project Control Document (PCD). ................................................ 19
3.1.1.2 Deliverable 1.1.2: Project Office Physical Site Plan. .................................................. 20
3.1.1.3 Deliverable 1.1.3: Project Office Certification of Readiness. .................................... 21
3.1.1.4 Deliverable 1.1.4: Incoming Orientation Plans. ......................................................... 21
3.1.1.5 Deliverable 1.1.5: Project Initiation Completion Report............................................ 22
3.1.2 Subtask 1.2: Project Planning............................................................................................22
3.1.2.1 Deliverable 1.2.1: M&O Services Plan ........................................................................ 44
3.1.2.2 Deliverable 1.2.2: M&E Services Plan ........................................................................ 44
3.1.2.3 Deliverable 1.2.3: Conversion and Archiving Plans .................................................. 44
3.1.3 Subtask 1.3: Ongoing Project Administration .................................................................45
3.1.3.1 Deliverable 1.3: Ongoing Project Administration. ...................................................... 49
3.2TASK 2: DEVELOPMENT METHODOLOGY AND TECHNICAL PRACTICES: .............. 49
3.2.1 Subtask 2.1: Establish Integrated Development Environment (IDE). ...........................50
3.2.1.1 Deliverable 2.1: Integrated Development Environment Configuration
Control Document. ........................................................................................................ 52
3.2.2 Subtask 2.2: Orientation to Project System Development Methodology, Tools, and
Technical Practices. ............................................................................................................52
3.2.2.1 Deliverable 2.2: System Development Lifecycle Orientation and Materials. .......... 53
3.3TASK 3: REQUIREMENTS VERIFICATION AND ANALYSIS: ............................................ 54
3.3.1 Subtask 3.1: Planning for Requirements Verification. ....................................................54
3.3.1.1 Deliverable 3.1: Requirements Verification Schedule. .............................................. 54
LRS RFP - Attachment A (SOW) Page ii April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3.3.2 Subtask 3.2: Analyze and Verify the LRS Requirements. ...............................................54
3.3.2.1 Deliverable 3.2.1: System Requirements Document (SRD). ...................................... 56
3.3.2.2 Deliverable 3.2.2: Requirements Traceability Matrix and Report. .......................... 56
3.4TASK 4: GENERAL DESIGN: ...................................................................................................... 57
3.4.1.1 Deliverable 4: General Design Document: .................................................................. 58
3.5TASK 5: TECHNICAL INFRASTRUCTURE PLANNING AND DESIGN: ............................ 59
3.5.1 Subtask 5.1: Design Technical Infrastructure. .................................................................60
3.5.1.1 Deliverable 5.1: Technical Infrastructure Design Document. ................................... 62
3.5.2 Subtask 5.2: Facility Management Plan. ..........................................................................62
3.5.2.1 Deliverable 5.2: Facility Management Plan. ............................................................... 64
3.5.3 Subtask 5.3: Develop Information Systems Security Plan. .............................................65
3.5.3.1 Deliverable 5.3: Information Systems Security Plan. ................................................ 66
3.5.4 Subtask 5.4: Network Design Plan. ...................................................................................67
3.5.4.1 Deliverable 5.4: Network Design Plan......................................................................... 68
3.6TASK 6: FUNCTIONAL DESIGN: ............................................................................................... 69
3.6.1 Subtask 6.1: Develop the Functional Design. ...................................................................69
3.6.1.1 Deliverable 6.1: Functional Design Document (FDD). .............................................. 71
3.6.2 Subtask 6.2: Functional Design Presentation. ...................................................................71
3.6.2.1 Deliverable 6.2: Functional Design Presentation Report. .......................................... 72
3.7TASK 7: TECHNICAL INFRASTRUCTURE DEPLOYMENT: .............................................. 72
3.7.1 Subtask 7.1: Acquire and Configure Technical Infrastructure Assets. .........................73
3.7.1.1 Deliverable 7.1: Technical Infrastructure Asset Configuration Report................... 73
3.7.2 Subtask 7.2: Document Technical Infrastructure System Administration Procedures.
..............................................................................................................................................74
3.7.2.1 Deliverable 7.2: Technical Infrastructure System Administration
Procedures. ..................................................................................................................... 75
3.7.3 Subtask 7.3: Integrate and Demonstrate LRS Connectivity. ..........................................76
3.7.3.1 Deliverable 7.3: Technical Infrastructure Review and Acceptance
Document. ....................................................................................................................... 78
3.8TASK 8: BASELINE APPLICATION SOFTWARE AND CONVERSION AND
ARCHIVING TOOLS: ............................................................................................................. 79
3.8.1 Subtask 8.1: Prepare Baseline Application Software Development Plan. .....................80
3.8.1.1 Deliverable 8.1: Baseline Application Software Development Plan (SDP). ............. 80
3.8.2 Subtask 8.2: Baseline Application Software Development Reviews. ...............................82
3.8.2.1 Deliverable 8.2: Baseline Application Software Development Review
Report. ............................................................................................................................ 83
3.8.3 Subtask 8.3: Document LRS Application Software SDLC Standards. ..........................83
3.8.3.1 Deliverable 8.3: LRS Application Software SDLC Standards. ................................. 84
3.8.4 Subtask 8.4: Build Baseline Application Software Components/Modules and
Conversion and Archiving Software Programs/Tools. ....................................................84
3.8.4.1 Deliverable 8.4: Baseline Application Software Components/Modules and
Conversion and Archiving Software Programs/Tools. ............................................... 85
3.8.5 Subtask 8.5: Unit Testing. ..................................................................................................85
3.8.5.1 Deliverable 8.5.1: Unit Test Template. ........................................................................ 86
3.8.5.2 Deliverable 8.5.2: Unit Test Procedures and Results Report. ................................... 86
3.8.6 Subtask 8.6: Validation. .....................................................................................................86
LRS RFP - Attachment A (SOW) Page iii April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3.8.6.1 Deliverable 8.6: Unit Test and Validation Results Report. ....................................... 87
3.8.7 Subtask 8.7: Interface Development. ................................................................................87
3.8.7.1 Deliverable 8.7.1: Interface Control Documents (ICD). ............................................ 88
3.8.7.2 Deliverable 8.7.2: Interface Test Procedures and Results Report. ........................... 88
3.8.7.3 Deliverable 8.7.3: Interface Documentation. .............................................................. 89
3.9TASK 9: TESTING: ........................................................................................................................ 89
3.9.1 Subtask 9.1: Develop Master Test Plan. ...........................................................................90
3.9.1.1 Deliverable 9.1: Master Test Plan. ............................................................................... 91
3.9.2 Subtask 9.2: Integration and System Testing. ..................................................................91
3.9.2.1 Deliverable 9.2.1: Integration Test Plan. .................................................................... 94
3.9.2.2 Deliverable 9.2.2: Integration Test Procedures. .......................................................... 94
3.9.2.3 Deliverable 9.2.3: Integration Test Results Report. ................................................... 95
3.9.2.4 Deliverable 9.2.4: Integration Test Summary Report. .............................................. 95
3.9.2.5 Deliverable 9.2.5: System Test Plan. ............................................................................... 96
3.9.2.6 Deliverable 9.2.6: System Test Procedures. ................................................................... 96
3.9.2.7 Deliverable 9.2.7: System Test Results Report. ............................................................. 97
3.9.2.8 Deliverable 9.2.8: System Test Summary Report. ......................................................... 97
3.9.3 Subtask 9.3: User Acceptance Testing. .............................................................................97
3.9.3.1 Deliverable 9.3.1: Recommended User Acceptance Test Plan. ................................ 101
3.9.3.2 Deliverable 9.3.2: User Acceptance Test Procedures/Scenarios Inventory
Report. .......................................................................................................................... 101
3.9.3.3 Deliverable 9.3.3: User Acceptance Test Weekly Status Reports. .......................... 101
3.9.3.4 Deliverable 9.3.4: User Acceptance Test Certification of Successful
Completion. .................................................................................................................. 102
3.9.3.5 Deliverable 9.3.5: Regression Test Scripts. ............................................................... 103
3.10 TASK 10: IMPLEMENTATION PLANNING: .................................................................. 104
3.10.1 Subtask 10.1: Prepare Implementation Master Plan.....................................................104
3.10.1.1Deliverable 10.1: Implementation Master Plan. ......................................................... 106
3.10.2 Subtask 10.2: Update Conversion and Archiving Plans. ...............................................107
3.10.2.1 Deliverable 10.2: Updated Conversion and Archiving Plans. ................................. 109
3.10.3 Subtask 10.3: Prepare LRS Training Plans. ......................................................................109
3.10.3.1 Deliverable 10.3: LRS Training Plans. ....................................................................... 111
3.11TASK 11: IMPLEMENTATION PREPARATION: ................................................................. 112
3.11.1 Subtask 11.1: Prepare Documentation. ..........................................................................112
3.11.1.1 Deliverable 11.1: Documentation. ............................................................................. 113
3.11.2 Subtask 11.2: Prepare LRS Helpdesk Support and Application. .................................113
3.11.2.1 Deliverable 11.2: LRS Helpdesk Procedures. ........................................................... 114
3.11.3 Subtask 11.3: Prepare LRS Training Materials. ...........................................................115
3.11.3.1 Deliverable 11.3: LRS Training Materials. .............................................................. 116
3.11.4 Subtask 11.4: Implement LRS Training Records Database. ........................................117
3.11.4.1 Deliverable 11.4: LRS Training Records Database. ................................................ 117
3.11.5 Subtask 11.5: Prepare for Implementation and Operations. .......................................118
3.11.5.1 Deliverable 11.5: Certification of Operational Readiness. ...................................... 118
3.12 TASK 12: PILOT: .................................................................................................................. 118
3.12.1 Subtask 12.1 Prepare Pilot Plan. ......................................................................................119
3.12.1.1 Deliverable 12.1: Pilot Plan. ....................................................................................... 120
LRS RFP - Attachment A (SOW) Page iv April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3.12.2 Subtask 12.2: Conduct and Evaluate Pilot. ....................................................................121
3.12.2.1 Deliverable 12.2.1: Pilot Evaluation Report. ............................................................ 123
3.12.2.2 Deliverable 12.2.2: Pilot Post-Evaluation Report..................................................... 125
3.12.3 Subtask 12.3: Prepare for Countywide Implementation. ..............................................125
3.12.3.1 Deliverable 12.3: Certification of Countywide Implementation Readiness
Report and Plans Update. ........................................................................................... 126
3.13 TASK 13: COUNTYWIDE IMPLEMENTATION: ........................................................... 127
3.13.1 Subtask 13.1: Execute Conversion and Archiving Plans. ..............................................128
3.13.1.1 Deliverable 13.1.1: Conversion and Archiving Results Reports. ............................ 128
3.13.1.2 Deliverable 13.1.2: Conversion and Archiving Final Report. ................................. 129
3.13.2 Subtask 13.2: Conduct LRS Training. ............................................................................129
3.13.2.1 Deliverable 13.2: LRS Training Report. ................................................................... 130
3.13.3 Subtask 13.3: Verification of Local Office Site Readiness. ...........................................130
3.13.3.1 Deliverable 13.3: Certification of Local Office Site Readiness. .............................. 131
3.13.4 Subtask 13.4: Execution of Countywide Implementation. ............................................131
3.13.4.1 Deliverable 13.4: Local Office Site Implementation Interim Reports. ................... 132
3.13.5 Subtask 13.5: Completion of Countywide Implementation. .........................................133
3.13.5.1 Deliverable 13.5.1: Countywide Implementation Report. ....................................... 134
3.13.5.2 Deliverable 13.5.2: Certification of Countywide Implementation. ......................... 135
3.14 TASK 14: PHASE 2 (PERFORMANCE VERIFICATION PHASE): .............................. 136
3.14.1 Subtask 14.1: Continue Specialized Training. ...................................................................137
3.14.1.1Deliverable 14.1: Specialized Training Reports. ......................................................... 137
3.14.2 Subtask 14.2: Develop LRS Transition Plan. .................................................................137
3.14.2.1Deliverable 14.2: LRS Transition Plan. ....................................................................... 138
3.14.3 Subtask 14.3: Prepare Performance Verification Report and Certification. ..............139
3.14.3.1 Deliverable 14.3.1: Performance Verification Report .............................................. 139
3.14.3.2 Deliverable 14.3.2: Certification of Performance Verification. ................................ 140
3.15 TASK 15: PHASE 3 (OPERATIONAL PHASE): ............................................................... 141
3.15.1 Subtask 15.1: Ongoing Specialized Training. ....................................................................141
3.15.1.1 Deliverable 15.1.: Ongoing Specialized Training Reports. ....................................... 141
3.15.2 Subtask 15.2: Final Acceptance Report and Certification. ...........................................141
3.15.2.1 Deliverable 15.2.1: Final Acceptance Report ............................................................. 142
3.15.2.2 Deliverable 15.2.2: Final Acceptance Certification. ................................................ 143
3.15.3 Subtask 15.3: Outgoing Transition Support. ..................................................................144
3.15.3.1 Deliverable 15.3: Certification of Completion of Outgoing Transition
Support. ........................................................................................................................ 144
4. DELIVERABLE SUMMARY: ...................................................................................................... 145
4.1 PHASE 1 (DESIGN/DEVELOPMENT/IMPLEMENTATION PHASE) DELIVERABLES:145
4.2 PHASE 2 (PERFORMANCE VERIFICATION PHASE) DELIVERABLES: ........................ 151
4.3 PHASE 3 (OPERATIONAL PHASE) DELIVERABLES: ........................................................ 152
EXHIBIT A: DELIVERABLE EXPECTATION DOCUMENT (DED) .............................................. 153
1. TABLE OF CONTENTS: .............................................................................................................. 153
2. INTRODUCTION: ......................................................................................................................... 153
3. DELIVERABLE DESCRIPTION: ............................................................................................... 153
LRS RFP - Attachment A (SOW) Page v April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3.1 METHODOLOGY FOR CREATING THE DELIVERABLE: ....................................153
3.2 APPLICABLE STANDARDS: .........................................................................................154
3.3 DELIVERABLE REQUIREMENTS: .............................................................................154
3.4 DELIVERABLE FORMAT: ............................................................................................154
4. RECOMMENDED DELIVERABLE ACCEPTANCE CRITERIA: ......................................... 154
5. DELIVERABLE SCHEDULE: ..................................................................................................... 155
5.1 KEY DATES FOR DELIVERABLES: ...........................................................................155
5.2 SCHEDULE FOR DELIVERABLE UPDATES: ...........................................................156
6. STAFF RESOURCES REQUIRED:............................................................................................. 156
LRS RFP - Attachment A (SOW) Page vi April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
1 [NOTICE TO RFP PROPOSERS: A document substantially similar to this
2 Attachment A (Statement of Work) shall become Exhibit A (Statement of Work) of
3 any resultant Agreement.]
4 1. INTRODUCTION AND OVERVIEW:
5 This Attachment A (Statement of Work) (SOW) is part of the Los Angeles COUNTY
6 Department of Public Social Services (DPSS) LEADER Replacement System (LRS)
7 Request for Proposals (RFP).
8 This Section 1 describes the general scope of Work that CONTRACTOR shall perform
9 for the LRS Project. CONTRACTOR shall be responsible for the design, development,
10 implementation, management, and operation of the LRS, which shall utilize a service-
11 oriented architecture (SOA) solution that meets the requirements described in the
12 Agreement. CONTRACTOR shall perform, complete, and deliver all Work, however
13 denoted, as set forth in this SOW, or in any attached or referenced document, in full
14 compliance with the Agreement.
15 1.1 PROJECT BACKGROUND:
16 In May 1994, COUNTY released an RFP to solicit proposals from qualified proposers to
17 design, develop, pilot, implement, manage, operate, and maintain the existing LEADER
18 System as specified in the original RFP. Unisys Corporation (Unisys) was selected as the
19 Contractor for the LEADER System.
20 The LEADER Agreement with Unisys began in November 1995 and continues through
21 April 30, 2011, and may be extended at COUNTY‟s option through April 30, 2015. In
22 January 1996, Unisys entered into a subcontract with Deloitte Consulting (DC) to provide
23 the existing LEADER System application software design, development, training and
24 data conversion resources, and ongoing application software modifications and
25 enhancements. In September 1998, Unisys entered into a subcontract with Xerox to
26 provide document production and distribution services for the ongoing printing, mailing,
27 and distribution of documents generated by the existing LEADER System. In November
LRS RFP - Attachment A (SOW) Page 1 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
28 2003, Unisys ended its subcontract with DC and assumed responsibility for the ongoing
29 existing LEADER System application software modifications and enhancements.
30 1.2 PROJECT OBJECTIVES:
31 The general objectives of this project are twofold. The first objective is to replace DPSS
32 Systems and DCFS Systems with an LRS that meets the requirements of a Web-services,
33 SOA design, using the COUNTY-specified standards in the Agreement, and all functions
34 and requirements of the Agreement. The second objective is to manage, operate, and
35 support, including maintain, modify, and enhance, the LRS for the term of the
36 Agreement, including ensuring that LRS functionality continues to meet the requirements
37 of COUNTY and that LRS performance continues to meet the requirements established
38 by COUNTY.
39 1.3 PROJECT SCOPE:
40 The general scope of Work to be performed during the Initial Term is covered in three (3)
41 phases. Unless expressly stated otherwise, CONTRACTOR shall provide all goods and
42 services to successfully perform and complete all of the Work set forth in the Agreement.
43 The project scope includes:
44 1. Phase 1 (Design/Development/Implementation Phase): Phase 1
45 (Design/Development/Implementation Phase) includes all planning, design,
46 development, testing, training, conversion, archiving, implementation, and
47 acceptance work that are required to replace DPSS Systems and DCFS Systems
48 with a standards-based, Web-services, SOA design, conforming to the federal
49 Technical Reference Model (see www.whitehouse.gov/omb/egov/a-6-trm.html)
50 and meeting the requirements set forth in Attachment B (Statement of
51 Requirements). Phase 1 (Design/Development/Implementation Phase) also
52 includes Management and Operations Services (M&O Services).
53 2. Phase 2 (Performance Verification Phase): Phase 2 (Performance Verification
54 Phase) follows the successful completion of Phase 1
55 (Design/Development/Implementation Phase), as determined by COUNTY
LRS RFP - Attachment A (SOW) Page 2 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
56 Project Director. During Phase 2 (Performance Verification Phase),
57 CONTRACTOR and COUNTY will verify that LRS performance meets all the
58 requirements specified in the Agreement under full production load. All
59 Deficiencies identified by either CONTRACTOR or COUNTY during Phase 1
60 (Design/Development/Implementation Phase) and Phase 2 (Performance
61 Verification Phase) must be corrected, as determined by COUNTY‟s Project
62 Director, prior to Final Acceptance of the LRS by COUNTY. Phase 2
63 (Performance Verification Phase) also includes M&O Services and Application
64 Software Modifications and/or Enhancements Services (M&E Services).
65 3. Phase 3 (Operational Phase): Phase 3 (Operational Phase) includes the
66 following Work:
67 A. Continued M&O Services that include continued project management
68 and Project Office operations, hosting of the LRS, operation of the Central
69 Print Facility, and all support services.
70 B. Continued M&E Services that include continued provision of COUNTY-
71 requested modifications of the LRS Application Software (e.g., work
72 associated with developing functional improvements of the LRS) and
73 enhancements of the LRS Application Software (e.g., work associated
74 with development of new application functionality and major
75 enhancements of the LRS as a result of changes in COUNTY/program
76 requirements).
77 C. Outgoing Transition Support that provides for a smooth transition or
78 transfer of the LRS and LRS Data from CONTRACTOR‟s environment to
79 the new environment of COUNTY or COUNTY-selected vendor.
80 4. Extended Term: The Extended Term includes the following Work:
81 A. Continued M&O Services that include continued project management and
82 Project Office operations, hosting of the LRS, operation of the Central Print
83 Facility, and all support services.
LRS RFP - Attachment A (SOW) Page 3 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
84 B. Continued M&E Services that include continued provision of COUNTY-
85 requested modifications of the LRS Application Software (e.g., work
86 associated with developing functional improvements of the LRS) and
87 enhancements of the LRS Application Software (e.g., work associated with
88 development of new application functionality and major enhancements of
89 the LRS as a result of changes in COUNTY/program requirements).
90 C. Outgoing Transition Support that provides for a smooth transition or
91 transfer of the LRS and LRS Data from CONTRACTOR‟s environment to
92 the new environment of COUNTY or COUNTY-selected vendor.
93 COUNTY, in its sole discretion, may terminate the Work related to DCFS Systems and
94 DCFS Programs, at any time, pursuant to Paragraph 75 (Termination Related to DCFS
95 Systems and DCFS Programs) of Attachment C (Sample Agreement). Termination of
96 such Work shall be at no additional cost to COUNTY. CONTRACTOR shall ensure that
97 any such termination shall not adversely impact the project schedule, as determined by
98 COUNTY.
99 1.4 PROJECT TIMEFRAME:
100 The timeframes established by COUNTY are as follows:
101 1. Forty-eight (48) months inclusive of all Phase 1
102 (Design/Development/Implementation Phase) Work to include all planning,
103 design, development, testing, training, conversion, archiving, and implementation
104 of the LRS that meets COUNTY objectives and requirements. The duration of
105 Phase 1 (Design/Development/Implementation Phase) and the Initial Term of the
106 Agreement shall automatically be extended at no additional cost to COUNTY
107 until CONTRACTOR has provided and COUNTY has approved Deliverable
108 13.5.2 (Certification of Countywide Implementation).
109 2. Six (6) months inclusive of all Phase 2 (Performance Verification Phase) Work
110 prior to the commencement of Phase 3 (Operational Phase).
LRS RFP - Attachment A (SOW) Page 4 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
111 3. Seventy-eight (78) months inclusive of all Phase 3 (Operational Phase) Work to
112 include continued M&O Services and M&E Services. In no event shall the
113 duration of Phase 3 (Operational Phase) be less than seventy-eight (78) months,
114 and the Initial Term of the Agreement shall automatically be extended at no
115 additional cost to COUNTY in order for CONTRACTOR to provide such
116 seventy-eight (78) of Phase 3.
117 4. A maximum three (3) year Extended Term, as determined by DPSS Director.
118 1.5 ORGANIZATION OF STATEMENT OF WORK:
119 The document is organized as follows:
120 1. Introduction and Overview that includes the project background, objectives, and
121 scope as well as an overview of COUNTY desired timeframe for LRS design,
122 development, implementation, management, and operational support.
123 2. General Requirements that includes necessary background on the LRS project
124 organization, CONTRACTOR and COUNTY furnished items, place of
125 performance, and the specified methods for managing and delivering the goods
126 and services described in this SOW.
127 3. Scope of Work that includes the Work, and related requirements that
128 CONTRACTOR must perform for Phase 1 (Design/
129 Development/Implementation Phase), Phase 2 (Performance Verification Phase),
130 and Phase 3 (Operational Phase).
131 4. Deliverables Summary that includes an overview of the Deliverables for Phase 1
132 (Design/Development/Implementation Phase), Phase 2 (Performance Verification
133 Phase), and Phase 3 (Operational Phase).
134 5. Exhibit A (Deliverable Expectation Document (DED)) which includes the
135 template for the Deliverable Expectation Document (DED).
136 1.6 CONSTRUCTION OF TERMS:
137 In construing the terms of this SOW, the following rules shall apply:
LRS RFP - Attachment A (SOW) Page 5 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
138 1. Singular nouns, and phrases incorporating them (e.g., referring to objects,
139 persons, events, or otherwise), shall be construed to also include the plural except
140 where reference to a single item is implied or necessary pursuant to the context of
141 the word or phrase in question and except as otherwise expressly stated for
142 particular defined terms set forth in Subparagraph 1.4 (Definitions) of the Base
143 Agreement of Attachment C (Sample Agreement). Plural nouns, and phrases
144 incorporating them, shall be construed to also include the singular except where
145 reference to multiple items is implied or necessary pursuant to the context of the
146 word or phrase in question and except as otherwise expressly stated for particular
147 defined terms set forth in Subparagraph 1.4 (Definitions) of the Base Agreement
148 of Attachment C (Sample Agreement).
149 2. Any use of the masculine gender shall be construed to include the feminine, and
150 vice versa.
151 3. Examples provided by using words and phrases, such as “including,” “include,”
152 “includes,” or “e.g.,” shall not be construed as limiting the term clarified thereby.
153 For example, “including” shall be construed as “including, but not limited to.”
154 4. References in this SOW to federal, State, COUNTY and/or other governmental
155 laws, rules, regulations, ordinances, guidelines, directives, policies, and/or
156 procedures shall mean such laws, rules, regulations, ordinances, guidelines,
157 directives, policies, and/or procedures as amended from time-to-time.
158 5. Unless expressly stated otherwise, all approvals, consents, or determinations by or
159 on behalf of COUNTY under the Agreement, will be in writing, and may be given
160 or withheld in the sole discretion or judgment of the person or entity authorized to
161 provide or make such approval, consent, or determination.
162 2. GENERAL REQUIREMENTS:
163 This Section 2 provides certain background on the LRS project organization,
164 CONTRACTOR and COUNTY furnished items, place of performance, and the specified
165 methods for managing and delivering the goods and services described in the SOW.
LRS RFP - Attachment A (SOW) Page 6 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
166 2.1 PROJECT ORGANIZATION AND GOVERNANCE:
167 A high-level LRS project organization and roles structure is depicted in Figure 1.
168 CONTRACTOR staff, including Subcontractor staff, assigned to the Project Office
169 (CONTRACTOR Project Team) and COUNTY staff assigned to the Project Office
170 (COUNTY Project Team) are collectively referred to in the SOW as “Project Team”.
171 The Project Team will be responsible for the overall management, planning, integration,
172 implementation, operational oversight, support, and performance monitoring of the LRS
173 for the duration of the LRS Project. COUNTY‟s Internal Services Department (ISD) will
174 be responsible for all network and security management and monitoring activities
175 involving the use of the County Enterprise Network (LAnet/EN) for LRS development
176 and operations.
California State Project Sponsors
Office of Systems Integration (OSI)
California Department of Social Services (CDSS)
Department of Health Care Services (DHCS)
COUNTY Oversight and COUNTY COUNTY
Executive Steering Project Sponsor Project Sponsor
Committee DPSS Director DPSS Chief Deputy Director
Independent Validation & COUNTY
CONTRACTOR
Verification (IV&V) Project Executive
Project Executive
Consultant DPSS Assistant Director
Quality Assurance (QA) COUNTY CONTRACTOR
Consultant Project Director Project Director
Other
COUNTY
Resources
177 COUNTY Project Team CONTRACTOR Project Team
178 Figure 1: COUNTY LRS Governance Structure
179
180 COUNTY intends to utilize the services of various COUNTY departments and
181 contractors in the overall implementation and ongoing support of the LRS. COUNTY
182 will be responsible for the design, integration, deployment, and support of the local office
183 network infrastructure. COUNTY may utilize the services of Quality Assurance (QA)
184 and Independent Verification and Validation (IV&V) contractors to support the LRS
185 development and acceptance processes.
186 CONTRACTOR shall cooperate with COUNTY and any COUNTY designated
187 contractors or associates participating in the design, development, implementation,
LRS RFP - Attachment A (SOW) Page 7 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
188 management, and operation of LRS and any related COUNTY information systems or
189 networks, and in the provision of COUNTY-requested Application Software
190 Modifications and/or Enhancements. At the direction of COUNTY, CONTRACTOR
191 shall provide COUNTY and any designated QA and IV&V contractors with all
192 applicable information needed to verify and validate that COUNTY is receiving all
193 contracted services. Failure or refusal to coordinate and cooperate with COUNTY-
194 specified entities precludes effective performance of the LRS Project and may lead to a
195 default determination by COUNTY.
196 CONTRACTOR shall be responsible for establishing an organization to manage and
197 deliver the goods and services defined in this SOW. CONTRACTOR shall interact with
198 the LRS COUNTY project governance structure at all levels as shown in Figure 1. This
199 organization must remain in effect for the term of the Agreement.
200 2.1.1 COUNTY Resources.
201 COUNTY will provide the following:
202 1. COUNTY LRS Oversight and Executive Steering Committee will provide
203 leadership and support for the LRS Project to include monitor project
204 progress against the COUNTY-approved Project Work Plan timelines and
205 milestones, project costs, and project risk assessment. COUNTY LRS
206 Oversight and Executive Steering Committee will help identify and solicit
207 COUNTY resources, oversee periodic external project management
208 audits, approve any plans related for transition to production and monitor
209 that transition, and serve as the final escalation point for project issues.
210 2. COUNTY Project Executive has overall responsibility for COUNTY for
211 the LRS Project, including the authority to commit COUNTY resources in
212 addressing LRS Project needs and requirements. COUNTY Project
213 Executive will communicate with COUNTY and executive leadership and
214 stakeholders regarding program strategy, direction, and changes.
215 COUNTY Project Executive will provide direction to COUNTY Project
216 Director.
LRS RFP - Attachment A (SOW) Page 8 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
217 3. COUNTY Project Director has responsibility for COUNTY for overseeing
218 the project‟s day-to-day activities. COUNTY Project Director has the final
219 approval authority for all Deliverables and other Work. Specifically,
220 COUNTY Project Director will:
221 A. Monitor CONTRACTOR performance of the Agreement;
222 B. Coordinate activities between COUNTY staff on the COUNTY
223 Project Team and CONTRACTOR staff on the CONTRACTOR
224 Project Team on a regular basis;
225 C. Review all Deliverables and other Work; and
226 D. Provide direction and serve as liaison to CONTRACTOR in areas
227 relating to policy, information, and procedural requirements.
228 4. COUNTY staff on the COUNTY Project Team, as depicted in Figure 1, is
229 responsible for certain project activities, as determined by COUNTY
230 Project Director, including working with CONTRACTOR staff, providing
231 certain subject matter expertise and additional resources for workgroups,
232 requirements validation, testing, and review of Deliverables and other
233 Work.
234 2.1.2 CONTRACTOR Resources.
235 CONTRACTOR shall provide the following CONTRACTOR Key Staff, which
236 shall be part of CONTRACTOR‟s project management team:
237 1. CONTRACTOR Project Executive shall be a full-time employee of
238 CONTRACTOR responsible for CONTRACTOR‟s overall performance
239 of the Agreement and shall have the authority to commit resources of
240 CONTRACTOR to address all LRS Project needs and requirements.
241 [NOTICE TO RFP PROPOSERS: COUNTY anticipates that
242 CONTRACTOR Project Executive will be an individual at the level of
243 partner, corporate vice president, or equivalent.]
LRS RFP - Attachment A (SOW) Page 9 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
244 2. CONTRACTOR Project Director shall be a full-time employee of
245 CONTRACTOR and shall be assigned full-time to the LRS Project on-site
246 at the Project Office or other location(s) approved by COUNTY Project
247 Director. CONTRACTOR Project Director shall report directly to
248 CONTRACTOR Project Executive. CONTRACTOR Project Director
249 shall serve as the primary point-of-contact between COUNTY Project
250 Director and CONTRACTOR. CONTRACTOR Project Director is
251 responsible for the overall day-to-day management and coordination of the
252 project to ensure that all Deliverables and other requirements are
253 completed successfully and that all contract dates are met.
254 3. The System Architect shall be a full-time employee of CONTRACTOR
255 and shall be available at any time, as requested by COUNTY Project
256 Director, including on-site at the Project Office or other location(s)
257 approved by COUNTY Project Director. The System Architect shall lead
258 the LRS design effort, reporting to CONTRACTOR Project Director and
259 working with CONTRACTOR team leads and COUNTY to analyze and
260 resolve issues related to LRS design. The System Architect shall have
261 primary responsibility for optimizing the design of the LRS, proactively
262 addressing potential design challenges, and utilizing proven application
263 development tools.
264 4. The Technical Manager shall be a full-time employee of CONTRACTOR
265 and shall be assigned full-time to the LRS Project on-site at the Project
266 Office or other location(s) approved by COUNTY Project Director. The
267 Technical Manager shall lead the management of all technical design,
268 development, and implementation activities related to the LRS functional
269 design, monitor the development of the LRS based on the design
270 documentation, and serve as the technical liaison to COUNTY for
271 managing, analyzing and resolving operational issues and technical
272 concerns related to the LRS (e.g., system performance) during the term of
LRS RFP - Attachment A (SOW) Page 10 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
273 the Agreement. The Technical Manager shall oversee the procurement and
274 integration of all hardware and software components of the LRS.
275 5. The Functional Manager shall be a full-time employee of CONTRACTOR
276 and shall be assigned full-time to the LRS Project on-site at the Project
277 Office or other location(s) approved by COUNTY Project Director. The
278 Functional Manager shall oversee the process of LRS functional
279 requirements analysis, verification, and validation as it relates to LRS
280 rules and workflows. The Functional Manager shall work with the
281 Technical Manager to ensure that the technical design and implementation
282 of the LRS meets all functional requirements.
283 6. The Implementation Manager shall be a full-time employee of
284 CONTRACTOR and shall be assigned full-time to the LRS Project on-site
285 at the Project Office or other location(s) approved by COUNTY Project
286 Director, during Phase 1 (Design/Development/Implementation Phase).
287 The Implementation Manager shall manage LRS implementation
288 preparation, planning, and execution, including delivery of required
289 training. The chief responsibility of the Implementation Manager is to
290 ensure that all implementation Tasks of the LRS Project proceed
291 smoothly, creating minimal disruption to DPSS Systems and DCFS
292 Systems activities.
293 7. The Conversion and Archive Manager shall be a full-time employee of the
294 CONTRACTOR and shall be assigned full-time to the LRS Project on-site
295 at the Project Office or other location(s) approved by COUNTY Project
296 Director, during Phase 1 (Design/Development/Implementation Phase).
297 The Conversion and Archive Manager shall manage the automated
298 conversion of DPSS Systems data, DCFS Systems data, and other legacy
299 data to the LRS and the LRS Data archiving methodology.
300 8. The Project Controller shall be a full-time employee of CONTRACTOR
301 and shall be assigned full-time to the LRS Project on-site at the Project
LRS RFP - Attachment A (SOW) Page 11 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
302 Office or other location(s) approved by COUNTY Project Director. The
303 Project Controller shall provide fiscal management and contract
304 administration for the Agreement, supervise, control, and coordinate the
305 contractual obligations of the Contractor, plan the project schedule,
306 perform project planning, and track task progress, resource assignments,
307 and actual work (hours and cost) performed by individual resources.
308 2.2 PLACE OF PERFORMANCE:
309 All Work shall be performed at CONTRACTOR supplied locations (i.e., Primary Central
310 Site, Backup Central Site, Central Print Facility, Backup Central Print Facility, and
311 Project Office), except that the Gateway shall be located at two (2) COUNTY sites
312 approved by COUNTY Project Director. Work performed at COUNTY or non-COUNTY
313 sites must be approved in advance by COUNTY Project Director.
314 CONTRACTOR may request COUNTY Project Director approval to perform Work at
315 COUNTY-specified facilities during the term of the Agreement on such terms and condi-
316 tions as determined by COUNTY Project Director. Additionally, CONTRACTOR may
317 be requested by COUNTY Project Director to perform Work at COUNTY-specified fa-
318 cilities during the term of the Agreement, and CONTRACTOR shall perform such Work
319 at the COUNTY-specified facilities in accordance with COUNTY Project Director‟s re-
320 quest. In all cases, CONTRACTOR shall comply with all COUNTY requirements, in-
321 cluding physical security requirements, for each COUNTY-specified facility that is used
322 during the Agreement.
323 2.3 COUNTY FURNISHED ITEMS:
324 All COUNTY furnished items are provided by COUNTY only for the term of the
325 Agreement and solely for the performance of the Work required by the Agreement.
326 COUNTY will provide, or cause to be provided, at no cost to CONTRACTOR, the
327 following:
328 1. Technical support and maintenance for the LAnet/EN, including related network
329 hardware;
LRS RFP - Attachment A (SOW) Page 12 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
330 2. Technical support and operations for the Local Office Sites infrastructure at various
331 COUNTY locations, including the physical workstations, management of the
332 desktop environment, the Local Office Site servers, and the Local Office Site
333 network; and
334 3. Any information technology (IT) resources as determined necessary by COUNTY
335 Project Director.
336 2.4 CONTRACTOR FURNISHED ITEMS:
337 Unless expressly stated otherwise, CONTRACTOR shall provide all goods and services
338 to perform and complete all Work set forth in the Agreement.
339 2.5 DELIVERABLE ACCEPTANCE CRITERIA (GENERAL):
340 In Subtask 1.1 (Project Initiation), CONTRACTOR shall develop the Project Work Plan
341 as part of Deliverable 1.1.1 (Project Control Document (PCD)) that defines the schedule
342 of Deliverables, identifying any dependencies between Deliverables that require
343 COUNTY approval of one or more prior Deliverables. Once this schedule is approved by
344 COUNTY Project Director, Deliverables must be approved by COUNTY Project
345 Director according to this schedule prior to CONTRACTOR beginning work on any
346 subsequent Deliverables. If CONTRACTOR begins work on the next scheduled
347 Deliverable without receiving COUNTY Project Director approval, CONTRACTOR
348 does so at CONTRACTOR‟s sole risk, including COUNTY right to withhold payment
349 pursuant to Subparagraph 9.11 (COUNTY‟s Right to Withhold Payment) of the Base
350 Agreement of Attachment C (Sample Agreement).
351 In general, COUNTY requires a minimum of ten (10) working days to review each
352 Deliverable, with a corresponding ten (10) working day resolution period for
353 CONTRACTOR to correct any deficiencies regarding the Deliverable. However,
354 COUNTY realizes that some Deliverables may require a more extensive review and
355 resolution. CONTRACTOR shall identify such Deliverables and schedule Deliverable
356 review/resolution periods accordingly in its proposed Project Work Plan. COUNTY
LRS RFP - Attachment A (SOW) Page 13 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
357 reserves the right to increase the review period prior to its final approval of the proposed
358 Project Work Plan.
359 Prior to the initiation of any work on any Deliverable, CONTRACTOR shall provide
360 COUNTY five (5) copies of a Deliverable Expectation Document (DED), developed in
361 accordance with Exhibit A (Deliverable Expectation Document (DED)) of this
362 Attachment A (Statement of Work), no later than thirty (30) days before the scheduled
363 start of any related Task or Subtask, with the exception of Deliverables due within the
364 first ninety (90) days after the Effective Date. Each DED submitted to COUNTY for its
365 approval shall describe the contents of the Deliverable, including a table of contents,
366 overview, objectives, scope, methodology, applicable standards, Deliverable
367 requirements, format, proposed acceptance criteria, key dates, and staff resources
368 required. The DED shall indicate whether a presentation will be part of the Deliverable
369 review process. Prior to any Deliverable development, CONTRACTOR shall obtain
370 COUNTY approval of the applicable DED. No Deliverable shall be accepted by
371 COUNTY for review without an approved DED.
372 CONTRACTOR shall submit each Deliverable to COUNTY in one (1) or more hard
373 cover 8 ½ by 11 inch three-ring binders, single sided sheets, 12 point Arial font, with
374 separated and partitioned sections as required. CONTRACTOR shall submit one (1)
375 original and twelve (12) copies of each Deliverable and provide an electronic copy in the
376 Microsoft Office Suite version specified by COUNTY.
377 COUNTY‟s right to approve all Deliverables and other Work, as set forth in
378 Subparagraph 4.2 (COUNTY Approval of Work) of the Base Agreement of Attachment
379 C (Sample Agreement), shall not be limited in any way by the contents of any DED
380 approved by COUNTY.
381
LRS RFP - Attachment A (SOW) Page 14 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
382 3. SCOPE OF WORK:
383 This Section 3 describes the primary Work that the CONTRACTOR shall perform, which
384 includes:
385 1. Task 1 - Project Administration
386 2. Task 2 - Development Methodology and Technical Practices
387 3. Task 3 - Requirements Verification and Analysis
388 4. Task 4 - General Design
389 5. Task 5 - Technical Infrastructure Planning and Design.
390 6. Task 6 - Functional Design
391 7. Task 7 - Technical Infrastructure Deployment
392 8. Task 8 – Baseline Application Software and Conversion and Archiving Tools
393 9. Task 9 - Testing
394 10. Task 10 - Implementation Planning
395 11. Task 11 - Implementation Preparation
396 12. Task 12 - Pilot
397 13. Task 13 - Countywide Implementation
398 14. Task 14 - Phase 2 (Performance Verification Phase)
399 15. Task 15 - Phase 3 (Operational Phase)
400 To accomplish the Work, CONTRACTOR shall work collaboratively with key
401 stakeholders, including Users, and State and federal governments and other external
402 agencies whose systems will interface with the LRS.
403 3.1 TASK 1: PROJECT ADMINISTRATION:
404 CONTRACTOR shall provide full project management, planning, monitoring,
405 supervision, tracking, and control for all project activities during the term of the
406 Agreement. CONTRACTOR shall employ project management standards and practices
407 (e.g., Project Management Institute‟s (PMI) Project Management Body of Knowledge),
LRS RFP - Attachment A (SOW) Page 15 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
408 including Integration Management, Scope Management, Time Management, Cost
409 Management, Quality Management, Human Resource Management, Communications
410 Management, Risk Management and Procurement Management, in the performance of all
411 Work.
412 3.1.1 Subtask 1.1: Project Initiation.
413 CONTRACTOR shall perform the following Work in this Subtask 1.1:
414 1. Deliver and obtain COUNTY approval for the Project Control Document
415 (PCD), including the initial Project Work Plan and Risk Management
416 Plan, which shall include the initial identification of risks that may
417 adversely impact or delay the delivery of the LRS.
418 2. Prepare the Project Office Physical Site Plan, secure the Project Office
419 site, and provide a certification of readiness for occupancy of the Project
420 Office, certifying that all planned construction for the Project Office has
421 been completed in accordance with the Project Office Physical Site Plan
422 and that the Project Office is ready for occupancy by the Project Team.
423 3. Prepare Incoming Orientation Plans to allow appropriate knowledge
424 transfer between DPSS Systems contractors and subject matter experts and
425 DCFS Systems subject matter experts, and CONTRACTOR.
426 4. Conduct a Project Initiation Completion Review with COUNTY.
427 CONTRACTOR shall deliver and present Deliverable 1.1.1 (Project Control
428 Document (PCD)) to COUNTY at a meeting within thirty (30) days of the
429 Effective Date. Approval by COUNTY Project Director of Deliverable 1.1.1
430 (Project Control Document (PCD)) must occur before any further work under the
431 Agreement may continue. At COUNTY Project Director‟s request, from time-to-
432 time during the term of the Agreement, CONTRACTOR shall provide an updated
433 PCD.
434 All Work under the Agreement shall be described specifically by
435 CONTRACTOR in the PCD. CONTRACTOR may automate the production of
LRS RFP - Attachment A (SOW) Page 16 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
436 PCD components (e.g., Risk Management Plan) using software package(s)
437 approved by COUNTY. CONTRACTOR shall provide these tools to COUNTY
438 at no additional charge, regardless of the number of Users.
439 As part of Deliverable 1.1.1 (Project Control Document (PCD)), CONTRACTOR
440 shall include the initial version of the Project Work Plan, developed in COUNTY-
441 specified version of Microsoft Project, and the initial version of Risk Management
442 Plan. In the Project Work Plan, CONTRACTOR shall identify the time required
443 to complete all Tasks and Subtasks and document the project‟s critical path. In the
444 Risk Management Plan, CONTRACTOR shall document its approach to risk
445 assessment, risk mitigation, and risk management for all Work under the
446 Agreement, including the overall methodology, the tools to be used, and the
447 escalation process. The Project Work Plan and Risk Management Plan shall be
448 periodically updated by CONTRACTOR as specified in Subtask 1.2 (Project
449 Planning).
450 CONTRACTOR shall provide the Project Office that supports all activities,
451 including project administration, development, testing, LRS performance
452 monitoring, ad-hoc training, and demonstration activities. CONTRACTOR shall
453 be fully responsible for maintaining the Project Office throughout the term of the
454 Agreement. COUNTY requires the Project Office be located within Los Angeles
455 County and within ten (10) miles of DPSS Administrative Headquarters, 12860
456 Crossroads Parkway South, City of Industry, CA 91746, unless otherwise
457 approved by COUNTY Project Director.
458 CONTRACTOR shall describe the overall physical facility considerations for the
459 Project Office in Deliverable 1.1.2 (Project Office Physical Site Plan), including
460 the Project Office requirements in Attachment B (Statement of Requirements).
461 CONTRACTOR shall identify one or more potential sites for the Project Office
462 within thirty (30) days after COUNTY notification of CONTRACTOR selection
463 under the RFP. COUNTY will make site visits and select the site which shall be
464 the designated Project Office site in Deliverable 1.1.2 (Project Office Physical
LRS RFP - Attachment A (SOW) Page 17 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
465 Site Plan). CONTRACTOR shall ensure that the Project Office, at the site
466 approved by COUNTY in Deliverable 1.1.2 (Project Office Physical Site Plan), is
467 ready for occupancy by CONTRACTOR and COUNTY staff within ninety (90)
468 days of COUNTY approval of Deliverable 1.1.2 (Project Office Physical Site
469 Plan). CONTRACTOR shall provide Deliverable 1.1.3 (Project Office
470 Certification of Readiness), certifying in writing to COUNTY that the Project
471 Office site is ready for occupancy.
472 CONTRACTOR shall ensure that the Project Office will continue to comply with
473 the specifications indicated in Deliverable 1.1.2 (Project Office Physical Site
474 Plan) through the term of the Agreement. Any change in Project Office site
475 location shall require approval of COUNTY in the same manner as the initial
476 approval.
477 Within ninety (90) days after the Effective Date, CONTRACTOR shall prepare
478 Deliverable 1.1.4 (Incoming Orientation Plans) to provide appropriate knowledge
479 transfer from DPSS Systems contractors and subject matter experts and DCFS
480 Systems subject matter experts to CONTRACTOR regarding existing
481 functionality and business processes.
482 COUNTY will review Deliverable 1.1.4 (Incoming Orientation Plans) with
483 CONTRACTOR to verify its completeness. CONTRACTOR shall revise
484 Deliverable 1.1.4 (Incoming Orientation Plans), as appropriate, following the joint
485 review with COUNTY. CONTRACTOR shall incorporate all orientation
486 activities into the Project Work Plan.
487 Prior to the completion of this Subtask 1.1, CONTRACTOR shall conduct a
488 Project Initiation Completion Review with COUNTY, presenting to COUNTY
489 evidence that all project initiation-related work has been completed.
490 CONTRACTOR shall then prepare Deliverable 1.1.5 (Project Initiation
491 Completion Report), including the agenda, minutes, and supporting
492 documentation from the Project Initiation Completion Review.
LRS RFP - Attachment A (SOW) Page 18 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
493 3.1.1.1 Deliverable 1.1.1: Project Control Document (PCD).
494 CONTRACTOR shall provide the Project Control Document (PCD)
495 which shall include:
496 1. All Work described in Attachment A (Statement of Work) and
497 elsewhere in the Agreement;
498 2. An approach to completing all Work, including a work breakdown
499 structure (WBS) with Task and Subtask descriptions, associated
500 Deliverables, and resource requirements;
501 3. A Project Work Plan, developed in COUNTY-specified version of
502 Microsoft Project, which shall include:
503 A. All Deliverables, including those referenced in Attachment G
504 (Pricing Schedule Forms);
505 B. All Tasks, Subtasks, and other Work;
506 C. Associated dependencies among Tasks, Subtasks, and other
507 Work;
508 D. Resources assigned to each Task, Subtask, and other Work;
509 E. Start date and date of completion for each Deliverable, Task,
510 Subtask, and other Work;
511 F. Proposed COUNTY review period for each Deliverable; and
512 G. Proposed milestones;
513 4. Identification of all CONTRACTOR Key Staff, including those
514 described in Section 2.1.2 (CONTRACTOR Resources);
515 5. Quality assurance (QA) methodology and practices;
516 6. A comprehensive Deficiency Management Plan, documenting the
517 approach to Deficiency management, including methodology,
518 recommended tool(s), and escalation process;
519 7. Approach to project communications;
LRS RFP - Attachment A (SOW) Page 19 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
520 8. A comprehensive Risk Management Plan, documenting the
521 approach to risk analysis (e.g., the evaluation of risks and risk
522 interactions to assess the range of possible project outcomes), risk
523 mitigation (e.g., the identification of ways to minimize or eliminate
524 project risks), and risk tracking/control (e.g., a method to ensure
525 that all steps of the risk management process are being followed
526 and, risks are being mitigated effectively). The plan shall have a
527 clearly established process for problem escalation and shall be
528 updated, as needed, through the term of the Agreement;
529 9. Initial identification of risks that may impact the timely delivery of
530 the LRS, probability and potential impact, recommended
531 mitigation strategy, and impact of implementing any risk
532 mitigation strategies;
533 10. Project staffing and resource management plan; and
534 11. An approach to configuration management and change
535 management. Changes, in this context, refer to changing the
536 functionality of a component/module or adding additional
537 functionality (e.g., changes to the project scope). The approach
538 shall ensure that the impacts and rationale for each change are
539 analyzed and coordinated prior to being approved. The change
540 management process may vary from item to item, as determined by
541 COUNTY Project Director.
542 3.1.1.2 Deliverable 1.1.2: Project Office Physical Site Plan.
543 In this Deliverable 1.1.2, CONTRACTOR shall provide the Project
544 Office Physical Site Plan which shall include:
545 1. Floor plans for the Project Office in accordance with
546 Attachment B (Statement of Requirements).
547 2. Physical security requirements, including access control
548 plans and procedures, security plans and procedures, and
LRS RFP - Attachment A (SOW) Page 20 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
549 physical considerations for business continuity and disaster
550 recovery at the Project Office;
551 3. Plan for protected access to the Integrated Development
552 Environment (IDE) for the LRS for all authorized
553 CONTRACTOR and COUNTY staff at the Project Office
554 to review pertinent data and documentation related to the
555 LRS design, development, implementation, and acceptance;
556 3.1.1.3 Deliverable 1.1.3: Project Office Certification of Readiness.
557 CONTRACTOR shall provide the Project Office Certification of
558 Readiness certifying that all planned construction for the Project
559 Office has been completed in accordance with Subtask 1.1 (Project
560 Initiation) and Deliverable 1.1.2 (Project Office Physical Site Plan)
561 and that the Project Office is ready for occupancy by the Project
562 Team. CONTRACTOR shall provide COUNTY a copy of the
563 executed lease or ownership documents, as applicable, for the
564 Project Office as part of this Deliverable 1.1.3. Approval of this
565 Deliverable 1.1.3 by COUNTY shall allow CONTRACTOR to
566 start invoicing COUNTY for the Fixed Monthly Rate Price for
567 M&O Services.
568 3.1.1.4 Deliverable 1.1.4: Incoming Orientation Plans.
569 CONTRACTOR shall provide an Incoming Orientation Plan for
570 DPSS Systems and an Incoming Orientation Plan for DCFS
571 Systems.
572 The Incoming Orientation Plan for DPSS Systems shall include:
573 1. Any information, data, and documentation required from
574 DPSS Systems contractors and subject matter experts ;
575 2. Activities needed to ensure appropriate knowledge transfer
576 from DPSS Systems contractors and subject matter experts
LRS RFP - Attachment A (SOW) Page 21 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
577 to CONTRACTOR, regarding existing functionality and
578 business processes; and
579 3. CONTRACTOR roles and responsibilities for all activities.
580 The Incoming Orientation Plan for DCFS Systems shall include:
581 1. Any information, data, and documentation required from
582 DCFS Systems subject matter experts;
583 2. Activities needed to ensure appropriate knowledge transfer
584 from DCFS Systems subject matter experts to
585 CONTRACTOR, regarding existing functionality and
586 business processes; and
587 3. CONTRACTOR roles and responsibilities for all activities.
588
589 3.1.1.5 Deliverable 1.1.5: Project Initiation Completion Report.
590 CONTRACTOR shall provide the Project Initiation Completion
591 Report that documents all Work and its satisfactory completion
592 during Subtask 1.1 (Project Initiation) to include:
593 1. Summary of Subtask 1.1 (Project Initiation) Work, results,
594 and satisfactory completion;
595 2. Lessons learned during Subtask 1.1 (Project Initiation); and
596 3. Agenda, minutes, and supporting documentation from the
597 Project Initiation Completion Review.
598 3.1.2 Subtask 1.2: Project Planning.
599 CONTRACTOR shall prepare: (I) M&O Services Plan, (II) M&E Services
600 Plan, and (III) Conversion and Archiving Plans, as follows:
601 I. M&O Services Plan:
602 CONTRACTOR shall provide M&O Services which shall include all
603 goods and services necessary to manage, operate, and support the LRS to
LRS RFP - Attachment A (SOW) Page 22 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
604 comply with the Specifications and shall be provided on a 24x7x365 basis
605 during the term of the Agreement. CONTRACTOR shall provide to
606 COUNTY Deliverable 1.2.1 (M&O Services Plan), which shall include
607 documentation of the activities and processes for M&O Services. M&O
608 Services shall include the following:
609 Central Sites Services: CONTRACTOR shall provide Central
610 Sites Services, including management, operations, and support for
611 LRS. Management, operations, and support shall include
612 monitoring of system and application activity, performing backups
613 and restoration as needed, business continuity/disaster recovery,
614 security and network monitoring, management, and alerting.
615 Central Sites Services shall include LRS Hardware, LRS Software,
616 and maintenance services. CONTRACTOR shall manage the
617 electronic transfer of data (e.g., interfaces, downloads, reports,
618 extracts, etc.) between CONTRACTOR, and COUNTY and other
619 agencies. CONTRACTOR shall coordinate with ISD regarding
620 network and security management, including monitoring LRS
621 access to and from the Internet and to and from the LAnet/EN.
622 Print Facility Sites Services: CONTRACTOR shall provide Print
623 Facility Sites Services, including management, operations, and
624 support for Print Facility Sites. Management, operations, and
625 support shall include printing operations, monitoring of facility
626 activity, performing backups and restoration as needed, business
627 continuity/disaster recovery, security and network monitoring,
628 management, and alerting. Print Facility Sites Services shall
629 include LRS Hardware, LRS Software, and maintenance services.
630 CONTRACTOR shall process and manage mailing and
631 distribution of all LRS generated material (e.g., reports, Notices of
632 Action, etc.) from the Print Facility Sites. CONTRACTOR shall
LRS RFP - Attachment A (SOW) Page 23 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
633 manage all COUNTY negotiable materials (e.g., warrants and
634 vouchers), providing secure storage and documented reconciliation
635 services.
636 Project Office Services: CONTRACTOR shall provide Project
637 Office Services, including analysis, monitoring and reporting
638 services, and asset management to demonstrate to COUNTY that
639 all warranties, licenses, and maintenance contracts with third party
640 vendors are kept current. CONTRACTOR shall coordinate with
641 COUNTY system, network, and Security Management and
642 administration staff as described in Deliverable 1.2.1 (M&O
643 Services Plan).
644 Enterprise Connecting Hardware goods and services:
645 CONTRACTOR shall provide Enterprise Connecting Hardware
646 goods and services, including management, operations, and
647 support of the Enterprise Connecting Hardware, which includes the
648 Gateway. Management, operations, and support shall include the
649 monitoring of security and network activity, and maintenance of
650 Enterprise Connecting Hardware, including the Gateway.
651 Project management goods and services: CONTRACTOR shall
652 provide project management goods and services, including project
653 management, operations management, network management,
654 configuration management, integration management, Security
655 Management, quality assurance management, change management,
656 risk management, Deficiency management, business
657 continuity/disaster recovery management, procurement and asset
658 management, communications management, capacity
659 management, and performance management.
660 CONTRACTOR shall provide a 24-month staffing plan that
661 includes the organizational chart, the roster, the roles, the
LRS RFP - Attachment A (SOW) Page 24 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
662 responsibilities, and the qualifications of CONTRACTOR staff
663 involved in the ongoing management, operations, and support of
664 the LRS. The staffing plan shall demonstrate and ensure that the
665 LRS shall comply with the Specifications, including meeting and
666 maintaining the performance requirements, and that
667 CONTRACTOR shall comply with the Agreement.
668 CONTRACTOR shall provide an updated 24-month staffing plan
669 at the beginning of each quarter.
670 CONTRACTOR shall provide help desk services, problem fixes,
671 change/enhancement implementation, backups, and business
672 continuity/disaster recovery, and lifecycle phases required for each
673 new LRS Application Software release. CONTRACTOR shall
674 provide configuration management, change management, and
675 change notification processes to ensure that a complete and
676 accurate version of the LRS is maintained at all times.
677 Operational Support Communications Plan goods and
678 services: CONTRACTOR shall provide the Operational Support
679 Communications Plan and related goods and services. The
680 Operational Support Communications Plan shall include the
681 procedures for the coordination and communication between
682 CONTRACTOR, COUNTY, and external interface entities shown
683 in Section 4 (Interfaces) of Attachment B (Statement of
684 Requirements). CONTACTOR shall inform COUNTY of any
685 issues that may affect the LRS in complying with the
686 Specifications, including meeting the performance requirements.
687 The priority and severity of each issue shall determine what
688 communication procedures shall be followed. CONTRACTOR
689 shall include the various communication trees. CONTRACTOR
690 shall maintain these communication trees and shall receive input
691 from COUNTY regarding the COUNTY staff on the
LRS RFP - Attachment A (SOW) Page 25 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
692 communication trees. The Operational Support Communications
693 Plan shall include:
694 1. Procedures for coordination and communication between
695 CONTRACTOR staff, COUNTY staff, and external
696 interface entities; and
697 2. Communication tree documentation for CONTRACTOR
698 staff, COUNTY staff, and external interface entities.
699 M&O Request goods and services: CONTRACTOR shall
700 provide M&O Request goods and services, including the
701 implementation and support of all changes to M&O Services, as
702 requested by COUNTY in M&O Requests.
703 M&E Proposal goods and services: CONTRACTOR shall
704 provide M&E Proposals and related goods and services, including
705 the preparation, provision, and presentation of M&E Proposals in
706 response to M&E Requests.
707 Change Management Plan goods and services: CONTRACTOR
708 shall provide a Change Management Plan and related goods and
709 services. The Change Management Plan shall include change
710 management procedures for tracking M&O Requests, M&E
711 Requests, and M&E Proposals, describing the use of tools for
712 tracking, monitoring progress, and reporting on activities and
713 outcomes resulting from the completion of an M&O Request and
714 an M&E Proposal. CONTRACTOR shall make these procedures
715 available to COUNTY-specified staff, including an online
716 handbook. CONTRACTOR shall provide timely and accurate
717 updates to the Change Management Plan during the term of the
718 Agreement and as required by COUNTY Project Director.
LRS RFP - Attachment A (SOW) Page 26 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
719 The Change Management Plan shall document the strategy and
720 procedures for change management of the LRS, including:
721 1. Change management process flow and strategy;
722 2. Description of Automated Change Tracking System
723 (ACTS);
724 3. Management of the impact and rationale for each change;
725 4. Process for M&O Request submission by COUNTY,
726 implementation by CONTRACTOR, and approval by
727 COUNTY of all Work;
728 5. Process for M&E Request submission by COUNTY;
729 6. Process for M&E Proposal submission by
730 CONTRACTOR, approval by COUNTY, implementation
731 by CONTRACTOR, and approval by COUNTY of all
732 Work.
733 7. Process for the management of LRS Application Software
734 releases to each test environment and production
735 environment, including rollback to the COUNTY-specified
736 previous version;
737 8. Process for updates to LRS Hardware;
738 9. Process for updates to LRS Software;
739 10. Process for version control of LRS Hardware; and
740 11. Process for version control of LRS Software.
741 CONTRACTOR shall develop and utilize the ACTS, as specified
742 in Attachment B (Statement of Requirements), to track and report
743 on all programming and operational support hours, projected and
744 actual, used to complete each M&O Request and M&E Proposal.
745 CONTRACTOR shall provide training in the use of ACTS prior to
LRS RFP - Attachment A (SOW) Page 27 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
746 any CONTRACTOR and/or COUNTY staff being authorized
747 access to ACTS.
748 Performance Management Plan goods and services:
749 CONTRACTOR shall provide a Performance Management Plan
750 and related goods and services. The Performance Management
751 Plan shall include a description of CONTRACTOR‟s approach for
752 meeting the performance requirements, including availability and
753 response times, set forth in the Agreement. CONTRACTOR shall
754 update this Plan with COUNTY on an annual basis or as otherwise
755 requested by COUNTY Project Director. CONTRACTOR shall
756 document how CONTRACTOR shall conduct LRS performance
757 verification, the procedures for capturing, analyzing, and reporting
758 results, and the acceptance criteria for ensuring that LRS meets the
759 performance criteria. CONTRACTOR shall document how and
760 when results will be reported, how any Deficiencies will be
761 identified, and the plan and procedures for corrective actions. The
762 Performance Management Plan shall document how
763 CONTRACTOR shall monitor, analyze, and manage the
764 performance of the LRS to meet the performance requirements.
765 The Plan shall include:
766 1. Process and procedures used to monitor each performance
767 requirement specified in the Agreement, including
768 performance objectives, metrics, and indicators;
769 2. Tools and procedures for monitoring, analyzing, and
770 reporting results;
771 3. Acceptance criteria for each performance requirement;
772 4. Retention periods for system activity logs and test results;
773 5. Reporting of results including format and frequency;
LRS RFP - Attachment A (SOW) Page 28 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
774 6. Procedures to correct each Deficiency using a corrective
775 action plan. Each corrective action plan shall include:
776 A. Description of each Deficiency and its root cause;
777 B. Business processes, LRS functions, and/or
778 interfaces impacted;
779 C. Description of all potential risks to the LRS,
780 including to Countywide Implementation, and
781 mitigation strategy for the LRS;
782 D. Corrective action plan, test scenarios, and
783 implementation approach;
784 E. Schedule for completion of each corrective action
785 and resources required/assigned;
786 F. Status of each corrective action; and
787 G. Approval procedures that require COUNTY Project
788 Director‟s approval of each correction.
789 Business Continuity/Disaster Recovery Plan goods and
790 services: CONTRACTOR shall provide a Business
791 Continuity/Disaster Recovery Plan and related goods and services,
792 including LRS Application Software backups and LRS Data
793 backups. The Business Continuity/Disaster Recovery Plan shall be
794 consistent with COUNTY business continuity/disaster recovery
795 plans. CONTACTOR shall provide all goods and services,
796 excluding responsibilities for LAnet/EN, related to any and all
797 issues pertaining to LRS business continuity and disaster recovery.
798 The range of goods and services covers the spectrum from partial
799 loss of function or data for a brief amount of time to a “worst-case”
800 scenario in which a man-made or natural disaster or IT failure may
801 result in the loss of the entire LRS. CONTRACTOR shall
802 categorize system disruptions by the severity of the event. The
LRS RFP - Attachment A (SOW) Page 29 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
803 parameters of these events, identified in advance by
804 CONTRACTOR, shall require approval of COUNTY Project
805 Director, and may be changed from time-to-time as required by
806 COUNTY Project Director. The categories of system disruptions
807 include:
808 1. Minor Event that includes a minor or partial loss of LRS
809 functionality.
810 2. Significant Event that includes a significant loss of LRS
811 functionality.
812 3. Serious Event that includes an extended disruption of LRS
813 functionality due to a major disaster (e.g., earthquakes,
814 fires, floods, hurricanes, and terrorist attacks).
815 The Business Continuity/Disaster Recovery Plan shall include a
816 business impact analysis to determine the areas in the technical
817 infrastructure that are required to ensure that all requirements in
818 the Agreement shall be met. The Plan shall describe each of the
819 above system disruption events in accordance with the proposed
820 LRS technical infrastructure, document the results of the business
821 impact analysis for each severity level, and determine the
822 appropriate actions to be taken to ensure restoration and/or
823 continuity of services in accordance with the Agreement. This Plan
824 shall define and describe the procedures required to ensure that the
825 LRS, including Primary Central Site, Backup Central Site, Central
826 Print Facility, Backup Print Facility, Project Office, and the
827 Enterprise Connecting Hardware, which includes the Gateway,
828 shall be able to recover from any disruption in service regardless of
829 the level of severity.
LRS RFP - Attachment A (SOW) Page 30 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
830 The Business Continuity/Disaster Recovery Plan shall describe the
831 monitoring, testing, and plan revision processes used to verify that
832 the LRS, including Primary Central Site, Backup Central Site,
833 Central Print Facility, Backup Print Facility, Project Office, and
834 Enterprise Connecting Hardware, which includes the Gateway,
835 continue to comply with the Specifications, including meeting the
836 requirements in the Agreement for business continuity operations
837 and disaster recovery.
838 The Business Continuity/Disaster Recovery Plan shall serve as a
839 master plan for responding to system outages, ensuring continuity
840 of business operations, and recovery from a disaster. In this Plan,
841 CONTRACTOR shall include:
842 1. Overview of the technical infrastructure and how it relates
843 to COUNTY business continuity/disaster recovery plans
844 and operations.
845 2. Business impact analysis of the LRS functionality and the
846 LRS Data that identifies and prioritizes the critical LRS
847 systems and components.
848 3. Data backup/recovery procedures for backing up,
849 retrieving, and restoring exact copies of most current LRS
850 Data. CONTRACTOR shall document the procedures for
851 ensuring physical safety of media upon which the LRS and
852 LRS Data are backed up. CONTRACTOR shall document
853 its approach for the secure storage of all backup media,
854 both on-site and off-site, including the proposed response
855 time for recovery of the media from off-site storage.
856 4. LRS Application Software backup/recovery procedures for
857 backing up, retrieving, and restoring LRS Application
858 Software. CONTRACTOR shall document its approach for
LRS RFP - Attachment A (SOW) Page 31 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
859 the backup and recovery of the LRS Application Software,
860 both on-site and off-site, including the proposed response
861 time for recovery.
862 5. Emergency mode of operations that provides the
863 procedures to enable business continuity, protect the
864 security of electronic IT information during and
865 immediately after an emergency, and recover from the
866 emergency mode of operation with minimal impact on
867 Users.
868 6. Command and control processes and procedures that
869 delineate specific roles and responsibilities, communication
870 and actions that CONTRACTOR system administration
871 staff must follow in an emergency.
872 7. Procedures for performing business continuity/disaster
873 recovery testing during Subtask 9.2 (Integration and
874 System Testing), during Subtask 9.3 (User Acceptance
875 Testing), during Task 12 (Pilot), during Task 14 (Phase 2
876 (Performance Verification Phase)), and semi-annually
877 throughout Task 15 (Phase 3 (Operational Phase)). Each
878 test shall continue until all test results have been approved
879 by COUNTY Project Director. Each test shall include:
880 A. Coordination from the Project Office;
881 B. Automated switchover to the Backup Central Site
882 and/or Backup Print Facility to meet performance
883 requirements under full load in the production
884 environment;
885 C. Connectivity between LAnet/EN and the Primary
886 Central Site or Backup Central Site, Central Print
LRS RFP - Attachment A (SOW) Page 32 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
887 Facility or Backup Print Facility, and Enterprise
888 Connecting Hardware, which includes the Gateway;
889 D. Interfaces to all external systems;
890 E. Test results reports; and
891 F. Updates to the Business Continuity/Disaster
892 Recovery Plan.
893 8. Workforce contingency training plan that describes the
894 training and preparation of designated workforce members
895 regarding the enactment of the Business
896 Continuity/Disaster Recovery Plan.
897 9. Procedures to replace office space or data center facilities if
898 required by the nature of the disaster or emergency.
899 10. Exercise log that documents the calendar day(s) when the
900 Business Continuity/Disaster Recovery Plan is tested, what
901 the nature of the test(s) are, any problems identified during
902 each test, and corrective actions to be taken. The results of
903 each test shall require approval by COUNTY Project
904 Director.
905 11. Revision history that documents any changes made to the
906 Plan, the date and details of the changes, and the parties
907 responsible for initiating and approving the changes.
908 CONTRACTOR shall maintain a backup of the LRS Application
909 Software and LRS Data as set forth in the Agreement.
910 CONTRACTOR shall complete a full backup of the LRS
911 Application Software and LRS Data that reflects the LRS
912 configuration and data at the completion of the week‟s processing
913 cycle (e.g., Sunday). CONTRACTOR shall provide a daily backup
914 of the LRS Data at the end of day processing Monday through
915 Saturday. CONTRACTOR shall provide a copy of the daily
LRS RFP - Attachment A (SOW) Page 33 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
916 backup of the LRS Application Software, as requested by
917 COUNTY Project Director. CONTRACTOR shall verify that all
918 backups are complete, accurate, and functional. CONTRACTOR
919 shall make available to COUNTY a daily report, preferably online,
920 delineating the completion of each backup, its status, and a catalog
921 of the items backed up.
922 Project Reporting Plan goods and services: CONTRACTOR
923 shall provide a Project Reporting Plan and related goods and
924 services. The Project Reporting Plan shall include a description of
925 CONTRACTOR‟s approach to all project reporting, including
926 meetings, presentations, and reports provided to COUNTY on a
927 periodic basis. CONTRACTOR shall describe the structure and/or
928 format of any periodic meetings, presentations, and reports
929 provided to COUNTY. The format of these meetings,
930 presentations, and reports shall require approval by COUNTY
931 Project Director, and shall change from time-to-time during the
932 term of the Agreement as determined by COUNTY Project
933 Director. The Project Reporting Plan shall include:
934 1. Bi-weekly and monthly reporting for ongoing project
935 administration, including:
936 A. Central Sites Services status summary;
937 B. Print Facility Sites Services status summary;
938 C. Project Office Site Services status summary;
939 D. Security Management services summary that
940 includes a description of each security incident,
941 including any breach, any attack, or the introduction
942 of any Disabling Device, that occurred during the
943 reporting period;
LRS RFP - Attachment A (SOW) Page 34 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
944 E. LRS Hardware management summary, including an
945 overview of each update to LRS Hardware;
946 F. LRS Application Software management summary,
947 including an overview of each Update to LRS
948 Application Software;
949 G. Commercially Available Software management
950 summary, including an overview of each Update to
951 Commercially Available Software;
952 H. LRS Helpdesk activity summary, including an
953 overview of CONTRACTOR responses to all
954 requests by COUNTY-specified Users during the
955 previous reporting period, disposition of each
956 request, and any open issues;
957 I. Summary of Deficiencies identified by
958 CONTRACTOR or COUNTY; and
959 J. Summary of performance verification and the
960 Specifications compliance status to include:
961 i. LRS performance target and actual
962 performance;
963 ii. Performance of the LRS during the previous
964 reporting period;
965 iii. LRS performance compliance status; and
966 iv. For each Deficiency, include:
967 a. Description of each Deficiency and its
968 root cause;
969 b. Business processes, LRS functions,
970 and/or interfaces impacted;
971 c. Description of all potential risks to the
972 LRS, including to Countywide
LRS RFP - Attachment A (SOW) Page 35 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
973 Implementation, and mitigation strategy
974 for the LRS;
975 d. Corrective action plan, test scenarios,
976 and implementation approach;
977 e. Schedule for completion of each
978 corrective action and resources
979 required/assigned;
980 f. Status of each corrective action;
981 g. Date of completion of each correction; and
982 h. Date of COUNTY Project Director‟s
983 approval of each correction.
984 2. Monthly reporting for M&O Requests, including:
985 A. Number of M&O Requests by type as specified by
986 COUNTY Project Director;
987 B. Number of active M&O Requests (by current
988 month, year);
989 C. Number of completed M&O Requests (by current
990 month, year);
991 D. Describe deviations, including schedule deviations,
992 related to each M&O Request; and
993 E. Identified issues, proposed solutions, and status.
994 3. Monthly reporting for M&E Requests and M&E Proposals,
995 including:
996 A. Number of M&E Requests by type as specified by
997 COUNTY Project Director;
998 B. Number of M&E Proposals by type as specified by
999 COUNTY Project Director;
1000 C. Number of active M&E Requests (by current month
1001 and year);
LRS RFP - Attachment A (SOW) Page 36 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
1002 D. Number of active M&E Proposals (by current
1003 month and year);
1004 E. Number of completed M&E Proposals (by current
1005 month, year);
1006 F. Describe deviations, including schedule deviations,
1007 related to each M&E Proposal; and
1008 G. Identified issues, proposed solutions, and status.
1009 4. Semi-annual reporting for asset management of the LRS,
1010 including:
1011 A. Inventory of all LRS Hardware, including hardware
1012 manufacturers, types, product names, model
1013 numbers, quantities by model number, and
1014 configuration specifications; and
1015 B. Inventory of all LRS Software, including software
1016 manufacturers, types, product names, version
1017 numbers, and quantities of license by version
1018 number.
1019 5. Semi-annual reporting of all telecommunication circuits for
1020 the LRS, including, circuit providers, circuit types,
1021 termination points, and bandwidth usage statistics.
1022 6. Semi-annual reporting for business continuity/disaster
1023 recovery testing, including test results.
1024 7. Annual reporting for the Statement of Auditing Standards
1025 No. 70 (SAS 70) Report Type II. The SAS 70 audit report
1026 shall comply with the standards set forth by the Auditing
1027 Standards Board of the American Institute of Certified
1028 Public Accountants (AICPA). The SAS 70 audit shall
1029 cover all aspects, including controls and operations, of the
1030 LRS. CONTRACTOR shall address and remedy, as
LRS RFP - Attachment A (SOW) Page 37 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
1031 determined by COUNTY Project Director, any issues
1032 and/or risks identified in the SAS 70 audit report and
1033 provide any necessary follow-up SAS 70 audit reports, as
1034 determined by COUNTY Project Director.
1035 8. Monthly reporting of end dates of Original Equipment
1036 Manufacturer (OEM) full service life of LRS Hardware,
1037 OEM service warranty of LRS Hardware, and OEM full
1038 support of Commercially Available Software as described
1039 in Attachment B (Statement of Requirements).
1040 9. Daily and monthly performance monitoring reports as
1041 described in Subsection 3.6 (LRS Performance
1042 Requirements) of Attachment B (Statement of
1043 Requirements).
1044 10. Monthly requirements metrics that include the number of
1045 requirements added, deleted, modified and outstanding
1046 during the particular month and the total number of all
1047 requirements in existence at the end of the reporting month.
1048 11. Monthly product quality metrics that include Pareto
1049 analysis, Errors density, and average age of outstanding
1050 Errors.
1051 12. Daily system size and utilization metrics that include daily
1052 system utilization (e.g., Direct Access Storage Device
1053 (DASD), memory, processors, and System Management
1054 Facilities (SMF) data).
1055 II. M&E Services Plan:
1056 CONTRACTOR shall provide to COUNTY Deliverable 1.2.2 (M&E
1057 Services Plan), which shall include a description of the activities and
1058 processes for M&E Services. CONTRACTOR shall provide M&E
1059 Services which shall include all goods and services to complete
LRS RFP - Attachment A (SOW) Page 38 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
1060 Application Software Modifications and/or Enhancements as may be
1061 requested by COUNTY Project Director and set forth in COUNTY-
1062 approved and COUNTY-prioritized M&E Proposals during Phase 2
1063 (Performance Verification Phase) and Phase 3 (Operational Phase).
1064 M&E shall include the following:
1065 1. Additions, deletions, or other modifications of LRS Application
1066 Software functions, such as changes to the current LRS outputs or
1067 processes, new or modified reports, new or modified screens;
1068 2. Modifications and/or enhancements to LRS Application Software
1069 workflows, attribute tables, workflow/process flows, logical data
1070 model, physical data model, and data dictionary; and
1071 3. Development of additional system interfaces with LRS.
1072 CONTRACTOR shall provide a 24-month staffing plan that includes the
1073 organizational chart, the roster, the roles, the responsibilities, and the
1074 qualifications of CONTRACTOR staff involved in providing M&E
1075 Services. CONTRACTOR shall provide an updated 24-month staffing
1076 plan at the beginning of each quarter. CONTRACTOR shall provide all
1077 software, including automated regression test tools, and any other goods
1078 and services to perform M&E Services and complete M&E.
1079 CONTRACTOR shall train the COUNTY Project Team on the use of
1080 CONTRACTOR-supplied automated regression test tools.
1081 CONTRACTOR shall evaluate each M&E Request from COUNTY and
1082 timely submit to COUNTY an M&E Proposal. CONTRACTOR shall
1083 confirm each functional and technical requirement in each M&E Request,
1084 including an impact analysis of the proposed change on the current LRS.
1085 CONTRACTOR may propose to bundle one or more M&E Requests into
1086 a single M&E Proposal with the prior approval of COUNTY Project
LRS RFP - Attachment A (SOW) Page 39 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
1087 Director. CONTRACTOR shall prepare and timely submit M&E
1088 Proposals to COUNTY. Each M&E Proposal shall include:
1089 1. Description of each M&E and objectives and outcomes;
1090 2. Impact analysis of each M&E on the LRS and LAnet/EN,
1091 including assessment of the complexity, estimated lines of Source
1092 Code, and impact on operations, security, programs, screens, edits,
1093 error messages, online/batch processing, interfaces, performance,
1094 and User training;
1095 3. Maximum, not-to-exceed price for the M&E Proposal; and
1096 4. Work plan for the M&E Proposal, including:
1097 A. Schedule;
1098 B. Tasks and deliverables, including;
1099 i. Requirements verification document;
1100 ii. Design document;
1101 iii. Development activities;
1102 iv. Test plan and reports; and
1103 v. Production certification;
1104 C. Staff resources by name for each task/deliverable; and
1105 D. Estimated hours by staff resource for each task/deliverable.
1106 All M&E Proposals require COUNTY Project Director‟s approval and
1107 shall be prioritized by COUNTY Project Director. COUNTY Project
1108 Director must approve each M&E Proposal prior to CONTRACTOR
1109 commencing any work to provide the specified M&E. All M&E Proposals
1110 shall be prioritized by COUNTY Project Director, and CONTRACTOR
1111 shall participate in M&E Proposal prioritization meetings with COUNTY.
1112 CONTRACTOR shall complete each M&E within the original schedule
1113 contained in the M&E Proposal. COUNTY Project Director may require
LRS RFP - Attachment A (SOW) Page 40 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
1114 an expedited completion time depending on the urgency of a specified
1115 M&E.
1116 CONTRACTOR shall develop and implement each M&E in an M&E
1117 Proposal in accordance with the LRS System Development Lifecycle
1118 (SDLC) used in Phase 1 (Design/Development/Implementation Phase),
1119 including:
1120 1. Configuration change package that documents the changes to LRS
1121 Application Software, including requirements, design
1122 specifications, technical infrastructure, and application, which shall
1123 result from the specified M&E; and
1124 2. Test plan.
1125 CONTRACTOR shall develop functional/technical design specifications
1126 for each M&E in an M&E Proposal based on the verified requirements
1127 and shall develop, code, test, and validate each M&E. CONTRACTOR
1128 shall also maintain existing, and incorporate new, COUNTY-developed
1129 test scenarios into the IDE.
1130 CONTRACTOR shall provide the following after completing all activities
1131 involved in modifying and/or enhancing the LRS Application Software in
1132 accordance with each M&E Proposal:
1133 1. A written summary of the M&E Proposal and related activities;
1134 2. A description of any modifications and/or enhancements to the
1135 LRS Application Software, including requirements, design
1136 specifications, technical infrastructure, and application;
1137 3. Any related test plans, test execution, including automated
1138 regression testing procedures, and a final report on test results;
1139 4. LRS Documentation affected by the M&E, using a method that
1140 clearly identifies the M&E to the Documentation and the date of
1141 the change;
LRS RFP - Attachment A (SOW) Page 41 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
1142 5. Updated LRS Application Software Source Code, Object Code,
1143 and Documentation, which shall be placed in the LRS Repository;
1144 and
1145 6. Updated LRS Training Materials and LRS Training Plans.
1146 CONTRACTOR shall maintain documentation of the test results to verify
1147 the adequacy and completeness of the LRS Application Software change.
1148 CONTRACTOR shall update all documentation that pertains to the
1149 implementation of the M&E Proposal. CONTRACTOR shall place into
1150 the LRS Repository all test results and all documentation, including LRS
1151 Application Software Source Code, Object Code and Documentation, and
1152 updated training materials.
1153 CONTRACTOR shall apply its SDLC processes, followed during Phase 1
1154 (Design/Development/Implementation Phase), to implement COUNTY-
1155 approved M&E Proposals during Phase 2 (Performance Verification
1156 Phase) and Phase 3 (Operational Phase). For each COUNTY-approved
1157 M&E Proposal, CONTRACTOR shall:
1158 1. Participate in M&E Proposal prioritization meetings with
1159 COUNTY.
1160 2. Verify COUNTY functional and technical requirements for each
1161 M&E in such M&E Proposal, including an impact analysis of the
1162 proposed change on the current LRS Application Software
1163 implemented design and use.
1164 3. Develop functional/technical design specifications for each M&E
1165 in such M&E Proposal based on the verified requirements;
1166 4. Develop, code, test, and validate each M&E in such M&E
1167 Proposal;
1168 5. Maintain existing, and incorporate new, COUNTY-developed test
1169 scenarios into the IDE;
LRS RFP - Attachment A (SOW) Page 42 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
1170 6. Support automated regression testing of all COUNTY-developed
1171 test scenarios, including the integration of COUNTY-developed
1172 test scenarios into the automated regression test tool;
1173 7. Update all affected LRS Application Software Source Code,
1174 Object Code, and Documentation;
1175 8. Upon COUNTY approval of each successfully tested M&E in such
1176 M&E Proposal, provide updated LRS Application Software Source
1177 Code, Object Code, and Documentation, and updated LRS
1178 Training Plans and LRS Training Materials, no later fifteen (15)
1179 working days prior to implementation of such M&E, which shall
1180 be placed by CONTRACTOR in the LRS Repository; and
1181 9. Implement each successfully tested and COUNTY-approved M&E
1182 in such M&E Proposal into Production Use, as determined by
1183 COUNTY Project Director.
1184 III. Conversion and Archiving Plans:
1185 CONTRACTOR shall provide Deliverable 1.2.3 (Conversion and
1186 Archiving Plans) that includes a Conversion and Archiving Plan for DPSS
1187 Systems and a Conversion and Archiving Plan for DCFS Systems. Each
1188 Conversion and Archiving Plan shall include a description of the strategy
1189 for automated conversion and archiving of DPSS Systems data, DCFS
1190 Systems data, and other legacy data into the LRS in accordance with
1191 Attachment B (Statement of Requirements), which shall include the
1192 development, testing and validation of conversion and archiving software
1193 programs/tools in Task 8 (Baseline Application Software and Conversion
1194 and Archiving Tools) and Task 9 (Testing). The conversion and archiving
1195 strategy shall facilitate the full transition of all DPSS Systems data, DCFS
1196 Systems data, and other legacy data into the LRS and shall optimize the
1197 performance of the LRS, while minimizing disruption of services to the
1198 applicant/participant population in Los Angeles County.
LRS RFP - Attachment A (SOW) Page 43 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
1199 3.1.2.1 Deliverable 1.2.1: M&O Services Plan
1200 CONTRACTOR shall provide an M&O Services Plan that shall
1201 include:
1202 1. Description of M&O Services activities and processes;
1203 2. Yearly staffing plan, including the roles and responsibilities
1204 of CONTRACTOR staff;
1205 3. Operational Support Communications Plan, including
1206 communication trees;
1207 4. Change Management Plan;
1208 5. Performance Management Plan;
1209 6. Business Continuity/Disaster Recovery Plan; and
1210 7. Project Reporting Plan, including schedule and structure of
1211 bi-weekly and monthly status meetings and reports.
1212 3.1.2.2 Deliverable 1.2.2: M&E Services Plan
1213 CONTRACTOR shall provide an M&E Services Plan that shall
1214 include:
1215 1. Description of M&E Services activities and processes; and
1216 2. Yearly staffing plan, including the roles and responsibilities
1217 of CONTRACTOR staff.
1218 3.1.2.3 Deliverable 1.2.3: Conversion and Archiving Plans
1219 CONTRACTOR shall provide a Conversion and Archiving Plan
1220 for DPSS Systems and a Conversion and Archiving Plan for DCFS
1221 Systems in accordance with Subtask 1.2 (Project Planning) and
1222 Attachment B (Statement of Requirements).
1223 The Conversion and Archiving Plan for DPSS Systems shall
1224 include:
LRS RFP - Attachment A (SOW) Page 44 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
1225 1. Conversion and archiving strategy that provides full
1226 accessibility of LRS Data and DPSS Systems data and
1227 other legacy data to Users while meeting the LRS
1228 performance requirements;
1229 2. Development and testing of conversion and archiving
1230 software programs/tools;
1231 3. Transition of all DPSS Systems data and other legacy data
1232 to the LRS in a manner that minimizes disruption of
1233 services; and
1234 4. Recommendation for Local Office Site groupings for
1235 Countywide implementation.
1236 The Conversion and Archiving Plan for DCFS Systems shall
1237 include:
1238 1. Conversion and archiving strategy that provides full
1239 accessibility of LRS Data, DCFS Systems data, and other
1240 legacy data to Users while meeting the LRS performance
1241 requirements;
1242 2. Development and testing of conversion and archiving
1243 software programs/tools;
1244 3. Transition of all DCFS Systems data and other legacy data
1245 to the LRS in a manner that minimizes disruption of
1246 services; and
1247 4. Recommendation for Local Office Site groupings for
1248 Countywide implementation.
1249 3.1.3 Subtask 1.3: Ongoing Project Administration
1250 CONTRACTOR shall perform ongoing project administration during the
1251 term of the Agreement, which shall include:
LRS RFP - Attachment A (SOW) Page 45 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
1252 1. Manage all CONTRACTOR staff, including Subcontractor staff,
1253 assigned to the project;
1254 2. Coordinate with other COUNTY departments, or external
1255 agencies, as appropriate;
1256 3. Manage issues raised by COUNTY and documented in bi-weekly
1257 status reports;
1258 4. Manage risks as described by the Risk Management Plan;
1259 5. Provide planning and direction in accordance with the COUNTY
1260 approved PCD, ensuring that proper project management controls
1261 exist and are in use;
1262 6. Provide change management, following the methodology
1263 documented in the Change Management Plan;
1264 7. Provide routine and realistic assessments of progress as targeted in
1265 the Project Work Plan;
1266 8. Implement quality assurance measures that allow the delivery of
1267 high quality, effective Deliverables to COUNTY;
1268 9. Manage all CONTRACTOR-supplied facilities directly related to
1269 the project which include the Central Sites, the Print Facility Sites,
1270 and Project Office;
1271 10. Participate in the Deliverable review/resolution process for all
1272 Deliverables;
1273 11. Provide updated copies of the PCD, including Project Work Plan
1274 and Risk Management Plan, which incorporates only COUNTY-
1275 approved variances from the current COUNTY-approved PCD;
1276 and
1277 12. Provide ongoing risk management that includes input from all
1278 CONTRACTOR Key Staff.
LRS RFP - Attachment A (SOW) Page 46 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
1279 CONTRACTOR Project Director shall submit bi-weekly status reports in
1280 a COUNTY-specified format to COUNTY Project Director throughout the
1281 term of the Agreement. The first bi-weekly status report shall be due to
1282 COUNTY Project Director fourteen (14) days after the Effective Date,
1283 with subsequent reports due every other Tuesday thereafter for the term of
1284 the Agreement. CONTRACTOR shall compare actual progress for the
1285 preceding bi-weekly period with current COUNTY-approved Project
1286 Work Plan and discuss any variances and work scheduled for the
1287 following period. In each bi-weekly status report, CONTRACTOR shall
1288 include:
1289 1. CONTRACTOR Project Director Name;
1290 2. CONTRACTOR Name;
1291 3. Reporting period start and stop dates;
1292 4. Date of report;
1293 5. Highlights of the reporting period;
1294 6. Tasks, Subtasks and other Work completed during the reporting
1295 period which were not scheduled;
1296 7. Tasks, Subtasks, and other Work completed during the reporting
1297 period which were scheduled;
1298 8. Tasks, Subtasks, and other Work started during the reporting
1299 period;
1300 9. Tasks, Subtasks, and other Work in progress during the reporting
1301 period;
1302 10. Tasks, Subtasks, and other Work scheduled for completion during
1303 the reporting period which were not completed;
1304 11. Activities for the next reporting period;
1305 12. Issues identified during that reporting period;
1306 13. Issues resolved during that reporting period;
LRS RFP - Attachment A (SOW) Page 47 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
1307 14. Corrections to the prior bi-weekly status report;
1308 15. Meetings scheduled for the next reporting period;
1309 16. Updated risk summary report based on the Risk Management Plan;
1310 and
1311 17. Any other items requested by COUNTY Project Director.
1312 CONTRACTOR Project Director shall attend bi-weekly status meetings
1313 with COUNTY Project Director to review any issues, the status of the
1314 Project Work Plan, and the status of the Risk Management Plan and any
1315 LRS-related risks. CONTRACTOR shall deliver an updated PCD in
1316 COUNTY-specified version of Microsoft Project format and include an
1317 indication of any variance from the current COUNTY-approved Project
1318 Work Plan affecting the project‟s schedule, resources, or impacting the
1319 project‟s critical path. All variances shall be presented to COUNTY
1320 Project Director for approval at the bi-weekly status meeting.
1321 CONTRACTOR shall send an updated copy of the PCD incorporating
1322 only COUNTY-approved variances to COUNTY Project Director for
1323 approval no later than twenty-four (24) hours prior to any subsequent bi-
1324 weekly status meeting. CONTRACTOR shall provide an electronic
1325 version of the updated PCD in the LRS Repository.
1326 During Phase 3 (Operational Phase), COUNTY Project Director, in his
1327 sole discretion, may from time-to-time change the frequency of such status
1328 meetings and status reports.
1329 Starting ninety (90) days after the Effective Date and continuing
1330 throughout the term of the Agreement, CONTRACTOR Project Director
1331 shall prepare monthly status reports, summarizing all project activities for
1332 the preceding month, project progress against all Deliverable due dates,
1333 issues and risks to the DPSS Assistant Director for BCTS and other key
1334 stakeholders. CONTRACTOR Project Director, or his designee as
1335 approved by COUNTY Project Director, shall present a monthly project
LRS RFP - Attachment A (SOW) Page 48 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
1336 status report at a designated meeting of the COUNTY LRS Oversight and
1337 Executive Steering Committee. The first monthly status report shall be due
1338 to COUNTY Project Director ninety (90) days after the Effective Date and
1339 thereafter by the fifth (5th) working day of each month, in a format
1340 approved by COUNTY Project Director.
1341 3.1.3.1 Deliverable 1.3: Ongoing Project Administration.
1342 CONTRACTOR shall provide ongoing project administration to
1343 include:
1344 1. LRS bi-weekly and monthly status reports; and
1345 2. Updates to the PCD, including Project Work Plan and Risk
1346 Management Plan.
1347 3.2 TASK 2: DEVELOPMENT METHODOLOGY AND TECHNICAL
1348 PRACTICES:
1349 CONTRACTOR shall describe the development methodology and technical practices
1350 to be utilized in the design, development, implementation, and operation of the LRS.
1351 CONTRACTOR shall provide its methodology and tools for both design time and run
1352 time governance and management of any resulting LRS processes, policies,
1353 procedures, and services. CONTRACTOR shall perform the following Work in this
1354 Task 2:
1355 1. Establish the IDE according to the requirements in Attachment B (Statement
1356 of Requirements); and
1357 2. Orient CONTRACTOR and COUNTY staff to the SDLC methodology to be
1358 used, the specific tools to be used, and the IDE which provides the
1359 environment for team collaboration, interoperability across all LRS project
1360 tools, and management of all project artifacts.
LRS RFP - Attachment A (SOW) Page 49 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
1361 3.2.1 Subtask 2.1: Establish Integrated Development Environment (IDE).
1362 CONTRACTOR shall establish the IDE, in accordance with the technical
1363 requirements in Attachment B (Statement of Requirements). The IDE shall
1364 support the following:
1365 1. Requirements traceability, tracking, and verification;
1366 2. Tracking of COUNTY-developed and CONTRACTOR-developed
1367 test scenarios, together with the related procedures, including
1368 traceability to the requirements;
1369 3. Language development environments;
1370 4. User interface tools that promote reuse of user interface (UI)
1371 components;
1372 5. Software configuration management (SCM) tools;
1373 6. Tools to manage business logic;
1374 7. Testing, including automated regression testing;
1375 8. Version control on all electronic work products, including both
1376 software, system documentation, and project correspondence and
1377 documentation;
1378 9. Tools to establish and track the contents of the LRS Repository, in
1379 a COUNTY-approved readily retrievable form;
1380 10. Defect tracking;
1381 11. Configuration management; and
1382 12. Version release.
1383 CONTRACTOR shall maintain the LRS Repository, whose contents shall
1384 include:
1385 1. LRS functional, technical, and training requirements, including all
1386 validation and traceability results;
1387 2. Physical and logical data and process models;
LRS RFP - Attachment A (SOW) Page 50 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
1388 3. All metadata;
1389 4. Data dictionary;
1390 5. Project Deliverables;
1391 6. All LRS-related documentation, including a tracking mechanism
1392 for any documentation that must be retained in hardcopy;
1393 7. LRS Application Software Source Code;
1394 8. Detailed design specifications for all screens contained within the
1395 LRS;
1396 9. Audit trails and version control documentation for changes made
1397 to the LRS; and
1398 10. Data conversion strategies and processes.
1399 CONTRACTOR shall be responsible for establishing and maintaining this
1400 environment throughout the term of the Agreement. The IDE shall be
1401 accessible at all times by CONTRACTOR and COUNTY staff, at the
1402 Project Office upon occupancy. Access to the tools within the IDE will be
1403 based on CONTRACTOR and COUNTY staff roles and responsibilities as
1404 established by CONTRACTOR and COUNTY. The IDE shall be available
1405 to COUNTY-specified stakeholders and the IV&V contractor. At
1406 COUNTY Project Director‟s request, from time-to-time during the
1407 Agreement, the contents of the LRS Repository shall be fully transferred
1408 to COUNTY in a COUNTY-approved readily retrievable form.
1409 CONTRACTOR shall document the IDE in Deliverable 2.1 (Integrated
1410 Development Environment Configuration Control Document), including a
1411 detailed description of the actual IDE configuration. Deliverable 2.1
1412 (Integrated Development Environment Configuration Control Document)
1413 shall be provided to COUNTY no later than thirty (30) days after the
1414 Effective Date. The IDE shall be fully operational within ninety (90) days
1415 of the Effective Date.
LRS RFP - Attachment A (SOW) Page 51 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
1416 CONTRACTOR shall provide updates to Deliverable 2.1 (Integrated
1417 Development Environment Configuration Control Document) when
1418 configuration of the IDE is modified or updated, additional tools are
1419 incorporated, procedures are updated, or significant changes occur to the
1420 contents of the IDE as related to the LRS design, development, or
1421 implementation. CONTRACTOR shall transition the LRS Repository to
1422 COUNTY and/or any COUNTY-specified parties at the expiration or
1423 termination of the Agreement.
1424 3.2.1.1 Deliverable 2.1: Integrated Development Environment
1425 Configuration Control Document.
1426 CONTRACTOR shall provide the Integrated Development
1427 Environment Configuration Control Document to include the
1428 following information, indexed and organized for easy reference:
1429 1. A high-level description of the IDE configuration; and
1430 2. A complete description of the IDE to include:
1431 A. All hardware, software, and utilities used in the
1432 IDE, including any custom tools supplied by
1433 CONTRACTOR;
1434 B. Reference list of all supporting IDE technical
1435 documentation;
1436 C. Structure and organization of LRS Repository;
1437 D. IDE operational procedures and security
1438 procedures; and
1439 E. IDE training materials.
1440 3.2.2 Subtask 2.2: Orientation to Project System Development
1441 Methodology, Tools, and Technical Practices.
1442 CONTRACTOR shall orient the Project Team on its SDLC methodology
1443 and how it will be applied to the project. CONTRACTOR shall fully
1444 describe the use of the IDE and any tools to be used as part of the design
LRS RFP - Attachment A (SOW) Page 52 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
1445 and development process. During this orientation, CONTRACTOR will
1446 work with COUNTY to establish the roles, responsibilities, and
1447 expectations for the Project Team.
1448 CONTRACTOR shall describe the basic technical practices that will be
1449 used throughout the project, provide familiarization to the specific tools to
1450 be used to support these practices, and orient the Project Team on the
1451 procedures based on these tools. CONTRACTOR shall specifically
1452 describe its approach to asset management, LRS Repository management,
1453 and configuration management.
1454 3.2.2.1 Deliverable 2.2: System Development Lifecycle Orientation
1455 and Materials.
1456 CONTRACTOR shall conduct orientation for the Project Team.
1457 CONTRACTOR shall provide documentation of the orientation
1458 sessions (e.g., attendance sheet).
1459 CONTRACTOR shall provide COUNTY with all orientation
1460 materials that include:
1461 1. All orientation material for the SDLC methodology,
1462 description of the IDE, and supporting tools, including
1463 presentation materials, descriptive information on the IDE
1464 and tools, and vendor literature for any commercial
1465 products used;
1466 2. All user documentation for the SDLC methodology, IDE,
1467 and supporting tools including User manuals, help files,
1468 checklist, tutorials, and vendor literature for any
1469 commercial products used; and
1470 3. Documentation on technical management practices (to
1471 include asset management, document management, and
1472 configuration/change management), encompassing
1473 procedural materials (i.e., books, checklists) to ensure
LRS RFP - Attachment A (SOW) Page 53 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
1474 compliance by the Project Team in following these
1475 practices, and detailed documentation on how the IDE and
1476 tools are to be used in accomplishing these procedures.
1477 3.3 TASK 3: REQUIREMENTS VERIFICATION AND ANALYSIS:
1478 CONTRACTOR shall perform the following Work during this Task 3:
1479 1. Plan Task 3 with COUNTY and other stakeholders; and
1480 2. Analyze and verify all LRS functional, technical, and training requirements.
1481 3.3.1 Subtask 3.1: Planning for Requirements Verification.
1482 CONTRACTOR, working in conjunction with COUNTY designated
1483 stakeholders, shall plan the schedule for the activities in Task 3 (Requirements
1484 Verification and Analysis). The planning shall include the development of
1485 schedules and locations for the appropriate analysis and meetings with COUNTY
1486 and others approved by COUNTY, as well as identification of the key participants
1487 for each meeting.
1488 3.3.1.1 Deliverable 3.1: Requirements Verification Schedule.
1489 CONTRACTOR shall provide the Requirements Verification Schedule
1490 that describes the proposed number of meetings, names of anticipated
1491 participants, proposed agenda(s), and updates to the Project Work Plan.
1492 The updates to the Project Work Plan will include the detailed activities,
1493 schedule, and resources required for completing Task 3 (Requirements
1494 Verification and Analysis).
1495 3.3.2 Subtask 3.2: Analyze and Verify the LRS Requirements.
1496 CONTRACTOR shall conduct a thorough verification of all functional, technical,
1497 and training requirements. CONTRACTOR shall validate all functional,
1498 technical, and training requirements and verify that all requirements have been
1499 identified. As a result of this Subtask, CONTRACTOR shall establish a complete
1500 set of LRS baseline functional, technical, and training requirements that will serve
LRS RFP - Attachment A (SOW) Page 54 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
1501 as the basis for LRS design and development. CONTRACTOR shall accomplish
1502 this by completing the following steps:
1503 1. Reviewing Attachment B (Statement of Requirements) ;
1504 2. Reviewing pertinent material contained in the Diligence Library;
1505 3. Conducting any indicated clarification sessions with COUNTY staff and
1506 COUNTY-specified key Users of the LRS to ensure a common
1507 understanding of the requirements; and
1508 4. Requesting additional information, as appropriate, to ensure a thorough
1509 understanding of the requirements.
1510 CONTRACTOR shall record all functional, technical, and training requirements
1511 in the requirements traceability and verification tool that is part of the IDE.
1512 CONTRACTOR shall ensure that:
1513 1. All functional, technical, and training requirements will be uniquely
1514 identified in the IDE.
1515 2. Additional documentation, such as clarifications, details, and/or examples
1516 that help more thoroughly define a requirement, shall be attached to the
1517 appropriate requirement(s); and
1518 3. All Requirements Traceability Matrix links between each unique
1519 functional, technical, and training requirement and other related
1520 functional, technical, and training requirements, including Attachment B
1521 (Statement of Requirements), documents (e.g., clarifications or examples),
1522 or other Deliverables, are established and maintained in the IDE.
1523 CONTRACTOR shall prepare Deliverable 3.2.1 (System Requirements
1524 Document (SRD)), summarizing CONTRACTOR analysis and verification of the
1525 functional, technical, and training requirements, including any impacts to the
1526 proposed LRS design concept and its related components prior to initiating
1527 design. This document shall serve as the foundation for future design and
1528 development.
LRS RFP - Attachment A (SOW) Page 55 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
1529 CONTRACTOR shall prepare Deliverable 3.2.2 (Requirements Traceability
1530 Matrix and Report) that includes any unresolved traceability issues. Deliverable
1531 3.2.2 (Requirements Traceability Matrix and Report) shall be used to ensure that
1532 all technical requirements can be clearly traced to the business or functional
1533 requirements that they must support. CONTRACTOR shall use COUNTY
1534 business processes, workflows, terminology and nomenclature wherever possible.
1535 The Requirements Traceability Matrix can also be used to ensure that all proposed
1536 LRS business logic can be traced to the supporting business need or COUNTY
1537 objective. This matrix will be used as a quality assurance tool throughout the LRS
1538 design and development process and shall be updated by CONTRACTOR as
1539 needed for subsequent activities.
1540 3.3.2.1 Deliverable 3.2.1: System Requirements Document (SRD).
1541 CONTRACTOR shall provide a System Requirements Document (SRD)
1542 that shall document the complete set of verified functional, technical, and
1543 training requirements for the LRS, describing in detail what the LRS must
1544 do and other attributes the LRS must have in order to provide and support
1545 all services.
1546 3.3.2.2 Deliverable 3.2.2: Requirements Traceability Matrix and Report.
1547 CONTRACTOR shall provide a Requirements Traceability Matrix and
1548 corresponding report to establish that all links for each functional,
1549 technical, and training requirement, as set forth in Attachment B
1550 (Statement of Requirements), to other supporting requirements, including
1551 Attachment B (Statement of Requirements), documents (e.g., clarifications
1552 or examples), or other Deliverables, have been successfully established in
1553 the IDE. CONTRACTOR shall also indicate any unresolved traceability
1554 issues.
1555 CONTRACTOR shall provide an updated PCD, M&O Services Plan,
1556 M&E Services Plan, and Conversion and Archiving Plans.
LRS RFP - Attachment A (SOW) Page 56 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
1557 3.4 TASK 4: GENERAL DESIGN:
1558 The General Design shall describe the features and functions of the LRS, outlining LRS
1559 behavior as seen by an external observer, and containing the technical information and
1560 data needed for the design. CONTRACTOR shall describe the following LRS
1561 architectures based on Deliverable 3.2.1 (System Requirements Document (SRD)):
1562 hardware and network, software, functional, application, and data. CONTRACTOR shall
1563 document these architectures in Deliverable 4 (General Design Document) that:
1564 1. Ensures that all LRS features and functions are correctly understood before
1565 moving into the LRS detailed design tasks;
1566 2. State any assumptions, limitations, and constraints used in formulating the LRS
1567 architectures;
1568 3. Clearly establishes traceability for each architectural component to requirements
1569 as documented in Deliverable 3.2.1 (System Requirements Document (SRD));
1570 and
1571 4. Clearly and unambiguously provides all the information necessary for the detailed
1572 design of the Baseline Application Software, interfaces, and technical
1573 infrastructure.
1574 The General Design Document shall include specific information about each LRS
1575 architectural component to include:
1576 1. Hardware and network architecture: a high-level description of the computing
1577 and network resources across all LRS processing environments and physical sites,
1578 including connectivity to LAnet/EN;
1579 2. Software architecture: a high-level description of software layers and components
1580 (e.g., operating systems, protocols, database management, languages, utilities,
1581 middleware) and how they interact to implement the functional architecture;
1582 3. Functional architecture: a high-level description of the functionality and
1583 capabilities of the LRS;
LRS RFP - Attachment A (SOW) Page 57 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
1584 4. Application architecture: a high-level description of the organization of the
1585 application into service components, interface management, and security
1586 processing; and
1587 5. Data architecture: a high-level description of the logical design, structure, and
1588 implementation of the data needed for the LRS functionality and operations.
1589 CONTRACTOR will participate with COUNTY at a meeting in a review of the General
1590 Design Document to obtain concurrence between CONTRACTOR and COUNTY on the
1591 contents of the final General Design Document before proceeding to Task 5 (Technical
1592 Infrastructure Planning and Design) and Task 6 (Functional Design).
1593 3.4.1.1 Deliverable 4: General Design Document:
1594 CONTRACTOR shall provide a General Design Document to include:
1595 1. Overview: An overview of the proposed LRS general design;
1596 2. Architectural Component Descriptions: A description of the
1597 LRS in terms of its architectural components, highlighting the most
1598 important features and capabilities of each, to include: hardware
1599 and network architecture, software architecture, functional
1600 architecture, application architecture, and data architecture;
1601 3. General Constraints, Limitations, and Assumptions: Any
1602 constraints or limitations discovered or assumptions made in
1603 specifying the LRS general design. In its design of the LRS,
1604 CONTRACTOR shall utilize existing business processes and
1605 workflows, terminology and nomenclature, and datasets, in order
1606 to mitigate the impact on Users;
1607 4. Security Design: A discussion of the overall LRS security design
1608 in terms of how it is implemented within each architectural
1609 component;
1610 5. Communication Interfaces: A description of how the LRS
1611 Application Software will communicate within itself as a multi-
LRS RFP - Attachment A (SOW) Page 58 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
1612 platform application (e.g., use of messaging and Web services)
1613 among and between the Primary Central Site, Backup Central Site,
1614 Central Print Facility, Backup Central Print Facility and Project
1615 Office and with other applications, including COUNTY desktop
1616 and User environments, email, Internet, and LAnet/EN;
1617 6. External Interfaces: A description of CONTRACTOR interface
1618 design strategy for the required interfaces to external systems;
1619 7. User Interface(s): A description of CONTRACTOR user
1620 interface design strategy, describing compliance with related LRS
1621 functional, technical, and training requirements and usability
1622 features;
1623 8. Performance: A discussion of design considerations that may
1624 impact LRS performance, to include availability, response time,
1625 throughput, data volume, problem complexity, maximum number
1626 of concurrent Users, and peak load; and
1627 9. Additional Design Considerations: A description of any other
1628 characteristics of the LRS design that were not covered in the prior
1629 sections.
1630 CONTRACTOR shall provide an updated PCD, M&O Services Plan,
1631 M&E Services Plan, and Conversion and Archiving Plans.
1632 3.5 TASK 5: TECHNICAL INFRASTRUCTURE PLANNING AND DESIGN:
1633 The technical infrastructure shall be designed and sized to support an n-tier application
1634 that shall deliver LRS services to support the applicant and participant populations in Los
1635 Angeles County. The LRS shall be hosted at the Primary Central Site and Backup Central
1636 Site, accessed via a secure browser-based interface, and shall meet the performance
1637 requirements as set forth in the Agreement.
1638 CONTRACTOR shall perform the following Work in this Task 5:
LRS RFP - Attachment A (SOW) Page 59 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
1639 1. Develop an overall design for the technical infrastructure that details the specific
1640 hardware and software components for each processing environment, interface,
1641 and the locations of the Primary Central Site, Backup Central Site, Central Print
1642 Facility, Backup Central Print Facility, and Project Office;
1643 2. Develop the Facility Management Plan for the Primary Central Site, Backup
1644 Central Site, Central Print Facility, Backup Central Print Facility, and Project
1645 Office;
1646 3. Develop the Information Systems Security Plan that describes how security will
1647 be implemented and administered in accordance with the specifications in the
1648 SRD and the General Design Document;
1649 4. Develop the Network Design Plan that describes how the LRS network design
1650 will interface and interact with COUNTY assets, performance issues, and how the
1651 design will support the LRS requirements for business continuity and disaster
1652 recovery; and
1653 5. Update the Business Continuity/Disaster Recovery Plan that is consistent with
1654 COUNTY business continuity plans.
1655 3.5.1 Subtask 5.1: Design Technical Infrastructure.
1656 CONTRACTOR shall describe all the physical locations of the Central Sites,
1657 Print Facility Sites, Project Office, and the Enterprise Connecting Hardware,
1658 which includes the Gateway, and how each is incorporated into the overall LRS
1659 topology.
1660 CONTRACTOR shall describe the six (6) main processing environments that
1661 shall be used throughout the term of the Agreement. CONTRACTOR shall
1662 demonstrate how the proposed LRS technical infrastructure design will meet all
1663 the performance requirements. CONTRACTOR shall document its technical
1664 design of the six (6) main LRS processing environments to be used for the LRS,
1665 including a description of the changes from one environment to another. The six
1666 (6) main LRS processing environments shall include:
LRS RFP - Attachment A (SOW) Page 60 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
1667 1. Development – an environment for the programming of the application,
1668 used primarily by application programmers.
1669 2. Test – an environment robust enough to support multiple tests
1670 simultaneously. The test environment shall be comprised of multiple sub-
1671 environments, including the ability to change the system date by sub-
1672 environment and parallel test environments for the sole use of COUNTY
1673 for the testing of all modifications and enhancements. Additionally, the
1674 Central Print Facility shall have a test environment uniquely suited to the
1675 testing of printing materials.
1676 3. Staging – an intermediate platform used to move LRS Application
1677 Software and services from the test environment to the production
1678 environment.
1679 4. Production – the fully tested and integrated LRS accessible by Users.
1680 5. Reporting – a copy of the production database to be used for standard and
1681 ad hoc reporting.
1682 6. Training – a separate environment to be used to train Users.
1683 CONTRACTOR shall design the test and training processing environments, so
1684 that they are easily configurable for any special processing needs such as
1685 simulation of conditions in the production environment, inclusion of special tools
1686 for testing or training, or the integration of new technologies for planning and
1687 analysis purposes.
1688 CONTRACTOR shall document how its design for the LRS technical
1689 infrastructure shall guarantee that the Specifications, including all performance
1690 requirements, shall be met at the commencement of LRS implementation during
1691 Phase 1 (Design/Development/Implementation Phase), shall be verified during
1692 Phase 2 (Performance Verification Phase), and shall be maintained throughout
1693 Phase 3 (Operational Phase), including any modifications or enhancements made
1694 to the LRS.
LRS RFP - Attachment A (SOW) Page 61 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
1695 CONTRACTOR shall advise COUNTY as to the configuration of any hardware
1696 and software required at the Local Office Sites to support the LRS.
1697 3.5.1.1 Deliverable 5.1: Technical Infrastructure Design Document.
1698 CONTRACTOR shall provide a Technical Infrastructure Design
1699 Document to include:
1700 1. An overall description of the LRS topology;
1701 2. Specific topology for each LRS processing environment, interface,
1702 and physical location;
1703 3. LRS hardware and software products used;
1704 4. LRS maintenance strategy;
1705 5. Strategy for ensuring that the LRS shall continue to meet
1706 scalability and growth demands throughout the term of the
1707 Agreement;
1708 6. LRS technical refresh strategy that ensures hardware and software
1709 in the various processing environments do not reach end of life
1710 during the term of the Agreement;
1711 7. Storage management standards;
1712 8. System administration and management strategy; and
1713 9. Any special utilities or tools needed to meet the requirements of
1714 the Agreement.
1715 3.5.2 Subtask 5.2: Facility Management Plan.
1716 CONTRACTOR shall establish and manage the following facilities:
1717 1. Primary Central Site and Backup Central Site that host the LRS technical
1718 infrastructure, LRS Application Software, and LRS Data, and support
1719 LRS system administration and management operations;
1720 2. Central Print Facility and Backup Central Print Facility that host the
1721 production print and distribution services required by the LRS; and
LRS RFP - Attachment A (SOW) Page 62 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
1722 3. Project Office.
1723 CONTRACTOR shall prepare Deliverable 5.2 (Facility Management Plan) that
1724 describes the overall physical facility requirements for the Primary Central Site,
1725 Backup Central Site, Central Print Facility, Backup Central Print Facility, and
1726 Project Office. Deliverable 5.2 (Facility Management Plan) shall include:
1727 1. Space planning requirements;
1728 2. Physical security requirements;
1729 3. Access control plans and procedures;
1730 4. Data security plans and procedures; and
1731 5. Physical requirements for business continuity and disaster recovery.
1732 COUNTY reserves the right to visit any CONTRACTOR-operated site with
1733 twenty-four (24) hour notice to CONTRACTOR at any time during the term of
1734 the Agreement. All sites shall continue to comply with the specifications
1735 documented in Deliverable 5.2 (Facility Management Plan) throughout the term
1736 of the Agreement. Any change in site location shall require prior approval of
1737 COUNTY Project Director.
1738 The Central Print Facility shall provide a cost effective means for all labor and
1739 automation involved in the printing, processing and mailing of bulk output from
1740 the LRS, including the automated or manual compilation, insertion, and mailing
1741 of re-determination packets. CONTRACTOR shall ensure that the Central Print
1742 Facility and the Backup Print Facility are scalable facilities with adequate
1743 technology, staff, and physical space to meet production schedule requirements,
1744 as described in Attachment H (Technical Exhibits) and Attachment B (Statement
1745 of Requirements). The Central Print Facility shall provide:
1746 1. Sufficient warehouse space to stock all consumable items necessary to
1747 ensure normal operation for at least one (1) month. Additionally,
1748 sufficient space to store at least four (4) months of redetermination and
1749 recertification packets.
LRS RFP - Attachment A (SOW) Page 63 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
1750 2. Pre-delivery staging area with space for regulation United States Postal
1751 Service (USPS) postal carts adequate to hold a month-end volume of
1752 posted mail in intermediate storage prior to delivery to the United States
1753 Post Office.
1754 3. Hardened and secured storage area for any stock involved in the
1755 production of negotiable instruments (e.g., negotiable warrant stock).
1756 CONTRACTOR shall document how it will meet all Central Print Facility and
1757 Backup Print Facility physical requirements in Deliverable 5.2 (Facility
1758 Management Plan), including a description of all services provided at the Central
1759 Print Facility and the equipment, staff, and supplies used by CONTRACTOR to
1760 provide these services. CONTRACTOR shall provide twenty-four (24) hour
1761 physical security for the Central Print Facility and the Backup Print Facility,
1762 including video surveillance, restrictions on visitor access and control, secure
1763 loading dock, and document shredding.
1764 3.5.2.1 Deliverable 5.2: Facility Management Plan.
1765 CONTRACTOR shall provide the Facility Management Plan that
1766 describes both general and site-specific requirements to include:
1767 1. Location and general description of the Primary Central Site,
1768 Backup Central Site, Central Print Facility, Backup Print Facility,
1769 and Project Office:
1770 A. Key contacts for facility management;
1771 B. Procedures for access control;
1772 C. Requirements for physical security; and
1773 D. Physical data security.
1774 2. Business continuity and disaster recovery plans for the physical
1775 locations of the Primary Central Site, Backup Central Site, Central
1776 Print Facility, Backup Print Facility, and Project Office.
LRS RFP - Attachment A (SOW) Page 64 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
1777 CONTRACTOR shall include a separate appendix for each physical
1778 location of the Primary Central Site, Backup Central Site, Central Print
1779 Facility, Backup Print Facility, and Project Office. Each appendix shall be
1780 structured as a stand-alone document, delineating the above information in
1781 a form that can be used in the management of that specific physical
1782 location.
1783 3.5.3 Subtask 5.3: Develop Information Systems Security Plan.
1784 CONTRACTOR shall provide a security architecture that provides for the careful
1785 and full protection of all clients‟ and others‟ rights to privacy and confidentiality
1786 through the effective internal and external security controls which meet or exceed
1787 all legal requirements, including federal, State, and local laws, rules, regulations,
1788 ordinances, guidelines, directives, policies and procedures. CONTRACTOR shall
1789 develop a security plan concurrent with the development of defining the LRS
1790 processing environments. Varying levels of security shall be documented in
1791 Deliverable 5.3 (Information Systems Security Plan) in accordance with
1792 COUNTY security requirements implemented and administered in accordance
1793 with the specifications in the SRD and the General Design Document. This Work
1794 shall include:
1795 1. Establish security standards for the LRS that are consistent with COUNTY
1796 security requirements (e.g., those documented in the Los Angeles County
1797 Board of Supervisors Policy Manual, such as Policy Number 6.100 et
1798 seq.).
1799 2. Develop and implement a process to monitor LRS security and report
1800 security incidents, including breaches, attacks, and introduction of any
1801 Disabling Devices, on an ongoing basis.
1802 3. Develop an audit process that shall be implemented to provide LRS
1803 security measures that address all COUNTY policies, procedures, and
1804 instructions.
LRS RFP - Attachment A (SOW) Page 65 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
1805 4. Review the network topology, with COUNTY, for end-to-end security of
1806 the LRS.
1807 5. Review the security design with COUNTY and with the development
1808 project staff.
1809 6. Identify network security architecture and/or approach, which provides
1810 single sign-on, minimizes password administration, and optimizes security
1811 of the LRS Data integrity and access.
1812 7. Develop and implement a process for the prevention of any Disabling
1813 Device from being incorporated or introduced into the LRS.
1814 8. Develop and implement a process for the correction of any security
1815 breaches, unplanned interruptions, and data corruption in LRS caused by
1816 any Disabling Device, including escalation and remediation procedures.
1817 9. Develop and implement processes for a Computer Emergency Response
1818 Team (CERT), including CONTRACTOR‟s roles and responsibilities.
1819 10. Perform routine security vulnerability, threat and risk assessments of the
1820 LRS including the technical infrastructure, the LRS Application Software
1821 code, and interfaces.
1822 3.5.3.1 Deliverable 5.3: Information Systems Security Plan.
1823 CONTRACTOR shall provide the Information Systems Security Plan
1824 which shall describe in detail the security strategy. CONTRACTOR shall
1825 include a description of the different levels of security, the processes that
1826 shall ensure LRS security meets COUNTY requirements and the roles and
1827 responsibilities for managing LRS security. In addition to all other
1828 requirements, CONTRACTOR shall specifically comply with COUNTY's
1829 information security policies, standards, guidelines, and procedures.
1830 In this Plan, CONTRACTOR shall include:
1831 1. Roles and responsibilities of CONTRACTOR;
LRS RFP - Attachment A (SOW) Page 66 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
1832 2. Strategies for complying with all legal requirements including
1833 federal, State, and local laws, rules, regulations, ordinances,
1834 guidelines, directives, policies and procedures;
1835 3. Baseline security measures, risk assessments, and continual
1836 monitoring of LRS security;
1837 4. Incident response activities;
1838 5. Security awareness training;
1839 6. Physical security;
1840 7. Hardware security;
1841 8. Software security;
1842 9. Access to all processing environments;
1843 10. User security profiles, audit trails, and transaction sampling;
1844 11. Physical and logical network management and security, access
1845 controls, event management, and reporting;
1846 12. Data security administration, file server security, data structure
1847 integrity, Disabling Device protection, patch management, backup
1848 and recovery, and data encryption; and
1849 13. Internet security, including information movement.
1850 3.5.4 Subtask 5.4: Network Design Plan.
1851 CONTRACTOR shall provide to COUNTY a network design for the LRS,
1852 including the Enterprise Connecting Hardware which includes the Gateway,
1853 taking into account the current infrastructure of LAnet/EN, COUNTY networking
1854 and security standards, and any proposed initiatives that COUNTY has to upgrade
1855 its network and services. CONTRACTOR shall perform detailed modeling to
1856 verify network capacity requirements and ensure that the proposed network
1857 design contains adequate bandwidth and can meet response time performance
1858 based on known parameters such as known or assumed network latency.
1859 CONTRACTOR shall ensure that any backup system and network configuration
LRS RFP - Attachment A (SOW) Page 67 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
1860 are sized to accommodate the production environment in the event of LRS failure
1861 at the Primary Central Site or Central Print Facility. CONTRACTOR shall
1862 document the results of this analysis and its supporting recommendations.
1863 CONTRACTOR shall provide a network design that shall meet redundancy and
1864 failover such that if the Gateway, the Primary Central Site and/or Central Print
1865 Facility become unavailable, the LRS shall immediately re-route all
1866 communications to the Backup Central Site and/or Backup Print Facility as
1867 appropriate. CONTRACTOR shall work with COUNTY to develop procedures
1868 for failover if the failure occurs on COUNTY side of the Gateway.
1869 CONTRACTOR shall document all related design, analysis, plans, and
1870 recommendations as required below in Deliverable 5.4 (Network Design Plan).
1871 CONTRACTOR shall document its proposed solution(s) for secure LRS access
1872 from locations and/or through services deemed by COUNTY as appropriate in
1873 satisfying the functional requirements, including those specified in Attachment B
1874 (Statement of Requirements). This may include any of the following items, or
1875 other items as proposed by CONTRACTOR:
1876 1. Browser-based access from COUNTY workstations, laptops, or other
1877 devices;
1878 2. Browser-based access from COUNTY maintained public kiosks;
1879 3. Browser-based access from resources available to private citizens;
1880 4. Access through other communications software, such as email;
1881 5. Access via third party reporting or analysis tools; and
1882 6. Automated interfaces with other electronic systems.
1883 3.5.4.1 Deliverable 5.4: Network Design Plan.
1884 CONTRACTOR shall provide a Network Design Plan that includes a
1885 description of the following:
LRS RFP - Attachment A (SOW) Page 68 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
1886 1. The LRS network design, including the Enterprise Connecting
1887 Hardware, which includes the Gateway, and interfaces;
1888 2. The LRS network security infrastructure;
1889 3. The network management approach established by
1890 CONTRACTOR, which includes participation from the COUNTY;
1891 4. How CONTRACTOR will meet COUNTY network-related
1892 performance requirements;
1893 5. How the proposed network design will support the Business
1894 Continuity/Disaster Recovery Plan; and
1895 6. Assessment of the impact of the LRS on LAnet/EN, including
1896 bandwidth and security, and solution for minimizing impact of the
1897 LRS on LAnet/EN.
1898 CONTRACTOR shall provide an updated PCD, M&O Services Plan,
1899 M&E Services Plan, and Conversion and Archiving Plans.
1900 3.6 TASK 6: FUNCTIONAL DESIGN:
1901 CONTRACTOR shall perform the following Work in this Task 6:
1902 1. Develop and document the functional design of the Baseline Application
1903 Software; and
1904 2. Conduct a meeting for presentation to COUNTY of the LRS functional design.
1905 3.6.1 Subtask 6.1: Develop the Functional Design.
1906 CONTRACTOR shall develop the functional design of the Baseline Application
1907 Software based on both Deliverable 3.2.1 (System Requirements Document
1908 (SRD)) and Deliverable 4 (General Design Document). The functional design will
1909 include the requisite data structures, data flows, business logic, user interface
1910 design, interfaces, and algorithms needed for the Baseline Application Software.
1911 CONTRACTOR shall document the elements of the functional design using the
1912 tools within the IDE, such as process models, data models (with the ability to
LRS RFP - Attachment A (SOW) Page 69 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
1913 translate from the logical data model to the appropriate physical model), use case
1914 analysis, and pseudo code. CONTRACTOR shall develop models that achieve the
1915 functional requirements while describing key constraints, such as performance
1916 goals, performance requirements, and infrastructure concerns. CONTRACTOR
1917 shall:
1918 1. Describe all functional components/modules of the Baseline Application
1919 Software, describing how each component/module will be structured and
1920 what functionality will be included in that component/module.
1921 2. Design the user interface to include specific User controls, layout for
1922 major screens, navigation flow, and expected content for each screen,
1923 input validation, and data protection.
1924 3. Define the LRS business rules, including formulas and algorithms not
1925 documented in the SRD.
1926 4. Document the LRS logical data model.
1927 5. Document security design for the LRS Application Software, including
1928 role- and assignment-based access control.
1929 6. Define appropriate scenarios (defined through process maps, use cases, or
1930 prototyping).
1931 7. Design each interface specified in the SRD, including message structure,
1932 protocols, and communication pathways.
1933 8. Provide functional design traceability to verified requirements.
1934 CONTRACTOR shall document the LRS functional design in Deliverable 6.1
1935 (Functional Design Document (FDD)). This document shall serve as the detailed
1936 functional specification for the LRS design and shall be updated, as appropriate,
1937 throughout the term of the Agreement, as a part of Management and Operations
1938 Services.
LRS RFP - Attachment A (SOW) Page 70 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
1939 3.6.1.1 Deliverable 6.1: Functional Design Document (FDD).
1940 CONTRACTOR shall provide a Functional Design Document (FDD) to
1941 include:
1942 1. High-level summary of the LRS design including a module /
1943 component decomposition chart and a functional description of
1944 each module.
1945 2. Detailed design for each component / module to include:
1946 A. Name and description;
1947 B. Function;
1948 C. Process (algorithm);
1949 D. Presentation if component / module requires;
1950 E. Interfaces; and
1951 F. Data.
1952 3. Description of the user interface to include specific User controls,
1953 layout for major screens, navigation flow, and expected content for
1954 each screen, input validation, and data protection.
1955 4. Baseline Application Software design to include the business rules
1956 and the LRS logical data model.
1957 5. Formulas and algorithms not documented in the SRD.
1958 6. Description of the LRS security design.
1959 7. Documentation of scenarios.
1960 8. Document the design of each interface contained in the SRD.
1961 9. Provide updated Requirements Traceability Matrix.
1962 3.6.2 Subtask 6.2: Functional Design Presentation.
1963 Prior to the completion of Task 6 (Functional Design), CONTRACTOR shall
1964 make a presentation to COUNTY, including the COUNTY LRS Oversight and
1965 Executive Steering Committee at a meeting, where CONTRACTOR shall
1966 summarize the functional design, based on Deliverable 6.1 (Functional Design
LRS RFP - Attachment A (SOW) Page 71 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
1967 Document (FDD)). CONTRACTOR shall prepare all supporting technical
1968 materials, documentation, and LRS-generated output and provide any appropriate
1969 walkthroughs and/or demonstration of LRS capability. During this presentation,
1970 CONTRACTOR shall verify to COUNTY that the LRS functional design
1971 demonstrates full traceability to verified requirements.
1972 3.6.2.1 Deliverable 6.2: Functional Design Presentation Report.
1973 CONTRACTOR shall provide a Functional Design Presentation Report
1974 that includes all technical materials, documentation, and LRS-generated
1975 output. In the report, CONTRACTOR shall include:
1976 1. Summary of Task 6 (Functional Design) Work, results, and
1977 outcomes;
1978 2. Verification that the LRS functional design demonstrates full
1979 traceability to verified requirements;
1980 3. Updated Requirements Traceability Matrix; and
1981 4. Agenda, minutes, and supporting documentation from LRS
1982 Functional Design Presentation.
1983 CONTRACTOR shall provide an updated PCD, M&O Services Plan,
1984 M&E Services Plan, and Conversion and Archiving Plans.
1985 3.7 TASK 7: TECHNICAL INFRASTRUCTURE DEPLOYMENT:
1986 CONTRACTOR shall perform the following Work in this Task 7:
1987 1. Identify, acquire, configure, and install all software and hardware assets that are
1988 part of the LRS technical infrastructure;
1989 2. Document system administration procedures for the operation of the deployed
1990 LRS technical infrastructure; and,
1991 3. Deploy the Primary Central Site, Backup Central Site, Central Print Facility,
1992 Backup Print Facility, and Project Office, including the Enterprise Connecting
1993 Hardware, according to a COUNTY-approved schedule, establish connectivity
LRS RFP - Attachment A (SOW) Page 72 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
1994 among and between all sites, and demonstrate that the technical infrastructure is
1995 ready and able to support the LRS Application Software.
1996 3.7.1 Subtask 7.1: Acquire and Configure Technical Infrastructure Assets.
1997 CONTRACTOR shall identify all software and hardware assets, organized by the
1998 physical locations of the Primary Central Site, Backup Central Site, Central Print
1999 Facility, Backup Print Facility, and Project Office, including the Enterprise
2000 Connecting Hardware, needed to support the LRS Application Software and meet
2001 performance requirements designated by COUNTY. CONTRACTOR shall fully
2002 describe the configuration for each software and hardware asset in Deliverable 7.1
2003 (Technical Infrastructure Asset Configuration Report), identifying the assets used
2004 in each such physical location. CONTRACTOR shall install and configure
2005 hardware for all environments, including any related software (e.g., operating
2006 software, etc.).
2007 3.7.1.1 Deliverable 7.1: Technical Infrastructure Asset Configuration
2008 Report.
2009 CONTRACTOR shall prepare the Technical Infrastructure Asset
2010 Configuration Report to include the following:
2011 1. Servers: Detailed description of all servers, operating systems,
2012 middleware, database management, and other utility software
2013 required for each processing environment. The specification shall
2014 include high availability, redundancy, and disaster recovery
2015 capabilities.
2016 2. Workstations: Detailed description of all desktops and laptops,
2017 including operating systems, application software, and utility
2018 software, used in each processing environment. This does not
2019 include COUNTY workstations.
2020 3. Network: Detailed description of how the LRS shall be integrated
2021 with LAnet/EN, including domain name service (DNS), messaging
2022 and email, and others as indicated by COUNTY.
LRS RFP - Attachment A (SOW) Page 73 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
2023 4. Storage: Detailed description of storage configuration, including
2024 considerations for high availability, redundancy, and disaster
2025 recovery capabilities.
2026 5. Peripherals: Detailed description of all CONTRACTOR-
2027 maintained output devices, such as printers, and input devices,
2028 such as scanners, as well as any other peripherals required by
2029 COUNTY. This shall include all specialized production equipment
2030 required within the Central Print Facility and Backup Print
2031 Facility.
2032 3.7.2 Subtask 7.2: Document Technical Infrastructure System Administration
2033 Procedures.
2034 CONTRACTOR shall provide Deliverable 7.2 (Technical Infrastructure System
2035 Administration Procedures) that includes roles and responsibilities, specific
2036 procedures, frequency with which activities will be performed, and best practices
2037 to be used in the operation of the deployed LRS technical infrastructure.
2038 CONTRACTOR shall include, without limitation:
2039 1. Data backup, archiving and file restoration processes.
2040 2. Asset and configuration management within each of the Primary Central
2041 Site, Backup Central Site, Central Print Facility, Backup Print Facility,
2042 and Project Office sites, including the Enterprise Connecting Hardware.
2043 3. Monitoring of LRS activity (e.g., event logs), identification of abnormal
2044 activity, and alerting of appropriate staff for corrective action.
2045 4. Update and patch management procedures.
2046 5. Ability to restore the last known stable configuration/state for the LRS in
2047 the least disruptive fashion to its Users.
2048 6. Storage management procedures, such as the monitoring of User storage
2049 quotas.
LRS RFP - Attachment A (SOW) Page 74 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
2050 7. Data management and administration procedures, including procedures to
2051 ensure data integrity and minimize data corruption from data transferred
2052 into the application.
2053 8. Specific procedures for protection of physical assets, including authorized
2054 access to backups of LRS Application Software and LRS Data in the case
2055 of an emergency or disaster.
2056 9. Security procedures that support COUNTY security policies and User
2057 authorization practices.
2058 CONTRACTOR shall provide COUNTY all supporting documentation supplied
2059 by the hardware and Commercially Available Software vendors.
2060 3.7.2.1 Deliverable 7.2: Technical Infrastructure System Administration
2061 Procedures.
2062 CONTRACTOR shall provide the Technical Infrastructure System
2063 Administration Procedures that describe the activities required for the
2064 operation of the deployed LRS infrastructure, to include:
2065 1. Backup and recovery procedures;
2066 2. LRS configuration management;
2067 3. System monitoring, management, and alerting activities;
2068 4. Update and patch management procedures;
2069 5. System configuration restoration;
2070 6. Storage management;
2071 7. Data management and administration activities;
2072 8. Physical asset protection; and
2073 9. Security procedures.
2074 CONTRACTOR shall provide all vendor-supplied documentation that
2075 reflects the hardware and Commercially Available Software products
2076 incorporated in the LRS technical infrastructure.
LRS RFP - Attachment A (SOW) Page 75 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
2077 3.7.3 Subtask 7.3: Integrate and Demonstrate LRS Connectivity.
2078 CONTRACTOR shall integrate all LRS technical infrastructure components. As
2079 defined in Subtask 5.1 (Design Technical Infrastructure), CONTRACTOR shall
2080 establish appropriate connectivity among and between the Primary Central Site,
2081 Backup Central Site, Central Print Facility, Backup Print Facility, and Project
2082 Office, and the LAnet/EN at the Gateway. Appropriate connectivity includes:
2083 1. Protected access to all processing environments by a User, according to
2084 his/her authorization;
2085 2. Response times in accordance with all performance requirements included
2086 in the Agreement; and
2087 3. Interoperability with COUNTY designated network services (e.g., e-mail,
2088 intrusion detection).
2089 CONTRACTOR shall provide, manage, operate, and support network resources
2090 and connections, including the Enterprise Connecting Hardware, among and
2091 between CONTRACTOR-operated locations to include the Primary Central Site,
2092 Backup Central Site, Central Print Facility, Backup Print Facility, and Project
2093 Office. CONTRACTOR shall provide, manage, operate, and support a secure
2094 Gateway to join these locations to the LAnet/EN.
2095 CONTRACTOR shall demonstrate, including the use of tools, to the satisfaction
2096 of COUNTY, the following:
2097 1. Connectivity – CONTRACTOR shall demonstrate that a browser-based
2098 device (e.g., workstation, laptop, or personal digital assistant) can
2099 successfully connect to all processing environments, the hardware within
2100 each environment performs as required for LRS operation (e.g., printers,
2101 servers), and the software and database services running on the hardware
2102 which the LRS Application Software will require from a COUNTY-
2103 specified location. CONTRACTOR shall base its demonstration on
2104 procedures that will be used during Task 12 (Pilot), Task 13 (Countywide
LRS RFP - Attachment A (SOW) Page 76 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
2105 Implementation), and whenever COUNTY requires CONTRACTOR to
2106 test and confirm connectivity from a Local Office Site to the LRS.
2107 2. Response Times – CONTRACTOR shall demonstrate that a browser-
2108 based device exhibits adequate response times, given any known latencies
2109 or delays in the CONTRACTOR or COUNTY infrastructure, to ensure the
2110 LRS shall meet all performance requirements in the Agreement.
2111 CONTRACTOR shall ensure that each response time measure includes
2112 the LRS Application Software, and data layers in the LRS architecture as
2113 part of the measure and that, for demonstration purposes, a set of
2114 transactions that will be representative of operational LRS transactions
2115 (e.g., size, frequency) shall be used. CONTRACTOR shall base its
2116 demonstration on tools and procedures that will be used to measure
2117 response times when the LRS is fully operational.
2118 3. Availability – CONTRACTOR shall demonstrate that the LRS technical
2119 infrastructure shall meet all performance requirements in the Agreement.
2120 CONTRACTOR shall base its demonstration on tools and procedures that
2121 will be used to measure availability when the LRS is fully operational.
2122 4. Business Continuity/Disaster Recovery – CONTRACTOR shall
2123 demonstrate the backup and restoration of the LRS and LRS Data from
2124 backup, the ability to the switch from the Primary Central Site to Backup
2125 Central Site and the Central Print Facility to the Backup Print Facility.
2126 CONTRACTOR shall conduct this demonstration using plans, procedures,
2127 and tools that will be used for disaster recovery when the LRS is
2128 operational.
2129 5. Central Print Facility – CONTRACTOR shall demonstrate, either
2130 through COUNTY inspection of the proposed design or actual print
2131 volumes generated by the proposed facility, that the Central Print Facility
2132 shall meet all output volumes and retention capacity.
LRS RFP - Attachment A (SOW) Page 77 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
2133 6. Security – CONTRACTOR shall demonstrate the ability to meet
2134 COUNTY network and infrastructure related security requirements, such
2135 as Role-Based Access Control, auditing, and LRS monitoring.
2136 CONTRACTOR shall demonstrate all plans, procedures, and tools used
2137 for Security Management. CONTRACTOR shall provide a self-
2138 assessment of the state of the LRS security architecture, including a
2139 security risk assessment, vulnerability scan, and penetration test.
2140 COUNTY reserves the right to verify CONTRACTOR self-assessment
2141 using an independent third party.
2142 7. Tools, Documentation, and Procedures for Administration and
2143 Management – CONTRACTOR shall demonstrate that the LRS is
2144 correctly configured for remote administration and management and that
2145 the delivered system administration plans and procedures are in
2146 conformance with the actual practices. All remote access to the LRS shall
2147 require approval by COUNTY Project Director. CONTRACTOR shall
2148 provide training to COUNTY-specified staff so that COUNTY can verify,
2149 during the demonstration of operational capabilities, the completeness of
2150 tools, documentation, and procedures that COUNTY will use when the
2151 LRS is operational.
2152 CONTRACTOR shall document the results of the demonstration for the LRS
2153 technical infrastructure in Deliverable 7.3 (Technical Infrastructure Review and
2154 Acceptance Document).
2155 3.7.3.1 Deliverable 7.3: Technical Infrastructure Review and Acceptance
2156 Document.
2157 CONTRACTOR shall provide the Technical Infrastructure Review and
2158 Acceptance Document which shall document the results of Subtask 7.3
2159 (Integrate and Demonstrate LRS Connectivity), verifying that the LRS
2160 technical infrastructure performs according to the Specifications.
LRS RFP - Attachment A (SOW) Page 78 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
2161 CONTRACTOR shall provide an updated PCD, M&O Services Plan,
2162 M&E Services Plan, Conversion and Archiving Plans, and Technical
2163 Infrastructure Design Document.
2164 3.8 TASK 8: BASELINE APPLICATION SOFTWARE AND CONVERSION AND
2165 ARCHIVING TOOLS:
2166 CONTRACTOR shall perform all Work to provide, design, develop, test, and validate the
2167 Baseline Application Software components/modules in conjunction with conversion and
2168 archiving software programs/tools. The Baseline Application Software components shall
2169 include the application as well as utilities developed for reporting, interfaces, and
2170 conversion and archiving of DPSS Systems data, DCFS Systems data, and other legacy
2171 data. All development efforts in this Task shall be based on Deliverable 1.2.3
2172 (Conversion and Archiving Plans) and Deliverable 6.1 (Functional Design Document
2173 (FDD)) as approved by COUNTY.
2174 CONTRACTOR shall perform the following Work during this Task 8:
2175 1. Prepare Deliverable 8.1 (Baseline Application Software Development Plan
2176 (SDP));
2177 2. Conduct software development reviews;
2178 3. Establish system development standards that will apply to the build, unit test, and
2179 validation processes in this Task 8;
2180 4. Build the software components/modules, using secure coding methodologies and
2181 techniques, based on the FDD;
2182 5. Develop, test, and execute the conversion and archiving software programs/tools
2183 in accordance with Attachment B (Statement of Requirements);
2184 6. Perform unit test, including the use of converted legacy data, on each software
2185 component/module to ensure that the component/module performs to the
2186 functional, technical, and training specifications established during design,
2187 including the FDD;
2188 7. Validate conversion and archiving, and unit test results; and
LRS RFP - Attachment A (SOW) Page 79 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
2189 8. Document, build, and test all LRS interfaces to external systems.
2190 3.8.1 Subtask 8.1: Prepare Baseline Application Software Development Plan.
2191 CONTRACTOR shall prepare Deliverable 8.1 (Baseline Application Software
2192 Development Plan (SDP)) that describes how the Baseline Application Software
2193 will be designed, built, documented, tested, and integrated. Based on the SDP,
2194 CONTRACTOR shall provide detailed updates to the Project Work Plan
2195 reflecting the specific schedule and resource requirements for Task 8 (Baseline
2196 Application Software and Conversion and Archiving Tools).
2197 3.8.1.1 Deliverable 8.1: Baseline Application Software Development Plan
2198 (SDP).
2199 CONTRACTOR shall provide the Baseline Application Software
2200 Development Plan which shall include:
2201 1. Project Organization: CONTRACTOR shall identify the roles
2202 and responsibilities for the software development portion of the
2203 LRS Project. CONTRACTOR shall indicate how this portion of
2204 the LRS Project will be managed and controlled and what
2205 procedures will be used for tracking and reporting progress.
2206 2. Project Assumptions and Potential Risks: CONTRACTOR
2207 shall document all key assumptions, risks, and plans for mitigation
2208 that exist at the initiation of all Baseline Application Software
2209 design, development, and testing activities. CONTRACTOR shall
2210 track these assumptions and potential risks on a bi-weekly basis.
2211 3. Schedule: CONTRACTOR shall provide a detailed plan for Task
2212 8 (Baseline Application Software and Conversion and Archiving
2213 Tools), integrated and consistent with the Project Work Plan,
2214 which describes the activities, schedule, and resources for Baseline
2215 Application Software development, including any
2216 CONTRACTOR-proposed milestones, status meetings, software
LRS RFP - Attachment A (SOW) Page 80 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
2217 development reviews, and documentation preparation. Updates to
2218 this schedule shall be reflected in the Project Work Plan.
2219 4. Baseline Application Software Design and Control Plan:
2220 CONTRACTOR shall describe the following:
2221 A. Configuration management: CONTRACTOR shall
2222 describe how multiple development builds of the Baseline
2223 Application Software are tracked to avoid confusion.
2224 B. Release control: CONTRACTOR shall describe its
2225 criteria for releasing Baseline Application Software.
2226 CONTRACTOR shall include a description of how the
2227 Baseline Application Software meets requirements
2228 (validation) and works properly (verification).
2229 C. Test process: CONTRACTOR shall describe the
2230 methodology for testing the Baseline Application Software.
2231 D. Deficiency tracking: CONTRACTOR shall describe how
2232 CONTRACTOR tracks and resolves Baseline Application
2233 Software Deficiencies.
2234 5. Test Strategy: CONTRACTOR shall document the strategy for
2235 system testing, including the following:
2236 A. Testing Approach: CONTRACTOR shall describe its
2237 approach for planning and executing testing, both
2238 incrementally during development and for the entire
2239 product before delivery to COUNTY. CONTRACTOR
2240 shall describe test objectives and responsibilities for all
2241 testing levels, including testing of modules, unit testing,
2242 system testing, integration testing, automated regression
2243 testing, and User Acceptance Testing (UAT), and shall
2244 describe the scope and guiding principles for the testing
LRS RFP - Attachment A (SOW) Page 81 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
2245 effort, and the proposed policy for resolving conflicts that
2246 arise during the testing process.
2247 B. Testing tasks to be performed: CONTRACTOR shall
2248 describe how each major group of software features will be
2249 tested and the major testing activities, techniques, and
2250 testing tools to be used. CONTRACTOR shall include:, (i)
2251 configuration of the LRS test environment; (ii) test
2252 equipment procurement and setup; (iii) unit test procedures;
2253 (iv) test scenario/ script creation; and (v) integration
2254 testing. CONTRACTOR shall propose the responsible
2255 individuals or organizations and its responsibilities.
2256 CONTRACTOR shall document the general rules for
2257 software acceptance.
2258 C. Testing schedule: CONTRACTOR shall include all
2259 proposed tasks and major testing milestones, including start
2260 and end of testing of modules, unit testing, system testing,
2261 integration testing, system builds, test script creation,
2262 automated regression testing, and UAT. CONTRACTOR
2263 shall also integrate these dates with the schedule in the
2264 Project Work Plan.
2265 3.8.2 Subtask 8.2: Baseline Application Software Development Reviews.
2266 CONTRACTOR shall conduct regularly scheduled Baseline Application Software
2267 development reviews at meetings with COUNTY, as described in Deliverable 8.1
2268 (Baseline Application Software Development Plan (SDP)), to ensure that
2269 development is proceeding in accordance with the FDD and Project Work Plan
2270 and that any issues are identified and resolved in a timely fashion.
2271 CONTRACTOR shall provide an agenda at least one (1) week prior to each
2272 review including type of review, goals and objectives, detailed description of the
2273 event, and any pass criteria (if applicable). CONTRACTOR shall document the
LRS RFP - Attachment A (SOW) Page 82 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
2274 proceedings of each review in Deliverable 8.2 (Baseline Application Software
2275 Development Review Report) within one (1) week following a Baseline
2276 Application Software development review. CONTRACTOR shall also update the
2277 Project Work Plan to reflect any changes to Task 8 (Baseline Application
2278 Software and Conversion and Archiving Tools) activities or schedule.
2279 3.8.2.1 Deliverable 8.2: Baseline Application Software Development Review
2280 Report.
2281 CONTRACTOR shall provide the Baseline Application Software
2282 Development Review Report which shall document the following for each
2283 Baseline Application Software review, including:
2284 1. Date/time of the meeting;
2285 2. Attendees;
2286 3. Location;
2287 4. Agenda items;
2288 5. Minutes;
2289 6. Issues;
2290 7. Resolutions;
2291 8. Major outcomes from the review; and
2292 9. Action items and assignments.
2293 3.8.3 Subtask 8.3: Document LRS Application Software SDLC Standards.
2294 CONTRACTOR shall conduct a review of its existing System Development
2295 Lifecycle (SDLC) standards for LRS Application Software development
2296 specifically as they apply to the build, test, and validation Work of the LRS
2297 Project. CONTRACTOR shall indicate how SDLC standards will result in code
2298 that is self-documenting, clearly organized, and easy to maintain.
2299 CONTRACTOR shall assess whether any changes are needed to these standards
2300 in light of the Baseline Application Software detailed design. CONTRACTOR
2301 shall detail the various SDLC standards to be applied to LRS Application
LRS RFP - Attachment A (SOW) Page 83 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
2302 Software development, customization, and integration activities, and adhered to
2303 throughout the term of the Agreement in Deliverable 8.3 (LRS Application
2304 Software SDLC Standards).
2305 3.8.3.1 Deliverable 8.3: LRS Application Software SDLC Standards.
2306 CONTRACTOR shall provide LRS Application Software Development
2307 SDLC Standards which shall incorporate CONTRACTOR and COUNTY
2308 development standards to include: naming conventions, coding standards,
2309 internal documentation standards, user interface standards, and style
2310 conventions that shall be used by CONTRACTOR.
2311 3.8.4 Subtask 8.4: Build Baseline Application Software Components/Modules and
2312 Conversion and Archiving Software Programs/Tools.
2313 CONTRACTOR shall develop the Source Code and Object Code for all Baseline
2314 Application Software components/modules and conversion and archiving
2315 software programs/tools in accordance with Deliverable 6.1 (Functional Design
2316 Document (FDD)). As part of Deliverable 8.4 (Baseline Application Software
2317 Components/Modules and Conversion and Archiving Software Programs/Tools),
2318 CONTRACTOR shall document each Baseline Application Software
2319 component/module and conversion and archiving software programs/tools, any
2320 associated documentation, and any additional information used to support unit
2321 test, validation, or quality assurance activities. CONTRACTOR shall place the
2322 resulting Baseline Application Software component/module and conversion and
2323 archiving software programs/tools in the LRS Repository with appropriate access
2324 permissions and configuration management rules applied.
2325 CONTRACTOR shall develop preliminary documentation for Baseline
2326 Application Software components/modules and conversion and archiving
2327 software programs/tools. This documentation shall include „solved example
2328 problems‟ that will also serve as test cases to help identify and isolate defects. In
2329 each „solved example problem‟, a set of specified inputs will produce a set of
2330 known outputs or responses from the software. CONTRACTOR shall ensure that
LRS RFP - Attachment A (SOW) Page 84 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
2331 the set of „solved example problems‟ cover the core functions of each Baseline
2332 Application Software component/module and conversion and archiving software
2333 programs/tools.
2334 3.8.4.1 Deliverable 8.4: Baseline Application Software Components/Modules
2335 and Conversion and Archiving Software Programs/Tools.
2336 CONTRACTOR shall provide Baseline Application Software
2337 components/modules and conversion and archiving software
2338 programs/tools, which shall include:
2339 1. Source Code and Object Code;
2340 2. Associated Documentation; and
2341 3. Additional information used to support unit test, validation, or
2342 quality assurance activities.
2343 3.8.5 Subtask 8.5: Unit Testing.
2344 CONTRACTOR shall successfully complete unit testing for each Baseline
2345 Application Software component/module and each conversion and archiving
2346 software program/tool prior to Subtask 8.6 (Validation). User interface standards
2347 shall be met, including usability. The components/modules/programs/tools
2348 functions shall work as expected, and the presentation, business logic, security,
2349 and data layers shall perform the specific function as designed in accordance with
2350 the FDD.
2351 For unit testing, CONTRACTOR shall develop Deliverable 8.5.1 (Unit Test
2352 Template), a standard template that incorporates and documents all aspects of unit
2353 testing for a given Baseline Application Software component/module and given
2354 conversion and archiving software program/tool, including planning, procedures,
2355 checklists, and „solved problem examples‟ as described in Subtask 8.4 (Build
2356 Baseline Application Software Components/Modules and Conversion and
2357 Archiving Software Programs/Tools), test execution, and capture of test results.
2358 This template shall require COUNTY Project Director approval prior to its
2359 subsequent use in unit testing.
LRS RFP - Attachment A (SOW) Page 85 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
2360 CONTRACTOR shall perform unit testing on all Baseline Application Software
2361 and conversion and archiving software programs/tools. CONTRACTOR shall use
2362 Deliverable 8.5.1 (Unit Test Template) as the basis for documenting the test
2363 details for a specific Baseline Application Software component/module and
2364 specific conversion and archiving software program/tool, the test procedures, and
2365 the test results. The resulting document will be Deliverable 8.5.2 (Unit Test
2366 Procedures and Results Report).
2367 CONTRACTOR shall store the resulting document in the LRS Repository, linked
2368 with the Baseline Application Software component/module and the conversion
2369 and archiving software program/tool it represents, and allow an IDE User to
2370 access the tailored document and any test results it contains along with access to
2371 the corresponding Baseline Application Software component/module and the
2372 conversion and archiving software program/tool.
2373 3.8.5.1 Deliverable 8.5.1: Unit Test Template.
2374 CONTRACTOR shall provide a Unit Test Template that incorporates all
2375 key aspects of Baseline Application Software component/module and
2376 conversion and archiving software program/tool unit testing as defined in
2377 Subtask 8.5 (Unit Testing) above.
2378 3.8.5.2 Deliverable 8.5.2: Unit Test Procedures and Results Report.
2379 CONTRACTOR shall provide Unit Test Procedures and Results Report,
2380 which shall detail the unit test procedures and results, including usability,
2381 for each specific Baseline Application Software component/module and
2382 each specific conversion and archiving software program/tool.
2383 3.8.6 Subtask 8.6: Validation.
2384 When CONTRACTOR has completed unit testing on a Baseline Application
2385 Software component/module and a conversion and archiving software
2386 program/tool, CONTRACTOR shall compare the actual results of the unit testing
2387 against the expected results that were identified before any testing was performed.
2388 CONTRACTOR shall determine what corrections, if any, are required in the
LRS RFP - Attachment A (SOW) Page 86 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
2389 Baseline Application Software component/module and the conversion and
2390 archiving software program/tool and initiate another set of build, test, and validate
2391 activities for that component/module/program/tool as needed.
2392 Upon successful validation, CONTRACTOR Project Director shall certify in
2393 writing that the Baseline Application Software component/module and the
2394 conversion and archiving software program/tool is ready for release to Task 9
2395 (Testing). CONTRACTOR shall record disposition of the unit test results and
2396 validation against LRS requirements for such
2397 components/modules/programs/tools in Deliverable 8.6 (Unit Test and Validation
2398 Results Report).
2399 3.8.6.1 Deliverable 8.6: Unit Test and Validation Results Report.
2400 CONTRACTOR shall provide Unit Test and Validation Results Report for
2401 each Baseline Application Software component/module and each
2402 conversion and archiving software program/tool indicating that the unit
2403 test results have been successfully validated against LRS requirements for
2404 such component/module/program/tool and that such
2405 component/module/program/tool has been approved by CONTRACTOR
2406 Project Director as tested for release to Task 9 (Testing).
2407 3.8.7 Subtask 8.7: Interface Development.
2408 For each interface, CONTRACTOR shall develop Deliverable 8.7.1 (Interface
2409 Control Documents (ICD)) that defines and specifies the interface.
2410 CONTRACTOR shall work with COUNTY and external interface entities in the
2411 development of the interfaces. CONTRACTOR shall implement each interface
2412 between the LRS and each external system in accordance with the ICD for that
2413 interface.
2414 CONTRACTOR shall determine the qualification requirements that each interface
2415 must meet and incorporate these requirements into an interface test procedure that
2416 exercises all aspects of the interface, including any required data processing.
2417 CONTRACTOR may propose a testing method that emulates the behavior of the
LRS RFP - Attachment A (SOW) Page 87 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
2418 external system if there is difficulty in obtaining permission for a „live‟ test in
2419 early stages of development. CONTRACTOR proposed approach to testing any
2420 interface shall require COUNTY Project Director approval prior to the conduct of
2421 the actual test.
2422 CONTRACTOR shall present the test approach, execute the test, and provide the
2423 test results to COUNTY in Deliverable 8.7.2 (Interface Test Procedures and
2424 Results Report). The results of the interface test(s) shall require COUNTY Project
2425 Director approval prior to placing the interface in use within the production
2426 environment. If available, CONTRACTOR shall provide any additional
2427 documentation, such as system administration manuals, related to the external
2428 system and its interface to the LRS as Deliverable 8.7.3 (Interface
2429 Documentation).
2430 3.8.7.1 Deliverable 8.7.1: Interface Control Documents (ICD).
2431 For each interface, CONTRACTOR shall provide an Interface Control
2432 Document (ICD). The ICD will describe the concept of operations for the
2433 interface, define the message structure and protocols that govern the
2434 exchange of data, and identifies the communication paths along which the
2435 data is expected to flow. The ICD will fully identify each external system
2436 participating in a given interface, the entities responsible for establishing,
2437 maintaining, and managing the systems and the interfaces, and the
2438 hardware and software involved in the interface. The ICD will also
2439 describe the implementation of security controls, such as access
2440 management, encryption, and data integrity. Performance requirements,
2441 such as capacity, availability, frequency, and interface processing times,
2442 will also be included in the ICD.
2443 3.8.7.2 Deliverable 8.7.2: Interface Test Procedures and Results Report.
2444 For each interface, CONTRACTOR shall provide the interface test
2445 procedures and results which shall include:
LRS RFP - Attachment A (SOW) Page 88 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
2446 1. Identification of all requirements to test and accept the interface
2447 between the LRS and an external system or Web service;
2448 2. Description of the test procedures, including scenarios;
2449 3. Execution of the test; and
2450 4. Document the execution and results of all tests.
2451 3.8.7.3 Deliverable 8.7.3: Interface Documentation.
2452 For each interface, CONTRACTOR shall provide Interface
2453 Documentation, including any additional documentation for the interface,
2454 such as system administration manuals provided by the owner or manager
2455 of the external system.
2456 CONTRACTOR shall provide an updated PCD, M&O Services Plan,
2457 M&E Services Plan, Conversion and Archiving Plans, and Technical
2458 Infrastructure Design Document.
2459 3.9 TASK 9: TESTING:
2460 This Task 9 includes integration and testing, which shall incorporate the conversion and
2461 archiving strategies described in Deliverable 1.2.3 (Conversion and Archiving Plans). A
2462 full automated regression test shall be conducted at the conclusion of each major set of
2463 testing activities.
2464 CONTRACTOR shall perform the following Work during this Task 9:
2465 1. Develop the Master Test Plan;
2466 2. Develop test plans and procedures for all stages of testing, including integration
2467 testing, system testing, and UAT, that ensures all requirements are being tested
2468 and verified;
2469 3. Conduct the testing for all stages of testing, including integration testing, system
2470 testing, and UAT, evaluate results, correct problems, and re-test; and
2471 4. Develop, maintain, and execute automated regression test scripts in all stages of
2472 testing including integration testing, system testing, and UAT.
LRS RFP - Attachment A (SOW) Page 89 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
2473 3.9.1 Subtask 9.1: Develop Master Test Plan.
2474 CONTRACTOR shall prepare Deliverable 9.1 (Master Test Plan) that describes
2475 the overall approach to testing the LRS, including conversion and archiving
2476 testing, integration testing, system testing, UAT, and automated regression
2477 testing. CONTRACTOR shall include:
2478 1. Scope and guiding principles for LRS testing, both for the overall testing
2479 effort as well as specific to each type of testing. CONTRACTOR shall
2480 take into account all software lifecycles, including design time, runtime,
2481 and change time.
2482 2. Roles and responsibilities for CONTRACTOR‟s LRS test team members,
2483 for functional, technical, and training purposes, and required
2484 CONTRACTOR staffing resources.
2485 3. Overall test approach, including a summary of techniques to be used, how
2486 CONTRACTOR will group LRS functionality for testing, strategy for
2487 testing interfaces to external systems and agencies, and conduct of any
2488 end-to-end system tests.
2489 4. Testing schedule, including all proposed activities and major testing
2490 milestones, system builds, test script creation, and automated regression
2491 testing. CONTRACTOR shall also integrate these dates with the schedule
2492 in the Project Work Plan.
2493 5. Approach to validating that all requirements have been tested and verified.
2494 6. Tools to be used, including automated test tools, additional materials
2495 needed (e.g., test databases, test transactions, and load simulators), and
2496 tools to track testing progress.
2497 7. Approach to automated regression testing, describing when automated
2498 regression testing is appropriate, standard procedures to be followed, and
2499 tools to be used.
2500 8. Configuration of the LRS processing environments used for each specific
2501 level of testing, including: (i) configuration of the test environment; (ii)
LRS RFP - Attachment A (SOW) Page 90 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
2502 test equipment procurement and setup; (iii) test scenario/ script creation;
2503 and, (iv) integration testing.
2504 9. General rules for software acceptance at each level of testing, as approved
2505 by COUNTY.
2506 10. Management of all testing products and results using the LRS Repository
2507 to ensure that all products are accessible to the Project Team as needed.
2508 11. Approach to specialty testing to include usability, security, and
2509 performance.
2510 3.9.1.1 Deliverable 9.1: Master Test Plan.
2511 CONTRACTOR shall provide the Master Test Plan in accordance with
2512 Subtask 9.1 (Develop Master Test Plan).
2513 3.9.2 Subtask 9.2: Integration and System Testing.
2514 Integration and system testing ensures that all facets of the LRS work together as
2515 a cohesive whole. At the conclusion of this Subtask 9.2, CONTRACTOR shall
2516 have verified that the complete LRS operates in compliance with the
2517 Specifications.
2518 CONTRACTOR shall designate a test group independent from the LRS
2519 development staff to perform all testing beyond unit test. This test group shall
2520 include functional, technical, and training representatives, as needed, and may
2521 include COUNTY staff as approved by COUNTY Project Director.
2522 CONTRACTOR shall develop Deliverable 9.2.1 (Integration Test Plan) and
2523 Deliverable 9.2.5 (System Test Plan) that expands on the Master Test Plan with
2524 elements specific to integration and system testing. CONTRACTOR shall develop
2525 Deliverable 9.2.2 (Integration Test Procedures) and Deliverable 9.2.6 (System
2526 Test Procedures), including:
2527 1. Thoroughly test all LRS Components;
2528 2. Thoroughly test all LRS interfaces both internal and external, including
2529 real-time, host-to-host communications;
LRS RFP - Attachment A (SOW) Page 91 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
2530 3. Thoroughly test batch processing;
2531 4. Thoroughly test production print capabilities; and
2532 5. Verify the correct generation of all errors messages, warnings, or other
2533 messages as designed.
2534 CONTRACTOR shall conduct integration testing as each Baseline Application
2535 Software component/module and each conversion and archiving software
2536 program/tool is developed and added to the LRS. In Deliverable 9.2.3 (Integration
2537 Test Results Report), CONTRACTOR shall document the results for each
2538 integration test conducted.
2539 CONTRACTOR shall ensure that all processing environments utilized for a given
2540 test shall be restored to its original condition prior to the start of the given test,
2541 including all system files and data that may be affected or changed during
2542 execution of the test. CONTRACTOR shall complete certain integration testing,
2543 including:
2544 1. Performance and Load Testing – CONTRACTOR shall demonstrate
2545 that the LRS can successfully meet the performance requirements
2546 specified in the Agreement under full load conditions.
2547 2. Security Testing – CONTRACTOR shall demonstrate that the LRS can
2548 successfully meet COUNTY security requirements.
2549 3. Business Continuity/Disaster Recovery Testing – CONTRACTOR shall
2550 demonstrate that the LRS can successfully continue to provide services
2551 while executing business continuity/disaster recovery testing, including
2552 the effect on LRS performance requirements.
2553 4. Interface Testing – CONTRACTOR shall demonstrate that all interfaces
2554 are working properly and adhere to the Specifications.
2555 5. Cycle Testing – CONTRACTOR shall conduct cycle tests where each
2556 cycle test‟s processing is dependent upon previous processing in the LRS
2557 flow. CONTRACTOR shall conduct cycle tests to simulate the LRS
LRS RFP - Attachment A (SOW) Page 92 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
2558 operation during conversion and in production, including nightly, weekly,
2559 monthly, and other scheduled batch jobs to demonstrate that the cycles
2560 complete successfully in accordance with the Specifications.
2561 6. Client Correspondence and Reports Testing – CONTRACTOR shall
2562 verify the correct layout, format, and distribution of all LRS generated
2563 forms, Notices of Action (NOAs), documents, and reports, along with its
2564 supporting procedures. CONTRACTOR shall demonstrate that the LRS
2565 produces all forms, NOAs, documents, and reports in all COUNTY-
2566 required languages, including all languages for which the State has
2567 provided a translation.
2568 7. Reports Testing – CONTRACTOR shall verify the correct layout,
2569 format, and distribution of all LRS generated reports, both standard and ad
2570 hoc, with its supporting procedures.
2571 At the end of integration test, CONTRACTOR shall prepare Deliverable 9.2.4
2572 (Integration Test Summary Report), summarizing the activities, types of tests, and
2573 test results. Deliverable 9.2.4 (Integration Test Summary Report) shall include all
2574 technical materials, documentation, and LRS-generated output as required by
2575 COUNTY. CONTRACTOR shall present to COUNTY evidence that all Subtask
2576 9.2 related requirements have been met. CONTRACTOR shall prepare supporting
2577 documentation, conduct a review at a meeting with COUNTY, and provide any
2578 appropriate demonstration(s) of LRS capabilities, including COUNTY
2579 participation in or observation of tests. Approval of Deliverable 9.2.4 (Integration
2580 Test Summary Report) by COUNTY Project Director will allow CONTRACTOR
2581 to proceed to Subtask 9.3 (User Acceptance Testing).
2582 The System Test shall include execution of the Business Continuity/Disaster
2583 Recovery Plan.
2584 CONTRACTOR shall correct all Deficiencies prior to the start of Subtask 9.3
2585 (User Acceptance Testing), provided that, prior to CONTRACTOR‟s submission
2586 of Deliverable 9.2.8 (System Test Summary Report), CONTRACTOR may
LRS RFP - Attachment A (SOW) Page 93 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
2587 request in writing that COUNTY Project Director approve an exception to this
2588 requirement for the correction of specific Deficiencies, which Deficiencies: (i)
2589 individually and collectively are inconsequential and do not adversely affect any
2590 functional or technical requirement as determined by COUNTY Project Director;
2591 and (ii) shall be corrected by CONTRACTOR within the time period, not to
2592 exceed thirty (30) days, specified by COUNTY Project Director as a condition of
2593 providing his approval, except that such time period may be extended if approved
2594 by DPSS Director.
2595 3.9.2.1 Deliverable 9.2.1: Integration Test Plan.
2596 CONTRACTOR shall provide an Integration Test Plan which shall
2597 include:
2598 1. Test approach, identifying the progression of integration testing;
2599 2. Scheduling and resources;
2600 3. Tools, environments, and controls to be used during integration
2601 test;
2602 4. Entrance and exit criteria for integration test; and
2603 5. Metrics to be used to evaluate integration test results.
2604 3.9.2.2 Deliverable 9.2.2: Integration Test Procedures.
2605 CONTRACTOR shall provide Integration Test Procedures which shall
2606 include:
2607 1. Name, description, objectives, intended audience, and references
2608 of each specific test, including automated regression test;
2609 2. Traceability of integration test procedures to requirement(s) being
2610 tested;
2611 3. Assumptions, issues, and constraints;
2612 4. Special needs, tools, and programs;
2613 5. Instructions for conducting integration test:
LRS RFP - Attachment A (SOW) Page 94 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
2614 A. How to set up the test preconditions (e.g., configure/
2615 initialize the test environment);
2616 B. How to perform the test steps;
2617 C. How to determine and document the actual test post-
2618 conditions;
2619 D. How to compare the actual and expected results from the
2620 test; and
2621 E. How to report the results of the associated test.
2622 3.9.2.3 Deliverable 9.2.3: Integration Test Results Report.
2623 CONTRACTOR shall provide the Integration Test Report which shall
2624 include:
2625 1. Name and description of each specific test;
2626 2. Date and time test conducted;
2627 3. Name of each test team member;
2628 4. Test environment name, parameters, and configuration; and
2629 5. Results of test, including automated regression testing.
2630 3.9.2.4 Deliverable 9.2.4: Integration Test Summary Report.
2631 CONTRACTOR shall provide the Integration Test Summary Report,
2632 which summarizes all activities, types of tests, and results of the
2633 integration testing to allow COUNTY to assess the integration test
2634 outcome. This Report shall include:
2635 1. Summary of all tests conducted during integration testing;
2636 2. Summary of results;
2637 3. Summary of each Deficiency identified by CONTRACTOR or
2638 COUNTY, its corrective action status, date of completion of each
2639 correction, and date of COUNTY Project Director‟s approval of
2640 each correction; and
2641 4. Justification for moving to UAT.
LRS RFP - Attachment A (SOW) Page 95 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
2642 COUNTY Project Director‟s approval of this Deliverable 9.2.4 is required
2643 prior to CONTRACTOR proceeding to Subtask 9.3 (User Acceptance
2644 Testing).
2645 3.9.2.5 Deliverable 9.2.5: System Test Plan.
2646 CONTRACTOR shall provide a System Test Plan which shall include:
2647 1. Test approach, identifying the progression of system testing;
2648 2. Scheduling and resources;
2649 3. Tools, environments, and controls to be used during system
2650 testing;
2651 4. Entrance and exit criteria for system testing; and
2652 5. Metrics to be used to evaluate system testing results.
2653 3.9.2.6 Deliverable 9.2.6: System Test Procedures.
2654 CONTRACTOR shall provide System Test Procedures which shall
2655 include:
2656 1. Name, description, objectives, intended audience, and references
2657 of each specific test, including automated regression test;
2658 2. Traceability of system test procedures to requirement(s) being
2659 tested;
2660 3. Assumptions, issues, and constraints;
2661 4. Special needs, tools, and programs;
2662 5. Instructions for conducting system test:
2663 A. How to set up the test preconditions (e.g., configure/
2664 initialize the test environment);
2665 B. How to perform the test steps;
2666 C. How to determine and document the actual test post-
2667 conditions;
2668 D. How to compare the actual and expected results from the
2669 test; and
LRS RFP - Attachment A (SOW) Page 96 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
2670 E. How to report the results of the associated test.
2671 3.9.2.7 Deliverable 9.2.7: System Test Results Report.
2672 CONTRACTOR shall provide the System Test Report which shall
2673 include:
2674 1. Name and description of each specific test;
2675 2. Date and time test conducted;
2676 3. Name of each test team member;
2677 4. Name of test environment; and
2678 5. Results of test, including automated regression testing.
2679 3.9.2.8 Deliverable 9.2.8: System Test Summary Report.
2680 CONTRACTOR shall provide the System Test Summary Report, which
2681 summarizes all activities, types of tests, and results of the system testing to
2682 allow COUNTY to assess the system test outcome. This Report shall
2683 include:
2684 1. Summary of all tests conducted during system testing;
2685 2. Summary of results;
2686 3. Summary of each Deficiency identified by CONTRACTOR or
2687 COUNTY, its corrective action status, date of completion of each
2688 correction, and date of COUNTY Project Director‟s approval of
2689 each correction; and
2690 4. Justification for moving to UAT.
2691 COUNTY Project Director‟s approval of this Deliverable 9.2.8 is required
2692 prior to CONTRACTOR proceeding to Subtask 9.3 (User Acceptance
2693 Testing).
2694 3.9.3 Subtask 9.3: User Acceptance Testing.
2695 User Acceptance Testing (UAT) is a major project milestone during which
2696 COUNTY, with the assistance of CONTRACTOR, comprehensively tests the
LRS RFP - Attachment A (SOW) Page 97 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
2697 LRS against the Specifications to determine if the LRS is ready for Pilot
2698 implementation.
2699 CONTRACTOR shall provide a Recommended User Acceptance Test Plan to
2700 include:
2701 1. A description of proposed tests to be conducted during UAT;
2702 2. A description of tools, environments, and controls to be used during UAT;
2703 3. A proposed test schedule;
2704 4. A description of CONTRACTOR and COUNTY roles, responsibilities,
2705 and resources needed to perform UAT;
2706 5. A proposed training plan and schedule for UAT team;
2707 6. A process for UAT problem reporting, tracking, and resolution process;
2708 7. A proposed approach for the correction of Deficiencies identified by
2709 CONTRACTOR or COUNTY during UAT; and
2710 8. Execution of the Business Continuity/Disaster Recovery Plan.
2711 CONTRACTOR shall provide the above to COUNTY in Deliverable 9.3.1
2712 (Recommended User Acceptance Test Plan).
2713 CONTRACTOR shall provide tools, environment, and controls to be used during
2714 UAT.
2715 COUNTY will develop all test scenarios. CONTRACTOR shall incorporate and
2716 manage all COUNTY-developed scenarios, together with the related procedures,
2717 in the IDE and verify traceability between scenario/procedures to the
2718 Specifications throughout the term of the Agreement. CONTRACTOR shall
2719 update Deliverable 9.3.2 (User Acceptance Test Procedures/Scenarios Inventory
2720 Report) and provide update to COUNTY from time-to-time when requested by
2721 COUNTY Project Director. CONTRACTOR shall assist the COUNTY Project
2722 Team with the integration of COUNTY-developed scenarios into the automated
2723 regression test tool.
LRS RFP - Attachment A (SOW) Page 98 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
2724 CONTRACTOR shall assist COUNTY in developing the User Acceptance Test
2725 Plan which shall be prepared by COUNTY.
2726 During UAT, CONTRACTOR shall provide support to COUNTY, including
2727 configuration of the test environment, training on testing tools or processes for
2728 COUNTY UAT team, management of test results, and performance of any
2729 corrective actions in the case of identified Deficiencies by CONTRACTOR or
2730 COUNTY. CONTRACTOR shall be responsible for installing any special
2731 software and/or making any other needed changes to ensure the LRS is ready for
2732 UAT. CONTRACTOR shall provide any necessary tools to simulate LRS
2733 performance under operational conditions. COUNTY staff will perform UAT
2734 using data sets representative of operational complexity. COUNTY will record all
2735 UAT results, and CONTRACTOR shall prepare the reports that include a record
2736 of all successes, failures, and corrective actions taken by CONTRACTOR.
2737 CONTRACTOR shall provide Deliverable 9.3.3 (User Acceptance Test Weekly
2738 Status Reports) which summarizes all aspects of UAT performed during that
2739 week, including any Deficiencies identified by CONTRACTOR or COUNTY,
2740 corrected, and still outstanding. Reports shall be due every Tuesday for the entire
2741 period of the UAT. CONTRACTOR shall document the review and acceptance of
2742 test materials, activities, and results at weekly meetings with COUNTY.
2743 COUNTY will notify CONTRACTOR of any Deficiencies identified by
2744 COUNTY during UAT. For each Deficiency identified by CONTRACTOR or
2745 COUNTY, CONTRACTOR shall provide a corrective action plan, which shall
2746 include:
2747 1. Description of each Deficiency and its root cause;
2748 2. Business processes, LRS functions, and/or interfaces impacted;
2749 3. Description of all potential risks to the LRS, including to Countywide
2750 Implementation, and mitigation strategy for the LRS;
2751 4. Corrective action plan, test scenarios, and implementation approach;
LRS RFP - Attachment A (SOW) Page 99 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
2752 5. Incorporation of test scenario(s) into automated regression testing to detect
2753 each Deficiency;
2754 6. Schedule for completion of each corrective action and resources
2755 required/assigned;
2756 7. Status of each corrective action; and
2757 8. Approval procedures that require COUNTY Project Director‟s approval of
2758 each correction.
2759 CONTRACTOR shall schedule and participate in a meeting with COUNTY to
2760 review the results of UAT and determine whether CONTRACTOR has met all
2761 COUNTY requirements for LRS design and development prior to the start of
2762 Task 12 (Pilot).
2763 UAT shall include execution of the Business Continuity/Disaster Recovery Plan.
2764 CONTRACTOR shall provide Deliverable 9.3.4 (User Acceptance Test
2765 Certification of Successful Completion) to COUNTY certifying that all known
2766 Deficiencies identified by CONTRACTOR or COUNTY have been corrected by
2767 CONTRACTOR, and that all corrections have been approved by COUNTY
2768 Project Director. COUNTY Project Director‟s approval of Deliverable 9.3.4 (User
2769 Acceptance Test Certification of Successful Completion) will indicate the
2770 completion of Subtask 9.3 (User Acceptance Testing) and CONTACTOR may
2771 commence Task 12 (Pilot).
2772 CONTRACTOR shall correct all Deficiencies prior to the start of Task 12 (Pilot),
2773 provided that, prior to CONTRACTOR‟s submission of Deliverable 9.3.4 (User
2774 Acceptance Test Certification of Successful Completion), CONTRACTOR may
2775 request in writing that COUNTY Project Director approve an exception to this
2776 requirement for the correction of specific Deficiencies, which Deficiencies: (i)
2777 individually and collectively are inconsequential and do not adversely affect any
2778 functional or technical requirement as determined by COUNTY Project Director;
2779 and (ii) shall be corrected by CONTRACTOR within the time period, not to
LRS RFP - Attachment A (SOW) Page 100 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
2780 exceed thirty (30) days, specified by COUNTY Project Director as a condition of
2781 providing his approval, except that such time period may be extended if approved
2782 by DPSS Director.
2783 3.9.3.1 Deliverable 9.3.1: Recommended User Acceptance Test Plan.
2784 CONTRACTOR shall provide a Recommended User Acceptance Test
2785 Plan which shall include:
2786 1. Description of proposed tests to be conducted during UAT;
2787 2. Tools, environments, and controls to be used during UAT;
2788 3. Proposed test schedule;
2789 4. CONTRACTOR roles, responsibilities, and resources in
2790 performing UAT;
2791 5. Training plan and schedule for UAT team;
2792 6. Deficiency reporting, tracking, and correction process; and
2793 7. Approach to correcting Deficiencies identified during UAT.
2794 3.9.3.2 Deliverable 9.3.2: User Acceptance Test Procedures/Scenarios
2795 Inventory Report.
2796 CONTRACTOR shall provide the User Acceptance Test
2797 Procedures/Scenarios Inventory Report which shall include an inventory
2798 of all COUNTY-developed scenarios, together with the related
2799 procedures, in the IDE and verify traceability between scenario/procedures
2800 to the LRS requirements.
2801 3.9.3.3 Deliverable 9.3.3: User Acceptance Test Weekly Status Reports.
2802 CONTRACTOR shall provide User Acceptance Test Weekly Status
2803 Reports throughout UAT period. Each Report shall include:
2804 1. Summary of all tests conducted during UAT;
2805 2. Summary of test results;
2806 3. Summary of each Deficiency identified by CONTRACTOR or
2807 COUNTY. The summary shall include for each Deficiency:
LRS RFP - Attachment A (SOW) Page 101 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
2808 a. Description of each Deficiency and its root cause;
2809 b. Business processes, LRS functions, and/or interfaces
2810 impacted;
2811 c. Description of all potential risks to the LRS, including to
2812 Countywide Implementation, and mitigation strategy for
2813 the LRS;
2814 d. Corrective action plan, test scenarios, and implementation
2815 approach;
2816 e. Schedule for completion of each corrective action and
2817 resources required/assigned;
2818 f. Status of each corrective action;
2819 g. Date of completion of each correction; and
2820 h. Date of COUNTY Project Director‟s approval of each
2821 correction.
2822 4. Documentation of the review of the previous week‟s Report with
2823 COUNTY, including agenda, attendees, action items, and
2824 supporting documentation.
2825 3.9.3.4 Deliverable 9.3.4: User Acceptance Test Certification of Successful
2826 Completion.
2827 CONTRACTOR shall provide a User Acceptance Test Certification of
2828 Successful Completion to COUNTY within ten (10) days after successful
2829 completion of UAT, certifying that (i) all requirements traceability to all
2830 tests and test results have been verified, (ii) all Deficiencies identified by
2831 CONTRACTOR or COUNTY have been corrected by CONTRACTOR
2832 except for any delay in the correction of specific Deficiencies approved by
2833 COUNTY Project Director as described in Subtask 9.3 (User Acceptance
2834 Testing), (iii) all Deficiencies approved for correction delay by COUNTY
2835 Project Director as described in Subtask 9.3 (User Acceptance Testing)
2836 shall be corrected by CONTRACTOR within the time period, not to
2837 exceed thirty (30) days, specified by COUNTY Project Director for each
LRS RFP - Attachment A (SOW) Page 102 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
2838 such Deficiency as a condition of providing his approval, except that one
2839 (1) or more of such time periods for specific Deficiencies may have been
2840 extended by DPSS Director as described in Subtask 9.3 (User Acceptance
2841 Testing); (iv) all corrections have been approved by COUNTY Project
2842 Director, (v) test results of the Business Continuity/Disaster Recovery
2843 Plan, and (vi) all other UAT–related activities have been completed.
2844 CONTRACTOR shall also summarize all actions taken during UAT to
2845 correct each Deficiency identified by CONTRACTOR or COUNTY. The
2846 summary shall include for each Deficiency:
2847 1. Description of each Deficiency and its root cause;
2848 2. Business processes, LRS functions, and/or interfaces impacted;
2849 3. Description of all potential risks to the LRS, including to
2850 Countywide Implementation, and mitigation strategy for the LRS;
2851 4. Corrective action plan, test scenarios, and implementation
2852 approach;
2853 5. Schedule for completion of each corrective action and resources
2854 required/assigned;
2855 6. Status of each corrective action;
2856 7. Date of completion of each correction; and
2857 8. Date of COUNTY Project Director‟s approval of each correction.
2858 COUNTY Project Director‟s approval of this Deliverable 9.3.4 shall
2859 indicate the completion of Subtask 9.3 (User Acceptance Testing) and will
2860 allow CONTRACTOR to proceed with Task 12 (Pilot).
2861 3.9.3.5 Deliverable 9.3.5: Regression Test Scripts.
2862 CONTRACTOR shall provide the automated regression test scripts, which
2863 encompass all test scenarios for the integration test, system test, and UAT.
LRS RFP - Attachment A (SOW) Page 103 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
2864 3.10 TASK 10: IMPLEMENTATION PLANNING:
2865 In this Task 10, CONTRACTOR shall initiate planning for Countywide implementation
2866 of the LRS. CONTRACTOR shall perform the following Work in this Task 10:
2867 1. Develop the Implementation Master Plan that includes the strategy, resources, and
2868 schedule for Countywide implementation of the LRS;
2869 2. Update the Conversion and Archiving Plan for DPSS Systems that documents all
2870 data conversion activities required to transition from DPSS Systems to the LRS;
2871 3. Update the Conversion and Archiving Plan for DCFS Systems that documents all
2872 data conversion activities required to transition from DCFS Systems to the LRS;
2873 4. Update the M&O Services Plan that describes ongoing Management and
2874 Operations Services, including all processes, resources, and required tools;
2875 5. Update the M&E Services Plan that describes ongoing Application Software
2876 Modifications and/or Enhancements Services, including all processes, resources,
2877 and required tools; and
2878 6. Develop LRS Training Plans that describe how CONTRACTOR shall provide
2879 training for all COUNTY-specified Users, including COUNTY support staff.
2880 3.10.1 Subtask 10.1: Prepare Implementation Master Plan.
2881 CONTRACTOR, in consultation with COUNTY, shall develop Deliverable 10.1
2882 (Implementation Master Plan), including a description of preparation activities to
2883 be included in Task 11 (Implementation Preparation), the conduct of Pilot
2884 (described in Task 12 (Pilot)), the approach to concurrent operation of DPSS
2885 Systems and DCFS Systems with the LRS, and the schedule to ensure that all
2886 support services and sites are fully operational by the end Task 13 (Countywide
2887 Implementation). CONTRACTOR shall also reference any additional plans,
2888 developed during this Task 10 (Implementation Planning), in Deliverable 10.1
2889 (Implementation Master Plan).
2890 CONTRACTOR shall propose an implementation approach that describes the size
2891 and complexity of the User population, taking into account any transition and
LRS RFP - Attachment A (SOW) Page 104 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
2892 productivity concerns, hardware/technical considerations, and logistical, training,
2893 or implementation support issues. COUNTY requires a staggered schedule,
2894 grouping multiple Local Office Sites for implementation based on COUNTY
2895 monthly business cycles. CONTRACTOR shall document its approach for
2896 implementation activities in Deliverable 10.1 (Implementation Master Plan).
2897 CONTRACTOR shall provide an implementation work plan in COUNTY-
2898 specified version of Microsoft Project that provides a detailed schedule and
2899 required resources for both CONTRACTOR and COUNTY. CONTRACTOR
2900 must obtain COUNTY Project Director‟s approval of this plan prior to the start of
2901 Task 12 (Pilot).
2902 CONTRACTOR shall provide fully-trained support staff at each Local Office Site
2903 involved in the Pilot to provide direct User support for the LRS. CONTRACTOR
2904 shall provide at least one (1) onsite support staff person for every fifty (50) Users
2905 or a portion thereof at each Local Office Site.
2906 COUNTY requires CONTRACTOR to provide qualified support staff for on-site
2907 User support during the initial thirty (30) days after each Local Office Site
2908 implementation is completed.
2909 CONTRACTOR shall minimize any disruption to the public and to COUNTY
2910 staff in the normal operation of business.
2911 CONTRACTOR shall ensure that the LRS shall be able to interface with, share
2912 data with, and maintain data concurrency, as needed, with existing legacy
2913 systems, including DPSS Systems and DCFS Systems, during implementation
2914 activities. CONTRACTOR and COUNTY will jointly determine the data
2915 concurrency requirements as part of this Subtask 10.1. CONTRACTOR shall
2916 support all interfaces with federal, State, COUNTY, and external agency systems
2917 during the period of concurrent operations and thereafter. Deliverable 10.1
2918 (Implementation Master Plan) shall describe how CONTRACTOR will
2919 coordinate with DPSS Systems contractors and subject matter experts and DCFS
2920 Systems subject matter experts to ensure a smooth transition. CONTRACTOR
LRS RFP - Attachment A (SOW) Page 105 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
2921 shall document its proposed plan(s) for contingency operations if, at any point
2922 during Countywide implementation, the LRS fails to comply with COUNTY
2923 requirements for functionality, availability, response time and other performance.
2924 In Deliverable 10.1 (Implementation Master Plan), CONTRACTOR shall
2925 describe its approach to transition operations from the existing LEADER System
2926 central print facility and the GEARS mail management facility to the LRS Central
2927 Print Facility. CONTRACTOR shall describe the schedule for achieving full
2928 operational production at the Central Print Facility in Task 13 (Countywide
2929 Implementation).
2930 CONTRACTOR shall describe the process for issue identification, tracking, and
2931 resolution that sets forth how CONTRACTOR shall work with COUNTY to
2932 track, manage, resolve, and/or mitigate any issues arising throughout the
2933 implementation of the LRS.
2934 3.10.1.1Deliverable 10.1: Implementation Master Plan.
2935 Deliverable 10.1, CONTRACTOR shall provide the Implementation
2936 Master Plan which shall document the strategy, plan, and resources needed
2937 for the implementation of the LRS, including:
2938 1. Roles and responsibilities of CONTRACTOR staff.
2939 2. Implementation work plan, including Task 11 (Implementation
2940 Preparation) and Task 12 (Pilot), that includes schedule and
2941 resources required.
2942 3. Reference to supporting plans and schedule for DPSS Systems data
2943 conversion, training DPSS support staff (including LRS Helpdesk
2944 staff and local site Information Systems Analyst Aids), and
2945 training DPSS Users.
2946 4. Reference to supporting plans and schedule for DCFS Systems
2947 data conversion, training DCFS support staff (including Computer
2948 Application Technicians (CATs)), and training DCFS Users.
LRS RFP - Attachment A (SOW) Page 106 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
2949 5. Installation, configuration, and testing for the LRS processing
2950 environments and databases, including Primary Central Site,
2951 Backup Central Site, Central Print Facility, and Backup Print
2952 Facility.
2953 6. Installation, configuration, and testing for Enterprise Connecting
2954 Hardware, including the Gateway.
2955 7. System migration activities describing cutover from DPSS
2956 Systems to the LRS.
2957 8. System migration activities describing cutover from DCFS
2958 Systems to the LRS.
2959 9. Operational transition for the Central Print Facility from DPSS
2960 Systems to the LRS.
2961 10. Operational transition for the Central Print Facility from DCFS
2962 Systems to the LRS.
2963 11. Approach for support of Local Office Sites as they begin to use the
2964 LRS.
2965 12. Contingency plan(s) if, at any point during implementation, the
2966 LRS fails to meet or comply with COUNTY requirements for
2967 functionality, availability, response time, and other performance.
2968 13. Configuration considerations for User workstations and laptops
2969 and local printers.
2970 CONTRACTOR shall provide an updated PCD, M&O Services Plan,
2971 M&E Services Plan, and Technical Infrastructure Design Document.
2972 3.10.2 Subtask 10.2: Update Conversion and Archiving Plans.
2973 CONTRACTOR shall update Deliverable 1.2.3 (Conversion and Archiving Plans)
2974 incorporating lessons learned during the development, testing and validation of
2975 the automated conversion and archiving tools/software programs in Task 8
2976 (Baseline Application Software and Conversion and Archiving Tools) and Task 9
LRS RFP - Attachment A (SOW) Page 107 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
2977 (Testing). CONTRACTOR shall prepare a Deliverable 10.2 (Updated Conversion
2978 and Archiving Plans), describing all steps involved in the conversion, loading, and
2979 archiving of legacy data, in accordance with Attachment B (Statement of
2980 Requirements).
2981 The updated Conversion and Archiving Plan for DPSS Systems shall include:
2982 1. Approach to analyze DPSS Systems data and other legacy data;
2983 2. Approach used to map the DPSS Systems and other legacy data structures
2984 to the LRS Data structures, including data transformation rules and default
2985 values;
2986 3. Any automated tools or software programs to be used in the conversion
2987 and testing of results;
2988 4. Approach to reconcile converted data and DPSS Systems data, and other
2989 legacy data, including recommendations for the handling of any cases
2990 that should be considered conversion exceptions;
2991 5. Approach to archiving to optimize LRS performance;
2992 6. Approach to full accessibility of all converted data, including archived
2993 data;
2994 7. Data integrity rules, testing and quality assurance measures; and
2995 8. Proposed timelines, schedules, and resources for conversion and archiving
2996 activities.
2997 The updated Conversion and Archiving Plan for DCFS Systems shall include:
2998 1. Approach to analyze DCFS Systems data and other legacy data;
2999 2. Approach used to map the DCFS Systems and other legacy data structures to
3000 the LRS Data structures, including data transformation rules and default
3001 values;
3002 3. Any automated tools or software programs to be used in the conversion and
3003 testing of results;
LRS RFP - Attachment A (SOW) Page 108 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3004 4. Approach to reconcile converted data and DCFS Systems data and other
3005 legacy data, including recommendations for the handling of any cases that
3006 should be considered conversion exceptions;
3007 5. Approach to archiving to optimize LRS performance;
3008 6. Approach to full accessibility of all converted data, including archived data;
3009 7. Data integrity rules, testing and quality assurance measures; and
3010 8. Proposed timelines, schedules, and resources for conversion and archiving
3011 activities.
3012 CONTRACTOR shall prepare updated Conversion and Archiving Test Plans as
3013 part of Deliverable 10.2 (Updated Conversion and Archiving Plans) that describes
3014 CONTRACTOR approach to testing all data conversion, loading, and archiving
3015 processes, the use of data integrity rules, and methods to correct (if needed) any
3016 conversion rules (and hence the data) during the conversion and archiving
3017 processes.
3018 3.10.2.1Deliverable 10.2: Updated Conversion and Archiving Plans.
3019 CONTRACTOR shall provide the updated Conversion and Archiving
3020 Plans which shall incorporate all the planning components for data
3021 conversion and archiving of DPSS Systems data, DCFS Systems data, and
3022 other legacy data into the LRS, as described in Subtask 10.2 (Update
3023 Conversion and Archiving Plans).
3024 3.10.3 Subtask 10.3: Prepare LRS Training Plans.
3025 COUNTY anticipates that significant training will be needed to provide
3026 applicable COUNTY staff with a comprehensive understanding of the LRS.
3027 Initial instructor-led training shall be the responsibility of CONTRACTOR and
3028 developed based, in part, on COUNTY input. CONTRACTOR shall evaluate the
3029 needs of the various User groups to be trained. The User groups may be changed
3030 from time-to-time, as determined by COUNTY. CONTRACTOR shall provide
LRS RFP - Attachment A (SOW) Page 109 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3031 Deliverable 10.3 (LRS Training Plans) that includes an LRS Training Plan for
3032 DPSS Systems Users and an LRS Training Plan for DCFS Systems Users.
3033 The LRS Training Plan for DPSS Systems Users shall include:
3034 1. Roles and responsibilities of CONTRACTOR.
3035 2. Training locations, site preparation plans, provision and installation of all
3036 necessary equipment for the training sites.
3037 3. Curriculum Plan that describes modules, materials, learning objectives and
3038 proficiency standards, and hours of required training for each User group,
3039 including procedures for using any CONTRACTOR-provided LRS
3040 Helpdesk resources.
3041 4. Preliminary schedule for training, based on LRS implementation schedule
3042 and any identified COUNTY constraints for staffing, and resources for
3043 training.
3044 The LRS Training Plan for DCFS Systems Users shall include:
3045 1. Roles and responsibilities of CONTRACTOR.
3046 2. Training locations, site preparation plans, provision and installation of all
3047 necessary equipment for the training sites.
3048 3. Curriculum Plan that describes modules, materials, learning objectives and
3049 proficiency standards, and hours of required training for each User group,
3050 including procedures for using any CONTRACTOR-provided LRS
3051 Helpdesk resources.
3052 4. Preliminary schedule for training, based on LRS implementation schedule
3053 and any identified COUNTY constraints for staffing, and resources for
3054 training.
3055 The LRS Training Plans shall include all requirements set forth in Attachment B
3056 (Statement of Requirements).
LRS RFP - Attachment A (SOW) Page 110 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3057 The LRS Training Plans shall include a description of specialized training for
3058 COUNTY-specified Users as set forth in Attachment B (Statement of
3059 Requirements).
3060 During Phase 1 (Design/Development/Implementation Phase), CONTRACTOR
3061 shall provide all training, including specialized training and LRS Training
3062 Materials to COUNTY-specified Users. During Phase 2 (Performance
3063 Verification Phase) and Phase 3 (Operational Phase), CONTRACTOR shall
3064 continue to provide specialized training on a quarterly basis for COUNTY-
3065 specified Users. During Phase 2 (Performance Verification Phase) and Phase 3
3066 (Operational Phase), CONTRACTOR shall provide updated LRS Training
3067 Materials.
3068 During Phase 1 (Design/Development/Implementation Phase), CONTRACTOR
3069 shall provide all training locations, equipment, and connectivity to the LRS
3070 training processing environment for the initial training of COUNTY-specified
3071 Users. CONTRACTOR shall provide COUNTY-approved geographically
3072 dispersed locations throughout Los Angeles County to limit each trainee‟s travel
3073 distance between training location and trainee‟s work location to no more than
3074 twenty (20) miles.
3075 During Phase 2 (Performance Verification Phase) and Phase 3 (Operational
3076 Phase), CONTRACTOR shall provide specialized training at the Project Office.
3077 CONTRACTOR must obtain COUNTY Project Director approval of this Plan
3078 prior to the start of Task 12 (Pilot).
3079 3.10.3.1 Deliverable 10.3: LRS Training Plans.
3080 CONTRACTOR shall provide the LRS Training Plans as described in
3081 Subtask 10.3 (Prepare LRS Training Plans).
3082 CONTRACTOR shall provide an updated PCD, M&O Services Plan,
3083 M&E Services Plan, Conversion and Archiving Plans, and Technical
3084 Infrastructure Design Document.
LRS RFP - Attachment A (SOW) Page 111 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3085 3.11TASK 11: IMPLEMENTATION PREPARATION:
3086 In this Task 11, CONTRACTOR shall prepare for Countywide implementation.
3087 CONTRACTOR shall perform the following Work:
3088 1. Provide all Baseline Application Software Source Code, Object Code, and
3089 Documentation in a hardcopy format, electronic format, and on read-only
3090 medium, as specified by COUNTY, prior to the start of Task 12 (Pilot);
3091 2. Prepare the LRS Helpdesk application and CONTRACTOR support staff for the
3092 support of the LRS and document all LRS Helpdesk procedures;
3093 3. Review and update the PCD, M&O Services Plan, M&E Services Plan,
3094 Conversion and Archiving Plans, and Technical Infrastructure Design Document;
3095 4. Prepare LRS Training Materials in accordance with Deliverable 10.3 (LRS
3096 Training Plans) and design, develop, and implement the LRS Training Records
3097 Database used to track User enrollment, attendance, and training results;
3098 5. Establish the procedures for informing COUNTY of any issues that will affect the
3099 LRS in complying with the Specifications, and including meeting the
3100 performance requirements; and
3101 6. Prepare the LRS for implementation and operations, ensuring that all support and
3102 operational procedures, tools, and facilities are in place and operational in
3103 accordance with the schedule in Deliverable 10.1 (Implementation Master Plan).
3104 3.11.1 Subtask 11.1: Prepare Documentation.
3105 CONTRACTOR shall provide all Baseline Application Software Source Code,
3106 Object Code, and Documentation in hardcopy format, electronic format, and on
3107 read-only medium, as specified by COUNTY, prior to the start of Task 12 (Pilot).
3108 CONTRACTOR shall establish Documentation update procedures that allow
3109 specified COUNTY representatives to update and add Documentation to the LRS
3110 processing environments as needed. Any update to Documentation shall require
3111 prior approval of COUNTY Project Director.
LRS RFP - Attachment A (SOW) Page 112 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3112 3.11.1.1Deliverable 11.1: Documentation.
3113 CONTRACTOR shall provide all Baseline Application Software Source
3114 Code, Object Code, and Documentation, including:
3115 1. User manuals;
3116 2. Online help, both general and context sensitive;
3117 3. Learning aids, such as online tutorials;
3118 4. Orientation and training materials and manuals;
3119 5. LRS Application Software and data administration manuals;
3120 6. LRS technical infrastructure system administration manuals;
3121 7. LRS practices and procedures; and
3122 8. Commercial product manuals and documentation.
3123 3.11.2 Subtask 11.2: Prepare LRS Helpdesk Support and Application.
3124 CONTRACTOR shall provide LRS Helpdesk support staff and the LRS Helpdesk
3125 application. The LRS Helpdesk shall be accessible by COUNTY-specified
3126 persons for the reporting, tracking, and correction of Deficiencies in all LRS
3127 processing environments.
3128 LRS Helpdesk shall support the LRS with contact by COUNTY-specified
3129 persons. Both the LRS Helpdesk application and CONTRACTOR support staff
3130 shall be available at all times. The LRS Helpdesk application will be browser-
3131 based and conform to the requirements in Attachment B (Statement of
3132 Requirements) for the LRS Helpdesk application, or as otherwise approved by
3133 COUNTY Project Director.
3134 CONTRACTOR shall provide access for COUNTY-specified Users to
3135 knowledgeable CONTRACTOR support staff who can answer questions on the
3136 use of the LRS or on solutions to Deficiencies that COUNTY may encounter.
3137 CONTRACTOR shall provide toll-free telephone access for COUNTY-specified
3138 Users.
LRS RFP - Attachment A (SOW) Page 113 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3139 CONTRACTOR shall conduct conferences, weekly and as requested by
3140 COUNTY Project Director, for COUNTY-specified technical and helpdesk
3141 support staff using a real-time Web-enabled conference collaboration tool (e.g.,
3142 WebEx) and, if proposed by CONTRACTOR and approved by COUNTY, real-
3143 time videoconferencing, for strategic support and corrective action planning.
3144 Prior to the start of Task 12 (Pilot), CONTRACTOR shall document the structure
3145 and functions of the LRS Helpdesk support organization, which will provide
3146 ongoing assistance to COUNTY in Deficiency correction. CONTRACTOR shall
3147 design and document LRS Helpdesk procedures that meet the COUNTY
3148 requirements as set forth in the Agreement. For each Deficiency, COUNTY will
3149 determine the severity of the Deficiency (e.g., high, medium, low), the category of
3150 the Deficiency (e.g., User error, application error), and the nature of the
3151 Deficiency (e.g., hardware, software, network, data). COUNTY will also
3152 determine the procedures for the escalation of a Deficiency to increasingly
3153 responsible levels within CONTRACTOR for correction of Deficiencies reported
3154 to the LRS Helpdesk. CONTRACTOR shall ensure that the LRS Helpdesk
3155 application supports these escalation procedures, including automated notification
3156 to the appropriate parties.
3157 CONTRACTOR shall ensure that the LRS Helpdesk application and procedures
3158 shall be fully tested prior to use by COUNTY staff.
3159 CONTRACTOR shall document all related functional, technical, and training
3160 issues in Deliverable 11.2 (LRS Helpdesk Procedures).
3161 3.11.2.1Deliverable 11.2: LRS Helpdesk Procedures.
3162 CONTRACTOR shall provide LRS Helpdesk Procedures which shall
3163 include:
3164 1. An overview of the LRS Helpdesk application, including a
3165 description of the software and hardware used to support the LRS
3166 Helpdesk, the plan for its implementation, the approach to its
LRS RFP - Attachment A (SOW) Page 114 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3167 management and maintenance that will ensure that both the
3168 application and its knowledge base are kept current during the term
3169 of the Agreement, and the standard reports available to COUNTY
3170 for oversight and understanding of the LRS Helpdesk activities.
3171 2. An overview of the functions performed by the LRS Helpdesk and
3172 how they interface with other support activities for which
3173 CONTRACTOR is responsible (e.g., problem reporting, tracking,
3174 and resolution).
3175 3. The staffing requirements and organizational structure of the LRS
3176 Helpdesk, including roles and responsibilities of CONTRACTOR
3177 staff and points of contact with COUNTY helpdesks and support
3178 infrastructure.
3179 4. LRS Helpdesk standard operating procedures, including those
3180 performed by CONTRACTOR and those requiring coordination
3181 with COUNTY.
3182 5. LRS Helpdesk review process to provide both CONTRACTOR
3183 Project Director and COUNTY Project Director regular updates on
3184 the status and activities of the LRS Helpdesk operations.
3185 3.11.3 Subtask 11.3: Prepare LRS Training Materials.
3186 CONTRACTOR shall provide Deliverable 11.3 (LRS Training Materials),
3187 including procedures for accessing CONTRACTOR-provided LRS support
3188 resources. The LRS Training Materials shall be provided at least thirty (30) days
3189 prior to the start of Task 12 (Pilot). The LRS Training Materials shall include all
3190 training requirements in Attachment B (Statement of Requirements).
3191 During Phase 1 (Design/Development/Implementation Phase), CONTRACTOR
3192 shall provide all training, including specialized training, and LRS Training
3193 Materials to COUNTY-specified Users. During Phase 2 (Performance
3194 Verification Phase) and Phase 3 (Operational Phase), CONTRACTOR shall
3195 continue to provide specialized training, on a quarterly basis, for COUNTY-
LRS RFP - Attachment A (SOW) Page 115 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3196 specified Users. During Phase 2 (Performance Verification Phase) and Phase 3
3197 (Operational Phase), CONTRACTOR shall provide updated LRS Training
3198 Materials.
3199 CONTRACTOR shall provide and maintain all LRS Training Materials (e.g.,
3200 hardcopy and softcopy) for each training session, consistent with the Curriculum
3201 Plan described in Deliverable 10.3 (LRS Training Plans). CONTRACTOR shall
3202 work with COUNTY to develop materials that reflect realistic scenarios based on
3203 COUNTY standard business processes and procedures, tailored to User groups as
3204 required. The training materials and tutorials shall accurately reflect the online
3205 version of LRS functionality.
3206 CONTRACTOR shall provide hard copy documentation to each User by the first
3207 day of any classroom training (or videoconference training, if proposed by
3208 CONTRACTOR and approved by COUNTY) and online documentation and/or
3209 help functions by the first day of function and/or feature implementation in the
3210 LRS.
3211 CONTRACTOR shall provide COUNTY with master copies of all training
3212 materials. The LRS Training Materials shall be clear and understandable to both
3213 Users and technical staff.
3214 3.11.3.1Deliverable 11.3: LRS Training Materials.
3215 CONTRACTOR shall provide COUNTY with LRS Training Materials for
3216 DPSS Systems Users and DCFS Systems Users in accordance with
3217 Subtask 11.3 (Prepare LRS Training Materials) and Attachment B
3218 (Statement of Requirements).
3219 LRS Training Materials for DPSS Systems Users shall include:
3220 1. Master copies, both hardcopy and electronic, of all training
3221 materials and manuals provided by CONTRACTOR and third
3222 parties (e.g., product vendors);
3223 2. Hardcopy training materials for each trainee;
LRS RFP - Attachment A (SOW) Page 116 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3224 3. Online LRS tutorials and documentation;
3225 4. User proficiency tests; and
3226 5. All e-Learning modules.
3227 LRS Training Materials for DCFS Systems Users shall include:
3228 1. Master copies, both hardcopy and electronic, of all training
3229 materials and manuals provided by CONTRACTOR and third
3230 parties (e.g., product vendors);
3231 2. Hardcopy training materials for each trainee;
3232 3. Online LRS tutorials and documentation;
3233 4. User proficiency tests; and
3234 5. All e-Learning modules.
3235 3.11.4 Subtask 11.4: Implement LRS Training Records Database.
3236 CONTRACTOR shall design, develop, implement, host, and manage the LRS
3237 Training Records Database, available in all Local Office Sites for enrolling and
3238 reviewing training records, and to track pertinent training information.
3239 CONTRACTOR shall develop the LRS Training Records Database to allow
3240 secure, distributed access using a Web browser. CONTRACTOR shall provide
3241 Deliverable 11.4 (LRS Training Records Database) prior to the start of Task 12
3242 (Pilot).
3243 3.11.4.1Deliverable 11.4: LRS Training Records Database.
3244 CONTRACTOR shall provide a LRS Training Records Database that
3245 includes:
3246 1. Training sessions in accordance with the curriculum plan in
3247 Deliverable 10.3 (LRS Training Plans);
3248 2. Schedules for each training session including dates, locations,
3249 hours in training, and number of trainees in each session;
3250 3. Trainee name(s) and demographic information; and
LRS RFP - Attachment A (SOW) Page 117 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3251 4. Results for each training session including attendance, proficiency
3252 test results, and recommendations for additional training.
3253 3.11.5 Subtask 11.5: Prepare for Implementation and Operations.
3254 CONTRACTOR shall provide all support and operational procedures, tools, and
3255 facilities in accordance with Subtask 11.5 (Prepare for Implementation and
3256 Operations) and the schedule provided in Deliverable 10.1 (Implementation
3257 Master Plan), including:
3258 1. Primary Central Site and Backup Central Site;
3259 2. Central Print Facility and Backup Print Facility;
3260 3. Enterprise Connecting Hardware, including the Gateway;
3261 4. All management and operations procedures; and
3262 5. All tools for performance management.
3263 CONTRACTOR shall certify LRS operational readiness in Deliverable 11.5
3264 (Certification of Operational Readiness) prior to the start of Task 12 (Pilot).
3265 3.11.5.1 Deliverable 11.5: Certification of Operational Readiness.
3266 CONTRACTOR shall provide the Certification of Operational
3267 Readiness which shall certify that the LRS is operational and ready for
3268 Task 12 (Pilot).
3269 CONTRACTOR shall provide an updated PCD, M&O Services Plan,
3270 M&E Services Plan, Conversion and Archiving Plans, and Technical
3271 Infrastructure Design Document.
3272 3.12 TASK 12: PILOT:
3273 The purpose of Pilot is to serve as the primary validation of the production LRS prior to
3274 the commencement of Countywide implementation. CONTRACTOR shall work with
3275 COUNTY to define the representative User population most appropriate for Pilot. The
3276 Pilot shall emphasize validation of the LRS, including external interfaces, connectivity
3277 between the LRS and LAnet/EN, LRS functional and technical performance under
LRS RFP - Attachment A (SOW) Page 118 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3278 operational loads, and M&O Services. The Pilot duration shall be a minimum of four
3279 (4) months and a maximum of seven (7) months unless extended as requested by
3280 COUNTY Project Director in his sole discretion.
3281 CONTRACTOR shall perform the following Work during this Task 12:
3282 1. Prepare the Pilot Plan that provides the detailed set of activities, resources, and
3283 schedules needed for this Task 12;
3284 2. Conduct the Pilot commensurate with the proposed implementation approach,
3285 including any required data conversion and training activities;
3286 3. Execute the Business Continuity/Disaster Recovery Plan;
3287 4. Review with COUNTY the outcomes from Pilot, a summary of all corrective
3288 actions taken during Pilot, and activities needed to ensure that the LRS is ready
3289 for Countywide implementation;
3290 5. Perform all corrective actions and update implementation plans; and
3291 6. Certify that the LRS is ready for Countywide implementation.
3292 3.12.1 Subtask 12.1 Prepare Pilot Plan.
3293 CONTRACTOR shall develop the detailed set of activities, resources, and
3294 schedules needed for Task 12 (Pilot), including support of each Local Office
3295 Site involved in the Pilot. CONTRACTOR shall provide a work plan for Task
3296 12 (Pilot) in COUNTY-specified version of Microsoft Project that includes a
3297 detailed schedule and required resources for both CONTRACTOR and
3298 COUNTY.
3299 CONTRACTOR shall describe the process for issue identification, tracking, and
3300 resolution that includes how CONTRACTOR shall work with COUNTY to
3301 track, manage, resolve, and/or mitigate any issues arising during the Pilot.
3302 CONTRACTOR shall document its approach to Pilot in Deliverable 12.1 (Pilot
3303 Plan).
LRS RFP - Attachment A (SOW) Page 119 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3304 3.12.1.1 Deliverable 12.1: Pilot Plan.
3305 CONTRACTOR shall work with COUNTY to determine the specific
3306 objectives and results that COUNTY would like to achieve during
3307 Pilot. CONTRACTOR shall provide a Pilot Plan which shall describe
3308 the appropriate set of activities, resources, and schedules related to the
3309 conduct of the Pilot, including:
3310 1. Roles and responsibilities for CONTRACTOR.
3311 2. Project work plan for the Pilot that includes schedule and resources
3312 required of CONTRACTOR and each Local Office Site involved
3313 in the Pilot.
3314 3. Description of data conversion activities related to Pilot, including:
3315 A. Any Pilot pre-conversion requirements.
3316 B. A list of cases and/or files being converted.
3317 C. Conversion sequence and dependencies critical to LRS data
3318 integrity during conversion.
3319 D. A description of the methods to be used for calculating
3320 default values, as appropriate.
3321 E. Exception reporting processes.
3322 4. Description of training activities related to the Pilot, including the
3323 preparation of the LRS Training Records Database, delivery of all
3324 training and materials, and evaluation of the training.
3325 5. Usability testing, including Section 508 (Rehabilitation Act of
3326 1973, as amended) compliance evaluation.
3327 6. Metrics to be used to evaluate LRS performance during Pilot.
3328 7. Contingency strategy and plans to fall back to DPSS Systems
3329 operations following COUNTY‟s decision to restore the use of the
3330 existing system(s).
LRS RFP - Attachment A (SOW) Page 120 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3331 8. Contingency strategy and plans to fall back to DCFS Systems
3332 operations following COUNTY‟s decision to restore the use of the
3333 existing system(s).
3334
3335 3.12.2 Subtask 12.2: Conduct and Evaluate Pilot.
3336 CONTRACTOR shall conduct the Pilot commensurate with its proposed
3337 implementation approach as described in Deliverable 10.1 (Implementation
3338 Master Plan) and Deliverable 12.1 (Pilot Plan).
3339 CONTRACTOR shall perform all required data conversion activities as
3340 documented in Deliverable 10.2 (Updated Conversion and Archiving Plans) and
3341 Deliverable 12.1 (Pilot Plan). CONTRACTOR shall report on the results of
3342 Pilot data conversion activities, detailing the progress and accuracy of all data
3343 conversion activities.
3344 CONTRACTOR shall load and update LRS Training Records Database in
3345 preparation for Pilot. CONTRACTOR shall conduct training for all Pilot Users.
3346 CONTRACTOR shall update the LRS Training Records Database to report on
3347 all Pilot training activities and User proficiency test results, aggregated by User
3348 group. CONTRACTOR shall provide fully-trained support staff at each Local
3349 Office Site involved in the Pilot to provide direct User support for the LRS.
3350 CONTRACTOR shall provide at one (1) onsite support staff person for every
3351 fifty (50) Users or a portion thereof at each Local Office Site.
3352 If Deficiencies are identified by CONTRACTOR or COUNTY through Pilot,
3353 CONTRACTOR shall develop and execute, with the prior approval of
3354 COUNTY Project Director, a corrective action plan for the correction of each
3355 Deficiency identified by CONTRACTOR or COUNTY. Each corrective action
3356 plan shall include:
3357 1. Description of each Deficiency and its root cause;
3358 2. Business processes, LRS functions, and/or interfaces impacted;
LRS RFP - Attachment A (SOW) Page 121 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3359 3. Description of all potential risks to the LRS, including to Countywide
3360 Implementation, and mitigation strategy for the LRS;
3361 4. Corrective action plan, test scenarios, and implementation approach;
3362 5. Incorporation of test scenario(s) into automated regression testing to detect
3363 each Deficiency;
3364 6. Schedule for completion of each corrective action and resources
3365 required/assigned;
3366 7. Status of each corrective action; and
3367 8. Approval procedures that require COUNTY Project Director‟s approval of
3368 each correction.
3369 During Pilot, CONTRACTOR and COUNTY shall perform continuous
3370 evaluation of the LRS, including the following:
3371 1. LRS functionality as defined by Deliverable 6.1 (Functional Design
3372 Document (FDD));
3373 2. LRS performance as set forth in the Agreement;
3374 3. User feedback as to ease of use and support of the business processes;
3375 4. Adequacy of LRS support tools, procedures, and documentation;
3376 5. Adequacy of User training, ensuring that a satisfactory level of User
3377 proficiency is attained as a result of the training;
3378 6. Effectiveness of data conversion process and accuracy of the results;
3379 7. Performance of the Central Print Facility, including the printing and
3380 delivery of client correspondence;
3381 8. Ability to produce standard and ad hoc reports; and
3382 9. Effectiveness of M&O Services.
3383 CONTRACTOR shall document the outcomes of the Pilot in Deliverable 12.2.1
3384 (Pilot Evaluation Report). CONTRACTOR shall conduct a meeting with
3385 COUNTY to review Deliverable 12.2.1 (Pilot Evaluation Report), discuss
LRS RFP - Attachment A (SOW) Page 122 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3386 CONTRACTOR‟s approach to mitigating any potential risk(s) and/or correcting
3387 outstanding Deficiencies prior to the start of Task 13 (Countywide
3388 Implementation), and assess readiness of LRS for Countywide implementation.
3389 CONTRACTOR shall correct all Deficiencies prior to the start of Task 13
3390 (Countywide Implementation).
3391 CONTRACTOR shall correct all Deficiencies prior to the start of Task 13
3392 (Countywide Implementation), provided that, prior to CONTRACTOR‟s
3393 submission of Deliverable 12.2.1 (Pilot Evaluation Report), CONTRACTOR
3394 may request in writing that COUNTY Project Director approve an exception to
3395 this requirement for the correction of specific Deficiencies, which Deficiencies:
3396 (i) individually and collectively are inconsequential and do not adversely affect
3397 any functional or technical requirement as determined by COUNTY Project
3398 Director; and (ii) shall be corrected by CONTRACTOR within the time period,
3399 not to exceed thirty (30) days, specified by COUNTY Project Director as a
3400 condition of providing his approval, except that such time period may be
3401 extended if approved by DPSS Director.
3402 3.12.2.1 Deliverable 12.2.1: Pilot Evaluation Report.
3403 CONTRACTOR shall provide the Pilot Evaluation Report which shall
3404 document the outcomes of Pilot and include:
3405 1. LRS functionality, including all interfaces;
3406 2. LRS performance;
3407 3. Ease of use and support of the business process;
3408 4. Overall adequacy of LRS support tools, procedures, and
3409 documentation;
3410 5. Adequacy of training;
3411 6. Effectiveness of data conversion process and accuracy of the
3412 results, including percentage of cases converted;
3413 7. Performance of the Central Print Facility;
LRS RFP - Attachment A (SOW) Page 123 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3414 8. Test results of the Business Continuity/Disaster Recovery Plan,
3415 including the effects on LRS performance requirements;
3416 9. Ability to produce standard and ad hoc reports;
3417 10. Effectiveness of M&O Services;
3418 11. Updated Risk Management Plan, including a corrective action plan
3419 for each Deficiency identified by CONTRACTOR or COUNTY;
3420 12. Summary of lessons learned;
3421 13. Recommendations for any improvements to the LRS; and
3422 14. Certification that all Deficiencies approved for correction delay by
3423 COUNTY Project Director as described in Subtask 12.2 (Conduct
3424 and Evaluate Pilot) shall be corrected by CONTRACTOR within
3425 the time period, not to exceed thirty (30) days, specified by
3426 COUNTY Project Director for each such Deficiency as a condition
3427 of providing his approval, except that one (1) or more of such time
3428 periods for specific Deficiencies may have been extended by DPSS
3429 Director as described in Subtask 12.2 (Conduct and Evaluate
3430 Pilot).
3431 CONTRACTOR shall also summarize all actions taken to correct each
3432 Deficiency identified by CONTRACTOR or COUNTY. The summary
3433 shall include for each Deficiency:
LRS RFP - Attachment A (SOW) Page 124 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3434 1. Description of each Deficiency and its root cause;
3435 2. Business processes, LRS functions, or interfaces impacted;
3436 3. Description of all potential risks to the LRS, including to
3437 Countywide Implementation, and mitigation strategy for the LRS;
3438 4. Corrective action plan, test scenarios, and implementation
3439 approach;
3440 5. Schedule for completion of each corrective action and resources
3441 required/assigned;
3442 6. Status of each corrective action;
3443 7. Date of completion of each correction; and
3444 8. Date of COUNTY Project Director‟s approval of each correction.
3445 CONTRACTOR shall provide an updated Requirements Traceability
3446 Matrix which shall include the status of each functional, technical, and
3447 training requirement.
3448 3.12.2.2 Deliverable 12.2.2: Pilot Post-Evaluation Report.
3449 CONTRACTOR shall document the review with COUNTY of
3450 Deliverable 12.2.1 (Pilot Evaluation Report), including agenda,
3451 attendees, action items, and supporting documentation.
3452 CONTRACTOR shall provide an updated PCD, M&O Services Plan,
3453 M&E Services Plan, Conversion and Archiving Plans, and Technical
3454 Infrastructure Design Document.
3455 3.12.3 Subtask 12.3: Prepare for Countywide Implementation.
3456 Based on the review of Deliverable 12.2.1 (Pilot Evaluation Report), as described
3457 in Subtask 12.2 (Conduct and Evaluate Pilot), CONTRACTOR shall undertake all
3458 corrective actions, as required by COUNTY Project Director, to correct all
3459 Deficiencies identified by CONTRACTOR or COUNTY prior to the
3460 commencement of Task 13 (Countywide Implementation). CONTRACTOR shall
3461 prepare Deliverable 12.3 (Certification of Countywide Implementation Readiness
3462 Report and Plans Update). COUNTY will review Deliverable 12.3 (Certification
LRS RFP - Attachment A (SOW) Page 125 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3463 of Countywide Implementation Readiness Report and Plans Update) and
3464 determine whether CONTRACTOR has corrected all Deficiencies and/or
3465 undertaken all corrective actions required by COUNTY Project Director and has
3466 adequately addressed all potential risks that have been identified by
3467 CONTRACTOR or COUNTY.
3468 CONTRACTOR shall update Deliverable 10.1 (Implementation Master Plan) and
3469 any contingency plans referenced by Deliverable 10.1 (Implementation Master
3470 Plan). As part of Deliverable 12.3 (Certification of Countywide Implementation
3471 Readiness Report and Plans Update), CONTRACTOR shall deliver all updated
3472 plans to COUNTY for approval.
3473 Approval of Deliverable 12.3 (Certification of Countywide Implementation
3474 Readiness Report and Plans Update) by COUNTY Project Director will allow
3475 CONTRACTOR to proceed to Task 13 (Countywide Implementation).
3476 3.12.3.1Deliverable 12.3: Certification of Countywide Implementation
3477 Readiness Report and Plans Update.
3478 CONTRACTOR shall provide the Certification of Countywide
3479 Implementation Readiness Report, which shall summarize all actions
3480 taken during Subtask 12.3 (Prepare for Countywide Implementation) to
3481 correct all Deficiencies identified by CONTRACTOR or COUNTY during
3482 Pilot. The summary shall include for each Deficiency:
LRS RFP - Attachment A (SOW) Page 126 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3483 1. Description of each Deficiency and its root cause;
3484 2. Business processes, LRS functions, and/or interfaces impacted;
3485 3. Description of all potential risks to the LRS, including to
3486 Countywide Implementation, and mitigation strategy for the LRS;
3487 4. Corrective action plan, test scenarios, and implementation
3488 approach;
3489 5. Schedule for completion of each corrective action and resources
3490 required/assigned;
3491 6. Status of each corrective action;
3492 7. Date of completion of each correction; and
3493 8. Date of COUNTY Project Director‟s approval of each correction.
3494 In this Deliverable 12.3, CONTRACTOR shall certify in writing that all
3495 corrective actions required by COUNTY Project Director for Countywide
3496 implementation have been successfully completed and that each correction
3497 has been approved by COUNTY Project Director.
3498 CONTRACTOR shall provide COUNTY an updated Deliverable 10.1
3499 (Implementation Master Plan) including any contingency plans included in
3500 Deliverable 10.1 (Implementation Master Plan).
3501 CONTRACTOR shall provide an updated PCD, M&O Services Plan,
3502 M&E Services Plan, Conversion and Archiving Plans, and Technical
3503 Infrastructure Design Document.
3504 3.13 TASK 13: COUNTYWIDE IMPLEMENTATION:
3505 After successful completion of Task 12 (Pilot), CONTRACTOR shall implement the
3506 LRS Countywide in accordance with the COUNTY-approved updated Deliverable 10.1
3507 (Implementation Master Plan) provided in Deliverable 12.3 (Certification of Countywide
3508 Implementation Readiness Report and Plans Update). CONTRACTOR shall perform the
3509 following Work during this Task 13:
3510 1. Complete all data conversion and archiving activities and report on results;
LRS RFP - Attachment A (SOW) Page 127 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3511 2. Train COUNTY-specified support staff and COUNTY-specified Users;
3512 3. Verify that all Local Office Sites are ready for cutover to the LRS;
3513 4. Implement all Local Office Sites in accordance with a schedule based on
3514 COUNTY monthly business cycles;
3515 5. Prepare interim and final reports documenting the results of Countywide
3516 implementation; and
3517 6. Achieve COUNTY Project Director approval of the successful completion of
3518 Countywide implementation, which allows the move from Phase 1
3519 (Design/Development/Implementation Phase) to Phase 2 (Performance
3520 Verification Phase).
3521 3.13.1 Subtask 13.1: Execute Conversion and Archiving Plans.
3522 CONTRACTOR shall execute the Conversion and Archiving Plans, provided in
3523 Deliverable 10.2 (Updated Conversion and Archiving Plans), including data
3524 preparation and quality assurance testing. CONTRACTOR shall report on the
3525 results of each data conversion/archiving effort in Deliverable 13.1.1 (Conversion
3526 and Archiving Results Report). These reports detail the progress and accuracy of
3527 all data conversion and archiving activities until DPSS Systems and DCFS
3528 Systems are completely migrated to the LRS.
3529 At the conclusion of this Subtask 13.1, CONTRACTOR shall prepare Deliverable
3530 13.1.2 (Conversion and Archiving Final Report). As part of Deliverable 13.1.2
3531 (Conversion and Archiving Final Report), CONTRACTOR shall describe
3532 recommended methods for any ongoing data verification and/or reconciliation
3533 needs.
3534 3.13.1.1Deliverable 13.1.1: Conversion and Archiving Results Reports.
3535 For each group of Local Office Sites that is converted, CONTRACTOR
3536 shall prepare a Conversion and Archiving Results Report which shall
3537 include:
3538 1. Data conversion and archiving results and performance analysis;
LRS RFP - Attachment A (SOW) Page 128 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3539 2. Data conversion and archiving problems identified by
3540 CONTRACTOR or COUNTY, including discrepant conversions,
3541 and failed conversions; and
3542 3. For each data conversion and archiving problem identified by
3543 CONTRACTOR or COUNTY, include:
3544 A. Description of each problem and its root cause;
3545 B. Business processes, LRS functions, and/or interfaces
3546 impacted;
3547 C. Description of all potential risks to the LRS, including to
3548 Countywide Implementation, and mitigation strategy for
3549 the LRS;
3550 D. Corrective action plan, test scenarios, and implementation
3551 approach;
3552 E. Schedule for completion of each corrective action and
3553 resources required/assigned;
3554 F. Status of each corrective action;
3555 G. Date of completion of each correction; and
3556 H. Date of COUNTY Project Director‟s approval of each
3557 correction.
3558 3.13.1.2Deliverable 13.1.2: Conversion and Archiving Final Report.
3559 After the successful completion of all data conversion and archiving
3560 activities, CONTRACTOR shall prepare a Conversion and Archiving
3561 Final Report which shall summarize all data conversion and archiving
3562 activities and recommendations for ongoing data verification and/or
3563 reconciliation needs.
3564 3.13.2 Subtask 13.2: Conduct LRS Training.
3565 CONTRACTOR shall conduct LRS training in accordance with Deliverable 10.3
3566 (LRS Training Plans). CONTRACTOR shall provide all trainers, training
3567 manuals and materials, training locations, network connectivity, and equipment
LRS RFP - Attachment A (SOW) Page 129 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3568 necessary to train COUNTY-specified Users. CONTRACTOR shall be
3569 responsible for loading and updating the LRS Training Records Database. Upon
3570 completion of Countywide implementation, CONTRACTOR shall prepare
3571 Deliverable 13.2 (LRS Training Report) that contains how many Users received
3572 training, how many Users passed the COUNTY-approved User proficiency test,
3573 and any retraining that was required.
3574 3.13.2.1Deliverable 13.2: LRS Training Report.
3575 CONTRACTOR shall provide the LRS Training Report which shall
3576 summarize all training delivered to Users, document the effectiveness of
3577 this training (including the results from the COUNTY-approved User
3578 proficiency test) and provide recommendations for further training
3579 activities or processes.
3580 3.13.3 Subtask 13.3: Verification of Local Office Site Readiness.
3581 Prior to each group of Local Office Sites being implemented, CONTRACTOR
3582 shall verify implementation readiness, including the following:
3583 1. LRS functionality continues to meet the Specifications, including
3584 Deliverable 6.1 (Functional Design Document (FDD)).
3585 2. LRS performance (e.g., availability and response time) is being met as set
3586 forth in the Agreement).
3587 3. All cases, related data, and information maintained by each Local Office
3588 Site scheduled for conversion have been successfully converted.
3589 4. All Users at each scheduled Local Office Site have received appropriate
3590 training according to their roles as described in Subtask 13.2 (Conduct
3591 LRS Training).
3592 5. All User documentation has been delivered and is accessible to Users at
3593 the scheduled Local Office Sites.
3594 6. CONTRACTOR support staff has been assigned to each Local Office Site
3595 in the group to be converted.
LRS RFP - Attachment A (SOW) Page 130 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3596 3.13.3.1Deliverable 13.3: Certification of Local Office Site Readiness.
3597 CONTRACTOR shall provide a Certification of Local Office Site
3598 Readiness for each group of Local Office Sites certifying that the Local
3599 Office Sites meet all implementation readiness requirements and are
3600 prepared for Production Use of the LRS, in accordance with Subtask 13.3
3601 (Verification of Local Office Site Readiness).
3602 3.13.4 Subtask 13.4: Execution of Countywide Implementation.
3603 After COUNTY Project Director approval of Deliverable 13.3 (Certification of
3604 Local Office Site Readiness) for a specific group of Local Office Sites,
3605 CONTRACTOR shall bring the Local Office Sites online for Production Use in
3606 accordance with the accepted schedule.
3607 CONTRACTOR and COUNTY shall assess the following for at least thirty (30)
3608 days following the implementation of each group of Local Office Sites:
3609 1. Impact on LRS performance due to the additional load on the LRS;
3610 2. Continued effectiveness of M&O Services;
3611 3. User feedback as to ease of use and support of the business processes;
3612 4. Adequacy of LRS support tools, procedures, and documentation;
3613 5. Impact on performance of the Central Print Facility, including the printing
3614 and delivery of client correspondence;
3615 6. Impact on the ability to produce standard and ad hoc reports; and
3616 7. Any other matter requested by COUNTY Project Director.
3617 If Deficiencies are identified by CONTRACTOR or COUNTY during any
3618 implementation, CONTRACTOR shall develop and execute (with prior approval
3619 of COUNTY Project Director) a corrective action plan to describe how each
3620 Deficiency will be corrected and a schedule for the corrective actions. Each
3621 corrective action plan shall include:
3622 1. Description of each Deficiency and its root cause;
LRS RFP - Attachment A (SOW) Page 131 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3623 2. Business processes, LRS functions, and/or interfaces impacted;
3624 3. Description of all potential risks to the LRS, including to Countywide
3625 Implementation, and mitigation strategy for the LRS;
3626 4. Corrective action plan, test scenarios, and implementation approach;
3627 5. Incorporation of test scenario(s) into automated regression testing to detect
3628 each Deficiency;
3629 6. Schedule for completion of each corrective action and resources
3630 required/assigned;
3631 7. Status of each corrective action; and
3632 8. Approval procedures that require COUNTY Project Director‟s approval of
3633 each correction.
3634 CONTRACTOR shall document the results of the implementation of each group of
3635 Local Office Sites in Deliverable 13.4 (Local Office Site Implementation Interim
3636 Reports).
3637 3.13.4.1 Deliverable 13.4: Local Office Site Implementation Interim Reports.
3638 CONTRACTOR shall provide its analysis of LRS performance
3639 requirements and functionality after implementation of each group of
3640 Local Office Sites and verify that the LRS remains fully operational. For
3641 each group of Local Office Sites, CONTRACTOR shall provide a Local
3642 Office Site Implementation Interim Report which shall document the
3643 results of the implementation, including:
3644 1. Impact on LRS performance due to the additional load on the LRS;
3645 2. Continued effectiveness of M&O Services;
3646 3. User feedback as to ease of use and support of the business
3647 processes;
3648 4. Adequacy of LRS support tools, procedures, and documentation;
3649 5. Impact on performance of the Central Print Facility, including the
3650 printing and delivery of client correspondence; and
LRS RFP - Attachment A (SOW) Page 132 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3651 6. Impact on the ability to produce standard and ad hoc reports.
3652 For each group of Local Office Sites, CONTRACTOR shall summarize all
3653 actions taken during Local Office Site implementation to correct any
3654 Deficiencies identified during Local Office Site implementation,
3655 including: (i) description of each Deficiency and its root cause; (ii)
3656 business processes, LRS functions, or interfaces impacted; (iii) corrective
3657 action(s) taken; and (iv) outcome(s). CONTRACTOR shall also
3658 summarize any remaining Deficiencies that need to be corrected prior to
3659 continuing Task 13 (Countywide Implementation); provide its assessment
3660 of the potential risk(s) to Countywide implementation, proposed approach
3661 to risk mitigation, and plans to implement any corrective actions.
3662 3.13.5 Subtask 13.5: Completion of Countywide Implementation.
3663 Prior to the completion of Task 13 (Countywide Implementation),
3664 CONTRACTOR shall provide to COUNTY evidence, including supporting
3665 documentation, that all requirements for Countywide Implementation have been
3666 successfully met. CONTRACTOR shall conduct a review of Deliverable 13.5.1
3667 (Countywide Implementation Report) with COUNTY at a meeting and provide
3668 any COUNTY-requested demonstrations of the deployed LRS.
3669 CONTRACTOR shall evaluate the status of each Deficiency identified by
3670 CONTRACTOR or COUNTY, and shall include for each Deficiency:
LRS RFP - Attachment A (SOW) Page 133 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3671 1. Description of each Deficiency and its root cause;
3672 2. Business processes, LRS functions, and/or interfaces impacted;
3673 3. Description of all potential risks to the LRS and mitigation strategy for the
3674 LRS;
3675 4. Corrective action plan, test scenarios, and implementation approach;
3676 5. Incorporation of test scenario(s) into automated regression testing to detect
3677 each Deficiency;
3678 6. Schedule for completion of each corrective action and resources
3679 required/assigned;
3680 7. Status of each corrective action;
3681 8. Date of completion of each correction; and
3682 9. Date of COUNTY Project Director‟s approval of each correction
3683 CONTRACTOR shall provide:
3684 1. Summary of lessons learned; and
3685 2. Recommendations for any improvements to the LRS.
3686 Approval of Deliverable 13.5.1 (Countywide Implementation Report) by
3687 COUNTY Project Director constitutes successful completion of Countywide
3688 implementation and allows the move from Phase 1
3689 (Design/Development/Implementation Phase) to Phase 2 (Performance
3690 Verification Phase).
3691 3.13.5.1Deliverable 13.5.1: Countywide Implementation Report.
3692 CONTRACTOR shall provide the Countywide Implementation Report
3693 documenting the successful completion of Task 13 (Countywide
3694 Implementation), including:
3695 1. Summary of Task 13 (Countywide Implementation) activities,
3696 results, and outcomes;
3697 2. Summary of each Deficiency identified by CONTRACTOR or
3698 COUNTY. The summary shall include for each Deficiency:
LRS RFP - Attachment A (SOW) Page 134 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3699 A. Description of each Deficiency and its root cause;
3700 B. Business processes, LRS functions, and/or interfaces
3701 impacted;
3702 C. Description of all potential risks to the LRS and mitigation
3703 strategy for the LRS;
3704 D. Corrective action plan, test scenarios, and implementation
3705 approach;
3706 E. Schedule for completion of each corrective action and
3707 resources required/assigned;
3708 F. Status of each corrective action;
3709 G. Date of completion of each correction; and
3710 H. Date of COUNTY Project Director‟s approval of each
3711 correction.
3712 3. Summary of lessons learned; and
3713 4. Recommendations for any improvements to the LRS.
3714
3715 CONTRACTOR shall provide an updated Requirements Traceability
3716 Matrix which shall include the status of each functional, technical, and
3717 training requirement.
3718 3.13.5.2Deliverable 13.5.2: Certification of Countywide Implementation.
3719 CONTRACTOR shall provide the Certification of Countywide
3720 Implementation certifying the successful completion of Countywide
3721 implementation and that CONTRACTOR has completed all Work
3722 necessary for the LRS to be available for Production Use by all Users.
3723 The Certification shall also document the review with COUNTY of
3724 Deliverable 13.5.1 (Countywide Implementation Report), including
3725 agenda, attendees, action items, and supporting documentation.
LRS RFP - Attachment A (SOW) Page 135 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3726 Approval of Deliverable 13.5.2 (Certification of Countywide
3727 Implementation) by COUNTY Project Director constitutes successful
3728 completion of Countywide implementation and allows the move from
3729 Phase 1 (Design/Development/Implementation Phase) to Phase 2
3730 (Performance Verification Phase).
3731 CONTRACTOR shall provide an updated PCD, M&O Services Plan,
3732 M&E Services Plan, and Conversion and Archiving Plans.
3733 3.14 TASK 14: PHASE 2 (PERFORMANCE VERIFICATION PHASE):
3734 Phase 2 (Performance Verification Phase) will commence upon successful completion of
3735 Phase 1 (Design/Development/Implementation Phase), as determined by COUNTY
3736 Project Director, and continue through the following six (6) months.
3737 During Phase 2 (Performance Verification Phase), CONTRACTOR shall measure and
3738 report on LRS performance using the metrics described in the Performance Management
3739 Plan and in Attachment B (Statement of Requirements) during this period of six (6)
3740 months following Countywide Implementation.
3741 Prior to Final Acceptance, (i) all Deficiencies identified by CONTRACTOR or
3742 COUNTY during Phase 1 (Design/Development/Implementation Phase) and Phase 2
3743 (Performance Verification Phase) shall be corrected by CONTRACTOR, and all
3744 corrections of such Deficiencies must have been approved by COUNTY Project Director,
3745 and (ii) following COUNTY Project Director‟s approval of all such corrections, the LRS
3746 must have performed for thirty (30) consecutive days in compliance with the
3747 Specifications, including all performance requirements, with no Deficiencies, except any
3748 new Deficiencies that may be identified by CONTRACTOR or COUNTY during Phase 3
3749 (Operational Phase), which Deficiencies individually and collectively are inconsequential
3750 and do not adversely affect any performance requirement, as determined by COUNTY
3751 Project Director.
3752 CONTRACTOR shall perform Work during Phase 2 (Performance Verification Phase)
3753 which shall include:
LRS RFP - Attachment A (SOW) Page 136 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3754 1. M&O Services: CONTRACTOR shall continue to provide M&O Services in
3755 accordance with the M&O Services Plan;
3756 2. M&E Services: CONTRACTOR shall provide M&E Services in accordance
3757 with the M&E Services Plan; and
3758 3. Specialized Training: CONTRACTOR shall continue to provide specialized
3759 training, on a quarterly basis, for COUNTY-specified Users in accordance with
3760 the LRS Training Plans.
3761 CONTRACTOR shall provide an updated PCD, M&O Services Plan, M&E Services
3762 Plan, Conversion and Archiving Plans, Requirements Traceability Matrix, Technical
3763 Infrastructure Design Document, LRS Training Plans, and any other documents, as
3764 requested from time-to-time by COUNTY Project Director.
3765 3.14.1 Subtask 14.1: Continue Specialized Training.
3766 CONTRACTOR shall continue to provide specialized training, on a quarterly
3767 basis, for COUNTY-specified Users in accordance with the LRS Training Plans.
3768 3.14.1.1Deliverable 14.1: Specialized Training Reports.
3769 CONTRACTOR shall provide Specialized Training Reports, on a
3770 quarterly basis, which shall summarize all specialized training delivered
3771 during the previous quarter to COUNTY-specified Users.
3772 3.14.2 Subtask 14.2: Develop LRS Transition Plan.
3773 At least thirty (30) days prior to, and upon, expiration or termination of the
3774 Agreement, and at any other times as set forth in the Agreement, CONTRACTOR
3775 shall provide to COUNTY all Source Code, Object Code, Updates, and
3776 Documentation of the LRS Application Software, in a hard copy format,
3777 electronically, and on read-only medium, as specified by COUNTY. Further,
3778 CONTRACTOR shall have the following transition responsibilities:
3779 1. Preparation of a LRS Transition Plan, which shall provide for a smooth
3780 transition or transfer of the LRS and LRS Data from CONTRACTOR‟s
LRS RFP - Attachment A (SOW) Page 137 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3781 environment to the new environment of COUNTY or COUNTY-selected
3782 vendor.
3783 2. Identification of resource requirements to needed transition, host, and
3784 operate the LRS at COUNTY or COUNTY-selected vendor data center(s).
3785 3. Identification of transition team roles and responsibilities.
3786 4. Proposed timeline for completion of transition activities.
3787 5. Training plan and training of COUNTY-specified persons for the
3788 transition of the LRS, LRS Data, and system data as specified in
3789 Subsection 12.4 (System Data).
3790 6. Submission of the LRS Transition Plan to COUNTY for approval.
3791 CONTRACTOR shall provide an initial draft of Deliverable 14.2 (LRS Transition
3792 Plan) within thirty (30) days of completing Deliverable 13.5.1 (Countywide
3793 Implementation Report). CONTRACTOR shall maintain and update the LRS
3794 Transition Plan annually for COUNTY Project Director approval and be able to
3795 provide an updated copy within thirty (30) days of COUNTY request.
3796 CONTRACTOR shall keep the most current version of Deliverable 14.2 (LRS
3797 Transition Plan) in the LRS Repository throughout the term of the Agreement.
3798 3.14.2.1Deliverable 14.2: LRS Transition Plan.
3799 CONTRACTOR shall provide the LRS Transition Plan which shall
3800 include:
3801 1. Procedures and processes which shall provide for a smooth
3802 transition or transfer of the LRS and LRS Data from
3803 CONTRACTOR‟s environment to the new environment of
3804 COUNTY or COUNTY-selected vendor.
3805 2. Identification of resource requirements needed to transition, host,
3806 and operate the LRS at COUNTY or COUNTY-selected vendor
3807 data center(s).
3808 3. Identification of transition team roles and responsibilities.
LRS RFP - Attachment A (SOW) Page 138 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3809 4. Proposed timeline for completion of transition activities.
3810 5. Training plan and training of COUNTY-specified persons for the
3811 transition of the LRS, LRS Data, and system data as specified in
3812 Subsection 12.4 (System Data).
3813 6. Information and supporting documentation, as required by
3814 COUNTY, related to volumes, file sizes, and growth trends.
3815 3.14.3 Subtask 14.3: Prepare Performance Verification Report and Certification.
3816 At the completion of Phase 2 (Performance Verification Phase), CONTRACTOR
3817 shall provide to COUNTY evidence, including supporting documentation, that the
3818 LRS substantially complies with the Specifications, including all performance
3819 requirements, under full production load. CONTRACTOR shall conduct a review
3820 of Deliverable 14.3.1 (Performance Verification Report) with COUNTY at a
3821 meeting scheduled by COUNTY and provide any COUNTY-requested
3822 demonstrations of the LRS.
3823 3.14.3.1 Deliverable 14.3.1: Performance Verification Report
3824 CONTRACTOR shall provide the Performance Verification Report, do-
3825 cumenting the completion of Phase 2 (Performance Verification Phase),
3826 including:
3827 1. Summary of Task 14 (Phase 2 (Performance Verification Phase))
3828 activities, results, and outcomes;
3829 2. Summary of each Deficiency identified by CONTRACTOR or
3830 COUNTY. The summary shall include for each Deficiency:
LRS RFP - Attachment A (SOW) Page 139 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3831 A. Description of each Deficiency and its root cause;
3832 B. Business processes, LRS functions, and/or interfaces
3833 impacted;
3834 C. Description of all potential risks to the LRS and mitigation
3835 strategy for the LRS;
3836 D. Corrective action plan, test scenarios, and implementation
3837 approach;
3838 E. Schedule for completion of each corrective action and
3839 resources required/assigned;
3840 F. Status of each corrective action;
3841 G. Date of completion of each correction; and
3842 H. Date of COUNTY Project Director‟s approval of each
3843 correction.
3844 3. Summary of lessons learned; and
3845 4. Recommendations for any improvements to the LRS.
3846 CONTRACTOR shall provide an updated Requirements Traceability
3847 Matrix which shall include the status of each functional, technical, and
3848 training requirement.
3849 3.14.3.2 Deliverable 14.3.2: Certification of Performance Verification.
3850 CONTRACTOR shall provide the Certification of Performance
3851 Verification, certifying that the LRS substantially complies with the
3852 Specifications, including all performance requirements, under full
3853 production load. The Certification shall also document the review with
3854 COUNTY of Deliverable 14.3.1 (Performance Verification Report),
3855 including agenda, attendees, action items and supporting documentation.
3856 CONTRACTOR shall provide an updated PCD, M&O Services Plan,
3857 M&E Services Plan, Conversion and Archiving Plans, Technical
3858 Infrastructure Design Document, Requirements Traceability Matrix,
3859 LRS Training Plans, and any other documents.
LRS RFP - Attachment A (SOW) Page 140 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3860 3.15 TASK 15: PHASE 3 (OPERATIONAL PHASE):
3861 Phase 3 (Operational Phase) will commence upon the completion of Phase 2
3862 (Performance Verification Phase). CONTRACTOR shall provide Work in Phase 3
3863 (Operational Phase) which shall include:
3864 1. M&O Services: CONTRACTOR shall continue to provide M&O Services in
3865 accordance with the M&O Services Plan;
3866 2. M&E Services: CONTRACTOR shall continue to provide M&E Services in
3867 accordance with the M&E Services Plan; and
3868 3. Specialized Training: CONTRACTOR shall continue to provide specialized
3869 training, on a quarterly basis, for COUNTY-specified Users in accordance with
3870 the LRS Training Plans.
3871 CONTRACTOR shall provide an updated PCD, M&O Services Plan, M&E Services
3872 Plan, Conversion and Archiving Plans, Requirements Traceability Matrix, LRS Training
3873 Plans, and any other documents, as requested from time-to-time by COUNTY Project
3874 Director.
3875 3.15.1 Subtask 15.1: Ongoing Specialized Training.
3876 CONTRACTOR shall continue to provide specialized training, on a quarterly
3877 basis, for COUNTY-specified Users in accordance with the LRS Training Plans.
3878 3.15.1.1 Deliverable 15.1.: Ongoing Specialized Training Reports.
3879 CONTRACTOR shall provide ongoing Specialized Training Reports, on
3880 a quarterly basis, which shall summarize all specialized training
3881 delivered during the previous quarter to COUNTY-specified Users.
3882 3.15.2 Subtask 15.2: Final Acceptance Report and Certification.
3883 CONTRACTOR shall provide to COUNTY evidence, including supporting
3884 documentation, that (i) all Deficiencies identified by CONTRACTOR or
3885 COUNTY during Phase 1 (Design/Development/Implementation Phase) and
3886 Phase 2 (Performance Verification Phase) have been corrected by
3887 CONTRACTOR, (ii) all corrections of such Deficiencies have been approved by
LRS RFP - Attachment A (SOW) Page 141 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3888 COUNTY Project Director, and (iii) following COUNTY Project Director‟s
3889 approval of all such corrections, the LRS has performed for thirty (30)
3890 consecutive days in compliance with the Specifications, including all performance
3891 requirements, with no Deficiencies, except any new Deficiencies that may be
3892 identified by CONTRACTOR or COUNTY during Phase 3 (Operational Phase),
3893 which Deficiencies individually and collectively are inconsequential and do not
3894 adversely affect any performance requirement, as determined by COUNTY
3895 Project Director. If a new Deficiency is identified by CONTRACTOR or
3896 COUNTY during Phase 3 (Operational Phase) which is consequential or
3897 adversely affects any performance requirement, as determined by COUNTY
3898 Project Director, then CONTRACTOR shall correct such Deficiency and all
3899 corrections must be approved by COUNTY Project Director before such thirty
3900 (30) consecutive day period shall again commence. CONTRACTOR shall
3901 conduct a review of Deliverable 15.2.1 (Final Acceptance Report) with COUNTY
3902 at a meeting scheduled by COUNTY and provide any COUNTY-requested
3903 demonstrations of the LRS.
3904 3.15.2.1 Deliverable 15.2.1: Final Acceptance Report
3905 CONTRACTOR shall provide the Final Acceptance Report,
3906 documenting the achievement of Final Acceptance, including:
3907 1. Summary of the correction of each Deficiency identified by
3908 CONTRACTOR or COUNTY during Phase 1
3909 (Design/Development/Implementation Phase) and Phase 2
3910 (Performance Verification Phase). The summary shall include for
3911 each Deficiency:
LRS RFP - Attachment A (SOW) Page 142 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3912 A. Description of each Deficiency and its root cause;
3913 B. Business processes, LRS functions, and/or interfaces
3914 impacted;
3915 C. Description of all potential risks to the LRS and mitigation
3916 strategy for the LRS;
3917 D. Corrective action plan, test scenarios, and implementation
3918 approach;
3919 E. Schedule for completion of each corrective action and
3920 resources required/assigned;
3921 F. Status of each corrective action;
3922 G. Date of completion of each correction; and
3923 H. Date of COUNTY Project Director‟s approval of each
3924 correction.
3925 2. Summary of lessons learned; and
3926 3. Recommendations for any improvements to the LRS.
3927 CONTRACTOR shall provide an updated Requirements Traceability
3928 Matrix which shall include the status of each functional, technical, and
3929 training requirement.
3930 3.15.2.2 Deliverable 15.2.2: Final Acceptance Certification.
3931 CONTRACTOR shall provide the Final Acceptance Certification,
3932 certifying that: (i) all Deficiencies identified by CONTRACTOR or
3933 COUNTY during Phase 1 (Design/Development/Implementation Phase)
3934 and Phase 2 (Performance Verification Phase) have been corrected by
3935 CONTRACTOR, (ii) all corrections of such Deficiencies have been
3936 approved by COUNTY Project Director, and (iii) following COUNTY
3937 Project Director‟s approval of all such corrections, the LRS has
3938 performed for thirty (30) consecutive days in compliance with the
3939 Specifications, including all performance requirements, with no
3940 Deficiencies, except any new Deficiencies that may be identified by
LRS RFP - Attachment A (SOW) Page 143 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3941 CONTRACTOR or COUNTY during Phase 3 (Operational Phase),
3942 which Deficiencies individually and collectively are inconsequential and
3943 do not adversely affect any performance requirement, as determined by
3944 COUNTY Project Director. The Certification shall also document the
3945 review with COUNTY of Deliverable 15.2.1 (Final Acceptance Report),
3946 including agenda, attendees, action items and supporting documentation.
3947 COUNTY requires thirty (30) days to approve this Deliverable 15.2.2.
3948 COUNTY approval of this Deliverable 15.2.2 shall signify Final
3949 Acceptance of the LRS by COUNTY.
3950 CONTRACTOR shall provide an updated PCD, M&O Services Plan,
3951 M&E Services Plan, Conversion and Archiving Plans, Requirements
3952 Traceability Matrix, LRS Training Plans, and any other documents.
3953 3.15.3 Subtask 15.3: Outgoing Transition Support.
3954 Prior to the expiration or termination of the Agreement, CONTRACTOR shall
3955 provide training and other support to COUNTY and the COUNTY-selected
3956 vendor to transition the LRS in accordance with the LRS Transition Plan.
3957 3.15.3.1 Deliverable 15.3: Certification of Completion of Outgoing Transition
3958 Support.
3959 CONTRACTOR shall certify to COUNTY that all activities described in
3960 Deliverable 14.2 (LRS Transition Plan), as updated and approved by
3961 COUNTY through the term of the Agreement, have been successfully
3962 completed.
3963
LRS RFP - Attachment A (SOW) Page 144 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3964 4. DELIVERABLE SUMMARY:
3965 This Section 4 provides a summary of all Deliverables for Phase 1
3966 (Design/Development/Implementation Phase), Phase 2 (Performance Verification Phase),
3967 and Phase 3 (Operational Phase) as detailed in the sections above. COUNTY
3968 requirements for Due Dates are specified. As part of the Project Work Plan,
3969 CONTRACTOR shall provide a proposed schedule for the submission of all Deliverables
3970 to COUNTY in accordance with COUNTY requirements.
3971 4.1 PHASE 1 (DESIGN/DEVELOPMENT/IMPLEMENTATION PHASE)
3972 DELIVERABLES:
3973 The Deliverables for Phase 1 (Design/Development/Implementation Phase) are shown on
3974 the tables below.
3975 Table 1: Deliverables for Task 1 – Project Administration
DEL. # PARA. DELIVERABLE NAME DUE DATE
1.1.1 3.1.1.1 Project Control Document (PCD) Effective Date + 30 days
1.1.2 3.1.1.2 Project Office Physical Site Plan Effective Date + 30 days
1.1.3 3.1.1.3 Project Office Certification of Readiness COUNTY Approval of
Deliverable 1.1.2 + 90 Days
1.1.4 3.1.1.4 Incoming Orientation Plans Effective Date + 90 days
1.1.5 3.1.1.5 Project Initiation Completion Report Completion of Subtask 1.1
1.2.1 3.1.2.1 M&O Services Plan In PCD
1.2.2 3.1.2.2 M&E Services Plan In PCD
1.2.3 3.1.2.3 Conversion and Archiving Plans In PCD
1.3 3.1.3.1 Ongoing Project Administration In PCD
3976
3977
LRS RFP - Attachment A (SOW) Page 145 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3978
3979 Table 2: Deliverables for Task 2 – Development Methodology and Technical Practices
DEL. # PARA. DELIVERABLE NAME DUE DATE
Integrated Development Environment
2.1. 3.2.1.1 Effective Date + 30 days
Configuration Control Document
System Development Lifecycle Orientation
2.2 3.2.2.1 In PCD
and Materials
3980
3981 Table 3: Deliverables for Task 3 – Requirements Verification and Analysis
DEL. # PARA. DELIVERABLE NAME DUE DATE
3.1 3.3.1.1 Requirements Verification Schedule In PCD
3.2.1 3.3.2.1 System Requirements Document (SRD) In PCD
Requirements Traceability Matrix and
3.2.2 3.3.2.2 In PCD
Report
3982
3983 Table 4: Deliverable for Task 4 – General Design
DEL. # PARA. DELIVERABLE NAME DUE DATE
4 3.4.1.1 General Design Document In PCD
3984
3985
LRS RFP - Attachment A (SOW) Page 146 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3986 Table 5: Deliverables for Task 5 – Technical Infrastructure Planning and Design
DEL. # PARA. DELIVERABLE NAME DUE DATE
5.1 3.5.1.1 Technical Infrastructure Design Document In PCD
5.2 3.5.2.1 Facility Management Plan In PCD
5.3 3.5.3.1 Information Systems Security Plan In PCD
5.4 3.5.4.1 Network Design Plan In PCD
3987
3988 Table 6: Deliverables for Task 6– Functional Design
DEL. # PARA. DELIVERABLE NAME DUE DATE
6.1 3.6.1.1 Functional Design Document (FDD) In PCD
6.2 3.6.2.1 Functional Design Presentation Report Completion of Task 6
3989
3990 Table 7: Deliverables for Task 7 – Technical Infrastructure Deployment
DEL. # PARA. DELIVERABLE NAME DUE DATE
Technical Infrastructure Asset
7.1 3.7.1.1 In PCD
Configuration Report
Technical Infrastructure System
7.2 3.7.2.1 In PCD
Administration Procedures
Technical Infrastructure Review and
7.3 3.7.3.1 In PCD
Acceptance Document
3991
3992
LRS RFP - Attachment A (SOW) Page 147 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3993 Table 8: Deliverables for Task 8 – Baseline Application Software and Conversion and
3994 Archiving Tools
DEL. # PARA. DELIVERABLE NAME DUE DATE
Baseline Application Software
8.1 3.8.1.1 In PCD
Development Plan (SDP)
Baseline Application Software
8.2 3.8.2.1 In PCD
Development Review Report
LRS Application Software SDLC
8.3 3.8.3.1 In PCD
Standards
Baseline Application Software
8.4 3.8.4.1 Components/Modules and Conversion and In PCD
Archiving Software Programs/Tools
8.5.1 3.8.5.1 Unit Test Template In PCD
8.5.2 3.8.5.2 Unit Test Procedures and Results Report In PCD
8.6 3.8.6.1 Unit Test and Validation Results Report In PCD
8.7.1 3.8.7.1 Interface Control Documents (ICD) In PCD
Interface Test Procedures and Results
8.7.2 3.8.7.2 In PCD
Report
8.7.3 3.8.7.3 Interface Documentation In PCD
3995
3996
LRS RFP - Attachment A (SOW) Page 148 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
3997 Table 9: Deliverables for Task 9 –Testing
DEL. # PARA. DELIVERABLE NAME DUE DATE
9.1 3.9.1.1 Master Test Plan In PCD
9.2.1 3.9.2.1 Integration Test Plan In PCD
9.2.2 3.9.2.2 Integration Test Procedures In PCD
9.2.3 3.9.2.3 Integration Test Results Report In PCD
Completion of Subtask
9.2.4 3.9.2.4 Integration Test Summary Report
9.2
9.2.5 3.9.2.5 System Test Plan In PCD
9.2.6 3.9.2.6 System Test Procedures In PCD
9.2.7 3.9.2.7 System Test Results Report In PCD
9.2.8 3.9.2.8 System Test Summary Report In PCD
9.3.1 3.9.3.1 Recommended User Acceptance Test Plan In PCD
User Acceptance Test Procedures/Scenarios
9.3.2 3.9.3.2 In PCD
Inventory Report
User Acceptance Test Weekly Status
9.3.3 3.9.3.3 In PCD
Reports
User Acceptance Test Certification of
9.3.4 3.9.3.4 In PCD
Successful Completion
9.3.5 3.9.3.5 Regression Test Scripts In PCD
3998
3999 Table 10: Deliverables for Task 10– Implementation Planning
DEL. # PARA. DELIVERABLE NAME DUE DATE
10.1 3.10.1.1 Implementation Master Plan In PCD
10.2 3.10.2.1 Updated Conversion and Archiving Plans In PCD
10.3 3.10.3.1 LRS Training Plans In PCD
4000
4001
LRS RFP - Attachment A (SOW) Page 149 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
4002 Table 11: Deliverables for Task 11 – Implementation Preparation
DEL. # PARA. DELIVERABLE NAME DUE DATE
11.1 3.11.1.1 Documentation Prior to start of Task 12
11.2 3.11.2.1 LRS Helpdesk Procedures Prior to start of Task 12
30 days prior to start of
11.3 3.11.3.1 LRS Training Materials
Task 12
11.4 3.11.4.1 LRS Training Records Database Prior to start of Task 12
11.5 3.11.5.1 Certification of Operational Readiness Prior to start of Task 12
4003
4004 Table 12: Deliverables for Task 12– Pilot
DEL. # PARA. DELIVERABLE NAME DUE DATE
12.1 3.12.1.1 Pilot Plan In PCD
12.2.1 3.12.2.1 Pilot Evaluation Report In PCD
12.2.2 3.12.2.2 Pilot Post-Evaluation Report In PCD
Certification of Countywide
12.3 3.12.3.1 Implementation Readiness Report and In PCD
Plans Update
4005
4006
LRS RFP - Attachment A (SOW) Page 150 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
4007 Table 13: Deliverables for Task 13 – Countywide Implementation
DEL. # PARA. DELIVERABLE NAME DUE DATE
13.1.1 3.13.1.1 Conversion and Archiving Results Report In PCD
13.1.2 3.13.1.2 Conversion and Archiving Final Report In PCD
13.2 3.13.2.1 LRS Training Report In PCD
Certification of Local Office Site
13.3 3.13.3.1 For each Local Office Site
Readiness
After the completion of
implementation activities
Local Office Site Implementation Interim
13.4 3.13.4.1 at each Local Office Site
Reports
or group of Local Office
Sites
13.5.1 3.13.5.1 Countywide Implementation Report Completion of Task 13
Certification of Countywide
13.5.2 3.13.5.2 Completion of Task 13
Implementation
4008
4009 4.2 PHASE 2 (PERFORMANCE VERIFICATION PHASE) DELIVERABLES:
4010 The Deliverables for Phase 2 (Performance Verification Phase) are shown on the tables
4011 below.
4012 Table 14: Deliverables for Task 14 – Phase 2 (Performance Verification Phase)
DEL. # PARA. DELIVERABLE NAME DUE DATE
14.1 3.14.1.1 Specialized Training Reports In PCD
14.2 3.14.2.1 LRS Transition Plan In PCD
14.3.1 3.14.3.1 Performance Verification Report In PCD
14.3.2 3.14.3.2 Certification of Performance Verification In PCD
4013
4014
LRS RFP - Attachment A (SOW) Page 151 April 8, 2008
Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
4015
4016 4.3 PHASE 3 (OPERATIONAL PHASE) DELIVERABLES:
4017 The Deliverables for Phase 3 (Operational Phase) are shown on the tables below.
4018 Table 15: Deliverables for Task 15 – Phase 3 (Operational Phase)
DEL. # PARA. DELIVERABLE NAME DUE DATE
15.1.1 3.15.1.1 Ongoing Specialized Training Reports In PCD
15.2.1 3.15.2.1 Final Acceptance Report In PCD
15.2.2 3.15.2.2 Final Acceptance Certification In PCD
Certification of Completion of Outgoing
15.3.1 3.15.3.1 In PCD
Transition Support
4019
LRS RFP - Attachment A (SOW) Page 152 April 8, 2008
Los Angeles County
Department of Public Social Services
LEADER Replacement System (LRS)
4020 Exhibit A: Deliverable Expectation Document (DED)
4021 This Exhibit A provides a template that describes the required contents of a Deliverable
4022 Expectation Document (DED). The format for the DED must be approved by COUNTY Project
4023 Director prior to its use. A DED must be prepared by CONTRACTOR and approved by
4024 COUNTY Project Director prior to the submittal of each Deliverable as set forth in this SOW,
4025 with the exception of Deliverables due within the first ninety (90) days after the Effective Date.
4026 Refer to Section 2.5 (Deliverable Acceptance Criteria (General)) of the SOW for information on
4027 submitting the DED. The requested information in this Exhibit A must be readily identifiable in
4028 the DED. Work plans that support the activity summary may be attached and referenced to
4029 support the methodology and schedule summary.
4030 1. TABLE OF CONTENTS:
4031 This section of the DED shall include the table of contents for the DED. A brief
4032 overview of the proposed content for each major section, level of detail and format of key
4033 sections shall be provided, where appropriate, to more fully delineate the expectations for
4034 the Deliverable.
4035 2. INTRODUCTION:
4036 This section of the DED shall include a brief overview defining the purpose of the
4037 Deliverable and how it fits within the overall completion of the project. Any dependant
4038 tasks, subtasks, deliverables, and other Work shall be described in the Introduction.
4039 3. DELIVERABLE DESCRIPTION:
4040 This section of the DED shall include the Deliverable‟s objectives and scope which shall
4041 be described in clear, specific terms.
4042 3.1 METHODOLOGY FOR CREATING THE DELIVERABLE:
4043 A brief explanation of the tasks, activities, and methods to be used to develop the
4044 Deliverable shall be provided. Process flow diagrams shall be included where applicable.
4045 Methodologies described in detail elsewhere, such as CONTRACTOR‟s SDLC, shall be
LRS RFP - Attachment A (SOW) Page 153 April 8, 2008
Los Angeles County
Department of Public Social Services
LEADER Replacement System (LRS)
4046 referenced appropriately. Any assumptions or constraints on the development of the
4047 Deliverable shall be indicated.
4048 3.2 APPLICABLE STANDARDS:
4049 All applicable industry and/or government standards that the Deliverable shall reference
4050 must be listed, including descriptions of version level and extent of compliance.
4051 CONTRACTOR may provide a mapping of its format to the applicable standard to show
4052 compliance.
4053 3.3 DELIVERABLE REQUIREMENTS:
4054 The specific description of the Deliverable from the SOW shall be included, delineating
4055 any additional requirements related to the Deliverable and their source.
4056 3.4 DELIVERABLE FORMAT:
4057 Any templates, diagrams, tables, or specific content that will be required for the
4058 Deliverable shall be listed. For example, in design and test Deliverables, an updated
4059 Requirements Traceability Matrix shall be included in the Deliverable.
4060 The format of the Deliverable shall be described, including any associated diagrams,
4061 spreadsheets, or databases and the tools (e.g., COUNTY-specified versions of Microsoft
4062 Word, Microsoft Visio, Microsoft Project, etc.) used for production and viewing of the
4063 Deliverable. The number of hardcopies and the number of electronic copies, of the
4064 Deliverable to be provided and distributed to COUNTY shall be stated.
4065 4. RECOMMENDED DELIVERABLE ACCEPTANCE CRITERIA:
4066 This section of the DED shall include a description of the recommended acceptance
4067 criteria for the Deliverable. The recommended acceptance criteria shall be specific to the
4068 Deliverable and indicate key needs of the project (e.g., must include detailed description
4069 of database sizing, growth considerations, performance considerations, and
4070 normalization/de-normalization considerations).
4071 General review criteria (e.g., those which are primarily the same for all Deliverables)
4072 shall be referenced or attached. The following shall be considered the minimum
4073 recommended acceptance criteria:
LRS RFP - Attachment A (SOW) Page 154 April 8, 2008
Los Angeles County
Department of Public Social Services
LEADER Replacement System (LRS)
4074 Compliance with the applicable standards as described in Section 3.2 (Applicable
4075 Standards) of this Exhibit A;
4076 Compliance with the deliverable requirements as described in Section 3.3
4077 (Deliverable Requirements) of this Exhibit A;
4078 Compliance with the deliverable format as described in Section 3.4 (Deliverable
4079 Format) of this Exhibit A;
4080 Consistency, as appropriate, with other COUNTY-approved Deliverables; and
4081 Compliance with quality assurance standards (e.g., free of formatting, spelling, and
4082 grammar errors, clearly written with no incomplete sections, etc.).
4083 5. DELIVERABLE SCHEDULE:
4084 5.1 KEY DATES FOR DELIVERABLES:
4085 This section of the DED shall include references to the key activities and due dates in
4086 Deliverable preparation and review, ensuring that all associated Work is consistent with
4087 the Project Work Plan and the Agreement timeframes regarding Deliverable delivery and
4088 approval/rejection. The process described shall refer to the Project Control Document
4089 and any other applicable schedules or plans. Reference shall be made to any key
4090 meetings, walkthroughs, inspections and reviews associated with the Deliverable.
4091 Table 1 illustrates an example of Deliverable-related key dates.
4092
LRS RFP - Attachment A (SOW) Page 155 April 8, 2008
Los Angeles County
Department of Public Social Services
LEADER Replacement System (LRS)
4093
4094 Table 1: Key Dates Related to Deliverable xx (Example)
KEY ACTIVITY DUE COMMENT
DATE
Submission of DED
COUNTY Review and Approval of DED
Submission of Deliverable to COUNTY
Presentation of Deliverable to COUNTY (if necessary or
requested by COUNTY Project Director)
COUNTY Review of Deliverable
Resolution of COUNTY Comments and Submission of
Revised Deliverable (if necessary)
COUNTY Review of Revised Deliverable (if necessary)
Resolution of COUNTY Comments (if necessary)
COUNTY Approval of Deliverable
4095 5.2 SCHEDULE FOR DELIVERABLE UPDATES:
4096 This section of the DED shall include the proposed schedule of updates and tentative time
4097 frames shall be provided if the Deliverable is expected to be updated on a periodic basis.
4098 6. STAFF RESOURCES REQUIRED:
4099 This section of the DED shall include, the specific staff resources involved in Deliverable
4100 preparation and review which shall be listed in a format similar to Table 2. This list shall
4101 identify the specific, key individuals/skills needed to ensure successful completion of the
4102 Deliverable. An estimate of the amount of time required from each CONTRACTOR Key
4103 Staff resource shall be indicated.
4104
LRS RFP - Attachment A (SOW) Page 156 April 8, 2008
(
Los Angeles County
Department of Public Social Services
LEADER Replacement System (LRS)
4105 Table 2: Required Staff Resources (Example)
ROLE NAME(S) RESPONSIBILITIES ESTIMATED NEED
Deliverable Lead 2 months
Deliverable Approver 5 days
Deliverable Reviewers 7 days
Subject Matter Experts 10 days
Policy Representative 10 days
COUNTY IV&V 5 days
Contractor
4106
LRS RFP - Attachment A (SOW) Page 157 April 8, 2008