Indiana University HPC Scratch File System IU …...F. Statement of Needs 12 G. Terms and Conditions 17 H. Proposal Response 22 Appendix A. Non-Collusive Certificate 25 Appendix B

IUP RFP-TEC-295-2020 Indiana University HPC Scratch File System Refresh

1

Request for Proposal

For

Indiana University HPC Scratch File System IU Pervasive Technology Institute

Final Response due no later than 05:00 PM (Eastern Time) on 05/22/2020

Issued by: Jennifer Guynn Purchasing Contract Manager Indiana University 1000 Waterway Blvd., Suite 101 Indianapolis, Indiana 46202 Issued: May 1st, 2020


2

Section A: Table of Contents Section Topic Page A. Table of Contents 2 B. Purpose 2 C. Background 3 D. Proposal Instructions & Conditions 9 E. Schedule of Events 11 F. Statement of Needs 12 G. Terms and Conditions 17 H. Proposal Response 22 Appendix A. Non-Collusive Certificate 25 Appendix B. Supplier Diversity Information 26 Appendix C. Minimum Insurance Requirements 28 Appendix D. Federal Debarment Certification 32 Section B: Purpose Indiana University (IU) is requesting proposals from firms interested in providing research cyberinfrastructure (CI) file systems in support of high-performance computing, as specified herein. The intent of this Request for Proposal (RFP) and the ensuing process is to provide companies with the information, requirements, and specifications necessary for the preparation of a professional and comprehensive proposal. Specific terms and conditions are outlined. Selection of one or more successful Supplier(s) will be based upon a variety of factors such as, but not limited to:

• Ability to meet statement of needs and technical specifications as specified in Section F1 • Ability to meet scope of work as specified in Section F2 • Total cost of ownership (TCO), including but not limited to:

o Price of system and installation o Efficiency of the proposed solution o Long-term cost of support and maintenance.

• References • Acceptance of terms & conditions • Opportunities for future partnerships as indicated in Section F3 in:

o Research and Development o Education and Outreach o Economic Development

These criteria have been listed in order of importance. As used within this RFP, “Participant” shall refer to those companies receiving and responding to this RFP. “Supplier” shall refer to the successful Participant of the process. “University” shall refer to Indiana University.


3

Section C: Background Founded in 1820, Indiana University (IU) is a public, multi-campus, three-billion-dollar educational institution with undergraduate and graduate students exceeding 114,000. All 50 states, Washington, D.C., three U.S. territories and over 150 foreign countries are represented. It has an additional 23,000 faculty and staff body that supports the educational mission of the institution. IU spans the state with eight campuses. For more general information about the institution, please visit the institution’s home page at http://www.indiana.edu and its fact book at http://factbook.indiana.edu/. The mission of Research Technologies (RT), a division of IU’s University Information Technology Services and a Pervasive Technology Institute, is simple: Enable and Support research at IU. RT develops, delivers, and supports advanced technology solutions that enable new possibilities in research, scholarly endeavors, and creative activity at Indiana University and beyond. Reducing the barriers for all to use IU’s advanced cyberinfrastructure (CI) is a core component of RT’s service delivery. From students using virtual reality goggles for the first time to IU medical researchers trying to solve some of humankind’s most pressing problems, Research Technologies at Indiana University is there to support the basic and the most complex scientific and educational challenges with sophisticated tools, powerful high-performance computing resources, and talented, supportive people. RT provides services that benefit fields ranging from astronomy to zoology and has developed a new suite of systems and services to address the needs of disciplines like the arts, cinema, humanities, and recreation. Services range from software consulting and workshops to computing and creating new software tools that meet researchers’ needs wherever they are, and at whatever technical grasp they may have. RT complements these efforts with education and technology translation activities to improve the quality of life for people in the community, state, the nation, and the world. Indiana University has provided high performance computing systems and storage for research since the 1950s. As data for the University continues to grow UITS/RT plans to provide storage services to meet this need. The major systems in our current CI environment are as follows: Data Storage Systems (filesystems and archive) In addition to the locally attached storage listed below within the HPC systems, IU has three major disk-based file systems and one archival storage system that serve local and remote users. These include:

• Slate and Slate-Project [disk-based]. Developed in partnership with DDN, Slate and Slate Project are two high-speed/high-bandwidth Lustre storage systems mounted on the high-performance computing systems at IU. They were designed to serve the persistent storage needs of individual researchers and larger collaborative projects, respectively.

http://www.indiana.edu/

http://factbook.indiana.edu/


4

The file systems run Lustre with ZFS to leverage its many features (block level integrity, online data scrubbing, online data compression, etc.) and unlike other DDN solutions are constructed from scalable building blocks. Each object storage building block consists of 2 servers and 2 disk enclosures providing approximately 1PB of raw storage and (2) 100-gigabit EDR connections. Slate consists of 4 such building blocks, providing a usable size of 3.6 PB and a measured aggregate write performance of 64 GB/s. Slate Project consists of 8 building blocks and provides 7.2 PB usable PB of storage and a measured aggregate write performance of 81 GB/s. Both Slate and Slate Project use an active-active configuration of two metadata servers running Lustre’s distributed namespace code (DNE-1) backed by SSDs and connected to the switch fabric by 100-gigabit EDR connections.

• Data Capacitor II [disk-based]. Data Capacitor II is a high-speed/high-bandwidth Lustre

storage system that provides short to mid-term storage for the high-performance computing systems at Indiana University Bloomington. Installed in February 2013, DCII includes a 7.56 PB Lustre file system (5.3 PB usable) from Data Direct Networks (DDN), with an aggregate 48 GB/s of data I/O capability. DCII includes 16 Lustre object storage servers, two Lustre metadata servers, and eight Lustre routers, all connected via 56-gigabit FDR InfiniBand to two DDN SFA12000 storage controllers. The Lustre routers also have bonded 10-gigabit Ethernet connections to allow systems without InfiniBand to access the system with an aggregate throughput of 160 Gbps. The two metadata servers are backed by a DDN SFA7700 storage controller.

• Data Capacitor Wide Area Network (DC-WAN) [disk-based]. The DC-WAN file system

is a high-speed/high-bandwidth Lustre storage system for research computing that serves all IU campuses and other sites across the country, primarily by wide area network (remote) Lustre file system mounts. DC-WAN has a total formatted capacity of 1.1 PB and 160 Gbps maximum I/O. DC-WAN consists of six Supermicro servers running the Lustre file system backed by ZFS. DC-WAN has four servers used for object storage equipped with 40-gigabit Ethernet cards, and two used for Lustre metadata that use 10-gigabit Ethernet. DC-WAN allows systems outside of the data center to access DC-WAN as though it were local, using the IU-developed nodemap feature to allow machines to maintain appropriate ownership and permissions across different administrative domains. IU provides wide area file system connections for over 10 collaborators and facilities.

