Get documents about "Information Technology San Francisco
Description
Information Technology San Francisco document sample
Document Sample
Information Technology Department
601 McAllister Street, 2nd Floor
San Francisco, CA 94102
San Francisco Unified School District
Information Technology Department
Request for Proposals
Francisco Middle School
Technology Infrastructure Upgrade
San Francisco Unified School District
Information Technology Department
601 McAllister Street, 2nd Floor
San Francisco, CA 94102
December 10, 2007
1
Table of Contents
1.0 Background ...................................................................................................4
1.1 Background and Overview................................................................................... 4
1.2 Purpose and Expectations ................................................................................. 4
2.0 Terms and Conditions of Competition........................................................4
2.1 Classification of RFP Requirements ............................................................. 4
2.1.1 Prerequisite Qualification........................................................................................... 4
2.1.2 Requirements............................................................................................................. 5
2.2 Limits of the RFP................................................................................................. 5
2.3 Proposal Requirements and Conditions............................................................ 5
2.3.1 General Information ................................................................................................... 5
2.3.2 Addendum to RFP ..................................................................................................... 6
2.3.3 Questions Regarding the RFP................................................................................... 6
2.3.4 Vendor’s Proprietary Questions................................................................................. 6
2.4 Vendors’ Conference ...................................................................................... 6
2.5 Submission of Proposals ............................................................................... 7
2.5.1 Preparation ................................................................................................................ 7
2.5.2 Vendor’s Costs........................................................................................................... 7
2.5.3 Completion of the RFP............................................................................................... 7
2.5.4 False and Misleading Statements........................................................................... 7
2.5.5 Delivery to District ...................................................................................................... 8
2.5.6 Withdrawal, Resubmission or Modification ................................................................ 8
3.0 General Contractual Requirements...........................................................8
3.1 General ............................................................................................................. 8
3.2 Contract Provisions ........................................................................................ 9
3.2.1 Type and Term of Contract........................................................................................ 9
3.2.2 Warranty ................................................................................................................... 9
4.0 Proposal Format ...........................................................................................9
4.1 General................................................................................................................ 9
4.1.1 Format of Requirements .......................................................................................... 10
4.1.2 Format of Responses to Requirements ................................................................... 10
4.2 Content and Sequence ................................................................................. 10
4.2.1 Proposal Identification Statement ............................................................................ 11
4.2.2 Response to Requirements ..................................................................................... 11
4.2.3 Supplementary Information...................................................................................... 11
5.0 Evaluation and Selection Process ........................................................12
5.1 General ........................................................................................................... 12
5.2 Evaluation Scoring........................................................................................ 12
5.3 Site Inspection............................................................................................... 13
5.4 Final Selection ............................................................................................... 13
5.5 Execution of Agreement ............................................................................... 14
6. 0 Projected Calendar of Events .................................................................14
6.1 District Contacts ............................................................................................... 14
7.0 District Responsibilities ............................................................................15
8.0 Prerequisite Qualifications.........................................................................15
9.0 Requirements ..............................................................................................17
10.0 Cost Response..........................................................................................20
Appendix A: Standard Contracts.....................................................................21
2
A1 Sample Contract........................................................................................... 21
A2 Performance Bond ....................................................................................... 22
A3 Payment Bond .............................................................................................. 24
3
1.0 Background
1.1 Background and Overview
The San Francisco Unified School District (SFUSD), founded in 1851, educates
approximately 55,000 of San Francisco’s pre-school, elementary, middle, and
high school students. SFUSD has 104 K-12 school sites, and 37 pre-school
sites.
The technology infrastructure at many SFUSD schools is outdated and
inadequate. The demand for technology at these sites, however, is increasing
rapidly. Sites require adequate technology to support hundreds of simultaneous
users, real-time access to data, streaming video, and interactive lessons.
Francisco Middle School requires a complete technology infrastructure upgrade,
including voice and data cabling and upgraded Local Area Network (LAN)
equipment.
1.2 Purpose and Expectations
The purpose of this Request for Proposals (RFP) is to solicit proposals to upgrade
the technology infrastructure at Francisco Middle School, including:
• Voice and data cabling materials and services in the school’s East and
West wing;
• Voice and data cabling materials and services in the school’s Annex
building;
• Purchase and delivery of Local Area Network hardware for the East wing,
West wing, and Annex building.
2.0 Terms and Conditions of Competition
2.1 Classification of RFP Requirements
The District has established two classes of requirements with respect to a
Proposal to be submitted by a prospective Vendor.
2.1.1 Prerequisite Qualification
Vendors must have a valid eRate Service Provider Invoice Number
(SPIN) and agree to the following terms and conditions:
(1) Purchase will be contingent upon SFUSD Board of Education
Approval, successful completion of the SFUSD contracting
procedures, and funding approval from the Schools and
Libraries Division (SLD).
(2) Vendor must agree to SLD’s Service Provider Invoicing (SPI)
format for reimbursement/payment.
4
(3) Vendor must guarantee that all fiber and copper cable
installation is done in compliance with applicable building
codes and by persons with the appropriate licensure.
(4) Vendor is responsible for providing all permits. Cost of such
permits must be included in Vendor’s proposal.
(5) Vendor must comply with prevailing wage regulations,
including adhering to the following requirements:
• Pay the prevailing wages applicable to the work being
done;
• Comply with all State laws in the payment and
administration of prevailing wages applicable to the work
being done;
• Submit certified payroll records;
• Keep documentation of fringe benefit payments, if any;
• Maintain a daily sign in sheet with the names and trades of
the employees, if any;
• Post or notify workers of the Prevailing Wage Rates at the
job site; and,
• Employ registered apprentices, if any.
2.1.2 Requirements
Requirements for vendor performance are defined in sections 8.0 and
9.0. Each proposal meeting the Prerequisite Qualifications will be
evaluated in its entirety according to the evaluation criteria defined in
section 5.0.
2.2 Limits of the RFP
The San Francisco Unified School District (SFUSD) reserves the right to reject all
proposals and will determine what further action, if any, will be taken.
2.3 Proposal Requirements and Conditions
2.3.1 General Information
Issuance of this RFP, the evaluation of responses, and the award of any
resultant Agreement shall be made in conformance with current
competitive bidding procedures as they relate to the procurement of
goods and services by the District.
In addition to identifying the District's needs, this RFP includes
instructions, which prescribe the format and content of a Proposal to be
submitted and the description of the Agreement to be executed
between the District and the Selected Vendor.
5
2.3.2 Addendum to RFP
The District may modify this RFP by issuance of one or more written
addendum. Any such addendum will be sent to all vendors on the
district’s Vendor List.
2.3.3 Questions Regarding the RFP
A Vendor requiring clarification of the intent or content of this RFP or on
procedural matters regarding the Proposal process may request
clarification by submitting questions electronically marked "Questions
on RFP " to Mr. Sean Rozell, IT Infrastructure Director. Questions
about specific topics or statements in this RFP must include the RFP
document page number(s). Questions must be received by the
Deadline for questions specified in Section 6.0, Projected Calendar of
Events. Question and answer sets will be discussed at the Vendor
Conference and subsequently posted on the SFUSD web.
2.3.4 Vendor’s Proprietary Questions
A Vendor who desires clarification or further information on the content
of this RFP, but whose questions relate to the proprietary aspect of the
Vendor's Proposal and which, if disclosed to other bidders, would
expose the Vendor's Proposal, may submit such questions in an
envelope clearly marked "Confidential Questions on RFP" to Mr.
Sean Rozell not later than the Deadline for questions specified in
Section 6.0, Projected Calendar of Events. The Vendor must explain
why the questions are sensitive in nature.
If the District concurs that the disclosure of the question or answer
would expose the proprietary nature of the Proposal, the question will
be answered and both the question and answer will be kept in
confidence. If the District does not concur with the proprietary aspect of
a question, the question will not be answered and the Vendor so
notified. The Vendor may then re-phrase and re-submit the question, if
desired, but only if such question is re-submitted within the time period
Deadline for questions specified in Section 6.0, Projected Calendar of
Events.
2.4 Vendors’ Conference
A Vendor conference will be held, during which a Vendor will be afforded the
opportunity to meet with District personnel and discuss the content of this RFP in
further detail.
The Vendor’s Conference will be held on the day and time specified in Section
6.0, Projected Calendar of Events at the location list below:
San Francisco Unified School District
601 McAllister Street
San Francisco, California 94102
Written questions received on or before the Deadline for questions specified in
Section 6.0, Projected Calendar of Events, will be answered at the conference
6
without divulging the source of the query. The District may also accept oral
questions during the conference and will make a reasonable attempt to provide
answers prior to the conclusion of the conference.
If changes to this RFP are deemed necessary following the Vendors'
Conference, an RFP addendum will be sent to all vendors on the Vendor List.
Questions asked at the conference that cannot be adequately answered during
the conference will be addressed with an RFP addendum. Each Vendor is
cautioned that no questions regarding the content of this RFP will be answered
following the conclusion of the conference.
2.5 Submission of Proposals
One (1) original, five (5) copies and (1) CD soft copy of a Vendor’s Proposal,
including all accompanying documentation and related material, must be
received in the Purchasing Department of San Francisco Unified School District,
135 Van Ness Avenue, San Francisco, California 94102, by the Proposal
Submission Deadline specified in Section 6.0, Projected Calendar of Events. A
Proposal must be submitted under sealed cover bearing on the outside
of the envelope, the name and address of the Vendor and indicating
"Confidential Proposal in Response to Francisco MS IT Upgrade RFP". One
copy of the Proposal must be clearly marked "Original Copy".
2.5.1 Preparation
A Proposal should be prepared in such a way as to provide a
straightforward, concise description of Vendor capabilities to satisfy the
requirements of this RFP. Emphasis should be concentrated on
conformance to the RFP instructions, responsiveness to the RFP
requirements, and on completeness and clarity of content.
2.5.2 Vendor’s Costs
All costs incurred in the preparation or submission of a Proposal shall
be entirely the responsibility of the Vendor and shall not be chargeable
either directly or indirectly to the District.
2.5.3 Completion of the RFP
A Vendor’s Proposal shall be completed in all respects as described in
Section 4.0, Proposal Format. A Proposal may be rejected if it is
conditional or incomplete, or if it contains any alterations of form or
other irregularities of any kind. The Proposal may be rejected if any
such defect or irregularity changes the prices submitted.
2.5.4 False and Misleading Statements
A Proposal which contain false or misleading statements, or which
provide references which do not support an attribute or condition
contended by the Vendor, may be rejected. If, in the opinion of the
District, such information was intended to mislead the District in its
evaluation of the Proposal and the attribute, which is a condition or
capability of a requirement of this RFP, the Proposal shall be rejected.
7
2.5.5 Delivery to District
A written Proposal must be received by the Purchasing Department, no
later than the Proposal Submission Deadline specified in Section 6.0,
Projected Calendar of Events. No telegraphic, facsimile, or telephone
Proposal will be accepted. If mailed, the Vendor should use certified or
registered mail, UPS, Federal Express or other carrier with return
receipt requested. The District assumes no responsibility for late
delivery, for any reason whatsoever, including but not limited to weather
or traffic conditions, illness, accident, delivery to wrong location, courier
problems, etc.
All copies of the Proposal must be under sealed cover, plainly
marked "Confidential Proposal In Response to Francisco MS IT
Upgrade RFP ".
A Proposal submitted under improperly marked covers might be
rejected. If discrepancies between two or more copies of the Proposal
are found, the Proposal may be rejected. If, however, the Proposal is
not rejected, the master copy will provide the basis for resolving such
discrepancies.
2.5.6 Withdrawal, Resubmission or Modification
A Vendor may withdraw the Vendor's final Proposal at any time prior to
the Proposal Submission Deadline specified in Section 6.0, Projected
Calendar of Events, by submitting a written request for its withdrawal to
Purchasing Department, signed by the Vendor or authorized agent.
The Vendor may thereafter submit a new or modified Proposal prior to
the Proposal Submission Deadline. Modification offered in any other
manner, oral or written, will not be considered. A Proposal cannot be
changed, corrected, or withdrawn after the Proposal Submission
Deadline.
3.0 General Contractual Requirements
3.1 General
The District will prepare and negotiate its own Agreement with the Selected
Vendor, giving due consideration to the language of the Vendor’s standard
contracts and associated legal documents. The Agreement with the Selected
Vendor will be executed on or about the date of Board Approval. The contract
must comply with all legal requirements and all applicable Board of Education
Policies.
In the event a protest is submitted, by the deadline specified in Section 6.0,
Projected Calendar of Events, it may result in execution of the Agreement being
delayed. Execution of the Agreement will be deferred until after resolution of the
protest and will occur not earlier than the latest of a) the date of Board Approval
of Contract Award or b) the date of the next available Board meeting following
the date the protest is resolved.
8
3.2 Contract Provisions
The District expects the following general terms to be part of any contract
negotiated following selection of the Vendor. These general terms are not
exhaustive but do represent important terms and conditions that shall be part of
any contract executed between the District and the Selected Vendor. Each
Proposal must identify which of the provisions, if any, is not acceptable. Vendors
are instructed to review District’s Standard contract provided in Appendix A. A
copy of the Vendor’s standard contract is required to be included with each
Proposal.
3.2.1 Type and Term of Contract
The District desires to award purchase orders for:
a) Purchase (not lease) of new network hardware;
b) Installation services for cabling required in the Requirements section
of the RFP.
3.2.2 Warranty
The Selected Vendor will guarantee that the Proposed Products shall
conform in all material respects to the District’s specifications in this
RFP and the Selected Vendor’s Documentation accompanying or
referred to in this RFP.
If a contract is awarded as a result of this procurement process all
warranties made by the Selected Vendor shall be incorporated into the
Agreement and shall be binding upon the Selected Vendor. This
commitment shall include any modification of, or affirmation or
representation as to the above, which is made by the Selected Vendor
in the course of this procurement process, including contract
negotiations.
4.0 Proposal Format
4.1 General
These instructions prescribe the mandatory Proposal format and the approach
for the development and presentation of Proposal data. Proposal format
instructions must be adhered to, all questions must be answered, and all
requested data must be supplied. Vendor response to each of the requirements
in this RFP is required. Failure to respond or non-adherence to any requirement
in this section may be cause for the Proposal to be rejected.
This RFP and the Selected Vendor’s Proposal will become a part of the
Agreement. Any Proposal attachments, documents, letters and materials
submitted by the Vendor shall be binding and may be included as part of the
Agreement.
9
To avoid any confusion as to the set of factual assumptions a Vendor uses in
submitting its Proposal, each Proposal must state specifically those factual
assumptions upon which each Proposal is based. A mere reference to this RFP
will be considered non-responsive. It is expected that each representation of fact
and of future performance will be incorporated completely within the Agreement
as a warranty by the Selected Vendor. Any statement of fact or of future
performance that is not intended by a Vendor as a warranty should be clearly
identified. Submission of a successful Proposal is not the end of the contractual
process; further negotiation over the Agreement terms and conditions will be
necessary, which, in and of itself, could change the Selected Vendor.
The Proposal must include detailed specifications of any required hardware, any
required software packages not included as part of the Vendor’s Proposal, and
any personnel time which will be required of District staff. The Vendor shall
provide such specifications as attachments to the Proposal. Additional material
may be submitted with the Proposal as attachments. Any additional descriptive
matter used in the Proposal must be referenced by the appropriate publication
name and page number.
Each Vendor shall submit a Proposal with all information requested. The
Proposal should be as clear, complete and consistent as possible.
4.1.1 Format of Requirements
Requirements are presented in a tabular format.
4.1.2 Format of Responses to Requirements
A Vendor must respond to each requirement by entering a “Yes” or “No”
response in the column entitled “Response” for mandatory
requirements. Each response should be accompanied with an
explanation or a reference.
Vendor shall use the electronic version of this RFP available on the
District web page in compiling their Proposal, in which case the
“Response” and “Explanation and/or Reference” columns can be used
to provide required reference and/or supporting information. A Vendor
may include this information directly below a requirement, or as an
attachment identified by the requirement number.
4.2 Content and Sequence
All information shall be entered in ink or typewritten. Mistakes may be crossed
out and corrections inserted before submission of the Proposal. The person
signing the Proposal should initial any corrections in ink.
All Proposals shall be submitted under sealed cover bearing on the outside the
name and address of the Vendor and indicating "Confidential Proposal in
Response to Francisco MS IT Upgrade RFP ". A Vendor shall submit one (1)
original, marked “Master Copy”, five (5) copies, One (1) CD soft copy of their
10
Proposal to the Purchasing Department. Please be advised that if a Vendor
responds to this RFP using the electronic file provided the appropriate number of
hard copies with the appropriate signatures of execution will still be required.
The completed Proposal must include the following items:
4.2.1 Proposal Identification Statement
The Vendor should provide the organization name, mailing address,
and primary contact person information.
4.2.2 Response to Requirements
The response must contain all responses to the requirements in this RFP
with organization in the same format and order as presented in this RFP.
All cost information required must be included in the response.
The Vendor shall submit “Master Copy” and five (5) copies of the
proposal which will be organized in the following format:
4.2.2.1 Table of Contents - The table of contents and Proposal will
conform to the same order as presented in this RFP.
4.2.2.2 Exceptions- This section of the Proposal will note any
exceptions to the requirements and conditions taken by the
Vendor. Identify, with explanation, any requirements and/or
conditions of this RFP with which you cannot or will not comply.
If exceptions are not noted, the District will assume that a
Vendor’s Proposal meets those requirements and conditions.
4.2.2.3 Prerequisite Qualifications Response- This section must
include a response to each requirement in Section 8.0,
Prerequisite Qualifications.
4.2.2.4 Requirements Response- This section must include a
response to each requirement in Section 9.0, Requirements.
4.2.2.5 Cost Response- This section must itemize all costs chargeable
to the District, as described in Section 10.0, Cost Data.
4.2.3 Supplementary Information
4.2.3.1 Technical Literature - Literature required to substantiate the
Vendor’s response to the requirements, including fiber and
copper cable test results, qualifications of company and
installation/support personnel.
4.2.3.2 Vendor Contract - The Vendor must submit a copy of their
standard contract.
11
4.2.3.3 Customer References – The vendor must provide at least three
references from customers meeting the following criteria:
(1) Scope of project similar to the requirements outlined in this
RFP;
(2) Work is currently underway or was completed within the last
three years.
4.2.3.4 Optional Exhibits and Attachments - Any other information
submitted beyond that required by this RFP, which the Vendor
deems applicable to their Proposal, should be placed in this
section.
5.0 Evaluation and Selection Process
5.1 General
This section outlines the philosophy and general conduct of the evaluation and
selection process, which the District will use to select a Vendor. All Proposals
received in response to this RFP will receive a fair and impartial evaluation by the
District, which shall make its evaluation in its sole discretion and its decision shall
be final.
In conducting this evaluation the District may obtain and use information, in
addition to that contained in the Proposals, from any source desired. Customers
on each Vendor’s customer list will be contacted, as may other customers
selected by the District.
5.2 Evaluation Scoring
Proposal responses will be weighed on either a pass/fail and/or scored basis in
the sequence outlined below. Grading of each criterion is deemed as
confidential to the District.
A Proposal that is not responsive to those criteria judged on a pass/fail basis may
be rejected, in its sole discretion and if rejected shall not be considered for further
evaluation by the District. Alternatively, the District may, choose to ask
clarification questions of a proposal, in writing, and may then take into
consideration the additional information gathered in from its clarification
questions its scoring process.
Prerequisite Qualifications
a. Conformance to Terms and Conditions of Competition as set
forth in this
RFP………………………………………………………………….…..(Pass/Fail)
Vendor Acknowledgement that purchase will be contingent upon SFUSD
b.
Board of Education Approval, successful completion of the SFUSD
contracting procedures, and funding approval from the Schools and
12
Libraries Division (SLD)……………………………………………….(Pass/Fail)
Vendor agreement to SLD’s Service Provider Invoicing (SPI) format for
c.
reimbursement/payment………………………………………………(Pass/Fail)
Vendor guarantee that all cabling is done in compliance with applicable
d.
building codes and by persons with the appropriate licensure.
……………………………………...……………………………………(Pass/Fail)
Vendor agrees to provide all permits within the scope and cost of the
e.
proposal submitted……………………………………………...……..(Pass/Fail)
Vendor agrees to furnish performance/payment bond ……………(Pass/Fail)
f.
Vendor agrees to comply with prevailing wage regulations, including
g.
adhering to the following requirements:
• Pay the prevailing wages applicable to the work being done;
• Comply with all State laws in the payment and administration of
prevailing wages applicable to the work being done;
• Submit certified payroll records;
• Keep documentation of fringe benefit payments, if any;
• Maintain a daily sign in sheet with the names and trades of the
employees, if any;
• Post or notify workers of the Prevailing Wage Rates at the job site;
and,
• Employ registered apprentices, if any.
Qualifying vendors will be evaluated based on their responses to the
requirements.
Requirements
a. Price of eligible goods and services meeting minimum
requirements………………………………….…………………………..50%
b. Vendor Ability to Perform
- Customer References
- Qualifications and Location of Support Personnel……………………30%
c. Capacity/Quality of goods and services exceeding
requirements…………………………………………………………….…..20%
5.3 Site Inspection
After Vendor demonstration of the Proposed Products is complete, the District
reserves the right to inspect a system in operation at one or more customer sites
prior to notification of the issuance of the award.
5.4 Final Selection
The decision as to what Proposal is recommended for award of contract will be
made on the basis of those Proposed Products and Proposed Services that are
determined to be most responsive to the requirements of this RFP. Award will be
made to the Vendor offering a Proposal deemed to be the most advantageous to
13
the District. The District shall be the sole judge in making such determination
and its decision shall be final. All respondents will be notified in writing of the
District’s selection on or about the date of Notification of Selection specified in
Section 6.0 projected Calendar of Events, of this RFP.
If contracts result from this RFP the Selected Vendor will be required to provide
the Proposed Products and Proposed Services at the prices and rates either
submitted in their Proposal or as a result of negotiations based upon the
Proposal.
5.5 Execution of Agreement
After District selection, negotiations will ensue with the Selected Vendor
regarding the terms and conditions of an Agreement for the Proposed Products
and Proposed Services. Mutually acceptable contracts must be presented to the
District Board of Education for approval. Terms and conditions, which do not
comply in substance with all material requirements of this RFP, which are
contrary to the best interest of the District, or which are in opposition to its policy,
will not be accepted.
6. 0 Projected Calendar of Events
1. RFP advertised --------------------------------------- 12/11/2007
2. Site Walks (By Request) --------------------------- 12/31/2007-01/04/2008
3. Vendor Conference---------------------------------- 01/09/2008 3:30pm- 5pm
4. Last Day to Submit Questions--------------------- 01/10/2008
5. Response to questions------------------------------- 01/11/2008
6. Proposals submission deadline--------------------- 01/21/2008
7. Complete Reference Checks/Site Inspection--- 01/31/2008
8. Notification of Selection--------------------------- 01/31/2008
9. Protest selection deadline-------------------------- 02/08/2008 11:00 am.
10. Final Contract Negotiations and Board Approval 01/31/2008 to TBD
The District reserves the right to extend the above dates, if necessary. All changes will
be posted on our Website http://www.sfusd.edu.
.
6.1 District Contacts
Contract Compliance Office
Ms. Sue Moock Voice (415) 355-6945
135 Van Ness Avenue Fax (415) 522-6711
San Francisco, CA 94102 Email: moocks@sfusd.edu
Purchasing Office
Mr. Rod Sarmiento Voice: (415) 241-6468
135 Van Ness Avenue Fax: (415) 241-6487
San Francisco, CA 94102 Email: sarmientor@sfusd.edu
14
Information Technology Department
Infrastructure Director
Mr. Sean Rozell Voice: (415) 241-6220
601 McAllister Street Fax: (415) 202-0758
San Francisco, CA 94102 Email: rozells@sfusd.edu
Information Technology Department
Chief Information Officer
Ms. Brianne Meyer Voice: (415) 241-6169
601 McAllister Street Fax: (415) 749-3415
San Francisco, CA 94102 Email: fordb@sfusd.edu
7.0 District Responsibilities
The Vendor may assume at least the following tasks for the District and may
propose additional tasks as appropriate.
(1) Provide District-specific information to the Vendor and access to facilities.
(2) Review all Contract Deliverables, equipment, and/or Vendor work
products.
(3) Arrange meeting rooms and coordinate staff attendance.
(4) Document problems and/or approve test results.
(5) SFUSD will provide network hardware installation and integration
(6) SFUSD will provide end user and IDF patch cabling.
8.0 Prerequisite Qualifications
Requirement Vendor Acknowledgement
(Signature of Authorized
Agent)
Vendor Acknowledgement that purchase
will be contingent upon SFUSD Board of
Education Approval, successful completion
of the SFUSD contracting procedures, and
funding approval from the Schools and
Libraries Division (SLD)
Vendor agreement to SLD’s Service
Provider Invoicing (SPI) format for
reimbursement/payment
Vendor guarantee that all fiber installation is
done in compliance with applicable building
15
codes
Vendor agrees to provide all permits within
the scope and cost of the proposal
submitted
16
9.0 Requirements
Section Requirement Vendor Comments/Explanation
Response
1.0 Voice and Data cabling (East
and West Wing)
1.1 Furnish and Install:
• 19” Data Rack for New
East Wing IDF with the
following hardware:
o Four 48-port
CAT6/RJ45 patch
panels
o Four 2-Rack-Unit
horizontal Cable
Management Panels
o One 12-Port
(minimum) Fiber LIU
w/SC termination
o 12” Ladder Rack for
overhead cable
management and
support
• 6-Strand Multi-Mode
Fiber from East Wing
IDF to MDF
o Plenum 6-strand
Multi-Mode Fiber,
50/62.5 Microns,
Terminated on LIU
Shelf
• 6-Strand Multi-Mode
Fiber from 2nd Floor
West Wing IDF to MDF
o Plenum 6-strand
Multi-Mode Fiber,
50/62.5 Microns,
Terminated on
LIU Shelf
• 8 CAT6/RJ45 drops per
classroom from the
East Wing IDF to the
following:
o Two classrooms on
the 1st floor (16
drops total)
o Five classrooms on
the 2nd floor (40
drops total)
o Seven classrooms
17
Section Requirement Vendor Comments/Explanation
Response
on the 3rd floor (56
drops total)
• 16 CAT6/RJ45 drops
from the East Wing IDF
to the East Wing Library
• 36 CAT6/RJ45 drops
from the East Wing IDF
to the East Wing
Computer Lab
o Delivered to Lab
computer
workbenches via three
vertical Power/Data
poles (12 Drops per
pole, one pole per row
of workbenches)
2.0 Voice and Data cabling
(Annex Building)
2.1 • 19” Rack for New Annex IDF
with the following hardware:
o Two 48-port CAT6/RJ45
patch panels
o Two 2-Rack-Unit
horizontal Cable
Management Panels
o 12” Ladder Rack for
overhead cable
management and
support
• 8 CAT6/RJ45 drops per
classroom from the Annex
IDF to the following:
o One classroom in the
Basement (8 drops total)
o Three classrooms on
the 1st floor (24 drops
total)
o Two classrooms on the
second floor (16 drops
total)
• 4 CAT6/RJ45 drops per
office from the Annex IDF to
the following:
o Two offices on 1st floor
(8 drops total)
o Three offices in the
Basement (12 Drops
total)
•
18
Section Requirement Vendor Comments/Explanation
Response
• 8 CAT6/RJ45 drops from the
Annex IDF to the Music
Room
3.0 Local Area Network Switch
Hardware (East Wing)
3.1 Furnish and deliver/ship to
SFUSD main office:
• One HP ProCurve
5372xl Switch (J4848B)
• One HP Procurve xl 2-
Port Mini GBIC plus 14
10/100/100 ports via
RJ45 Switch Module
(J4907A)
• Two HP Procurve xl
switch module (J4820B)
24-port via rj45 10/100
Mbps
• One HP Procurve xl
Redundant Power
Supply (J4839A)
• Four HP Procurve
Gigabit-SX-LC Mini
GBIC module (J4858C)
4.0 Local Area Network Switch
Hardware (Annex)
4.1 Furnish and deliver/ship to
SFUSD main office:
• One HP ProCurve
5348xl Switch (J4849A)
• One HP Procurve xl 2-
Port Mini GBIC plus 14
10/100/100 ports via
RJ45 Switch Module
(J4907A)
• One HP Procurve xl
Redundant Power
Supply (J4839A)
19
10.0 Cost Response
Requirements Item Cost
Section
1.1 Section Total Cost
2.1 Section Total Cost
3.1 Section Total Cost
4.1 Section Total Cost
Total
Cost must include all applicable taxes and fees.
20
Appendix A: Standard Contracts
The SFUSD will require the vendor to use the SFUSD’s templates for
contracting. The sample contract is currently under review and will be posted as
an addendum to this RFP.
A1 Sample Contract
To be added to this RFP by amendment no later than January 1st, 2008.
21
A2 Performance Bond
PERFORMANCE BOND
(100% of Contract Price)
(Note: Bidders must use this form, NOT a surety company form.)
KNOW ALL PERSONS BY THESE PRESENTS:
That WHEREAS, the governing board (“Board”) of the San Francisco Unified
School District (“District”) and (“Principal”)
have entered into a contract for the furnishing of all materials and labor, services and
transportation, necessary, convenient, and proper to perform the following project:
Francisco Middle School Upgrade
which Contract dated , 20___, and all of the Contract Documents
attached to or forming a part of the Contract, are hereby referred to and made a part
hereof, and
WHEREAS, said Principal is required under the terms of the Contract to furnish a bond
for the faithful performance of the Contract;
NOW, THEREFORE, the Principal and
(“Surety”) are held and firmly bound unto the Board of the District in the penal sum of
DOLLARS ($ ),
lawful money of the United States, for the payment of which sum well and truly to be
made we bind ourselves, our heirs, executors, administrators, successors, and assigns
jointly and severally, firmly by these presents, to perform all the work required to
complete the Project and to pay to the District all damages the District incurs as a result
of the Principal’s failure to perform all the Work required to complete the Project.
The condition of the obligation is such that, if the above bounden Principal, his or its
heirs, executors, administrators, successors, or assigns, shall in all things stand to and
abide by, and well and truly keep and perform the covenants, conditions, and
agreements in the Contract and any alteration thereof made as therein provided, on his
or their part to be kept and performed at the time and in the intent and meaning, and
shall indemnify and save harmless the District's Board, its officers and agents, as therein
stipulated, then this obligation shall become null and void, otherwise it shall be and
remain in full force and virtue.
And the Surety, for value received, hereby stipulates and agrees that no change,
extension of time, alteration, or addition to the terms of the contract or to the work to be
performed thereunder or the specifications accompanying the same shall in any way
affect its obligation on this bond, and it does hereby waive notice of any such change,
extension of time, alteration, or addition to the terms of the Contract or to the work or to
the specifications.
22
IN WITNESS WHEREOF, two (2) identical counterparts of this instrument, each of which
shall for all purposes be deemed an original thereof, have been duly executed by the
Principal and Surety above named, on the day of , 20___.
(Affix Corporate Seal)
Principal
By
Surety
By
Name of California Agent of Surety
Address of California Agent of Surety
Telephone Number of California Agent of
Surety
Bidder must attach original Power of Attorney and Certificate of Authority for
Surety and a Notarial Acknowledgment for all Surety's signatures. The California
Department of Insurance must authorize the Surety to be an admitted surety
insurer.
23
A3 Payment Bond
PAYMENT BOND
KNOW ALL MEN BY THESE PRESENTS:
Whereas, San Francisco Unified School District (hereinafter referred to as “Owner”) and
(hereinafter referred to as “contractor”) have entered into a written contract for furnishing
of all
labor, materials, equipment, transportation and services for the construction of
Francisco Middle School Upgrade Project
(address of project here)
at
project located in San Francisco, California (hereinafter referred to as the
“Construction Contract); and
WHEREAS, Contractor is required by the terms of the construction Contract to furnish a
bond for all work, labor, materials, equipment or services furnished in connection with
the Construction Contract;
NOW, THEREFORE, Contractor, as principal, and
(hereinafter referred to as “Surety”), as surety, are held and firmly bound unto
Claimants, as
defined herein, in the penal sum of
DOLLARS($____________),
lawful money of the United States, for the payment of which sum well and truly to be
made as provided in this Payment Bond.
1. Contractor and Surety, jointly and severally, bind themselves, their heirs,
executors, administrators, successors and assigns to Owner to pay for work,
labor, materials, equipment, services or other items furnished for use and
actually used in the performance of the Construction Contract, which is
incorporated herein by reference.
2. With respect to Owner, this obligation shall be null and void if Contractor.
2.1 Promptly makes payment, directly or indirectly, for all sums due
claimants, and
24
2.2 Defends, indemnifies and holds Owner harmless from claims,
demands, liens or suits by any persons or entity whose claim,
demand, lien or suit is for the payment for work, labor, materials,
equipment, services or other items furnished for use in the
performance of the Construction Contract, provided Owner has
promptly notified Contractor and Surety (at the address described in
Paragraph 12) of any claims, demands, liens or suits and tendered
defense of such claims, demands, liens or suits to Contractor and
Surety.
3. With respect to Claimants, this obligation shall be null and void if Contractor
promptly makes payment, directly or indirectly, for all sums due.
4. Surety shall have no obligation to Claimants under this Bond until:
4.1 Claimants who are employed by or have a direct contract with
Contractor have given notice to Surety (at the address described
below) and sent a copy, or notice thereof, to Owner, stating that a
claim is being made under this Payment Bond and, with substantial
accuracy, the amount of the claim.
4.2 Claimants who do not have a direct contract with the Contractor:
.1 Have furnished written notice to Contractor and sent a copy, or
notice thereof, to Owner, as required by and conforming with
Civil Code sections 3252 and 3091; and
.2 Not having been paid within 30 days of sending the required
notice, have sent a written notice to Surety (at the address
described below) and sent a copy to the Owner, stating that a
claim is being made under this Payment Bond and enclosing a
coy of the previous written notice furnished to Contractor.
5. When the Claimant has satisfied the conditions of Paragraph 4, Surety shall
promptly and at Surety’s expense take the following actions:
5.1 Send an answer to the Claimant, with a copy to Owner, within 20 days
after receipt of the claim, stating the amounts that are undisputed and
the basis for challenging any amounts that are disputed.
5.2 Pay or arrange for payment of any undisputed amounts.
6. Surety’s total obligation shall not exceed the amount of this Payment Bond, and
the amount of this Payment Bond shall be credited for any payments made in
good faith by Surety.
7. Amounts owed by Owner to Contractor under the Construction Contract shall be
used for the performance of the Construction Contract and to satisfy claims, if
any, under the Performance Bond. By Contractor furnishing and Owner
accepting this Payment Bond, they agree that all funds earned by Contractor in
the performance of the Construction Contract are dedicated to satisfy obligations
25
of Contractor and Surety under this Bond, subject to the Owner’s priority to use
the funds for the completion of the work or the satisfaction of Owner’s claims,
including liquidated damages, under the Construction Contract.
8. Surety shall not be liable to Owner, Claimants or others for obligations of the
Contractor that are unrelated to the Construction Contract. Owner shall not be
liable for payment of any costs or expenses of any Claimants under this Payment
Bond, and shall have under this Payment Bond no obligation to make payments
to, give notices on behalf of, or otherwise have any obligation to Claimants under
this Payment Bond.
9. Surety hereby waives notice of any change, including changes of time, to the
Construction Contract or to related subcontracts, purchase orders and other
obligations.
10. No suit or action shall be commenced by a Claimant under this bond other than
in a court of competent jurisdiction. The prevailing party in any such action shall
be entitled to recover its attorneys’ fees, to be taxed as costs.
11. Notice to Surety, Owner or Contractor shall be mailed or delivered to the address
shown on the signature page.
12. This Payment Bond has been furnished to comply with Civil Code sections 3247
through 3252. Any provision in this Payment Bond conflicting with those
statutory requirements shall be deemed deleted and provisions conforming to
such statutory or other legal requirement shall be deemed incorporated herein.
The intent is that this Payment Bond shall be construed as a statutory bond and
not as a common law bond.
13. Upon request by any person or entity appearing to be a potential beneficiary of
this Payment Bond, the Contractor shall promptly furnish a copy of this Payment
Bond or shall permit a copy to be made.
14. DEFINITIONS
14.1 Claimant: An individual or entity identified in California Civil Code
sections 3181 or 3248.
14.2 Construction Contract: The agreement between Owner and
Contractor identified above, including all Contract Documents and
changes thereto.
26
CONTRACTOR, as principal Surety
_________________________________ ___________________________________
By: ______________________________ By: ________________________________
Title: _____________________________ Title: _______________________________
Address: Address:
_________________________________ ___________________________________
_________________________________ ___________________________________
_________________________________ ___________________________________
Fax: _____________________________ Fax: _______________________________
Phone: ___________________________ Phone: _____________________________
OWNER:
San Francisco Unified School District
135 Van Ness Avenue
San Francisco, CA 94102
Phone: (415) 355-6979
Fax: (415) 355-6954
27
Related docs
