MONTANA STATE UNIVERSITY REQUEST FOR PROPOSAL (RFP)

tangibleassistantSoftware and s/w Development

Dec 3, 2013 (3 years and 10 months ago)

300 views

RFP#14
-
05 Shared Research Computing Infrastructure

Dept.: Information Technology


Page
1

of
50


Ather

MONTANA STATE UNIVERSITY

REQUEST FOR PROPOSAL (RFP)


(THIS IS NOT AN ORDER)


RFP Number:

14
-
05

RFP Title:

Shared Research Computing Infrastructure

RFP Response
Due Date and
Time:

December 6
, 2013

2:00 p.m., Mountain Time

Number of Pages:

50

Issue Date:

October 25
, 2013



Procurement Officer:

Brian O’Connor

Montana State University
-
Bozeman

Procurement Services

19

Montana Hall

PO Box 172600

Bozeman, MT. 59717
-
2600

Montana
State University
-
Bozeman

Procurement Services

19

Montana Hall
,
PO Box 172600

Bozeman, MT. 59717
-
2600


Phone:

(
406) 994
-
3211

Fax:


(406) 994
-
3000

TTY
: (800) 253
-
4091 Montana Relay Services

Website:
http://vendor.mt.gov/


INSTRUCTIONS TO OFFERORS

Return Sealed Proposal to:

Mark Face of Envelope/Package
with:

RFP
Numbe
r:

14
-
05

RFP Response Due Date:

December 6, 2013




PHYSICAL
AND MAILING
ADDRESS:

Montana State University
-
Bozeman

Procurement
Services

19
Montana Hall
,
PO Box 172600

Bozeman, MT. 59717
-
2600


Special Instructions:


OFFERORS MUST COMPLETE THE FOLLOWING

Offeror Name/Address:




(Name/Title)




(Signature)

Print name and title and sign in ink. By submitting a response to this RFP,
Offeror

acknowledges it understands and will comply with the RFP specifications and
requirements.

Type of Entity (e.g., corporation, LLC,
etc.)

Offeror Phone Number:

Offeror
E
-
mail Address:



Offeror FAX Number:

OFFERORS MUST RETURN THIS COVER SHEET WITH RFP RESPONSE


R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
2

of
50


TABLE OF
CONTENTS


Instructions to Offerors

................................
................................
..............................

3


Schedule of Events

................................
................................
................................
.....

4


Section 1:

Project Overview and Instructions

................................
......................

5
-
8


Section 2: RFP Standard Information

................................
................................
..

9
-
1
1


Section 3:

Scope of Services and System

................................
........................

12
-
18


Section 4:

Offeror Qualifications

................................
................................
............

19


Section 5:
Cost Proposal
…………………………………………………


........

.

20
-
23


Section 6:

Evaluation Process

................................
................................
...........

24
-
26


Appendix A



Standard Terms & Conditions

................................
.....................

27
-
30


Appendix B



Contract


................................
................................
......................

31
-
43


Appendix C



RFP Response Form


................................
................................
.......

44


Appendix D



Cost Sheet Parts List


................................
................................
.

45
-
49


Appendix E



Part Specifications


................................
................................
..........

50





















R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
3

of
50


INSTRUCTIONS TO OFFERORS

It is the responsibility of each
Offeror

to:

Follow the format required in the RFP

when preparing your response. Provide responses in a clear and
concise manner.

Provide complete
answers/descriptions.

Read and answer
all

questions and requirements. Proposals
are evaluated based
solely

on the information and materials provided in your written response.

U
se any forms provided
, e.g., cover page, budget form, certification forms, etc
.

Submit your response on time.

Note all the dates and times listed in the Schedule of Events and within
the document. Late proposals are
never

accepted.

The following items MUST be included in the response.

Failure to include ANY of these items may resu
lt in a nonresponsive determination.



Si杮敤 C潶敲eS桥整