• Geode [disk-based]. A Lenovo disk storage solution that uses IBM’s Spectrum Scale,

Geode provides 7.2PB of raw (3.6PB usable/replicated) storage that is asynchronously mirrored between Bloomington and Indianapolis campuses for high availability. This environment provides home directory space for IU’s HPC systems with GPFS native clients. Using the Samba, mapped drive, interface users are also using this storage for desktop access across campus. Geode also provides condo project storage, storage that is departmentally purchased. The system is integrated with the campus Active Directory to leverage existing permission schemes in those departments.

• Scholarly Data Archive (SDA) [tape-based]. SDA uses the High-Performance Storage

System (HPSS) software to make available to IU researchers a total storage capacity


5

exceeding 150PB. Data are written to a fast, front-end disk cache (2.2PB raw) and migrated over time to IBM TS3500 tape libraries on the Bloomington and Indianapolis campuses. Data written to IU’s HPSS system are copied synchronously to both locations, providing highly reliable disaster protection. Users can access data over the network from central research systems or from personal workstations, using SFTP, Globus, and HIS/HTAR. The default allowance per user is 50TB of mirrored data. Additional space is available at a nominal charge to the IU community.

High Performance Computing Systems

• Big Red 200. Big Red 200 is a Cray Shasta supercomputer designed to support scientific and medical research, and advanced research in artificial intelligence, machine learning, and data analytics. Installed at Indiana University in January 2020, Big Red 200 will enter production service during the spring 2020 semester. Big Red 200 features 672 compute nodes, each equipped with 256 GB of memory and two 64-core, 2.25 GHz, 225-watt AMD EPYC 7742 processors. An upcoming expansion will add 64 GPU-accelerated nodes, each with 512 GB of memory and four NVIDIA Tensor Core GPUs. After the expansion, Big Red 200 will have a theoretical peak performance (Rpeak) greater than 6 peta FLOPS, making it one of the fastest university-owned supercomputers in the nation. Big Red 200 runs a proprietary variant of Linux called Cray Linux Environment (CLE). In CLE, compute elements run a lightweight kernel called Compute Node Linux (CNL), and the service nodes run SUSE Enterprise Linux Server (SLES). Big Red 200 uses Slurm to coordinate resource management and job scheduling.

• Big Red 3. Big Red 3 is a Cray XC40 supercomputer dedicated to researchers, scholars,

and artists with large-scale, compute-intensive applications that can take advantage of the system's extreme processing capability and high-bandwidth network topology. Big Red 3 supports programs at the highest level of the university, including the Grand Challenges program. Featuring 930 dual-socket compute nodes equipped with Intel Haswell Xeon processors (22,464 compute cores), Big Red 3 has a theoretical peak performance (Rpeak) of 934 trillion floating-point operations per second (934 teraFLOPS). Big Red 3 runs a proprietary variant of Linux called Cray Linux Environment (CLE). In CLE, compute elements run a lightweight kernel called Compute Node Linux (CNL), and the service nodes run SUSE Enterprise Linux Server (SLES). Big Red 3 uses Slurm to coordinate resource management and job scheduling.

• Carbonate. Carbonate is a high-throughput cluster that is a larger memory version of

Karst with a peak theoretical capability of 83.8 TFLOPS, and an aggregate RAM of 28 TB. Carbonate consists of 96 nodes total each with 256 GB of RAM or larger. An additional 8 nodes are dedicated to specific research areas. Each node is a Lenovo NeXtScale nx360 M5 server equipped with two 12-core Intel Xeon E5-2680 v3 CPUs and four 480 GB solid-state drives.

o Deep Learning Nodes. Carbonate has been expanded to include 12 Lenovo ThinkSystem SD530 servers with NVIDIA GPUs. Eight of these nodes have dual NVIDIA16GB Tesla P100s per server and four of these nodes have dual


6

NVIDIA32GB TeslaV100s per server. All twelve servers have dual Intel Xeon Gold 6126 12-core 2.6GHz processors, 192GB RAM and 7.68TB of local disk.

o GPU-centric Expansion. During the first quarter of 2020, Carbonate has been expanded to include an additional 24 Apollo 6500 nodes with 8 NVLink-capable V100s per node.

• Karst. Karst is a high-throughput cluster that includes condominium services for research groups. Karst has an aggregate peak theoretical capability of 98.8 TFLOP, and an aggregate RAM of 14 TB. Karst consists of 275 nodes total. Of these, 3 larger-memory nodes are dedicated to supporting NIH users. Karst has a 10-gigabit Ethernet interconnect. Karst includes 450 TB of local spinning disk storage. Karst includes standard Linux nodes, a group of nodes in a condominium style –nodes owned by a particular user, but available for IU community use when the node owner is not using them.

Systems and Services for the National Research Community IU operates a number of projects for the national community or regional organizations.

• Jetstream. Jetstream is the National Science Foundation’s first production cloud for science and consists of 640 nodes geographically dispersed into two 320 node systems. One is housed at Indiana University’s Data Center. The second system is at the Texas Advanced Computing Center (TACC). Each 320-node system has 640 Intel Haswell CPUs with 7,680 cores, 40TB of memory, 640TB of local disk, and 960TB of additional available storage. The two systems are connected to Internet2 via 100Gbps links and via 10Gbps links to XSEDE resources. Jetstream provides a user selectable library of virtual machines for research use or allow for customized environments. System images can be archived for long-term storage and restored on demand.

• GlobalNOC. The Global Research Network Operations Center (GlobalNOC) at Indiana

University provides carrier grade operations, tools, and network expertise, while placing a singular focus on the unique requirements of the research and education (R&E) community. IU formed the GlobalNOC in 1998 to help Internet2 form its new R&E networking community, providing high quality network operations center services for Internet2's Abilene network. Since then, it has evolved alongside the community, growing from a three-person staff to an organization of more than 80 people who deliver unrivalled service and support for the world's most advanced research and education networks. The GlobalNOC's Service Desk, Network Engineering, and Software and Systems teams work to ensure the reliability, performance, and advanced capabilities for more than 20 projects, including: Internet2, N-Wave, TransPAC, ACE, I-Light, and the Indiana GigaPoP. A full list of support networks can be found online (https://globalnoc.iu.edu/supported-networks.html).

• National Center for Genome Analysis Support. The mission of the National Center for

Genome Analysis Support (NCGAS) is to enable the biological research community of the US to analyze, understand, and make use of the vast amount of genomic information

https://globalnoc.iu.edu/supported-networks.html


7

now available. NCGAS focuses particularly on transcriptome-and genome-level assembly, phylogenetics, metagenomics/transcriptomics and community genomics. NCGAS received a renewal from the National Science Foundation in 2015 to continue its work helping scientists analyze, understand, and make use of the vast amount of genomic information now available. This grant renewal has allowed the center to develop and deliver services that meet a national need for support of genome analyses that includes consulting services, software enhancements, and computation for the national community of researchers. The center currently supports hundreds of scientists working on more than 40 long-term research projects all over the US.


