Download 5 - VendorNet

TECHNICAL REQUIRMENTS TEMPLATE
Appendix A Continued - Overview of technical standards
The proposed Solution must operate within and be compatible with existing Department of Correction's
standards. The proposed solution must operate in a secure fashion within existing Department of Corrections
Technology Environment.
Security Standards
Security addresses the manner in which the proposed Solution protects data and ensures that only
authorized individuals / entities may utilize the suite of applications within the System and view, add, or
update records. The security design matrix detailing the security architecture should be developed as
part of this project.

The proposed solution must use the DOC Active Directory LDAP security architecture to provide
authentication as an element of security to verify the identity of entities using the proposed solution.

The proposed solution must provide access control that permits or denies access to the application,
information, or other resources, based on parameters including (but not limited to) the identity of the
source and destination.

Vendors will not be allowed to remotely connect to servers or other equipment installed with DOC
or other State facilities either via dial-up or VPN. If remote access is a requirement, the proposed
solution must describe how this will be done in a secured way.

The proposed solution must provide comprehensive reports and metrics on logons for effective
decision making and improved security. Source and report data must be accessible and exportable.

The proposed solution should utilize roles and groups to provide granular security for all application
components by individual component, screen, or Web page.

The proposed solution should be capable of selectively maintaining audit-trail information by entity,
which includes data actions such as read, write and delete, and should also include date, time and
function of the data action.

The proposed solution must support an inactivity timeout to allow user sessions to be terminated
after a specific time period of inactivity.

The proposed solution must ensure confidentiality as an element of security that makes information
available only to authorized entities. Data should be digitally secure with access restrictions to
protect confidential information (e.g. sensitive internal data).
Application Standards
Application describes the technical features that support, augment, and enhance the functionality
provided by the proposed system.
5/8/2017

The proposed solution should provide the ability for a system administrator to modify system lookup
tables for purposes of modifying local codes and other common codes (e.g. Zip Codes or Part
Numbers). This activity should be able to be performed by the administrator without requiring the
need for proposer assistance or associated costs.

The proposed solution should provide the ability for a system administrator at the departmental unit
to define and set up the appropriate organization subunits for purposes of correctly managing
workflow. This includes user-defined roles and assignment of all location-specific information
(facility name, address, etc.).
Page 1 of 7
TECHNICAL REQUIRMENTS TEMPLATE

For user-initiated system actions that may take considerable time to complete (e.g., long reports), the
proposed solution should provide indicators that show estimated time to complete and provide the
user the ability to proceed or cancel the activity or task.

The proposed solution should limit the requirement for additional files or applications to be stored
on the Windows workstation. Ideally, no files or applications should be required on the workstation.
Proposer must identify in detail any files required to be installed or temporarily stored on the end
user workstation.

The proposed solution should provide robust on-line help features with relevant user help features
such as indexing and search capabilities.

The proposed solution should minimize data entry efforts by:
- Providing default values for fields based on previous input, referential lookup, or other
mechanisms.
- Providing lookup tables for valid values for fields.

The proposed solution must provide data quality editing, consistency and validity checks on data
elements at the point of data entry. The proposed solution must display a meaningful error message,
and prevent entry of data that does not pass edit checks.

The proposed solution should provide a logical sequence of screens and fields enabling users to
quickly access, modify, skip or jump to other areas of interest for data entry based on the customized
user-defined specific workflow.

The proposed solution must provide a positive acknowledgement that the data entry has been
accepted for all add and update functions.

The proposed solution should provide a means to facilitate rapid data entry for large volume or highspeed data entry requirements. This includes the ability to use the TAB or ENTER key to progress
through fields on the screen.

The proposed solution should minimize reliance on third-party software applications, such as office
automation applications, image display tools, and graphics packages.

The proposed solution should be capable of providing administrator defined time-outs for user
sessions, server threads, and other persistent features within the environment and must provide a
capability for managing and handling record locking and releasing of locks.

The proposed solution must comply with Section 508 (b) of the Rehabilitation Act of 1973, as
amended 29 USC § 794 (d). § 794d pertaining to visually or hearing impaired employees.

The proposed solution should provide basic word processing functionality, including word wrap,
spell check, and font control, for the entry and manipulation of text data.

The proposed solution must provide a consistent look and feel.
Integration Standards
Integration explains how the System supports the information exchanges and messaging needs of the
System environment and DOC applications.

