Computer Information Services RFP and Cover Letter to Vendors (166163293)

7/30/2019 Computer Information Services RFP and Cover Letter to Vendors (166163293)

http://slidepdf.com/reader/full/computer-information-services-rfp-and-cover-letter-to-vendors-166163293 1/42

Computer Information Services RFP and Cover Letter to Vendors

CAUSE INFORMATION RESOURCES LIBRARY

The attached document is provided through the CAUSEInformation Resources Library.

As part of the CAUSE Information Resources Program, theLibrary provides CAUSE members access to a collection ofinformation related to the development, use, management, andevaluation of information resources- technology, services,and information- in higher education. Most of the documentshave not been formally published and thus are not in generaldistribution.

Statements of fact or opinion in the attached document aremade on the responsibility of the author(s) alone and do notimply an opinion on the part of the CAUSE Board of Directors,officers, staff, or membership.

This document was contributed by the named organization tothe CAUSE Information Resources Library. It is theintellectual property of the author(s). Permission to copy

or disseminate all or part of this material is grantedprovided that the copies are not made or distributed forcommercial advantage, that the title and organization thatsubmitted the document appear, and that notice is given thatthis document was obtained from the CAUSE InformationResources Library. To copy or disseminate otherwise, or torepublish in any form, requires written permission from thecontributing organization. For further information: CAUSE,4840 Pearl East Circle, Suite 302E, Boulder, CO 80301; 303-449-4430; e-mail [email protected].

To order a hard copy of this document contact CAUSE or sende-mail to

[email protected].

TABLE OF CONTENTS

Section 1 - Introduction....................................1Definition of College...........................................1Purpose of Request for Proposal.................................1Structure of Request for Proposal...............................1Vendor Proposals................................................3

General......................................................3Organization.................................................4

Content......................................................5Format.......................................................7Process and Timetable........................................7

Reserved Rights.................................................8Business and Financial Contractual Requirements.................9

Section 2 - History and Direction of College InformationServices...............................................13History......................................................13Current Environments...........................................13



Network.....................................................13Institutional...............................................14Academic....................................................14Administrative..............................................15

Direction......................................................16

Section 3 - Network Information Services................18Hardware.......................................................18Software.......................................................18Transition.....................................................19

Section 4 - Institutional Information Services..........21Hardware.......................................................21Software.......................................................21

User Access.................................................21Library Information System..................................22Office Automation...........................................22Data Sharing................................................23Access To and From Remote Computing Facilities..............23User Created Information....................................23Bulletin Boards.............................................24Industry Standard Software..................................24Common User Interface.......................................24Interoperable Software Applications.........................25

Uninterruptable Power Systems...............................25Other.......................................................25Transition.....................................................25

Section 5 - Academic Information Services...............26General........................................................26Overviews......................................................26

Needs.......................................................26

Solutions...................................................26Components..................................................27First Component: Microcomputers................................28

General.....................................................28General Student Access to Microcomputing....................29

Hardware.................................................30Software.................................................30Transition...............................................30

Faculty Access to Microcomputing............................30Hardware.................................................31Software.................................................31Transition...............................................31

Computer Aided Design Classroom and Laboratory Computing....31

Hardware.................................................32Software.................................................32Transition...............................................32

Engineering Graphics Computing..............................32Hardware.................................................33Software.................................................33Transition...............................................34

Summary of First Component: Microcomputers.................34Second Component: Networking..................................34Third Component: Minicomputer.................................35



Hardware....................................................35Software....................................................35Transition..................................................36

Section 6 - Administrative Information Services.........37Hardware.......................................................37Software.......................................................38

Student Information and Campus Administrative System........38Operating System and System Software........................40

Transition.....................................................41

Section 7 - Summary of Information Services.............42Summary........................................................42Implementation Plan............................................45

Appendix A - General Municipal Law.......................46

Section 1 - Introduction

1.1 Definition of College

Hudson Valley Community College, hereafter referred to as the"College", is a public, comprehensive community college. The College,sponsored by Rensselaer County and supervised by the State University

of New York, is accredited by the Middle States Association ofColleges and Secondary Schools. Programs and curricula are registeredby the State Education Department and approved by the State UniversityBoard of Trustees.

The College's enrollment for Fall 1989 was composed of approximately5,500 full-time and 3,800 part-time students. This 9,300 totalstudent population resulted in the generation of 6,700 full-timeequivalent students.

The mission of the College is to serve the people of Rensselaer Countyand other areas in appropriate and diverse ways, striving always toimprove their quality of life through education, training and service

at an affordable cost. Through its dedication to teaching andlearning the College makes it possible for every applicant to pursue asuitable program of study. The mission of the College is to offer arange of programs which serve the educational needs of a diversepopulation. The College serves students from Rensselaer County, fromother areas of the State, from other states, and from foreign nations.

The College's 1989-1990 Statement of Mission and 1979-1989 President'sReport are included to further define our institution.

1.2 Purpose of Request for Proposal

The College invites suppliers of communications and computer hardware

and software systems to submit formal responses for providinginformation services to the College. The services will include thehardware, software, installation, testing, data conversion, andtraining necessary to implement a successful vendor's response. Avendor may respond to a single part, to multiple parts, or to allparts of this Request for Proposal.

1.3 Structure of Request for Proposal

We have structured this Request for Proposal as follows.



Section 1 - Introduction

This section will provide vendors with information regarding thepurpose of the RFP; the structure of the RFP; the organization,content, and format for vendor responses to the RFP; the timetablefor analysis of vendor responses to the RFP; and the timetable forCollege recommendations for acquisition of communications andcomputer systems.

Section 2 - History and Direction of Information Services

This section will provide vendors with information regarding theevolution of computing at the College from a data processing to acomputing services environment and to our vision for an informationservices environment.

Section 3 - Network Information Services

This section will provide vendors with information regarding thehardware, software, and transition requirements of our vision forproviding information services on a campus-wide network of computingenvironments.

Section 4 - Institutional Information Services

This section will provide vendors with information regarding thehardware, software, and transition requirements of our vision forproviding campus-wide institutional information services, such as anElectronic Mail system available to all students, faculty, andstaff.

Section 5 - Academic Information Services

This section will provide vendors with information regarding thehardware, software, and transition requirements of our vision forproviding academic information services, such as increased student

and faculty access to microcomputers and continued support for theindustry-standard software requirements of our Computer InformationSystems and Computer Science curricula.

Section 6 - Administrative Information Services

This section will provide vendors with information regarding thehardware, software, and transition requirements of our vision forproviding administrative information services, such as an integratedStudent Information and Campus Administrative System withcapabilities equal to, or better than, our current system andimproved software tools for user access to and manipulation of datacontained in this system.

Section 7 - Summary of Information Services

This section will provide vendors with a summary of the previousinformation regarding the hardware, software, and transitionrequirements of our vision for providing network, institutional,academic, and administrative information services and will provide aprojected plan for implementation of these services.



1.4 Vendor Proposals

1.4.1 General

Vendors should stress clarity, completeness and brevity ofpresentation when preparing responses to this RFP. Vendors arerequested not to perceive the RFP structure as a desire for them topropose some number of distinct computing environments. Vendorsshould propose solutions which simply and cost-effectively address ourinformation service needs. A vendor's solution(s) may include one ormany computing environments.

Vendors may elect to respond jointly to this RFP and in this case,each corporation name should appear on the outside front cover andspine of the binder.

Vendors may submit a primary proposal and an alternate proposal(s).Alternate proposals must be used when a vendor wishes to propose morethan one solution for providing any or all of the network,institutional, academic, or administrative information services wehave identified. For example, a vendor proposing two StudentInformation and Campus Administrative Systems must include the firstin a primary proposal and the second in an alternate proposal.

Primary and alternate proposals must follow the format described inthis section. Only material which differs from the primary proposalshould be included in alternate proposals. All pages of alternateproposals must be clearly marked as Alternate Proposal #1 (or #2, or...) to prevent confusion.

The College invites all vendors to our campus for an RFP presentationon Wednesday, June 6, 1990 from 10:00 to 12:00 in the Faculty StaffConference Room located on the 2nd floor of the Raymond H. Siek CampusCenter. After a brief overview of the RFP, vendors will have anopportunity to ask questions for clarification of any outstandingissues.

Vendors must submit 6 copies of each primary and alternate proposaland 2 copies of all supporting documentation to the College by nolater than 2:30 PM on Friday, July 27, 1990. Vendor proposals must besealed, labeled as shown below, and delivered to the Office ofBusiness Services.

Jane S. GorzelnikDirector of Business ServicesHudson Valley Community CollegeTrustees Administrative Center45 Vandenburgh AvenueTroy, New York 12180

RFP #90-98 Computer Information Systems

Proposals which are not sealed will be rejected. Proposals which arenot received by the deadline for submission will not be accepted.

Proposals will be opened in the Conference Room of the TrusteesAdministrative Center at 3:00 PM on Friday, July 27, 1990 and thenames of those firms or individuals submitting proposals will bepublicly announced. No other public disclosure will be made until all



proposals have been reviewed and evaluated.

All provisions of a vendor's proposal must be in effect for a minimumof 180 days starting with the day after the deadline for submission ofproposals. All inquiries and correspondence regarding this RFP must bedirected to:

Bryan L. EatonDirector of Computer ServicesHudson Valley Community College80 Vandenburgh AvenueTroy, New York 12180

Telephone: 518-270-7311

All inquiries of a substantive nature must be submitted in writing,citing the particular page, section, and text in question, wheneverapplicable. Answers to questions of this type will be detailed to allvendors who have notified the College of their intent to respond tothis RFP unless the question is of such a nature that it relates toproprietary information.

Vendors who intend to respond must submit written notification to theabove address to this effect by June 20, 1990. Failure to provide

such notification will not preclude a vendor from responding to thisRFP. However, only vendors complying with this requirement will beplaced on the mailing list for official RFP communications.

1.4.2 Organization

The proposal must begin with a cover letter indicating the vendor'ssubmission of a response to this RFP and designating the vendor'sauthorized representative to the College. This cover letter must besigned by the vendor's authorized representative to the College.

