Worksheet in Deloittes System Design Document

Deloitte Consulting LLP General System Design 12/03/2010
Mandatory/
Desirable
Original
Require
ment ID
New
Requirement
ID
RFP Type Requirement Description In Scope/
Out of
Scope
Added/
Modified/
Deleted
Reason
E
l
i
g
i
b
i
l
i
t
y
C
u
s
t
o
m
e
r

S
e
r
v
i
c
e
P
I
Q
A
T
e
c
h
n
i
c
a
l
A
p
p
r
o
a
c
h
P
r
o
p
o
s
a
l Business
Process ID
Use Case
ID
Mandatory 1 CCMS-REQ-001 Electronic
Document
Workflow
System must provide an electronic document workflow
to automate the activities and information flow related
to eligibility,. customer service, and fraud.
In Scope Modified Split into 3
requirements (see
below).
X X All Eligibility
Business
Processes
All Eligibility
Use Cases
Document
Workflow
to customer service.
In Scope Modified X X All Customer
Service
Business
Processes
All Customer
Service Use
Cases
Document
Workflow
to fraud.
In Scope Modified X X All PIQA
Business
Processes
All PIQA Use
Cases
Document
Workflow
CCMS must provide a proven, Web-based document
management system, with process improvements.,
and centralized storage. The Vendor must provide the
software and any additional hardware to implement
this system.
requirements (see
below).
X All All
Document
Workflow
CCMS must provide a proven, Web-based centralized
storage with secured access.
In Scope Modified X All All
Document
Workflow
The Vendor must provide the software and any
additional hardware to implement this system as
clarified in Appendix D of the contract.
In Scope Modified X N/A N/A
Document
Workflow
The system must automatically assign an identifier to
CCMS generated forms, so that they can automatically
route to the appropriate work queue at BCCD, CCR&R
or SITE Administered Providers.
In Scope X CCMS-BP-DOC-
001
CCMS-USE-
DOC-001
Document
Workflow
System must allow the user with appropriate security
levels to override specific any information pre-
populated on the CCMS screens. the modules
automatically enter into any field. For example, if the
system puts in the provider address and it is incorrect
the user must be able to update the incorrect
information.
In Scope Modified Added clarification. X All All
Document
Workflow
Maintain centralized shared electronic repository with
secured access. and document management features
such as versioning, check in/check out, full text
search. Based on security levels, staff would be able to
view all documents in a case file or a provider file.
Some forms would be part of both the case file and
the provider file.
requirements (see
below).
X All All
Document
Workflow
The system will provide the following document
management features: versioning, check in/check
out, and full text search.
In Scope X All All
Document
Workflow
Some forms would be part of both the case file and
the provider file.
In Scope X All All
Document
Workflow
The proposal system must describe provide the ability
to Index the documents by multiple items, (i.e. RIN,
SSN, Case Number, Last Name and First Name,
Provider Number, Parent Last Name and First Name,
Parent Date of Birth, 2nd Parent Last Name and First
Name, 2nd Parent Date of Birth, Childs Names,
Provider Names, Family Members and Addresses).
In Scope Modified Based on JAD
session.
X CCMS-BP-DOC-
001
CCMS-USE-
DOC-001
Document
Workflow
The System software must provide a method to
manage non-indexed items.
001
CCMS-USE-
DOC-001
Requirements Traceability 1 of 32
CCMS
227782107.xlsx.ms_office
Mandatory/
Desirable
Original
Require
ment ID
New
Requirement
ID
Out of
Scope
Added/
Modified/
Deleted
Reason
E
l
i
g
i
b
i
l
i
t
y
C
u
s
t
o
m
e
r

S
e
r
v
i
c
e
P
I
Q
A
T
e
c
h
n
i
c
a
l
A
p
p
r
o
a
c
h
P
r
o
p
o
s
a
l Business
Process ID
Use Case
ID
Document
Workflow
The system must be able to customize the approval
process to move cases from one Work Queue to
another Work Queue. The system must be
customizable enough that each CCR&R can set up their
personal process flow. The system must allow for
customization of the approval process to assign
documents in a manner that is customized for a
particular agency. An administration module can
include the ability to indicate how documents are
assigned, e.g. place in generic queue for users to
select the document/case they would like to work on,
assign by last name, assign by zip code.
In Scope Modified Based on JAD
session.
X CCMS-BP-DOC-
001
CCMS-USE-
DOC-001
Document
Workflow
The system must provide the ability to capture, link
and store all case related documents (paper and
electronic) as defined in Appendix B of the General
System Design and image files in a single case jacket.
In Scope Modified Added clarification. X CCMS-BP-DOC-
001
CCMS-USE-
DOC-001
Document
Workflow
Image files can include supporting contract and
payment documents - users will have the ability to
identify the type of document that was scanned and
associate it to a case.
In Scope Added X CCMS-BP-DOC-
001
CCMS-USE-
DOC-001
Document
Workflow
Provide ability to scan documents and associated
envelopes into CCMS where client information cannot
be identified, which would be placed in a generic
queue. These documents would be available for a
worker to search, e.g. when the client calls to inquire
about a document that was never acted upon.
001
CCMS-USE-
DOC-001
Document
Workflow
If mailed document is returned as undeliverable,
provide ability to flag the document in CCMS as
undeliverable and scan in the envelope.
001
CCMS-USE-
DOC-001
Document
Workflow
The software must provide work queues for a wide
range of retrieval activities based on. Record retrieval
activities will depend on a variety of conditions, such
as user roles, user location, queue status, record
status, transfer status, and date ranges., etc. Work
queues may include unfinished records, records ready
to be authenticated, records which are late, records
which are being monitored, records which have been
assigned to an individual, etc.
In Scope Modified Added clarification
and split
requirement (see
below).
X All All
Document
Workflow
Work queues will include unfinished records, records
ready to be authenticated, records which are late,
records which are being monitored and records which
have been assigned to an individual.
In Scope X All All
Document
Workflow
Please describe your approach to work queue
processing.
In Scope Deleted Covered in first part
of Mandatory
requirement 9.
X N/A N/A
Document
Workflow
System must allow users to create and edit image file
annotations such as highlighting, stamps or sticky
notes. on image files. System security must control
who can view annotations such as highlighting, stamps
or sticky notes, and who can see through redaction.
and split
requirement (see
below).
X All All
CCMS
Mandatory/
Desirable
Original
Require
ment ID
New
Requirement
ID
Out of
Scope
Added/
Modified/
Deleted
Reason
E
l
i
g
i
b
i
l
i
t
y
C
u
s
t
o
m
e
r

S
e
r
v
i
c
e
P
I
Q
A
T
e
c
h
n
i
c
a
l
A
p
p
r
o
a
c
h
P
r
o
p
o
s
a
l Business
Process ID
Use Case
ID
Document
Workflow
System security must control who can view image
annotations such as highlighting, stamps or sticky
notes, and who can see through redaction.
In Scope X All All
Document
Workflow
All annotations must be overlaid and not change the
actual image. This way, a document can be printed
with or without the annotations.
In Scope X All All
Document
Workflow
The system must set-up "filters" that will allow users
to search for documents that are retrieved on a
regular basis, by maintaining an audit trail of access to
each image, so that the search criteria does not have
to be populated every time. This requirement will be
further defined/clarified during Detailed System
Design.
In Scope Modified X CCMS-BP-DOC-
001
CCMS-USE-
DOC-001
Document
Workflow
The CCMS must have the ability to track and manage
multiple versions of the same information.
In Scope X All All
Document
Workflow
There will be concurrent users who may collaborate
simultaneously on the same document. The system
must maintain version control and allow re-indexing as
needed. An audit trail of changes must be maintained.
In Scope X All All
Document
Workflow
Work queues must accommodate large numbers of
Active Cases. In addition to dropdown lists and
paging, work queues must be sorted and filtered.
and split
requirement (see
below).
X All All
Document
Workflow
In addition to dropdown lists and paging, work queues
must be sorted and filtered.
In Scope X All All
Document
Workflow
BCCD users must be able to add documents specified
in Appendix B or image files directly into the CCMS via
email, fax or scan. In addition, application form can be
submitted via the internet.
In Scope Modified Added clarification.
Appendix D: The
system will have
the ability to add
individual
documents to an
existing case file,
residing in the
Content Manager.
During DSD,
Deloitte will confirm
approach.
X CCMS-BP-DOC-
001
CCMS-USE-
DOC-001,
CCMS-USE-
DOC-001
N/A N/A CCMS-REQ-031 Electronic
Document
Workflow
Provide ability for staff to email or fax any form out of
CCMS, and provide a field to capture each
client/provider's delivery preference.
Out of Scope Added DHS is verifying
with Legal if bulk
emailing is possible,
and if so would like
to explore technical
options.
X N/A N/A
Desirable 1 CCMS-REQ-032 Electronic
Document
Workflow
All WEB CCMS screens should be able to switch from
English to Spanish with a simple switch. The Child Care
Application Form will be in English and Spanish and
IDHS will provide the English-to-Spanish translation.
In Scope Modified Added clarification. X CCMS-BP-ELI-
001
CCMS-USE-
DOC-001
CCMS
Mandatory/
Desirable
Original
Require
ment ID
New
Requirement
ID
Out of
Scope
Added/
Modified/
Deleted
Reason
E
l
i
g
i
b
i
l
i
t
y
C
u
s
t
o
m
e
r

S
e
r
v
i
c
e
P
I
Q
A
T
e
c
h
n
i
c
a
l
A
p
p
r
o
a
c
h
P
r
o
p
o
s
a
l Business
Process ID
Use Case
ID
Document
Workflow
The system should be designed so that it is intuitive by
the end-user. The end-users should not be required
any technical computer knowledge. The reading level
of the screens should be no higher than the eighth
grade level.
In Scope X All All
Document
Workflow
The software system should include keyboard
shortcuts that can be used to navigate screens in lieu
of mouse navigation.
In Scope X All All
Document
Workflow
The software should support frequent saves to the
database when a user is entering information so that a
minimum of information is lost if the end-users
connection is lost.
In Scope X All All
Document
Workflow
Please describe the frequency of saves to the
database. The frequency of saves will be defined
during detail design.
Document
Workflow
End-users should be able to gain full functionality from
the Web browser-based interface including: the entry
of data, the editing of data, the submission of finished
data to the database, the generation of ad hoc reports
from the database, and the printing of reports, form
letters, certificates, and other documents as might be
necessary for the conduct of business as set forth in
the other requirements specified in this document. The
User should be able to have the system Auto Tab
between fields if the field is complete; i.e. Date field.
In Scope Modified Added clarification.
Auto Tab is not
accessibility
compliant.
X All All
Document
Workflow
Clients and Certificate Providers should be able to fax
documents to a statewide 800 number that would
automatically store the document in the central
document management system.
001
CCMS-USE-
DOC-002
Document
Workflow
The System should provide a method to allow the
caseworker to attach the document to a specified
case.
001
CCMS-USE-
DOC-001,
CCMS-USE-
DOC-002
Document
Workflow
The system will have the ability to add any image
attachment to any case. The attachments will update
to the CCMS with the index information for the case it
was just attached to.
001
CCMS-USE-
DOC-001,
CCMS-USE-
DOC-002
Document
Workflow
The system will also have the ability to OCR the
Application, Rede, and COI and other forms not to
exceed a total of 10 forms (including handwritten
documents ) Documents or parse predefined Bar-
coded Documents sent as email attachments or faxes.
Handwritten documents can be scanned and stored as
images into the system and linked to the appropriate
case or provider files.
In Scope X N/A N/A
CCMS
Mandatory/
Desirable
Original
Require
ment ID
New
Requirement
ID
Out of
Scope
Added/
Modified/
Deleted
Reason
E
l
i
g
i
b
i
l
i
t
y
C
u
s
t
o
m
e
r