5/8/2017
The proposed solution should utilize web services, i.e. XML/HTTP REST as the preferred interface
for data exchange. As needed, the services must support the secure transmission of data and support
synchronous and asynchronous communication between the client application and the web services.
Page 2 of 7
TECHNICAL REQUIRMENTS TEMPLATE

Proposer must list all technologies used as a part of the application including any web browser plugins that need to be utilized to make the application function correctly.

The proposed solution must ensure that all communication from servers utilized for this system to
internal applications and services shall be controlled using existing security systems software and
management tools used by DOC
Analysis Support Standards
Analysis Support describes the support and tools for analysis and program measurement required to
conduct operations.

The proposed solution must provide a data dictionary that defines the data in the System database.
This should be available to authorized individuals for the creation and storage of views.

The proposed solution should support defined roles, processes, and responsibilities for views, data
marts, and extracts.

The proposed solution must allow for export and access to data for analysis and program
measurement.

The proposed solution should have defined data standards and utilize consistent data schema, data
element, class word, field length, data tables, view naming conventions and should also provide a
data dictionary that defines the data base. This should be available to authorized users for the
creation and storage of views.
Systems Management & Support Services Standards
Systems Management and Support addresses the technical functionality that permits System resources to
be effectively monitored and managed by technical support staff, permits support staff to prevent system
failures, recover quickly from failures that do occur, and enables support staff to respond quickly and
effectively to customer-reported problems.
5/8/2017

The proposed solution must have a defined and formal release management procedure and process
for the release and distribution of upgrades, patches, and end-of-life-cycle.

The proposed solution must provide a centralized repository for all error messages. This repository
should be accessible and exportable for support staff for easy alteration.

The proposed solution must provide defined and documented procedures and processes to restart
system components and recover and restore incomplete transactions.

The proposed solution should support the capability to create, administer and modify help screens
and online manuals.

The proposed solution should support the printing of all documentation in the PDF format.

The proposed solution must provide a mechanism to uniquely identify each screen or Web page to
allow support staff to quickly and easily deliver assistance and to provide easy reference to reference
materials, such as on-line help, training materials, product documentation, user guides, etc.

The proposed solution must record all errors and warnings to a system log that is easily accessible to
and exportable by support staff.
Page 3 of 7
TECHNICAL REQUIRMENTS TEMPLATE

The proposed solution should allow for maintenance and support performance activities (such as
"Hot" backup procedures) to be carried out while the application and supporting systems are on line.

The proposed solution should have the ability to provide alerts to users regarding system status,
maintenance outages, shutdown advisories, etc.

The proposed solution should provide application and system usage reports to help plan system
resource utilization.

The proposed solution should immediately notify the system administrator, using SNMP MIBs when
definable thresholds are exceeded, and, if the occurrence or accumulation of these relevant events
continues, the system should take the least disruptive action to terminate the event.

The proposed solution should support data archiving.

The vendor of the proposed solution must be able to provide support based on tiered severity levels.
- High Severity – Must be supported 365x24x7.
* Vendor must be able to respond within 1 hour
* Vendor must be able to diagnose the problem within 2 hours
* Vendor must be able to have the system operational within 4 hours
* Vendor must have full functionality and performance restored within 24 hours
- Medium Severity – Must be supported 8x5, business hours 7:45 – 4:30, Central time.
* Vendor must be able to respond within 4 hour
* Vendor must be able to diagnose the problem within 8 hours
* Vendor must be able to have the system operational within 1 day
* Vendor must have full functionality and performance restored within 3 days
- Low Severity – Must be supported 8x5, business hours 7:45 – 4:30, Central time.
* Vendor must be able to respond within 2 days
* Vendor must be able to diagnose the problem within 4 days
* Vendor must be able to have the system operational within 2 weeks
* Vendor must have full functionality and performance restored within 1 month
Performance Standards
Performance establishes the criteria for System availability and responsiveness that are critical to the
effective operation of facilities and programs.
5/8/2017

The proposed solution must utilize robust system architecture capable of accommodating a baseline
of 6,000 concurrent users and 11,000 total users.

With the exception of planned maintenance outages, the proposed solution must be operational,
reliable, and available (24x7x365) for essential business processes and mission-critical business
operations. Proposer must define in detail their tiered support structure, including response time to
varying levels of criticality of support incidents i.e. System Down, Critical/degraded and Normal.