The proposal must be organized and presented using at minimum thefollowing Table of Contents. Vendors wishing to differentiate

further, any or all sections of their proposal, may do so in a clearlydefined manner.

TABLE OF CONTENTS

1. INTRODUCTION1.1 Corporate History1.2 Proposal Summary

2. ADMINISTRATIVE INFORMATION2.1 Vendor Contacts2.2 Vendor Certification Statement

2.3 Vendor Customer References2.4 Pricing Information

2.4.1 Overview of All Information Services2.4.2 Network Information Services2.4.3 Institutional Information Services2.4.4 Academic Information Services2.4.5 Administrative Information Services

3. NETWORK INFORMATION SERVICES3.1 Hardware



3.2 Software3.3 Transition

4. INSTITUTIONAL INFORMATION SERVICES4.1 Hardware4.2 Software4.3 Transition

5. ACADEMIC INFORMATION SERVICES5.1 Hardware5.2 Software5.3 Transition

6. ADMINISTRATIVE INFORMATION SERVICES6.1 Hardware6.2 Software6.3 Transition

APPENDICES

1.4.3 Content

Section 1.1 Vendors must provide a brief history of their

involvement in the information services industry with pertinentinformation regarding their corporation's innovativeness, financialstability, and commitment to higher education.

Section 1.2 Vendors must provide a brief summary of their proposal

including narrative(s) on how their proposal satisfies any, or all ofthe information services we have identified and including a listing ofthe major hardware and software components being proposed for any, orall of the information services we have identified.

Section 2.1 Vendors must provide a point of contact, including

name, job title, job function, address, and telephone number, withintheir organization for each major section of their proposal.

Section 2.2 Vendors must complete and provide a signed copy of the

certification statement regarding General Municipal Law included inAppendix A of this RFP.

Section 2.3 Vendors must provide at minimum four customer

references. Each reference should be a comparably sized institution

of higher education using the proposed hardware and software products.Since we expect to visit a number of customers in the evaluation ofvendor responses, references should be located as close in proximityas possible to the College.

Vendors must submit the following information for each

customer reference.

- the organization name, address, and telephone number



- the name of a key senior-level contact person,his/her title, and his/her telephone number

- a written narrative describing the organization'ssimilarity to our College and the organization's useof the proposed hardware and software products

- a description of the number and type of computerand/or communications personnel needed to support theorganization's requirements

Section 2.4 Vendors must propose new, not used or refurbished,

hardware components in the early phases of their product life cycles.Vendors must propose hardware and software components of the latesttechnology.

Vendors must provide list pricing, discounted pricing,

state contract pricing whenever available, monthly maintenancepricing, discounted monthly maintenance pricing, delivery charges, andinstallation charges for each hardware and software componentproposed. This pricing section must follow the structure shown inSection 1.4.2 and must be separated into the three identifiedcomponents: hardware, software, and transition, for each informationservice area shown in Sections 3 through 6.

Sections 3-6 Vendors must provide narrative defining their proposed

solution(s) corresponding to Sections 3 through 6 of this RFP. Whilethe hardware components of these sections are important, the Collegewill place emphasis on the software and transition components. TheCollege views this RFP process as a software, solution-oriented one,and views the transitioning to an information environment whichprovides better services to the College, as an important part of thissolution-oriented approach. All aspects of moving from our currentenvironment(s) to the proposed environment(s) must be included in thetransition component. The College is especially interested in theconversion and training aspects of this transition.

Appendices Vendors may provide any material related to their

proposal to assist the College with our evaluation.

1.4.4 Format

Vendors must submit proposals in loose-leaf binder form with theircorporation name on the outside front cover and spine of the binder.

All proposals must be typewritten on standard 8 1/2 x 11 inch paper at10 or 12 pitch (larger paper is permissible for spreadsheets, charts,

etc...).

The major sections of the proposal shown in the Table of Contents mustbe labeled with index tabs that identify the titles of those sections.The section headings of the proposal must be numbered to reflect thoseshown in the Table of Contents. Each page of the proposal must benumbered consecutively by page in the same manner in which pages ofthis RFP are numbered.

1.4.5 Process and Timetable



In early 1989 the Computer Procurement Committee, hereafter referredto as the "CPC", was formed with responsibility for investigating,evaluating, and recommending the network, institutional, academic, andadministrative information service requirements of the College. TheCPC is composed of the following College professionals.

Dale Bryant Assistant Professor of MathematicsDon Bowman Dean of Enrollment ServicesMaureen Crean Director of Institutional PlanningBryan Eaton - Chairperson Director of Computer ServicesJoel Fatato Chief Fiscal OfficerJohn Fogarty Associate Director of Computer

ServicesFred Zipprich Dean of the School of Engineering

and Industrial Technologies

The CPC has established the following timetable of events.

April - May 1989 Conduct presentation(s) to CPC oncomputing directions in highereducation

June - August 1989 Develop schedule of events foreducating and surveying usercommunity

September - January 1990 Coordinate vendor presentations forour user community and conduct usersurvey

February - May 1990 Develop RFP to be sent to vendorsJune - July 1990 Vendors - Prepare RFP responsesAugust - October 1990 Analyze vendor RFP responses

including presentations /demonstrations by vendors and sitevisits to customer references

November - December 1990 Evaluate vendor RFP responses

January 1991 Recommendations to the College

Vendors should clearly understand that the College will not makedecisions on what product(s) to purchase based solely on pricing. Wewill take into consideration many other factors such as the vendor'scommitment to higher education, the vendor's commitment to current andevolving industry standards, and the ability of a vendor's proposedproducts to satisfy our current and evolving information requirements.

1.5 Reserved Rights

The College reserves the following rights.

- Examine the responsibility of bidders for contracts and proposedsubcontractors on a case-by-case basis including, but not limitedto, an examination of the skill, judgement, integrity, good faith,sufficiency of financial resources, quality of execution,performance and conduct on prior similar contracts, and laborpractices, of a bidder and/or of a proposed subcontractor; and toinvestigate and consider the background of such bidders andsubcontractors for this purpose including their ownership,management, affiliation, history of past performance, and compliance



with relevant state and federal laws and regulations

- Reject any, and all proposals received in response to this RFP

- Select one vendor, or many vendors to support the informationservice needs of the College

- Modify or waive irregularities in any proposals received afterconsultation with the vendor(s)

- Adjust and correct any vendor supplied cost figures found to be inerror with notification to the vendor(s)

- Utilize any and all ideas submitted in the proposals received unlessthose ideas are covered by legal patent or proprietary rights asstated by the vendor(s)

- Adopt any, or all parts of a vendor's proposal in selecting theoptimum configuration

- Negotiate hardware and software configurations different from thoseproposed by the vendor(s)

- Amend the RFP specifications after release in order to correcterrors, respond to oversights, or modify requirements

- Begin contract negotiations with another vendor in order to servethe best interests of the College in the event that we areunsuccessful in negotiating a contract with the selected vendor(s)

- Change any of the scheduled dates

- Seek 3rd party financing

- Acquire 3rd party hardware and software

- Accept or reject price decreases made after submission of proposals

1.6 Business and Financial Contractual Requirements

Transfer of Subcontracting of Contract - No contractor to whom anycontract for these specifications shall be awarded shall assign,transfer, convey, sublet, or otherwise dispose of the same or hisright, title, or interest therein, or his power to execute suchcontract, to any other persons or corporation without the previousconsent in writing of the College.

Default Provisions - In case of default by the contractor, the Collegemay procure the article or services from other sources and hold the

contractor responsible for excess costs occasioned thereby.

Contractor's Guarantee - By submitting on these specifications, thevendor binds himself to all conditions in these specifications,irrespective of any formalities in his order acknowledgement. Noattachment or part may be substituted or applied contrary tomanufacturer's recommendations and standard practice. Any variancewith the specifications must be stated within the submitted bid, andmay, after review of all consequences of the variance, disqualify thebid. Accessories supplied shall be compatible with the rest of the



equipment.

Contractor guarantees that the equipment is standard new equipment,latest model of regular stock product with all parts regularly usedwith the type of equipment offered. Each unit delivered is guaranteedagainst faulty material and workmanship for a period of one year afteracceptance of delivery by the College, unless otherwise specified.If, during this period, any such faults develop, the unit or partaffected is to be replaced without any cost to the College.

All regularly manufactured stock electrical items shall be listed byUnderwriter's Laboratory, Incorporated. Other electrical equipmentshall be constructed to conform to applicable portions of NationalElectrical Code. Where electronic components are part of theequipment, the manufacturer's standard guarantee shall apply.

Permits and Ordinances - In all operations connected with the workherein specified, all city and town ordinances and laws controlling orlimiting in any way the action of those engaged in the work, must berespected and strictly complied with. Contractor must obtain allpermits and pay fees, if and as required.

Hazardous Materials - Any materials required by this order that are

deemed hazardous will be packaged, marked, and shipped by the sellerto comply with all present and future federal, state, and localregulations and will further comply with any special companyrequirements. All MSDS sheets are to be directed to the attention ofthe Campus Safety Officer.

Safety and Health Devices - All equipment shall meet the requirementsof the Federal Government, the State of New York, and the County ofRensselaer Safety and Health Regulations, as well as the local safetyand health regulations of the City of Troy. Equipment shall conformto applicable standards of all national regulations.

Payment - It is the desire of the College to pay promptly. It is the

vendor's responsibility to submit invoices directly to the AccountsPayable department.

Hudson Valley Community CollegeAttention: Accounts PayableP.O. Box 569Troy, New York 12181-0569

Invoices shall include purchase order number and date, College itemnumber, description of items, catalog number, sizes, quantities, unitprices, extended prices, and date of delivery. Invoices not onprinted billheads shall be signed by vendor.

Invoices exceeding the limits established by the contract, or formaterials or services not qualifying under its specifications, are notsubject to payment.

Partial payments may be made upon properly executed invoices ofdelivered goods, unless otherwise stated in the bid. Final paymentwill occur when the materials, supplies, or equipment items have beenfully delivered and accepted.



