Appendix D  - Technical Requirements

Technical Requirements

Technical Requirements

Application Services

TECH-001

Please describe your proposed application architecture and how it supports future changes in technology and business requirements. Include a narrative description and diagram illustrating the total architecture including all software and hardware components.

 

TECH-002

Please describe how your proposed software provides the ability to perform several actions (i.e. end-user multi-tasking such as the ability to handle multiple data intensive applications, view multiple analyses or processes simultaneously) in the same work area. If proposing a browser solution, please describe how multiple browser instances are handled by the application. Are each of the instances their own unique session?

 

TECH-003

Please describe the ability of software to integrate with Microsoft Office tools, including the ability to extract data to Excel or from other MS Office applications. Describe how the software can create MS Word documents or use MS Word templates.

 

TECH-004

Please describe how the software addresses the problem of complex processes that require the participation of multiple groups. Include details on the ability to define, manage, and execute automated business processes through a GUI, both in terms of what has to be done, and by whom. Also explain how the package can integrate with FileNET Panagon Workflow product either directly or via XML.

 

Hardware

TECH-005

Please describe your proposed optimal hardware platform / configuration (servers, workstations, printers, etc.) for the Development, Testing, Production and Reporting environments. Be sure to include all environments required for a system of this size and complexity.

This description must include a detailed layout of individual servers (Application, Database, Web, etc.) and be in compliance, to the extent possible, with the State of CT EWTA standards. Enterprise servers must be among the choices below (listed in alphabetical order). This is a mandatory requirement.

Hewlett-Packard Unix (HPUX)

IBM OS/390

Microsoft Windows 2000

Sun Unix (Solaris)

Application, database and print servers should be Windows 2000, provided by top tier hardware suppliers.

The State of CT envisions three types of user roles. They are transaction processing, decision making, and casual self-service. Please indicate your proposed platform for each user type.

Thin client configurations should be Internet Browser based, or a combination of Citrix Metaframe or Microsoft Terminal Server.

Rich client configurations should run on Windows 2000.

 

TECH-006

Please describe the platform (including OS and related software) and relational database that the software is developed on. Please describe the sequence of release organized by platforms and databases and their dependencies.

 

TECH-007

Please describe the components & products used in the system to support Wireless Network Services such as server, middleware, terminals and radio communications. Please describe how these products conform to or support the State standard of IEEE 802.11.

 

Database Services

TECH-008

The State of Connecticut has identified strategic database products which include IBM (DB2/UDB), MS SQL Server and Oracle (listed in alphabetical order). Your proposed solution must use one or a combination of the listed databases. This is a mandatory requirement. Please describe the database product(s) being recommended in your proposed solution. Include descriptions of any database specific abilities or constraints of the software and its dependencies on other software and hardware.

 

 

TECH-009

If a data warehousing solution is proposed, please describe OLAP and data warehousing products offered through the bidder's product line, VAR or business partners. Describe the architecture and licensing for each product identified.

 

TECH-010

Please describe any data dictionary or metadata repository that is separate from the database system catalog that can be used as an enterprise wide universal data definition source.

 

TECH-011

Please describe the software's ability to coordinate commit transactions, either on a single machine or on multiple machines within the network. Include in your description available transaction back-out capabilities.

 

TECH-012

Please describe the ability to synchronize and replicate data to local and remote locations for purposes that could include reporting (report generation), disaster recovery and federated data management. Please include a description of how you would use MQ Series or other messaging middleware to accomplish synchronization and replication.

 

TECH-013

Please describe the tools available to support the automatic backup and restoration of files databases and repositories in the development, test and production environments.

 

TECH-014

Please describe the software's built in functionality for archiving and retrieving data. Include the process and tools for archiving, tracking and reporting archived media.

 

TECH-015

Please describe the software's ability to monitor database performance in real-time. Describe any product tools for gathering, displaying and analyzing a variety of database performance statistics including but not limited to users, throughput, tablespaces, activity logs, buffers, caches and I/O. Describe any additional system performance capabilities of the software. Describe any capabilities for integration with enterprise systems management framework, for either passive monitoring or proactive intervention.

 

TECH-016

Please describe the software's ability to provide logical and physical data modeling capabilities, including graphically depicting data on an Entity-Relationship Diagram, reporting capabilities of entities and attributes, zooming in and out of data models, dividing the model into smaller segments/subject areas (Membership, Claims, etc.) database generation based on a subset of a larger model, and producing model documentation.

 

Organization

TECH-017

Please describe FTE requirements, job titles and levels of experience by module to support your proposed ERP system, including but not limited to the application, database, operations, help desk, security, and network for an organization the size of the State of CT. Include details for training.

 

Reporting

TECH-018