Si杮敤 A摤敮摡 (if 慰灲潰物at攩 in 慣捯牤慮c攠with
S散ti潮 1.
5




C潲牥捴oy 數散畴敤⁓瑡t攠潦 M潮t慮a "Affi摡vit fo爠
T牡摥 S散牥t C潮fi摥湴nality" f潲洬 if 捬ci浩湧
i湦潲浡mi潮 t漠扥 捯湦i摥湴nal 潲 灲潰物et慲a
i渠慣捯牤慮捥 with
S散ti潮 2.㌮3
.



I渠慤niti潮 t漠o 摥taile搠d敳灯湳攠t漠oll 牥煵ir敭敮ts withi渠卥cti潮s ㌬ 㐬 慮d

5,
Off敲er

浵獴s
慣歮owl敤来 t桡t it 桡猠s敡搬

畮摥牳t慮摳, a湤 will 捯浰my wit栠敡h栠獥捴i潮/獵扳散ti潮 li獴敤s
扥low 批 i湩niali湧 t桥 li湥 t漠t桥 l敦t of 敡捨. If
Off敲潲

捡湮潴 浥mt a 灡牴i捵la爠牥煵ir敭敮t,
灲潶i摥 愠摥瑡il敤 數pl慮慴a潮 湥硴 to t桡t 牥r畩u敭敮t.




Section 1, Introduction and
Instructions



Section 2, RFP Standard Information



Section 4.1,
University’s

Right to Investigate and Reject



Section 5
,
Cost Sheet



Section 6, Evaluation Process



Appendix A,
Standard Terms and Conditions



Appendix B, Contract



Appendix C,
RFP Resp
onse Form



Appendix D
,

Cost Sheet Parts List




Appendix E
,

Parts Specifications





R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
4

of
50


SCHEDULE OF EVENTS


EVENT

DATE


RFP Issue Date

................................
................................
...................

October 25,

2013


Deadline for Receipt of Written Questions

................................
....

November 8,

2013


Deadline for Posting Written Responses to the

State's Website

November 22,
2013


RFP Response Due Date

................................
................................
.

December 6,

2013


Offeror Interviews/Product Demonstrations


................................
.......................

TBD


Intended Date for Contract Award

................................
..................

January 10,

2013
*



*The dates above identified by an asterisk are included for planning purposes.

These dates
are subject to change.




























R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
5

of
50


SECTION 1:
PROJECT OVERVIEW

AND INSTRUCTIONS


1.
1

INTRODUCTION


Montana State University (hereinafter referred to as “the University”) seeks to
purchase equipment for the
purposes of scalable high performance computing for research (collectively referred to as “the System”). The
System will be composed of three Components: computational and storage hardware (referred to as
“Computation & Storage”
), virtualization software (referred to as “Virtualization”), and networking hardware
(referred to as “Networking”). These Components will work together to form the core of the System. This
System will be incrementally expanded by over time to grow its ca
pabilities and to allow more usage.
Offerors

need not

address all
of the Components
, and may
submit proposals

for just one or two of the
Components
; however
preference

will be given to vendors capable of providing more than a single
component.


A fund has
been established to purchase the Components. The precise split of funds between the Components
will depend on the offerings that are made. Each Offeror is expected to submit detailed specifications of
increments of the Component(s) that they provide in Se
ction 3. They will provide pricing details for a
hypothetical Component purchase and the
expansion of the hypothetical purchase via the
Component
increments of expansion in Section 5. In order to provide the opportunity for an Offeror to provide pricing
that
benefits from scale,

and also to capture the costs associated with scaling at different levels,

Component
expansion increment

price
s are
requested

in
three
different increments.


A more complete

description of
the
equipment and/or services
to

be provided is found in Section 3.



1.
2

CONTRACT
PERIOD


The contract period
is three year(s), beginning

upon contract execution, and ending three years thereafter,
inclusive. The parties may mutually agree to a renewal of this contract in one
-
year inter
vals, or any interval that
is advantageous to the University This contract, including any
renewals, may not exceed a total of ten years,

at
the University's option.


1.
3

SINGLE POINT OF CONTACT


From the date this Request for Proposal (RFP) is issued until an
Offeror

is selected and the selection is
announced by the procurement officer,
Offeror
s

are not allowed to communicate with any
University

staff
or officials regarding this procurement, excep
t
the staff of MSU Procurement Services: Brian
O’Connor, Linda Bell, Kara Stermitz, and Cheri Toeniskoetter. Any other contact must be approved in
advance by
Brian O’Connor,

Director of Procurement.

U
nauthorized contact may disqualify the
Offeror

from fu
rther consideration.

Contact information is as follows:


Procurement Officer: Brian O’Connor

Montana State University
-
Bozeman

Procurement Services

Address: 19

Montana Hall

PO Box 172600

Bozeman, MT 59717
-
2600

Telephone Number:

(406) 994
-
3211

Fax Number:
(406) 994
-
3000

E
-
mail Address:
boconnor@montana.edu


R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
6

of
50


1.4



OPTIONAL PRE
-
PROPOSAL

CONFERENCE

CALL


An
optional

Pre
-
Proposal

conference

call

will be conducted
on

Thursday, October 31, at

1 p.m.,

local time.
Bidders are encouraged to use this opportun
ity to ask clarifying questions
,

obtain a better understanding of the
project, or to notify the
University

of any ambiguities, inconsistencies, or errors discovered upon examination of
this
RFP
.

All
responses to questions at the Pre
-
Proposal

Conference

Call

will be oral and in no way binding on
the
University
.

Participation in the Pre
-
Proposal Conference

Call

is optional; however, it is advisable that all
interested parties participate. To attend ca
ll MSU Procurement Services at 406
-
994
-
3211 before

5:00 p.m. on
October 30, 2013, to receive teleconference instructions.
Offeror will need to provide the names of those
attending the conference.


1.5

REQUIRED REVIEW


1.5.1 Review RFP.

Offerors shall ca
refully review the entire RFP. Offerors shall promptly notify the
procurement officer identified above via e
-
mail or in writing of any ambiguity, inconsistency, unduly restrictive
specifications, or error that they discover. In this notice, the Offeror s
hall include any terms or requirements
within the RFP that preclude the Offeror from responding or add unnecessary cost. Offerors shall provide an
explanation with suggested modifications. The notice must be received by the deadline for receipt of inquir
ies
set forth in Section 1.4.2. The University will determine any changes to the RFP.


1.5.2 Form of Questions.

Offerors having questions or requiring clarification or interpretation of any
section within this RFP must address these issues via e
-
mail or in writing to the procurement officer listed
above on or before
2013
-
11
-
08
.

Offerors are to submit questions us
ing the Vendor
RFP Question and Answer
Form available
on the
OneStop Vendor Information website at:

http://svc.mt.gov/gsd/OneStop/GSDDocuments.aspx
.
Clear reference to the section, page, and
item in
question must be included in the form.


Questions received after the deadline may not be considered.


1.5.3 University's Response.

The University will provide a written response by
2013
-
1
1
-
22

to all
questions received by
2013
-
11
-
0
8
.

The Univers
ity’s response will be by written addendum and will be posted
on the State of Montana's website with the RFP at
http://svc.mt.gov/gsd/OneStop/SolicitationDefault.aspx

by
the close of bu
siness on the date listed. Any other form of interpretation, correction, or change to this RFP will
not be binding upon the University.
Offerors shall sign and return with their RFP response an
Acknowledgment of Addendum for any addendum issued.



1.6

GENERAL REQUIREMENTS


1.6.1

Acceptance of Standard Terms and Conditions/Contract.

By submitting a response to this
RFP, Offeror accepts the standard terms and conditions and contract set out in Appendices A and B,
respectively.

Much of the language incl
uded in the standard terms and conditions and contract reflects the
requirements of Montana law.


Offerors requesting additions or exceptions to the standard terms and conditions, or to the contract terms, shall
submit them to the procurement officer liste
d above by the date specified in Section
1.
5
.2
. A request must be
accompanied by an explanation why the exception is being sought and what specific effect it will have on the
Offeror’s ability to respond to the RFP or perform the contract. The University

reserves the right to address
nonmaterial

requests for exceptions to the standard terms and conditions and contract language with the
highest scoring Offeror during contract negotiation.


The University shall identify any revisions to the standard terms and conditions and contract language in a
written addendum issued for this RFP. The addendum will apply to all Offerors submitting a response to this
RFP. The University will determine any

changes to
the standard terms and conditions and/or contract.


R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
7

of
50



1.6.2 Resulting Contract.

This RFP and any addenda, the Offeror’s RFP response, including any
amendments, a best and final offer

(if any)
, and any clarification question responses shall be
incorporated by
reference

in any resulting contract.


1.6.
3

Understanding of Specifications and Requirements.

By submitting a response to this RFP,
Offeror acknowledges it understands and shall comply with the RFP specifications and requirements.


1.6.
4


Offeror's Signature.

Offeror's proposal must be signed in ink by an individual authorized to
legally bind the Offeror. The Offeror’s signature guarantees that the offer has been established without
collusion. Offeror shall provide proof of authority of
the person signing the RFP upon University’s request.


1.6.
5

Offer in Effect for 120 Calendar Days.

Offeror agrees that it may not modify, withdraw, or
cancel its proposal for a 120
-
day period following the RFP due date or receipt of best and final offer
, if
required.


1.7

SUBMITTING A PROPOSA
L


1.7.1 Organization of Proposal.

Offerors must organize their proposal into sections that follow the
format of this RFP. Proposals should be bound, and must include tabbed dividers separating each section.
Proposal pages must be consecutively numbered.


All subsections not listed in the
"Instructions to Offerors" on page 3

require a response. R
estate the
section/subs
ection number and the text immediately prior to your written response.


Unless specifically
requested in the RFP, an Offeror making the statement "Refer to our literature…" or "Please
see www…….com" may be deemed nonresponsive or receive point deductions. If making reference to
materials located in another section of the proposal, specific page
numbers and sections must be noted.
The
Evaluator/Evaluation Committee is not required to search through the proposal or literature to find a
response.


The

University

encourages

Offerors to use materials

(e.g., paper, dividers, binders, brochures, etc.)
that
contain post
-
consumer recycled content. Offerors are encouraged to print/copy on both sides
of each page
.


1.7.2 Failure to Comply with Instructions.

Offerors failing to comply with these instructions may be
subject to point deductions. Further, the University may
deem
a proposal nonresponsive or disqualify it from
further consideration if it does not follow the response format, is difficult to read or

understand, or is missing
requested information.


1.7.3 Multiple Proposals.

Offerors may, at their option, submit multiple proposals. Each proposal
shall be evaluated separately.


1.7.4
Price Sheets.

Offerors
must

use the RFP Price Sheets found in Se
ction
5.
These price sheets
serve as

the primary representation of O
fferor's cost/price. Offeror should include additional information as
necessary to explain the Offeror’s cost/price.


1.7.5 Copies Required and Deadline for Receipt of Proposals.

Offer
ors must submit
one original
propos
al and
one

copy

to the University Procurement Office. In addition, Offerors must submit
an

electronic
copy

on compact disc (CD) or universal serial bus (USB) flash drive in Microsoft Word or portable document
format (PDF). If any confidential materials are included in accordance with the requirements of Section 2.3.2,
they must be submitted on a separate CD o
r USB flash drive.

Please note that email submissions are
NOT

accepted.

R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
8

of
50



EACH PROPOSAL MUST B
E SEALED AND LABELED

ON THE OUTSIDE OF TH
E PACKAGE

clearly
indicating it is in response to RFP 14
-
05.
Proposals must be received at the reception desk of the
Univ
ersity Procurement Office prior to 2:00 p.m., Mountain Time
,
2013
-
12
-
06
. Offeror is solely
responsible for assuring delivery to the reception desk by the designated time.


1.
7
.6

Facsimile Responses.

F
acsimile
response
s

will

NOT

be
accepted
.


1.7.7 Late

Proposals.

Regardless of cause, the University shall not accept late proposals.
Such proposals will automatically be disqualified from consideration.

Offeror may request the University
return the proposal at Offeror’s expense or the University will dis
pose of the proposal if requested by the
Offeror. (See
Administrative Rules of Montana (ARM)
2.5.509.)


1.8

COSTS/OWNERSHIP OF MATERIALS


1.8.1 University Not Responsible for Preparation Costs.

Offeror is solely responsible for

all costs it
incurs prior to contract execution.


1.8.2 Ownership of Timely Submitted Materials.

The University shall own all materials submitted in
response to this RFP.




R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
9

of
50


SECTION 2: RFP STANDARD INFORMATION


2.
1

AUTHORITY


The
RFP

is issued

under 18
-
4
-
304, Montana Code Annotated

(MCA)

and
ARM
2.5.602.

The RFP process is a
procurement option allowing the award to be based on stated evaluation criteria.

The RFP states the relative
importance of all evaluation criteria.

The
University

shall use o
nly
the evaluation criteria outlined in this RFP
.


2
.
2

OFFEROR COMPETITION


The
University

encourages free and open competition to obtain quality, cost
-
effective services and supplies.


The

University

design
s

specifications, proposal requests, and conditions t
o accomplish this objective
.


2.
3

RECEIPT OF PROPOSALS

AND PUBLIC INSPECTIO
N


2.
3
.1

Public Information.


Subject to exceptions provided by Montana law, a
ll information received in
response to this RFP, including copyrighted material, is public information
.

Proposals

will be made available
for public viewing and copying shortly after the
proposal due date and time
.

The exceptions to this requirement
are
:

(1) bona fide trade secrets meeting the requirements of the Uniform Trade Secrets Act, Title 30, chap
ter
14, part 4, MCA, that have been properly marked, separated, and documented; (2) matters involving individual
safety as determined by the
University
; and (3) other constitutional protections.

See

18
-
4
-
304
, MCA
. T
he
University

provides

a copier for

int
erested parties
'

use at $0.10 per page.


The interested party is responsible
for the cost of copies and to provide personnel to do the copying.


2.
3
.2

Procurement Officer Review of Proposals.


Upon opening the proposals in response to this
RFP the
procurement officer review
s

the proposals
for
information that meets the exceptions in Section 2.
3
.1,
providing the following conditions have been met:




Confidential information
(including any provided
in electronic media
)
is clearly marked and
separated

from the rest of the proposal.



The proposal does not contain confidential material in the cost or price section.



An affidavit from
the

Offeror
'
s legal counsel attesting to and explaining the validity of the trade
secret claim as set out in Title 30, c
hapter 14, part 4, MCA, is attached to each proposal containing
trade secrets.


Counsel must use the State of Montana
"
Affidavit for Trade Secret Confidentiality
"

form in requesting the trade secret claim.

This affidavit form is available on the
OneStop V
endor
Information website at:


http://svc.mt.gov/gsd/OneStop/GSDDocuments.aspx

or by calling (406)
444
-
2575.


Information separated out under this process will be available for review only by the procurement officer, the
evaluator/evaluation committee members, and limited other designees.

Offerors

shall

pay all

of its

legal costs
and

related
fees

and expenses

ass
ociated with defending a claim for confidentiality
should another party
submit

a
"
right to know
"

(open records) request
.


2.
4

CLASSIFICATION AND EVALUATION OF PROPOSALS


2.
4
.1

Initial Classification of Proposals as Responsive or Nonresponsive.


The
Univers
ity

shall
initially classify a
ll proposals
as
either
"
responsive
"

or
"
nonresponsive
"

(
ARM 2.5.602
)
.

The
University

may
de
em

a

p
roposal nonresponsive if
:

(1
)
any of the required information is not provided;
(2)
the submitted price
is found to be excessive

or inadequate as measured by

the RFP

criteria
;

or

(3)

the proposal
does not meet
RFP

requirements
and specifications
.


The
University

may find any proposal to be nonresponsive at any time
R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
10

of
50


during the procurement process.

If
the
University

deems
a

proposal
nonresponsive,
it

will not
be
consider
ed

further.


2.
4
.2

Determination of Responsibility.


The procurement officer will determine whether an
Offeror

has met the standards of responsibility
consistent

with ARM 2.5.407.

An
Offeror

may be determined
nonresponsible at any time during the procurement process if information surfaces that supports a
nonresponsible determination.


If an
Offeror

is found nonresponsible, the

procurement officer will notify the
Offeror

by mail. The determination will be
made

a part of the procurement file.


2.
4
.3

Evaluation of Proposals.


An
evaluator/
evaluation committee will evaluate
all responsive

proposals
based on stated criteria

and recommend award to the highest scoring
Offeror
.

The

evaluator/
evaluation
committee may

initiate

discussion
,
negotiation
,

or a best and final offer.

In scoring against
stated criteria, the
evaluator/
evaluation committee
may consider such factors as accepted industry standards
and a comparative evaluation of other
proposals

in terms of diffe
ring price
and
quality
.


These scores will be
used to determine the most advantageous offering to the
University
.


If an evaluation committee meets to
deliberate and evaluate the proposals, the public may attend and observe the evaluation committee
deliber
ations.


2.
4
.4

Completeness of Proposals.


Selection and award will be based on the
Offeror
'
s proposal and
other items outlined in this RFP.
Proposals
may not include references to information such as Internet
websites, unless specifically requested.


Information or materials presented by
Offeror
s outside the formal
response or subsequent discussion
,
negotiation
,

or best and final offer, if requested, will not be considered, will
have no bearing on any
award, and may result in the
Offeror

being disqual
ified from further consideration.


2.4.5 Achieve Minimum Score.

Any proposal that fails to achieve
960

points (60
% of the total
available points possible excluding points for cost) in a particular Component category
will be

eliminated from further consideration for that Component category. A "fail" for any individual evaluation criteria
may result in proposal disqualification at the discretion of the procurement officer. A “fail” for one Component
category does not preclud
e the Offeror from being successful in another.


2.4.6 Opportunity for Discussion/Negotiation
and/or Oral Presentation/Product Demonstration.

After receipt of proposals and prior to the recommendation of award, the procurement officer may initiate
discus
sions with one or more Offerors should clarification or negotiation be necessary.
Offerors may also be
required to make an oral presentation and/or product demonstration to clarify their RFP response or to further
define their offer. In either case,
Offe
rors should be prepared to host a videoconferencing session or send
qualified personnel to
Bozeman
, Montana, to discuss technical and contractual aspects

of their proposal.
Oral
presentations and product demonstrations, if requested, shall be at the Offer
or’s expense.


2.4.7 Best and Final Offer.


Under Montana law, the procurement officer may request a best and final
offer if additional information is required to make a final decision.
The
University
reserves the right to request a
best and final offer

based on price/cost alone
.
Please note that the
University
rarely requests a best and final
offer on cost alone.


2.4.8 Evaluator/Evaluation Committee Recommendation for Contract Award.

The evaluator/
evaluation committee will provide a written recommendation for contract award to the procurement officer that
contains the scores, justification, and rationale for the decision. The procurement officer will review the
recommendation to en
sure its compliance with the RFP process and criteria before concurring with the
evaluator's/evaluation committee's recommendation.


2.4.9 Request for Documents Notice.

Upon concurrence with the evaluator's/evaluation committee's
recommendation, the proc
urement officer will request from the highest scoring Offeror the required documents
and information, such as insurance documents, contract performance security, an electronic copy of any
R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
11

of
50


requested material (e.g., proposal, response to clarification questi
ons, and/or best and final offer), and any
other necessary documents. Receipt of this request does not constitute a contract and
no work may begin
until a contract signed by all parties is in place
. The procurement officer will notify all other Offerors
of the
University’s
selection.


2.
4
.10

Contract Execution.

Upon receipt of all required materials
,

a contract
(
Appendix B
)

incorporating the Standard Terms and Conditions
(
Appendix A
)
,

as well as the highest scoring
Offeror
's
proposal
, will be provided to

the highest scoring
Offeror

for signature.

The highest scoring
Offeror

will be
expected to accept and agree to all material requirements contained in Appendices A and B of this RFP.

If the
highest scoring
Offeror

does not accept all material requirements, the
University

may move to the next highest
scoring
Offeror
, or cancel the RFP.

Work under the contract may begin when the contract is signed by all
parties.


2.
5

UNIVERSITY’S

RIGHTS RESERVED


While the
Universi
ty

has every intention to award a contract
resulting from

this RFP, issuance of the RFP in no
way constitutes a commitment by the
University

to award and execute a contract.

Upon a determination such
actions would be in its best interest, the
University
,
in its sole discretion, reserves the right to:




Cancel or terminate this RFP (18
-
4
-
307
, MCA
);



Reject any or all proposals received in response to this RFP (ARM 2.5.602);



Waive any undesirable, inconsequential, or inconsistent provisions of this RFP
t
hat

would not have
significant impact on any proposal (ARM 2.5.505);



Not award

a contract,
if it is in the

University
'
s
best interest
not
to proceed with contract execution
(ARM 2.5.602); or



If awarded, terminate any contract if the
University

determines adequate state funds are not
available (18
-
4
-
313
, MCA
).




R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
12

of
50


SE
CTION 3: SCOPE OF
SERVICES

AND SYSTEM


To enable the
University
to determine the capabilities of an Offeror to provid
e the supplies and/or perform the
services specified in the RFP,

the Offeror shall respond to the following regarding

its ability to meet the
University’s
requirements.


All subsections of
Section 3

not listed in the
"Instructions to Offerors" on page 3

require a response.
R
estate the
subs
ection number and the text im
mediately prior to your written response.


NOTE: Each item must be thoroughly addressed.
THE RESPONSE, "(OFFEROR'S NAME)
UNDERSTANDS AND WILL COMPLY," OR “REQUIREMENT MET,” IS NOT APPROPRIATE FOR THIS
SECTION.
Such summary responses to items may be found

nonresponsive. Offerors taking exception
to any requirements listed in this section may be found nonresponsive or be subject to point
deductions.



3.1

OVERVIEW


Offerors should submit responses for any of the following supply and/or service Categories t
hat they feel
qualified to provide. Evaluation of proposals will be evaluated on
the Responses to the Scope of Services,

Company Profile and Experience, Comprehensive Service, and Price. Awards will be made to the Offeror with
the highest score in each Cat
egory.


3.1.1 Overall Goal

The purpose of the System is to create a shared, scalable research computation
infrastructure that provides storage, computation and virtualization services to MSU researchers. The System
is intended to serve as a basis for all
central
ized

high performance computing (HPC)

activities at the
University. In particular, the University plans to invest future start
-
up funds for faculty and future grant funds
garnered by faculty to expand the system over time by adding additional hardw
are; ergo incremental
expandability is a mandatory requirement. Describe how the supplies and/or services provided will contribute
to this requirement.


3.1.2 System Expansion

The University expects to make additional purchases in the future that are
comp
atible with the System. Firm pricing is solicited for expansion of the initial system valid for a period of at
least twelve months after acceptance of the system by the University.
This infrastructure will be provisioned in
a “Condo” model wherein research
ers will purchase additional computational and storage resources, and the
combination of the hardware and software Components will allow the infrastructure to scale incrementally over
time.

Describe how the supplies and/or services provided will contribute

to this requirement.


3.1.3 Condo Model

This infrastructure will be expanded in a “Condo” model wherein researchers will
purchase additional computational and storage resources, and the combination of the hardware and software
Components will allow the in
frastructure to scale incrementally over time. The system will be made available to
researchers in such a way as to allow the researchers the ability self
-
provision and/or easily request
computational and storage resources (with preference given to solutio
ns that allow self
-
provisioning).
Researchers will gain priority access to their purchased resources (their “Condo”), while other portions of the
System will be useable by all
system users

(a “General Pool”). It should be possible to re
-
organize the
hardw
are resources of the System to easily move hardware between the Condo and General Pool. It is
mandatory that the Components be able to interoperate in such a way as to accommodate this model.
Describe how the supplies and/or services provided will contribu
te to this requirement.


3.1.4

Timely Installation

& Professional Services

The University

requires System availability as soon
as possible and as such, Offerors must confirm timeline of availability of proposed components and
R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
13

of
50


professional services. In add
ition to the
professional services associated with
initial implementation of the
System, the Offeror should be able to provide ongoing Support and Training for the hardware and/or services
provided.


3.1.5 Comprehensive Services

The University would prefer

the simplicity of an overall solution that
uses fewer vendors to one that uses many. This is balanced against the requirement to find the very best
vendor solution for each of the Components; while an overall single
-
vendor solution is not a requirement,
it will
receive prefer
ential scoring. Please describe, if relevant, how supplies and/or services will be provided for
each Component category and how they will work together to meet the requirements of the System
.


3.2

COMPUTATION & STORAG
E


The Computati
on Component includes all hardware that will be used for high performance computing on the
System. A single computational increment (a “Computational Node”) will be capable of operating
independently of the rest of the Computational Nodes in the System.
The local storage of the Computational
Node will be the high
-
speed initial target for computational results (“Scratch”). The Computation Component
will grow incrementally over the lifetime of the System through additional procurement of nodes. The System
w
ill not necessarily be homogenous; there will eventually be some portion of nodes with higher RAM, additional
local storage, higher cores, or GPU/MIC availability. The initial goal is for base
-
level general
-
purpose
computational functionality, but the syst
em will grow to fill more diverse needs over time.


The Storage Component includes network storage that will be used as the large
-
scale data storage for the
System. The local cache of the Computational Nodes will be the initial target for computational re
sults
(“Scratch”) with the large
-
scale storage providing more durable storage for research data. A single storage
increment (a “Storage Node”) will be capable of operating independently of the rest of the Storage Nodes in the
System. Storage Nodes will be
added to the System in pairs to enable data redundancy.


For both computational and storage hardware,
the University is seeking
“general purpose” hardware as
opposed to hardware with a sp
ecialized or narrow use case.
The purpose of this Category within th
e System is
to be
utilized by the Virtualization category C
omponent in order to provide computational
and storage
services
to researchers.



3.2.1 Computation Hardware


3
.2
.1.1 Incremental Expansion


Computational Nodes must be able to be added to the System incrementally over the lifetime of the System.
These increments should be able to include innovations in computer hardware without necessitating the
construction of a new System. The increments o
f expansion must be described in detail, including (but not
limited to) any additional resources that would be required to expand by one or more increments. Assuming
that the initially purchased system was at capacity, describe in detail the minimum subse
quent increment of
growth, and describe the requirements of expanding the system by: 1 node, 10 nodes and 30 nodes (
costs for
these items to be included in Section 5 along with parts lists and hardware details in the referenced
Appendices; see Section 5 f
or more information
).


3
.2
.1.2 High Speed Networking


Computational Nodes will be connected to each other and the Storage
servers

via high speed networking
(>
=
1
0
Gb). Due to potential interoperability issues with existing hardware,
Ethernet and
10GBASE
-
T

p
hysical
port is preferred.
However, if the Offeror
’s solution uses alternative networking technology
, then
hardware with
equivalent or superior bandwidth characteristics will be acceptable. In any regard t
he nodes should also have

a

1GbE
-
compatible
networ
k interface
for management purposes

and legacy connectivity
.


R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
14

of
50


3
.2
.1.3 Local Storage


Computational Nodes must have local storage to act as a high
-
speed target of local computation (“Scratch”).


3
.2
.1.4 Node Hardware Options


Computational Nodes should be available in different configurations. The System may include the following
types of Computational Nodes: Intel Node, AMD Node, MIC Node, GPU Node, High RAM Node, High Local
Disk Size, High Network Bandwidth Node. The configu
ration options (to the extent possible) should be flexible

and interoperable
. A detailed description of each type of available node should be available.


3
.2
.1.5 Virtualization
-
ready

Computational Nodes should be “Virtualization
-
ready” with CPU Architectu
res that support full Virtualization
(VT
-
x extensions for Intel, AMD
-
V extensions for AMD).


3
.2
.1.6 Hardware Management Tools


Computational Nodes should be manageable via a networked software tool.


3
.2
.1.7 Datacenter Requirements

Computational Nodes

will be
installed

into

standard data center equipment

racks

and must come with all
necessary hardware for installation (rack rails, etc)
.
If the proposed equipment requires non
-
standard racks or
rack hardware, then the Offeror must include those materials (and their cost) in this proposal.
The University
will supply

racks and

electrical power (208 volts, three
-
phase, or 110 volts single
-
phas
e).


3.2.2 Storage Hardware


3.2.2.1 Incremental Expansion


Storage must be able to be added to the System incrementally over the lifetime of the System. These
increments should be able to include innovations in computer hardware without necessitating th
e construction
of a new System. The increments of expansion must be described in detail, including (but not limited to) any
additional resources that would be required to expand by one or more increments. For example, if the raw
storage would require sto
rage head hardware to be usable, this additional equipment should be included.
Assuming that the initially purchased system was at capacity, describe in detail the minimum subsequent
increment of growth, and describe the requirements of expanding the syste
m by: 1 increment, 10 increme
nts
and 30 increments
(costs for these items to be included in Section 5

along with parts lists and hardware details
in the referenced Appendices; see Section 5 for more information
).


3.2.2.2 High Speed Networking


Storage
Nodes

will be connected to each other and the Compute Nodes via high speed networking (>=10Gb).
Due to potential interoperability issues with existing hardware, Ethernet and 10GBASE
-
T physical port is
preferred. However, if the Offeror’s solution uses alt
ernative networking technology, then hardware with
equivalent or superior bandwidth characteristics will be acceptable. In any regard the nodes should also have
a 1GbE
-
compatible network interface for management purposes and legacy connectivity.


3.2.2.3
Distributed Parallel Filesystem Ready


Stor
age
Nodes

must be able to be configured into a distributed parallel file system. Offeror should list the
recommended distributed parallel file
-
systems that are appropriate to use for the System

and any configurati
on
caveats associated with the use of those file
-
systems
.


3.2.2.4 Hardware Management Tools


Storage
Nodes

should be manageable via a networked software tool.
Describe the management tools
available for the storage servers.


R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
15

of
50


3.2.2.5 Datacenter Requireme
nts

Storage Nodes will be installed into standard data center equipment racks and must come with all necessary
hardware for installation (rack rails, etc). If the proposed equipment requires non
-
standard racks or rack
hardware, then the Offeror must inclu
de those materials (and their cost) in this proposal.
The University will
supply electrical power (208 volts, three
-
phase, or 110 volts single
-
phase).



3.2.3

Networking Recommendations


3.2.3
.1 Recommended Networking


Specify, in detail, the recommended networking equipment that the Compute and Storage hardware should be
used with as described in sections 3.2.1 and 3.2.2.


3.2.3
.2 Compatible Networking


Describe the networking hardware that the storage and compute
r

har
dware will be compatible with. If the
storage and compute
r

hardware is compatible with a class of networking hardware instead of a particular
model or set of models, specify what the characteristics of that class of networking is.


3.2.3
.
3

Incompatible N
etworking


Specify in detail the models or classes of networking hardware that would be considered in the same “class” as
the hardware listed above in sections 3.2.4.1 and 3.2.4.2 but yet is known to be incompatible or unusable with
the Compute and Storage

hardware listed in sections 3.2.1 and 3.2.2.



3.2.4

Professional Services & Support


3.2.4.1
Professional Services


The Offeror
will

provide professional services
for

the installation and configuration of the hardware and/or
software associated with the
Computation & Storage Component
.

The cost for such services should be
included in the price of the hardware (there will be no additional charge for installation and co
nfiguration of this
hardware). However, o
ngoing professional services
subsequent to the initial installation and configuration of
the hardware
should be available from the Offeror
over

the lifetime of the system

should the need for those
services arise
.

Describe the professional services
that will be included in the initial installation and
configuration and the subsequent/ongoing available professional services along with the

hourl
y cost(s)
associated with those
services. The hourly charge for
subsequent
/ongoing

professional services will not be
included in the cost scoring determination.



3.2.4.2

Burn
-
in and Testing


All hardware that is installed should undergo a thorough burn
-
in and testing suite. Describe the burn
-
in and
testing procedures that the
hardware will be subject to.


3.2.4.3

Hardware Support SLA


A
Hardware Replacement SLA should be available for replacement of failed hardware within a reasonable
window of time.


Describe the Hardware Replacement Schedule that will be available for the hardware
provided.


3.2.4.4

Technical Support SLA


High Quality Technical S
upport should be available

for hardware and/or services provided. Describe the
Support Schedule that will
be available for the hardware and/or services provided.


R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
16

of
50


3.2.4.5

Ongoing Training
Regular training should be available for the hardware and/or services after
the system is installed and accepted.


Describe the opportunities available (offered by the Offero
r or generally
available in the industry) for regular training on the system.


3.3

VIRTUALIZATION


The Virtualization system will bind together the hardware components and make the System available as a
shared resource for researchers. Users will be able
to log into the System and provision virtual machines
(VMs) in order to perform computational tasks. Most computational VMs are expected to be ephemeral, but
persistent VMs should also be possible. Administrative access to the System will allow systems ad
ministrators
the ability to allocate the hardware resources into “pools” for researchers to use. A researcher who purchases
“Condo” resources will have priority access to their pool of resources, but also have access to any other pools
of resources they
have been allowed access to.


3.3.1 Incremental Expansion


Virtualization must be available clearly defined growth increments. The cost to add Nodes to the Virtualization
system must be at most a one
-
time cost per node. This requirement does not apply to Support or Training
Services (see Section 3.5). The busin
ess case of research
-
funded computation is such that there will be initial
funds procured for hardware and services, but limited or no continuing funds past the end of the grant period.
The Virtualization Component pricing must meet this business requireme
nt. Describe in detail the
resource/support requirements of the expanding the Compute Nodes and
available
Storage in the system
(costs for these items to be included in Section 5).


3.3.2 Affordable Upgrade and Security Patches


The cost to upgrade

and patch

the Virtualization software must be at most a one
-
time cost per major version
upgrade.
Describe the process and requirements of system upgrades and patching.


3.3.3 Resource Pools


Computational Nodes in the System can be associated with user gr
oups into “pools” with different
characteristics and user privileges.


3.3.4 Rapid Resource Provisioning


Researchers
with access to the System must be able to self
-
provision or request provisioning of VMs for their
computational use from a user
-
friendly
user interface (with preference given to systems that include self
-
provisioning). Researchers can be granted “priority access” to resources within the System and the VMs that
are deployed into those resources will run at the highest priority on those resou
rces.


3.3.5 Network Flexibility


Virtualization will allow flexible network configuration of VMs. A VM or set of VMs may be isolated in their own
private subnet or connected to an existing network within the System.


3.3.6 Resource Prioritization by
User/Group


VMs deployed by a researcher will have a higher priority on resources that have been allocated to their group.


3.3.7 Integration with Enterprise IDM


The
Virtualization Component will use the MSU Enterprise LDAP for user groups, provisioning

and
authentication.


3.3.8 Guest OS Agnostic


The
Virtualization Component will support the usage of any modern operating system on guest VMs (including
but not limited to Linux, BSD, Windows).


R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
17

of
50


3.3.9 Ephemeral/Persistent VM Storage


The VMs

can be confi
gured with either ephemeral storage or persistent block storage.


3.3.10 VM Migration, Snapshotting and Cloning


The VM
s can be mi
grated to different
physical
Computational Component and/or Storage Component
resources if necessary. VMs can be snapshotted t
o provide a point
-
in
-
time backup of the state of the VM. VMs
can be cloned.
It would be preferred to have these functions available from a graphical user interface.


3.3.11 Image Management


The
Virtualization system should have a repository of VM
images that will be maintained by the University.
Researchers can select an existing VM image when deploying a new VM or they can upload an image of their
own into the repository.


3.3.12 Timely Installation


The system must be installed in a reasonable p
eriod of time. The Offeror should provide a sample project plan
describing the timeline of component installation, provisioning and production availability.


3.3.13
Professional Services


The Offeror will provide professional services for the installation

and configuration of the hardware and/or
software associated with the Virtualization Component. The cost for such services should be included in the
price of the software (there are no recurring charges for installation and configuration of this software
).
However, ongoing professional services subsequent to the initial installation and configuration of the hardware
should be available from the Offeror over the lifetime of the system should the need for those services arise.
Describe the professional ser
vices that will be included in the initial installation and configuration and the
subsequent/ongoing available professional services along with the hourly cost(s) associated with those
services. The hourly charge for subsequent/ongoing professional service
s will not be included in the cost
scoring determination.


3.3.14 Hardware Support SLA


If hardware is a component of the Virtualization system, a

Hardware Replacement SLA should be available for
replacement of failed hardware within a reasonable window of

time.


Describe the Hardware Replacement
Schedule that will be available for the hardware provided.



3.3.15 Technical Support SLA


High Quality Technical S
upport should be available

for hardware and/or services provided. Describe the
Support Schedule that will be available for the hardware and/or services provided.


3.3.16 Ongoing Training

Regular training should be available for the hardware and/or services after the system is inst
alled and
accepted. Describe the opportunities available (offered by the Offeror or generally available in the industry) for
regular training on the system.



3.4

NETWORKING


The Networking Component includes switches necessary to form the backbone of the
System. This network
will have to uplink to the main backbone of the MSU network; but it will provide network isolation for the
research System.


3.4.1 Incremental Expansion


Network capacity must be able to be added to the System incrementally over the
life of the System. These
increments should be able to include innovations in computer hardware without necessitating the construction
R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
18

of
50


of a new System. The increments of expansion must be described in detail, including (but not limited to) any
additional
resources that would be required to expand by one or more increments. Assuming that the initially
purchased system was at capacity, describe in detail the minimum subsequent increment of growth, and
describe the requirements of expanding the system by: 3
network devices, 20 network devices and 50 network
devices (costs for these items to be included in Section 5).


3.4.2
High Speed Networking Ports

for Compute/Storage Communication


The network switches will provide the high
-
speed connectivity (>=
10Gbps) between the System servers. Due
to potential interoperability issues with existing hardware, Ethernet and 10GBASE
-
T physical port is preferred.
However, if the Offeror’s solution uses alternative networking technology, then hardware with equivalent

or
superior bandwidth characteristics will be acceptable.


Describe the characteristics of the network system and
how they meet the requirements of the System.


3.4.3 1GbE 1000BASE
-
T for Compute/Storage Management


The network switches for
hardware

manage
ment

interfaces

must operate at a minimum of 1GbE, using
1000BASE
-
T interconnects.
Describe the hardware that will be used to accommodate this and how it is
accessible and connected to the rest of the network.


3.4.3 Uplink to Cisco Nexus 7000


The System
must be able to uplink to the core Cisco Nexus 7000 switch in the data center. This uplink should
occur at single points for each of the Communication and Management networks, isolating the bulk of the
System from the core Administrative network.

Describ
e the architecture of the network and how it connects to
the core networking switches using a high
-
level graphical diagram and accompanying narrative description.


3.4.4 Hardware Management Tools


Network
equipment

should be manageable via a software tool.
Describe the tools available for the
management of the network switches listed above.


3.4.5 Datacenter Requirements

Network equipment will be installed into standard data center equipment racks and must come wit
h all
necessary hardware for installation (rack rails, etc). If the proposed equipment requires non
-
standard racks or
rack hardware, then the Offeror must include those materials (and their cost) in this proposal.

The University
will supply electrical powe
r (208 volts, three
-
phase, or 110 volts single
-
phase).


3.4.6 Timely Installation


The system must be installed in a reasonable period of time. The Offeror should provide a sample project plan
describing the timeline of component installation, provisionin
g and production availability.


3.4.7 Profess
ional Services


The Offeror will provide professional services for the installation and configuration of the hardware and/or
software associated with the Networking Component. The cost for such services should
be included in the
price of the hardware (there are no recurring charges for installation and configuration of this hardware).
However, ongoing professional services subsequent to the initial installation and configuration of the hardware
should be availa
ble from the Offeror over the lifetime of the system should the need for those services arise.
Describe the professional services that will be included in the initial installation and configuration and the
subsequent/ongoing available professional services

along with the hourly cost(s) associated with those
services. The hourly charge for subsequent/ongoing professional services will not be included in the cost
scoring determination.



R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
19

of
50


3.4.8

Burn
-
in and Testing


All hardware that is installed should undergo

a thorough burn
-
in and testing suite. Describe the burn
-
in and
testing procedures that the hardware will be subject to.


3.4.9

Hardware Support SLA


A
Hardware Replacement SLA should be available for replacement of failed hardware within a reasonable
win
dow of time.


Describe the Hardware Replacement Schedule that will be available for the hardware
provided.


3.4.10

Technical Support SLA


High Quality Technical S
upport should be available

for hardware and/or services provided. Describe the
Support Schedule that will be available for the hardware and/or services provided.


3.4.11

Ongoing Training
Regular training should be available for the hardware and/or services after
the system is insta
lled and accepted.


Describe the opportunities available (offered by the Offeror or generally
available in the industry) for regular training on the system.




R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
20

of
50


SECTION 4: OFFEROR QUALIFICATIONS


All subsections of
Section
4 not listed in the
"Instructions

to Offerors" on page 3

require a response.
R
estate the
subs
ection number and the text immediately prior to your written response.


4.1

UNIVERSITY’S RIGHT T
O INVESTIGATE AND RE
JECT


The University may make such investigations as deemed necessary to determine the Offeror’s ability to
provide the supplies and/or services specified. The
University
reserves the right to reject a proposal if the
information submitted by, or investigation
of, the Offeror fails to satisfy the
University’s
determination that the
Offeror is properly qualified to perform the obligations of the contract.
This includes the University’s ability to
reject the proposal based on negative references.


4.2

OFFEROR QUA
LIFICATIONS


To enable the
University
to determine the capabilities of an
Offeror to provide the supplies and/or services
specified in the RFP, the Offeror shall respond to the following regarding

its ability to meet the University’s
requirements.
THE
RESPONSE, "(OFFEROR'S NAME) UNDERSTANDS AND WILL COMPLY," IS NOT
APPROPRIATE FOR THIS SECTION.


NOTE: Each item must be thoroughly addressed. Offerors taking exception to any requirements listed
in this section may be found nonresponsive or be subject to

point deductions.


4.2.1 References

Offeror shall provide a minimum of

three (3)

references that have used the services
of the type proposed in this R
FP. The references must include at least one university and/or research center

where the Offeror, prefer
ably within the last

five (5)

years, has successfully completed similar services.


At a
minimum, the Offeror shall provide the University name, the location where the services were provided, contact
person(s), customer’s telephone number, customer’s email
address, a complete description of the service type,
dates the services were provided, and quality of service provided. If the University has contracted with the
Offeror in the past, the University will use its experience with the Offeror as one of its ref
erences.


These
references may be contacted to verify Offeror’s ability to perform the contract.


The University reserves the
right to use any information or additional references deemed necessary to establish the ability of the Offeror to
perform the cond
itions of the contract.

Negative references may be grounds for proposal disqualification.


4.2.2

Company Profile and Experience

MSU seeks a supplier with experience implementing
hardware and/or services like those referenced in this RFP and meeting implementation requirements.
Offeror
shall provide documentation establishing the individual or company submitting the proposal has the

qualifications and experience to provide the supplies and/or services specified in this RFP, including, at a
minimum:



a detailed description of any similar past projects

implemented at
a
university or
research center

in
the last 5 years (also include the
current status of the project).



location of support staff and distribution center(s)


4.2.
3

Presentation/Demonstration/Interview

Offerors must be prepared to have the key personnel
assigned to this project complete a(n)
oral presentation/product demons
tration/interview

(hereinafter
referred to as a “Demo”) via teleconferencing or onsite in Bozeman, Montana. The University reserves the
right to: (1) have Demos

from only the

highest scoring Offero
r

per
C
omponent
c
ategory; (2) have Demos from
all Offerors within
8
0%

of the highest scoring Offeror

per Component category
; or (3) have
Demos

from all
Offerors who are deemed to have a passing score prior to
Demo

process

per Component category
, at the
University’s discret
ion.

The University reserves the right to re
-
score based on the result of a
Presentation/Demonstration/Interview.

R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
21

of
50


SECTION 5: COST PROPOSAL


Provide a cost proposal

listing the prices for the following Component category supplies and/or services
.


Offeror
s are not required to bid on all
Component categories
. If not bidding on a Component category
,
please enter “NO BID” in that section
.
Parts lists
and physical impact summaries
MUST be included in
Appendix D and
Hardware
specifications

MUST be attached in Appendix E.


Each Component category will be broken down into two proposals, the first of which is a hypothetical purchase
of hardware with particular specification requirements and size. The second is a set of incremental prices for
expansion of the Component category to be added onto the initial hypothetical purchase. All hardware
required to make that expansion is required to be listed, including affiliated equipment and/or software licenses
that are required for the hardware expa
nsion. The Offeror can assume that the University will be providing
power resources and datacent
er space as listed in Section 3.



Due to the fact that hardware will
vary

from vendor to vendor, it is not required that you meet the exact
hypothetical specif
ications, but
the following points of interest should be taken into account
:



The size and scale of the hypothetical system is based on the expectations of the initial purchase of this
RFP. The size and scale of the incremental expansions are based on the expectations of likely growth
patterns of the system over time.



The hypothet
ical

hardware
specifications represent performance characteristics that meet the needs of
the System.

It is not required that you meet the hypothetical system specifications exactly,
usage of
equivalent or superior individual components are acceptable,
but

it
must

meet or exceed the minimum
performance characteristics of the items listed.



Hardware that is listed in these cost sheets should
be built from the hardware increments that are
described
in Section 3
, with the component equipment part numbers

and ph
ysical impact summaries

listed in Appendix D, and those parts specifications subsequently described in detail in Appendix E
.


5.1

COMPUTATION & STORAGE COST



5.1.1 Hypothetical Computational
& Storage
Purchase

The Hypothetical Computational and Storage
Purchase would include the following:



Compute

o

320 E5
-
2650

Intel Xeon Cores

o

4GB RAM/core

o

1TB Local Storage Per Compute Node



Storage

o

120 TB Raw Storage


5.1.2 Expansion of Computational

& Storage

Purchase

Expansion will be
priced

in three
hypothetical
increm
ents. Using the same increments that were used to build
the initial system, describe the costs associated with
expanding the initial system

by the increments listed on
the cost sheet. The increments of expansion should match those listed in Section 3
, wi
th the same component
part numbers and physical impact summaries listed in Appendix D,
and those parts specifications
subsequently described in detail in Appendix E.

R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
22

of
50


5.1.3

Compute & Storage Cost Sheet

It is not expected that there will be

recurring

costs associated with hardware

(to support system requirements,
mandatory
cost
(s)

should be restricted to
the

initial purchase)
, but cost sheet areas have been provided in
case there are
recurring

license or other costs associated with ownership and oper
ation of the hardware
as
provided
by the Offeror.



The score for this section is based entirely on Grand Total Cost at the bottom
right cell
of the sheet
that

represents a sum of the initial and expansion costs for the system.





ORIGINAL CONTRACT TERM



Item

Item
Description

RFP
Section

Initial
Cost

Year 2

Year 3

Renewal
Years 4
-
10

Total
Cost of
Potential
Contract

1.

Initial Computational Hardware

Parts List: App
dx D


1
.
1

3.
2.1






2.

Expand by 16 cores

Parts List: Appdx D


1
.2

3.2.1
.1






3.

Expand by 160 cores

Parts List: Appdx D


1
.3

3.2.1
.1






4.

Expand by 480 cores

Parts List: Appdx D


1
.4

3.2.1
.1






5.

Initial Storage Hardware

Parts List: Appdx D


2
.
1

3.2
.2






6.

Expand by 4 TB

Parts List: Appdx D


2
.
2

3.2.2
.1






7.

Expand

by 40 TB

Pa
rts List: Appdx D


2
.
3

3.2.2
.1






8.

Expand by 120 TB

Parts List: Appdx D


2
.
4

3.2.2
.1






9.

Grand Total

Cost






R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
23

of
50


5.2

VIRTUALIZATION COST


5.2
.1 Hypothetical
Virtualization
Purchase

The Hypothetical Virtualization Purchase would
include the following:



Virtualization software to Manage 20 Compute Nodes and 120 TB of storage with the
requirements set forth in Section 3.


5.2
.2 Expansion of
Virtualization

Purchase

Expansion will be shown in three increments. Using the same increments that were used to build the initial
hypothetical system, describe the costs associated with
expanding the initial system

by the increments listed
on the cost sheet.
The increments of e
xpansion should match those listed in Section 3, with the same
component part numbers and physical impact summaries listed in Appendix D,
and those parts specifications
subsequently described in detail in Appendix E.


5.2.3

Virtualization Cost Sheet

It is
not expected that there will be recurring/annual costs associated with Virtualization (to support system
requirements,
mandatory
cost
(s)

should be restricted to
the

initial purchase), but cost sheet areas have been
provided in case there are recurring license or other costs associated with ownership and operation of the
Virtualization software as provided by the Offeror.


The score for this section is based entirely

on Grand Total Cost at the bottom right cell of the sheet that
represents a sum of the initial and expansion costs for the system.





ORIGINAL CONTRACT TERM



Item

Item
Description

RFP
Section

Initial
Cost

Year 2

Year 3

Renewal
Years 4
-
10

Total
Cost of
Potential
Contract

1.

Initial Virtualization Installation

Parts List: App
dx D


3
.
1

3.
3






2.

Expand by 1 Compute Node &
4 TB Storage

Parts List: Appdx D


3.2

3.3.1






3.

Expand by 10 Compute Nodes
& 40 TB Storage

Parts List: Appdx D


3.3

3.3.1






4.

Expand by 30 Compute Nodes
& 120 TB Storage

Parts List: Appdx D


3.4

3.3.1






5
.

Grand Total

Cost






R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
24

of
50


5.3

NETWORK COST


5.3
.1 Hypothetical
Network
Purchase

The Hypothetical Network Purchase would include the following:



27
10GBASE
-
T
Network
Ports



40 Gb Uplink


5.3
.2 Expansion of Computational

& Storage

Purchase

Expansion will be shown in three increments. Using the same increments that were used to build the initial
system, describe the costs associated with
expanding the initial system

by the increments listed on the cost
sheet. The increments of expansion should match those listed in Section 3 and specified in detail in Appendix
D.


List any additional costs or considerations that would be required with the incremental expansion.


In
clude additional lines within each subcategory if necessary.


5.3.3

Network Cost Sheet

It is not expected that there will be recurring/annual costs associated with Networking hardware (to support
system requirements,
mandatory
cost
(s)

should be restricted to
the

initial purchase), but cost sheet areas have
been provided in case there are recurring license or other costs associated with ownership and operation of
the Networking hardware as provided by the Offeror.


The score for this s
ection is based entirely on Grand Total Cost at the bottom right cell of the sheet that
represents a sum of the initial and expansion costs for the system.





ORIGINAL CONTRACT TERM



Item

Item
Description

RFP
Section


Initial
Cost

Year 2

Year 3

Renewal
Years 4
-
10

Total
Cost of
Potential
Contract

1.

Initial Networking Installation

Parts List: App
dx D


4
.
1

3.
4






2.

Expand by 3 High Speed
Network Devices

Parts List: Appdx D


4.2

3.4.1






3.

Expand by 20 High Speed
Network Devices


Parts List:
Appdx D


4.3

3.4.1






4.

Expand by 50 High Speed
Network Devices


Parts List: Appdx D


4.4

3.4.1






5
.

Grand Total Cost







R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
25

of
50


SECTION 6: EVALUATION PROCESS


6.
1

BASIS OF EVALUATION


The evaluator/evaluation committee will review and evaluate the offers according to the following criteria
based
on
a total number of
2000

points

per C
omponent c
ategory
.



All categories except Client Reference Forms and the Cost Proposal will be evaluate
d based on the following
Scoring Guide. The
Cost Proposal

will be evaluated based on the formula set forth below.

References will be
evaluated on a Pass /Fail basis.


Any response that fails to achieve a minimum score per the requirements of Section
2.4.5

will be
eliminated from further consideration. A "fail" for any individual evaluation criterion may result in
proposal disqualification at the discretion of the procurement officer.


6.1.1

Scoring Guide

In awarding points to the evaluation criteria, the

evaluator/evaluation committee
will consider the following guidelines:



Superior Response (9
5
-
100%):

A superior response is a
n exceptional reply that completely and

comprehensive
ly
meets all of the requirements of the RFP. In addition, the response may cover areas not
originally addressed within the RFP and/or include additional information and recommendations that would
prove both valuable and beneficial to the agency.


Good Respo
nse

(75
-
94
%):

A good response
clearly
meets all the requirements of the RFP and
demonstrates in a
n

unambiguous and concise manner a thorough knowledge and understanding of the
project, with no deficiencies noted.



Fair Response

(60
-
74%):

A fair respons
e minimally meets most requirements set forth in the RFP. The
Offeror demonstrates some ability to comply with guidelines and requirements of the project, but knowledge of
the subject matter is limited.


Failed Response

(59% or less):

A failed response d
oes not meet the requirements set forth in the RFP. The
Offeror has not demonstrated sufficient knowledge of the subject matter.


6.1.2

Cost Proposal Scoring Guide

In awarding points to the
Cost Proposal
, the evaluator/evaluation
committee will consider
the following guidelines:



Lowest overall cost receives the maximum allotted points. All other proposals receive a percentage of the
points available based on their cost relationship to the lowest. Example: Total possible points for cost are 200.
Offe
ror A's cost is $20,000. Offeror B's cost is $30,000. Offeror A would receive 200 points. Offeror B would
receive 134 points ($20,000/$30,000) = 67% x 200 points =
134
).