Insurance Coverage - The successful bidder shall provide the Directorof Business Services with a certificate or proof of insurance coveragefor a minimum of:

Property Damage and Liability $ 250,000Bodily Injury Liability $ 500,000 - $ 1,000,000

Protection - Contractor shall be held liable for any injury to personsand/or property during the execution of his work and shall take allsafety measures required or affirmed during execution of his work.

Contractor's Liability Insurance - The contractor shall maintain suchinsurance as will protect him from claims under Workmen's CompensationActs and other employee benefit acts; from claim for damages becauseof bodily injury, including death, to his employees and all others;and from claims from damages to property, any or all of which mayarise out of, or result from, the contractor's operations under thiscontract.

Equal Opportunity - Affirmative Action - Executive Order Number 11246,as amended, relative to Equal Employment Opportunity and all otherapplicable laws, rules, and regulations, including Title VII of theCivil Rights Act of 1964, are incorporated herein by this specificreference. In addition, all laws, rules, and regulations applicable

to the hiring of disabled veterans, veterans of the Vietnam era, andindividuals with physical or mental handicaps are incorporated hereinby this specific reference.

The contractor further agrees that:

(a) in the hiring of employees for the performance of work under thiscontract, the contractor shall not discriminate against anycitizen in the employment of a person qualified and available toperform the work under the contract, by reason of race, color,religion, sex, age, handicap, national origin, or ancestry;(b) the contractor or any person acting on his behalf, shall not, inany manner, discriminate against, intimidate, or retaliate

against any employee hired for the performance of work under thecontract on account of race, color, religion, sex, age, handicap,national origin, or ancestry;(c) the contractor shall include this language in all subcontractsentered into, for the performance of the contract

Fair Labor Standards Act - The contractor warrants and represents thatthe goods covered by this contract have been manufactured inaccordance with the requirements of the Fair Labor Standards Act andall other applicable federal, state, and municipal laws, rules, andregulations.

Minority Business Enterprise - It is the policy of the College to takeaffirmative action to ensure that minority business enterprises aregiven the opportunity to demonstrate their ability to provide theCollege with goods and services at competitive prices.

Taxes - The College is a tax exempt organization and therefore lacksthe authority to pay taxes.

Section 2 - History and Direction of College Information Services



2.1 History

The College has a long history of providing data processing, and thencomputing services for our students, faculty, and staff. In the late1960's an IBM 1401 computer system was introduced to the College andserved both academic and administrative computing. In the early1970's a Burroughs B2500 computer system was installed and againserved both academic and administrative computing. In the middle1970's, while the Burroughs B2500 continued serving administrativecomputing, a Prime 400 computer system was installed to serve academiccomputing. Since that time the College has upgraded both academic andadministrative computing environments within the Prime andUnisys/Burroughs family of computer systems respectively.

Microcomputers were introduced to the College in the early 1980's.Apple, Commodore, IBM, and Radio Shack microcomputers were integratedinto academic computing and Burroughs microcomputers were integratedinto administrative computing. In the middle 1980's the Collegedecided to standardize on IBM PC or PC-compatible microcomputers andevaluated microcomputers from many different vendors with Zenith DataSystems being selected as the standard PC-compatible microcomputervendor. Since that time the College has experienced tremendous growthin the integration of microcomputers into both academic andadministrative computing. Five microcomputer classrooms have been

constructed, two student open-access microcomputer areas have beencreated, and hundreds of microcomputers have been provided for facultyand staff.

2.2 Current Environments

2.2.1 Network

The College's current computer networks exist uniquely, andseparately, from each other. These data communication systems includedistinct networks for the two academic super-minicomputers and the oneadministrative mainframe computer. All attached devices, includingterminals, microcomputers, and printers, are directly wired to the

specific computer system(s) to which the user requires access.

The College is in the beginning stages of a campus-wide network pilotproject. The project will allow the use of our existing campus-widebroadband cabling plant as a campus-wide Ethernet backbone. Anacademic computer system, an academic microcomputer local area networkfile server, a group of academic terminals, and the administrativecomputer system will be connected to this backbone. TCP/IP will beused in the project as a standard terminal protocol allowing commonworkstation access to multiple, and different, computing environments.

2.2.2 Institutional

The College does not currently have an institutional computingenvironment. Information services such as electronic mail, calendars,schedulers, bulletin boards, access to off-campus computing resources,and a library information system are not available campus-wide. Theseservices either do not exist at all, or exist in a unique computingenvironment which is not accessible to our entire campus population.

2.2.3 Academic



The College's academic computing environment includes two Prime 9955Model II computer systems with over 250 attached devices, includingterminals, microcomputers, and printers, and over 250 microcomputersin classrooms, laboratories, student open-access areas, and facultyoffices.

During the 1988/89 academic year over 2800 student users logged in tothe Prime systems over 110,000 times for a total accumulated connecttime of over 4,000,000 minutes. During the 1988/89 academic year over1600 students were enrolled in courses using our microcomputerclassrooms which are among the most heavily used classroom facilitiesat the College. Student usage of microcomputers in our open-accessareas was also consistently heavy.

The following charts detail the Prime academic computing environments.

Prime 9955 II Single Processor - System A

Memory 16 MegabytesDisk Storage 1.5 Gigabytes/3 Fixed Disk UnitsTape Drive 1 800/1600/6250 BPIPrinter 1 650 LPMAttached Devices 130 Terminals/Microcomputers/Printers

Prime 9955 II Single Processor - System B

Memory 24 MegabytesDisk Storage 1.5 Gigabytes/3 Fixed Disk UnitsTape Drive 1 800/1600/6250 BPIPrinter 1 650 LPMAttached Devices 130 Terminals/Microcomputers/Printers

Prime 9955 II System Software

Operating System PRIMOSEditors EMACS and EDDatabase Management ORACLE

Compilers ASSEMBLER FORTRAN IVBASIC FORTRAN 77C PASCALCOBOL 74 RPG

Programming Tool DEBUGGERCommunication PRIMELINK PRIMENET

Prime 9955 II Application Software

Computer Aided Design ANVIL 4000Computer Assisted Instruction

Authoring Language KATYElectrical Circuit Analysis P-SPICE

Graphics IGL PLOT 10Electronic Mail MAIL - from SUNY BrockportStatistical SPSS

The following narrative details the microcomputer academic computingenvironment.

Microcomputer Systems

The majority of the approximately 450 microcomputers at the College



are IBM PC and PC/XT compatible systems with Intel 8088 processorchips from Zenith Data Systems. The College has approximately 350of these microcomputers installed. The College has recently begunto purchase Zenith microcomputers with Intel 80286 and 80386processor chips and now has approximately 100 of thesemicrocomputers installed.

From this population of microcomputers, approximately 220 systemsare installed in purely instructional environments. The College hasa total of 135 systems installed in 4 classrooms each equipped with30 microcomputers and in 1 classroom equipped with 15microcomputers. Two classrooms are equipped with dual-floppysystems, two classrooms are equipped with hard disk systems and oneclassroom is networked to a file server using Novell Netware LANsoftware. The College has approximately 50 systems installed inlaboratories in many different academic departments andapproximately 35 systems installed in student open-access areas.

From the remaining 230 microcomputers, approximately 90 systems areinstalled in faculty and department chairperson offices and are usedfor instructional and academic administrative functions andapproximately 140 systems are installed in staff offices and are usedfor administrative functions.

The College is committed to providing access to education for ourcommunity's disabled student population. An important aspect ofthis commitment is providing the necessary facilities to allow forthe use of computing. We are now constructing for our disabledstudent population a 5 workstation lab for general computing and a15 workstation lab for computing in our technologies curricula.

2.2.4 Administrative

The College's administrative computing environment includes a UnisysA10H computer system with over 300 attached devices, includingterminals, microcomputers, and printers.

The following chart details the Unisys administrative computingenvironment.

Unisys A10H Dual-Processor

Memory 24 MegabytesDisk Storage 4.5 Gigabytes/9 Fixed Disk UnitsTape Drive 3 1600/6250 BPIPrinter 2 650 LPM and 2000 LPMAttached Devices 300 Terminals/Microcomputers/Printers

Unisys A10H System Software

Operating System MCP/ASEditor CANDECommunications Management COMSDatabase Management DMSIICompilers ALGOL and DCALGOL

COBOL 74Operations MARCResource Management SMFIICommunication NDLII and IDC



Unisys A10H Application Software

User Inquiry Tool ERGOElectronic Mail MAIL - from Division of Criminal

Justice ServicesStudent Information and Campus includes the components listed

Administrative System in Section 6

From the total population of 450 microcomputers at the College,approximately 140 systems are installed in staff offices and are usedfor administrative functions and approximately 90 systems areinstalled in faculty and department chairperson offices and are usedfor instructional and academic administrative functions. Approximately180 of these 230 microcomputers are connected to the Unisys A10Hsystem.

2.3 Direction

The College is in the process of changing from a computing to aninformation services environment. The information needs of ourCollege have changed and grown tremendously in the last few years.With our current computing environments we are having a difficult timesupporting these new demands for campus-wide information services.

Of primary importance to our strategy for providing informationservices to users is access from a single workstation to whatevercomputing environment(s) are required to perform their jobs. Weexpect to evolve to an Ethernet network using TCP/IP as the standardterminal protocol with our campus-wide network pilot project being afirst step in this process.

We have identified information services needed by the institution as awhole. These services can be, and in some cases are currently being,provided separately to the user groups of our academic andadministrative computing environments. As only one example, we haveelectronic mail for our academic users and for our administrative

users. These two mail systems are distinct and a user of one cannotsend mail to a user of the other. We expect to evolve to anenvironment where these institutional information services will beaccessible and common to all user groups.

The College is experiencing tremendous growth in the integration ofmicrocomputers into academic curricula and in the use ofmicrocomputers by faculty as a productivity tool. We expect to evolveto a more complex academic computing environment involving stand-alonemicrocomputers; departmental networked micro or mini computer systems;and a centralized mini, super-mini, or mainframe computer system. Thedepartmental computing environments may include networkedmicrocomputer systems using an operating system such as Novell