The proposed solution must provide a response to a query within 2 - 5 seconds under peak load 95%
of the time, measured monthly and in no case should response time exceed 15 seconds.
Page 4 of 7
TECHNICAL REQUIRMENTS TEMPLATE
Existing Technology Environment Attachment
This section presents an overview of the current technology infrastructure. The DOC technology infrastructure
consists of systems provided by DOC/BTM.
Servers
All server hardware must conform to the following DOC hardware standards:
 IBM Server x3650
 Quad-Core Intel Xeon Processor E5420 (2.5Hz, 12mb L2 1333Mhz 80w)
 4gb RAM
 Windows 2003 Enterprise Server SP2 and Windows 2008 R2
Desktops
All desktops hardware must conform to the following DOC hardware standards:
 Lenovo ThinkCenter M58
 Intel Core 2 Duo Processor E8400
 3gb RAM
 160gb 7200 rpm S-ATA HDD
 Intel Graphics Media Accelerator
 Intel Gigabit Ethernet
 Windows XP Professional SP2
Laptops
All laptops hardware must conform to the following DOC hardware standards:
 Lenovo R400 ThinkPad
 Intel Core Duo Processor P8600
 3gb RAM
 80gb 5400 rpm HDD
 14.1” 1280x800 LCD
 Intel X4500HD
 Intel Gigabit Ethernet
 Windows XP Professional SP2
Multi Function Devices
All printing / scanning needs must follow DOC standards:
 Ricoh (Lanier) LD series devices
 Global Scan scanning software
Network
The network infrastructure that supports department operations is a comprehensive mix of facility-based LANs
supported and interconnected by a DOC WAN utilizing several types of links and transports. The DOC WAN is
configured in a hub and spoke arrangement with the DET Datacenter being the hub and all remote sites being
spokes. The network is TCP/IP based with no use of IPX/SPX or Appletalk. Specific technology sets that
compose the DOC network are:

5/8/2017
Wide Area Network (WAN) – The WAN combines BadgerNet and the telecommunication links listed
below to interconnect the DOC LANs. BadgerNet is operated by the Department of Administration’s
Page 5 of 7
TECHNICAL REQUIRMENTS TEMPLATE
Division of Enterprise Technology (DET) and provides a significant portion of DOC’s
telecommunication links. Although these links are reliable, they do not provide connection to all of the
DOC remote locations. The combination of services provides a reliable backbone for the computing
environment.





20 ISDN connected locations
120+ BadgerNet T1s
4 BadgerNet DS3s
2 BadgerNet DSLs
LANs – Connected to the WAN by various telecommunications facilities, the LAN communication is
generally based on Cisco equipment. The Cisco switches use gigabit fiber for in-house transport and
connectivity of end-user workstations, printers, and servers.
 IP based network – DOC is an all IP based network infrastructure
 Dial-in services – DOC manages an AS5300 dial solution for some of the remote mobile users to
access the DOC network. This access uses an RSA ACE server with RSA Secure ID FOBs for
authentication to network resources.
 Redundant firewalls – DOC uses a pair of redundant firewalls to facilitate security both within
the DOC network as well as with connectivity to outside resources.
These technologies provide the overall connections between DOC facilities, DOC headquarters, DOA/DET, and
the Internet. In addition to these technologies, BTM employs industry-standard security components. The
bureau is focusing several staff members, significant investment capital, and numerous projects aimed at
upgrading its network facilities.
5/8/2017
Page 6 of 7
TECHNICAL REQUIRMENTS TEMPLATE
Applications Software
All software must meet following DOC standards where applicable:
 Supported application servers are WebSphere 7.0 or higher, or Microsoft IIS 6.0 or higher
 Java 2 Enterprise Edition (J2EE 1.4.2)
 Any software installed on DOC workstations must pass the BTM Software Certification Process.
 Must be easily deployable to the desktop via LANDesk 8.7 or above
 Any software must be able to run with the following minimal workstation standards
- Intel P4 2.26Ghz
- 512 RAM
 Any Active X Controls, Java Plug-ins, or other “heavy” plug-ins must go through the BTM Software
Certification Process.
 Must function on Internet Explorer 7.0 or higher
 Must be able to operate in a Citrix environment
 Must function at a minimum screen resolution of 800x600.
5/8/2017
Page 7 of 7