University of Michigan Request for Proposal # 1223-09 LS Date Dec.

23, 2009

Request for Proposal # 1223-09 LS

For

Products/Services

Request for Proposal Ver.09.06.06 Page 1 of 19

 University of Michigan Request for Proposal # 1223-09 LS Date Dec. 23, 2009

TABLE OF CONTENTS

TABLE OF CONTENTS..............................................................................................................................................2

SECTION 1: INTRODUCTION.................................................................................................................................3

SECTION 2: SCHEDULE OF EVENTS...................................................................................................................5

SECTION 3: PROPOSAL INFORMATION AND PROCESSES..........................................................................5

3.8 SUPPLIER GIFT AND GRATUITY POLICY. UNIVERSITY EMPLOYEES ARE PROHIBITED
FROM ACCEPTING ANY GIFTS, SERVICES OR GRATUITIES FROM SUPPLIERS OR POTENTIAL
SUPPLIERS. RESPONDENT AND SUPPLIER CONFORMANCE TO THIS STANDARD IS EXPECTED.
.........................................................................................................................................................................................9

SECTION 4: SUPPLIER INFORMATION..............................................................................................................9

SECTION 5: SPECIFICATIONS/QUALIFICATIONS.........................................................................................12

SECTION 6: PRICING INFORMATION..............................................................................................................12

SECTION 7: AGREEMENT/MISCELLANEOUS TERMS AND CONDITIONS............................................12

SECTION 9. SIGNATURE PAGE...........................................................................................................................14

ATTACHMENT A......................................................................................................................................................16

INCLUDE APPROPRIATE STANDARD AGREEMENT AS AN ADDITIONAL ATTACHMENT..............16

ATTACHMENT B......................................................................................................................................................17

[PHONE NUMBER].................................................................................................................................................17

[FAX NUMBER].......................................................................................................................................................17

[E-MAIL ADDRESS]...............................................................................................................................................17

ATTACHMENT C......................................................................................................................................................18

ATTACHMENT D......................................................................................................................................................19
...........................................................................................................................................................

Request for Proposal Ver.09.06.06 Page 2 of 19

 University of Michigan Request for Proposal # 1223-09 LS Date Dec. 23, 2009

Section 1: INTRODUCTION
This Introduction section is intended as an explanatory overview only and not intended as
detailed specifications. Additional details and specifications are included in the sections that
follow (see specifically Sections 5, 6, and 7) and in the Agreement, (Attachment A).

1.0 Purpose of this Request for Proposal (RFP). The University of Michigan (the
“University”) intends to establish an Agreement for developing a content repository in
the Drupal environment and then migrating the Open.Michigan content from its current
Plone platform to the new Drupal platform. The relationship shall provide for current
and future needs of the University. The University’s intention is to award one Agreement
for this migration and Drupal customization but retains the right to award multiple
Agreements.

1.1 Background Information. Open.Michigan has a website