Netware, minicomputer systems using an operating system such as UNIX,or some combination of these systems. All of these academic computingenvironments will be connected to, and accessible from, thecampus-wide network.

The College is also experiencing tremendous growth in the integrationof microcomputers into administrative departments, in the use ofmicrocomputers by staff as a productivity tool, and in the demand foraccess to our institutional data base. We expect to evolve to anenvironment where a centralized, integrated institutional data base



will continue to support the on-line and batch processing requirementsof the College and will improve our users access to data forsupporting their own unique and dynamic information needs.

The previous brief narratives, relative to our vision for providingnetwork, institutional, academic, and administrative informationservices, represent an overview of information contained in each areaspecific section of this RFP.

Section 3 - Network Information Services

3.1 Hardware

Within the next few months the College will be entering into acampus-wide network pilot project and will be installing a broadbandEthernet supporting IEEE 802.3 standards and using TCP/IP as astandard terminal protocol.

This data communication network will attach to an already installedcampus-wide broadband video backbone trunk cable which consists of thefollowing.

- 1/2" Belden 9292, or equivalent, coaxial cable

- 300 MHZ indoor self-powered, blonder tongue, trunk amplifiers,equipped with reverse feed amplifiers and filters for 5 MHZ - 50MHZ "T" channels

Vendors should include hardware components for all proposed computersystems, terminal servers for all proposed terminals, andmicrocomputer bridges for all proposed microcomputer file servers toprovide for connectivity to a network compatible with these standards.This does not imply that a proposed microcomputer local area networkmust be Ethernet topology, but does indicate that a proposedmicrocomputer local area network must be able to connect to ourcampus-wide Ethernet backbone.

The design of the hardware to connect microcomputers to the networkshould not impact the performance capacity of the microcomputer. Forexample, a faculty member using a microcomputer for basicapplications, such as word processing and spreadsheeting, should notbe required to purchase additional memory or to sacrifice processingspeed when connecting to the campus-wide network.

Vendors should include any additional hardware components and/orcomputer systems necessary for providing management of this network.

3.2 Software

The major focus of network software will be to support communication

from any terminal or microcomputer to any College computing host,including microcomputer file servers and mini, super-mini or mainframecomputer systems. We do not expect, nor desire, that a microcomputeruser connected to the network be allowed direct access to the files onsome other microcomputer user's hard disk, or be allowed to initiateprocessing on some other user's microcomputer system.

We also do not expect to develop a microcomputer local area networkoperating system across multiple file servers using our campus-wideEthernet backbone. However, vendors should propose this kind of



computing environment if they believe that a campus-wide microcomputernetwork operating system will provide significant advantage andbenefit to the College.

The following are some examples of the campus community making use ofthe network software to allow them to access different computingresources and to perform different information service functions.

- An administrator connecting through a microcomputer to aninstitutional computing resource to send and receive electronic mail

- A secretary sending a document from a microcomputer to a computinghost that functions as a queue manager and print server

- A faculty connecting through a microcomputer to a BITNET server tosend and receive a file from a colleague at some other SUNYinstitution

- A student connecting through a microcomputer to an administrativecomputing resource to check the status of his/her financial aid

Vendors should include software components for all proposed computersystems, terminal servers for all proposed terminals, andmicrocomputer bridges for all proposed microcomputer file servers to

provide for connectivity to a network compatible with these standardsand to provide at minimum the capabilities described below.

- Support for communicating across the network to any Collegecomputing host with terminal emulation and file transfer facilities

- Support for establishing shared peripheral devices, especially highquality printers

- Support for establishing a communication link through the network toprovide access to SUNYNET and BITNET

Vendors should include any additional software components necessary

for providing accounting, configuration, fault, performance, andsecurity management functions of this network. The securitymanagement functions of the network will be critical. The ability tocollect information including times and types of usage of the networkwill be very useful. If possible, the ability to collect similarinformation whenever a microcomputer workstation is powered on bymeans of its connection to the network would be very helpful to theCollege in the management and distribution of our microcomputingresource.

3.3 Transition

Vendors should propose a plan for transition from our current

environment, where attached devices are directly connected to a hostcomputer system, to an environment where attached devices are directlyconnected to the campus-wide network. These attached devices includeterminals, printers and microcomputers. Vendors should include anynecessary hardware or software components for connection of ourcurrent population of microcomputers to this network. Microcomputersin a microcomputer local area network should be attached to thecampus-wide network through a microcomputer file server.

This transition plan should include, but not be limited to, site



preparation, hardware and software installation, support foroff-campus dial up access to and from on-campus computing facilities,training, and implementation support. This transition plan shouldincorporate, and be incorporated into, all other components of avendor's proposal. The training of our network and system supportpersonnel is especially important to the College.

Vendors may propose a plan for transition from our current networkenvironment to a network environment where all attached devices arenot directly connected to the network. Some attached devices wouldremain directly connected to a host computer system. Vendors shouldclearly explain the benefits to the College of this networkenvironment.

Section 4 - Institutional Information Services

4.1 Hardware

The hardware component(s) of the computer system(s) which will be usedfor providing institutional information services must supportconnection to a campus-wide Ethernet backbone and use of TCP/IP as aterminal protocol.

Some institutional information services, such as data sharing, areapplicable to any, and all of the computing environments beingproposed. Whenever applicable, vendors must incorporate theseinstitutional information services into other sections of theirproposal.

4.2 Software

The following sections will describe the information services we haveidentified as being needed by our entire institutional populationincluding students, faculty, and staff. These services will notnecessarily correspond to a single software application. In someinstances vendors will need to propose a software environment

including more than one software application on more than one hardwareplatform.

We understand that for some of our institutional information serviceswe are defining a direction and may not be able to implement acomplete solution at this time. Vendors are requested to respondwherever possible with complete solutions. When a complete solutionis not possible vendors are requested to respond with a partial ordirectional solution which defines for the College the stages ofimplementation required to reach our service goal.

4.2.1 User Access

Students, faculty, and staff at the College must be able to access alllevels of computing resource where the information services needed toperform their jobs are provided. We have separated computingresources at the College into three levels.

The Personal Level reflects those computing resources which are usedby individuals and are typically stand-alone microcomputers. TheDepartmental Level reflects those computing resources which are usedby a group of individuals and are typically microcomputers in anetworked micro or mini computer system. The Institutional Level



reflects those computing resources which are used by large segmentsof, or by the entire, campus population and are typically mini,super-mini, or mainframe computer systems.

A critical component of access to multiple computing resources by somany people is the ability to secure access to these resources so thatattempts at unauthorized access are tightly controlled. Vendorsshould describe in detail how access security is implemented for allproposed computing environments.

Tracking of the usage of all computing resources at the College isneeded. Vendors should describe how usage information is collectedand reported for all proposed computing environments.

4.2.2 Library Information System

The implementation of a Library Information System is of primaryimportance to the College. The Library Information System beingproposed by vendors must either be a component of, or allow for datatransfer to and from, the Student Information and CampusAdministrative System. This information environment should allow foraccess to the holdings of other libraries.

The proposed Library Information System must include the followingfunctional areas.

On-Line Public Access CatalogCirculationBibliographic and Authority Control

The proposed Library Information System should include, but does nothave to be limited to, the following additional functional areas.

Overdue Notice Inter Library LoanAcquisitions Collection DevelopmentSerial Control Collection Inventory

Material Control Equipment LoanReserve Room

4.2.3 Office Automation

A common Office Automation System including electronic mail withaccess to BITNET and activity management functions such as calendars,schedulers for meetings and rooms, action lists, and reminders is alsoof primary importance to the College. We view this system as thecenter for electronic exchange of information at the College. Theproposed Office Automation System should include an electronic mailfacility which allows for the sending and receiving of informationincluding mail messages, data files, and microcomputer files created

with word processing, spreadsheet, data base, or graphic applications.

4.2.4 Data Sharing

The sharing of data among all levels of computing resource has becomevery important to the College. As computing, especiallymicrocomputing, has been integrated into virtually all aspects of theCollege, there has developed the real need for students, faculty, andstaff to easily and electronically share data among our own Collegecommunity. There has also developed the real need for our College



community to easily and electronically share data with othereducational institutions and with state and federal agencies. Thisincludes capabilities such as the electronic exchange of studenttranscripts with other colleges and the electronic exchange of studentloan processing information with governmental agencies.

Vendors should describe their electronic mail facility's ability tointegrate data from different computing environments as describedpreviously in Section 4.2.3 on Office Automation. Vendors should alsodescribe any additional software and capabilities, such as dataextraction, data transfer, or virtual disks, which may be used in thesharing of data.

4.2.5 Access To and From Remote Computing Facilities

The ability of users to access College computing facilities from theirhomes and to access off-campus computing facilities, such as BITNET orthe LEXIS database of legal information used by our Criminal Justicestudents and faculty, has become very important.

Vendors should describe their ability to provide students, faculty,and staff with the capability of off-campus dial up access to and fromon-campus computing facilities.

4.2.6 User Created Information

The ability of users to access institutional data and to create theirown unique and dynamic information has also become very important tothe College. Vendors should describe a software environment whichallows for easy access to, manipulation of, and reporting ofinstitutional data. Vendors should include in this environment a highperformance statistical analysis tool to support our increasing needfor academic and administrative research. Relational databasetechnology and an industry standard SQL-based user interface mayprovide the College with the basis for a solution to these serviceneeds.

Vendors should not limit their responses to a single computing hostenvironment or to a multiple host environment. Vendors should proposea solution based on the integration of data being collected at any ofthe three levels of computing resource described before.

Vendors should also describe their ability to provide a desktoppublishing solution which will allow for user department creation oftheir own internal or external College reports or publications.

4.2.7 Bulletin Boards

Vendors should propose a solution for allowing the creation of publicinformation such as announcements of meetings or events, a campustelephone directory, and schedules of open hours for Collegefacilities (Bookstore, Computer Labs, Learning Resource Center,Physical Education Building, ...). This public information should beaccessible to any user of computing at the College.