Lowest Responsive Offer Total Cost

x

Number of available points = Award Points


This Offeror's Total Cost





R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
26

of
50


6.
2

EVALUATION CRITERIA


6.2.1 Computation & Storage Component Category




Category

Section of RFP

Point Value





Responses to the Scope of Services Overview

25% of points for a possible 5
00 points





1.


Overall Goal

3.1.1

100

2.


System Expansion

3.1.2

100

3.


Condo Model

3.1.3

100

4.


Timely Installation

3.1.4

100

5.


Comprehensive Service

3.1.5

1
00






Responses to the Scope of Services

4
5
% of points for a possible
9
00

points





6.


Responses to the Computation &
Storage Scope of Services

3.2

9
00






Offeror Qualifications

10% of points for a possible 200 points





A.


References

4.2.1

P
ass
/F
ail





B.


Company Profile and Experience

4.2.2

200





Cost Proposal

20% of points for a possible 400 points





C.


Cost Proposal

5.
1

400



6.2.2 Virtualization Component Category



Category

Section of RFP

Point Value





Responses to the Scope of Services

25
% of points for a possible
5
00 points





1.


Overall Goal

3.1.1

100

2.


System Expansion

3.1.2

100

3.


Condo
Model

3.1.3

100

4.


Timely Installation