S
e
r
v
i
c
e
P
I
Q
A
T
e
c
h
n
i
c
a
l
A
p
p
r
o
a
c
h
P
r
o
p
o
s
a
l Business
Process ID
Use Case
ID
Document
Workflow
The System should provide a method to allow the
caseworker to attach the information to a specified
case and verify the accuracy of the recognition.
In Scope X N/A N/A
Document
Workflow
Should be capable of consolidating all completed
applications automatically from all remote sites on a
daily basis for Management and reporting. Provide a
single web-based system and not a distributed
database.
based on JAD
session.
X All All
Document
Workflow
The software should provide a window to inform users
of the number of Cases needing attention in their
various work queues. This window should be displayed
when users log into the system and should be able to
be refreshed throughout the users session. It should
be possible for users to go directly to a work queue by
clicking on the appropriate link in the window.
In Scope X All All
Workflow
The software should automatically route and transfer
Case data, under specific conditions, to different users
involved in the Approval process.
In Scope X X All All
Mandatory 15 CCMS-REQ-046 Content
Management
Any remote user BCCD, R&R or Site administrator
users requiring access to data will be granted access in
the form of Crystal Reports. should be able to
download any or all-raw data to which he/she has
been granted access to into a spreadsheet, database,
and or statistical software on the users local computer
or a format that can be loaded into the software.
In Scope Modified Clarified based on
JAD follow-on
discussion.
X All All
Management
Provide the ability to store and track image exceptions
(possible exceptions could be mismatch, duplicate,
null-values, erroneous data type). Alert User if
exception occurs in System.
requirements (see
below).
X All All
Management
Alert User if image exception occurs in System. In Scope X All All
Management
Route forms and approval processing to assigned case
manager/ provider.
Management
Have the ability to electronically transmit assign cases
or correspondence among agency program units that
are CCMS users.
Management
Provide user-friendly user interface and navigational
menus compliant with project user interface
standards. All data entry functions must operate the
same way in all modules (i.e., same function keys,
Windows tool bars).
and split
requirement (see
below).
X All All
CCMS
Mandatory/
Desirable
Original
Require
ment ID
New
Requirement
ID
Out of
Scope
Added/
Modified/
Deleted
Reason
E
l
i
g
i
b
i
l
i
t
y
C
u
s
t
o
m
e
r

S
e
r
v
i
c
e
P
I
Q
A
T
e
c
h
n
i
c
a
l
A
p
p
r
o
a
c
h
P
r
o
p
o
s
a
l Business
Process ID
Use Case
ID
Management
Provide capability for users to enter CCTS front-end
eligibility data entry (applications, re-determinations,
and changes of information, shared cases).
All Edits/Alerts included in CCTS legacy system must
be included in CCMS.
Allow users to enter data from applications onto CCMS
screens instead of CCTS. Client and other parent work
and school schedules as well as Child Care schedules
for each provider not currently on CCTS would be
added to CCMS and add necessary new Edits/Alerts.
Add new Edits/Alerts to replace current CCTS reports.
In Scope Modified Split into 7 separate
requirements.
X X N/A N/A
Management
"eligibility" data entry for applications.
In Scope X X CCMS-BP-ELI-
001
CCMS-USE-
ELI-001,
CCMS-USE-
ELI-002
Management
"eligibility" data entry for re-determinations.
002
CCMS-USE-
ELI-002,
CCMS-USE-
ELI-003,
CCMS-USE-
ELI-004
Management
"eligibility" data entry for changes of information.
003
CCMS-USE-
ELI-002,
CCMS-USE-
ELI-006,
CCMS-USE-
ELI-007
Management
"eligibility" data entry for shared cases.
004, CCMS-BP-
ELI-005, CCMS-
BP-ELI-005,
CCMS-BP-ELI-
007
CCMS-USE-
ELI-005,
CCMS-USE-
ELI-008
Management
Add new Edits/Alerts to replace current CCTS reports
as outlined in the Alerts requirements.
In Scope Modified X X All Eligibility
Business
Processes
All Eligibility
Use Cases
Management
All Edits/Alerts related to Eligibility included in CCTS
legacy system and pertinent to the screens list
documented in Appendix B must be included in CCMS.
Business
Processes
All Eligibility
Use Cases
Management
Allow users to enter data from applications onto CCMS
screens instead of CCTS. Client and other parent work
and school schedules as well as Child Care schedules
for each provider not currently on CCTS would be
added to CCMS and add necessary new Edits/Alerts.
001
CCMS-USE-
ELI-001,
CCMS-USE-
ELI-002
Management
For informational purposes, CCMS will provide a field
to record a related case number, e.g. RPY case, joint
custody cases, shared case to determine correct co-
pay.
Business
Processes
All Eligibility
Use Cases
CCMS
Mandatory/
Desirable
Original
Require
ment ID
New
Requirement
ID
Out of
Scope
Added/
Modified/
Deleted
Reason
E
l
i
g
i
b
i
l
i
t
y
C
u
s
t
o
m
e
r

S
e
r
v
i
c
e
P
I
Q
A
T
e
c
h
n
i
c
a
l
A
p
p
r
o
a
c
h
P
r
o
p
o
s
a
l Business
Process ID
Use Case
ID
Management
CCTS front-end provider data entry (including rates),
edits and provider documentation tracking would be
moved to CCMS. All Provider edits included on the 4
provider screens in the Child Care Tracking System
Legacy System must be included in the Provider
system. Specific data that users should be able to
enter in CCMS includes the ability to store multiple
provider addresses (e.g. billing address, second
address), enter both a provider's SSN and FEIN
(system should link these to prevent duplicate
providers in the system).
In Scope Modified Added detail. X CCMS-BP-ELI-
008
CCMS-USE-
ELI-009
N/A N/A CCMS-REQ-062 Content
Management
Provide ability in CCMS to attach screenshots
automatically to an electronic case file and label.
Out of Scope Added Users will be able to
take screenshots
and scan into
CCMS, but
providing ability to
take screenshots
from CCMS and
upload would need
to be custom
coded. It is needed
since there are
limited printers for
staff and DHS
would like to
explore options.
X N/A N/A
Management
Currently an approval/denial/cancellation notice is
generated out of CCTS and given to the parent,
provider and R&R. CCTS will continue to generate
these notices and upload them to Mobius system, and
CCMS will store copies of the notices to view online via
CCMS.
In Scope Added X N/A N/A
Management
CCMS should link a providers SSN and FEIN for
existing providers to identify duplicate providers, and
display addresses associated with each, but neither of
these will used as unique identifiers. RINs will be used
as unique identifiers for providers by utilizing the
existing process for creating RINs.
In Scope Added X CCMS-BP-ELI-
008
CCMS-USE-
ELI-009
Management
When a provider's certification status is approved,
automatically generate certificate for the current
month.
Out of Scope Added Wish list item. X N/A N/A
CCMS
Mandatory/
Desirable
Original
Require
ment ID
New
Requirement
ID
Out of
Scope
Added/
Modified/
Deleted
Reason
E
l
i
g
i
b
i
l
i
t
y
C
u
s
t
o
m
e
r

S
e
r
v
i
c
e
P
I
Q
A
T
e
c
h
n
i
c
a
l
A
p
p
r
o
a
c
h
P
r
o
p
o
s
a
l Business
Process ID
Use Case
ID
Management
CCMS should automatically generate a supplemental
certificate when individuals are added to a case after
the initial batch runs, and send supplemental
certificate for each necessary month. This is only for
centers (codes 760, 761).
Out of Scope Added X N/A N/A
Management
Provide ability for parents to enter a change of address
online via CCMS.
Out of Scope Added Further DHS
internal discussion
needed.MIS to
review Finalist real-
time functionality.
The following notes
have been added
for future BCCD-
Deloitte reference:
How far reaching is
this address
change? How can
BCCD changes be
incorporated into
other IDHS
programs?
Deborah
Levi/Jeremy
Margaron to
discuss.
X N/A N/A
Management
For eligible parents under non-TANF
education/training, provide CCMS screens to enter and
track education data, including history.
Out of Scope Added The following notes
have been added
for future BCCD-
Deloitte reference:
Item to be included
in database
discussion.
X N/A N/A
Management
Denial or cancellation notice should be automatically
sent out if case document not scanned in by the X
business day (the number of days should be
customizable by each R&R/Site). Also provide ability to
stop notice from being generated.
Out of Scope Added Not needed -
generating an alert
when an app/re-de
should be denied or
cancelled is
sufficient.
X N/A N/A
Management
Provide an override ability in CCMS to re-open denied
applications that are past 30 days from 1st RAI being
sent. , e.g. when an appeal is approved and BCCD
appeals coordinator needs to override the denial.
Out of Scope Added Wish list item. X N/A N/A
Management
When a child is enrolled with a headstart provider and
the system identifies the child has a sibling in a non-
headstart provider, update sibling's care to match the
headstart child, e.g. headstart child is eligible for care
for 1 year but non-Headstart sibling should be able to
get 1 year of care as well.
Out of Scope Added Low priority wish
list item.
X N/A N/A
CCMS
Mandatory/
Desirable
Original
Require
ment ID
New
Requirement
ID
Out of
Scope
Added/
Modified/
Deleted
Reason
E
l
i
g
i
b
i
l
i
t
y
C
u
s
t
o
m
e
r