4.2.8 Industry Standard Software

The College is interested in software solutions which will provide



independence from computer hardware platforms. Wherever possible, wewould like to implement software solutions compatible with current, orevolving, industry standards.

Vendors should describe their commitment to industry standards andshould propose for all sections of this RFP, software solutions whichconform to these standards. Vendors should also propose solutionswhich best support the current, and evolving requirements of theCollege. The melding of industry standard and best solutions isimportant to the long-term information services environment we areattempting to create at the College.

4.2.9 Common User Interface

The way in which a user accesses student records, a catalog of ourlibrary holdings, electronic mail, departmental budget records,computer assisted instruction modules, or any other information sourceshould be consistent.

We are describing an environment which is much more than a menu forchoosing access to one of these information sources. We aredescribing an environment where the "look and feel" of all softwareapplications used to provide information is the same. Vendors shoulddescribe their ability to provide this environment for the software

applications being proposed. This ability may include the capabilityfor the College to customize the user environment to create thiscommon user interface.

4.2.10 Interoperable Software Applications

Vendors should describe the ability of the software applications beingproposed to execute across all three levels of computing resourcedescribed before. For example, if the College were to standardize ona data base management system or a statistical analysis system whichexecuted on the three levels of computing, the training and support ofour users would become much simpler. Vendors should apply this

concept in their proposal wherever possible and wherever in theirjudgement, the solution does not become weakened by usinginteroperable software applications.

4.2.11 Uninterruptable Power Systems

Vendors should include Uninterruptable Power Systems with sufficientcapacity for providing protection from momentary power interruptionsfor all proposed microcomputer file servers and for all proposed mini,super-mini, and mainframe computer systems.

4.2.12 Other

Vendors should propose any other institutional information serviceswhich we have not identified and which would be of benefit to theCollege.

4.3 Transition

Vendors should propose a plan for implementation of these informationservices. This plan should include all aspects of the transitioningfrom those information services we currently have to the vendor'sproposed environment. The training of our system support and



departmental user personnel is especially important to the College.

Section 5 - Academic Information Services

5.1 General

The hardware and software components of the computer system(s) whichwill be used for providing academic information services must supportconnection to a campus-wide Ethernet backbone and use TCP/IP as aterminal protocol.

The College's plan for providing academic information services iscomplex in structure and includes three major components. Thesecomponents will be achieved in stages which will likely cover severalyears. Each component will be described in terms of its own hardware,software and transition requirements. In describing each component wewill share the rationale for our plan so that vendors may propose,where they believe appropriate, alternate approaches to achieving ourobjectives.

5.2 Overviews

5.2.1 Needs

Over the last decade, the College has developed a strong computersupport structure for specific curricula, basically through the use oflarge minicomputers. Our needs for the 1990's include the following.

- Continuing support for existing curricula

- Increasing the availability of computing to larger numbers ofstudents and faculty who will be doing more diverse applications

- Better serving courses that have special hardware needs, such asComputer Aided Design

- Promoting greater communication among students and faculty withinour own academic community and between other academic communities

- Sharing and managing our computing resources flexibly andeffectively

- Reducing our dependence on a single vendor for hardware and software

- Providing easier access to industry standard tools to support ourvocational training curricula

5.2.2 SolutionsMeeting these needs for the 1990's will require the following.

- Support of a large computer system environment, comparable to one ofthe Prime computer systems currently available

- Increased access to microcomputers for general student use and forboth general, and more complex, faculty applications

- Development of special departmental computing environments forparticular academic constituencies, such as Computer Aided Design



and Engineering Graphics, that support current industry standardsoftware packages

- Connection of these different computing environments to thecampus-wide network

- Accessibility of all major computing resources from any part of theacademic computing environment

- Usage monitoring of all major computing resources of the academiccomputing environment

- Preference for industry standard software that is available onmultiple vendors' hardware platforms

5.2.3 Components

Transitioning parts of our academic community from a centralizedminicomputer to a more diverse and distributed networked environmentcannot realistically be accomplished in a single acquisition, norprobably in a single year. We must do a significant amount ofsoftware conversion and must change the orientation of both studentsand faculty with substantial training. We must also engage ininstitutional learning about what different hardware, software, and

network facilities can, and cannot, do.

In order to provide for this institutional adjustment we anticipatethree components or dimensions in the acquisition of this new academicinformation services environment. Each component will have differenthardware, software, and transition concerns.

FIRST - The first component will address our microcomputinginfrastructure. We will be interested in acquiring a variety of low,medium, and high level microcomputing systems. Some of these systemswill be connected into departmental networked micro or mini computerenvironments. During this first component, the College will begin toconvert some minicomputer applications to one of these other

environments and will focus both students and faculty onmicrocomputers as the basic resource for individual initiativecomputing.

SECOND - The second component will address the networking of thismicrocomputer infrastructure with itself, and with all other computingresources at the College. Any microcomputer user, with appropriatesecurity access rights, should be able to connect to, and log into,any College computing resource. The network should support thesharing of peripheral devices, such as laser printers. Network accessby students and faculty from their homes is very important.

As discussed in Section 3.2, we do not expect to develop amicrocomputer local area network operating system across multiple fileservers using our campus-wide Ethernet backbone.

THIRD - The third component will address our mini, super-mini, ormainframe computing needs. The availability of the first twocomponents will allow some academic applications to migrate from thecurrent minicomputer environment to a new departmental networked microor mini computer environment. At that time our academic computingneeds for a larger computer system will be more clearly defined. We



fully expect to continue to require computing of this order to supportsome amount of instructional computing.

5.3 First Component: Microcomputers

5.3.1 General

This component of the RFP addresses the continued development of amicrocomputer infrastructure. Microcomputers are seen as appropriateto support "low intensity" computing, such as word processing, becausethey are relatively inexpensive, are stand-alone, are highly mobileand offer a broad selection of software. More powerful microcomputersystems will be needed to support special Computer Aided Design andEngineering Graphics environments. These systems allow a broadselection of software and offer more fault tolerant laboratorysettings.

Microcomputer systems are so diverse that it is important to bespecific about what levels of performance are required withoutconstant reference to particular pieces of equipment. The followingterms will be used in describing our performance expectations. Theterms are defined in reference to MS-DOS systems because this is ourcurrent campus microcomputing environment and makes a convenientreference. This does not mean however, that only these types of

microcomputers are acceptable.

The following basic information provides more detail regarding thelow, average, and high level of microcomputing systems the Collegerequires. Vendors should propose systems to approximate as closely aspossible, these performance levels. Vendors should propose a range ofprinters, from dot-matrix to laser technology, from which the Collegecan select when developing this microcomputer infrastructure.

LOW LEVEL - These systems will be used to support basicmicrocomputing applications, such as word processing, and should be atleast comparable to an Intel 8088, 8 MHz clock, 640K memory system. Inthis classification, video resolution should be at minimum, the VGA

level, 640x480 pixel.

MEDIUM LEVEL - These systems will be used to support morecomputationally intensive processing, such as computer languageprogramming, and should be at minimum, comparable to an Intel 286, 12MHz clock, 1 MB memory system with extended memory support. In thisclassification, the availability of floating point coprocessors andvideo resolution above the standard VGA level are important options.

HIGH LEVEL - These systems will be used to support verycomputationally intensive processing, such as three-dimensionalComputer Aided Design or symbolic manipulation of mathematical

entities. These systems should be at minimum, comparable to an Intel386, 25 MHz clock, 2 MB memory system with extended memory support. Aswith medium level systems, the availability of floating pointcoprocessors and video resolution above the standard VGA level areimportant options. Operating system software to support the use ofthis classification of microprocessors as a microcomputer file serveror computer host of a small, 10 to 30 workstation, classroom orlaboratory network is also an important option. Vendors shouldreference Section 2.3 for a description of departmental computingenvironments.



In addition, all microcomputer systems must have a clock to supportusage monitoring which maintains the date and time when the system ispowered off. A serial port is required so that these microcomputersystems can be used as terminals on some other specific computingsystem, as nodes connected to a departmental network, or as nodesconnected to the campus-wide network.

Vendors should provide information regarding the maintenance ofproposed microcomputers. This includes at least two options. Thefirst option includes the cost for vendor provided maintenance supportand a description of how this would be accomplished. The second optionincludes the cost for spare parts and training if the College were tocontinue to provide maintenance support on our own or by becoming anauthorized repair center for a vendor's products.

The four specific user environments that will be addressed in thefirst component include the following.

- General Student Access to Microcomputing- Faculty Access to Microcomputing- Computer Aided Design Classroom and Laboratory Computing- Engineering Graphics Computing

5.3.2 General Student Access to Microcomputing

Students, regardless of their course of study, need to have access tolow level microcomputing facilities to support paper preparation withword processing, analytical work with spreadsheeting, and courseenrichment with provided instructional software. This microcomputingresource needs to be available to the general student population on a24 hours per day, 7 days per week basis. Since this microcomputingresource must be public access, the use and management of hard disksystems is not realistic.

Microcomputers will begin to replace terminals currently available onour academic computing systems. A student workstation would then be

multi-functional and would be capable of acting as either astand-alone microcomputer, or as a terminal connected to a largercomputing system.

Vendors should describe their involvement with providing access tocomputing for disabled persons. The continued development ofcomputing access for our disabled student population is very importantto the College.

5.3.2.1 Hardware

The College expects to acquire in the range of 10 to 40 low levelmicrocomputer systems with dual floppy disk drives and monochrome

monitors in this student access environment.

5.3.2.2 Software

The College expects to provide inexperienced users with simple andinexpensive access to basic microcomputer applications. Softwareneeded in this environment includes an entry level word processor andspreadsheet, an easy to use file transfer product, a standard terminalemulator, and a user interface support shell to the operating system.



5.3.2.3 Transition

This environment represents the formal introduction of a new level ofservice to our student population. The College will need to developan ongoing process to train students in the use of thesemicrocomputing systems. Vendors should include any training supportmaterials appropriate to this level of microcomputing. Thesematerials may include CDROM or videotape presentations, explanatory ortutorial software, or trouble shooting manuals or texts.