3.1.4

100

5.


Comprehensive Service

3.1.5

100






Responses to the Scope of Services

45
% of points for a possible
9
00

points





6.


Responses to the Virtualization Scope of Services

3.
3

9
00






Company Profile and

Experience

10% of points for a possible 200 points





A.


References

4.2.1

P
ass
/F
ail





B.


Company Profile and Experience

4.2.2

200

R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
27

of
50



Category

Section of RFP

Point Value





Cost Proposal

20% of points for a possible 400 points





C.


Cost Proposal

5.
2

400



6.2.3 Netw
ork
Component
Category



Category

Section of RFP

Point Value





Responses to the Scope of Services

25
% of points for a possible
5
00 points





1.


Overall Goal

3.1.1

100

2.


System Expansion

3.1.2

100

3.


Condo Model

3.1.3

100

4.


Timely Installation

3.1.4

100

5.


Comprehensive Service

3.1.5

100






Responses to the Scope of Services

4
5
% of points for a possible
9
00

points





6.


Responses to the Network Scope of Services

3.4

9
00






Company Profile and Experience

10% of points for a possible 200 points





A.


References

4.2.1

P/F





B.


Company Profile and Experience

4.2.2

200





Cost Proposal

20% of points for a possible 400 points





C.


Cost Proposal

