|
ISAWS Migration Assessment Project
Frequently Asked Questions - Fiscal
Can How are Maintenance & Operations hours allocated?
(IMAP ID#22)
C-IV
C-IV's most recent monthly average allocation included 3,752 hours for
Application Maintenance and 6,802 for Operations, approximately 10,550
hours per month. Following discussion with HHSDC, it was determined that
C-IV should modify the hours requested for Application Maintenance to
align with the CalWIN and LEADER requests. Therefore, the most recent
C-IV funding request included 8,000 hours/month for Application Maintenance.
No additional Application Maintenance hours will be required, regardless
of the number of counties that ultimately join C-IV. It is anticipated
that standard maintenance will require from 3,750 to 6,000 hours per month.
The additional hours will be available for enhancements and extraordinary
policy changes (of the scale of Quarterly Reporting).
CalWIN
CalWIN's most recent request was for 4,000 additional hours bringing the
total to 8,000 hours per month for application modifications and enhancements.
Back to Top
What is the expectation of this consortium regarding
our county financial participation for application development, implementation
and ongoing maintenance? (IMAP ID #130)
C-IV
Current regulations that govern financial participation would apply. Counties
would be expected to pay 5% of the incremental increase to application
development as a result of the inclusion of that county into the project.
During ongoing maintenance the county share would be 15% of the telecommunication
charges, operation charges, and other server monitoring charges specific
to the County's sites, users and caseload.
CalWIN
Counties would be expected to pay 5% of the incremental increase to application
development as a result of the inclusion of that county into the project.
For CalWIN this may be limited to the cost associated with a joining county
who wishes to have county-specific GA program automated support or support
for their county-specific client correspondence. All local hardware and
software, training and conversion costs would be specific to the County
based on sites and users. If a county chooses to include GA there would
be a county share for these costs relative to that counties' GA population.
During ongoing maintenance the county share would be 15% of the telecommunication
charges, operation charges, and other server monitoring charges specific
to the County's sites, users and caseload. The application maintenance
costs would be is shared between counties based on a small, medium, and
large size counties. The county participation is 15% of their county share.
Back to Top
If a county has its our own XP OS and Office Licenses,
could it receive the hardware refresh at a reduced cost and image the
PC's to meet the standards in the system? Are there any licensing issues
for these as well? (IMAP #152)
C-IV
This question was also raised by the original four counties of the C-IV
Consortium. The complexity of managing multiple different sets of licenses,
particularly when dealing with upgrades and support, outweighed the possible
benefits of re-using existing licenses. C-IV recommends using C-IV licenses
on the C-IV workstations.
CalWIN
Technical refreshment is not provided by CalWIN.
Back to Top
What is an IAPDU? (IMAP #105)
Consortium Staff Response
Implementation Advance Planning Document Update. The APD is developed
by the State in accordance with Federal instructions and guidelines. Its
purpose is to request and secure initial and continuing Federal Financial
Participation (FFP) for an approved project. The initial or planning APD
(PAPD) discusses the overall proposed project, schedule, budget, cost
allocation plan, alternatives and benefits. Once the APD receives federal
approval, the project is considered to be in implementation status (rather
than planning) and it is managed by the State in accordance with the APD
plan, schedule and budget. The APD is updated minimally on an annual basis
and when a major change to the project or project budget occurs. The implementation
APD is termed the IAPD and the updated document is termed the IAPDU. All
current consortia (C-IV, CalWIN, ISAWS and LEADER) operate independently
under respectively approved IAPDs and IAPDUs. For the migration of ISAWS
counties to the C-IV or CalWIN consortia, each consortium will prepare
and submit an IAPDU to secure FFP for the expanded projects.
Back to Top
There is a registration charge for licenses on WTW
system when moving from NT to Win2K or XP. Does this have a cost associated
with it? (IMAP #150)
Consortium Staff Response
WTW will no longer be used when migration to either system is completed
and will work as is until such time.
Back to Top
Will upgrades from the ISAWS counties' versions
to the current consortium's version of MS-Office be included as a project
cost? (IMAP #128)
Consortium Staff Response
Unless approved through the ISAWS change management process, these upgrades
will not be funded by the ISAWS project as the current version of MS-Office
will be replaced by the consortia: the C-IV system includes MS-Office
and CalWIN will offer the option of MS-Office to be included Within the
initial one-time costs.
Back to Top
|