S
e
r
v
i
c
e
P
I
Q
A
T
e
c
h
n
i
c
a
l
A
p
p
r
o
a
c
h
P
r
o
p
o
s
a
l Business
Process ID
Use Case
ID
Management
For shared cases, since one re-de is typically
completed per elibility period if there are multiple
cases, if re-de not returned in X business days,
generate cancellation notice and cancel both cases.
list item, but would
like alert to remind
worker to cancel
both cases, which
has been included
in the Alerts list in
the GSD Appendix.
X N/A N/A
Management
If a client moves and they need to complete a new
application, automatically generate a letter/application
that includes the client's new R&R, so the client sends
documents back to the new R&R.
In Scope Added Dependent upon
where address
changes occur and
if this can be
triggered -
determine in DSD.
X CCMS-BP-ELI-
001
CCMS-USE-
ELI-001
Management
Provide ability in CCMS for parents and non-contracted
providers to have the ability to view the status of their
cases online, in which they would have access to only
their own cases after creating a login account. Also
display client's caseworker and contact information.
Out of Scope Added DHS internal
discussion needed
regarding parent
portal.
X N/A N/A
Management
Provide a parent/non-contracted provider CCMS
dashboard where forms can be retrieved, e.g. change
of address/change of information/etc., as well as
general program information.
discussion needed
regarding parent
portal.
X N/A N/A
Management
Provide ability in CCMS for parents/non-contracted
providers to be able to see details of information
requested as part of RAI process, including why RAI
forms are requested. This should be separate from
case notes.
discussion needed
regarding parent
portal.
X N/A N/A
Management
Provide interface with web-services based posotal
preferred software (Finalist) for all client and provider
addresses. When staff entrers the address information
on the screen, the address entered would be overlaid
with the postal preferred address. All During Detailed
System Design BCCD will identify the forms and letters
printed that must have postal preferred addresses.
In Scope Modified Added clarification. X All Eligibility
Business
Processes
All Eligibility
Use Cases
Management
Provide a link with CCTS front end Reports to have a
reporting component with standardized reports as
identified in Appendix B of this document.
Management
Provide the ability for any users to generate summary
and detailed statistical and productivity reports as
defined in Appendix B of the General System Design.
related to each component of this RFP.
Management
Users will have ability to create ad- hoc reports based
on Indexed fields and data items as defined in
Appendix B of the General System Design.
CCMS
Mandatory/
Desirable
Original
Require
ment ID
New
Requirement
ID
Out of
Scope
Added/
Modified/
Deleted
Reason
E
l
i
g
i
b
i
l
i
t
y
C
u
s
t
o
m
e
r

S
e
r
v
i
c
e
P
I
Q
A
T
e
c
h
n
i
c
a
l
A
p
p
r
o
a
c
h
P
r
o
p
o
s
a
l Business
Process ID
Use Case
ID
Management
The CCMS systems must link with the CCTS and other
systems to standardize access to other applications,
enabling data to be easily transferred between the
CCMS and applications such as word-processors and e-
mail in a manner that avoids the difficulties that arise
from non-conforming file formats.
In Scope Deleted System interface
requirements are
individually
identified and
makes this
requirement
redundant.
X N/A N/A
Management
Set up near or real-time application-to-approval
process by maximizing use of an online interface.
001
CCMS-USE-
ELI-001,
CCMS-USE-
ELI-002
Management
The software must provide for the assignment of data
fields as mandatory or optional.
In Scope X All All
Management
Must store the Date, Time, and the person who
uploads a document each time a document is added to
the system.
001
CCMS-USE-
DOC-001,
CCMS-USE-
DOC-002
Management
The system must maintain an audit trail of all actions
and documents generated as dictated by business
needs and defined during detail design.
Management
System must have a case notes component, that
includes the ability to add provider notes, with security
roles/levels.
In Scope Modified Added clarification. X X X X All All
Management
Provide a read and write real time, near real-time or
batch interface to communicate with the CCTS legacy
mainframe IMS system.
In Scope Modified Added clarification. X X All Eligibility
Business
Processes
All Eligibility
Use Cases
Management
Provide a read-only query interface with the City of
Chicagos current Web-based system.
In Scope X All Eligibility
Business
Processes
All Eligibility
Use Cases
Management
Provide a read-only interface link or in screen-scrape
with the States Consolidated Accounting and
Reporting System (CARS), (CICS/VSAM).
Business
Processes
All Eligibility
Use Cases
Management
Provide a read-only interface link with the States
IPACS, AWVS, ACID, and KIDS., SAMS Mainframe
Online Systems.
In Scope Modified Split requirement
and deleted SAMS
interface based on
JAD session.
X All Eligibility
Business
Processes
All Eligibility
Use Cases
Management
AWVS system.
Business
Processes
All Eligibility
Use Cases
Management
Provide a read-only interface link with the States ACID
system.
Business
Processes
All Eligibility
Use Cases
Management
Provide a read-only interface link with the States KIDS
system.
Business
Processes
All Eligibility
Use Cases
Management
SAMS Mainframe Online system.
In Scope Deleted X N/A N/A
Management
Provide field-sensitive online help information for each
screen, and the ability to edit same as business rules
change. Provide link to policy manual.
CCMS
Mandatory/
Desirable
Original
Require
ment ID
New
Requirement
ID
Out of
Scope
Added/
Modified/
Deleted
Reason
E
l
i
g
i
b
i
l
i
t
y
C
u
s
t
o
m
e
r

S
e
r
v
i
c
e
P
I
Q
A
T
e
c
h
n
i
c
a
l
A
p
p
r
o
a
c
h
P
r
o
p
o
s
a
l Business
Process ID
Use Case
ID
N/A N/A CCMS-REQ-096 Interface A two-way interface between CCTS and QRS system
currently exists. The CCMS system will provide a data
field or flag to display QRS data. Alternately, the
CCMS system will acquire QRS data through a web
service developed by INCCRRA's DTP system.
have been added
for future BCCD-
Deloitte reference:
Dons
understanding is
that this was
pertaining to the
existing export they
do to MIS to
populate the Quality
Rating data for
providers. His notes
say that INCCRRAs
DTP system will
expose a secure
web service that
would allow, once
the CCMS unique id
was entered into
their system for a
specific provider,
CCMS to retrieve
the QRS
information from
their system on a
per-provider basis.
X All All
N/A N/A CCMS-REQ-097 Interface Provide one-way interface between CCTS and DTS for
the purpose of transmitting information on providers
in child care program.
Out of Scope Added X All All
Management
The system must provide a mechanism to back up and
store all information within the CCMS on a daily and
weekly basis.
In Scope X All All
Management
System must interface and link with existing CCTS for
email, fax, and postal addresses to enable the printing
of correct addresses and other pertinent information
on reports and notifications.
Business
Processes
All Eligibility
Use Cases
Management
The system must be capable of importing/exporting
selected data via an interface, to/ from other IDHS
Systems and other agencies NACCRAWARE and
INCCRRA.
TBD Modified Added clarification
based on JAD
session.
X All All
Management
Provide a(n) expandable data mart(s) to be used for
investigative reporting of the information contained in
the transactional CCMS data. This will be based on
business questions gathered during detail design and
will result in reports that are part of the 30 reports
proposed for this initiative.
based on JAD
session.
X All All
Management
Provide ability to generate supporting contract and
payment documents out of CCMS. When they are
scanned, the system should automatically identify the
document type and associate the document to an
appropriate checklist. Generate a workflow/alerts to
users as documents are scanned.
Out of Scope Added N/A N/A
Desirable 12 CCMS-REQ-103 Content
Management
The System should have ability to pre-populate entry
fields with known data. Once the User enters a Key
Index Item the system would populate all related data
fields.
In Scope X All All
CCMS
Mandatory/
Desirable
Original
Require
ment ID
New
Requirement
ID
Out of
Scope
Added/
Modified/
Deleted
Reason
E
l
i
g
i
b
i
l
i
t
y
C
u
s
t
o
m
e
r

S
e
r
v
i
c
e
P
I
Q
A
T
e
c
h
n
i
c
a
l
A
p
p
r
o
a
c
h
P
r
o
p
o
s
a
l Business
Process ID
Use Case
ID
Management
Should allow the user to switch to another application
and still maintain position in the original application.
001
CCMS-USE-
ELI-001
Management
System must have the capability to scan and store a
generated payment certificate from CCTS in the
proposed system with the ability to print that
certificate on demand.
001
CCMS-USE-
DOC-001
Management
Any remote user should be able to download any or all-
raw data to which he/she has been granted access to
into a spreadsheet, database, and or statistical
software on the users local computer or a format that
can be loaded into the software.
In Scope Deleted Duplicate
requirement - same
as Mandatory 15.
X N/A N/A
Management
Provide a table to store all program violation
information that the CCMS system will check to verify.
In Scope X All PIQA
Business
Processes
All PIQA Use
Cases
Management
All fields in the system Database should be searchable. In Scope X All All
Mandatory 42 CCMS-REQ-109 Customer
Service Content
Management
System must provide ability to perform CCTS front-
end CANTS forms background processing and
tracking by staff members. System must provide an
indicator in CCMS for users to update when a
CANTS/SORS/Criminal check has taken place, and
users can scan in any related documents as images
with no data extraction.
008
CCMS-USE-
ELI-009
Service Content
Management
See Use Case attachment Provider Application. This
will provide the information that has to be captured in
the CCMS system. CCMS will provide the ability to
enter provider data currently entered on CCTS
screens: Provider Index, Provider List, App/Re-de
Provider Entry/Update, Approval Provider Update.
In Scope Modified Use cases ended up
not being included
in the RFP (business
flows replaced).
Added clarification/
detail.
X CCMS-BP-ELI-
008
CCMS-USE-
ELI-009
Desirable 39 CCMS-REQ-111 Alerts Content
Management
Provide the ability to search for case by the Parents
name, a childs name, a case number or Provider
number SSN/FEIN/RIN or address. Vendor should
provide a separate lookup screen accessed by hitting
the binoculars next to the Case Number text box on
the main screen. User should be able to access
information by Type: (i.e. Applications, Re-
Determinations, Requests for Additional Information,
miscellaneous, Family Members Names).
Business
Processes
All Eligibility
Use Cases
Management
The system should allow the entry of child times and
calculate the capacity of a provider at each address
(for license-home, license-exempt and centers). The
system should also provide access to check other
systems (CCTS System, the City of Chicago System
COPA, CCMIS, IMEDGE) and the IPACS System) to
verify capacity and provide comment if necessary.
In Scope Modified Added detail. X CCMS-BP-ELI-
008
CCMS-USE-
ELI-009
CCMS
Mandatory/
Desirable
Original
Require
ment ID
New
Requirement
ID
Out of
Scope
Added/
Modified/
Deleted
Reason
E
l
i
g
i
b
i
l
i
t
y
C
u
s
t
o
m
e
r