8


9

Section D: Proposal Instructions and Conditions D1 All questions and inquiries regarding this document should be submitted via the

JAGGAER Supplier Portal. Please respond by uploading your proposal under the Supplier Attachments section. If you experience issues you may contact Purchasing Contract Manager, Jennifer Guynn, directly at [email protected]. EXCEPT FOR CASES AUTHORIZED IN WRITING BY Jennifer Guynn, DURING THE DURATION OF THIS RFP PROCESS, THROUGH SELECTION AND NOTIFICATION, ANY COMMUNICATION BY PARTICIPANTS WITH INDIANA UNIVERSITY STAFF OTHER THAN Jennifer Guynn MAY RESULT IN IMMEDIATE REJECTION OF THAT PARTICIPANT. Questions regarding this RFP should be submitted through the Q&A Board within the Supplier Portal. Questions asked after the deadline may not be answered.

D2 The University reserves the right to waive any irregularities, to reject any or all proposals,

and to select the proposal that, in the sole opinion of The University, best meets The University’s interests. The University also reserves the right to negotiate with potential bidders so that its best interests are served. Proposals will be evaluated on the assumption that the proposed rates are your most favorable.

D3 The University will not pay for any information requested herein, nor is it liable for any

costs incurred by the participant in responding to this request. All proposals submitted become the property of the University; they will not be returned and may be subject to the Freedom of Information Act.

D4 Participants may withdraw their proposals prior to the closing time. Proposals received

after the time set for receipt will not be considered. The proposal constitutes an offer by the participant, which shall remain open and irrevocable for a period of 90 days.

D5 After the RFP closing time, proposals will be opened and reviewed at the convenience of

the University Purchasing Contract Manager. There is no public opening. D6 The University reserves the right to accept the proposal that appears to be in the best

interests of Indiana University and to negotiate a contract with that participant using the proposal submitted as a basis.

D7 The University reserves the right to award multiple contracts if deemed by University to

be in its best interest. Consequently, any contract awarded does not provide Supplier exclusive rights.

D8 Any information released either verbally or in writing prior to the issuance of this request

shall be deemed preliminary and not binding upon the University in any manner. D9 If requested, participants must submit audited financial statements for the past two (2)

years (or equivalent data) in order to demonstrate financial capability to provide the required services.


10

D10 Participants may be invited to come to Indiana University to provide a presentation about their submission at their own expense.

D11 The University will not enter into any agreement or execute any contract or affix

signature to any document from a participant whose terms, written or verbal, require the University to waive all conditions or requirements negotiated, provided for in this document, our purchase order, or by mutual consent. Any document containing a clause or clauses that serve to supersede all other documents attached to this transaction may be rejected.

D12 Notwithstanding any other provision of this Request for Proposal, the University

expressly reserves the right to:

1. Conduct discussions with any or all participants for the purpose of clarification of proposals;

2. Waive, or decline to waive, any insignificant defect or informality in any proposal

or proposal procedures; 3. Accept, reject, or negotiate the terms of any proposal, or any parts thereof, for the

purpose of obtaining the best and final offer; 4. Reissue a Request for Proposal; 5. Select the finalist(s) based on the University's analysis and evaluation of

proposals submitted. The University reserves the right to request presentations of proposals if the University feels further information is appropriate to the decision-making process.

6. Negotiate with any or all of the participant’s representatives for the purpose of

obtaining best and final offers. However, proposals will be evaluated on the assumption that the proposed costs/revenues are your most favorable.

7. Make no awards and cancel the RFP, make multiple awards, or make one award,

as an outcome of this process.

D13 The University reserves the right to use any and all concepts presented in any reply to obtain the most beneficial and effective path to achieving the desired goals. Selection or rejection of submittals shall not affect this right.

D14 By virtue of submittal, the participant is attesting that all requirements, terms, and

conditions in Section G have been read and understood. Unless the responding participant expressly and specifically provides otherwise in its written proposal, the proposal received in response to this Request for Proposal shall automatically be deemed to include the responding participant’s agreement to all terms and conditions of the RFP.


11

D15 University Infrastructure Data: In consideration of the Homeland Security Act, a supplier selected by the University may by necessity become privy to infrastructure information that is proprietary and confidential. A selected supplier may receive access to protected systems or media containing restricted information provided for the sole purpose of facilitating delivery of the services or product(s) requested in this Solicitation. The preferred supplier may be permitted to use and/or retain such information by effecting a Non-Disclosure Agreement and providing a contractual guarantee that you will afford appropriate measures to secure the information provided to you. Further, you agree to return any such proprietary information at the completion or termination of contract.

D16 All proposals or offers must be signed by a duly appointed officer or agent of your company. D17 Unless judged a trade-secret, no part of your offer or proposal can be guaranteed

proprietary or confidential. As required by the Indiana Open Records law, I.C. 5-14-et seq., submittals may become public information once a contract has been completed. Unless otherwise authorized in writing by Indiana University, Participants should not share this RFP outside of your organization except in the case of business partners providing equipment or services as part of your proposal response, until the RFP process is complete.

D18 Proposals responding to this Solicitation shall not be tied to any potential or future arrangements. Section E: Schedule of Events Following is the detailed schedule of events for this RFP. The University reserves the right to modify the below schedule. ACTIVITY DATE E1 Request for Proposal issued. 05/1/2020 E2 Participants’ questions concerning the proposal must be

received no later than 3:00 pm Eastern Time, in accordance with Section D1. A response or status of response will be provided within 24 hours. If the information is related to substantive content of the RFP, then clarifications will be sent to all known participants of the RFP.

05/15/2020

E3 Proposals due by 5:00 pm Eastern Time, in accordance with Section D2.

05/22/2020

E4 Post-Proposal meeting – by invitation only: Participants may be requested to present their proposal virtually, or in person to Indiana University. These dates are subject to change.

05/28/2020 - 06/10/2020

E5 Selection of Supplier(s) on or about 06/17/2020


12

E6 Implementation of services. 07/15/2020 - 09/13/2020

Delivery and Supplier implementation of awarded equipment must be made between July 15, 2020 and September 13, 2020. Final contract(s) will include a discount structure if equipment is not delivered in this time frame.

Section F: Statement of Needs Section F1 describes the technical objectives. Section F2 describes the scope of work. Section F3 describes the Research, Development, Outreach, and Economic Development Partnerships. Participants may choose to respond directly or partner with a reseller of their choice. Participants should respond point-by-point to the proposal request for each of the elements in sections F1, F2 and F3. Further response guidelines can be found in Section H. No more than three configurations in total are permitted from each Participant. Alternate configurations need not meet the exact configuration outlined in the objectives but must fit the overall capacity and performance targets. F1 Objectives F1.1 High Performance Scratch File System