(http://open.umich.edu/education/) that has been running on the EduCommons (Zope and
Plone-based) content management system (CMS) since late 2007. We have recently (last
6 months) attempted to scale our system up to host ~40 collections (courses/modules) of
downloadable resources. We have only 5-6 heavy administrative users but 4000-5000
monthly unique end-users. Our current database is 5 - 6 GB and we are already using
nearly 8GB of RAM on the Plone server. In addition, we currently have a large backlog
of content - approximately 750 individual files - to publish in early January, which will at
least double our current portfolio of published materials. Due to Plone’s limitations
related to large content objects, we are experiencing a number of scaling issues with its
architecture, database robustness, customization and development, and long-term
sustainability. We have chosen to migrate to Drupal in early 2010 in an effort to address
these scalability, reliability, and adaptability issues. At this time, we are also making
changes to our main website navigation (current: http://open.umich.edu -- new:
http://open.umich.edu/test-home) and would like the Drupal system to stay consistent
with the navigation as well as the look and feel of that site. Our content should also use
the same file names and follow the same structure so that all our current URLs will be the
same after the migration. Our effort at a Drupal prototype
(http://gateway.msis.med.umich.edu/educommons/) of the current website attempts to
keep the same basic look and feel for the end user.

We are looking for software developers to build a repository for educational content on a
Drupal platform that would replace our current Plone platform. This work will include
not only customizing Drupal to meet the various requirements (see Attachment C) for
functionality, but also a migration of our data in its current form to a new database within
Drupal. Since the data are formatted and stored in the Plone/Zope system, the developers
will need experience and expertise with migrating data from the Plone environment into
Drupal.

The Plone content is currently organized by colleges/schools and then by courses or

modules within those departments. Each course/module may be as simple as a description
with a link to an externally hosted website, or as complex as 70 individual downloadable
files. On average, there are roughly 6 HTML pages and 40 files per course/module. These

Request for Proposal Ver.09.06.06 Page 3 of 19

 University of Michigan Request for Proposal # 1223-09 LS Date Dec. 23, 2009

files are images, PowerPoint presentations, Word documents, OpenOffice documents,

PDFs, text files, and various code scripts. In addition, we have video files and MP3 files
that are hosted elsewhere (YouTube and archive.org) and embedded on our HTML pages.
Our current publishing process for this content can be found in Attachment D.

Our website includes rich metadata at the department, course/module, and individual file
level. Our current site includes RDF and RSS feeds across the level. The table below
provides an example of the feeds available:
Level RSS RDF
https://open.umich.edu/education
Site N/A
/rss
e.g., e.g.,
Department https://open.umich.edu/education https://open.umich.edu/education/si/
/si/rss rdf
e.g., e.g.,
Course/Module https://open.umich.edu/education https://open.umich.edu/education/si/
/si/si502-winter2009/rss si502-winter2009/rdf

This migration to Drupal will be completed in 2 phases -- the first phase is split into two
components. These phases indicate criticality of functionality based on our upcoming
expected timeline of use of the system. Phase 1a and 1b cover the main functionality of
the current system, with a few enhancements required to position us for Phase 2 work.
Prior to Phase 2 work, the current data within Plone/Zope needs to be migrated to the
new Drupal system. Phase 2 is comprised of additional functionality beyond our current
system but is not critical for the lateral move from Plone to Drupal.

Our initiative, Open.Michigan, works within an ethos of open and shared data, software,
and educational resources. This is why we choose to use Free/Open Source Software
solutions such as Drupal, Plone and EduCommons. Therefore, we expect to follow the
license conditions for Drupal, which uses the GNU General Public License version 2 (GPLv2),
and share the entire codebase for this project under the terms of the GPLv2 so that our
colleagues and anyone in the world can modify and distribute this system.

1.2 Service Area. The primary service area for this RFP is Ann Arbor, MI
however service may be required at additional locations.

1.3 Term of Agreement. The initial term of the Agreement will be for 5
months. The anticipated Agreement period will begin January 20, 2010 and
continue through May 2010, or until all services ordered prior to the ending date
have been satisfactorily delivered. For additional term provisions, please refer to
the Agreement, included as Attachment A.

1.4 Completeness and Compliance. In the initial phase of the evaluation,

proposals will be reviewed for completeness and compliance with all requests and
requirements, including proposal instructions, specifications, and terms and conditions of

Request for Proposal Ver.09.06.06 Page 4 of 19

 University of Michigan Request for Proposal # 1223-09 LS Date Dec. 23, 2009

the Agreement. Proposals that fail to comply with the essential requests and
requirements of the RFP may be rejected as non-responsive and eliminated from further
consideration. Suppliers should understand that Agreement terms, conditions and
technical specifications do not fully identify nor completely define the University’s
service requirements and satisfaction. The successful Supplier shall be expected to
work closely with the University’s designated representative(s) to administer an
effective and efficient program resulting in high overall customer satisfaction.

Section 2: SCHEDULE OF EVENTS

The approximate timelines relative to this RFP are provided below.

Activity Due Date
Request for Proposal issued December 23, 2009
Deadline for submission of Supplier written questions. Supplier to submit questions
by a MS Word document to [email protected],[email protected] January 4, 2009
Response to questions by the University (estimated) – Responses to questions will be
forwarded to Supplier recipients via email. January 6, 2010
Submission of Intent to Respond form – Fax or PDF are acceptable January 8, 2010
Pre-Bid Conference, RFP Review Meeting or Walk Through January 12, 2010
Deadline for Submission of Proposals – Hardcopy required. January 15, 2010
Closing Time – 4:00 p.m.

Section 3: PROPOSAL INFORMATION AND PROCESSES

The section includes instructions on the format Suppliers must follow in preparing and
submitting their proposals. This section further identifies how questions can be raised and will
be addressed. Finally, this section identifies the specific rights reserved by the University and
other restrictions imposed on the RFP Process.

3.0 Compliance with Specifications. Suppliers are required to respond to all requests
identified in this RFP and indicate their acceptance or objection to the terms of the
Agreement, included as Attachment A. The University intends to use the Agreement
(Attachment A) for any agreement resulting from this RFP. Any exceptions to the terms
and conditions in the Agreement must be clearly indicated in your response to this
proposal. The Agreement is to be signed upon award. The Supplier must minimally
indicate its ability to comply with each requirement, by indicating, “complies” in the
space provided. For consideration, Supplier must meet all specifications indicated.

3.1 Intent to Respond. The “Intent to Respond” Form, Attachment B, must be completed
and email to [email protected] on the date set forth in the Schedule of Events. Receipt
of the Intent to Respond form will ensure that the Supplier will receive copies of any
additional information or addenda.

Suppliers may revoke their Intent to Respond form at any time prior to the due date of the
proposals (see Section 2: Schedule of Events).

3.2 Decline to Offer. Any firm which received a copy of the Request for Proposal, but
which declines to make an offer is requested to send a formal “Decline to Offer” to the

Request for Proposal Ver.09.06.06 Page 5 of 19

 University of Michigan Request for Proposal # 1223-09 LS Date Dec. 23, 2009

issuing office by using the Intent to Respond form. Failure to respond as requested may
result in the Supplier’s removal from consideration on future requirements.

3.3 Required Proposal Format. While there is no intent to limit the contents of a proposal,
the proposal should conform to the format outlined below to ensure that all pertinent
information necessary for evaluation is included and in the same format to facilitate
review.

For each item under Sections 4, 5, & 6, please first list the University's request or
requirement and then list your response below it. Responses must be in the same
numerical format and order as the requirement you are responding to. You may use the
electronic copy of this RFP and insert your responses into it under each
requirement.

Tab 1 Table of Contents/Page Identification. Include a Table of Contents and number

the pages in the proposal consecutively. Attachments should be numbered and
labeled separately.

Tab 2 Introduction. This should consist of a concise non-technical summary providing a

management overview of the proposal that outlines the Supplier's approach to
meeting the University's requirements.

Tab 3 Supplier Information. Suppliers are to answer each request in Section 4: Supplier
Information. If desired, Suppliers can also include any additional information
regarding this program, additional benefits or incentives not included in other
sections. Suppliers must include any request for modifications to the
requirements in Section 4.

Tab 4 Specifications/Qualifications. Suppliers are to respond to each

specification/requirement in Section 5: Specifications/Qualifications. Suppliers
must include any request for modifications to the requirements in Section 5.

Tab 5 Pricing Information. Suppliers are to address each assumption or requirement in

Section 6: Pricing Information. Suppliers must include any request for
modifications to the requirements in Section 6. Suppliers must provide a complete
cost and time estimate for each phase of the development process (i.e., Phase 1a,
1b, 2, and the data migration).

Tab 6 Agreement. Suppliers are to address each term and condition in Attachment A:
Agreement, including any required Supplemental Terms and Conditions.
Suppliers must include in this section any objections or request for modifications
to the Agreement. Include all information and documents request in Section 7, if
not already provided elsewhere. The Agreement is to be signed upon award.

Tab 7 Alternative Proposal. Supplier must submit any alternative proposals to this
request under Tab 7 and not in any of the above Tabs.

Tab 8 Signature Page. Supplier must complete Section 9: Signature Page.

Request for Proposal Ver.09.06.06 Page 6 of 19
 University of Michigan Request for Proposal # 1223-09 LS Date Dec. 23, 2009

3.4 Requirements for Return of Proposal Responses. Supplier must submit the following:

• one (1) signed printed original

• one (1) printed copy
• one (1) electronic copy submitted

Each of the required copies must include all the elements specified in this RFP
and comply with the format specified above in 3.3.

3.4.1 Proposals must be received (1) by the time specified in the Schedule of Events
and (2) at the office indicated below. Carefully review the Schedule of Events in
Section 2 for due dates for submittal of important documents and for the
University’s response dates. Each Supplier is solely responsible for the timely
delivery of its proposal. Failure to meet the proposed due date and time shall be
grounds for rejection. Receipt of the Proposal by the University mail system
does not constitute receipt of a proposal by the University of Michigan
Procurement Services/Contracts and Procurement.

(1) A Supplier’s proposal is due no later than 4 p.m. local time on January
15, 2010 and must be returned to:

(2) Lalit Sharma

7071 Wolverine Tower
3003 S. State Street
Ann Arbor, Michigan 48109
Ph: 734-615-9240
Fax: 734-647-0733
E-mail: [email protected]
3.4.2 A Supplier may withdraw a proposal prior to the closing time. After the due
date, submitted proposals constitute an offer by the Supplier and shall remain
irrevocable for a period of 120 days.

3.4.3 Late responses will not be accepted.

3.4.4 A legally authorized representative of the Supplier must sign the proposal.

3.4.5 The ability of the University to “open” all electronic information submitted must
be verified by the University of Michigan Procurement Services/Contracts and
Procurement prior to being accepted.

3.5 Questions and Clarification. Any questions regarding this request must be directed, in
writing, to Ted Hanss ([email protected]) and [email protected]. All questions must
be submitted by January 4th, 2009. Questions submitted after this deadline, do not require
a response by the University.

Request for Proposal Ver.09.06.06 Page 7 of 19

 University of Michigan Request for Proposal # 1223-09 LS Date Dec. 23, 2009

3.5.1 A Supplier is expected to raise any questions, exceptions, or additions they have
concerning the RFP document. If Supplier discovers any significant ambiguity,
error, conflict, discrepancy, omission, or other deficiency in this RFP, Supplier
should immediately notify the above named individual of the deficiency and
request modification or clarification of the RFP document.

3.5.2 Questions and answers will be provided via e-mail or posted on a University
website.

3.5.3 In the event that it becomes necessary to provide additional clarifying

information or to revise any part of this RFP after January 8, 2010,
revisions/amendments and/or supplements will be provided to only those
suppliers that have submitted the Intent to Respond, Attachment B.

3.6 Supplier Presentations.

Selected suppliers may be required to make oral presentations. Failure of a supplier

to conduct a presentation on the date scheduled may result in rejection of the
supplier’s proposal. In addition, the University may decide to make site visits to the
selected suppliers’ sites.

3.7 Rights Reserved by the University and Restrictions on RFP Process.

3.7.1 The University reserves the right to reject any or all proposals, including by way
of example only and without limitation, any proposal that does not contain all the
requested information.

3.7.2 The University reserves the right to negotiate with any Supplier considered
qualified or to make an award without further discussions. The University highly
recommends that a Supplier’s initial proposal reflect Supplier’s terms most
favorable to the University.

3.7.3 The University reserves the right to waive any irregularity in any proposal
received.

3.7.4 The University reserves the right to negotiate with any Supplier(s) and to arrive at
its final decision and/or to request additional information or clarification on any
matter included in the proposal,

3.7.5 The University reserves the right to select the most responsive Supplier(s) without
further discussion, negotiation, or prior notice.

3.7.6 The University may presume that any proposal is a best-and-final offer.

3.7.7 The University reserves the rights to award in part, in whole, or not at all.

Request for Proposal Ver.09.06.06 Page 8 of 19

 University of Michigan Request for Proposal # 1223-09 LS Date Dec. 23, 2009

3.7.8 Suppliers who offer prices on all items may be given preference; however,
the University reserves the right to delete specific line items in order to
provide a basis for an evaluation of the prices quoted by all Suppliers.

3.7.9 The University will not pay for any information requested nor is it liable for costs
incurred by the Supplier in responding to this request. Elaborate proposals (e.g.
expensive artwork) beyond that sufficient to present a complete and effective
proposal are not necessary or desired.

3.7.10 Any discussions with University personnel, other than as listed above, regarding
this RFP while the RFP is in progress (from the time Supplier receives this RFP
until final award is made) are strictly prohibited. Such contact and discussion
may result in disqualification of Supplier’s proposal.

3.7.11 The University is the sole owner of all data and information contained within the
Request for Proposal document and accompanying attachments. Supplier shall
use this information exclusively to prepare a proposal. Supplier should not
disclose this information to any other firm or use it for any other purpose unless
required by law or legal process.

3.7.12 Supplier proposals will be opened and reviewed at the convenience of the
University; there is no public opening.

8.13 All proposals submitted become the property of the University; they will not be
returned and may be subject to disclosure under the STATE OF MICHIGAN
FREEDOM OF INFORMATION ACT (“FOIA”) or other legal process. As such,
proposal may be released to third parties, without prior notice to Supplier, as
required to comply with legal requirements.

3.8 Supplier Gift and Gratuity Policy. University employees are prohibited from accepting
any gifts, services or gratuities from suppliers or potential suppliers. Respondent and
supplier conformance to this standard is expected.

Section 4: SUPPLIER INFORMATION

Suppliers are required to address all the requests below and to provide samples when
appropriate. If providing an attachment, Supplier must clearly identify the request number for
each response.

4.0 General Corporate and Contact Information.

4.0.1 Provide (1) the legal name of Supplier’s firm, (2) the legal form of Supplier’s firm
(3) the state or county where organized, (4) the address of Supplier’s principle
place of business, (5) website address, and (6) an organizational chart and
description of major business ventures.

4.0.2 Provide the contact information for the person responsible for this proposal
including (1) name (2) title (3) address (4) telephone number (5) fax and (6) email
address.

Request for Proposal Ver.09.06.06 Page 9 of 19

 University of Michigan Request for Proposal # 1223-09 LS Date Dec. 23, 2009

4.0.3 If different from the contact information provided above, provide the contact
information for the individual duly authorized to enter into an Agreement on
behalf of Supplier.

4.1 Supplier Experience.

4.1.0 Indicate how long Supplier has been performing the services or selling the
products requested in this RFP.

4.1.1 Provide a corporate history/management summary showing that Supplier and/or

its officers have been engaged for a minimum of three (3) years in providing
similar services or products as requested in this RFP.

4.1.2 Provide a description of Supplier’s qualifications to meet Specifications and

provide the Services/Products requested in this RFP, including a history of
Supplier’s prior experience in this area.

4.1.3 Describe any specific growth in this service/product area over the past three (3)
years.

4.1.4 Describe any specific restructuring, mergers and/or downsizing with Supplier’s
firm that have occurred during the past three years or is anticipated in the next
three years, noting potential impacts to the Services/Products contemplated by
this RFP.

4.1.5 Provide information relating to Supplier bankruptcies or reorganizations due to

financial hardship.

4.1.6 Does Supplier’s firm partner with any other suppliers for the delivery of
Services/Products requested by this proposal? If so, please explain each partner,
the nature of the relationship and services/products provided.

4.2 N/A

4.3 Supplier Relationships or Potential Conflicts with the University.

4.3.1 Describe any business relations that Supplier currently has or has
had with the University; include relationships any parent, subsidiary, or other
affiliate company may have with the University.

4.3.2 Please indicate if any employees, officers, directors, members, agents or

consultants of Supplier are also an employee of the University. Please refer to
the University’s Conflict of Interest Policy available on the Internet at the
following address:
http://www.procurement.umich.edu/files/conflict_of_interest_policy.pdf

4.4 Supplier Client List/References.

Request for Proposal Ver.09.06.06 Page 10 of 19
 University of Michigan Request for Proposal # 1223-09 LS Date Dec. 23, 2009

4.4.1 Provide at least three (3) references, not including the University,
identifying clients with requirements similar to those of the University. At a
minimum, please provide the name of the client, contact person, and a telephone
number for such references. The University reserves the right to contact
additional references not provided by the Supplier. Preference may be given for
those references that are most similar in profile and type requested.

4.4.2 Please list any clients that have terminated the same or similar Services in the past
24 months. Include the contact name, title, phone number, size of account, date
client became a customer and date(s) of termination. Explain why client(s)
terminated.

4.5 Code of Conduct for University of Michigan Vendors.

The University of Michigan has a longstanding commitment to sound, ethical and
socially responsible practices. To ensure that such practices are codified for the
University's vendors, the President’s Task Force on Purchasing Ethics and Policies has
developed a Code of Conduct for University of Michigan Vendors. The Code of Conduct
can be found at: http://www.procurement.umich.edu/files/code_of_conduct.pdf

To promote socially responsible purchasing, UM and vendors will aspire to follow the
Code of Conduct. The Code of Conduct is not a contractual document but preference
may be given to suppliers, when all other criteria are equal, who demonstrate
compliance with the Code.

4.6 The University of Michigan encourages bidders to become involved in our Supplier
Diversity Program. Supplier Diversity includes businesses that qualify as Small
Disadvantaged Business (SDB), Women-Owned Business Enterprises (WBE),
HubZone, or Veteran Owned Business Enterprises, ADA (American Disability Act). To
qualify as one of the above business classifications your company must be more than
50% owner, controlled and actively managed by a person meeting those requirements.

4.6.1 State your company’s status: (______Small Business) (______ Large Business)
(______ SDB) (______ WBE) (______ HubZone) (_____ Historically Black
College/University) (_____ Veteran Owned) (______ Service Disabled Veteran
Owned) (______ADA)

4.6.2 Does Supplier’s business currently have a Supplier Diversity Program in place?
Yes _______ No _______

4.63 If Supplier answered “yes”, please provide the name and telephone number of
Supplier’s Program Coordinator ____________________________________.

4.6.4 Identify any and all Second Tier Business Relationships or First Tier Business
Relationships Supplier has with Minority, Women, and Handicapped Owned and
operated businesses.

Request for Proposal Ver.09.06.06 Page 11 of 19

 University of Michigan Request for Proposal # 1223-09 LS Date Dec. 23, 2009

4.7 Value Added Services. Describe, in detail, other value-added services available to
the University but not necessarily addressed. Supplier may offer additional
products or services. The University shall determine which value-added service
options shall be most beneficial from both a cost and service standpoint, and may
further negotiate these options to include or omit dependent on the needs of the
University.

4.8 Relevant Litigation/Investigations. Describe any current lawsuits, legal actions or

governmental investigations against your company including, but not limited to, parties
of dispute, any equipment affected, cause of action, jurisdiction and date of legal
complaint. Include in this section any problems that your firm or its personnel have
experienced pertaining to training, licensing or certification in the past five (5) years.

Section 5: SPECIFICATIONS/QUALIFICATIONS
Suppliers are required to meet the Specifications and Qualifications below and to provide
samples when appropriate. If providing an attachment, Supplier must identify the specification
number for each response. The Supplier must minimally indicate Supplier’s ability to comply
with each specification by indicating, “COMPLIES” in the space below each requirement. Any
objections must be clearly noted.

Section 6: PRICING INFORMATION

Supplier must identify all costs, fees or charges for which the University may be billed. Costs
not indicated in your proposal will not be paid.

Suppliers electing to propose pricing on additional products or services must submit

additional items on a separate list. The list must be labeled as “Additional Items” in an
“Alternative Proposal” included in Tab 7. The University retains the right to accept or
reject additional items in part or in whole.

Terms of Payment are indicated in the Exhibit B of the Agreement, included as Attachment A.

6.0 N/A

Section 7: AGREEMENT/MISCELLANEOUS TERMS AND CONDITIONS

7.0 In addition to the Specifications of Section 5 and the Pricing Terms of Section 6, any
exceptions to the remaining RFP Terms and Conditions or the Agreement included as
Attachment A must be clearly and completely indicated. Exceptions included may
negatively impact a Supplier’s proposal. In the absence of an objection, the term and
condition will be deemed acceptable to the Supplier and not open to further negotiation.
The University intends to use the Agreement (Attachment A) for any Agreement
resulting from this RFP. The Agreement is to be signed upon award.

7.1 N/A

Request for Proposal Ver.09.06.06 Page 12 of 19

 University of Michigan Request for Proposal # 1223-09 LS Date Dec. 23, 2009

7.2 The University desires to purchase “Energy Star” compliant equipment; this shall be
taken into consideration as part of the award decision. Supplier shall describe the
availability of “Energy Star” compliant equipment and include manufacturer
specifications as part of the Supplier’s response. For more information on Energy Star,
please reference the following website: www.energystar.gov

7.3 Inventory Controls - In the event of a manufacturer’s backorder, an approved

substitute will be provided at no extra charge. The Supplier will maintain sufficient
inventory of contracted items in its distribution system to guarantee delivery for the
University of Michigan within the time frames listed in this request.

7.4 [Furnish and Install] - The items in this Proposal shall be provided on a supplier
furnish and install basis. The successful Supplier shall have complete responsibility
for the items or products. All transportation and coordination arrangements shall
be the responsibility of the supplier. Delivery of products shall be coordinated so
that products shall be delivered direct to the installation site.

Request for Proposal Ver.09.06.06 Page 13 of 19

 University of Michigan Request for Proposal # 1223-09 LS Date Dec. 23, 2009

Section 8. SELECTION CRITERIA

Proposals will be evaluated on the basis of the most competitive offer considering quality of
products and services offered, cost, responsiveness to the RFP requirements, and the most
responsiveness in meeting those requirements.

The major criteria that may be used to evaluate proposals will include, but not be limited to, the
following:

• Supplier’s ability to meet the functional requirements of this RFP.

• Supplier’s financial stability.
• Supplier’s willingness to comply with the proposed agreement with no objections
• Supplier’s commitment and experience in successfully performing similar
agreements.
• Supplier’s commitment to healthcare.
• Supplier’s adherence to industry standards.
• Supplier’s cost for performing the requirements of this RFP.
• Supplier’s compliance to the schedule of events including participation in pre-bid
conference, RFP review meeting and walk through if applicable.
• Acceptability of product/services to the internal customer.
• Overall product quality including the results of product testing.
• Cost data (price, price protection and total cost of ownership).
• Lead times and delivery schedules.
• Ability to supply complete product line.
• Value added proposals.
• Energy Star compliant, if appropriate.
• Demonstrated compliance with Code of Conduct

Section 9. SIGNATURE PAGE

By virtue of submittal of a proposal, Supplier acknowledges:

• That all of the requirements of this RFP have been read and understood.
• That the Agreement has been read and understood.
• That compliance with the Specifications/Qualifications and Agreement and any
applicable Supplemental Terms and Conditions will be assumed by the University if
not otherwise noted in the submittal.
• That Supplier is not delinquent on the repayment of any Federal debt.
• That Supplier is presently not debarred, suspended, proposed for debarment,
declared ineligible, nor voluntarily excluded from covered transactions by any Federal
department or agency.
• Any responses, materials, correspondence, or documents provided to the University
are subject to the State of Michigan Freedom of Information Act and may be released
to third parties in compliance with that Act.
• The individual signing below has authority to enter into this on behalf of Supplier.

Request for Proposal Ver.09.06.06 Page 14 of 19

 University of Michigan Request for Proposal # 1223-09 LS Date Dec. 23, 2009

CORPORATE NAME ________________________________________________

AUTHORIZED SIGNATURE: _____________________________________________

PRINT NAME: ________________________________________________

TITLE: ________________________________________________

DATE: ________________________________________________

ADDRESS: ________________________________________________

CITY: ________________________STATE: ____________________________

ZIP CODE: __________ PHONE #: __________________________

TOLL FREE #: _______________________FAX #: ____________________________

EMAIL ADDRESS: ______________________________________________________

The Internal Revenue Code requires recipients of payments which must be reported on Form
1099 to provide their taxpayer identification number (TIN).

T.I.N. (Taxpayer Identification Number or Federal Identification Number, Social Security

Number)

T.I.N. Number________________________ Social Security Number_____________________

NOTE: If the address to submit purchase orders, remit payment or send additional request for
proposals is different from the above address, please indicate those addresses on a separate
sheet and include with your response.

Request for Proposal Ver.09.06.06 Page 15 of 19

 University of Michigan Request for Proposal # 1223-09 LS Date Dec. 23, 2009

ATTACHMENT A

Include appropriate standard agreement as an additional attachment.

Request for Proposal Ver.09.06.06 Page 16 of 19

 University of Michigan Request for Proposal # 1223-09 LS Date Dec. 23, 2009

ATTACHMENT B
INTENT TO RESPOND

MEMORANDUM TO BE COMPLETED AND RETURED BY JANUARY 8, 2010.

NOTE: It is acceptable to either fax this completed form or send an e-mail message containing
all of the elements of the form by using the contact information below.

TO: [Buyer Name]

[Title]
The University of Michigan
Procurement Services/Contracts and Procurement
[Address]
[Phone Number]
[Fax Number]
[E-mail Address]

RE: RFP Open.Michigan Drupal Migration

DATE: _____________

As requested, please accept this completed form as evidence of our intention to respond to this
request for proposal. We have checked all items that apply:

 We have all of the information that we need in order to prepare our proposal. We will be
submitting a RFP response.

 We will attend the Pre-Bid Conference, RFP Review Meeting or Walk Through on
January 12, 2010.

 We have questions that need to be addressed before we can prepare our proposal. Our
requests for additional information will be e-mailed to [email protected] as an attachment
in a word document.

 We will not be responding to the aforementioned RFP; however, we would like to be

considered on future requirements.

COMPANY NAME: ______________________________________ ________ _

AUTHORIZED SIGNATURE: ________________________________________ ___ _

PRINT NAME: _______________________________________________

TITLE: _______________________________________________

PHONE #: ________________________ FAX #:

E-MAIL ADDRESS: _

Request for Proposal Ver.09.06.06 Page 17 of 19

 University of Michigan Request for Proposal # 1223-09 LS Date Dec. 23, 2009

ATTACHMENT C

DETAILED FUNCTIONALTY REQUIREMENTS AND DEVELOPMENT PHASES

See the file titled "DrupalReqs_OpenMichigan.xls"

Request for Proposal Ver.09.06.06 Page 18 of 19

 University of Michigan Request for Proposal # 1223-09 LS Date Dec. 23, 2009

ATTACHMENT D

OPEN.MICHIGAN OER PUBLICATION PROCESS

1. The publication process begins once we have materials that have been cleared for
copyright – this content is typically stored in our web-based tool: OERca.
2. Our publishing staff (4 - 5 people) complete some file renaming and file conversion
(e.g. .doc to .pdf).
3. We add those files to the CMS (EduCommons/Plone/Zope) and create HTML pages to
present the resources.
4. In addition to the content we create manually using HTML, the EduCommons interface
lets us assign certain attributes to each course, including copyright/license info and
metadata.
5. We create a limited access account for content creators (e.g. faculty) to preview their
materials. They generally login only once for the review process.
6. We make revisions to the course/module based on the reviewer's comments.
7. We move the course from in progress/private to public.
8. Occasionally we have to make changes to a page after it's been published. We would like
to be able to have revisions of pages and modify/troubleshoot the page without affecting
the published one.

You can view the current detailed publication process at

https://open.umich.edu/wiki/Publishing_Process. The outline/table of contents will be the most helpful,
as the individual steps are quite detailed and focus on the workarounds in our current Plone
system.

Request for Proposal Ver.09.06.06 Page 19 of 19