5.3.3 Faculty Access to Microcomputing

The College has approximately 250 faculty in about 140 office spaces.We currently have about 50 faculty offices populated withmicrocomputer systems. Faculty require microcomputer support for thedevelopment of instructional materials, for the processing of routineclerical work, for electronic communication with both on-campus andoff-campus user communities, and for the integration and use ofinstructional software. The College will continue to support thistype of work by providing microcomputer systems for faculty. Since afaculty office typically represents a small group of users and is notpublicly accessible, the use and management of hard disk systems isrealistic and expected.

5.3.3.1 Hardware

The College expects to acquire in the range of 10 to 40 low levelmicrocomputer systems with single floppy and hard disk drives,monochrome monitors and printers in this faculty access environment.We expect in succeeding years to continue to provide this type ofmicrocomputer system to all interested faculty.

The College expects to acquire some smaller number, from 1 to 10, highlevel microcomputer systems for special faculty initiatives andprojects. For example, a Mathematics faculty investigating the use ofsymbolic manipulation software, such as MAPLE and MATHEMATICA, in

Calculus courses, will need access to a high level microcomputersystem.

5.3.3.2 Software

The College expects to provide faculty with basic microcomputerapplications including a word processor, a spreadsheet, a databasemanagement system, a file transfer product, a standard terminalemulator, and a user interface support shell to the operating system.

5.3.3.3 Transition

This environment represents the continued development of faculty

access to microcomputing. The College will need to develop an ongoingprocess to train faculty in the use of these microcomputer systems.Most of this training will be done on campus by staff and faculty.Vendors should include any training and usage support materialsappropriate to these levels of microcomputing. Materials may includeCDROM or videotape presentations, explanatory or tutorial software, ortrouble shooting manuals or texts. 5.3.4 Computer Aided Design Classroom and Laboratory Computing



The learning of Computer Aided Design requires a classroom andlaboratory environment in which students receive instruction, andafter instruction, have the opportunity for practice. This type oflaboratory currently exists in our Technologies Division with one labof terminals supporting instruction using ANVIL 4000 on our Primecomputer system and another lab of microcomputers supportinginstruction using AUTOCAD on stand-alone microcomputers.

The College expects to support this type of instruction with a networkof microcomputer workstations which will allow the sharing of filesbetween students and faculty and the sharing of output devices, suchas plotters and printers. Vendors should propose the hardware andsoftware components to create these departmental networked micro ormini computer systems and the hardware and software components toconnect these systems to the campus-wide network. Vendors shouldreference Section 2.3 for a description of departmental computingenvironments.

The College will first undertake the Computer Aided Design transitionfrom our current Prime computer system to a departmental system andthen will implement the connection of these environments to thecampus-wide network.

5.3.4.1 Hardware

The College expects to develop two Computer Aided Design classrooms orlaboratories each equipped with a departmental networked micro or minicomputer host; 15 microcomputer workstations; several facultymicrocomputer workstations; the appropriate departmental computer hosthardware for connection to the campus-wide network; and theappropriate departmental computer host and microcomputer workstationhardware for connection to a departmental network. Thesemicrocomputer systems should be in the high level category with largememory configurations, substantial hard disk capacity, and numericcoprocessors. Large 19 inch high resolution color monitors areimportant options.

5.3.4.2 Software

The College expects to support these laboratories with softwareapplications including, but not limited to, P-SPICE, ANVIL 5000 V.2,AUTOCAD V.10, ANSYS/PC, FRAME-3D, TIMELINE, and AEC modeling systemsor their equivalents. Network facilities will be needed for uploadingand downloading software and work files to and from the departmentalcomputer host, for monitoring of equipment usage, and for sharing ofoutput devices.

5.3.4.3 Transition

This environment represents a significant change in the delivery ofinstruction in the Technologies Division. The training of faculty touse the network facilities and the application software is veryimportant. Vendors should include any training support materialsappropriate to this computing environment.

5.3.5 Engineering Graphics Computing

The Engineering Science curriculum requires an environment for theinstruction of FORTRAN programming and for the use of Graphics



Libraries to accomplish elementary graphics applications. Theadvanced course makes use of a three-dimensional Computer Aided Designduring part of the semester. Currently, this instruction issupported on the Prime computer system with the Tektronics IGL PLOT 10library, a FORTRAN 77 compiler, and Tektronics 4014 graphicsemulation.

The College expects to support this type of instruction with a networkof microcomputer workstations which will allow the sharing of filesbetween students and faculty and the sharing of output devices, suchas plotters and printers. Engineering Science students need openaccess to the microcomputer systems for doing programming exercises,but do not require a dedicated laboratory environment.

These microcomputer systems will not be located in a single room orbuilding. They will be located in a number of student open accessareas with connectivity provided to the departmental networked microor mini computer system through our campus-wide network. The majoractivity of these systems will be computer program development, thatis, editing, compiling, executing and debugging.

Since this microcomputing resource must be public access, the use andmanagement of hard disk systems is not realistic. Vendors shouldpropose the hardware and software components to create this

departmental networked micro or mini computer system and the hardwareand software components to connect this system to the campus-widenetwork. Vendors should reference Section 2.3 for a description ofdepartmental computing environments.

The College will first undertake the Engineering Graphics transitionfrom our current Prime computer system to a departmental system andthen will implement the connection of this environment to thecampus-wide network.

5.3.5.1 Hardware

The College expects to develop one Engineering Graphics open access

network equipped with a departmental networked micro or mini computerhost; 15 microcomputer workstations; several faculty microcomputerworkstations; the appropriate departmental computer host hardware forconnection to the campus-wide network; and the appropriate departmentalcomputer host and microcomputer workstation hardware for connection toa departmental network. These microcomputer systems should be in thehigh level category with at minimum 3 MBs of memory and numericcoprocessors. Large 19 inch color monitors supporting videoresolution in the 1000x800 pixel range are required on at least 3 ofthe 15 workstations. Standard VGA level color monitors should beincluded on the remaining workstations. All 15 microcomputerworkstations will require dual floppy, high density disk drives, andnot hard disk drives.

5.3.5.2 Software

The College expects to support these laboratories with softwareapplications including, but not limited to, a text editor, a FORTRAN77 compiler, and a graphics library of standard graphics subroutinescapable of supporting all proposed color monitors.

Two options are available for student use of the software. One is toprovide a copy of the software to each student on a high density



floppy. The other approach is to have a single copy of the softwareon the hard disk of the departmental networked micro or mini computerhost and provide access through the departmental or campus-widenetwork. Vendors should propose the software option they believe willmost simply and cost-effectively support this computing environment.

Network facilities will be needed for uploading and downloadingsoftware and work files to and from the departmental computer host,for monitoring of equipment usage, for sharing of output devices, andfor maintaining private disk directories. Application softwarecapable of supporting three-dimensional Computer Aided Design will beneeded. Since the student nodes of this network will not have harddisks, this software must be able to load from or operate from thedepartmental computer host.

5.3.5.3 Transition

This environment represents a significant change in the delivery ofinstruction in Engineering Science. The training of faculty to usethe network facilities and the application software is very important.Most of the current applications are written using Tektronics IGL PLOT10 library calls. Vendor support for converting such applications tothe call format of the proposed graphics library would be very

helpful. Vendors should include any training support materialsappropriate to this computing environment.

5.3.6 Summary of First Component: Microcomputers

In summary, the first component of the academic section of this RFPincludes the need to establish, or continue development of, thefollowing four different computing environments.

- General Student Access to Microcomputing- Faculty Access to Microcomputing- Computer Aided Design Classroom and Laboratory Computing- Engineering Graphics Computing

The College expects to acquire different microcomputer hardware andsoftware platforms for the different computing environments.Departmental networked micro or mini computer systems are seen as themost straightforward computing environments to service our needs inComputer Aided Design and Engineering Graphics. The microcomputer andcomputer systems in each of these four environments must have thecapacity to connect to our developing campus-wide network.

5.4 Second Component: Networking

The diverse and distributed computing environments described in thefirst component are effective at providing for special needs and are

cost-effective in supporting general student and faculty computing.However, as disconnected computing environments, they are not a meansof facilitating communication, cannot share important resources, andcannot be effectively administered on the basis of utilization.

The second component of our new academic information servicesenvironment, connection to the campus-wide network, will provide forfacilitating communications, sharing resources, and monitoring usage.All academic computing systems will be able to communicate with each



other, with all other College computing systems, and with other remotecomputing systems.

All institutional information services described in Section 4 must bemade available to the academic community at the latest during thissecond component. Dial up communication capabilities to the networkfor access to College computing systems and from the network foraccess to remote computing systems is very important to the College.With a large student population using microcomputers for basicapplications, such as word processing, the sharing of high qualityprinters through the network will become essential to support theprinting requirements students will have when composing researchpapers or reports.

The time on task is an important component of the evaluation andadvisement of students. The network should provide support forfaculty to assess how often and to what extent their students areusing the College's computing facilities.

5.5 Third Component: Minicomputer

The student and faculty microcomputer infrastructure developed in thefirst component and connected by the networking accomplished in thesecond component will remove some of the academic computing workload

from the current minicomputer. However, the College will stillrequire a mini, super-mini, or mainframe computer system for thedelivery of instruction in areas such as computer programming and jobcontrol language.

5.5.1 Hardware

The hardware component(s) of this computer system must supportconnection to a campus-wide Ethernet backbone and use of TCP/IP as aterminal protocol. Vendors should describe a computer hardware systemcomparable to the Prime System B described in Section 2.

5.5.2 Software

The College will require software to support this environmentincluding, but not limited to, EMACS; compilers for FORTRAN 77, COBOL74, PASCAL, C, and RPG; an assembler language; program debuggingtools; and a SQL database system. IBM JCL, or an IBM JCL emulator, isalso required to support student instruction in our ComputerInformation Systems curriculum.

The ability to easily customize computing environments is required ininstructional computing. The mini, super-mini, or mainframe computeroperating system needs to allow for easy customization of the userinterface with symbolic abbreviations and command files to adapt to