S
e
r
v
i
c
e
P
I
Q
A
T
e
c
h
n
i
c
a
l
A
p
p
r
o
a
c
h
P
r
o
p
o
s
a
l Business
Process ID
Use Case
ID
Management
Provide a screen to enter the employment information,
should match the employment form used by BCCD
today. This would include School Schedule information
and travel time currently in the SPARE CCTS Web
system.
In Scope X CCMS-BP-ELI-
001
CCMS-USE-
DOC-001,
CCMS-USE-
ELI-001
Service
The system will automatically assign a tracking
number, distribute to appropriate staff Queues and to
move the process along in a timely manner and track
timeliness of tasks.
In Scope Modified Added clarification. X X All Customer
Service
Business
Processes
All Customer
Service Use
Cases
Service
The system must provide a venue for BCCD and
provider staffs to enter customer service requests, e.g
complaints or questions. Provide ability for user to
select request type/sub-type and to associate request
to a case or provider.
In Scope Modified Added detail. X CCMS-BP-CS-
001
CCMS-USE-
CS-001
Service
CCTS front end Appeals processing including data
entry with edits and attachments, Appeal information
must be entered into the front end system and routed
to staff to move the process along in a timely manner.
Both BCCD staff and providers with appropriate
security level will have the ability to view progress of
case.
In Scope X X CCMS-BP-CS-
004
CCMS-USE-
CS-004
Service
System must provide ability to complete W9
processing by providing a link to the IRS site to
retrieve the W9 form, users can scan the completed
W9 form and related documents as images with no
data extraction. to include data entry with edits and
attachments. The W9 form can be annotated with
comments for users to identify missing information.
In Scope Modified Added detail. X X CCMS-BP-ELI-
010
CCMS-USE-
ELI-012
Service
See Use Case Appendix W9 Error Processing. The
data for the W9 form and its related edits have to be
accounted for in the CCMS System.
In Scope Deleted Use cases ended up
not being included
in the RFP (business
flows replaced). W9
data edits cannot
be included in the
CCMS because the
W9 is an IRS-owned
form.
X N/A N/A
Desirable 18 CCMS-REQ-119 Customer
Service
The CCMS should provide a policy lookup feature
connected to each field. Provide link to policy manual.
based on JAD
session.
X X All Customer
Service
Business
Processes
All Customer
Service Use
Cases
Desirable 18 CCMS-REQ-120 Customer
Service
IDHS should have ability to update the policy
information to the lookup tables.
In Scope X X All Customer
Service
Business
Processes
All Customer
Service Use
Cases
N/A N/A CCMS-REQ-121 Customer
Service
Provide ability in CCMS for parents and non-contracted
providers to enter complaints/inquiries online.
discussion needed
regarding parent
portal.
X N/A N/A
CCMS
Mandatory/
Desirable
Original
Require
ment ID
New
Requirement
ID
Out of
Scope
Added/
Modified/
Deleted
Reason
E
l
i
g
i
b
i
l
i
t
y
C
u
s
t
o
m
e
r

S
e
r
v
i
c
e
P
I
Q
A
T
e
c
h
n
i
c
a
l
A
p
p
r
o
a
c
h
P
r
o
p
o
s
a
l Business
Process ID
Use Case
ID
N/A N/A CCMS-REQ-122 Customer
Service
Interface with BAH system to determine whether an
appeal was withdrawn and send BAH forms that have
are scanned into CCMS. The BAH interface could also
potentially be used to notify BCCD/CCR&R/Site that
client has filed an appeal.
list item.
X N/A N/A
Mandatory 43 CCMS-REQ-123 Program
Integrity &
Quality
Assurance
Identify and track each non-compliant case. Record
investigation actions and outcomes.
In Scope X All PIQA
Business
Processes
All PIQA Use
Cases
Integrity &
Quality
Assurance
Vendor must provide a Web-based software solution to
track child care program violations from a initial
discovery or inquiry phase to submission to the
Attorney General to include; forgery, overpayment and
fraud.
In Scope X All PIQA
Business
Processes
All PIQA Use
Cases
Integrity &
Quality
Assurance /
Customer
Service
Automatically calculate overpayments and
administrative penalties. Provide ability in CCMS to
track overpayment status (within BCCD) and reasons,
which include client error, provider error, or
administrative error, as well as sub-reasons. Provide
screen for users to identify case data related to an
overpayment and administrative fees, e.g. who was
overpaid, month, children, and calculate difference of
actual vs. planned.
In Scope Modified Added clarification/
detail.
X CCMS-BP-CS-
002
CCMS-BP-CS-
003
CCMS-USE-
CS-002
CCMS-USE-
CS-003
N/A N/A CCMS-REQ-126 Program
Integrity &
Quality
Assurance
Automate PIQA monitoring report. The Excel tool
currently links identifying cells like Name between
Worksheets.
have been added
for future BCCD-
Deloitte reference:
BCCD needs the
functionality.
X N/A N/A
Desirable N/A CCMS-REQ-
126a
Program
Integrity &
Quality
Assurance
The system will provide a data extract that can be
used to pre-populate Rosters in the existing Excel-
based PIQA Monitoring Tool.
In Scope Added X X
Desirable 19 CCMS-REQ-127 Fraud
Management &
Tracking (PIQA)
Have system check The system will provide a link to
the local White Pages or Yellow Pages for the
Employee Phone Number of the company the Client
has listed or check the system for other clients with
similar employer.
In Scope Modified Added clarification. X All PIQA
Business
Processes
All PIQA Use
Cases
Management &
Tracking (PIQA)
Provide a way to assign levels of Sanctions on
Providers and Clients.
In Scope X CCMS-BP-PIQA-
004, CCMS-BP-
PIQA-005
CCMS-USE-
PIQA-004,
CCMS-USE-
PIQA-005
Management &
Tracking (PIQA)
Provide a way for a Provider to be sanctioned, (i.e. a 6
month probation or 1 year status with no violations).
In Scope X CCMS-BP-PIQA-
004, CCMS-BP-
PIQA-005
CCMS-USE-
PIQA-004,
CCMS-USE-
PIQA-005
CCMS
Mandatory/
Desirable
Original
Require
ment ID
New
Requirement
ID
Out of
Scope
Added/
Modified/
Deleted
Reason
E
l
i
g
i
b
i
l
i
t
y
C
u
s
t
o
m
e
r

S
e
r
v
i
c
e
P
I
Q
A
T
e
c
h
n
i
c
a
l
A
p
p
r
o
a
c
h
P
r
o
p
o
s
a
l Business
Process ID
Use Case
ID
Management &
Tracking (PIQA)
Provide special security for employees that are either a
provider or client. Allow ability to block access or read
only.
In Scope X X All PIQA
Business
Processes
All PIQA Use
Cases
Management &
Tracking (PIQA)
Ability to move a case to a Fraud/Violations area of the
system and restrict access to case records.
In Scope X X CCMS-BP-PIQA-
004, CCMS-BP-
PIQA-005
CCMS-USE-
PIQA-004,
CCMS-USE-
PIQA-005
Management &
Tracking (PIQA)
Provider option to restrict access to case notes. In Scope X X All PIQA
Business
Processes
All PIQA Use
Cases
Management &
Tracking (PIQA)
The ability to lock a case from all users view and flag it
as a Program Violation.
004, CCMS-BP-
PIQA-005
CCMS-USE-
PIQA-004,
CCMS-USE-
PIQA-005
Management &
Tracking (PIQA)
The ability of the Fraud Provider Sanction system to
check the Provider, Addresses, Employer, Children
names, Parent Names, to send an alert if any name on
this table are used.
004, CCMS-BP-
PIQA-005
CCMS-USE-
PIQA-004,
CCMS-USE-
PIQA-005
Desirable 27 CCMS-REQ-135 Alerts Ability to send an Alert or basic message to a specific
user or all users over the CCMS system. The ability to
send based on search fields Providers, Countys,
Sites, CCR&Rs and to All users.
In Scope X All CCMS-USE-
GEN-001
Desirable 28 CCMS-REQ-136 Alerts Track the receipt of documents into the document
management System, as defined in Appendix B, and
alert supervisor of any action required to include
delayed response by more than the required amount
of days.
In Scope Modified Added clarification. X All CCMS-USE-
GEN-001
Desirable 29 CCMS-REQ-137 Alerts Should be capable of flagging a list of user-defined
critical or panic results and automatically prompt pre-
determined responses. Provide a generic queue for
each location that can be sorted and filtered.
based on JAD follow-
up discussion and
added another
requirement (see
below).
X All CCMS-USE-
GEN-001
Desirable 29 CCMS-REQ-138 Alerts Provide ability to escalate tasks to another queue. In Scope Modified X All CCMS-USE-
GEN-001
Desirable 30 CCMS-REQ-139 Alerts The software system should provide error messages to
the end-user when data entered into a field is not
valid. The error messages should be editable by IDHS
system administrators.
GEN-001
Desirable 31 CCMS-REQ-140 Alerts Individual provider sites should have the ability to turn
on or off non-mandatory alerts.
GEN-001
Desirable 32 CCMS-REQ-141 Alerts Generate alerts to the users work Queue or email for
pending cases and actions, as defined in Appendix B -
Assign task to user and if worker does not take action
within X number of days (based on how agency is
configured), escalate task to another queue, e.g. to
supervisor.
GEN-001
CCMS
Mandatory/
Desirable
Original
Require
ment ID
New
Requirement
ID
Out of
Scope
Added/
Modified/
Deleted
Reason
E
l
i
g
i
b
i
l
i
t
y
C
u
s
t
o
m
e
r

S
e
r
v
i
c
e
P
I
Q
A
T
e
c
h
n
i
c
a
l
A
p
p
r
o
a
c
h
P
r
o
p
o
s
a
l Business
Process ID
Use Case
ID
Desirable 33 CCMS-REQ-142 Alerts System will move the case into a review area for
children when their age changes and it affects their
rates, (i.e. age 2, 3, 5, 6, 13, 18) - only alert at 6 if
child not enrolled in kindergarten if worker has
indicated not to review again.
Business
Processes
CCMS-USE-
GEN-001
Desirable 34 CCMS-REQ-143 Alerts Ability to customize alerts defined in the GSD, at the
agency level, by turning on and off the alert and set
the number of days to set the alert, if a Request for
Additional information was sent out and it has been 7
to 10 days since and no information has been received
to identify the case in a work Q. The users work Q
screen should show cases that need work today and
cases in a pending status by date. BCCD to define
days range and R&R/Site to select the number of days
from that range.
In Scope Modified Added clarification. X X X X All CCMS-USE-
GEN-001
Desirable 34 CCMS-REQ-144 Alerts The system should have the ability for the BCCD staff
to prevent some Alerts from being turned off.
Mandatory Alerts cannot be changed.
GEN-001
Desirable 35 CCMS-REQ-145 Alerts Alert if a SSN or Client or other family member is used
on another Case.
In Scope X X X X All CCMS-USE-
GEN-001
Desirable 36 CCMS-REQ-146 Alerts Alert if the Client has information on another system
such as TANF and vital information on that system has
changed. We would like an Alert Web Service that
other systems could update with changes to RIN
numbers that have multiple cases. This process would
work with the City of Chicago Systems (CCMIS, COPA,
IMEDGE), Consolidated Accounting and Reporting
System (CARS), Head Start, and Quality Rating
System (QRS).
TBD DHS internal
discussion needed.
X All Eligibility
Business
Processes
All Eligibility
Use Cases,
CCMS-USE-
GEN-001
Desirable 37 CCMS-REQ-147 Alerts Alert if an Overpayment has not been received in
15/30 days.
In Scope X CCMS-BP-CS-
002, CCMS-BP-
CS-003
CCMS-USE-
CS-002,
CCMS-USE-
CS-003,
CCMS-USE-
GEN-001
Desirable 38 CCMS-REQ-148 Alerts Alert if a TIN Tax I.D. Number mismatch. In Scope Deleted DHS verifying this
can be deleted.
X All Eligibility
Business
Processes
All Eligibility
Use Cases,
CCMS-USE-
GEN-001
Desirable 40 CCMS-REQ-149 Alerts The system should show the date and time of the
other system checks and results of those checks.
GEN-001
Desirable 41 CCMS-REQ-150 Alerts Move Case to Work Queue and notify user the End-
Date is up as defined in Appendix B.
GEN-001
N/A N/A CCMS-REQ-151 Alerts If overpayment denied, CCMS should alert CCR&R/site
that it was denied and the case/provider file should be
unflagged as an overpayment file.
In Scope Added X CCMS-BP-CS-
002
CCMS-BP-CS-
003
CCMS-USE-
CS-002
CCMS-USE-
CS-003
CCMS-USE-
GEN-001
N/A N/A CCMS-REQ-152 Alerts If overpayment denied, CCMS should alert CCR&R/site
that it was denied and the case/provider file should be
unflagged as an overpayment file.
In Scope Added X CCMS-BP-CS-
002
CCMS-BP-CS-
003
CCMS-USE-
CS-002
CCMS-USE-
CS-003
CCMS
Mandatory/
Desirable
Original
Require
ment ID
New
Requirement
ID
Out of
Scope
Added/
Modified/
Deleted
Reason
E
l
i
g
i
b
i
l
i
t
y
C
u
s
t
o
m
e
r

