PROPOSAL TO DEVELOP A WRD INVENTORY OF HARDWARE AND SOFTWARE
=============================================
The development of a computer inventory tool for systems,
applications, and licensing will provided WRD with a starting
component for a much needed set of "Enterprise Management
Tools." The database and application will be developed based
upon our supported desktop productivity suite, Microsoft
Office. The application, electronic data entry forms, and
database will be designed to "work globally" but "run locally."
The application will be distributed to SA's and each District
will maintain a local database which will be replicated to a
central site where aggregation will occur, analysis will be
conducted, and data and reporting services will be provided.
Prior to the release/distribution of the database application
to all District and Sub-District offices, the database shall
be preloaded with the information generated during the
"Baseline Data Compilation" phase of the workplan. The
Baseline Data Compilation shall include compiling data
from DIS contract purchases that can be retrieved from AIS,
acquiring all names of machines that have registered IPs
(through Jim F), and pulling together the data from Graig
McHendrie's original data set (and new db for Lotus). Also,
license information for ESRI, SAS, and Frame; as well as
other new data that are deemed necessary such as LAN and
WAN equipment (and Y2K status) may be added to the database
application if those data are deemed necessary. Each equipment
item or tabular record will be referenced to a site by the
use of a "site code" database item. The site code will
likewise be an item in a spatial database as a point attribute
item that will allow all tables to be linked to a spatial
database, accessed, and served to the internet in a map-based
form through a GIS application.
The database application shall be distributed to all Districts
and Sub-Districts with preloaded information included. The
local database will be maintained by local computer section
staff and will be populated by using customized forms. Each
WRD district will have a "site" file that will be used to
provide information about the spatial location of the office
and will provide primary keys for other tables to use for links.
There will be separate tables for hardware items, software items,
maintenance items, and license tracking if needed (or desired).
The site code shall serve as the primary key - foreign key link
item between tables. All sites will maintain their local
database. If GIPO wants to maintain the ESRI license portion
for the nation then that could be easily worked out.
The delivered application shall primarily consist of a designed
data base, preloaded data, electronic database input forms,
and methods for data aggregation, analysis, and web serving.
Specific data items that the database shall provide include:
o Detailed information about hardware, OS
(and rev), and maintenance for each computer
in WRD;
o Report generating tools including map-
and form-based interfaces for pulling information
about equipment at individual sites as well as
information about a specific piece of equipment
at a given site.
o Provide revision information about the corporate
software for each individual computer platform.
o Provide information about licensed software including
GIS and statistical software.
o The status or use of NWIS on each platform.
(an NWIS server, an NWIS client, never used with NWIS, etc.)
*** o Local Area Network and Wide Area Network
equipment used on-site. (if desired)
The original CPAC proposal used the following table as a work plan for
developing the database and application.
AS PROPOSED
o System and Data Base Design 2 months
o Application Development 4 months
o Testing 2 Testers (1 week each) 2 weeks
o Release 3 weeks
o Installation Support 4 weeks
o Software tools $2000
The modified workplan follows:
AS MODIFIED
o System and Data Base Design 1 1/2 months
o Application Development 2 months
o Baseline data compilation 1 months
o Pre-acceptance testing 2 weeks
o Application and db modifications 1 1/2 month
o Final testing and modifications 2 weeks
o User Notes and Release Notes 1 month
o Release 2 weeks
o Installation Support 4 weeks
o Software tools $2000
If everything goes well, I would think that the above modifications
reflect the approximate "level of effort" as well as the chronology
of the workflow (moving down the list) for developing the database
and associated application. I think that the 35K to 40K funding
level that was offered should be close to doing the trick for
developing the application and getting it put into place. However,
it should be recognized that this type of application requires some
periodic care, feeding, and update. The group should be prepared
to budget a small annual amount to the maintenance, upgrades,
and care for the database and associated applications.