IU seeks to purchase a high-performance scratch file system that is based around the open source Lustre file system that will support IU’s existing HPC resources. The file system should have a usable capacity of no less than 2 PB with performance specifications meeting those detailed below. The file system should be either entirely or largely composed of flash storage and provide for incremental growth. The Supplier’s objective will be to create a Lustre file system which we will call Scratch that will provide users with short-term high-performance disk storage. The Data Capacitor II (DC2) file system currently provides scratch space and project space (for short to mid-term projects) to roughly 2262 clients, comprising Big Red 200, Big Red 3, Karst, Carbonate, and Jetstream as described in Section C. The new Scratch file system will support the same research and collaborations that we are currently supporting with Slate, Slate-Project, DC2 and DCWAN. Characteristics of the new file system to support the HPC system should include:

F1.1.1. Provide a solution that uses the Lustre open source file system, with a minimum version of Lustre 2.12.X


13

F1.1.2. Lustre solutions using LDISKFS for back end file system storage are preferred for performance

F1.1.3. Provide a solution that is highly available, having hardware redundancies/protections and software cluster/failover protections.

F1.1.4. Provide a solution with no less than 2 PB usable storage F1.1.5. Provide a way to ensure that expired returned media are destroyed, or

allow expired media to be destroyed on site. F1.1.6. If your solution can support encryption in flight and/or at rest, please

provide implementation details. F1.1.7. Provide a solution capable of supporting at least 70 GB/s sustained

aggregate read and 70 GB/s sustained aggregate write of streaming data to the file system.

F1.1.8. Provide a solution capable of supporting over 500,000 sustained Lustre mknod and 500,000 sustained Lustre unlink operations per second.

F1.1.9. MDS nodes should be sized to support 16 billion inodes for the Scratch file system.

F1.1.10. The proposed solution should be compatible with the existing IB and TCP connected hosts. The solution should include the appropriate HCA cards, supporting cables and all necessary networking components.

F1.1.11. Provide at least (8) LNET routers that have at least two dual ported HCA cards each, which support all existing clients/storage and the proposed solution. The LNET routers should be capable of connecting at 100Gb or higher. Each LNET router should have a minimum of 128GB of memory with dual socket processors, running at a minimum speed of 3 GHz with at least 8 cores per processor.

F1.1.12. Provide an administrative client node, that will mount the proposed solution and support customer focused administrative tasks. The administrative client should connect at a minimum of 100Gb or higher. All necessary HCA’s and cables should be included.

F1.1.13. All nodes should have dedicated management connectivity, including remote power control and remote console access. All management connectivity will operate on a private network, and only the management node(s) will be connected with a public network connection. All necessary cables and networking equipment should be included in the solution.

F1.1.14. Supplier will provide rack and power requirements for the solution, including the number and type of power cords for each rack and estimated power utilization in kilowatts (kW) and amps (total and per rack). Supplier will provide number and type of power distribution units (PDUs). PDUs should include remote monitoring and logging capabilities.

F1.1.15. Include tools and/or APIs at the storage layer and the Lustre layer for monitoring, managing, and reporting on storage usage, utilization, monitoring of failures, and other operational metrics. A description of how these tools work and what is covered should be included. The following items should be addressed by the solution:

• Real time metadata information about users, groups and other logical groupings including capacity usage, logical location of usage, and age


14

of data. Realtime monitoring must be demonstrated to scale up to max inode usage.

• Automatic mechanism for enforcing storage administrator defined policies based on the real time metadata information. For example, delete files older than 30 days based on the file’s “birth date” (not atime/mtime/ctime).

• Storage subsystem fault monitoring, and alerting mechanism via syslog, SNMP, and SMTP.

• Storage subsystem component level metrics (such as cache, logical disks, physical disks, bandwidth, IO sizes, IO latencies, IO histogram, etc.)

• Metrics should be displayed in real-time monitoring, with the ability to “export” the raw data for custom uses.

• Monitored metrics should be recorded and be available in the same interface for displaying trends of historical metrics. Recorded metric retention should be a minimum of 3 years.

• Lustre-specific metrics should be recorded and monitored in a similar fashion as the storage subsystem.

F1.1.16. Provide training for 10 IU staff on hardware and software configuration and operation.

F1.1.17. Acceptance tests will use Lustre specific utilities, available from the lustre-iokit. These utilities will match the Lustre version provided in the file system solution. Aggregate file system bandwidth tests shall use IOR. Other testing utilities may be used if pre-approved by IU.

Please respond to the following questions: F1.1.18. Describe how proposed system could be expanded in terms of both

capacity and capability without replacing hardware. Specifically, how can the system double in capacity, while leveraging the initial deployment.

F1.1.19. Provide the fixed cost in Section H8 for an option to purchase, within 24 months of issued purchase order, additional storage increments up to an additional 2 PB usable. Supplier must agree that the price will be decreased for University, if Supplier decreases such pricing generally to its customers below the offered cost of University, for the relevant goods and services.

• The Participant shall describe what options exist for increasing the capacity of the system beyond 4 useable PB.

F2 Scope of Work

F2.1.1. In addition to the benchmarks, requirements and criteria described above for the scratch file system, the following objectives shall be met.


15

F2.1.2. Training • The selected Supplier shall provide training for every software and hardware

component in the system. • Training can be provided after acceptance of the system but shall be prior

to production deployment of the system. • Training will be for up to 10 staff members within 10 days of acceptance and

shall be delivered virtually or on site to IU staff, at IU’s discretion.

F2.1.3. Installation and Testing Requirements • Final acceptance criteria will be determined upon award and added to the final

contract and will be based on the Supplier’s claims. • Systems will undergo a 3-phase acceptance test that includes functionality,

performance, and stability tests. • A detailed report of the tests and results will be approved by the University, prior

to final payment. • Failure to meet the acceptance testing performance criteria, will result in

penalties, and/or the right of the University to refuse the solution with no financial obligation. Penalties will be described in the final contract.

• All acceptance testing will take place at the University’s facility. IU Staff members will participate in acceptance testing.

• A 3-day stability test using a several scripts running on various servers will perform a continuous mix of file system operations on the file systems. The stability tests will be performed after all the functional and performance testing. During this period 100% file operations should succeed unless network connectivity between the test servers and the file systems fail due to components other than those provided by the Supplier.

• IU personnel will have the prerogative to perform functional testing to ensure operations of basic functions such as successful restarts of components and servers, and network connectivity and operation.

• IU personnel will have the option to verify performance prior to final acceptance based on the terms of the final contract.

• Supplier will demonstrate the support and escalation procedures while at the IU facility. IU Staff will have support initiation/escalation capabilities. Supplier shall describe the escalation process. Supplier is required to outline the Service Level Agreement terms and describe the penalties the Supplier will ensue if the SLA is not met.