S
e
r
v
i
c
e
P
I
Q
A
T
e
c
h
n
i
c
a
l
A
p
p
r
o
a
c
h
P
r
o
p
o
s
a
l Business
Process ID
Use Case
ID
N/A N/A CCMS-REQ-153 Alerts BCCD should have the ability to override an alert from
being turned off at a particular R&R/Site.
have been added
for future BCCD-
Deloitte reference:
BCCD needs the
functionality.
X N/A N/A
Mandatory 45 CCMS-REQ-154 Reporting and
Historical Data
System must maintain historical data in two states:
current data and historical data. Current Data is
applications or other forms that have not been
reported on and or are not more than five years old
and is readily available. The system will provide real
time or near real time access to application data that
is not more than five years old. If a case is no longer
active and more than 5 years old, it should still be
accessible if technically feasible but not in real or near
real time. Provide ability to flag cases that always
need to be real or near real time accessible.
based on JAD
session.
X All All
Historical Data
The system must have the ability to retrieve historical
data with a recall process. Archive Data is data over
five years old. Archive Data must be accessible online
or off-line for up to ten years or indefinitely for Fraud
Cases, depending on the program area.
The CCMS reporting database tables will provide a
mechanism to differentiate between the current and
historical data using effective date fields and/or
current-history indicators.
The CCMS system will provide online access to current
and historical data subject to the archival criteria.
(see below).
X All All
Historical Data
System must support all standard data entry record
maintenance functions associated with database
management systems. For example: transaction log
recovery, reorganization of the database, back ups,
recovery, re-indexing, importing and exporting.
In Scope X All All
Historical Data
Must allow audit searches based on keyword, user, or
workstation for user-defined periods of time or area of
practice (Eligibility, PIQA or Customer Service).
Historical Data
Allow users to self-subscribe to access standard
program reports within the limits of their authorization
level.
Historical Data
Provide and maintain historical reports for all CCMS
systems in daily, weekly and monthly summaries that
can be stored, viewed and printed for a minimum of 6
months.
Historical Data
Allow users to generate management and view Ad Hoc
reports and deliver them to multiple desktop PCs and
allow web-based access.
Historical Data
Provide the ability to export all report data to other
programs such as Excel.
Historical Data
Allow users the ability to print hard copies of all
reports currently located in the CCTS System. CCMS
will provide a link to Mobius to enable printing of CCTS
reports stored in Mobius.
based on JAD follow-
up session.
X All Eligibility
Business
Processes
All Eligibility
Use Cases
CCMS
Mandatory/
Desirable
Original
Require
ment ID
New
Requirement
ID
Out of
Scope
Added/
Modified/
Deleted
Reason
E
l
i
g
i
b
i
l
i
t
y
C
u
s
t
o
m
e
r

S
e
r
v
i
c
e
P
I
Q
A
T
e
c
h
n
i
c
a
l
A
p
p
r
o
a
c
h
P
r
o
p
o
s
a
l Business
Process ID
Use Case
ID
Historical Data
The System must be able to track and make available
all changes made to the Database as dictated by
business needs and identified during detail design.
Historical Data
Documents within this system must be easily printable
and viewable on the screen with the capability to
enlarge for easier viewing.
In Scope X All All
Desirable 43 CCMS-REQ-165 Reporting &
Historical Data
The user must have the ability to enter on a CCMS
wage verification screen the employment verification
calls, dates, times, person making calls placed on
cases, person contacted and job title of person
contacted.
Business
Processes
All Eligibility
Use Cases
Historical Data
Should maintain the History of Documents within the
system.
In Scope X All All
Historical Data
History of case results can only be edited or changed
by authorized users but the module CCMS must
maintain a record of all initially entered results,
verified results and any changed results with an audit
trail of all personnel entering or changing data as
dictated by the business need and defined during
detail design and case notes will be used to add
additional information on the record.
based on JAD
session follow-up.
X All All
Historical Data
The software should save a report to a file. In Scope X All All
Historical Data
The software should provide search lookup
capabilities. The ability to search the list of Providers,
Employers, Cities, and any other key field identified by
the Purchaser in the system.
In Scope X All All
Desirable 81 CCMS-REQ-170 Reporting and
Event
Monitoring
Should interface and link with existing CCTS for email,
fax, and postal addresses to enable the printing of
correct addresses and other pertinent information on
reports and notifications.
Business
Processes
All Eligibility
Use Cases
Mandatory 54 CCMS-REQ-171 Printing
Requirements
CCMS Software must link with Scanner/Imprinter to
enter a Date Time Group on to the original document,
and automatically stamp ID of who entered document.
001
CCMS-USE-
DOC-001
Requirements
Provide a forms/letters component. Staff would
request standardized forms/letters on the CCMS for all
correspondence specified in Appendix B to
clients/providers to manage cases.
In Scope Modified Added clarification. X X X X All All
Requirements
Allow the option to print forms locally or centrally to
IDHS Mail Processing.
In Scope X All All
Desirable 48 CCMS-REQ-174 Printing
Requirements
The software should have a Print Log, in which a
generic transaction log can be utilized. that will do the
following at a minimum:
In Scope Modified Separated into 5
requirements.
X All All
Requirements
It should be possible to add comments to the Print Log
record.
In Scope X All All
Requirements
It should be possible to search for and display log
records according to criteria designated by IDHS.
In Scope X All All
CCMS
Mandatory/
Desirable
Original
Require
ment ID
New
Requirement
ID
Out of
Scope
Added/
Modified/
Deleted
Reason
E
l
i
g
i
b
i
l
i
t
y
C
u
s
t
o
m
e
r

S
e
r
v
i
c
e
P
I
Q
A
T
e
c
h
n
i
c
a
l
A
p
p
r
o
a
c
h
P
r
o
p
o
s
a
l Business
Process ID
Use Case
ID
Requirements
The log record should contain enough identifying
information to trace the person and location printing a
certification.
In Scope X All All
Requirements
All log records should be locked to changes. In Scope X All All
Requirements
Should have the ability to print screen in every module
to capture exact display.
In Scope X All All
Requirements
Should have a print function for Ad hoc reporting,
allowing for a variety of ways to sort the data based
on fields such as a date, provider, applicant, and or
open cases.
In Scope X All All
Requirements
Each report must have a standardized header and
signature format, which can be customized by location
and function.
In Scope X All All
Requirements
System should have the ability to produce on-demand
screen prints from any workstation.
In Scope X All All
Mandatory 56 CCMS-REQ-183 Hardware/
Software
Assist, if requested, with the installation of hardware
purchased by the State. This requirement does not
include providing or installing end-user hardware.
In Scope X N/A N/A
Software
The software must provide utilities to enter CCMS
support table data and perform validity checks on data
fields.
In Scope Modified Added clarification. X N/A N/A
Software
Provide a detailed explanation of the licensing
requirements of the software system in total. This
licensing detail must include an explanation of all of
the following that apply: end user licensing, software
module licensing, concurrent user licensing, per-user
licensing, per-seat licensing, per-server licensing, third-
party software licensing, and other licensing
requirements. This licensing must be fully transferable
and extendable.
In Scope X N/A N/A
Software
List all third party software that will run on the State's
environment. If the software is modular, then the
individual modules must be identified and the list must
indicate if they are required or optional modules. The
list shall specify the following:
The name of the software.
The version of the software.
The platform that the software will run on.
If the software is a module.
If the software is a module then is it a required
module.
Is the software proprietary, open source or third
party?
Will the Vendor support the software?
In Scope X N/A N/A
Software
Fully specify the hardware necessary to support 1,200
concurrent users with update access and 200,000
users with view access. Please specify the software
necessary for successful implementation to meet
performance and reliability requirements.
In Scope X N/A N/A
Software
The system must be scaleable. The Vendor must state
the minimum and maximum number of concurrent
users the system will support.
In Scope X N/A N/A
CCMS
Mandatory/
Desirable
Original
Require
ment ID
New
Requirement
ID
Out of
Scope
Added/
Modified/
Deleted
Reason
E
l
i
g
i
b
i
l
i
t
y
C
u
s
t
o
m
e
r

