SECTION A – RFP/SUBCONTRACT FORM

1,525 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,525
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

SECTION A – RFP/SUBCONTRACT FORM

  1. 1. Request for Proposals (RFP) Scientific Earth Drilling Information Service (SEDIS) Phase III IODP-MI  August 10, 2009
  2. 2. REQUEST FOR PROPOSALS (RFP) Scientific Earth Drilling Information Service (SEDIS) Phase III Table of Contents Introduction ............................................................................................................................... 3 Project Description ................................................................................................................... 3 Statement of Work .................................................................................................................. 10 SEDIS III Requirements ......................................................................................................... 18 SEDIS III Deliverables ............................................................................................................ 20 Subcontract Administration .................................................................................................... 27 Special Subcontract Requirements ........................................................................................ 28 Subcontract Clauses .............................................................................................................. 30 Representations and Certifications ........................................................................................ 38 Proposal Instructions .............................................................................................................. 48 Proposal Evaluation Factors .................................................................................................. 50 2
  3. 3. SECTION A – SOLICITATION/CONTRACT FORM A.1 INTRODUCTION The Integrated Ocean Drilling Program (IODP) is an international research program that explores the history and structure of the Earth as recorded in seafloor sediments and geophysical properties of oceanic crust. IODP builds upon the earlier successes of the Deep Sea Drilling Project (DSDP) and Ocean Drilling Program (ODP), which revolutionized our view of Earth history and global processes through ocean basin exploration. IODP expands the reach of these previous programs by using multiple drilling vessels, including riser, riserless, and mission-specific platforms, to achieve its scientific goals. These goals follow the themes outlined in the IODP Initial Science Plan: "Earth, Oceans and Life: Scientific Investigations of the Earth System Using Multiple Drilling Platforms and New Technologies" The deep biosphere and the subseafloor ocean; Environmental change, processes and effects; and Solid earth cycles and geodynamics. The Integrated Ocean Drilling Program—Management International, Inc. (IODP-MI) is funded by the U.S. National Science Foundation (NSF), the Japan Ministry of Education, Culture, Sport, Science and Technology (MEXT), the European Consortium for Ocean Research Drilling (ECORD) and IODP member countries. IODP-MI has offices in Washington, D.C. and Sapporo, Japan. IODP-MI is the international management organization responsible for program management and oversight of the national Implementing Organizations (IOs) and member countries. IODP-MI is a not-for-profit 501(c)(3) tax-exempt organization incorporated on February 28, 2003. For more information, please visit www.iodp.org. IODP-MI requests proposals from qualified vendors for providing services to develop and deploy Phase III of the Scientific Earth Drilling Information System (SEDIS). The SEDIS system and goals for SEDIS Phase III development are described within this solicitation. IODP-MI further requests that the offeror outline its capabilities to provide the necessary personnel, facilities, supplies, and materials to perform the scope of work as set forth in Section C of this solicitation and in accordance with the proposal preparation instructions found in Section K, subject to the availability of funds from the US National Science Foundation. A.2 PROJECT DESCRIPTION IODP-MI has developed SEDIS for the purpose of providing an integrated data discovery and data access portal for information from the three scientific drilling platforms data management systems, operated by: US Implementing Organization (USIO): o http://www.iodp-usio.org/ Japanese Center for Deep Earth Exploration (CDEX): o http://www.jamstec.go.jp/jamstec-e/odinfo/cdex_top.html European Consortium for Ocean Research Drilling (ECORD) Science Operators (ESO): o http://www.ecord.org/eso/eso.html 3
  4. 4. Each IO utilizes its own data systems for collecting, processing, and distributing data collected on its drilling vessels and laboratories. The USIO has historically used a data system called JANUS to manage data collected during much of DSDP, ODP and IODP. As of 2009, USIO has launched the Laboratory Information Management System (LIMS) for management of new drilling data and data derived from earlier core material. CDEX operates a data management system called J-CORES for data associated with samples collected aboard the drilling vessel (D/V) Chikyu. ESO operates an offshore data collection system called Expedition Drilling Information System (DIS). All IOs use separate data collection and management system for borehole logging and similar data (e.g., vertical seismic profile). For USIO and ESO, the borehole logging data is managed via the Borehole Research Group at Columbia University Lamont Doherty Earth Observatory. CDEX utilizes an application called OPERATION for shipboard logging data collection, and the J-CORES Public Data Center for post-cruise log file dissemination. Each IO maintains a web site for public access of post-moratorium (i.e., generally 1-year after date of Expedition completion) data. USIO JANUS data is accessible via JANUSweb (http://www.iodp- usio.org/Data_Samples/default.html) USIO LIMS data is accessible via http://iodp.tamu.edu/janusweb/lims/limscmp.shtml USIO archives data sets at the National Geophysical Data Center (NGDC) USIO and ESO logging data is available via http://iodp.ldeo.columbia.edu/DATA/ ESO data is available via WDC-MARE/PANGAEA (http://iodp.wdc-mare.org/) CDEX data is available via J-CORES Public Data Center (http://sio7.jamstec.go.jp/j- cores.data/) IODP-MI manages a number of program-wide data systems that are also contributing components of the SEDIS system. The Site Survey Data Bank (SSDB) is a repository for seismic and other site survey data used in support of IODP proposals and expedition planning. The Proposal Database (PDB) is a system for submission and management of IODP expedition and shipboard project proposals. The Sample Management and Curation System (SMCS) is comprised of a Central Inventory of drilled materials under IODP curation and a Sample and Data Request Management System (SDRM). IODP-MI manages a Digital Object Identifier (DOI) registration system for assigning DOIs to program data and registering DOIs with a DOI registrar. IODP-MI is also responsible for maintaining lists of accepted vocabularies and terms, such as the IODP Depth Scale Terminology, the Taxonomic Names Lists, lithology classifications and terms, etc. IODP-MI also manages the central IODP data portal, SEDIS, having currently realized the first two phases of development of this system. Figure 1, below, is a view of the SEDIS metadata catalogue search interface. 4
  5. 5. Figure 1: SEDIS portal with tabs for metadata (SEDIS I) and publications (SEDIS II) IODP-MI is responsible for enabling integrated access to IODP, ODP and DSDP data (herein IODP data), developing providing public access to the distributed data systems via a ―one- stop‖ data portal integrating the IOs and IODP-MI source data systems, developing interfaces with external data and metadata networks, making IODP data searchable for data discovery, and making IODP data accessible for mapping and analytical applications. The goal of SEDIS therefore extends beyond IODP, and has the important objective of providing an integrated data portal for all scientific ocean drilling data from IODP and the legacy programs. SEDIS may later be expanded with harvest functions to allow incorporation of data and/or metadata from other geoscientific drilling programs, such as the International Scientific Continental Drilling Program (ICDP) and associated lake drilling programs, Antarctic drilling programs, etc. SEDIS is also intended to eventually make IODP data accessible for harvesting by other major geoscience data repositories, and by geoscientific data search engines (e.g., GEOSS, GEON, GEO Grid, Google Earth). However, this RFP only addresses ocean drilling data from DSDP, ODP and IODP, and their inclusion, display, and search functions within SEDIS. To meet the needs of integrating data from distributed IO and IODP-MI databases and providing centralized access across program data systems, IODP has undertaken development of SEDIS, a unified entry point for discovering and accessing IODP data. A phased approach to SEDIS development enables IODP-MI to build upon progress at IOs, in IODP-MI data systems, and within the SEDIS framework. The first phase of SEDIS consisted of development of a data inventory via a central metadata catalogue based on the ISO 19115 standard and ISO 19139 for its XML implementation. SEDIS I provides data discovery functionality via a searchable metadata catalogue of IODP data that is compliant with international metadata standards for structure (ISO 19115) and harvesting (Open Access Initiative—Protocol for Metadata Harvesting (OAI- PMH)) metadata. SEDIS I infrastructure harvests metadata from IOs and IODP-MI source systems. It is also a publicly harvestable metadata catalogue accessible to other scientific data networks. SEDIS I also established an internal Expedition database, with geospatial and 5
  6. 6. related data about IODP and legacy expeditions. SEDIS I provides an interface for text, controlled vocabulary, and geospatial searching of the metadata catalogue. The SEDIS I systems provides a web-based interface for end-users to perform data discovery across IODP data systems. SEDIS I metadata catalogue will eventually be expanded to include metadata from related geosciences programs (e.g., Intercontinental Drilling Program (ICDP), ANDRILL) to provide richer data discovery opportunities to the IODP community and the public. Figure 2, below, provides an overview of the IODP data flow from the collection of the drilling data through the harvesting and distribution of the metadata by SEDIS. Figure 2: IODP data flow and SEDIS I metadata framework For the purposes of SEDIS I metadata generation, a data set was defined as consisting of a grouping of data from one drill hole and one measurement type (e.g., physical properties, pore water chemistry, etc.). An example of a physical properties SEDIS data set is linked from SEDIS metadata and a data set DOI/URL is provided for clarity. This level of granularity is used for SEDIS metadata and is the level of granularity implied by the ―data set‖ within the SEDIS context. The definition is somewhat arbitrary, developed only for the purpose of managing SEDIS metadata generation. SEDIS data sets have been assigned DOIs at this ―data set‖ level of granularity and the DOI is an important attribute of SEDIS data because it supports the ―provenance‖ of data from its source when it is made available for potential publications. The second phase of SEDIS will be completed by 31 August 2009 and includes development of a searchable inventory of publications from the current and previous drilling programs. SEDIS II is based on a catalogue of IODP-related publications metadata and provides a keyword, controlled vocabulary, and geospatial search interface for retrieval of full text publications and links to publications-related data sets. SEDIS II performs full-text indexing of publications for rapid and accurate querying of publications based on keywords or text 6
  7. 7. strings. A core component of SEDIS II is a thesaurus of IODP and geoscientific terms to aid the system in returning appropriate results to search queries. The SEDIS thesaurus (site under development: http://sedis.iodp.org/thesaurus/index.php) is a dynamic collection of terms organized into a standard thesaurus schema, and the SEDIS thesaurus will be available for integration with all future SEDIS components. An admin interface for a SEDIS thesaurus entry is presented in Figure 3, below. Figure 3: SEDIS thesaurus (under development) administrative search interface IODP-MI maintains a Central Registry LDAP system used by several IODP-MI systems, including SEDIS. SEDIS II also includes a Publication Obligation Tracking System (POTS) to IODP staff in managing publication obligations associated with sample requests. SEDIS architecture tiers are presented in Figure 4, below, with Phase III and future deliverables presented as italicized text in gray. 7
  8. 8. Figure 4: SEDIS tiered architecture (Phase III and future deliverables in gray & italics) This request for proposals (RFP) seeks services for development and deployment of SEDIS Phase III components. A.3 ISSUING OFFICE Contractual questions should be e-mailed to: Technical questions should be directed to: John Emmitte Jamus Collier Contracts Officer Data Manager IODP-MI, Inc. IODP-MI Sapporo, Hokkaido University 815 Connecticut Avenue, NW, Suite 210 CRIS Bldg. 05-104 and 105 Washington, DC 20006 N21 W10, Kita-Ku, Sapporo, 001-0021 USA Japan E-mail: jemmitte@iodp.org E-mail: jcollier@iodp-mi-sapporo.org Phone: +1-202-465-7510 Phone: +81-11-738-1075 A.4 PROPOSAL DUE DATE Complete proposals must be received by the Issuing Office no later than the close of business on 28 September 2009 (5:30 P.M. Eastern U.S. DST) in order for the proposal to be considered. Late proposals will be disqualified from further consideration. IODP-MI‘s expected date for the selection of the SEDIS Phase III subcontractor is: 19 October 2009. The desired effective date of the resulting subcontract with IODP-MI is: 1 November 2009. 8
  9. 9. SEDIS Phase III shall be completed and delivered no later than 31 December 2010. Any information in the proposal that the offeror desires to claim as proprietary must be clearly designated. The only data that will be considered to be of a proprietary nature is commercial industry data. No proprietary science community data is allowable. Marking the entire proposal ―Confidential‖ will not be honored. Section K of this solicitation contains important information about the preparation of proposals for this acquisition. The offeror is expected to examine the schedule and all instructions in their entirety and to furnish all information required by this solicitation. A.5 VALIDITY OF PROPOSAL Proposals shall be valid for a minimum of 120 days after the proposal due date. A.6 REQUIREMENTS OF PROPOSAL Proposals must be provided with deliverables-based fixed-price budgets. Desired deliverables are described in Section C of this RFP. Vendors are allowed to propose alternate and/or additional deliverables. A fixed-price must be assigned to each deliverable proposed for development, and dependencies between proposed deliverables must be clearly stated. IODP-MI may select more than one proposal for a SEDIS III subcontract. IODP-MI reserves the right to select individual deliverables (or dependent deliverables) from the selected proposal(s) within the scope of the project, based on IODP-MI priorities, subsequent pre-contract discussions with the selected vendor(s), and the available budget for this project. (End of Section A) SECTION B - SUPPLIES OR SERVICES AND PRICES/COSTS B.1 SCOPE OF SUBCONTRACT Performance of this subcontract shall be in accordance with all terms, conditions and specifications as stipulated herein. B.2 TYPE OF SUBCONTRACT IODP-MI anticipates the award of a firm-fixed-price subcontract. (End of Section B) 9
  10. 10. SECTION C – STATEMENT OF WORK C.1 PROJECT OVERVIEW SEDIS development has been undertaken in a phased approach to accommodate the timeframes and fiscal year budgets of the IODP-MI. The scope of work for SEDIS III will apply only to SEDIS III components including, where necessary, integration with SEDIS I and II components. The proposal should indicate all work requiring integration with existing SEDIS infrastructure or components, including LDAP, session management, SEDIS website, SEDIS databases, SEDIS servers, etc. Technical documentation for existing SEDIS applications, LDAP and other IODP and IO systems will be provided to the selected vendor(s) during the project kickoff meetings. IODP-MI staff will facilitate timely communication with IODP-MI subcontractors, including existing systems hosting contractors and IOs. A brief description of Phases I and II of SEDIS will be provided in this section as background. Phase I: Provides the following capabilities: An inventory of IODP core and borehole logging data via a metadata catalog including legacy data (from previous drilling programs). IODP data has been organized into datasets that represent a measurement type (e.g., physical properties) from an individual drilling hole. An expedition catalog with dynamic mapping functionality for location viewing and searching tools A search engine for discovery of available core and bore hole data via tabular search results Metadata with links to the data returned as search results Map interface allowing display of coverages and geospatial searches on data sets. Result sets can also be export to KML files for display in Google Earth, etc. An OAI server to make metadata available to other geosciences metadata portals Expedition catalogue containing master SEDIS list of Expeditions, Sites, Holes, etc., geospatial information about the expeditions, and expedition metadata Phase II: Provides the following capabilities Publications catalogue with inventory using publications metadata. Program publications inventory for IODP, ODP and DSDP publications IODP-related publications published external to IODP and legacy programs Full text search of publications (HTML, PDF, etc.) from full-text indexed publications. A fast and sophisticated search engine allowing for simple as well as complex and full text retrievals of publications. Guided search functionality with coarse to fine grained grouping (classification) and filtering of publications allowing for a hierarchical or semi-hierarchical approach to the catalogue (e.g. leg -> site -> hole, or by keywords) Adjustable result sets configurable and tabular search result sets and display of detailed metadata for publications Map interface allowing display of coverages (locations + e.g. citations) and geospatial searches on publications. Result sets can also be export to KML files for display in Google Earth, etc. System Administration web-based front-end for system administration and update of metadata 10
  11. 11. C.2 FRAMEWORK FOR SEDIS III IODP-MI has managed development of framework systems in support of SEDIS III. These systems, currently under development, establish the foundation of SEDIS III development and will be described in this section. A fundamental design strategy of SEDIS III development is utilization of and Representational State Transfer (REST) approach to data delivery. REST is not a protocol or standard, but rather a style of software architecture for distributed hypermedia systems. The REST architecture style is based on resources referenced with a global identifier. In the context of SEDIS, a REST approach will mean that data are exposed by providers and delivered to requestor systems as resources with uniform resource identifiers (URI). One of the leading proponents of REST architecture describes the approach as follows: REST's client-server separation of concerns simplifies component implementation, reduces the complexity of connector semantics, improves the effectiveness of performance tuning, and increases the scalability of pure server components. Layered system constraints allow intermediaries—proxies, gateways, and firewalls—to be introduced at various points in the communication without changing the interfaces between components, thus allowing them to assist in communication translation or improve performance via large-scale, shared caching. REST enables intermediate processing by constraining messages to be self- descriptive: interaction is stateless between requests, standard methods and media types are used to indicate semantics and exchange information, and responses explicitly indicate cacheability.[Source] The advantages of REST include streamlined development, lightweight in terms of message packaging and markup, and scalability. Another significant advantage of REST in the context of SEDIS is the interoperability with IODP-MI and IOs existing data systems and the adoption of REST approaches in many of USIOs data management projects, including LIMS and Logging Database. IODP-MI is overseeing development of geospatial web services utilizing Open Geospatial Consortium (OGC) standards. The SEDIS OGC web services utilize SEDIS metadata to provide geospatial information. These web services will enable geospatially-enabled applications to discover and display geospatially the metadata for data sets from all IOs. By following the URIs to source data and metadata included in the SEDIS OGC web services, geospatial tools will be able to utilize SEDIS as a ―one-stop‖ source for discovery of data and access to the distributed data systems at the IOs and IODP-MI. The SEDIS OGC web services server supports both Simple Object Access Protocol/Web Services Description Language (SOAP/WSDL) and RESTful requests for data delivery. The SEDIS OGC web services are hosted separately from the SEDIS I and II metadata portal. Technical documentation for the SEDIS OGC web services based on SEDIS I metadata will be provided to the selected vendor(s) during the project kickoff meetings. Figure 5, below, provides an overview of the SEDIS OGC web services framework. 11
  12. 12. Figure 5: SEDIS OGC web services framework for SEDIS metadata IODP-MI has initiated development of OGC web services for Borehole Logging data from the Logging Database. This effort will include development of namespaces and vocabularies for borehole logging data from the 3 IOs borehole logging operations. These web services will be integrated with the GeoMapApp resource provider list in order to demonstrate applicability of a service-oriented approach for IODP data providers to make data available to community software application developers. Figure 6, below, presents an excerpt of a draft Simple Knowledge Management System (SKOS) metadata document describing borehole logging data in Resource Description Framework (RDF) format. 12
  13. 13. <rdf:RDF> −<skos:Concept rdf:about="http://brg.ldeo.columbia.edu/services/dict/#caliper"> −<skos:definition> A representation of the measured diameter of a borehole along its depth. </skos:definition> <skos:scopeNote rdf:resource="http://www.glossary.oilfield.slb.com/Display.cfm?Term=caliper%20log"/> <skos:prefLabel>caliper</skos:prefLabel> <skos:altLabel>caliper log</skos:altLabel> </skos:Concept> −<skos:Concept rdf:about="http://brg.ldeo.columbia.edu/services/dict/#density"> <skos:definition>Mass per unit of volume.</skos:definition> <skos:scopeNote rdf:resource="http://www.glossary.oilfield.slb.com/Display.cfm?Term=density"/> <skos:prefLabel>density</skos:prefLabel> <skos:altLabel>density log</skos:altLabel> </skos:Concept> −<skos:Concept rdf:about="http://brg.ldeo.columbia.edu/services/dict/#gamma%20ray"> <skos:definition>Total natural radioactivity.</skos:definition> <skos:scopeNote rdf:resource="http://www.glossary.oilfield.slb.com/Display.cfm?Term=gamma%20ray%20log"/> <skos:prefLabel>gamma ray</skos:prefLabel> <skos:altLabel>gamma ray log</skos:altLabel> </skos:Concept> … </rdf:RDF> Figure 6: Excerpt of draft SKOS metadata for borehole logging data (source: IODP-USIO) IODP-MI has initiated development of a reference implementation of SEDIS resource architecture as a basis and prototype for SEDIS III development. The SEDIS resource architecture reference implementation provides REST-based access to portions of JANUS and J-CORES data sources. As part of this implementation, IODP-MI will establish a documented a set of resources defining schemas, controlled vocabularies and namespaces for the serialization of a sub-set of data from Janus and J-CORES. These schemas, controlled vocabularies and namespaces, will be leveraged and adapted for providing web services access to all IODP data sources via SEDIS. A basic web-based parameterized search interface will be developed based on the XML schemas and the incorporated resources. The goals of this initiative are to establish the general framework (e.g., REST architecture style, schemas, namespaces, etc.,) for SEDIS III and provide proof-of-concept for utilizing SEDIS as a central location for providing stand-alone tools access to the distributed IODP data systems. Related to the development of IODP namespaces and schemas, IOs and IODP-MI are developing Resource Description Framework (RDF) documents using Simple Knowledge Management System (SKOS) to describe domains of related information relevant to IODP data sources. A major purpose the SKOS classifications is to categorize hierarchical terms used in IODP data, such as the measurement type ―Physical Properties‖, containing the subset of measurement parameters ―Density‖, which contains measurement components ―Density Bulk‖, ―Density Dry‖ and ―Density Grain‖. The SKOS vocabularies will be utilized for basic and advanced querying to enable either broad or exact returns for SEDIS search parameters. SKOS mappings for IODP information and terminologies will be accessible to the vendor for utilization in SEDIS III components. Technical documentation for IODP 13
  14. 14. namespaces, schemas, SKOS metadata, vocabularies and established schemas will be provided to the selected vendor(s) during project kickoff meetings. The current versions of IODP namespaces, RDF SKOS documents and controlled vocabularies should be considered alpha versions. The selected vendor(s) will be tasked to work with IOs and IODP-MI to finalize beta versions for SEDIS III implementation. Due to the evolving nature of IODP science and the data systems that support it, IODP namespaces, schemas, SKOS documents, controlled vocabularies, and the data systems themselves are likely to change over time. SEDIS III development is aimed at making significant increases in the accessibility of IODP data from analytical software tools and other data systems by releasing a functioning set of services, capabilities and documentation to enable software tool developers and other data systems to integrate with IODP data via SEDIS. Technical documentation for SEDIS, IODP-MI and IOs data systems will be provided to vendor(s) during project kickoff meeting and/or as they are requested become available. Selected technical documents for SEDIS, IODP-MI and IOs data systems are available for review by potential vendors via http://campanian.iodp-mi-sapporo.org/SEDIS_III_RFP/. Contact IODP-MI Data and Information Manager, Jamus Collier (jcollier@iodp-mi- sapporo.org) to request a username and password to access this background information directory. C.3 SCOPE OF WORK FOR SEDIS III The scope of work for SEDIS III development includes development of integrated data access services for IOs distributed data systems, mechanisms for: development of release versions of IODP namespaces, schemas, SKOS metadata and controlled vocabularies development of REST web services for delivery of XML-formatted data to service- enabled tools, including 3rd party analytical tools and SEDIS query interface importing additions and updates from source systems development of SEDIS parameterized querying services and interface development of a post-expedition data submission application project documentation. In this section, information and assumptions concerning project collaboration and meetings, the IOs source data systems, will be provided, followed by description of the additional development services required for successful implementation of SEDIS III. Project Collaboration and Meetings Due to the complexity of the IODP data systems and the SEDIS III project, there is a need for collaboration between IOs and IODP-MI and the selected vendor(s). The SEDIS III project will require an iterative workflow process that allows IODP-MI and IOs to review technical documents (e.g., technical requirements definitions, technical design documents, etc.) produced for this the project by the vendor. IODP-MI will coordinate information exchange between the vendor and IOs for review and acceptance of project planning, technical design materials and systems documentation. IODP-MI will convene two (2) meetings, of 2-3 days each, during the course of this contract to be attended by technical representatives from each IO, IODP-MI and the technical team from the vendor(s). IODP-MI will invite appropriate representatives from IOs, and possibly external applications developers responsible for important software tools utilized by the IODP 14
  15. 15. community (e.g., GeoMapApp). The vendor‘s travel costs for these meetings will be reimbursed by IODP-MI in accordance with the IODP-MI travel policy. In addition to the 2 technical meetings, IODP-MI will coordinate monthly videoconferences with IODP-MI, IOs and other invited participants. Due to the geographical distribution and the unique data systems of the IOs, vendors should anticipate up to six (6) hours per month of videoconference participation. Videoconferences utilize H.323 videoconference systems and may be hosted by IODP-MI or IOs. The purpose of these meetings and videoconferences is to ensure that necessary collaboration and knowledge transfer occurs between the IOs, IODP-MI and vendor(s). The development of namespaces is an example of a task that will require collaboration between the vendor and IOs to establish namespace elements and attributes common to all IODP data, identify outliers, and establish mappings between IOs source systems and the namespaces. Each of these tasks will be lead by, and the responsibility of, the vendor(s) but involvement of IOs and IODP-MI will be necessary to achieve appropriate integration of SEDIS III with source systems. USIO USIO regularly provides post-moratorium data to NGDC for archiving. SEDIS III will utilize the NGDC archived data sets (with SEDIS I metadata), via NGDC for integration with SEDIS. The primary and preferred source for SEDIS III access to USIO data will be NGDC World Data Center for Geophysics & Marine Geology archives. Sourcing data directly from USIO data systems may be necessary in some instances where the data resource does not exist in NGDC archives (e.g., ―hole splice‖ data sets). The format of the USIO core measurements data is delimited text. DOIs have been assigned to text files at a hole-measurement parameter level of granularity. The scope of work of SEDIS III includes development of services to expose the USIO core measurement data via REST web services. The REST web services must have resource end-points formatted as XML using namespaces, schemas and controlled vocabularies developed for the SEDIS web services reference implementation or accepted by IODP-MI. The REST web services must support transformations to allow querying via SEDIS or 3 rd party tools. Source data set DOIs must be associated with all XML data at a measurement result level for all XML data, including transforms resulting in aggregation of data from multiple source data sets. USIO borehole logging data maintained in a variety of file formats in the USIO Logging Database (e.g., http://brg.ldeo.columbia.edu/data/iodp-usio/exp301/U1301B/) and as REST web services (http://brg.ldeo.columbia.edu/services/). The scope of SEDIS III development will include providing access to USIO borehole logging data via SEDIS query functionality. USIO core photographs and digital images are maintained in a variety of file formats (http://iodp.tamu.edu/database/coreimages.html). Core photographs and digital images are accessible via NGDC and/or USIO web repositories. The scope of SEDIS III development will include providing access to USIO core photographs and digital images as resource end- points with IODP namespaced XML wrappers via the SEDIS query functionality. CDEX 15
  16. 16. CDEX maintains an archive of persistent J-CORES core measurement data (with SEDIS I metadata) in delimited text file format in J-CORES web repositories. DOIs have been assigned to text files at a hole-measurement parameter level of granularity. Within the scope of the SEDIS web services reference implementation, the J-CORES text files have been loaded to a schema-less database. Access to the J-CORES data will be provided as dynamic database views via a RESTful API. The scope of work of SEDIS III includes development of services to expose the CDEX core measurement data via REST web services. The REST web services must have resource end-points formatted as XML using namespaces, schemas and controlled vocabularies developed for the SEDIS web services reference implementation or accepted by IODP-MI. The REST web services must support transformations to allow querying via SEDIS or 3 rd party tools. Source data set DOIs must be associated with all XML data at a measurement result level for all XML data, including transforms resulting in aggregation of data from multiple source data sets. CDEX borehole logging data maintained in a variety of file formats in J-CORES Public Data Center web repositories. CDEX borehole logging data set metadata is managed by the LDEO Borehole Research Group, where it is provided to SEDIS and exposed as REST web services (http://brg.ldeo.columbia.edu/services/). The scope of SEDIS III development will include providing access to CDEX borehole logging data via SEDIS query functionality. CDEX core photographs and digital images are maintained in a variety of file formats in J- CORES Public Data Center web repositories. The scope of SEDIS III development will include providing access to CDEX core photographs and digital images as resource end- points with IODP namespaced XML wrappers via the SEDIS query functionality. ESO ESO maintains an archive of persistent core measurement data (with SEDIS I metadata) in the PANGAEA data system. PANGAEA is operated as an Open Access library aimed at archiving, publishing and distributing georeferenced data from earth system research. PANGAEA utilizes a relational database to makes data accessible via flat-files and web services. Within the PANGAEA database, DOIs have been assigned to data at a hole- measurement parameter level of granularity. The scope of work of SEDIS III includes development of services to integrate the PANGAEA core measurement data via REST web services. The REST web services will have resource end-points formatted as XML, and may require transformations to implement namespaces, schemas and controlled vocabularies developed for the SEDIS web services reference implementation or accepted by IODP-MI. Source data set DOIs are associated with all XML data at a measurement result level for all XML data, and must be persisted through all transformations resulting in aggregation of data from multiple source data sets. ESO borehole logging data maintained in a variety of file formats in WDC-MARE/PANGAEA (http://iodp.wdc-mare.org/front_content.php?idcat=122&count=10&q=logging) and USIO Log Database web repositories. ESO borehole logging data set metadata is provided to SEDIS and exposed as REST web services (http://brg.ldeo.columbia.edu/services/). The scope of SEDIS III development will include providing access to ESO borehole logging data via SEDIS query functionality. 16
  17. 17. ESO core photographs and digital images are maintained in a variety of file formats in WDC- MARE/PANGAEA web repositories (http://iodp.wdc- mare.org/front_content.php?idcat=122&count=10&q=citation:images). The scope of SEDIS III development will include providing access to ESO core photographs and digital images as resource end-points with IODP namespaced XML wrappers via the SEDIS query functionality. SEDIS III Services The primary goal of SEDIS III is to establish integrated service-oriented data delivery for all IODP scientific data so that users of service-enabled analytical software tools can readily discover and access the data. These data delivery services will be REST web services building upon the post-moratorium data in IO and IODP-MI data systems. Additional goals of SEDIS III include transformation services that will allow source data to be presented to users and tools in desired formats (e.g., MIME-types and schemas), query services that will provide SEDIS interfaces for parameterized querying that build upon the web services and transformations, data aggregation services that enable users to aggregate data from different data sets using the transformation services and algorithms developed to limit aggregation as agreed upon by domain specialists, and a data submission application for capturing post- moratorium data and making it discoverable and accessible within the SEDIS portal. Figure 7, below presents an illustrated schematic of SEDIS III services requested in this RFP. Figure 7: Schematic of SEDIS III services and functionality 17
  18. 18. C.4 SEDIS PHASE III REQUIREMENTS SUMMARY A primary goal of Phase III will be to expose IODP data as REST resources via SEDIS. This will enable service-enabled software tools to consider integrating with a centralized resource provider for discovery and access of all IODP scientific data. The SEDIS web services will also be utilized to provide parameterized query functionality via the SEDIS portal. TARGET USERS IODP-MI expects that SEDIS will be used to discover what data is available and where it is located. This will provide users with a single entry point to quickly find information about core and logging data that has been collected by multiple IODP contributors. The main users are expected to be: IODP Scientists, Technicians, Students, Curators, Managers External Researchers, Students Tools Developers (e.g., GeoMapApp, CoreWall, Google Earth) Public, Media Global geoscientific data networks (e.g., GEOSS, GEON, GEO Grid, Google Earth) DESIGN REQUIREMENTS IODP-MI needs to follow brand standards for the look of the SEDIS web site and the use of the IODP logo. IODP-MI will make the ―IODP Brand Standards‖ document available to the vendors. TECHNICAL AND INFRASTRUCTURE REQUIREMENTS Hosting A separate RFP or contract will address the server hosting of SEDIS III components. If a vendor proposes to host SEDIS III components as part of the SEDIS III contract, the terms of hosting services should be detailed in the proposal. IODP-MI will have full administration (root) access to the hosting server. SEDIS III components must be installed by the vendor on server(s) identified by IODP-MI. All software needed for SEDIS III components must be installed by the vendor. Domain name SEDIS sub-domain name: o http://sedis.iodp.org o IODP-MI is the owner of the iodp.org domain and will be responsible for maintaining an up-to-date registration Browser As a user and administrator, SEDIS needs to work on at least the 2 most recent release versions of the most common web browsers: Firefox Internet Explorer Safari 18
  19. 19. Other W3C XHTML 1.0 compliant web browser Platform SEDIS III components must be supported on the following common platforms: Microsoft Windows 2000, Windows Server 2003, XP, Vista Linux (all distributions) Unix (all versions) Mac (OS X 10+) System Vendors will need to provide a list of SEDIS software dependencies and hardware requirements for the hosting server. SEDIS III components are expected to use open source software, as appropriate: Operating system for the hosting server (e.g. Linux) Web server (e.g. Apache) Relational database (e.g. MySQL, PostgreSQL) or other methods of storing data and exposing web services resources as XML Schema-less database (e.g. CouchDB) and/or XML database (e.g. Berkeley DB) Geographic Information System (GIS) map server (e.g. GeoServer, OpenLayers, etc) Metadata IODP metadata for exists for data sets at a hole-measurement type (e.g., physical properties) level of granularity. Existing SEDIS metadata is compliant with the following standards: ISO 19115: for structure and content ISO 19139: for XML implementation of ISO 19115 XML 1.1 XML Schema (XSD) 1.0 SEDIS III components should comply with ISO 19115 standards, Dublin Core, Resource Description Framework in Attributes (RDFa) metadata, or another ISO or W3C standard (or proposed standard) for metadata. Web site and web services The SEDIS Phase III components should be compliant with the following standards, as applicable: XHTML 1.1 Cascading Style Sheet (CSS) 2.1 Web Content Accessibility Guidelines (WCAG) 1.0 Extensible Stylesheet Language (XSL) XSL 1.1 XSL Transformations (XSLT) 1.0 XML Schema Definition Language (XSD) 1.1 XForms 1.1 MIME Media Types OpenGIS standards o Web Feature Service (WFS) o Web Map Service (WMS) o Web Coverage Service (WCS) o KML 19
  20. 20. o GML in JPEG 2000 DOCUMENTATION REQUIREMENTS The selected vendor must provide IODP-MI detailed system documentation upon completion of user acceptance testing. The documentation must be provided in English. Documentation should cover at least: installation, maintenance, and administration of SEDIS III components. OTHER REQUIREMENTS Deploy web statistics package to monitor usage of the SEDIS III servers. Provide IODP-MI with a copy of all source code and web pages for SEDIS. IODP-MI will become the owner of the source code and SEDIS. Implement SEDIS authentication and authorization on SEDIS III components as identified by IODP-MI using IODP user registry (LDAP) and/or HTTP authentication methods approved by IODP-MI C.5 SEDIS III DELIVERABLES The deliverables in this section are requested for completion by the vendor(s) in the proposed scope of work of the SEDIS III contract. IODP-MI reserves the right to select proposed deliverables from the list below, or other deliverables proposed by the selected vendor(s), that can be accomplished within the available timeframe and budget of the SEDIS III contract. The deliverables in this section are listed in an approximate rank of the IODP-MI priority for completion should budgetary or other constraints prevent a contract from being signed for the entire set of deliverables. The deliverables have been divided into 3 categories. First Phase Deliverables are considered key achievements for SEDIS III as they underpin more advanced development of the SEDIS functionality. Second Phase Deliverables represent more advanced developments of SEDIS functionality that IODP-MI would like to achieve within SEDIS III scope of work. Administration, Documentation and Training Deliverables include administrative tools for SEDIS III deliverables, technical documentation and system administration training which should be scaled to the deliverables provided under this contract. Technical documentation for IODP-MI and external systems (e.g., IOs data systems) documentation will be provided as necessary by IODP-MI. First Phase SEDIS III Deliverables 1. Development of web services framework components for IODP data: Development of release versions (v.1) of IODP namespaces, schemas, SKOS metadata and controlled vocabulary. a. IODP namespace for IODP core measurements and borehole logging data web services must be developed using beta versions for JANUS and J- CORES as a source. WDC-MARE/PANGAEA data uses the same data elements as JANUS. b. XML schemas must be developed and implemented for core measurements and borehole logging data web services. 20
  21. 21. c. RDF SKOS metadata documents must be developed using beta versions for JANUS and J-CORES as a source. WDC-MARE/PANGAEA data uses the same data elements as JANUS. d. Controlled vocabulary dictionaries must be developed and implemented for core measurements and borehole logging data web services. 2. JANUS core measurement web services development and SEDIS integration: Development of web services for JANUS core measurements data using a REST approach to providing access to JANUS data resources. a. JANUS core measurements data web services must utilize data sources identified by IODP-MI, primarily and preferably NGDC archives. Potential alternate data sources include USIO data systems and the CHRONOS data system. b. JANUS core measurements data web services must provide RESTful resource URIs in XML format. c. JANUS core measurements data web services must implement IODP namespaces, schemas and vocabularies for XML resources. d. JANUS core measurements data web services must support querying multiple data sets using IODP SKOS vocabularies to retrieve relevant data. e. JANUS core measurements data web services must provide record-level association with source data set DOIs for XML resources. 3. WDC-MARE/PANGAEA core measurements web services development and SEDIS integration: Development of web services for WDC-MARE/PANGAEA core measurements data using a REST approach to providing access to WDC- MARE/PANGAEA data resources. a. WDC-MARE/PANGAEA core measurements data web services must utilize data sources identified by IODP-MI. The data source will be WDC- MARE/PANGAEA. b. Development of SEDIS web services will likely build upon existing web services of WDC-MARE/PANGAEA, and the bulk of effort of this deliverable is expected to be development of transformations from WDC-MARE/PANGAEA namespaces and schemas to IODP namespaces and schemas. c. WDC-MARE/PANGAEA core measurements data web services must provide RESTful resource URIs in XML format. d. WDC-MARE/PANGAEA core measurements data web services must implement IODP namespaces, schemas and vocabularies for XML resources. e. WDC-MARE/PANGAEA core measurements data web services must support querying multiple data sets using IODP SKOS vocabularies to retrieve relevant data. f. WDC-MARE core measurements data web services must provide record-level association with source data set DOIs for XML resources. 4. J-CORES core measurements web services development and SEDIS integration: Development of web services for J-CORES core measurements data using a REST approach to providing access to J-CORES data resources. a. J-CORES core measurements data web services must utilize data sources identified by IODP-MI. Potential data sources include J-CORES Public Data Center and a schema-less database hosted by IODP-MI. b. J-CORES core measurements data web services must provide RESTful resource URIs in XML format. 21
  22. 22. c. J-CORES core measurements data web services must implement IODP namespaces, schemas and vocabularies for XML resources. d. J-CORES core measurements data web services must support querying multiple data sets using IODP SKOS vocabularies to retrieve relevant data. e. J-CORES core measurements data web services must provide record-level association with source data set DOIs for XML resources. 5. USIO LIMS core measurements web services development and SEDIS integration: Development of web services for USIO data using a REST approach to providing access to USIO LIMS core measurements data resources. a. USIO LIMS core measurements data web services must utilize data sources identified by IODP-MI, primarily and preferably NGDC archives. Potential alternate data sources include USIO data systems, USIO data systems and the CHRONOS data system. b. USIO LIMS core measurements data web services must provide RESTful resource URIs in XML format. c. USIO LIMS core measurements data web services must implement IODP namespaces, schemas and vocabularies for XML resources. d. USIO LIMS core measurements data web services must support querying multiple data sets using IODP SKOS vocabularies to retrieve relevant data. e. USIO LIMS core measurements data web services must provide record-level association with source data set DOIs for XML resources. 6. Borehole Logging web services development and SEDIS integration: Development of web services for USIO, CDEX and ESO borehole logging data using a REST approach to providing access to IODP borehole logging data resources. a. Borehole logging data web services must utilize data sources identified by IODP-MI. Potential data sources include NGDC archives, USIO Log Database, J-CORES Public Data Center, and WDC-MARE/PANGAEA. b. Borehole logging data web services must provide RESTful resource URIs with XML-formatted wrappers for borehole logging data files, or processed log data converted to ASCII in XML format. c. Borehole data web services must implement IODP namespaces, schemas and vocabularies for XML resources. d. Borehole data web services must support querying multiple data sets using IODP SKOS vocabularies to retrieve relevant data. e. Borehole logging data web services must provide record-level and/or file-level association with source data set DOIs for XML resources. 7. Core photographs and digital images web services development and SEDIS integration: Development of mechanisms for exposing USIO, CDEX and core photographs and digital images (e.g., high-resolution photographs, close-ups, visual core descriptions, line scans, etc.) as web services using a REST approach to providing access to IODP core photograph and digital image data resources. IODP- MI will work with vendor to identify digital image data that is suitable for delivery as REST resource endpoints. a. Core photographs and digital images web services must utilize data sources identified by IODP-MI. Potential data sources include USIO archives, JANUSweb, J-CORES Public Data Center, and WDC-MARE/PANGAEA. b. Core photographs and digital images web services must provide RESTful resource URIs with XML-formatted wrappers for core photographs and digital 22
  23. 23. images data files, or implement embedded metadata approach that includes an automated process for creating JPEG 2000 images with embedded XML metadata. c. Core photographs and digital images web services must implement IODP namespaces, schemas and vocabularies for XML resources. d. Core photographs and digital images web services must support querying multiple data sets using IODP SKOS vocabularies to retrieve relevant data. e. Core photographs and digital images web services must provide record-level and/or file-level association with source data set DOIs. Second Phase SEDIS III Deliverables 8. SEDIS data transformation services: Development of transformation services capable of transforming and exporting SEDIS III core measurements data in a variety of pre- define formats and schemas. a. SEDIS data transformation services must be capable of transforming SEDIS XML data formats to .xls/.xlsx, delimited text (e.g., comma separated values, tab delimited text, custom delimiters), KML. b. SEDIS data transformation services should be capable of transforming SEDIS XML to appropriate geoscientific data formats, such as GML-compliant XML, GeoSciML, etc. c. SEDIS data transformation services must incorporate MIME types and support HTTP Accept request header specifications to enable identification of supported applications and their association with pre-defined data formats and schemas. d. SEDIS data transformation services must be integrated with SEDIS parameterized query services web interface to enable export of returned search results data in appropriate formats. 9. SEDIS parameterized query interface and functionality: Development of a SEDIS query services capable of searching SEDIS III source data systems using IODP SKOS vocabularies to retrieve relevant data. a. SEDIS query services must include a web-based parameterized query interface that is integrated with source data system web services developed for SEDIS III to deliver search results from distributed source systems. b. SEDIS query services returns must be structured as XML and should be transformed to XHTML for tabular display in web pages. c. SEDIS query services web interface ―basic‖ search results must be displayed in a formatted text table with clear headers labeling each column. The default return format should include Expedition, Site, Hole, source data set file names, source system, file size, as well as links to access the data set and metadata. d. The web-based query interface should provide functionality of expanding each search result data set to a web-based tabular format with column headers to view the data. e. SEDIS parameterized query services should have capabilities to allow at least the following parameters to be used as search criteria: o controlled vocabulary parameters (e.g., carbonate, density) using IODP SKOS vocabularies to correlate terms 23
  24. 24. o numeric measurement values (e.g., measured observation values less than, greater than or within a numerical range) o depth (e.g., depth values less than, greater than or within a numerical range) o age (e.g., age values less than, greater than or within a numerical range, geological age) o lithology (e.g., gabbro) o paleontology (e.g., phylum, class, order, genus, species) 10. SEDIS file submission application: Development of a SEDIS data file submission application enabling post-expedition and post-moratorium data sets to be submitted to SEDIS for archiving and inclusion in SEDIS source data inventories. a. SEDIS data file submission application must include a web-based interface for uploading data file and collecting or uploading SEDIS metadata on submitted data sets. b. SEDIS data file submission application must be integrated with IODP DOI registration service. Submitted data files and metadata should be stored on SEDIS III component server(s) and the data set should be assigned a DOI using the IODP DOI registration service. SEDIS administrator(s) must approve submitted data files before files are assigned a DOI and made available via the SEDIS metadata catalogue and source data inventory. Data sets with resolvable DOIs provided in metadata should retain the provided DOI. c. Data files submitted to SEDIS in SEDIS defined formats and schemas should be transformed into XML format using IODP namespaces, schemas and controlled vocabularies. d. Data set submission application must be integrated with IODP user registry (LDAP) and implement user authentication and authorization. e. SEDIS data file submission application must employ appropriate file scanning software to detect and prevent or quarantine malicious uploads. 11. SEDIS data aggregation services: Development of transformation and aggregation services with capabilities allowing transformations of various IODP core measurements schemas and borehole logging data to identified ―common‖ IODP schemas and namespaces. a. SEDIS data aggregation services must be integrated with SEDIS parameterized query services, as well as being accessible to service-enabled 3rd party tools. b. SEDIS data aggregation services must transform core measurements data from all SEDIS III data sources into XML formatted data using schemas and namespaces identified by IODP-MI and based on established IODP-MI schemas, namespaces and SKOS vocabularies. c. SEDIS data aggregation services must warn web-based interface users that aggregated data may not be internally consistent (i.e., the measurement values for the same parameters may not be equivalent at the record level for records sourced from different data sets). The final wording of the user warning will be provided by IODP-MI. d. SEDIS data aggregation services must implement administratively modifiable algorithms for control of data aggregation and transformation processes. These algorithms will control the applicability of aggregation queries to specific data types and data sets, for instance limiting data set aggregation from different timeframes, vessels, expeditions, etc. 24
  25. 25. e. SEDIS data aggregation services must provide record-level source data set DOIs. Administration, Documentation and Training SEDIS III Deliverables 1. Administration tools: Development of web-based interfaces for administration of SEDIS III components. a. Administration tools must provide an interface for reviewing and accepting or rejecting submitted data and metadata. b. Administration tools must provide an interface for expanding SEDIS the library of SEDIS schemas, namespaces, SKOS vocabularies, etc. c. Administration tools must provide an interface for expanding MIME-type application associations for SEDIS web services. d. Administration tools must provide an interface for managing authentication and authorization for SEDIS III components not implementing those processes via the IODP user registry. e. Administration tools must include web statistics interface to allow SEDIS administrator(s) to monitor usage of SEDIS III components. 2. Technical Documentation: Technical documentation of SEDIS III system components, including servers, source code, applications, backup and restore procedures. a. Written technical descriptions of SEDIS III system components describing hosting, installation, operation, maintenance, backup and restore requirements/recommendations must be developed. b. Technical documentation of the system (e.g., technical requirements definitions, system design documents, etc.) developed during the development phase must be compiled for project technical documentation package. c. Description of SEDIS III production infrastructure, including diagrams, must be developed to document SEDIS III deployment configuration. d. Source code, in both compiled and un-compiled forms, must be provided with comments for administrator. 3. Administrator Training: Technical training for SEDIS III administrator(s), including installation, operation, maintenance, backup and restore procedures. a. Two-day of technical training sessions focusing on system operation and maintenance must be provided for SEDIS administrator(s). b. Training materials must be developed by vendors and made available as an appendix to the project technical documentation package. (End of Section C) 25
  26. 26. SECTION D – PACKAGING AND MARKING D.1 PACKAGING AND MARKING Unless otherwise specified and as applicable, all items shall be packaged and packed in accordance with normal commercial practices. If magnetic media is involved, packaging shall be clearly marked identifying the contents as such and with a warning for protection against exposure to magnetic fields or temperature extremes. (End of Section D) SECTION E – INSPECTION AND ACCEPTANCE E.1 NOTICE LISTING CLAUSES INCORPORATED BY REFERENCE Federal Acquisition Regulations (48 CFR Chapter 1) Clauses 52.246-2 INSPECTION OF SUPPLIES – FIXED PRICE AUG 1996 52.246-4 INSPECTION OF SERVICES – FIXED PRICE AUG 1996 E.2 EVALUATION AND ACCEPTANCE Evaluation and acceptance of supplies and services delivered under this subcontract shall be performed by IODP-MI. (End of Section E) SECTION F - DELIVERIES OR PERFORMANCE F.1 NOTICE LISTING CLAUSES INCORPORATED BY REFERENCE Federal Acquisition Regulations (48 CFR Chapter 1) Clauses 52.242-15 STOP-WORK ORDER ALT I AUG 1989 F.2 PERIOD OF PERFORMANCE This resulting subcontract with the selected vendor shall commence when formally executed by both parties and shall expire no later than 31 December 2010. 26
  27. 27. F.3 REPORTING REQUIREMENTS This section identifies the technical, administrative, and financial reports required under the resulting subcontract. The list of reports is subject to revision as program developments dictate. The reports will be subject to review and approval by IODP-MI. The precise format of the reports shall be promulgated by IODP-MI. Quarterly Operations and Management Report. The vendor shall prepare and submit a quarterly operations and management report (progress report) to IODP-MI, which shall include a comparison of actual accomplishments with planned accomplishments. All quarterly reporting shall show the status of all major events and activities as identified in this solicitation and the resulting subcontract. The progress report shall present in narrative format a summary of all work performed during the quarter, including technical status, accomplishments, problems encountered, future plans for the upcoming period, and any action required on the part of IODP-MI. The report shall be submitted within 30 days following the end of the reporting period. Final Operations and Management Report. Within sixty (60) days of completion of the subcontract, the subcontractor shall prepare and submit a final technical report summarizing contributions to the IODP during the subcontract performance period. The format shall be developed by the subcontractor and approved by IODP-MI. Special Reports. The subcontractor will submit periodic special reports as IODP-MI may request from time to time. (End of Section F) SECTION G - SUBCONTRACT ADMINISTRATION DATA G.1 INVOICE AND PAYMENT INFORMATION In order to initiate payment following the execution of the resulting subcontract, the subcontractor shall submit invoices for payment in accordance with the schedule agreed to by the parties and incorporated in the resulting subcontract. G.2 CONTRACTING AUTHORITY The following individuals are the only personnel authorized to contractually bind the parties of this subcontract: Kiyoshi SUYEHIRO, President [OFFEROR MUST PROVIDE NAME & TITLE] IODP Management International, Inc. [ORGANIZATION] 27
  28. 28. G.3 SUBCONTRACTOR TECHNICAL REPRESENTATIVES The following individuals are authorized to provide programmatic approval for the subcontractor and administer the performance of work under this subcontract: [Offeror Must Provide Name(s), Title(s), Organization(s)] In no event, however, will any understanding, agreement, modification, change order, or other matter deviating from the terms of this subcontract be effective or binding upon IODP- MI unless formalized by contractual documents executed by the individuals designated in Section G.3. G.4 OTHER NOTICES 1. IODP-MI reserves the right to reject any or all proposals for this service without penalty following the review and evaluation of the proposals received. 2. IODP-MI may request additional information from an offeror. 3. Neither this solicitation nor the submission of any proposal creates any contract or obligation on the part of IODP-MI. 4. All proposals submitted become the property of IODP-MI. 5. Subcontractor selection may be made solely upon the review of the written proposal; therefore, offerors are cautioned to ensure that the written proposals are as complete, detailed, and thorough as possible, and that it thoroughly addresses the capability to satisfy the requirements of this RFP. IODP-MI reserves the right to select any proposal(s) as a basis for contract negotiation or to accept other than the lowest offer. (End of Section G) SECTION H - SPECIAL SUBCONTRACT REQUIREMENTS H.1 LIABILITY INSURANCE The subcontractor warrants that insurance coverage (currently in force) exists in the following areas and in amounts not less than those specified below: Type Per Coverage Insurance Person Property Per Accident 1. Comprehensive General Liability $500,000 $500,000 $1,000,000 2. Automobile $500,000 $500,000 $1,000,000 3. A supplemental umbrella policy for $5,000,000. 4. Worker's Compensation - As required by law at the job site. 28
  29. 29. The Comprehensive general and automobile liability policies shall contain a provision worded as follows: "The insurance company waives any right of subrogation against the United States of America which may arise by reason of any payment under the policy." The subcontractor shall file with the IODP-MI Contracts Officer prior to beginning performance under this subcontract, a copy of a certificate of insurance evidencing the above coverage. The subcontractor shall provide to the IODP-MI Contracts Officer within five (5) days after occurrence, notice of cancellation of or reductions below the above cited amounts of any insurance coverage related to this requirement. The subcontractor warrants that such insurance coverage for all lower-tier subcontractors who will work at any of the sites of performance does or will exist before said lower-tier subcontractors begin performance. H.2 INDEMNIFICATION The subcontractor shall indemnify IODP-MI against any claims for loss or damage to any property or injury or death to any person, during the course of the work, attributable to the negligence of the subcontractor or its employees. IODP-MI shall similarly hold the subcontractor harmless for any such claims attributable to the negligence of IODP-MI or its employees. H.3 LIMITED USE OF DATA AND INFORMATION Performance of this subcontract may require the subcontractor to access data and information proprietary to a government agency or government contractor and/or such a nature that its dissemination or use, other than in performance of this subcontract, would be adverse to the interest of the government and/or others. Subcontractor personnel shall not divulge or release data or information developed or obtained in performance of this subcontract, until made public by IODP-MI or the government, except to authorized personnel or upon written approval of the IODP-MI Contracts Officer. The subcontractor shall not use, disclose or reproduce proprietary data that bears a restrictive legend, other than as required in the performance of this subcontract. Nothing herein shall preclude the use of any data independently acquired by the subcontractor without such limitations or prohibit an agreement at no cost to IODP-MI between the subcontractor and the data owner which provides for greater rights to the subcontractor. H.4 CLEARANCE AND CONSTRAINTS Notwithstanding any other provision of this subcontract, at any point in the conduct of this project where IODP-MI approval is required, IODP-MI will endeavor to notify the subcontractor within ten (10) working days of receipt of a subcontractor‘s request as to its approval or disapproval. Failure of IODP-MI to respond within the ten (10) working day period shall NOT constitute approval. 29
  30. 30. H.5 SUBCONTRACT MONITORING In monitoring the subcontractor‘s performance, IODP-MI is primarily interested in progress toward successful completion of the specified requirements and the financial status of the subcontract. During the course of performance of the resulting subcontract, IODP-MI may conduct a site visit to review the progress of work or the management control systems of the subcontractor or its lower-tier subcontractors. The subcontractor shall provide and shall require its lower-tier subcontractors to provide all reasonable facilities and assistance for the safety and convenience of the representatives in the performance of their duties. Such access shall include the right to inspect the subcontractor's financial accounts or records that pertain to this subcontract. As part of the monitoring effort, the subcontractor shall submit a copy of its most recent annual A-133 audit report to IODP-MI (if applicable). (End of Section H) SECTION I - SUBCONTRACT CLAUSES I.1 52.252-2 CLAUSES INCORPORATED BY REFERENCE (FEB 1998) This solicitation incorporates one or more clauses by reference, with the same force and effect as if they were given in full text. The full text of a clause may be accessed electronically at http://acquisition.gov/far/index.html. All clauses contained in this solicitation and any resulting subcontract shall be appropriately interpreted to generally reflect the identities of the instant parties, i.e., substitute ―Prime Contractor (IODP-MI)‖ for ―Government;‖ ―Subcontractor‖ for ―Contractor;‖ and ―subcontract‖ for ―contract,‖ etc. NOTICE LISTING CLAUSES INCORPORATED BY REFERENCE Federal Regulations (48 CFR Chapter 1) Clauses 52.202-1 DEFINITIONS JUL 2004 52.203-3 GRATUITIES APR 1984 52.203-5 COVENANT AGAINST CONTINGENT FEES APR 1984 52.203-6 RESTRICTIONS ON SUBCONTRACTOR SALES SEP 2006 TO THE GOVERNMENT 52.203-7 ANTI-KICKBACK PROCEDURES JUL 1995 52.203-8 CANCELLATION, RECISSION, AND RECOVERY JAN 1997 OF FUNDS FOR ILLEGAL OR IMPROPER ACTIVITY 52.203-10 PRICE OR FEE ADJUSTMENT FOR ILLEGAL JAN 1997 30
  31. 31. OR IMPROPER ACTIVITY 52.203-11 CERTIFICATION AND DISCLOSURE REGARDING SEP 2007 PAYMENTS TO INFLUENCE CERTAIN FEDERAL TRANSACTIONS 52.203-12 LIMITATION ON PAYMENTS TO INFLUENCE SEP 2007 CERTAIN FEDERAL TRANSACTIONS 52.204-4 PRINTING/COPYING DOUBLE-SIDED ON AUG 2000 RECYCLED PAPER 52.204-7 CENTRAL CONTRACTOR REGISTRATION APR 2008 52.204-8 ANNUAL REPRESENTATIONS AND CERTIFICATIONS FEB 2009 52.209-5 CERTIFICATION REGARDING RESPONSIBILITY DEC 2008 MATTERS 52.209-6 PROTECTING THE GOVERNMENT'S SEP 2006 INTEREST WHEN SUBCONTRACTING WITH CONTRACTORS DEBARRED, SUSPENDED, OR PROPOSED FOR DEBARMENT 52.214-4 FALSE STATEMENTS IN BIDS APR 1984 52.214-6 EXPLANATION TO PROSPECTIVE BIDDERS APR 1984 52.214-12 PREPARATION OF BIDS APR 1984 52.215-2 AUDIT AND RECORDS—NEGOTIATION MAR 2009 52.215-8 ORDER OF PRECEDENCE – UNIFORM CONTRACT OCT 1997 FORMAT 52.219-8 UTILIZATION OF SMALL BUSINESS CONCERNS MAY 2004 52.222-3 CONVICT LABOR JUN 2003 52.222-26 EQUAL OPPORTUNITY MAR 2007 52.222-29 NOTIFICATION OF VISA DENIAL JUN 2003 52.222-35 EQUAL OPPORTUNITY FOR SPECIAL DISABLED SEP 2006 VETERANS, VETERANS OF THE VIETNAM ERA, AND OTHER ELIGIBLE VETERANS 52.222-36 AFFIRMATIVE ACTION FOR WORKERS WITH JUN 1998 DISABILITIES 52.222-37 EMPLOYMENT REPORTS ON SPECIAL SEP 2006 31
  32. 32. DISABLED VETERANS, VETERANS OF THE VIETNAM ERA, AND OTHER ELIGIBLE VETERANS 52.222-38 COMPLIANCE WITH VETERANS‘ EMPLOYMENT DEC 2001 REPORTING REQUIREMENTS 52.223-6 DRUG-FREE WORKPLACE MAY 2001 52.225-13 RESTRICTIONS ON CERTAIN FOREIGN JUN 2008 PURCHASES 52.227-1 AUTHORIZATION AND CONSENT DEC 2007 52.227-2 NOTICE AND ASSISTANCE REGARDING DEC 2007 PATENT AND COPYRIGHT INFRINGEMENT 52.227-14 RIGHTS IN DATA – GENERAL, ALT IV DEC 2007 The foreign members of the IODP are hereby granted the same rights in data as the U.S. Government under this clause. 52.229-6 TAXES – FOREIGN FIXED-PRICE CONTRACTS JUN 2003 52.230-2 COST ACCOUNTING STANDARDS OCT 2008 52.230-6 ADMINISTRATION OF COST ACCOUNTING MAR 2008 STANDARDS 52.232-8 DISCOUNTS FOR PROMPT PAYMENT FEB 2002 52.232-17 INTEREST OCT 2008 52.232-23 ASSIGNMENT OF CLAIMS JAN 1986 52.233-1 DISPUTES ALT I JUL 2002 52.233-3 PROTEST AFTER AWARD-ALT I (JUNE 1985) AUG 1996 52.237-3 CONTINUITY OF SERVICES JAN 1991 52.242-4 CERTIFICATION OF FINAL INDIRECT COSTS JAN 1997 52.242-13 BANKRUPTCY JUL 1995 52.243-1 CHANGES - FIXED-PRICE – ALT I AUG 1987 52.244-2 SUBCONTRACTS JUN 2007 Subparagraph (e) requirements for consent are identified as follows: Any Competitive subcontract in excess of $50,000 Any Sole Source subcontract in excess of $25,000 52.244-6 SUBCONTRACTS FOR COMMERCIAL ITEMS MAR 2009 32
  33. 33. 52.246-25 LIMITATION OF LIABILITY – SERVICES FEB 1997 52.247-63 PREFERENCE FOR US-FLAG AIR CARRIERS JUN 2003 52.248-1 VALUE ENGINEERING FEB 2000 52.249-2 TERMINATION FOR CONVENIENCE OF THE MAY 2004 GOVERNMENT (FIXED-PRICE) 52.251-1 GOVERNMENT SUPPLY SOURCES APR 1984 I.2 NSF ACQUISITION REGULATION-CLAUSE(S) INCORPORATED BY FULL TEXT 1) RIGHTS IN DATA (APR 1984) (a) Subject Data (i) The term "Subject Data" as used herein includes writings, information stored in any form, sound recordings, computer programs, pictorial reproductions, drawings, or other graphic representations and works of any similar nature which are first generated, produced or composed in the performance of this contract, whether delivered or not under this contract. (b) Other Data (i) The term "Other Data" as defined herein includes writings, information stored in any form, sound recordings, computer programs, pictorial reproductions, drawings, or other graphic representations and works of any similar nature, not generated, produced, or composed for the first time in the performance of this contract, whether or not copyrighted, which are delivered under this contract. (ii) The Government may duplicate, use and disclose in any manner and for any purpose whatsoever, and have others so do, all or any part of the Other Data delivered by the Contractor to the Government under this contract except as provided by subparagraph (b)(ii)(A) below. (A) Material Covered by Copyright. The Contractor agrees to and does hereby grant to the Government, and to its officers, agents, and employees acting within the scope of their official duties, a royalty-free, non-exclusive and irrevocable license, throughout the world for Government purposes to publish, translate, reproduce, deliver, perform, dispose of, and to authorize others to do so, all Other Data now or hereafter covered by copyright. No such copyrighted matter shall be included in Other Data furnished hereunder without the written permission of the copyright owner for the Government to use such copyrighted matter in the manner described in this subparagraph (b)(ii)(A). (c) The terms "Subject Data" and "Other Data" as defined herein do not include financial reports, cost analyses and similar information incidental to contract administration. 33
  34. 34. (d) The Contractor shall report to the Government promptly and in reasonable written detail each notice or claim of copyright infringement received by the Contractor with respect to any technical data delivered hereunder. 2) PATENT RIGHTS (a) Definitions--(1) Invention means any invention or discovery which is or may be patentable or otherwise protectable under title 35 of the United States Code, to any novel variety of plant which is or may be protected under the Plant Variety Protection Act (7 U.S.C. 2321 et seq.). (2) Subject invention means any invention of the contractor conceived or first actually reduced to practice in the performance of work under this contract, provided that in the case of a variety of plant, the date of determination (as defined in section 41(d) of the Plant Variety Protection Act (7 U.S.C. 2401(d)) must also occur during the period of contract performance. (3) Practical application means to manufacture in the case of a composition or product, to practice in the case of a process or method, or to operate in the case of a machine or system; and, in each case, under such conditions as to establish that the invention is being utilized and that its benefits are to the extent permitted by law or Government regulations available to the public on reasonable terms. (4) Made when used in relation to any invention means the conception or first actual reduction to practice of such invention. (5) Nonprofit organization means a domestic university or other institution of higher education or an organization of the type described in section 501(c)(3) of the Internal Revenue Code of 1954 (26 U.S.C. 501(c)) and exempt from taxation under section 501(a) of the Internal Revenue Code (26 U.S.C. 501(a)) or any domestic nonprofit scientific or educational organization qualified under a State nonprofit organization statute. (b) Allocation of Principal Rights. The contractor may retain the entire right, title, and interest throughout the world to each subject invention subject to the provisions of this Patents Rights clause and 35 U.S.C. 203. With respect to any subject invention in which the contractor retains title, the Federal Government shall have a nonexclusive, nontransferable, irrevocable, paid-up license to practice or have practiced for or on behalf of the United States the subject invention throughout the world. If the award indicates it is subject to an identified international agreement or treaty, the National Science Foundation (NSF) also has the right to direct the contractor to convey to any foreign participant such patent rights to subject inventions as are required to comply with that agreement or treaty. (c) Invention Disclosure, Election of Title and Filing of Patent Applications by Contractor. (1) The contractor will disclose each subject invention to NSF within two months after the inventor discloses it in writing to contractor personnel responsible for the administration of patent matters. The disclosure to NSF shall be in the form of a written report and shall identify the contract under which the invention was made and the inventor(s). It shall be sufficiently complete in technical detail to convey a clear understanding of the nature, purpose, operation, and, to the extent known, the physical, chemical, biological or electrical characteristics of the invention. The disclosure shall also identify any publication, on sale or public use of the invention and whether a manuscript describing the invention has been submitted for publication and, if so, whether it has been accepted for publication at 34
  35. 35. the time of disclosure. In addition, after disclosure to NSF, the contractor will promptly notify NSF of the acceptance of any manuscript describing the invention for publication or of any on sale or public use planned by the contractor. (2) The contractor will elect in writing whether or not to retain title to any such invention by notifying NSF within two years of disclosure to NSF. However, in any case where publication, on sale, or public use has initiated the one year statutory period wherein valid patent protection can still be obtained in the United States, the period for election of title may be shortened by NSF to a date that is no more than 60 days prior to the end of the statutory period. (3) The contractor will file its initial patent application on an invention to which it elects to retain title within one year after election of title or, if earlier, prior to the end of any statutory period wherein valid patent protection can be obtained in the United States after a publication, on sale, or public use. The contractor will file patent applications in additional countries or international patent offices within either ten months of the corresponding initial patent application, or six months from the date when permission is granted by the Commissioner of Patents and Trademarks to file foreign patent applications when such filing has been prohibited by a Secrecy Order. (4) Requests for extension of the time for disclosure to NSF, election, and filing under subparagraphs (c) (1), (2), and (3) of this clause may, at the discretion of NSF, be granted. (d) Conditions When the Government May Obtain Title. The contractor will convey to NSF, upon written request, title to any subject invention: (1) If the contractor fails to disclose or elect the subject invention within the times specified in paragraph (c) above, or elects not to retain title; provided that NSF may only request title within 60 days after learning of the failure of the contractor to disclose or elect within the specified times. (2) In those countries in which the contractor fails to file patent applications within the times specified in paragraph (c) above; provided, however, that if the contractor has filed a patent application in a country after the times specified in paragraph (c) above, but prior to its receipt of the written request of NSF, the contractor shall continue to retain title in that country. (3) In any country in which the contractor decides not to continue the prosecution of any application for, to pay the maintenance fees on, or defend in a reexamination or opposition proceeding on, a patent on a subject invention. (e) Minimum Rights to Contractor. (1) The contractor will retain a nonexclusive royalty-free license throughout the world in each subject invention to which the Government obtains title, except if the contractor fails to disclose the subject invention within the times specified in paragraph (c) above. The contractor's license extends to its domestic subsidiaries and affiliates, if any, within the corporate structure of which the contractor is a party and includes the right to grant sublicenses of the same scope to the extent the contractor was legally obligated to do so at the time the contract was awarded. The license is transferable only with the approval of NSF except when transferred to the successor of that part of the contractor's business to which the invention pertains. (2) The contractor's domestic license may be revoked or modified by NSF to the extent necessary to achieve expeditious practical application of the subject invention pursuant to an application for an exclusive license submitted in accordance with applicable provisions at 37 CFR part 404. This license will not be revoked in that field of use or the geographical areas in which the contractor has achieved practical application and continues to make the benefits of the invention reasonably accessible to the public. The license in any foreign country may be revoked or modified at the discretion of NSF to the extent the contractor, its licensees, or its 35
  36. 36. domestic subsidiaries or affiliates have failed to achieve practical application in that foreign country. (3) Before revocation or modification of the license, NSF will furnish the contractor a written notice of its intention to revoke or modify the license, and the contractor will be allowed thirty days (or such other time as may be authorized by NSF for good cause shown by the contractor) after the notice to show cause why the license should not be revoked or modified. The contractor has the right to appeal, in accordance with applicable regulations in 37 CFR part 404 concerning the licensing of Government-owned inventions, any decision concerning the revocation or modification of its license. (f) Contractor Action to Protect Government's Interest. (1) The contractor agrees to execute or to have executed and promptly deliver to NSF all instruments necessary to: (i) Establish or confirm the rights the Government has throughout the world in those subject inventions for which the contractor retains title, and (ii) Convey title to NSF when requested under paragraph (d) above, and to enable the Government to obtain patent protection throughout the world in that subject invention. (2) The contractor agrees to require, by written agreement, its employees, other than clerical and non-technical employees, to disclose promptly in writing to personnel identified as responsible for the administration of patent matters and in a format suggested by the contractor each subject invention made under this contract in order that the contractor can comply with the disclosure provisions of paragraph (c) above, and to execute all papers necessary to file patent applications on subject inventions and to establish the Government's rights in the subject inventions. The disclosure format should require, at a minimum, the information requested by paragraph (c)(1) above. The contractor shall instruct such employees through the employee agreements or other suitable educational programs on the importance of reporting inventions in sufficient time to permit the filing of patent applications prior to U.S. or foreign statutory bars. (3) The contractor will notify NSF of any decision not to continue prosecution of a patent application, pay maintenance fees, or defend in a reexamination or opposition proceeding on a patent, in any country, not less than thirty days before the expiration of the response period required by the relevant patent office. (4) The contractor agrees to include, within the specification of any United States patent application and any patent issuing thereon covering a subject invention, the following statement: ―This invention was made with Government support under (identify the contract) awarded by the National Science Foundation. The Government has certain rights in this invention.'' (5) The contractor or its representative will complete, execute, and forward to NSF a confirmation of a License to the United States Government and the page of a United States patent application that contains the Federal support clause within two months of filing any domestic or foreign patent application. (g) Subcontracts. (1) The contractor will include this Patents Rights clause, suitably modified to identify the parties, in all subcontracts, regardless of tier, for experimental, developmental, or research work. The subcontractor will retain all rights provided for the contractor in this Patents Rights clause, and the contractor will not, as part of the consideration for awarding the subcontract, obtain rights in the subcontractor's subject inventions. (2) In the case of subcontracts, at any tier, when the prime award by the Foundation was a contract (but not a grant or cooperative agreement), NSF, subcontractor, and contractor agree that the mutual obligations of the parties created by this Patents Rights clause 36
  37. 37. constitute a contract between the subcontractor and the Foundation with respect to those matters covered by this Patents Rights clause. (h) Reporting on Utilization of Subject Inventions. The contractor agrees to submit on request periodic reports no more frequently than annually on the utilization of a subject invention or on efforts at obtaining such utilization that are being made by the contractor or its licensees or assignees. Such reports shall include information regarding the status of development, date of first commercial sale or use, gross royalties received by the contractor, and such other data and information as NSF may reasonably specify. The contractor also agrees to provide additional reports in connection with any march-in proceeding undertaken by NSF in accordance with paragraph (j) of this Patents Rights clause. As required by 35 U.S.C. 202(c)(5), NSF agrees it will not disclose such information to persons outside the Government without the permission of the contractor. (i) Preference for United States Industry. Notwithstanding any other provision of this Patents Rights clause, the contractor agrees that neither it nor any assignee will grant to any person the exclusive right to use or sell any subject invention in the United States unless such person agrees that any products embodying the subject invention or produced through the use of the subject invention will be manufactured substantially in the United States. However, in individual cases, the requirement for such an agreement may be waived by NSF upon a showing by the contractor or its assignee that reasonable but unsuccessful efforts have been made to grant licenses on similar terms to potential licensees that would be likely to manufacture substantially in the United States or that under the circumstances domestic manufacture is not commercially feasible. (j) March-in Rights. The contractor agrees that with respect to any subject invention in which it has acquired title, NSF has the right in accordance with procedures at 37 CFR 401.6 and NSF regulations at 45 CFR 650.13 to require the contractor, an assignee or exclusive licensee of a subject invention to grant a nonexclusive, partially exclusive, or exclusive license in any field of use to a responsible applicant or applicants, upon terms that are reasonable under the circumstances, and if the contractor, assignee, or exclusive licensee refuses such a request, NSF has the right to grant such a license itself if NSF determines that: (1) Such action is necessary because the contractor or assignee has not taken, or is not expected to take within a reasonable time, effective steps to achieve practical application of the subject invention in such field of use; (2) Such action is necessary to alleviate health or safety needs which are not reasonably satisfied by the contractor, assignee, or their licensees; (3) Such action is necessary to meet requirements for public use specified by Federal regulations and such requirements are not reasonably satisfied by the contractor, assignee, or licensee; or (4) Such action is necessary because the agreement required by paragraph (i) of this Patents Rights clause has not been obtained or waived or because a licensee of the exclusive right to use or sell any subject invention in the United States is in breach of such agreement. (k) Special Provisions for Contracts with Nonprofit Organizations. If the contractor is a nonprofit organization, it agrees that: (1) Rights to a subject invention in the United States may not be assigned without the approval of NSF, except where such assignment is made to an organization which has as 37
  38. 38. one of its primary functions the management of inventions, provided that such assignee will be subject to the same provisions as the contractor; (2) The contractor will share royalties collected on a subject invention with the inventor, including Federal employee co-inventors (when NSF deems it appropriate) when the subject invention is assigned in accordance with 35 U.S.C. 202(e) and 37 CFR 401.10; (3) The balance of any royalties or income earned by the contractor with respect to subject inventions, after payment of expenses (including payments to inventors) incidental to the administration of subject inventions, will be utilized for the support of scientific research or education; and (4) It will make efforts that are reasonable under the circumstances to attract licensees of subject inventions that are small business firms and that it will give preference to a small business firm if the contractor determines that the small business firm has a plan or proposal for marketing the invention which, if executed, is equally likely to bring the invention to practical application as any plans or proposals from applicants that are not small business firms; provided that the contractor is also satisfied that the small business firm has the capability and resources to carry out it plan or proposal. The decision whether to give a preference in any specific case will be at the discretion of the contractor. However, the contractor agrees that the Secretary of Commerce may review the contractor's licensing program and decisions regarding small business applicants, and the contractor will negotiate changes to its licensing policies, procedures, or practices with the Secretary when the Secretary's review discloses that the contractor could take reasonable steps to implement more effectively the requirements of this paragraph (k)(4). (End of Section I) SECTION J – REPRESENTATIONS, CERTIFICATIONS AND OTHER STATEMENTS OF OFFERORS J.1 OFFEROR REPRESENTATIONS AND CERTIFICATIONS The offeror certifies that (i) all Representations and Certifications contained in the offer are complete, current, and accurate as required, (ii) the offeror is aware that award of any subcontract shall be considered to have incorporated the applicable Representations and Certifications by reference in accordance with FAR 14.201-1(c) or 15.204-1(b), and (iii) the offeror is aware of the penalty prescribed in 18 U.S.C. 1001 for making false statements in proposals. The Representations and Certifications contained in this section should be carefully reviewed and filled-in as appropriate. 38

×