Method of Inclusion
Criteria
The agency or enterprise
system, having met the Reporting Entity and Financial Impact criteria for
inclusion in NCAS, will determine the method of inclusion as follows.
The agency or enterprise
system is included as a primary user of NCAS if:
-
Agency system functionality
is met by the existing core systems of the NCAS or is added to the core
system functionality after a determination that it would be desirable for
this functionality to be included in the NCAS Model for application at
multiple agencies.
-
Agency system is of sufficient
complexity and criticality to warrant inclusion in the core systems of
the NCAS and meets the test of core cost/benefit analysis, which includes:
overall costs to implement, system enhancement and maintenance costs in
time and materials, and statewide information access and reporting costs.
The agency or enterprise system
is
included as a secondary user of the NCAS if:
-
Agency system functionality
is not met by the existing core systems of theNCAS, this functionality
is determined to be unique to one agency, and is further determined not
to be cost effective for inclusion in the NCAS primary core software.
-
Agency system is not of sufficient
complexity and criticality to warrant inclusion in the core systems of
NCAS and fails the test of core cost/benefit analysis, which includes:
overall costs to implement, system enhancement and maintenance costs in
time and materials, and statewide information access and reporting costs.
Agency or enterprise systems
defined as secondary users of NCAS will be required to meet the following
requirements:
-
NCAS policies and procedures
as documented in the NCAS Systems Information Guide (SIG) will guide the
system functional business design;
-
The FSMP requirements (and subsequent
updates) will guide the system functional and technical designs;
-
The data structures of new or
replacement systems will mirror the NCAS data structures and codes to meet
the uniform information and reporting requirements more efficiently;
-
Secondary user system projects,
in the absence of a direct OSC project management role, will minimally
provide the OSC with periodic progress reports documenting key functional
design, development, and implementation milestones and the OSC will review
these for adherence to NCAS requirements; and
-
Secondary user system projects
will continue to meet the IRMC strategic technical architecture guidelines
and project management reporting requirements.