the needs of a class or individual user. Software facilities forcommunicating among students and faculty, both directly, usingmessages or mail and indirectly, using techniques such as thecapturing of student terminal input and output in a file to facilitatedebugging, are needed in this instructional environment.

The security system is critical and must be able to resist determinedand persistent probing. Security must be strong enough to distinctlyseparate student files from each other, yet be flexible enough toallow faculty access to their own students' files.



5.5.3 Transition

The College will require support for the conversion of currentapplications and the training of faculty. The conversion ofinstructional software currently in use on the Prime computer systemwill represent a major effort for faculty whose curricula require alarge computer system platform. Vendors should describe their abilityto assist in converting PASCAL, BASIC, COBOL 74, FORTRAN IV, FORTRAN77, and C computer programs. The training, or retraining, of facultyand system support personnel is very important. Vendors shoulddescribe their ability to provide this training on our campus.

Section 6 - Administrative Information Services

6.1 Hardware

The hardware component(s) of the computer system which will be usedfor providing Administrative information services must supportconnection to a campus-wide Ethernet backbone and use of TCP/IP as aterminal protocol.

The computer system hardware being proposed by vendors should includeor support the following characteristics and capabilities.

- Support the processing requirements of an institution with at leastone and one-half times the total student population of our Collegeand with a comparable processing environment to our College

- Support at least 500 on-line transaction processing users of,in addition to the normal batch processing requirements of, theproposed Student Information and Campus Administrative System

- Support dial-up access from remote locations through the campus-wideEthernet network

- Include a disk subsystem with at least one and one-half times thestorage capacity required for a minimum retention of six years ofhistorical data and for the anticipated on-line and batchrequirements of the proposed Student Information and CampusAdministrative System

- Include a disk subsystem with sufficient redundancy to support andallow for continued operation of the proposed Student Informationand Campus Administrative System in the event of single disk drivefailure

- Include a tape subsystem capable of supporting both 1600 and 6250BPI tape formats and a tape cartridge option for the tape subsystem

- Include both impact and laser printers with sufficient capacitiesfor the anticipated printing requirements of the proposed StudentInformation and Campus Administrative System

6.2 SOFTWARE

6.2.1 Student Information and Campus Administrative System



The College's current Student Information and Campus AdministrativeSystem has been user written and developed in-house to operate on aUnisys A10H computer system. This development has occurred utilizingUnisys proprietary software for communications and data basemanagement, the Communications Management System (COMS) and DataManagement System II (DMSII) respectively. All application programshave been written in COBOL74 without the use of any source codegenerating software or 4th generation languages.

The maintenance of current programs and development of newapplications are very labor intensive functions. Due to thesemaintenance and new development demands, we are not always able todevote adequate resources to enhance current software systems toprovide better support for the changing needs of our users and toimprove operational efficiencies.

The modular development over a period of time of the College's currentStudent Information and Campus Administrative System has created manycomplex relationships between data elements. These complexrelationships, and the capabilities of our current inquiry and ad-hocreporting tool, create an environment where our users have greatdifficulty in supporting their own unique and dynamic informationneeds.

The College's current database implementation does not utilizerelational database technology nor does it provide an industrystandard SQL-based user interface for inquiry and ad-hoc reporting. Avendor supplied and maintained Student Information and CampusAdministrative System utilizing current relational database technologyand providing a SQL-based user interface may provide the College witha solution to these problems.

Vendors should propose a Student Information and Campus AdministrativeSystem which includes, but is not limited to, support for thefollowing application areas.

Accounts PayableAdmissionsAlumni/DevelopmentBudgetContinuing EducationCounty ChargebackDegree AuditEnrollment Management Services

(including prospect development and persistence tracking)

Exam SchedulingExtra Curricular Activities

Facilities Management(including facilities maintenance and utilities management)

Financial Aid(including analysis and disbursement)

General LedgerGrade ReportingHuman Resources/PersonnelInstitutional ResearchInventory Management

(including barcode technology)



Library AutomationMailing List ProcessingMaster Class ScheduleMaster Course CatalogPayrollPublic SafetyPurchasingRoom SchedulingStudent Accounts ReceivableStudent AdvisementStudent BillingStudent Class SchedulingStudent Health InsuranceStudent Health Reports/ImmunizationStudent Job Placement and TrackingStudent RegistrationStudent Transcript

The Student Information and Campus Administrative System beingproposed by vendors should include or support the followingcharacteristics and capabilities.

- Be highly integrated and flexible

- Be accessible to all users with appropriate security controls

- Interface with office automation facilities

- Include the use of industry standard software applications and tools

- Support at least 500 on-line transaction processing users

- Allow for student use of an on-line telephone registration system

- Support continuous, 24 hours per day and 7 days per week, on-lineinquiry and update processing

- Support database tape backup while on-line inquiry and updateprocessing is in progress

- Support complete transaction and database synchronized recovery inthe event of hardware or software failure

- Support the logging of all on-line update transactions including thedate, time and user identification of the transaction initiator

- Include complete vendor software support

- Comply with the "Code of Standards and Procedures for the

Administration and Operation of Community College under the Programof State University of New York State"

- Support sub-second transaction response time

- Include source code for each proposed software component

The vendor's response and proposal of a Student Information and CampusAdministrative System must include the following.



- A cross-reference report, indicating which module of the proposedsystem, supports each of the application areas listed previously

- A complete data element dictionary for each of the modules of theproposed system

- Sufficient documentation for each of the modules of the proposedsystem to allow the College to evaluate the proposed solution withrespect to our current system features and future needs

6.2.2 Operating System and System Software

The Operating and System software being proposed by vendors shouldinclude or support the following characteristics and capabilities.

- Include system resource management tools

- Support the detection, logging, and diagnosis of hardware, software,and/or security faults or problems

- Support the logging of all jobs and programs run including the date,the time, the user identification of the job or program initiator,the files accessed, the system resources used (processor,

input-output, memory), the termination status, and other datanecessary for appropriate system accounting and management

- Support the on-line and batch analysis of system log files

- Support usage of the system from remote locations by dial-up accessthrough the campus-wide Ethernet network

6.3 TransitionVendors should propose a plan for transition from our currentadministrative environment to their proposed Student Information andCampus Administrative System hardware and software environment. This

plan should include, but not be limited to, site preparation, hardwareand software installation, data conversion, training, andimplementation support. The training of our system support anddepartmental user personnel is especially important to the College.

Section 7 - Summary of Information Services

7.1 Summary

The College is evolving from an environment where computing servicesare provided by separate and distinct centralized computing resourcesto an environment where information services are provided by bothcentralized and decentralized computing resources. Personal level

information services will be provided to individuals by stand-alonemicrocomputing systems. Departmental level information services willbe provided to small groups of individuals by networked micro or minicomputer systems. Institutional level information services will beprovided to large segments of the campus population by mini,super-mini or mainframe computing systems.

These three levels of computing resources provide differentinformation services. Our users must be able to easily access thecomputing resource(s) required to obtain the information service(s)



needed to perform their jobs. For most of our users this will requireaccess to more than one of these three levels of computing resources.For many of our users this will require access to multiple computingresources within a particular level.

For example, a faculty advisor in our Engineering Science Departmentwould likely need access to all three levels of computing resourcesfor obtaining at minimum the following information services.

Personal - For the creation of course instructional materials andstudent handouts using stand-alone applications on a microcomputer

Departmental - For the development and testing of course assignmentsusing the library of graphic subroutines on a departmental networkedmicro or mini computer system

Institutional - For communicating with students using thecampus-wide electronic mail facility on a particular computing host;for communicating with faculty at some other institution using thecampus-wide electronic mail facility for access to BITNET on thesame computing host; or for advising students using the StudentInformation and Campus Administrative System on the same, or someother, computing host

The development of a campus-wide network, allowing for user access toany of our departmental or institutional computing resources andallowing for user access to remote computing facilities, is ofcritical importance to the delivery of the information servicesdescribed in this RFP. A user, by a single connection of his/herworkstation to this campus-wide network, should have access to theinformation services needed to perform his/her jobs.

Vendors should not perceive our distinction between network,institutional, academic, and administrative information services as adesire for them to propose four distinct computing environments.Vendors should propose solutions which simply and cost-effectively

address our information service needs. A vendor's solution(s) mayinclude one, or many computing environments.

Vendors should propose industry standard hardware and softwarearchitectures for both the communications and computing resourcesneeded in our development of this information services environment.The College is keenly aware of the importance of planning for thistransition in the four information services areas we have described.We are very interested in all aspects of the transition plans whichvendors will propose. We view this transition process as one whichwill become more clearly defined for the College as vendorrecommendations and plans are reviewed.

The campus-wide network pilot project will begin within a few monthsand will result in the installation of a broadband Ethernet supportingIEEE 802.3 standards and the use of TCP/IP as a standard terminalprotocol. Vendors should include hardware and software components forall proposed computing systems, terminal servers for all proposedterminals and microcomputer bridges for all proposed microcomputerfile servers to provide for connectivity to a network compatible withthese standards. Vendors should also include any necessary hardwareor software components for connection of our current population ofmicrocomputers to this network.



In our new information services environment, the critical element inproviding services to the College will become the campus-wide network.Vendors should include hardware and software components for managingthe network and should clearly describe how these components willallow the College to effectively maintain and secure this resource.

The development of institutional information services will greatlybenefit the flow of information throughout our entire campuscommunity. For example, students, faculty, and staff should haveaccess to a common Office Automation System for both intra-campusand inter-campus electronic mail and data sharing. Students, faculty,and staff should have access to a Library Information System for bothacademic and administrative research. We understand that for some ofthe services defined in this section we are describing a direction andmay not be able to implement a complete solution at this time. Vendorsare requested to respond wherever possible with complete solutions.When a complete solution is not possible vendors are requested torespond with a partial or directional solution which defines for theCollege the stages of implementation required to reach our servicegoal.

The academic and administrative information services sections describe