S
e
r
v
i
c
e
P
I
Q
A
T
e
c
h
n
i
c
a
l
A
p
p
r
o
a
c
h
P
r
o
p
o
s
a
l Business
Process ID
Use Case
ID
Software
Provide clear, detailed documentation of any hardware
and software. This may include documentation from
third party manufacturers when the Vendor has
provided third-party hardware and/or software
solutions as part of the proposed system installation.
In Scope X N/A N/A
Software
Vendor agrees they will be responsible for the costs of
any additional hardware needed to support the
requirements of this RFP not listed above.
In Scope X N/A N/A
Software
The Vendor proposed hardware and software will be
hosted by the Department of Central Management
Services (CMS) as part of a
centralization/consolidation plan. CMS will act as the
application service provider for the Agency. CMS will
provide all hardware necessary to support the
proposed solution. The Vendor will be expected to
provide system requirements and to work with the
Agency and CMS on the specification, installation, and
configuration of the systems hardware and software.
In Scope X N/A N/A
Software
The average transaction response time during peak
and non-peak periods must be less than 3 seconds on
all systems. IDHS will categorize each CCMS
transaction and define response time on a case-by-
case basis during detailed system design phase.
Software
Provide a tool foundational model that is scalable
enough to be re-used by DHS personnel to develop
scripts solutions for other functional areas of the
organization.
Software
The Agency will require the winning Vendor to certify
in writing, in conjunction with the State, that all
hardware and software installed by the Vendor is
functioning correctly at the end of the project.
In Scope X N/A N/A
Software
Provide licensing for development, testing, user
acceptance testing and production environments.
In Scope X N/A N/A
Software
The system and data must reside on State hardware. In Scope X N/A N/A
Desirable 54 CCMS-REQ-197 Software /
Hardware
It is desirable that the software should provide context-
sensitive help files and provide explicit instructions for
each type of user/customer and each form. Context-
sensitive help should be available for each data field.
In Scope X N/A N/A
Desirable 55 CCMS-REQ-198 Software /
Hardware
Several Providers and CCR&Rs have Scanners in their
current inventory. Software should accept data from
existing scanners provided that they are equivalent to
CCMS scanners.
Mandatory 69 CCMS-REQ-199 Operating
Environment
The CCMS System Database must be acceptable to
DHS MIS and CMS compliant, refer to
http://www.standards.Illinois.gov (ID=guestofstate
Password=Illinois) for a list of acceptable standards
for hardware and software. DHS currently supports
DB2 databases on IBM mainframes and AIX RS 6000S.
In Scope X N/A N/A
CCMS
Mandatory/
Desirable
Original
Require
ment ID
New
Requirement
ID
Out of
Scope
Added/
Modified/
Deleted
Reason
E
l
i
g
i
b
i
l
i
t
y
C
u
s
t
o
m
e
r

S
e
r
v
i
c
e
P
I
Q
A
T
e
c
h
n
i
c
a
l
A
p
p
r
o
a
c
h
P
r
o
p
o
s
a
l Business
Process ID
Use Case
ID
Environment
DHS currently uses Business Objects XIR2 and the
vendor will be required to use business objects to
meet the reporting requirements.
In Scope X N/A N/A
Environment
The system must interface with Active Directory Tivoli
Access Manager (TAM), which is the LDAP (Light
Directory Access Protocol) used by IDHS, for user
authentication and for individual/group application role
security assignments.
Environment
All custom coding for which DHS will assume support
must follow DHS coding standards.
In Scope X N/A N/A
Environment
The workflow software component must front-end IBM
Content Manager.
In Scope X N/A N/A
Environment
The Document System should be able to store and
index forms from the Legacy Mainframe CCTS Batch
System as identified in Appendix B. The data is
currently spooled out to the Mobius System using
Mainframe batch JCL Code Sysout = V.
Environment
All screens must be Americans with Disabilities Act
Standards (ADA) compliant. Please refer to
http://www.dhs.state.il.us.
In Scope X N/A N/A
Environment
Solution must use Adobe Business Transformation
Suite in an IBM WEBSPHERE environment. It must use
Spring, Struts and iBatis and must use appropriate
Adobe ECM connectors for data handling between the
input and data collection systems. Information-entry
screens must support the most common Web
browsers: Microsoft Internet Explorer version 6.0 and
later, and Mozilla Fire Fox. Manual submissions will use
the vendors mandated appropriate tool to connect to
IBM Content Manager with an integrator.
and added
clarification.
X N/A N/A
Environment
It must use Spring, Struts and iBatis Fast4J and must
use appropriate Adobe ECM connectors Adobe
LiveCycle Content Manager Connector for document
and data storage and retrieval to/from IBM Content
Manager. handling between the input and data
collection systems.
based on JAD
session.
X N/A N/A
Environment
Information-entry screens must support the most
common Web browsers: Microsoft Internet Explorer
version 6.0 and later, and Mozilla Fire Fox.
In Scope X N/A N/A
Environment
Manual submissions will use the vendors mandated
appropriate Adobe LiveCycle Content Manager
Connector tool to connect to IBM Content Manager
with an integrator.
Environment
The system must be capable of using alternate content
managers or technologies in the future thru an
integrator interface. Manual submissions will use the
vendors mandated appropriate tool to connect to IBM
Content Manager with an Adobe integrator plug-in.
The system must be capable of using alternate content
managers or technologies in the future thru an
integrator interface.
In Scope X N/A N/A
CCMS
Mandatory/
Desirable
Original
Require
ment ID
New
Requirement
ID
Out of
Scope
Added/
Modified/
Deleted
Reason
E
l
i
g
i
b
i
l
i
t
y
C
u
s
t
o
m
e
r

S
e
r
v
i
c
e
P
I
Q
A
T
e
c
h
n
i
c
a
l
A
p
p
r
o
a
c
h
P
r
o
p
o
s
a
l Business
Process ID
Use Case
ID
Mandatory 77 CCMS-REQ-211 Project Start
Up
The Agency will require the Vendor to meet with IDHS
staff to launch the project, formulate logistics such as
Vendors work location with IDHS, establish lines of
communications, review contract requirements, and
develop status reporting mechanism. The initial
meeting must occur within 14 days after contract
execution.
In Scope X N/A N/A
Up
The Vendor must begin the planning activities by
familiarizing itself with IDHS, the State of Illinois and
the project. At a minimum the Vendor must facilitate
meetings with selected IDHS managers and staff to
examine and gain an understanding of the childcare
assistance program, IPACS and State of Illinois
Technology.
In Scope X N/A N/A
Up
The Agency will require from the winning Vendor a
Scope of Work Statement defining the scope of the
work required for developing and implementing the
solutions.
In Scope X N/A N/A
Up
The Agency will require the winning Vendor to conduct
interview sessions with Agency staff to determine
project requirements.
In Scope X N/A N/A
Up
Work Breakdown Structure identifying the tasks and
the relationships between them.
In Scope X N/A N/A
Up
Network Diagram.
In Scope X N/A N/A
Up
Gantt Chart identifying the schedule and staff assigned
to the development, implementation, testing, and
training for the project.
In Scope X N/A N/A
Mandatory 83 CCMS-REQ-218 Project Plan The Agency will require from the winning Vendor a
Change Control Plan identifying the procedures for
requesting and approving changes to the Project Plan.
In Scope X N/A N/A
Communication Plan identifying the information that
needs to be communicated, from whom, to whom and
how it will be communicated.
In Scope X N/A N/A
Risk Analysis/Risk Management Plan identifying
procedures for analyzing risks and proposed
resolutions.
In Scope X N/A N/A
detailed timeline of all deliverables, as defined in
Section 3.3 for implementation of the solution.
In Scope X N/A N/A
Mandatory 87 CCMS-REQ-222 Implementation
Plan
The Agency will require the winning Vendor to provide
a comprehensive Implementation Plan including a
System Test Plan.
In Scope X N/A N/A
Plan
The Agency will require the winning Vendor to include
a description in the Implementation Plan of the
Vendors process, frequency and format for providing
regular updates regarding implementation activities to
IDHS.
In Scope X N/A N/A
CCMS
Mandatory/
Desirable
Original
Require
ment ID
New
Requirement
ID
Out of
Scope
Added/
Modified/
Deleted
Reason
E
l
i
g
i
b
i
l
i
t
y
C
u
s
t
o
m
e
r

S
e
r
v
i
c
e
P
I
Q
A
T
e
c
h
n
i
c
a
l
A
p
p
r
o
a
c
h
P
r
o
p
o
s
a
l Business
Process ID
Use Case
ID
Plan
The Agency will require the winning Vendor to include
in the Implementation Plan a description of how the
Vendor will provide contact information for key
implementation staff 24-hours-a-day, 7-days per
week.
In Scope X N/A N/A
Plan
staff dedicated to system administration, support and
problem response during implementation.
In Scope X N/A N/A
Plan
staff dedicated to system administration, support and
problem response during implementation.
In Scope X N/A N/A
Plan
The Agency will require the winning Vendor to obtain
written approval from the IDHS project manager of
acceptance of the Implementation Plan and any
changes to the plan there after.
In Scope X N/A N/A
Mandatory 93 CCMS-REQ-228 Testing The Agency will require the winning Vendor to
implement and demonstrate an Agency compatible
security scheme.
In Scope X N/A N/A
participate in beta testing with a selected number of
internal and external users to verify that the entire
software solution functions properly.
In Scope X N/A N/A
implement and demonstrate a successful, problem-
free parallel system operation for a 10 business day
pilot period.
In Scope X N/A N/A
demonstrate in Pilot Test (including a selected number
of internal and external users) all required
functionality.
In Scope X N/A N/A
Mandatory 97 CCMS-REQ-232 Testing The Agency will require the winning Vendor to provide,
install, and test all parts necessary to build separate
development, test, production, and training systems
with documentation for migration procedures.
In Scope X N/A N/A
Mandatory 98 CCMS-REQ-233 Testing The Agency will require the winning Vendor to obtain
written approval from the Agency of all changes after
acceptance of the Test and Development System.
Vendor and Agency will mutually agree upon
acceptance criteria.
In Scope X N/A N/A
Mandatory 99 CCMS-REQ-234 Detailed Design The system must be designed so that State staff can
easily install all upgrades. After the software system
has been put in production, the software must allow
IDHS database administrators to add and update
tables to the software system database without the
intervention of the vendor.
In Scope X N/A N/A
Mandatory 100 CCMS-REQ-235 Detailed Design The Vendor will provide written identification and
function of any and all integrated software packages.
In Scope X N/A N/A
Mandatory 101 CCMS-REQ-236 Detailed Design The system must be designed to allow the imaging
intake/indexing/retrieval process to be used as a plug
in.
In Scope X N/A N/A
Mandatory 102 CCMS-REQ-237 Detailed Design The Vendor will provide a description of any and all
integrated security mechanisms.
In Scope X N/A N/A
CCMS
Mandatory/
Desirable
Original
Require
ment ID
New
Requirement
ID
Out of
Scope
Added/
Modified/
Deleted
Reason
E
l
i
g
i
b
i
l
i
t
y
C
u
s
t
o
m
e
r

