BCH Telecom

Installation and Implementation of Single Sign-on Solution

March 9, 2008

I. Introduction

BCH Telecom is accepting proposals for the installation and implementation of single sign-on (SSO) solution into the network frame of their technical support department, with a user base of over 1000. SSO is needed to lessen employees' stress on remembering multiple login names and passwords, lessen administrator's burden of managing separate password databases on different servers, reduce calls to help desk for password reset, and reduce login time.

II. Time and place of submittal

The deadline for receipt of responses shall be 11:59 p.m. EST on Sunday, March 30, 2008. Responses received after this date and time will not be considered and will be returned to the respondents.

Respondents shall submit one (1) original signed, three (3) hard copies, and one (1) electronic copies of their proposal to:

Celeste Hasselbach
BCH Telecom
Technology Department
201 S. Grant Ave.
Columbus, Ohio 43215-5399
teamSSO@email.franklin.edu

III. How proposals will be evaluated

Responses to the RFP will be reviewed by the IT Project Manager using the following criteria:

• Quality of proposal and how well requirements and goals are met


• Total cost


• Time estimate for project as outlined in the project plan


• Demonstrated experience in the implementation and installation of SSO as well as related projects

IV. Proposal requirements

• Include the name, address, phone number, and email address of the person to contact regarding your company's proposal.


• Proposals must be fully organized, indexed, and refer to all requirements stated in RFP.


• Include your company's management credentials and a listing of all staff members who will be working with this project.


• Proposal must include a list of references for previous SSO implementation projects.

V. Goals and objectives for project

BCH Telecom is requesting to implement a SSO solution to integrate Microsoft Active Directory and a UNIX system. The goal is to minimize user interruption and produce a single login name and password. A single point of authority needs to be setup to use Active Directory.

VI. Critical success factors

A successful solution allows users of the system to only have to sign-on once. User should not have to reenter login name and password to access the either system. Once authenticated, a user should be able to connect to either system without having to authenticate again. Also, the users of the systems will only have to maintain a single password on Active Directory. The UNIX system will obtain user information from Active Directory.

VII. Functional specifications of present system (if applicable)

• The single LDAP authority is Microsoft Active Directory.


• Each system is currently autonomous. Users account must be created and maintained on each system.


• Each system has a different password policy (i.e. duration, length).


• Currently both systems are on the same network and are able to communicate using TCP/IP.

VIII. Functional specifications of projected system

• Every user will be maintaining a single login name and a single password policy.


• The support staff maintains a single point of authority on Active Directory.


• The creation and termination of users and groups is to be maintained on Active Directory.

IX. Project oversight

Vendor will cooperate with BCH project manager through the use of the following project oversight, communication, and management processes:

• A proposed project plan with milestones for software installation, configuration, training, implementation, delivery of documentation, and project completion will be submitted by the vendor.


• Attendance and participation in weekly project status meeting with BCH project manager.


• Documentation of weekly achievements and planned activity for the upcoming week will be submitted in writing to the BCH project manager.


• BCH project manager will be alerted of new discoveries that impact the timeline and success of the project within 24 hours of discovery.


• Changes to scope of project will be submitted in writing and will occur only with approval of BCH project manager.

X. Staffing requirements

Vendor will provide a project leader who will be responsible for communicating with the BCH project manager. Professionals employed by the vendor will be well versed in Active Directory and Unix security requirements, with an understanding of the implementation of LDAP.

BCH Telecom will provide a project manager to oversee and coordinate the project. The vendor will have access to technical staff within BCH as needed during the discovery process and installation process.

XI. Documentation requirements
The following minimum documentation will be submitted to BCH Telecom:

• A migration document detailing the strategy for deploying single sign on to the end users


• Documentation suitable for distribution to end user explaining the new sign on process


• Documentation for ongoing maintenance of the single sign on solution suitable for use by BCH technical staff


• Guides to be used for assisting users with common questions and issues pertaining to single sign on solution designed for use by BCH help desk staff

XII. Migration and acceptance requirements
The vendor will provide onsite or online technical support for migration of the first 100 users. BCH technical staff will oversee migration of the remaining 900+ users with vendor providing validation of the migration of users 101 through 200. Migration of approximately 1000 users will be completed within a mutually agreed upon period of time not to exceed three weeks. Successful migration of 1000 users will be the first component of system acceptance.

Training of BCH technical staff for self sufficiency in ongoing maintenance and support of the SSO will be required. Testing and verification of proficiency will be submitted as the second component for system acceptance.

XIII. Conclusion

Deadline for submitting a response to this RFP is 11:59 p.m. EST on Sunday, March 30, 2008, and will include the following:

• Complete proposal with an index; one signed original, three copies, one electronic


• Complete contact information


• List of management credentials


• List of staff members to be assigned to the project


• References for previous SSO installations


• Timeline for project identifying key milestones


• Cost of the project