Please describe the software's reporting capabilities, addressing the following key points:

Identify reports that are resource intensive and explain how you preserve online performance when executing these reports

Physical distribution of report pages (e.g. multiple reporting sites, local printing, electronic bursting, faxing)

Report distribution via system alerts

Report scheduling

Online report viewing

Integrate with FileNET's Panagon IDM product

Reporting for multiple versions of the same report to comply with retention regulations

Provide a list of the page sizes and layouts supported

Support of customized reports

Centralized check printing for all business units (must be able to utilize the State's Xerox 4635MX laser printer)

Support various report formatting and styles (grid, tab, cross tab, and graph styles)

Depict nested data windows for multiple levels of drill-down (reports within a report)

Document Services

TECH-019

The State of Connecticut's strategic product for document management is FileNET Integrated Document Management Suite (i.e. Panagon IDM). Please describe the ability of your software to interface with our strategic direction for document management. If you are unable to interface with FileNET, please describe the software's approach to content and document management. Included in this should be the ability to physically store documents as "objects" within the database. Describe the software's ability to create, view, and annotate imaged documents and to create, view and modify electronic documents, to perform wild card and partial searches and to maintain historical records of changes to a document. Please describe the software's ability to manage and publish documents so that document history of revisions and publication can be traced. Also describe the software's ability to limit access to documents to those authorized to view the information. Include a discussion of its ability to prevent the existence of documents from being revealed during a search by those who do not have the authorization to read them. What document management product or software do you use to accomplish this?

 

Web Services

TECH-020

Please describe the ability of your software to deploy network-centric applications in Intranet and Internet environments.

 

TECH-021

Please describe the features of your system that support a robust browser interface and those that do not. Explain your plans to provide a browser interface to any features that currently do not support one. Please describe the browser that you support their versions and at what level they are supported. What browser functions are available to the application (e.g. refresh, back, forward buttons)?

 

TECH-022

Please describe how your proposed software will support executing different types of applications and reporting tools from within a browser or thin client. (e.g. HTML, JAVA Applets, Citrix/Metaframe). If Java applets are proposed, describe the footprint requirements on the client. Also describe the ability to support automatic refresh of the applets and upgrades to new versions.

 

TECH-023

Please define the software's minimum requirement levels for use with web browsers (versions, types, etc.).

 

TECH-024

Please describe the State's ability to leverage portal technology based on your proposed solution. Include a description of the types of portals your application supports (e.g. enterprise, market, content).

 

TECH-025

Please describe how your software allows for interest in a particular piece of information to be registered, and then changed or new information to be communicated to the subscriber list.

 

Network

TECH-026

The ability of the proposed solution to utilize TCP/IP network protocol is a mandatory requirement. Please describe how the proposed system conforms with the State of CT network architecture standards and is capable of scaling and upgrading with any future plans. Please refer to Appendix I for more information on the State's network standards and current infrastructure.

 

TECH-027

Please describe the deployment options available for the software to run in a thin client environment (e.g. Citrix Metaframe, Microsoft Terminal Server, and browser based). This is a mandatory requirement.

 

TECH-028

Please describe the ability of the software and configuration to operate with common Firewalls (such as Checkpoint) having standard enterprise wide settings.

 

TECH-029

Please describe the software's ability to mediate traffic between a protected network and the Internet via proxy servers, shielding or screening server address.

 

TECH-030

Please describe the software's ability to establish, maintain and terminate connections across a communication network.

 

Security

TECH-031

Please describe how the application addresses a comprehensive role-based security approach that provides for access to the application and toolsets, access to function, access to data within the function and permissions for add, change, delete and inquire.

 

TECH-032

Please describe how security is handled within the development and execution toolset and how it interacts with the security functionality of the Native OS and the database. Describe your support of Novell NDS / e-Directory, i.e. LDAP and DIRXML.

 

TECH-033

Please describe the ability of software to conform to SSL V3 and IPsec protocols.

 

TECH-034

Please describe the products capabilities as it relates to remote home based browsers, wireless access protocol, ADA compliant access via web browsers and any other unique access methods and media. Please provide examples of implementation with other clients as proof of concept.

 

TECH-035

Please describe the software's ability to use encryption and authentication technologies. The State current standards are Nortel VPN for encryption and SecureID for authentication. Please describe the product's ability to interface with these technologies or provide alternative configurations. What is your recommended method of security and what are the overhead implications? In addition, provide details in relation to certificates, electronic signatures, PKI and biometrics options.

 

System Building

TECH-036

Please describe the ability of the software to rapidly build and modify screens, windows, or reports including its controls and variables to depict user requirements.

 

TECH-037

Please describe the ability of the software to do prototyping to graphically display screens, windows, reports and dialog flows of the application. This prototyping should be as these elements would appear at run-time.

 

TECH-038

Please describe the software's tool that provides a common repository for development objects, design documents, source code, test plans and data. Describe the capability to apply this tool to external applications.

 

TECH-039

Please describe the software's ability to publish documents, including on-line, application development and content related documentation.

 

TECH-040

Please describe the software's source code debugger including the ability to unit test program code, to locate the source of errors via monitoring and to step through program execution line by line or over function calls. Describe any functionality to view variable values, to display source code line numbers and to modify variable values while stepping through the execution of a program.

 

TECH-041

Please describe the capabilities of any testing tools delivered with the software or through integration with third party. This can include the creation, load and maintenance of test data, manipulation of test dates, creation of test scripts and the ability to track all the test activities. Also define any tools for test analysis, including impact analysis of changes and comparison of expected and actual results.

 

TECH-042

Please describe the capabilities to generate forms and reports at runtime and the ability to generate SQL scripts to new or altered database objects.

 

TECH-043

Please describe the method used for communication within an application, between modules and across applications.

 

TECH-044

Please describe the APIs your system exposes to external applications and the technologies supported (e.g. DCOM, J2EE, CORBA, etc.). Please provide a list of the APIs currently available.

 

TECH-045

Please describe internal version control hooks, check-in/check-out capabilities and the ability to plug into external controls to allow team development.

 

TECH-046

Please describe the software's ability to PUSH information to applications that have registered to be notified of an event (e.g. employee termination).

 

TECH-047

The strategic state product standard is FileNET's Panagon Workflow. Please describe the software's ability to integrate with FineNET's Panagon Workflow. In addition, describe any of the proposer software's delivered abilities to provide electronic workflow and attach appropriate documentation (e.g. bi-directional electronic routing of documents for approval or other tasks). Your description should also address, though not be limited to, the following functions:

Escalation and alternate routing

Splitting an event into multiple events and then coalesce

Process monitoring

Event notifications and messaging

Graphical modeling tool

Approval hierarchies

Navigational views

 

TECH-048

Please describe how your developer's toolset presents a single view of the entire environment and performs tool-to-tool communications, integrating the development environments.

 

 

Communication Services

TECH-049

The State of CT is in the process of implementing Novell Directory Services / e-Directory. Please describe how the application could interact with LDAP compatible directory services to provide data propagation, centralized login, and authorization and access control. Can the application use LDAP directory services directly in place of its directory services?

 

TECH-050

Please describe the capabilities of the software for inbound and outbound asynchronous interfaces, using a message oriented middleware. The strategic State product standard is MQ Series. Please describe any capabilities or restrictions beyond simple extract files using MQ Series. What other alternative options for message oriented middleware are supported?

 

TECH-051

Please describe the ability of the software to send and receive asynchronous communications. Include examples of inbound and outbound messaging in relation to e-mail, EDI, HTML, XML and FAX. Please describe the capabilities of the software for using SMTP e-mail and MS Exchange 2000/Outlook e-mail.

 

TECH-052

Please describe the ability of the software to integrate with legacy systems and to transfer data from existing systems into the new ERP System. The ability to integrate with the State's legacy systems is a mandatory requirement. Please describe the delivery vehicles that are available for integration (e.g. APIs, file transfer, batch, messaging). Please also describe the system's ability to apply the same edits and validation levels to batch and interface transactions as it would to on-line transactions.

 

TECH-053

Please describe the current and future approaches (plans, schedules, etc.) to using XML and SOAP in the development of the application software and in supporting those interface and interchange standards.

 

TECH-054

Please describe how the software handles alternative input formats, including but not limited to FAX, OCR and OMR.

 

TECH-055

Please describe the software's faxing capabilities which should include the ability to fax directly from the application (i.e. for notification purposes, invoices, purchase orders, RFI, RFQ, etc) and the ability to receive and process faxes within the software (i.e. proposals, invoices, quotes, etc). Also describe the how the software interfaces with other FAX software/gateways.

 

TECH-056

Please specify the specific EDI transaction sets supported by the software.

 

Configuration Management

TECH-057

Please describe the software's approach to release management. Include descriptions of the following:

Capability to control multiple versions of source components and data as they are moved from the development environment through the test environment to the production environment

Promotion mechanism to move components from one environment to another.

Mechanism for reverting to a previous release.

Audit trails per release.

Reporting on releases.

Change management support capabilities such as conversion tools that catalog changes and perform automatic data conversions and reapply program modifications to the new release. Include a description of the type of changes that can not be applied automatically.

Upgrade utilities such as tools that support identification of net differences between releases listing areas that need specific attention.

 

TECH-058

Please describe your approach to product life cycle management. Describe your release strategy for product upgrades (both major and minor), major revisions and maintenance and bug fixes. Also address the timeframes between major product releases and minor product releases. Please specify the amount of time that previous versions remain supported.

 

TECH-059

Please describe any dependencies of your application on other software and other software versions / releases within your proposed configuration.

 

TECH-060

Please describe the ability of the software to validate versions. Please describe how the software ensures functionality by monitoring, identifying and validating the environment integrity prior to and during program execution.

 

TECH-061

Please describe the tools available to enable automated distribution of data and software to the workstations and servers. How well does it fit in with other standard software distribution tools?

 

System Management

TECH-062

Please describe the software system monitoring capabilities. Include details on what is monitored, alert thresholds and the notification process. Describe the software's integration with monitoring tools. What aspects of performance are monitored? What are the application's own monitoring capabilities? To what extent are the application's own monitoring capabilities available to the external monitoring tools (i.e. Tivoli, CA Unicenter)? Also describe the system's ability to view user sessions and assist with processing a transaction or a report request.

 

TECH-063

Please describe the software's ability to provide performance analysis. Include all available metrics, such as tracking of CPU utilization, disk space, system warnings and errors. Please describe how this can be related to application and database performance.

 

TECH-064

Please describe the error alert, tracking and notification interface for the different levels and states of exception processing. Include details on any diagnostic assistance and audit trails of specified actions that are available to system support personnel. Also address the notification process for business users and support staff of business events and/or system alerts. Include ability to interface with various e-mail systems, including Exchange 2000/Outlook 2000 and standard enterprise help desk software.

 

TECH-065

Please describe the software's ability to collect performance data, both centrally and end to end. Is the software proprietary in nature, does it use standards interfaces? Please also describe the software's ability to relate performance of the application to specific resources, events, transactions and components of the applications. Include a description of the software's ability for tuning the applications and improve performance. Does the software have the ability to perform tuning adjustments and allow implementation while the application is running? Please describe the system's ability to perform remote diagnostics.

 

TECH-066

Please describe the software's ability to coordinate transactions either on a single machine or on multiple machines within the network (i.e. approach to load balancing, failover, and commit logic). Please describe the transaction back-out capabilities.

 

TECH-067

Given the criticality and magnitude of this project, the State desires a 'High -Availability' system architecture proposed. Resiliency, redundancy and manageability are key components of a 'High-Availability' solution and should be addressed in the proposed architecture. Although the State desires 7x24 availability, a four hour outage, due to a component failure is acceptable.

Please describe the systems fault tolerance and disaster recovery approach, detailing all levels of recovery from a single update failure to total system failure. Based on your proposal, please describe any single points of failure and what reasons the application (or parts of the application) must be brought down. Also include a description of how this affects availability and reliability and include a description of technical support services available.

 

TECH-068

Please describe your software's start up and shutdown procedures including any dependencies (e.g. reboot). Describe the software's ability to make configuration changes without requiring a reboot.

 

TECH-069

Please describe the ability of the system to perform mass storage management and backup/recovery functions. The State of CT currently uses an EMC DASD farms solution. Please describe how this environment can be utilized or provide an alternative recommendation.

 

TECH-070

Please describe your approach to and model for sizing the server platform(s), network (required bandwidth), and database. Include a list of all assumptions that are inherent to the sizing model. Also describe how this approach supports the ability to perform benchmarking and future scalability.

 

TECH-071

Please describe the control structure and framework for batch processes. Include automatic recovery and restart, run to run balances, batch totals and any scheduling capabilities delivered with the tool or through a third party software. If a mainframe environment is proposed, describe the software's ability to use IBM tools or CA scheduler or similar tools found in these environments.

 

TECH-072

Please describe the software's strategies and tools available for capacity modeling and planning.

 

TECH-073

Please describe any internal controls for tracking users and software usage or metering to help manage software licensing.

 

TECH-074

Please describe your ability to provide for the software to interface with help desk services software. Please provide a list of help desk service products that your software has integrated with in prior installations.

 

Benchmarking

TECH-075

Proposer must provide a certified application benchmark of a configuration similar to your proposed configuration. Include the following information for all tiers where applicable:

Hardware vendor

Operating system

RDBMS

Total disk space

System components and release version

Test script

Number of tested benchmark users

Throughput - online transactions per hour

Throughput - batch updates per hour

Average DB response time

Average dialog response time

CPU utilization

WAN Performance

Batch Performance

Network saturation test

 

TECH-076

Please provide a breakdown of your ERP configurations (Platform, OS and Databases) install base by size.

 

Table of Contents
Index of Comptroller's RFPs
Comptroller's Home Page