S
e
r
v
i
c
e
P
I
Q
A
T
e
c
h
n
i
c
a
l
A
p
p
r
o
a
c
h
P
r
o
p
o
s
a
l Business
Process ID
Use Case
ID
Mandatory 103 CCMS-REQ-238 Detailed Design The Vendor will provide recommendations for backup,
back out, restart, recovery, and utility features
necessary for the ongoing operation of the systems.
In Scope X N/A N/A
Mandatory 104 CCMS-REQ-239 Detailed Design The proposal will contain solution resource
requirements including final hardware, software and
communications configuration.
In Scope X N/A N/A
Mandatory 105 CCMS-REQ-240 Detailed Design Since the system will become a part of larger IDHS
systems and databases, the vendor must define and
create those tables required by the system that IDHS
does not currently have defined.
In Scope X N/A N/A
Mandatory 106 CCMS-REQ-241 Detailed Design Allow supervisors to have global access to override
queue routing and reroute to other users as needed.
In Scope X N/A N/A
Desirable 56 CCMS-REQ-242 Detailed Design The Detailed Design may also denote options, add-ins
or upgrades available for, but not included with, this
specific proposed installation.
In Scope X N/A N/A
Mandatory 107 CCMS-REQ-243 System
Maintenance
and Technical
Support
Provide warranties for software supplied by the
Vendor.
In Scope X N/A N/A
Maintenance
and Technical
Support
The Vendor must provide a one-year warranty for
each customized module to begin when the module is
deployed into production.
In Scope X N/A N/A
Maintenance
and Technical
Support
Agency/Buyer requires the Vendor to provide a
maintenance agreement for any and all hardware and
or modules proposed and bid, and, if applicable, for
any vendor-supplied database software or third-party
software, to take effect as soon as any portion of the
software has been deployed into Production.
In Scope X N/A N/A
Maintenance
and Technical
Support
The Agency/Buyer reserves the right to prorate the
annual cost if the agreement does not begin at the
start of the State fiscal year.
In Scope X N/A N/A
Maintenance
and Technical
Support
The Vendor must warrant all CCMS Solution software
for a minimum period of 365 calendar days. The
warranty period will begin on the date of final
acceptance of the system and signature of authorized
Agency personnel given for Mandatory Requirements.
In Scope X N/A N/A
Maintenance
and Technical
Support
Agency/Buyer requires the Vendor to provide 4th-tier
(System Level) technical phone support to CMS/IDHS
technical and program personnel. Provide 24x7 on-call
technical vendor support and problem resolution with
availability to respond within one hour for the life of
the contract.
In Scope X N/A N/A
Maintenance
and Technical
Support
All software and configuration problems must be
resolved before close of business (17:00 central time)
on the next business day.
In Scope X N/A N/A
CCMS
Mandatory/
Desirable
Original
Require
ment ID
New
Requirement
ID
Out of
Scope
Added/
Modified/
Deleted
Reason
E
l
i
g
i
b
i
l
i
t
y
C
u
s
t
o
m
e
r

S
e
r
v
i
c
e
P
I
Q
A
T
e
c
h
n
i
c
a
l
A
p
p
r
o
a
c
h
P
r
o
p
o
s
a
l Business
Process ID
Use Case
ID
Maintenance
and Technical
Support
Provide a problem escalation procedure. Please explain
in detail the escalation process for a technical
problems resolution (i.e. time to call in additional
resources or support up to the company president).
The Agency/Buyer reserves the right to prorate the
annual cost if the support does not begin at the start
of the State fiscal year.
In Scope X N/A N/A
Maintenance
and Technical
Support
The vendor must demonstrate how it would ensure
IDHS maintenance requests are addressed in a time
frame satisfactory to IDHS.
In Scope X N/A N/A
Maintenance
and Technical
Support
Vendor must provide a software tool so that the
Agency can report and track software errors found
during functionality and acceptance testing.
In Scope X N/A N/A
Maintenance
and Technical
Support
The software system must provide a means for IDHS
Information Technology personnel to notify all users of
system-wide issues such as scheduled maintenance
and system upgrades.
In Scope X N/A N/A
Maintenance
and Technical
Support
The system must allow for the addition, modification,
and removal of Business Rules to the system without
the Vendors assistance.
In Scope X N/A N/A
Maintenance
and Technical
Support
All revisions to the modules must support the BCCD
business logic, the CCTS Web and mainframe
programming logic and platforms, the CCTS Database
structure, and the client Database Structure. In
refining other requirements, the intent of this
requirement has been met.
Maintenance
and Technical
Support
Track open and closed service requests during the
warranty period, and provide monthly reports to the
Agency.
In Scope X N/A N/A
Maintenance
and Technical
Support
Provide for user modification and updating of formats,
information, scripting, instructions, etc.
In Scope X N/A N/A
Maintenance
and Technical
Support
The Agency will require the winning Vendor to obtain
written approval from the Agency of all changes after
acceptance of the Test and Development System.
Vendor and Agency will mutually agree upon
acceptance criteria.
In Scope X N/A N/A
Maintenance
and Technical
Support
The Agency will require the winning Vendor to
demonstrate in Pilot Test (including a selected number
of internal and external users) all required
functionality.
In Scope X N/A N/A
Maintenance
and Technical
Support
The software/hardware combination must be able to
handle transactions 7 days per week, 24 hours per
day, 365 days per year, with the exception of
scheduled down time during offhours for daily,
weekly, monthly, quarterly, and yearly system saves
and system upgrades and for the application of any
program patches and, minus time to perform routine
maintenance.
In Scope X N/A N/A
CCMS
Mandatory/
Desirable
Original
Require
ment ID
New
Requirement
ID
Out of
Scope
Added/
Modified/
Deleted
Reason
E
l
i
g
i
b
i
l
i
t
y
C
u
s
t
o
m
e
r

S
e
r
v
i
c
e
P
I
Q
A
T
e
c
h
n
i
c
a
l
A
p
p
r
o
a
c
h
P
r
o
p
o
s
a
l Business
Process ID
Use Case
ID
Maintenance
and Technical
Support
Routine maintenance must be performed during off-
hours and must not require unavailability of the
system for more than 30 minutes during any given 24
hour period. Normal business hours are 8:00 a.m. to
5:00 p.m., central time.
In Scope X N/A N/A
Desirable 57 CCMS-REQ-262 System
Maintenance
and Technical
Support
The vendor should supply detailed, step-by-step, fault-
tolerant and disaster continuity plans or approaches
that can satisfy the requirement.
In Scope X N/A N/A
Mandatory 128 CCMS-REQ-263 Training The Agency will require the winning Vendor to conduct
training and provide manuals and materials. The
Agency requires on-site staff training, and off-site
training sessions with providers.
In Scope X N/A N/A
Mandatory 129 CCMS-REQ-264 Training The Agency will require the winning Vendor to provide
installation of online training material, written training
material, and deployment of all vendor-supplied
training software and hardware components.
In Scope X N/A N/A
Desirable 80 CCMS-REQ-265 Training The System should have a method of communication
between someone who is taking a training course and
the training staff, i.e. Email questions as defined in the
customer service request business process.
Mandatory 130 CCMS-REQ-266 Vendor
Background &
Experience
Must have at least five years experience in designing,
and implementing and supporting the type of systems
required in this RFP.
In Scope X N/A N/A
Background &
Experience
Please specify the number of years experience with
type of systems required in this RFP.
In Scope X N/A N/A
Background &
Experience
Must have at least 10 full time employees. Please
specify the number of full time employees.
In Scope X N/A N/A
Background &
Experience
VENDOR must provide 3-5 references of projects of
similar size and scope. There must be at least two
references from clients for which the vendor
implemented a Web-based electronic document
management system, with a customer service, fraud
management or case management component.
In Scope X N/A N/A
Background &
Experience
The references must indicate an overall positive
experience in working with the vendor and satisfaction
with the implemented system.
In Scope X N/A N/A
Background &
Experience
Vendors will receive additional points for more than
three references.
In Scope X N/A N/A
Background &
Experience
The Vendor must provide an onsite visit to the
Agency/Buyers site. During the visit the Vendor must
describe past implementations, its plans for or
approaches to Agency/Buyers project and provide a
real time demonstration of a working document
management system and present their Scanner
Imprinter solution with examples of Scanners
Imprinters for the purchaser to view and review, which
will be followed by questions and answers.
In Scope X N/A N/A
CCMS
Mandatory/
Desirable
Original
Require
ment ID
New
Requirement
ID
Out of
Scope
Added/
Modified/
Deleted
Reason
E
l
i
g
i
b
i
l
i
t
y
C
u
s
t
o
m
e
r

S
e
r
v
i
c
e
P
I
Q
A
T
e
c
h
n
i
c
a
l
A
p
p
r
o
a
c
h
P
r
o
p
o
s
a
l Business
Process ID
Use Case
ID
Background &
Experience
The vendor must provide detailed resumes including
references for the proposed Project Manager and
Project Training Manager, Team Leaders, and
additional personnel that the VENDOR deems
necessary to the successful implementation of the
project.
In Scope X N/A N/A
Background &
Experience
The resumes must be signed and dated by the
proposed people. The Agency/Buyer must agree to
any change submitted to the Project Manager after the
contract is awarded. Key replacement staff must
possess the same skills and qualifications as the
originally bid staff member.
In Scope X N/A N/A
Background &
Experience
Describe the applications, and system hardware and
software environments of three verifiable projects that
show previous successful and comparable installations.
The installations must have consisted of a caseload
size of a minimum 200,000 cases.
In Scope X N/A N/A
Background &
Experience
For the three projects described above, supply
company names, contact names, their titles, current
telephone numbers, and which items were met for
each company. The vendor must notify the company
prior to submission of the proposal that the Agency
will be contacting them for a lengthy conference call or
a site visit.
In Scope X N/A N/A
Desirable 83 CCMS-REQ-277 Vendor
Background
and Experience
Provide details of previous experience with Child Care
Programs.
In Scope X N/A N/A
Mandatory 137 CCMS-REQ-278 Staffing
Specifications
The vendor must provide a Project Training Manager
who will be responsible for the planning and
implementing the training requirements associated
with the project.
In Scope X N/A N/A
Specifications
Provide a project manager who will be responsible for
the successful planning, installation, and deployment
of all Vendor-supplied software and hardware
components. The proposed project manager must
have experience in the installation of the proposed
products.
In Scope X N/A N/A
Specifications
Specify the amount of experience the proposed project
manager has in the installation of the proposed
products.
In Scope X N/A N/A
CCMS
Mandatory/
Desirable
Original
Require
ment ID
New
Requirement
ID
Out of
Scope
Added/
Modified/
Deleted
Reason
E
l
i
g
i
b
i
l
i
t
y
C
u
s
t
o
m
e
r