5.
3

400







R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
28

of
50


APPENDIX A: STANDARD TERMS AND CONDITIONS


By submitting a response to this invitation for bid, request for proposal, limited solicitation, or
acceptance of a contract, the vendor agrees to acceptance of the following Standard Terms
and Conditions and any other provisions that are specific to this
solicitation or contract.


ACCEPTANCE/REJECTION OF BIDS, PROPOSALS, OR LIMITED SOLICITATION RESPONSES:
The
University reserves the right to accept or reject any or all bids, proposals, or limited solicitation responses,
wholly or in part, and to make awar
ds in any manner deemed in the best interest of the University. Bids,
proposals, and limited solicitation responses will be firm for 30 days, unless stated otherwise in the text of the
invitation for bid, request for proposal, or limited solicitation.


ACC
ESS AND RETENTION OF RECORDS:
The contractor agrees to provide the University, Legislative
Auditor, or their authorized agents, access to any records necessary to determine contract compliance.
(Section 18
-
1
-
118, MCA). The contractor agrees to create and r
etain records supporting the services rendered
or supplies delivered for a period of three years after either the completion date of the contract or the
conclusion of any claim, litigation, or exception relating to the contract taken by the University or t
hird party.


ALTERATION OF SOLICITATION DOCUMENT:

In the event of inconsistencies or contradictions between
language contained in the University’s solicitation document and a vendor’s response, the language contained
in the University’s original solicitati
on document will prevail. Intentional manipulation and/or alteration of
solicitation document language will result in the vendor’s disqualification and possible debarment.


ASSIGNMENT, TRANSFER AND SUBCONTRACTING:

The contractor shall not assign, transfer
or
subcontract any portion of the contract without the express written consent of the University. (Section 18
-
4
-
141, MCA.)


AUTHORITY:
The attached bid, request for proposal, limited solicitation, or contract is issued under authority
of Title 18, Montana
Code Annotated, and the Administrative Rules of Montana, Title 2, chapter 5.


COMPLIANCE WITH LAWS:

The Contractor shall, in performance of work under this contract, fully comply
with all applicable federal, state, or local laws, rules, and regulations, in
cluding but not limited to, the Montana
Human Rights Act, the Civil Rights Act of 1964, the Age Discrimination Act of 1975, the Americans with
Disabilities Act of 1990, and Section 504 of the Rehabilitation Act of 1973. Any subletting or subcontracting by

the Contractor subjects subcontractors to the same provision. In accordance with 49
-
3
-
207, MCA, the
Contractor agrees that the hiring of persons to perform this contract will be made on the basis of merit and
qualifications and there will be no discrimin
ation
based upon
race, color, religion, creed, political ideas, sex,
age, marital status, physical or mental disability, or national origin by the persons performing this contract.


CONFORMANCE WITH CONTRACT:

No alteration of the terms, conditions, delivery, price, quality, quantities,
or specifications of the contract shall be granted without the University’s prior written consent. Product or
services provided that do not conform to the contract terms, condi
tions, and specifications may be rejected and
returned at the Contractor’s expense.


DEBARMENT:

The contractor certifies, by submitting this bid or proposal, that neither it nor its principals are
presently debarred, suspended, proposed for debarment, dec
lared ineligible, or voluntarily excluded from
participation in this transaction (contract) by any governmental department or agency. If the contractor cannot
certify this statement, attach a written explanation for review by the University.


DISABILITY AC
COMMODATIONS:
The University does not discriminate on the basis of disability in
admission to, access to, or operations of its programs, services, or activities. Individuals who need aids,
R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
29

of
50


alternative document formats, or services for effective communicat
ions or other disability related
accommodations in the programs and services offered are invited to make their needs and preferences known
to this office. Interested parties should provide as much advance notice as possible.


FACSIMILE RESPONSES:
Facsimil
e responses will be accepted for invitations for bids, small purchases, or
limited solicitations ONLY if they are completely
received

by University Procurement prior to the time set for
receipt. Bids, or portions thereof, received after the due time will n
ot be considered. Facsimile responses to
requests for proposals are ONLY accepted on an
exception

basis with
prior approval

of the procurement
officer.


FAILURE TO HONOR BID/PROPOSAL:
If a bidder/offeror to whom a contract is awarded refuses to accept
the
award (PO/contract) or fails to deliver in accordance with the contract terms and conditions, the department
may, in its discretion, suspend the bidder/offeror for a period of time from entering into any contracts with the
State of Montana.


FORCE MAJEURE:

Neither party is responsible for failure to fulfill its obligations due to causes beyond its
reasonable control, including without limitation, acts or omissions of government or military authority, acts of
God, materials shortages, transportation delays,
fires, floods, labor disturbances, riots, wars, terrorist acts, or
any other causes, directly or indirectly beyond the reasonable control of the nonperforming party, so long as
such party uses its best efforts to remedy such failure or delays. A party affe
cted by a force majeure condition
shall provide written notice to the other party within a reasonable time of the onset of the condition. In no event,
however, shall the notice be provided later than 5 working days after the onset. If the notice is not pro
vided
within the 5 day period, then a party may not claim a force majeure event. A force majeure condition suspends
a party’s obligations under this contract, unless the parties mutually agree that the obligation need not be
performed because of the condit
ion.


HOLD HARMLESS/INDEMNIFICATION:
The Contractor agrees to protect, defend, and save the University,
its elected and appointed officials, agents, and employees, while acting within the scope of their duties as
such, harmless from and against all claims
, demands, causes of action of any kind or character, including the
cost of defense thereof, arising in favor of the Contractor's employees or third parties on account of bodily or
personal injuries, death, or damage to property arising out of services per
formed or omissions of services or in
any way resulting from the acts or omissions of the Contractor and/or its agents, employees, representatives,
assigns, subcontractors, except the sole negligence of the University, under this agreement.


LATE BIDS AND
PROPOSALS:
Regardless of cause, late bids and proposals will not be accepted and will
automatically be disqualified from further consideration. It shall be solely the vendor’s risk to ensure delivery at
the designated office by the designated time. Late bi
ds and proposals will not be opened and may be returned
to the vendor at the expense of the vendor or destroyed if requested.


PAYMENT TERM:

All payment terms will be computed from the date of delivery of supplies or services OR
receipt of a properly execu
ted invoice, whichever is later. Unless otherwise noted in the solicitation document,
the University is allowed 30 days to pay such invoices. All contractors will be required to provide banking
information at the time of contract execution in order to faci
litate University electronic funds transfer payments.


RECIPROCAL PREFERENCE:

The State of Montana applies a reciprocal preference against a vendor
submitting a bid from a state or country that grants a residency preference to its resident businesses. A
re
ciprocal preference is only applied to an invitation for bid for supplies or an invitation for bid for
nonconstruction services for public works as defined in section 18
-
2
-
401(9), MCA, and then only if federal
funds are not involved. For a list of states t
hat grant resident preference, see
http://gsd.mt.gov/ProcurementServices/preferences.mcpx
.


R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
30

of
50


REDUCTION OF FUNDING:
The State must terminate this contract if funds are not appropriated or

otherwise
made available to support the State's continuation of performance in a subsequent fiscal period.


(See section
18
-
4
-
313(4), MCA.)


REFERENCE TO CONTRACT:

The contract or purchase order number MUST appear on all invoices, packing
lists, packages,

and correspondence pertaining to the contract.


REGISTRATION WITH THE SECRETARY OF STATE:

Any business intending to transact business in
Montana must register with the Secretary of State. Businesses that are incorporated in another state or
country, but w
hich are conducting activity in Montana, must determine whether they are transacting business in
Montana in accordance with sections 35
-
1
-
1026 and 35
-
8
-
1001, MCA. Such businesses may want to obtain
the guidance of their attorney or accountant to determine
whether their activity is considered transacting
business.


If businesses determine that they are transacting business in Montana, they must register with the Secretary of
State and obtain a certificate of authority to demonstrate that they are in good sta
nding in Montana. To obtain
registration materials, call the Office of the Secretary of State at (406) 444
-
3665, or visit their website at
http://sos.mt.gov
.


SEVERABILITY CLAUSE:
A declaration by any court, or any other
binding legal source, that any provision of
the contract is illegal and void shall not affect the legality and enforceability of any other provision of the
contract, unless the provisions are mutually dependent.


SHIPPING:
Supplies shall be shipped prepaid
, F.O.B. Destination, unless the contract specifies otherwise.


SOLICITATION DOCUMENT EXAMINATION:

Vendors shall promptly notify University Procurement of any
ambiguity, inconsistency, or error which they may discover upon examination of a solicitation doc
ument.


TAX EXEMPTION:
Montana State University

is exempt
from Federal Excise Taxes (#81
-
6010045
).


TECHNOLOGY ACCESS FOR BLIND OR VISUALLY IMPAIRED:

Contractor acknowledges that no state
funds may be expended for the purchase of information technology equ
ipment and software for use by
employees, program participants, or members of the public unless it provides blind or visually impaired
individuals with access, including interactive use of the equipment and services, that is equivalent to that
provided to
individuals who are not blind or visually imp
aired. (Section 18
-
5
-
603, MCA.)


EIT STANDARDS:

All Vendors selling information technology equipment and software to
Montana State
University
must currently meet the WCAG 2.0 AA standards and be willing to certi
fy that the software will be in
compliance with such standards.


More information on the WCAG 2.0 AA standards can be found here:
http://www.w3.org/WAI/intro/wcag.php


TERMINATION OF CONTRACT:
Unless
otherwise stated, the University may, by written notice to the
contractor, terminate the contract in whole or in part at any time the contractor fails to perform the contract.


U.S. FUNDS:

All prices and payments must be in U.S. dollars.


VENUE:
This solic
itation is governed by the laws of Montana. The parties agree that any litigation concerning
this bid, request for proposal, limited solicitation, or subsequent contract, must be brought in the Eighteenth
Judicial District in and for the County of Gallatin
, State of Montana, and each party shall pay its own costs and
attorney fees. (Section 18
-
1
-
401, MCA.)



R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
31

of
50


WARRANTY FOR SOFTWARE:
Upon initial installation of the software, the contractor warrants that: (i) the
unmodified software will provide the features

and functions, and will otherwise conform to all published
documentation including on the contractor's website; and (ii) the media upon which the software is furnished
will be free from defects in materials and workmanship under normal use and service.


T
he parties agree that the warranties set forth above do not require uninterrupted or error
-
free operation of
hardware or services unless otherwise stated in the specifications.


These warranties are the University
’s exclusive warranties and replace all oth
er warranties or conditions,
express or implied, including, but not limited to, the implied warranties or conditions of merchantability and
fitness for a particular purpose.










































R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
32

of
50


APPENDIX B: CONTRACT











Shared
Research Computing Infrastructure

Between

Montana State University

And



TABLE OF CONTENTS

1.

Parties

2.

Effective Date, Duration and Renewal

3.

Cost Adjustments

4.

Services and/or Supplies

5.

Consideration/Payment

6.

Reserved

7.

Access and Retention of
Records

8.

Assignment, Transfer and Subcontracting

9.

Hold Harmless/Indemnification

10.

Required Insurance

11.

Compliance with Workers’ Compensation Act

12.

Compliance with Laws

13.

Disability Accommodations

14.

Registration with the Secretary of State

15
.

Intellectual Property/Ownership

16.

Patent and Copyright Protection

17.

Contract Termination

18.

Event of Breach
-

Remedies

19.

Reserved

20.

Force Majeure

21.

Waiver of Breach

22.

Conformance with Contract

23.

Liaisons and Service of Notices

24.

Meetin
gs

25.

Transition Assistance

26.

Choice of Law and Venue

27.

Tax Exemption

28.

Authority

29.

Severability Clause

30.

Scope, Amendment and Interpretation

31.

Waiver

32.

Execution

Attachment A
-

Expanded Data Security Terms

Attachment B
-

Scope of Services




R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
33

of
50



1.

PARTIES


THIS CONTRACT
,

is entered into by and between Montana
State University,

(hereinafter referred to as
“MSU” or
“the
University”),

whose addresses and phone numbers are
and
,