• Supplier is responsible for installation at the IU facility after delivery, with appropriate help and participation from IU personnel. IU personnel will assist with local administration and connectivity issues such as network configuration, power cables, and any issues related to the IU facility.

• The Supplier shall provide all labor necessary for both physical installation and initial configuration of the delivered system.

• Specify the anticipated time required for installation after delivery and the anticipated project schedule, including delivery.


16

• Supplier shall provide all necessary power equipment. • Supplier shall provide racks according to the specifications adhered to by

the Indiana University data center • Raised floor load limit: 312 lbs/sq-ft • Rack Maximum Height: 8 feet

• Solution should be redundant and points of failure minimized. • Please provide a diagram of the full system architecture to illustrate how

this has been achieved. • Confirm how soon after the PO is issued and an agreement is signed that can you

deliver the equipment and begin implementation, keeping in mind the timelines outlined in Section E.

F2.1.4. Support

• The purchase price of the system shall include 3 years of hardware and software support with next business day (NBD) parts, including a comprehensive spare kit on site. Price these additional options:

• 24 x 7 x 365 support with 4-hour on-site response time • Guaranteed pricing for a fourth year of support • Guaranteed pricing for a fifth year of support

F3 Research, Development, Outreach, and Economic Development Partnerships Long term, sustainable partnerships have always been an important part of IU’s strategy for advanced information technology and cyberinfrastructure. Partnerships related to this solicitation are required in one area (F3.1) and are strongly encouraged in another set of areas (F3.2).

F3.1. Required – partnership to implement and tune system

It is expected that IU and Supplier experts will jointly author technical papers in refereed journals and conferences. IU will be willing to provide technical presentations at Supplier request, and to participate in publicity about what is expected to be a highly important set of systems added to the Indiana University cyberinfrastructure.

F3.2 Encouraged – partnerships in research and development, education and outreach, or economic development Participants are encouraged to identify any ongoing partnership opportunities available in the form of collaborative research and development programs, internship programs, student support programs, or hardware grants relevant to partnerships in research and development, education and outreach, or economic development. In particular, partnerships might involve any or all of the following areas: • Research and Development. Data movement between IUs three primary research storage systems is crucial to increasing the efficiency of researchers and shorten the time to discovery. Of particular interest would be the development of novel solutions to data lifecycle management and data curation.


17

• Economic Development. Indiana University would be interested in continued development of commercial research partnerships with companies located in the State of Indiana. Of particular interest would be developing best practices for commercial entities to maximize I/O efficiencies for current codes running at scale. • Education and outreach. Collaborative projects that allow IU and a participant to work together to create a highly trained 21st century workforce are encouraged. Such programs might involve postdoctoral fellowships, internships for graduate or undergraduate students, or involvement in and/or support for K-12 outreach led by IU. • These options are not intended to limit the creativity of your response or the opportunities to propose other ideas that fall into these areas of partnership.

Section G: Terms and Conditions The following terms and conditions may become a part of an agreement that will be entered into by the Supplier and Indiana University. G1 Contract Term

The Supplier will commence once a Supplier is chosen and an agreement is in place.

G2 Applicable Law The Agreement shall be governed by the laws of the State of Indiana, and Supplier shall at all times comply with and observe all federal, state and local laws, ordinances, and regulations which are in effect during the period of the Agreement and which in any manner affect the work or its conduct.

G3 Agreement Assignment

No right or duty in whole or in part of the Supplier under the Agreement may be assigned or delegated, including by transfer of stock or ownership in Supplier, without the prior written consent of the University.

G4 Conflict of Interests

Private and non-profit corporations are bound by state statute regarding conflicts of interest by employees in the conduct of state agreements. A completed non-collusion certificate must accompany the signing of the Agreement.

G5 Agreement Termination

Termination without Cause Either party may terminate the Agreement by giving the other party 60-day written notice of termination. Written notice of termination must be given by certified letter.

Termination for Cause Should either party breach any material terms or provisions of the Agreement, the non-breaching party shall promptly serve the breaching party with written notice setting forth the alleged breach. Unless the breaching party, within ten (10) working days of the receipt of the notice, has corrected or has taken reasonable steps toward correcting the


18

alleged breach, the non-breaching party may terminate the Agreement by giving thirty (30) days written notice to the breaching party of its intention to terminate the Agreement. Certified letter must give written notice of termination. The University may cancel the Agreement for breach, as determined by the University, of any material terms or provisions, including but not limited to insufficient insurance coverage or service unsatisfactory to the University. This may also include any cessation or diminution of service including but not limited to failure to maintain adequate personnel whether arising from labor disputes, or otherwise, any substantial change in ownership or proprietorship of the Supplier which, in the opinion of the University, is not in its best interest. Certified letter must give written notice of termination.

G6 Notices

With the exception of notice of termination, which must be made by certified mail, any written notice called for in the Agreement may be given by personal delivery, first class mail, overnight delivery service or facsimile transmission. Notices given by personal delivery will be effective on delivery; by overnight service, on the next business day; by first class mail, five business days after mailing; and by facsimile, when an answer back is received.

G7 Non-Discrimination

In connection with the performance of work under the Agreement, the Supplier agrees not to discriminate against any student, employee or applicant for employment because of age, race, religion, color, handicap, sex, sexual orientation, or national origin. This provision shall include, but not be limited to, the following: employment, upgrading, demotion or transfer, recruitment or recruitment advertising, lay-off or termination, rates of pay or other forms of compensation, and selection for training, including apprenticeship. The Supplier further agrees to take affirmative action to insure equal employment opportunities. If present on the campus, Supplier, including all employees and agents, shall agree to abide by, and comply with, all Indiana University, federal, state, and local policies, regulations, and laws that pertain to sexual harassment and non-discrimination. Supplier further agrees that employees and agents, while on University’s premises, shall comply with and observe all applicable rules and regulations concerning conduct on the University’s premises, which are imposed upon the University’s employees and agents.

G8 Excused Performance

If, because of riots, war, public emergency or calamity, fire, flood, earthquake, act of God, government restriction, business operations at the University are interrupted or stopped, the performance of the Agreement, with the exception of money already due and owing, shall be suspended and excused to the extent commensurate with such interfering occurrence. The expiration date of the Agreement may be extended, by mutual written consent, for a period of time equal to the time that such default in performance is excused.

G9 Independent Supplier Relationship


19

It is mutually understood and agreed that an independent Supplier relationship is hereby established and that employees of the Supplier are not employees of the University and that employees of the University are not employees of the Supplier.

G10 Severability

If any provision of the Agreement or its application to any party or circumstances shall be invalid or unenforceable to any extent, the remainder of the Agreement and the application of its provisions to other parties or circumstances shall not be affected and shall be enforced to the extent permitted by law.