S
e
r
v
i
c
e
P
I
Q
A
T
e
c
h
n
i
c
a
l
A
p
p
r
o
a
c
h
P
r
o
p
o
s
a
l Business
Process ID
Use Case
ID
Specifications
Supply the names, accreditations, qualifications and
contact information for Vendors Project Manager,
Project Training Manager, and Team Leaders who will
be involved in the design, development and installation
of the proposed solutions. DHS reserves the right to
interview and approve the Vendors Project Manager
and team leaders, prior to project start-up. The
Vendor must agree that no substitutions of such
specific individual(s) and/or personnel qualifications
shall be made without the prior written approval of
DHS. Any personnel substitution proposed by the
Vendor must have equal or better qualifications than
the originally proposed individual. DHS agrees that an
approval of a substitution will not be unreasonably
withheld.
In Scope X N/A N/A
Specifications
The Project Leader, Project Training Manager, Team
Leaders, and Development and Training Team must be
onsite in Springfield, Illinois or a site approved by the
Agency during normal business hours (Monday
through Friday, 8:00 a.m. to 5:00 p.m. central time).
In Scope X N/A N/A
Specifications
Supply the names and contact information for the
Technical Contact(s) and Help Desk contact(s.)
In Scope X N/A N/A
Specifications
Should the Vendor use a subcontractor for any
purpose, the Vendor retains the responsibility of
meeting all terms of the contract.
In Scope X N/A N/A
Specifications
Provide two staff that have a minimum of 1 year
experience on the proposed system and are part of the
system development to assist with ongoing
maintenance and knowledge transfer for one year
after the date of final acceptance of the system and
signature of authorized Agency personnel. This staff
must be onsite in Springfield, IL during normal
business hours (Monday through Friday, 8:00 a.m. to
5:00 p.m. central time). Provide resumes of the actual
personnel to meet the needs of the Agency.
In Scope X N/A N/A
Specifications
Provide a Help Desk for the Agency to call for all
problems reporting during the entire warranty period.
Said contact must be available 24 X 7 with a 1-hour
response time. During maintenance help desk support
must be available during normal business hours
(Monday through Friday, 8:00 a.m. 5:00 p.m. central
time.)
In Scope X N/A N/A
Specifications
The Vendor must provide support during the 1-year
warranty period.
In Scope X N/A N/A
Specifications
The vendor must provide optional 4-tier help desk
support for users of CCMS system for the first five
years of the project starting after Production
Deployment. For 4- tier help desk support, the vendor
will receive calls directly from IDHS/BCCD
stakeholders.
In Scope X N/A N/A
CCMS
Mandatory/
Desirable
Original
Require
ment ID
New
Requirement
ID
Out of
Scope
Added/
Modified/
Deleted
Reason
E
l
i
g
i
b
i
l
i
t
y
C
u
s
t
o
m
e
r

S
e
r
v
i
c
e
P
I
Q
A
T
e
c
h
n
i
c
a
l
A
p
p
r
o
a
c
h
P
r
o
p
o
s
a
l Business
Process ID
Use Case
ID
Specifications
The help desk must provide a guaranteed callback
time minimum. The help desk must provide a
published escalation policy for problems that cannot be
resolved by first-line help desk personnel.
In Scope X N/A N/A
Specifications
During any maintenance period, the Agency may
require the Vendor to provide staff to assist with
system enhancements. All Vendor supplemental
service activities will be authorization by the Project
Manager.
In Scope X N/A N/A
Specifications
One week after the Agency has notified the Vendor in
writing the Vendors Staff must report to Springfield
Illinois.
In Scope X X N/A N/A
Mandatory 148 CCMS-REQ-292 Contract
Monitoring
The Vendors project manager must meet in person
weekly with authorized Agency staff and provide
weekly written status reports to the Agencys Project
Manager or designee.
In Scope X N/A N/A
Monitoring
The Vendors project manager must respond in writing
to any changes, corrections, concerns, etc. presented
by Agency staff within five business days.
In Scope X N/A N/A
Monitoring
The Vendor is responsible for faithful performance of
the contract and shall have internal monitoring
procedures and processes to ensure compliance.
In Scope X N/A N/A
Monitoring
When appropriate, the Vendor will work with the State
to develop a performance scorecard with conditions,
milestones, requirements, or timetables that must be
met before additional steps may be taken, or payment
is due.
In Scope X N/A N/A
Monitoring
Cooperate with the State in monitoring and tracking
activity, which may require that the Vendor report
progress and problems (with proposed resolutions),
provide records of its performance, allow random
inspections of its facilities, participate in scheduled
meetings and provide management reports as
requested by the State.
In Scope X N/A N/A
Compatibility
Should communicate with the BCCD Mainframe Online
Systems: PASDX, SOLQ, CANTS, MNACCROAWARE,
and INCCRRA. The above systems are READ only.
Please consider a Web Service or a Screen Scrape
technology.
and added clarity
(see below).
X X X X N/A N/A
Compatibility
CCMS should communicate with PASDX in read only
mode. PASDX gets Social Security SSI and SSA income
overnight without Case Number. R&R staff uses the
information for validating SSN as by assigned by SSA.
TBD Modified X All Eligibility
Business
Processes
All Eligibility
Use Cases
Compatibility
There is an existing interface between CCTS and Child
Abuse and Neglect Tracking System (CANTS)/Sexual
Offender Registry System (SORS) for the purpose of
background checking. CCMS will provide the ability to
display the background check disposition (yes/no
indicator) passed to CCTS from CANTS.
In Scope Modified X CCMS-BP-ELI-
008
CCMS-USE-
ELI-009
CCMS
Mandatory/
Desirable
Original
Require
ment ID
New
Requirement
ID
Out of
Scope
Added/
Modified/
Deleted
Reason
E
l
i
g
i
b
i
l
i
t
y
C
u
s
t
o
m
e
r

S
e
r
v
i
c
e
P
I
Q
A
T
e
c
h
n
i
c
a
l
A
p
p
r
o
a
c
h
P
r
o
p
o
s
a
l Business
Process ID
Use Case
ID
Compatibility
CCMS should communicate one-way with
NACCRAWARE which is a resource and referral
database, if CCMS does provider registration and
contains the client/provider eligibility data.
Business
Processes
All Eligibility
Use Cases
Compatibility
CCMS should communicate one-way with INCCRRA
which is a resource and referral database, if CCMS
does provider registration and contains the
client/provider eligibility data.
Business
Processes
All Eligibility
Use Cases
Compatibility
CCMS should communicate with SOLQ in read-only
mode. SOLQ is a CICS system that provides online
access to Social Security and a Case Number is
required as opposed to PASDX where a Case Number
is not required. SOLQ is not on the IPACS HATS
menu. It is accessed via a Bluezone (web-based)
terminal emulator.
Business
Processes
All Eligibility
Use Cases
Desirable 58 CCMS-REQ-303 Access,
Security, and
Traceability
The software should support a method by which an
authorized user can attach an electronic signature or
other unique identifier to an electronic record.
In Scope X All All
Security, and
Traceability
Should provide a Form Dropdown to allow the user to
select the form being uploaded; this should be filtered
by the Case Requirements, (i.e. do not display forms
that do not apply to this case). This would be a
customizable table for security roles of users.
001
CCMS-USE-
DOC-001,
CCMS-USE-
DOC-002
Security, and
Traceability
The software should have an Alteration Audit Log. that
will do the following at a minimum:
requirements.
X N/A N/A
Security, and
Traceability
The software should search for and display log records
according to criteria designated by IDHS.
In Scope X N/A N/A
Security, and
Traceability
The log record will contain enough identifying
information to trace the person and location making
any alteration.
In Scope X N/A N/A
Security, and
Traceability
All log records should be locked to changes. In Scope X N/A N/A
Security, and
Traceability
The software system should support the use of Entrust
PKI digital (public/private keys) encryption as
implemented by the State of Illinois.
In Scope X N/A N/A
Security, and
Traceability
Should print a report that tracks the number of forms
added to the system and by whom.
In Scope X All All
Security, and
Traceability
Provide Provider and Client Status Identifier on each
screen.
In Scope X X X All All
Security, and
Traceability
Provide a way to execute a Batch job to verify no
Duplicate entries in the IDHS System as defined in
Appendix B.
based on JAD
session follow-up.
X All All
CCMS
Mandatory/
Desirable
Original
Require
ment ID
New
Requirement
ID
Out of
Scope
Added/
Modified/
Deleted
Reason
E
l
i
g
i
b
i
l
i
t
y
C
u
s
t
o
m
e
r

S
e
r
v
i
c
e
P
I
Q
A
T
e
c
h
n
i
c
a
l
A
p
p
r
o
a
c
h
P
r
o
p
o
s
a
l Business
Process ID
Use Case
ID
Security, and
Traceability
The system should have the ability to check the county
entered in the system and if it has been submitted to
the wrong CCR&R the system would route the Request
to the correct CCR&R work Que. The County to CCR&R
table exists in the Legacy CCTS System. The system
should provide the ability for one R&R to redirect a
request to another R&R.
based on JAD
session follow-up.
X All All
Security, and
Traceability
The system should have Security that could limit the
time a person has access to the system.
In Scope X All All
Security, and
Traceability
Capability to allow Shared Case access to two
Providers for one case.
004, CCMS-BP-
ELI-005, CCMS-
BP-ELI-006,
CCMS-BP-ELI-
007
CCMS-USE-
ELI-005,
CCMS-USE-
ELI-008
Security, and
Traceability
Allow ability to Override a lower security level persons
updates. BCCD staff with security levels specified in
the detail design will have the ability to migrate a case
from one I.D. to another if a mistake is discovered;
the update would be recorded.
Security, and
Traceability
Maintain a log of security access failed logins and
successful logins.
In Scope X N/A N/A
Security, and
Traceability
Provide for User authentication. Maintain a History/log
of security adds, updates, and deletes.
In Scope X N/A N/A
Security, and
Traceability
Produce detailed reports on security levels assigned to
each user.
In Scope X N/A N/A
Security, and
Traceability
Limit access and function by module, form/screen,
field data, and database table as defined by IDHS to
assure both role-based and matter-based security.
In Scope X All All
Security, and
Traceability
Roles will be defined for each user to provide
maximum security as defined by IDHS.
In Scope X N/A N/A
Security, and
Traceability
Capability of showing previous results on the same
applicant, when additional results are added to the
record.
In Scope X All All
Security, and
Traceability
The System should have security that could limit what
server has access.
In Scope X N/A N/A
Security, and
Traceability
Should allow different users roles to have different
levels of security access. Ability to add a User Role to a
specific restricted CASE for view only access (example,
restrict access to a client who is also a provider
employee working at an R&R and provide view only
access to the restricted to the supervisor at the R&R).
based on JAD
session follow-up.
X N/A N/A
Security, and
Traceability
Allows secure access to the modules for each user. In Scope X All All
CCMS
Mandatory/
Desirable
Original
Require
ment ID
New
Requirement
ID
Out of
Scope
Added/
Modified/
Deleted
Reason
E
l
i
g
i
b
i
l
i
t
y
C
u
s
t
o
m
e
r

S
e
r
v
i
c
e
P
I
Q
A
T
e
c
h
n
i
c
a
l
A
p
p
r
o
a
c
h
P
r
o
p
o
s
a
l Business
Process ID
Use Case
ID
Security, and
Traceability
The system should support a configurable number of
simultaneous logins by the same user. (Example: The
CENTRAL MANAGEMENT SYSTEMS (CMS)/IDHS system
administrators should be able to allow users multiple
session logins. Additional login attempts above the set
number (using the same username and password)
should be denied by the system.)
In Scope Deleted Deleted based on
JAD session.
X N/A N/A
CCMS

Worksheet in Deloittes System Design Document

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Worksheet in Deloittes System Design Document

Загружено:

Авторское право:

Доступные форматы

Deloitte Consulting LLP General System Design 12/03/2010

Вам также может понравиться