(hereinafter referred to as the
“Contractor”), address and Telephone (.


THE PARTIES AGREE AS FOLLOWS:


2.

EFFECTIVE DATE, DURATION, AND RENEWAL


2.1

Contract Term.

This
Contract

shall take effect on
upon contract execution

and terminate
three

year
s

thereafter
, unless terminated earlier in accordance with the terms of this
Contract.
(Section 18
-
4
-
313,
MCA)


2.2

Contract Renewal.

This
Contract

may, upon mutual agreement between the parties and
according to the terms of the existing
Contract,

be renewed in one
-
year intervals, or any interval that is
advantageous to the
University.

This
Contract,

including any renewals, may not exceed a total of

ten

(
10
)
years.


3.

COST ADJUSTMENTS


3.1 Cost Increase by Mutual Agreement.

After the contract’s initial term and if the University agrees
to a renewal, the parties may agree upon a cost increase. The University is not obligated to agree upon a
renewa
l or a cost increase. Any cost increases must be based on demonstrated industry
-
wide or regional
increases in Contractor's costs. Publications such as the Federal Bureau of Labor Statistics and the
Consumer Price Index (CPI) for all Urban

Consumers may b
e used to determine the increased value.


4.

SERVICES AND/OR SUPPLIES



<<TO BE ADDED>>


5
.

CONSIDERATION/PAYMENT


5
.1

Payment Schedule.

In consideration for the Services set forth in

Exhibit A, a
ll payment terms
will be computed from the date of acceptance of supplies or services OR receipt of a properly executed
invoice, whichever is later.



<<PMT SCHED TO BE ADDED>>



Unless otherwise noted, the University is allowed 30 days to

pay
such
invoices. All contractors may be
required to provide banking information at the time of Contract execution in order to facilitate University
electronic funds transfer payments. The Contract number MUST appear on all invoices, packing lists,
packages and
correspondence pertaining to the Contract.


5
.2

Withholding of Payment.

The
University

may withhold payments to the Contractor if the
Contractor has not performed in accordance with this
Contract.
Such withholding cannot be greater than the
additional cos
ts to the
University

caused by the lack of performance.



5
.3

Tax Exemption
.
The University is exempt from Federal Excise Taxe
s (#81
-
6010045)


R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
34

of
50



5
.4

Shipping:

Supplies shall be shipped prepaid, F.O.B. Destination, unless this Contract specifies
otherwise.


5
.5

U.S. Funds.

All prices and payments must be made in U.S. dollars.


6
.

RESERVED


7
.

ACCESS AND RETENTION OF RECORDS


7
.1

Access to Records.

The Contractor agrees to provide the
University,
State,

Legislative Auditor
or their authorized agents

access to any records necessary to determine
Contract

compliance. (Section 18
-
1
-
118, MCA)



7
.2

Retention Period.

The Contractor agrees to create and retain records supporting the services
stated in Section 4 for a period of five years after either the c
ompletion date of this
Contract
or the conclusion of
any claim, litigation or exception relating to this
Contract

taken by the
University, the
State of Montana or a
third party.


8
.


ASSIGNMENT, TRANSFER AND SUBCONTRACTING


The Contractor shall not assign,
transfer or subcontract any portion of this
Contract

without the express written
consent of the
University
State. (Section 18
-
4
-
141, MCA) The Contractor shall be responsible to the
University

for the acts and omissions of all subcontractors or agents and o
f persons directly or indirectly employed by
such subcontractors, and for the acts and omissions of persons employed directly by the Contractor.


No
contractual relationships exist between any subcontractor and the
University.


9.

HOLD
HARMLESS/INDEMNIFICATION


The Contractor agrees, to the limits of insurance as set forth in Section 1
0
, to protect, defend, and save the
University, its elected and appointed officials, agents, and employees, while acting within the scope of their
duties a
s such, harmless from and against all claims, demands, causes of action of any kind or character,
including the cost of defense thereof, arising in favor of the Contractor’s employees or third parties on account
of bodily or personal injuries, death, or da
mage to property arising out of services performed or omissions of
services or in any way resulting from the acts or omissions of the Contractor and/or its agents, employees,
representatives, assigns, subcontractors, except the sole negligence of the Unive
rsity, under this Contract.


10.

REQUIRED INSURANCE


10
.1 General Requirements.

Contractor shall maintain for the duration of this contract, at its cost and
expense, insurance against claims for injuries to persons or damages to property, including contractual liability,
which may arise from or in connection with the performance of th
e work by Contractor, agents, employees,
representatives, assigns, or subcontractors. This insurance shall cover such claims as may be caused by any
negligent act or omission.


10
.2 Primary Insurance.

Contractor's insurance coverage shall be primary i
nsurance with respect to
the University, its officers, officials, employees, and volunteers and shall apply separately to each project or
location. Any insurance or self
-
insurance maintained by the University, its officers, officials, employees, or
volunt
eers shall be excess of Contractor's insurance and shall not contribute with it.


10
.3 Specific Requirements for Commercial General Liability.
Contractor shall purchase and
maintain occurrence coverage with combined single limits for bodily injury, perso
nal injury, and property
R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
35

of
50


damage of $1,000,000 per occurrence and $2,000,000 aggregate per year to cover such claims as may be
caused by any act, omission, or negligence of Contractor or its officers, agents, representatives, assigns, or
subcontractors.


The University, its officers, officials, employees, and volunteers are to be covered and listed as additional
insureds for liability arising out of activities performed by or on behalf of Contractor, including the insured's
general supervision of Contracto
r, products, and completed operations, and the premises owned, leased,
occupied, or used.


10.4

Deductibles and Self
-
Insured Retentions.

Any deductible or self
-
insured retention must be
declared to and approved by the University. At the request of the a
gency either: (1) the insurer shall reduce or
eliminate such deductibles or self
-
insured retentions as respects the University, its officers, officials,
employees, or volunteers; or (2) at the expense of Contractor, Contractor shall procure a bond guarant
eeing
payment of losses and related investigations, claims administration, and defense expenses.


10.5

Certificate of Insurance/Endorsements.

A certificate of insurance from an insurer with a Best's
rating of no less than A
-

indicating compliance with th
e required coverages, has been received by
MSU
Procurement Services,

1
9

Montana Hall, Bozeman, MT 59717. Contractor must notify the University
immediately of any material change in insurance coverage, such as changes in limits, coverages, change in
statu
s of policy, etc. The University reserves the right to require

complete copies of insurance policies at all
times.


11.

COMPLIANCE WITH
WORKERS’

COMPENSATION ACT


Contractors are required to comply with the provisions of the Montana
Workers’

Compensation Act while
performing work for the State of Montana in accordance with sections 39
-
71
-
401, 39
-
71
-
405, and 39
-
71
-
417,
MCA. Proof of compliance must be in the form of
workers’

compensation insurance, an independent
contractor's exemption, or doc
umentation of corporate officer status. Neither the
Contractor

nor its employees
are employees of the
University.

This insurance/exemption must be valid for the entire term of
this Contract.

A
renewal document must be sent to the
MSU
-
Bozeman
Procurement
Services

19

Montana Hall, Bozeman,

MT
59717,

upon expiration.


1
2
.

COMPLIANCE WITH LAWS


The Contractor must, in performance of work under this
Contract,

fully comply with all applicable federal, state,
or local laws, rules and regulations, including the Montana Human Rights Act, the Civil Rights Act of 1964, the
Age Discrimination Act of 1975, the Americans with Disabilities Act of 1990, and Section 504 o
f the
Rehabilitation Act of 1973. Any subletting or subcontracting by the Contractor subjects subcontractors to the
same provision. In accordance with section 49
-
3
-
207, MCA, the Contractor agrees that the hiring of persons to
perform
this Contract

will be

made on the basis of merit and qualifications and there will be no discrimination
based upon
race, color, religion, creed, political ideas, sex, age, marital status, physical or mental disability, or
national origin by the persons performing
this Contract
.


1
3
.

DISABILITY ACCOMMODATIONS


The University does not discriminate on the basis of disability in admission to, access to, or operations of its
programs, services, or activities. Individuals who need aids, alternative document formats, or services for
effective communications or other disability related accommodations in the programs and services offered are
invited to make their needs and preferences


1
4
.

REGISTRATION WITH THE SECRETARY OF STATE

R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
36

of
50



Any business intending to transact business in Montana
must register with the Secretary of State. Businesses
that are incorporated in another state or country, but which are conducting activity in Montana, must determine
whether they are transacting business in Montana in accordance with 35
-
1
-
1026 and 35
-
8
-
10
01, MCA. Such
businesses may want to obtain the guidance of their attorney or accountant to determine whether their activity
is considered transacting business.


If businesses determine that they are transacting business in Montana, they must register wit
h the Secretary of
State and obtain a certificate of authority to demonstrate that they are in good standing in Montana. To obtain
registration materials, call the Office of the Secretary of State at (406) 444
-
3665, or visit their website at
http://sos.mt.gov
.


1
5
.

INTELLECTUAL PROPERTY/OWNERSHIP


15.1 Mutual Use.

Contractor shall make available to the University, on a royalty
-
free, non
-
exclusive
basis, all patent and other legal rights in or to inventions first conceive
d and reduced to practice, or created in
whole or in part under this contract, if such availability is necessary for the University to receive the benefits of
this contract. Unless otherwise specified in a statement of work, both parties shall have a roya
lty
-
free,
nonexclusive, and irrevocable right to reproduce, publish, or otherwise use copyrightable property created
under this contract. This mutual right includes (i)
all deliverables and other materials, products, modifications
that Contractor has deve
loped or prepared for the
University

under this contract; (ii) any program code, or site
-

related program code that Contractor has
created, developed, or prepared under or primarily in support of the
performance of its specific obligations under this
contract; and (iii) manuals, training materials, and
documentation. All information described in (i), (ii), and (iii) is collectively called the "Work Product".


15.2 Title and Ownership Rights.

The
University

retains title to and all ownership rights i
n all data
and content, including but not limited to multimedia or images (graphics, audio, and video), text, and the like
provided by the
University

(the "Content"), but grants Contractor the right to access and use Content for the
purpose of complying wi
th its obligations under this contract and any applicable statement of work.


15.3 Ownership of Work Product.

Contractor shall execute any documents or take any other actions
as may reasonably be necessary, or as the University may reasonably request,
to perfect the University’s
ownership of any Work Product.


15.4 Copy of Work Product.

Contractor shall, at no cost to the University, deliver to the University,
upon the University’s request during the term of this contract or at its expiration or termi
nation, a current copy
of all Work Product in the form and on the media in use as of the date of the University’s request, or such
expiration or termination.


15.5 Ownership of Contractor Pre
-
Existing Materials.

Contractor retains ownership of all

litera
ry or
other works of authorship (such as software programs and code, documentation, reports, and similar works),
information, data, intellectual property,

t
echniques, subroutines, algorithms, methods or related rights and
derivatives that Contractor owns
at the time this contract is executed or otherwise developed or acquired
independent of this contract and employed by Contractor in connection with the services provided to the
University

(the "Contractor Pre
-
existing Materials"). Contractor Pre
-
existing
Materials are not Work Product.
Contractor shall provide full disclosure of any Contractor Pre
-
Existing Materials to the
University

before its use
and to prove its ownership. If, however, Contractor fails to disclose to the
University

such Contractor Pre
-
Existing Materials, Contractor shall grant the
University

a
nonexclusive, worldwide, paid
-
up

license to use any
Contractor Pre
-
Existing Materials embedded in the Work Product to the extent such Contractor Pre
-
Existing
Materials are nec
essary for the
University

to receive the intended benefit under this contract. Such license
shall remain in effect for so long as such Pre
-
Existing Materials remain embedded in the Work Product.
R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
37

of
50


Except as otherwise provided for in
Section 15.3

or as may
be expressly agreed in any statement of work,
Contractor shall retain title to and ownership of any hardware it provides under this contract.


16.

PATENT AND COPYRIGHT PROTECTION


16.1 Third
-
Party Claim.

If a third party makes a claim against the Univers
ity that the products
furnished under this contract infringe upon or violate any patent or copyright, the University shall promptly
notify Contractor. Contractor shall defend such claim in the University’s name or its own name, as appropriate,
but at Cont
ractor's expense. Contractor shall indemnify the University against all costs, damages, attorney
fees, and all other costs and expenses of litigation that accrue as a result of such claim. If the University
reasonably concludes that its interests are not

being properly protected, or if principles of governmental or
public law are involved, it may enter any action.


16.2 Product Subject of Claim.

If any product furnished is likely to or does become the subject of a
claim of infringement of a patent or
copyright, then Contractor may, at its option, procure for the University the
right to continue using the alleged infringing product, or modify the product so that it becomes non
-
infringing. If
none of the above options can be accomplished, or if the use
of such product by the University shall be
prevented by injunction, the University will determine whether the contract has been breached.


17.

CONTRACT TERMINATION



17.1

Termination for
Cause.

The University may, by written notice to the Contractor,
terminate this
contract in whole or in part at any time the Contractor fails to perform the contract pursuant to Section 18,
Event of Breach


Remedies


17.2

Bankruptcy or Receivership.

Voluntary or involuntary Bankruptcy or rec
eivership by
Contractor may
be cause for termination.


17.3

Reduction of Funding.

The University must terminate this contract if funds are not
appropriated or otherwise made available to support the University's continuation of performance of this
Contract in a subsequent fiscal per
iod. (See section 18
-
4
-
313(4), MCA.)


18.

EVENT OF BREACH


REMEDIES


18.1 Event of Breach by Contractor.

Any one or more of the following Contractor acts or omissions
constitute an event of material breach under this contract:




products

or services furnished
fail to conform to any requirement;



failure to submit any report required by this contract;



failure to perform any of the other terms and conditions of this contract, including but not limited to
beginning work under this contr
act without prior
University

approval and breaching Section 28.1
obligations; or



voluntary or involuntary bankruptcy or receivership.


18.2 Event of Breach by University.

The
University
’s failure to perform any material terms or
conditions of this contra
ct constitutes an event of breach.


18.3 Actions in Event of Breach.



Upon the Contractor’s material breach, the University may:



terminat
e this contract under section 17
; or

R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
38

of
50




treat this contract as materially breached and pursue any of its remedies
under this contract, at
law, or in equity.


Upon the University’s material breach, the Contractor

may:



terminate this contract after giving the University written notice of the stated failure. The written
notice must demand performance of the stated failu
re within a specified period of time of not
less than 30 days. If the demanded performance is not completed within the specified period,
the termination is effective at the end of the specified period; or



treat

this contract as materially breached and, except as the remedy is limited in this contract,
pursue any of its remedies under this contract, at law, or in equity.


19.

RESERVED


20.

FORCE MAJEURE


Neither party is responsible for failure to fulfill its obl
igations due to causes beyond its reasonable control,
including without limitation, acts or omissions of government or military authority, acts of God, materials
shortages, transportation delays, fires, floods, labor disturbances, riots, wars, terrorist ac
ts, or any other
causes, directly or indirectly beyond the reasonable control of the nonperforming party, so long as such party
uses its best efforts to remedy such failure or delays. A party affected by a force majeure condition shall
provide written not
ice to the other party within a reasonable time of the onset of the condition. In no event,
however, shall the notice be provided later than 5 working days after the onset. If the notice is not provided
within the 5 day period, then a party may not claim

a force majeure event. A force majeure condition suspends
a party’s obligations under this contract, unless the parties mutually agree that the obligation is excused
because of the condition.


21.

WAIVER OF BREACH


Either party’s failure to enforce any

contract provisions after any event of breach is not a waiver of its right to
enforce the provisions and exercise appropriate remedies if the breach occurs again. Neither party may assert
the defense of waiver in these situations.


22.


CONFORMANCE WITH CONTRACT


No alteration of the terms, conditions, delivery, price, quality, quantities, or specifications of the contract shall
be granted without Montana State University Procurement Services prior written consent. Product or services
p
rovided that do not conform to the contract terms, conditions, and specifications may be rejected and returned
at Contractor’s expense.


23.

LIAISONS AND SERVICE OF NOTICES


23.1 Contract Liaisons.

All project management and coordination on the
University’s behalf must be
through a single point of contact designated as the University’s liaison. Contractor shall designate a liaison
that will provide the single point of contact for management and coordination of Contractor's work. All work
perfor
med under this contract must be coordinated between the University’s liaison and Contractor's liaison.


The University's liaison will be:


The Contractor's liaison will be:


23.2 Notifications.

The University’s liaison and Contractor's liaison may be cha
nged by written notice
to the other party. Written notices, requests, or complaints must first be directed to the liaison. Notice may be
R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
39

of
50


provided by personal service, mail, or facsimile. If notice is provided by personal service or facsimile, the
notice

is effective upon receipt; if notice is provided by mail, the notice is effective within three (3) business
days of mailing. A signed and dated acknowledgement of the notice is required of both parties.


23.3 Identification/Substitution of Personnel.

The personnel identified or described in Contractor's
proposal shall perform the services provided for the University under this contract. Contractor

agrees that any
personnel substituted during the term of this contract must be able to conduct the requir
ed work to industry
standards and be equally or better qualified than the personnel originally assigned. The
University

reserves
the right to approve Contractor personnel assigned to work under this contract and any changes or
substitutions to such person
nel. The
University
’s approval of a substitution will not be unreasonably withheld.
This approval or disapproval shall not relieve Contractor to perform and be responsible for its obligations under
this contract. The
University

reserves the right to req
uire Contractor personnel replacement. If Contractor
personnel become unavailable, Contractor shall provide an equally qualified replacement in time to avoid
delays to the work plan.


24.

MEETINGS


24.1 Technical or Contractual Problems.

Contractor shal
l meet with the University’s personnel, or
designated representatives, to resolve technical or contractual problems occurring during the contract term or
to discuss the progress made by
Contractor

and the
University

in the performance of their respective
obligations
, at no additional cost to the University. The University may request the meetings as problems arise
and will be coordinated by the University. The University shall provide Contractor a minimum of three
full
working days notice of meeting date, time, and location. Face
-
to
-
face meetings are desired; however, at
Contractor's option and expense, a conference call meeting may be substituted. Contractor’s consistent failure
to participate in problem resoluti
on meetings, Contractor missing or rescheduling two consecutive meetings, or
Contractor’s failure to make a good faith effort to resolve problems may result in termination of the contract.



24.2 Progress Meetings.

During the term of this contract, the
U
niversity
’s Project Manager shall plan
and schedule progress meetings with Contractor to discuss Contractor’s and the
University
’s progress in the
performance of their respective obligations. These progress meetings will include the
University

Project
Man
ager, the Contractor Project Manager, and any other additional personnel involved in the performance of
this contract as required. At each meeting, Contractor shall provide the
University

with a written status report
that identifies any problem or circums
tance encountered by Contractor, or of which Contractor gained
knowledge during the period since the last such status report, which may prevent Contractor from completing
any of its obligations or may generate charges in excess of those previously agreed t
o by the parties. This
may include the failure or inadequacy of the
University

to perform its obligation under this contract. Contractor
shall identify the amount of excess charges, if any, and the cause of any identified problem or circumstance
and the
steps taken to remedy the same.


24.3 Failure to Notify.

If Contractor fails to specify in writing any problem or circumstance that
materially affects the costs of its delivery of services or products, including a material breach by the
University
,
about

which Contractor knew or reasonably should have known with respect to the period during the term
covered by Contractor's status report, Contractor shall not be entitled to rely upon such problem or
circumstance as a purported justification for an increase

in the price for the agreed upon scope.


24.4 University's Failure or Delay.

For a problem or circumstance identified in Contractor's status
report in which Contractor claims was the result of the
University
's failure or delay in discharging any
University

obligation, the
University

shall review same and determine if such problem or circumstance was in fact the
result of such failure or delay. If the University agrees as to the cause of such problem or circumstance, then
the parties shall extend
any deadlines or due dates affected thereby, and provide for any additional charges by
Contractor. This is Contractor’s sole remedy. If the
University

does not agree as to the cause of such problem
R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
40

of
50


or circumstance, the parties shall each attempt to resolv
e the problem or circumstance in a manner satisfactory
to both parties.


25.

TRANSITION ASSISTANCE


If this contract is not renewed at the end of this term, if the contract is otherwise terminated before project
completion, or if particular work on a
project is terminated for any reason, Contractor shall provide transition
assistance for a reasonable, mutually agreed period of time after the expiration or termination of this contract
or particular work under this contract. The purpose of this assistan
ce is to allow for the expired or terminated
portion of the services to continue without interruption or adverse effect, and to facilitate the orderly transfer of
such services to the University or its designees. The parties agree that such transition ass
istance is governed
by the terms and conditions of this contract, except for those terms or conditions that do not reasonably apply
to such transition assistance. The University shall pay Contractor for any resources utilized in performing such
transition

assistance at the most contract current rates. If the University terminates a project or this contract for
cause, then the University may offset the cost of paying Contractor for the additional resources Contractor
utilized in providing transition assist
ance with any damages the University may have sustained as a result of
Contractor’s breach.


26.

CHOICE OF LAW AND VENUE


Montana law governs this contract. The parties agree that any litigation concerning this bid, proposal, or this
contract must be brou
ght in the Eighteenth Judicial District of the State of Montana, in the County of Gallatin,
State of Montana, and each party shall pay its own costs and attorney fees. (18
-
1
-
401, MCA.)



27.

TAX EXEMPTION



Montana State University is exempt from Federal

Excise Taxes (#81
-
6010045).


28.

AUTHORITY


This contract is issued under authority of Title 18, Montana Code Annotated, and the Administrative Rules of
Montana, Title 2, chapter 5.


29.

SEVERABILITY CLAUSE


A declaration by any court or any other bindi
ng legal source that any provision of the contract is illegal and void
shall not affect the legality and enforceability of any other provision of the contract, unless the provisions are
mutually and materially dependent.


30.

SCOPE, ENTIRE AGREEMENT, AND

AMENDMENT


30.1 Contract.

This contract consists of

XX

numbered pages, an
y At
tachments as required, RFP 14
-
05
, as amended, and Contractor's response, as amended. In the case of dispute or ambiguity arising between
or among the documents, the order of precedence of document interpretation is the same.


30.2 Entire Agreement.

These documents are the entire agr
eement of the parties. They supersede
all prior agreements, representations, and understandings. Any amendment or modification must be in a
written agreement signed by the parties.


31.

WAIVER


R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
41

of
50


The University's waiver of any Contractor obligation or respo
nsibility in a specific situation is not a waiver in a
future similar situation or is not a waiver of any other Contractor obligation or responsibility.


32
.

EXECUTION


The parties through their authorized agents have executed this Contract on the dates se
t out below.


MONTANA STATE UNIVERSITY




CONTRACTOR



BY: _______________________________


BY:
___________________________

(Name/Title)







(Name/Title)


BY: ___
_________________________
__


BY: ______
_____________________



(Signature)







(Signature)



DATE: _____________________________


DATE: ___
______________________



Approved as to Legal Content:








____________
_________________________



MSU Legal Counsel




(Date)



(Required for purchases over $25,000)








Approved as to

Form
:





____________
_________________________



Brian O’Connor



(Date)

Director of Procurement

(Required for purchases over $25,000)



















R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
42

of
50


ATTACHMENT A: EXPANDED

DATA SECURITY TERMS


Confidential Data Protection, Privacy, and Ownership:
Service
Provider must abide by the limitations on
information disclosure set for
th

in The Family Educational Rights and Privacy Act (FERPA),
(
34 CFR § 99.33
(a) (2))
and wi
th the terms set forth below.
34 CFR 99.33 (a)

(2) states that the officers, employees and
agents of a party that receives education record information from the Institution may use the
information, but only for the purposes for which the disclosure was made. Service Provider must also
abide by
other applicable laws such as The Health Insurance
Portability and Accountability Act (HIPPA) or
The Gramm
-
Leach
-
Bliley Act (GLB).

Definitions:

Service Provider

refers to the contractor named in this agreement
.

Institution
&

MSU

refer to Montana State University
.

Covered data and information (CDI)

includes

paper and electronic student education record information
supplied by Institution, as well as any data provided by Institution’s students to the Service Provider.

Personally Identifiable Information (PII)

includes student records, social security numbers,

or any other
information that can be used to identify, contact, or locate a single person.

Acknowledgment of Access to CDI

and/or

PII
:


Service Provider acknowledges that the Agreement allows
the Service Provider access to CDI

and/or PII
.


Prohibition on Unauthorized use or disclosure of CDI and PII:
If solution requires access to CDI and/or
PII, Service Provid
er shall not use or disclose such data

received from or on behalf of the Institution (or its
students) except as permitted or requir
ed by the Agreement, as required by law, or as otherwise authorized in
writing by Institution. Service Provider agrees not to use CDI
/PII

for any purpose other than the purpose for
which the disclosure was made. These measures will be extended by contrac
t to all subcontractors used by
Service Provider.


Maintenance of the security of electronic information:

If solution requires that Service Provider is given
access to and will be storing CDI/PII, Offeror must hold CDI/PII in strict confidence and must
use appropriate
security measures to preserve the confidentiality, integrity, and availability of all such data. All sessions
transmitting
CDI/PII

must be protected with minimum encryption levels of AES 256 or RSA 1024. Service
Provider must disclose whi
ch data elements (student ID #, name, contact information, etc.) are being stored in
the solution. Service Provider must employ data backup scheme and restore procedures and security controls
in the server and database environment used to store
CDI/PII
. S
ervers holding such data must be
appropriately secured and maintained (physical security, updates, backups, uptime requirements, monitoring,
etc.). CDI/PII must be encrypted at rest and segregated from other data.

Service Provider

must maintain

third
-
par
ty data center audit compliance to a standard such as SAS 70 or SSAE 16.


Return or Destruction of CDI/PII
: Upon termination, cancellation, expiration or other conclusion of the
Agreement, Service Provider must return, purge, and confirm purging of all Ins
titutional data, CDI/PII or
otherwise.




Remedies:
If the Institution reasonably determines in good faith that Service Provider has materially breached
any of its obligations under this contract, the Institution, in its sole discretion, shall have the rig
ht to require
Service Provider to submit to a plan of monitoring and reporting; provide Service Provider with a fifteen (15)
day period to cure the breach; or terminate the Agreement immediately if cure is not possible.


Before
R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
43

of
50


exercising any of these opt
ions, the Institution shall provide written notice to Service Provider describing the
violation and the action it intends to take. If the Family Policy Compliance Office of the U.S. Department of
Education determines that the Service Provider improperly di
sclosed personally identifiable information
obtained from the Institution’s education records, the Institution may not allow the Service Provider access to
education records for at least five years.


Reporting of Unauthorized Disclosures or Misuse of Cover
ed Data and Information:

Service Provider
shall, within one day of discovery, report to the Institution any use or disclosure of CDI/PII not authorized by
this agreement or in writing by Institution. Service Pro
vider’s report shall identify:
(i) the nature

of the
unauthorized use or disclosure, (ii) the CDI/PII used or disclosed, (iii) who made the unauthorized use or
received the unauthorized disclosure, (iv) what Service Provider has done or shall do to mitigate any
deleterious effect of the unauthorized
use or disclosure, and (v) what corrective action Service Provider has
taken or shall take to prevent future similar u
nauthorized use or disclosure.
Service Provider shall provide
such other information, including a written report, as reasonably requested

by Institution.


Contractor’s Responsibilities:

The Contractor may design, test, and operate all software on equipment
owned by MSU, using reasonable care to safeguard all software and equipment owned by MSU. All software
programs, including source code a
nd other program specific technology, including system designs, written or
changed by the contractor, are owned by MSU, but the Contractor owns all programming
techniques.


Distribution by the Contractor of programs developed under this contract or any der
ivative thereof
is prohibited unless agreed to in writing by MSU.






Indemnity:
Service Provider shall defend and hold Institution harmless from all claims, liabilities, damages, or
judgments involving a third party, including Institution’s costs and at
torney fees, which arise as a result of
Service Provider’s failure to meet any of its obligations under this agreement.




R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
44

of
50


ATTACHMENT B: SCOPE OF SERVICES


The Scope of Services
is

as stated in the RFP and Contractor’s response in addition to the clarifications below: The RFP
numbered section is cross referenced for consistency.

All numbers that are not included here are as stated and
responded to in the RFP.


<<TO BE ADDED>>

3.
3

IMPLEMENTATION PLAN



<<TO BE ADDED>>


3.4

TRAINING AND DOCUMENTATION


<<TO BE ADDED>>


3.5

ACCEP
TANCE PLAN CRITERIA AND PROCESS


<<TO BE ADDED>>


3.6

MAINTENANCE AND SUPPORT:


<<TO BE ADDED>>





























R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
45

of
50


APPENDIX C: RFP RESPONSE FORM



1.

Offeror must provide a signed copy of the RFP Cover Sheet.


2.

Offeror
must include the "Instructions to Offerors" page.


OFFEROR MUST PROVIDE

THE FOLLOWING INFORM
ATION THAT WILL BE E
VALUATED BY THE RFP
EVALUATOR/EVALUATION

COMMITTEE:


3
.

Scope of
Services and System

(Section 3).


4.

Offeror Qualifications

(Section 4.2)


5
.

Cost Proposal (Section 5.0).


6
.

Completeness of Proposal.

An
Offeror
's response must be complete at the time of submittal and
contain all the reference materials necessary to p
rovide a complete response to the RFP.


Unless
specifically requested in the RFP, a
n

Offeror

making the statement "Refer to our literature…" or "Please
see www…….com" may be deemed nonresponsive or receive point deductions.

If making reference to
materials located in another section of the RFP response, specific page numbers and sections must be
noted.


The Evaluator/Evaluation Committee is not required to search through literature or
another section of the proposal to find a response.


7
.

Copies
Required and Deadline for Receipt of Proposals.

Offerors must submit
one original
proposal
and
1

copy

to the University Purchasing Office.
In
addition, Offerors must submit
one

electronic copy

on
compact disc (CD) or universal serial bus (USB) flash drive

in Microsoft Word or
portable document format (PDF)

as a single file format
. Please submit the proposal as one file on the
electronic devices. If any confidential materials are included in accordance with the requirements of
Section 2.3.2, they must be
submitted on a separate CD or USB flash drive.


EACH PROPOSAL MUST B
E SEALED AND LABELED

ON THE OUTSIDE OF TH
E PACKAGE

clearly indicating it is in response to
Proposals must be receiv
ed at the reception desk of Montana
State University Purchasing

prior to
2:00 p.m., Mountain
Time,

December 6
, 2013.

Offeror is
solely responsible for assuring delivery to the reception desk by the designated

time.

Facsimile
or electronic submissions are not acceptable.


PHYSICAL AND MAILING ADDRESS:

Montana State
University
-
Bozeman

Procurement Services

19

Montana Hall
, PO

Box 172600

Bozeman, MT. 59717
-
2600








R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
46

of
50


APPENDIX

D
:

Cost Sheet Parts List


In as many pages as required, please list the
parts for each of the Cost Sheet items. Additionally, summarize
the
physical impact of the p
arts (in aggregate) in the table provided. The physical impact should be total for
the parts listed for the subsection. Parts should be listed one per line with a part name.

Each part should be
listed with detailed specifications
in Appendix E.


The intention of
this
Appendix is to

give the Committee a clear
understanding of the
component

hardware

items that are associated with initial implementation and expansion of the system.



Add additional rows or pages as necessary to
list a
ll of the parts necessary.


AD


1

COMPUTATION & STORAG
E PARTS



AD


1.
1
Initial Computational Hardware


Physical Impact Summary

(total for the parts listed below)

Rack Units

Watts

Amps

BTU/Hr

Tons A/C







Parts List

Qty


Part Number




Part
Name










AD


1.
2
Expand by 16 cores


Physical Impact Summary

(total for the parts listed below)

Rack Units

Watts

Amps

BTU/Hr

Tons A/C







Parts List

Qty


Part Number




Part
Name










AD


1.
3
Expand by 160 cores


Physical Impact Summary

(total for the parts listed below)

Rack Units

Watts

Amps

BTU/Hr

Tons A/C







Parts List

Qty


Part Number




Part
Name












AD


1.
4
Expand by 480 cores


Physical Impact Summary

(total for the parts listed below)

Rack Units

Watts

Amps

BTU/Hr

Tons A/C






R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
47

of
50



Parts List

Qty


Part Number




Part
Name










AD


2.
1
Initial Storage Hardware


Physical Impact Summary

(total for the parts listed below)

Rack Units

Watts

Amps

BTU/Hr

Tons A/C







Parts List

Qty


Part Number




Part
Name












AD


2.
2
Expand by 4 TB


Physical Impact Summary

(total for the parts listed below)

Rack Units

Watts

Amps

BTU/Hr

Tons A/C







Parts List

Qty


Part Number




Part
Name










AD


2.
3
Expand by 40 TB


Physical Impact Summary

(total for the parts listed below)

Rack Units

Watts

Amps

BTU/Hr

Tons A/C







Parts List

Qty


Part Number




Part
Name












AD


2.
4
Expand by 120 TB


Physical Impact Summary

(total for the parts listed below)

Rack Units

Watts

Amps

BTU/Hr

Tons
A/C







Parts List

Qty


Part Number




Part
Name









AD


3.
1
Initial Virtualization Installation


Physical Impact Summary

(total for the parts listed below)

Rack Units

Watts

Amps

BTU/Hr

Tons A/C






R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
48

of
50



Parts List

Qty


Part Number




Part
Name










AD


Expand by 1 Compute Node & 4 TB Storage


Physical Impact Summary

(total for the parts listed below)

Rack Units

Watts

Amps

BTU/Hr

Tons A/C







Parts List

Qty


Part Number




Part
Name












AD


Expand by 10 Compute Nodes & 40 TB
Storage


Physical Impact Summary

(total for the parts listed below)

Rack Units

Watts

Amps

BTU/Hr

Tons A/C







Parts List

Qty


Part Number




Part
Name










AD


Expand by 30 Compute Nodes & 120 TB Storage


Physical Impact Summary

(total for the parts listed below)

Rack Units

Watts

Amps

BTU/Hr

Tons A/C







Parts List

Qty


Part Number




Part
Name










AD


4.
1
Initial Networking Installation


Physical Impact Summary

(total for the parts listed below)

Rack Units

Watts

Amps

BTU/Hr

Tons A/C







Parts List

Qty


Part Number




Part
Name










AD


Expand by 3 High Speed Network Devices



Physical Impact Summary

(total for the parts listed below)

Rack Units

Watts

Amps

BTU/Hr

Tons A/C

R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
49

of
50








Parts List

Qty


Part Number




Part
Name










AD


Expand by 20 High Speed Network Devices


Physical Impact Summary

(total for the parts listed below)

Rack Units

Watts

Amps

BTU/Hr

Tons A/C







Parts List

Qty


Part Number




Part
Name










AD


Expand by 50 High Speed
Network Devices


Physical Impact Summary

(total for the parts listed below)

Rack Units

Watts

Amps

BTU/Hr

Tons A/C







Parts List

Qty


Part Number




Part
Name












R
FP#14
-
0
5
Shared Research Computing Infrastructure

Dept.: ITC


Page
50

of
50


APPENDIX E: PART SPECIFICATIONS



In as many pages as required, please
attach

the detailed specifications for
each of the parts listed in Appendix
D.
The intention of this Appendix is to give the Committee a clear and detailed understanding of the specific
hardware that the vendor intends to provide as a solution for the requiremen
ts of Section 3 along with the
pricing for Section 5.


Add
as many pages as necessary to list the detailed specifications for each part number.


Part Number




Part
Specifications