G11 No Waiver

The failure of University to insist in any one or more instances upon the performance of any one or more of the provisions of the Agreement or to pursue any rights here under shall not be construed as a waiver of any such provisions or the relinquishment of any such rights.

G12 Endorsement

Unless specifically authorized in writing by the University Purchasing Department on a case by case basis, Supplier shall have no right to use, and shall not use, the name of Indiana University, its officials or employees, or the seal or marks of the University in advertising, publicity, or promotion; nor to express or imply any endorsement of Supplier’s supplies or services.

G13 Non-Performance

In the event that the Supplier fails to perform under the terms and provision of the Agreement, after IU written notice of breach and a 30 day opportunity to cure or commence continuing cure activities, and only if Supplier is unable to cure within such time frame or after good faith efforts to cure on a continuing basis after 60 days, then the Supplier shall replace the equipment for the University to complete work at no additional cost to the University. Supplier agrees that a delay in the delivery of the equipment may cause both reputational and financial harm to the University and affect the ability of the University to receive future research funding.

G14 Force Majeure

Neither party shall be in considered in breach of the agreement for failure to perform if such failure is caused by national or local calamity, acts of terrorism, the act or regulation of any public authority, labor difficulty or strike, war, epidemic, fire, storm, inclement weather or other act of God, or any other cause beyond the reasonable control of the non-performing party that renders that party’s performance impossible.


20

G15 Funding The University represents that, as of the date of the Agreement, funds sufficient to pay immediate financial obligations under the Agreement have been allocated and are available. However, University is a publicly funded entity and our ongoing financial obligations herein are subject to allocation of funds by parties not controlled by the University. In the event, through no action initiated by the University, the legislative body of the State of Indiana does not appropriate sufficient funds allowing for the continuation of the agreement for any fiscal year, whole or part, and there are no funds from other sources to continue, the Agreement may be terminated by University.

G16 Data Security Supplier shall treat all data that it receives from University, or is otherwise exposed to within University data systems, with the highest degree of confidentiality and in compliance with all applicable federal and state laws and regulations and University policies. Supplier shall employ commercial best practices for ensuring the security of all University electronic and paper data accessed, used, maintained, or disposed of in the course of Supplier’s performance under this Agreement. Supplier shall only use such data for the purpose of fulfilling its duties under this Agreement and shall not further disclose such data to any third party without the prior written consent of Indiana University or as otherwise required by law. Upon termination or expiration of the contract, Supplier will either return or confirm the secure destruction of all University documents, records and data, at University’s election. Without limiting the foregoing, in the course of performing its duties under this Agreement Supplier may receive, or be exposed to, the following types of data: student education records; financial information as that term is defined in the Financial Modernization Act of 1999; protected health information as that term is defined in the Health Insurance Portability and Accountability Act; and various items of personal identifying information including but not limited to Social Security Numbers, credit card numbers, financial account numbers and corresponding security or access codes and passwords, drivers license numbers, and Indiana state identification card numbers. Supplier shall employ sufficient administrative, physical, and technical data security measures to meet the requirements under the specific federal and state laws and credit card industry standards applicable to those data, including but not limited to: Student Education Records: The Family Education Rights and Privacy Act (FERPA), 20 USC 1232g et seq., and related regulations at 34 CFR Part 99; Financial Information including credit card and financial account numbers: The Financial Modernization Act of 1999, 15 USC 1681 et seq.; the Safeguards Rule at 16 CFR Part 314; and Indiana Code 4-1-11 and 24-4-9. Protected Health Information: The Health Insurance Portability and Accountability Act (“HIPAA”), 42 USC 1320d-2 (note); implementing privacy and security regulations at 45


21

CFR Parts 160 and 164, and related agency guidance; and the terms of any Business Associate Agreement or LDS agreement between University and Supplier; Social Security Numbers: Indiana Code 4-1-10, 4-1-11, and 24-4.9. Drivers License Numbers: Indiana Code 4-1-11 and 24-4.9. Credit Card Numbers: Indiana Code 4-1-11 and 24-4.9; the Payment Card Industry Data Security Standards. Immediately upon becoming aware of a breach of the Supplier’s security that reasonably may have resulted in unauthorized access to University data, Supplier shall notify University and shall cooperate fully with University’s investigation of and response to the incident. Except as otherwise required by law, Supplier shall not provide notice of the incident directly to the persons whose data were involved, without prior written permission from University. Supplier acknowledges and agrees that University is subject to Indiana’s Open Records law, I.C. 5-14-et seq., and that disclosure of some or all of confidential information provided pursuant to this Agreement, or the Agreement itself, may be compelled pursuant to that law. University agrees that, upon receipt of a request for confidential information made pursuant to the Indiana Open Records law, it shall a) promptly notify Supplier of the fact and content of the request, b) consult with Supplier regarding any legitimate basis on which it might resist or narrow its response to the request, and c) disclose only information that University, in the opinion of its legal counsel, is legally compelled to disclose.” Notwithstanding any other provision of this agreement, Supplier shall reimburse the University in full for all costs, expenses, and liabilities of any kind whatever incurred by the University as a result of Supplier’s failure to comply with the above data confidentiality and security requirements. This obligation shall include defending, indemnifying, and holding the University harmless from any third party claims or causes of action of any kind arising from or relating to the Supplier’s use, maintenance, or handling of University data received in connection with its performance under this Agreement. These remedies shall be in addition to any other remedies provided within this Agreement or otherwise available under law.

G17 Indemnification Supplier shall indemnify and save harmless The Trustees of Indiana University, its

officers, agents and employees from any and all losses, costs, damages, liability and expenses (including costs of defense, settlement, and reasonable attorney’s fees) in connection with claims or suits for damage to property and/or injury to persons, including death, alleged or claimed to have been caused, by or through the performance of the work or operations incidental to the work, by the Supplier, its agents or employees, or by its subcontractors of any tier, their agents or employees, whether through negligence or


22

willful act; and Supplier shall at request of the University undertake to investigate and defend any and all such claims or suits against the University.

G18 Insurance Requirements Minimum insurance requirements are listed in Appendix C.

Section H. Proposal Response The participant’s response to this proposal should include answers to the following series of questions. So that the RFP team can easily follow the questions and responses, please assure that the question is stated immediately before the response. In addition to point-by-point responses, you may include descriptive literature if you make reference to specific contents. In reviewing the proposals, university personnel will not search through general literature. Where a question is asked, answer the question and supply any supportive detail. Any deviation from this format and sequence may result in the proposal being immediately rejected. While responses should address all Solicitation items, it is important to note that we also encourage and will consider any creative ideas for improvements or cost savings related to this transaction that may not be suggested in this document. Functional, technical, and economic solutions beyond the confines of this Solicitation may also be considered. The responses should address all Solicitation items. However, the University reserves the right to consider other ideas and solutions, or only a restricted subset of the configuration discussed in this document. All optional arrangements should be described and priced separately. H1 All proposal responses must include:

H1.1 The name, address, phone and fax number, and email address for the duly authorized agent submitting the proposal.

H1.2 Full description of company, including experience, qualifications and

organizational chart.

H1.3 Documentation of any intent to use another company(ies) or private individual(s) as a subcontractor(s) for any part or the whole of the services offered in response to this RFP. Indiana University reserves the right to approve or reject any subcontracting agent or to reject proposals based on the use of subcontracted work.

H1.4 Completed Non-Collusive Certificate (attached as Appendix A).

H1.5 Discuss current supplier diversity participation by your company (attached as

Appendix B).


23

H1.6 Copies of all documents that could become a part of a final Agreement arising from this process. A legal review of the Participant’s proposed Agreement terms will be part of the criteria in evaluating the Participant’s offer.

H1.7 Three references from previous clients. These references should be research 1

universities or US government laboratories (e.g. Department of Defense, Department of Energy, or NASA) that are willing to engage in discussions with the RFP team.

H2 Describe in detail your company’s capability of providing the services required in

Section F. H3 Describe in detail other systems of comparable size and complexity your company has

installed in the past 3-5 years. H4 Describe your methodology for providing these services, how you organize your team

and the IU team, and how you ensure you deliver a quality product that meets expectations.

H5 Describe the individual staff members in your company that would be assigned to this

project and include their resumes. H6 Describe how you would break down this project into specific tasks with a timeline and

assigned costs, using the outline in Section F as a guideline, and taking into consideration the delivery and implementation dates in Section E.

H7 Pursuant to H6 above, describe your rates for each component in section F proposed. This

will be a fixed price quote. This should include any training and support costs as requested in Section F. Line item pricing should be provided in Excel format.

H8 Provide the fixed cost for an option to purchase, within 24 months of issued purchase

order, additional storage increments up to an additional 2 PB usable as required in Section F1.1.19. Pricing should be guaranteed for this term. Supplier must agree that the price will be decreased for University, if Supplier decreases such pricing generally to its customers below the offered cost to University, for the relevant goods and services.

H9 Signature: the submission must be signed by a legally authorized agent of the firm. Name: __________________________________ Signature: __________________________________ Title: __________________________________


24

Company: __________________________________ Phone: __________________________________ Date: __________________________________


25

APPENDIX A NON-COLLUSIVE CERTIFICATE

By submission of this document, each person signing certifies, and in the case of a joint submittal, each party thereto certifies as to its own organization, under penalty of perjury, that to the best of its knowledge and belief: 1. The content of this request has been arrived at independently without collusion, consultation, communications, or agreement for the purpose of restricting competition as to any matter relating to service or cost with any other supplier(s) or with any competitor; 2. No attempt has been made or will be made by Supplier to include any other person, partnership or corporation to submit or not to submit a response for the purpose of restricting competition and; 3. No employee, agent or consultant of Indiana University has received or will receive any payment or any other form of compensation from Supplier as a result of award of an agreement or promise of award to Supplier. Name: __________________________________ Signature: __________________________________ Title: __________________________________ Company: __________________________________ Date: __________________________________


26

APPENDIX B SUPPLIER DIVERSITY INFORMATION

Participants in this RFP are required to return Appendix B with the appropriate information provided. This information is not applicable to my business, firm or corporation. Indiana University encourages participants in this RFP to become involved in our Supplier Diversity Program. The Supplier Diversity Program tracks businesses that qualify as Minority (MBE), Small Disadvantaged Business (SDB), Women-Owned Business Enterprises (WBE), HubZone, or Veteran Owned Business Enterprises. To qualify as one of the above business classifications, your company must be at least 51% owned, controlled and actively managed by a person in one of the categories listed above. For more information, please go to this website: http://www.indiana.edu/~busdiv/supplier_certification_form.doc

State your company’s status: ________ Small Business ________ WBE ________ HubZone ________ SDB ________ Historically Black

College/University ________ MBE ________ Veteran Owned ________ Service Disabled

Veteran Owned

- PLEASE ATTACH CERTFICATION WITH COMPLETED FORM -

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

If the Participant answered “yes”, please provide the name and telephone number of the Participant’s Program Coordinator __________________________________________

http://www.indiana.edu/%7Ebusdiv/supplier_certification_form.doc


27

Identify any and all Second Tier Business Relationships or First Tier Business Relationships Supplier has with Minority, Women, and Disadvantaged Owned and operated businesses. (1st Tier is defined as -- Any supplier, regardless of type or size, which has a direct contract with Indiana University. 2nd Tier is defined as -- Any supplier, regardless of type or size, which is contracted through a 1st tier supplier to Indiana University.) Name: __________________________________ Signature: __________________________________ Title: __________________________________ Company: __________________________________ Date: __________________________________


28

Appendix C

INDIANA UNIVERSITY MINIMUM INSURANCE REQUIREMENTS

FOR SUPPLIERS and OTHER NON-CONSTRUCTION CONTRACTS

Obligations of Supplier

Supplier (whether corporation, sole proprietorship or partnership) shall procure and maintain during the term of the contract insurance of the types of coverages and minimum limits as identified here and shall provide the Indiana University (IU) with Certificate(s) of Insurance evidencing these coverages prior to the beginning of the contract.

♦ It is the responsibility of the Suppliers to become familiar with IU’s insurance requirements

and to ensure that they can meet these requirements prior to signing of any contract(s). Please provide this exhibit to your insurance agent so the correct certificate can be issued without delay.

♦ No Supplier shall provide contracted services, and shall not be paid for any contracted

services, until proper certificate(s) of insurance have been submitted to and approved by the IU. All required insurance policies shall be written by a company(s) authorized to do business in Indiana. IU shall not be liable to any person for the failure of the Supplier to carry specified insurance.

♦ If any part of any coverage includes a deductible, self insurance, a captive insurance company or a fronting arrangement, the amount so covered must be disclosed on the certificate or in a separate letter from the Supplier. IU reserves the right to approve of this coverage.

CERTIFICATE HOLDER: The Trustees of Indiana University

c/o Office of Risk Management 400 E. 7th Street Room 705 Bloomington, In. 47405-2206 Insurance Requirements 1. General Liability

• Each occurrence: $1 million • Products: $1 million • Damage to premises: $500,0000F

1

1 $500,000 is the standard amount. IU reserves the right to increase this amount upon review of the contract and our judgment of the hazard posed to our premises. Lesser amounts may also be approved if “occupancy” only consists of the placement of, for instance, vending machines.


29

• General aggregate: $2 million • The "COMMERCIAL GENERAL LIABILITY" box must be checked • The "OCCUR" box must be checked

2. Automobile Liability

• The box(es) that is/are checked must include a check in the box for Any Auto or All Owned, Hired and Non-Owned Autos