complex, and changing, computing environments. The notion ofcentralized computing resources being able to support all of the needsof academic and administrative computing is no longer appropriate. TheCollege has already undergone significant transitioning to morediverse and distributed environments with the tremendous integrationof microcomputing into many academic curricula and into virtually allacademic and administrative departments. However, the perspectivespresented in the academic and administrative information servicessections are clearly different.

The following situations are examples to help vendors understand thesedifferent perspectives, are not universally applicable to allacademic, and administrative departments and may in fact, not be

applicable to these specific departments.

In providing academic services we describe an environment where bothinstructional, and instructional support, computing is decentralized.For example, a Mechanical Engineering Technology faculty would teachComputer Aided Design using an application on a departmental networkedmicro or mini computer system and would create course materials usingstand-alone applications on his/her microcomputer.

In providing administrative services we describe an environment whereadministrative computing is centralized and administrative supportcomputing is decentralized. For example, an Admissions counselorwould process student applications using the Student Information and

Campus Administrative System on an institutional computing resourceand would analyze downloaded data using a stand-alone spreadsheetapplication on his/her microcomputer.

We do not expect to departmentalize administrative computing in thesame way that we do expect to departmentalize academic computing.

In the academic information services section, the continued growth ofmicrocomputing, the development of departmental computingenvironments, and the connection to and use of the campus-wide network



for instruction, and instructional support, are the first stagesdescribed. As we more clearly understand the impact of theintegration and use of these environments, we will be better able todefine our need for a mini, super-mini, or mainframe computer systemto support instructional computing.

In the administrative information services section, the capabilitiesof the proposed Student Information and Campus Administrative Systemand the benefits to the College of using this product should beclearly described. Our current administrative solution does notprovide users with the tools they need to access institutional dataand to create their own unique, and dynamic, information. The abilityof our users to create their own information using institutional datahas become very important in the daily performance of their jobs andin the effective management of our College.

7.2 Implementation Plan

The development of a final implementation plan for the informationservices described in this RFP will be affected by many factors. Weexpect this final implementation plan to be more clearly defined afterwe have analyzed vendor responses to this RFP and have made decisionson what products will provide what information services for the

College. We expect active participation from selected vendors in theprocess of developing a final, more detailed implementation plan.

The following preliminary implementation plan is an attempt to extractthe major components from each of the information services areas, toprioritize these components based on their importance to the College,and to schedule these components based on the availability of Collegepersonnel to support the implementation.

Vendors should understand that information services not extracted asmajor components for this preliminary implementation plan will becomepart of our final implementation plan; that all information services

described in this RFP are important to the College; and that thescheduling of major components based on the availability of Collegepersonnel does not preclude the option of vendor personnel support toimprove the timeframe for implementation of information services.

January 1991 - August 1991

Network Install network management systemAcademic Install student open access microcomputers

Install faculty access microcomputersInstall first computer aided design systemInstall engineering science system

September 1991 - August 1992

Institutional Install office automation systemInstall bulletin board system

Academic Install second computer aided design systemAdministrative Install student information and campus

administrative system and user supporttools



September 1992 - August 1993

Network Install network components to attach remainingdevices directly to campus-wide Ethernet

Institutional Install library information systemAcademic Install large computer system

Appendix A - General Municipal Law

S. 103-a. Ground for cancellation of contract bymunicipal corporations and fire districts.

A clause shall be inserted in all specifications or contracts made orawarded by a municipal corporation or any public department, agency orofficial thereof on or after the first day of July, nineteen hundredfifty-nine or by a district or any agency or official thereof on orafter the first day of September, nineteen hundred sixty, for work orservices performed or to be performed, or goods sold or to be sold, toprovide that upon the refusal of a person, when called before a grandjury to testify concerning any transaction or contract had with the

state, and any political subdivision thereof, a public authority orwith any public department, agency or official of the state or of anypolitical subdivision thereof or a public authority, to sign a waiverof immunity against subsequent criminal prosecution or to answer anyrelevant question concerning such transaction or contract.

(a) Such person, and any firm, partnership or corporation ofwhich he is a member, partner, director or officer shall bedisqualified from thereafter selling to or submitting bids to orreceiving awards from or entering into any contracts with anymunicipal corporation or fire district, or any public departmentagency or official thereof, for goods, work or services, for aperiod of five years after such refusal, and to provide also

that

(b) any and all contracts made with any municipalcorporation or any public department, agency or official thereofon or after the first day of July, nineteen hundred fifty-nineor with any fire district or any agency or official thereof onor after the first day of September, nineteen hundred sixty,by such person, and by any firm, partnership or corporation ofwhich he is a member, partner, director or officer may becancelled or terminated by the municipal corporation or firedistrict without incurring any penalty or damages on account ofsuch cancellation or termination, but any monies owing by themunicipal corporation or fire district for goods delivered or

work done prior to the cancellation or termination shall bepaid.

The provisions of this section as in force and effect prior to thefirst day of September, nineteen hundred sixty, shall apply tospecifications or contracts made or awarded by a municipal corporationon or after the first day of July, nineteen hundred fifty-nine, butprior to the first day of September, nineteen hundred sixty.



S. 103-b. Disqualification to contract with municipalcorporations and fire districts.

Any person who, when called before a grand jury to testify concerningany transaction or contract had with the state, any politicalsubdivision thereof, a public authority, or with a public department,agency or official of the state or of any political subdivisionthereof or of a public authority, refuses to sign a waiver of immunityagainst subsequent criminal prosecution or to answer any relevantquestion concerning such transaction or contract, and any firm,partnership or corporation of which he is a member, partner, directoror officer shall be disqualified from thereafter selling to orsubmitting bids to or receiving awards from or entering into anycontracts with any municipal corporation or fire district, or with anypublic department, agency or official thereof, for goods, work orservices, for a period of five years after such refusal or until adisqualification shall be removed pursuant to the provisions ofsection one hundred three-c of this article.

It shall be the duty of the officer conducting the investigationbefore the grand jury before which the refusal occurs to send noticeof such refusal, together with the names of any firm, partnership orcorporation of which the person so refusing is known to be a member,partner, officer or director, to the superintendent of public works of

the State of New York, and the appropriate departments, agencies andofficials of the state, political subdivisions thereof or publicauthorities with whom the person so refusing and any firm, partnershipor corporation of which he is a member, partner, director or officer,is known to have a contract.

S. 103-c. Statement of non-collusion in contract withmunicipal corporations or fire districts.

Every contract hereafter made or awarded by a municipal corporation orany public department, agency or official thereof or by a firedistrict or any agency or official thereof, pursuant to bid, for work

or services following statement by the bidder, under penalty ofperjury: Non-collusive bidding certification. The bidder certifiesthat: (a) the bid has been arrived at the bidder independently andhas been submitted without collusion with any other vendor ofmaterials, supplies, or equipment of the type described in theinvitation for bids, and (b) the contents of the bid have not beencommunicated by the bidder, nor, to its best knowledge and belief, byany of its employees or agents, to any person not an employee or agentof the bidder or its surety on any bond furnished herewith prior tothe official opening of the bid.

S. 103-d. Statement of non-collusion in bids and proposals

topolitical subdivision of the state or fire district.

Every bid or proposal hereafter made to a political subdivision of the state orany public department, agency or official thereof or by a fire district or anyagency or official thereof, for work or services performed or to be performed orgoods sold or to be sold, shall contain the following statement subscribed by thebidder and affirmed by such bidder as true under the penalties of perjury:



Non-collusion bidding certification. By submission of this bid or proposal, thebidder certified that: (a) this bid or proposal has been independently arrivedatwithout collusion with any other bidder or with any competitor or potentialcompetitor; (b) this bid or proposal has not been knowingly disclosed and willnot be knowingly disclosed, prior to the opening of bids or proposals for thisproject, to any other bidder, competitor or potential competitor; (c) noattempt has been or will be made to induce any other person, partnership orcorporation to submit or not to submit a bid or proposal; (d) the personsigning this accuracy of the statements contained in this certification, andunder the penalties of perjury, affirms the truth thereof, such penalties beingapplicable to the bidder as well as to the person signing in its behalf; (e)that attached hereto (if a corporate bidder) is a certified copy of resolutionauthorizing the execution of this certificate by the signator of this bid orproposal in behalf of the corporate bidder.

IN THE CASE OF CORPORATE BIDDERS A RESOLUTION IN THE FOLLOWING FORM MUST ACCOMPANYTHE BIDS.

Resolved that.......................................................be(Name of Corporation)

authorized to sign and submit the bid or proposal of this corporationfor the following project...................................................................................................................

(Describe Project)

and to include with such bid or proposal the certificate as to non-collusionrequired by section one hundred three-d of the General Municipal Law as the actand deed of such corporation, and for any inaccuracies or misstatements in suchcertificate this corporate bidder shall be liable under the penalties of perjury.

The foregoing is a true and correct copy of the resolution adoptedby ....................................................... corporationat a meeting of its board of directors held on the ............... dayof ................ 19 .....

(SEAL OF CORPORATION)

I, the undersigned, do herby certify that: (a) this bid or proposal has beenindependently arrived at without collusion with any other bidder or with anycompetitor or potential competitor; (b) this bid or proposal has not been

knowingly disclosed and will not be knowingly disclosed, prior to the opening ofbids or proposals for this project, to any other bidder, competitor or potentialcompetitor; (c) no attempt has been or will be made to induce any other person, partnership, or corporation to submit or not to submit a bid or proposal; (d) theperson signing this bid or proposal certified that he has fully informed himself



regarding the accuracy of the statements contained in this certification, andunder the penalties of perjury, affirms the truth thereof, such penalties beingapplicable to the bidder as well as to the person signing in its behalf; (e) thatattached hereto (if a corporate bidder) is a certified copy of resolutionauthorizing the execution of this certificate by the signator of this bid orproposal in behalf of the corporate bidder.

________________________________________ Signature of Person

________________________________________ Name of Person

________________________________________ Title of Person

________________________________________ Date

Computer Information Services RFP and Cover Letter to Vendors (166163293)

Documents

Transcript of Computer Information Services RFP and Cover Letter to Vendors (166163293)