• Combined Single Limit coverage: $1 million. • If separate Bodily Injury and Property Damage limits are purchased, each must be

$1 million. • Indiana University agrees to waive this provision for BEI as long as no employee or

agent of BEI operates a vehicle in Indiana in furtherance of this contract.

3. Excess/Umbrella

• Excess coverage per se is not required. However, any of the dollar amount requirements can be met by a combination of primary and excess coverage.

• Excess/umbrella coverage must be per occurrence coverage.

IU reserves the right to require increased limits of coverage if, in the opinion of IU, any provision of the contract includes products or activity that is hazardous in nature or poses a higher than usual risk.

4. Worker’s Compensation

If the Supplier will be on University premises (other than incidental visits to the Purchasing Department), the Supplier shall procure and maintain a Workers’ Compensation policy to cover its obligation under the applicable laws of any state or federal government to its employees employed on the jobsite or elsewhere on this project, including its liability as an employer under common law (commonly known as Employer’s Liability Coverage “B”) with limits of not less than that listed below. Before commencing contracted activities, Supplier shall submit to IU a valid State Form 41321 (Certificate of Compliance – Worker’s Compensation and Occupational Diseases) or a facsimile thereof at IU’s option. If the Supplier has no employees (i.e., a one-person shop) then a Certificate of Exception must be obtained from the State.

Worker’s Compensation: Statutory Employer’s Liability: $ 500,000 each accident or disease

$ 500,000 policy limit $ 500,000 each employee


30

Insurance Policy Endorsements

All insurance policies must provide the following endorsements to the policy and must be noted on the certificate(s):1F

2

1. Additional Insured Endorsement (CG2010 10 01 and CG2037) or equivalent form required on General Liability, Automobile Liability and Excess/Umbrella Liability policies naming the IU and/or Other Parties as defined in the contract. IU shall be identified as: “The Trustees of Indiana University, its officers, agents and employees.” If additional insured status is automatically granted by the insurance form “where required by written contract” then it is sufficient to note that on the certificate with a reference to the form number. This must include information about the Excess/Umbrella coverage, e.g., “Excess coverage is following form.”

2. Waiver of Subrogation on General Liability, Automobile Liability, and Employer’s

Liability/Workers’ Compensation Policies in favor of IU.

3. All insurance policies shall be primary and non-contributing with respect to any insurance carried by IU, and shall contain a severability of interests clause in respect to liability, protecting each insured as though a separate policy had been issued to each.

4. All policies shall contain a covenant requiring (30) days written notice by the

insurer to the Indiana University Office of Risk Management before cancellation, reduction or other modifications of coverage for any reason, whenever possible.

Certificate Details Description of Operations The DOO must include the Indiana University purchase order number to which this coverage applies. Insurance Companies

All insurance carriers selected by Supplier must be rated “A-” or above in the most recent edition of the “A.M. Best’s Key Rating Guide.”

Hold Harmless Agreement

Supplier shall indemnify and save harmless IU from any and all losses, costs, damages, liability and expenses, including reasonable attorney fees, arising out of or in conjunction with claims or suits for damage to any property and/or injury to persons, including Supplier’s employees, including death, alleged or claimed to have

2 An addendum to the COI can be used if additional space is needed.


31

been caused by or through the performance of the contract or operations incidental to the contract by the Supplier, its agents or employees, whether through negligence or willful act; and Supplier shall, at the request of IU, undertake to investigate and defend any and all such claims or suits against IU.


32

Appendix D Federal Debarment Certification

_____________________ (date)

Purchasing Department

Indiana University 400 E. 7th Street Bloomington, IN 47405

In accordance with the Federal Acquisition Regulation, 52.209-5:

(a) (1) The Company certifies, to the best of its knowledge and belief, that—

(i) The Company and/or any of its Principals—

(A) (check one) Are ( ) or are not ( ) presently debarred, suspended, proposed for debarment, or declared ineligible for the award of contracts by any Federal agency; (The debarred list (List of Parties Excluded from Federal Procurement and Nonprocurement Programs) is at http://epls.arnet.gov on the Web.) (B) (check one) Have ( ) or have not ( ), within a three-year period preceding this offer, been convicted of or had a civil judgment rendered against them for: commission of fraud or a criminal offense in connection with obtaining, attempting to obtain, or performing a public (Federal, state, or local) contract or subcontract; violation of Federal or state antitrust statutes relating to the submission of offers; or commission of embezzlement, theft, forgery, bribery, falsification or destruction of records, making false statements, tax evasion, or receiving stolen property; and (C) (check one) Are ( ) or are not ( ) presently indicted for, or otherwise criminally or civilly charged by a governmental entity with, commission of any of the offenses enumerated in paragraph (a)(1)(i)(B) of this provision.

(ii) The Company (check one) has ( ) or has not ( ), within a three-year period preceding this offer, had one or more contracts terminated for default by any Federal agency.

(2) “Principals,” for the purposes of this certification, means officers; directors; owners; partners; and, persons having primary management or supervisory responsibilities within a business entity (e.g., general manager; plant manager; head of a subsidiary, division, or business segment, and similar positions).

http://epls.arnet.gov/


33

This Certification Concerns a Matter Within the Jurisdiction of an Agency of the United States and the Making of a False, Fictitious, or Fraudulent Certification May Render the Maker Subject to Prosecution Under Section 1001, Title 18, United States Code.

(b) The Company shall provide immediate written notice to the Contracting Officer if, at any time prior to contract award, the Company learns that its certification was erroneous when submitted or has become erroneous by reason of changed circumstances. (c) A certification that any of the items in paragraph (a) of this provision exists will not necessarily result in withholding of an award under this solicitation. However, the certification will be considered in connection with a determination of the Company’s responsibility. Failure of the Company to furnish a certification or provide such additional information as requested by the Contracting Officer may render the Company nonresponsible. (d) Nothing contained in the foregoing shall be construed to require establishment of a system of records in order to render, in good faith, the certification required by paragraph (a) of this provision. The knowledge and information of a Company is not required to exceed that which is normally possessed by a prudent person in the ordinary course of business dealings. (e) The certification in paragraph (a) of this provision is a material representation of fact upon which reliance was placed when making award. If it is later determined that the Company knowingly rendered an erroneous certification, in addition to other remedies available to the Government, the Contracting Officer may terminate any contract with the Company for default.

________________________________ (firm)

________________________________ (address)

________________________________ ________________________________ (signature required) (Phone) ________________________________ ________________________________ (print name) (fax) ________________________________ ________________________________ (print title) (Federal Taxpayer ID Number)

Documents

Indiana University HPC Scratch File System IU …...F. Statement of Needs 12 G. Terms and Conditions 17 H. Proposal Response 22 Appendix A. Non-Collusive Certificate 25 Appendix B