Inactive

IRP Core Lab & External Vendor Catalog Platform SOW 1 1. INTRODUCTION/OVERVIEW Acquire access to a private, searchable, web-based, software platform that will enable the 23 Institutes and Centers (I/C... IRP Core Lab & External Vendor Catalog Platform SOW 1 1. INTRODUCTION/OVERVIEW Acquire access to a private, searchable, web-based, software platform that will enable the 23 Institutes and Centers (I/C) of the National Institutes of Health (NIH) Intramural Research Program (IRP) to enhance visibility and promote sharing of research resources, technologies and expertise available through more than 170 IRP Core Laboratories, and through a majority of external commercial research vendors, including Academic Core Labs. The platform should enable IRP investigators to query capabilities of multiple "internal" IRP Core Labs and external vendors simultaneously through a secure communication channel, to enable the best source selection in terms of technology, price and availability. 1.1. BACKGROUND As part of the long-term strategic planning for the IRP, the Advisory Committee to the NIH Director (ACD) in 2014 recommended enhanced scientific interactions between I/Cs, including sharing of Core Labs and other shared research resources across all IRP I/Cs. To comply with the NIH ACD's recommendation, the IRP needs a platform that enhances both the visibility and sharing of research resources, technologies, and expertise available through over 170 centralized Core Labs. The platform should also include research services available through a majority of external vendors. The ability to simultaneously query capabilities of internal and external vendors allow IRP investigators to make side-by-side comparisons for the best source selection. Direct comparisons with external vendors also enable IRP Administrators and Core Labs to focus on providing new and emerging technologies rather than services available at a comparable or lower cost through external vendors. The appropriate annotation of external vendors for certifications, accreditations and existing NIH contract or procurement vehicles, can also increase compliance with NIH and Federal Acquisition Regulations (FAR), and streamline the procurement process for IRP investigators, at the same time enabling the IRP to negotiate better pricing. 1.2. SCOPE Acquire access to a web-based software platform that constitutes a Research Resources Marketplace ("RRM") accessible to all NIH IRP researchers. RRM shall include a searchable listing of scientific tools and research services available through IRP Core Labs and external vendors. Software platform shall enable IRP users to communicate with multiple internal and external vendors simultaneously to enable source selection. Software platform shall also include a parallel web-interface that enables IRP Core managers to easily manage and update their Lab’s content, and respond to users’ requests. The vendor shall provide an IRP RRM manager to coordinate IRP Core Lab’s content development, content updates and trainings for the IRP users and Core Managers. Contractor shall also provide IRP Core Lab & External Vendor Catalog Platform SOW 2 trained Full-Time Employees (FTEs) as sourcing specialists to review user requests and ensure Core Labs and vendors provide timely responses to user requests. 1.3. OBJECTIVES Acquire access to a web-based software platform that constitutes an RRM that shall be accessible only to NIH IRP researchers. The RRM shall include a comprehensive listing of scientific tools and research services relevant for the research of basic, translational and clinical biomedical scientists spread across broad disciplines. Capabilities of IRP Core Labs and a majority (>80%) of external vendors (Commercial Research Organizations and Academic Core Labs) shall be tied to the pertinent research services or technologies they provide, and shall be easily searchable using keywords for service categories or by name. Content for both research services and listings of external vendors shall be kept current to include the most innovative technologies and services and to ensure new providers are continuously added. Software platform shall enable users to communicate with multiple internal and external vendors simultaneously, including exchange of data files and price quotes. The software shall also include a parallel web-interface that enable IRP Core managers to manage their content, provide updates and respond to user requests. The vendor shall provide a Marketplace manager who will coordinate and perform content update for Core Labs, train Core Managers and I/C users on the platform, and coordinate marketing strategy for each participating I/C through the designated I/C Points of Contact (POC). The vendor shall also provide trained FTEs as part of a sourcing specialist team. The team will review user requests, help add qualified suppliers as requested, and ensure Core Labs and vendors provide timely responses to submitted requests. 2. REQUIREMENTS 2.1. TASKS I. Contractor shall provide access to a web-based software platform, as an enterprise-wide license, that constitutes a "Research Resources Marketplace" (RRM), to the participating I/Cs of the NIH Intramural Research Program (IRP). I.1 Web-based "Research Resources Marketplace" (RRM) for the NIH IRP shall be fully functional and readily available for use by participating I/Cs of the IRP of contract award. The participating I/Cs are based mainly in Maryland, with additional sites in Research Triangle, North Carolina, and Hamilton MT. Each participating I/C POC will be asked to confirm in writing to the COR, that content for their Core Labs has been loaded on the RRM and is searchable and accessible to users. In addition, the RRM will be tested by a group of power users, comprised of select scientists chosen from each participating I/Cs. The group will determine its IRP Core Lab & External Vendor Catalog Platform SOW 3 functionality as a tool to conduct market research and/or to identify research resources prior to making the award. Upon successful demonstration of platform capabilities, the COR will indicate that the requirement of delivery of a fully functional RRM has been met. I.2 RRM shall include at a minimum a listing of 2500 research service categories and scientific tools relevant for basic, translational and clinical biomedical research, within the disciplines of Biology, Chemistry, Pharmacology, Toxicology, DMPK and Clinical Research. This shall be included within 60 days of contract award. I.3 Capabilities of >170 NIH IRP Core Labs and >80% of external vendors, the latter including Contract Research Organizations (CROs) and Academic Core Labs, shall be associated with research service categories and technologies that are relevant to their lab’s capabilities, and shall be searchable using keywords relevant to the service or by name of the Cores/Vendors. This shall be included within 60 days of contract award. I.4 IRP Core Labs and vendors in the database shall be annotated for their affiliation (NIH I/C) and specific certifications and accreditation (CLIA, PHS, etc.) to help enhance compliance with NIH regulations. This shall be included in initial delivery within 60 days of contract award. The database should also have the capability to annotate external vendors and services with information useful for sourcing of federal procurements (GSA, BPA, Small Business badging etc.). I.5 A keyword search function shall enable users to identify multiple internal and external vendors for specific research services. The list of vendors for each research service should be customizable by IRP administrators to ensure IRP Core labs and vendors with preferred status (e.g., small and minority owned-business or with existing NIH contract vehicles), are included in the default list. This shall be included within 60 days of initial delivery of contract award. I.6 RRM shall include a secure communication channel that allows IRP researchers to query capabilities of multiple internal and external vendors simultaneously, discuss project details, exchange files and obtain detailed quotes to enable a side-by-side comparison. IRP researchers to maintain all communications with vendors within the marketplace through a request management system, and receive email notifications when the status of their request changes. This shall be included in initial delivery within 60 days of contract award. I.7 RRM shall include a directly linked web-interface that enables IRP Core Managers to manage and update information on their lab’s capabilities, IRP Core Lab & External Vendor Catalog Platform SOW 4 and respond to IRP requestors. This shall be included in initial delivery within 60 days of contract award. I.8 RRM software shall allow IRP investigators to post Ratings and Reviews on Vendor’s performance for specific services, and these shall be visible ONLY to the rest of the NIH IRP. The Ratings/Reviews shall not be used by the RRM Contractor or research services vendor for any self-promotional purposes. Any ratings of 3 and below (on a total 5-star range, with 5 being the highest) shall be shared by the Contractor with the CRO/Academic Core Lab. Responses/clarifications received from the vendor will be posted on the RRM. This shall be included in initial delivery within 60 days of contract award. I.9 RRM software shall have the capability to route user requests to designated NIH I/C-specific gatekeepers or approvers. If requested, I/C-specific gatekeepers will ensure that I/C-preferred internal and external sources are included in requests initiated by their users. The request routing workflow will be different across I/Cs and will need to be customizable for the needs of each I/C. I.10 Software platform shall have an Application Programming Interface (API) that can be used to link the Research Resources Marketplace to desired NIH I/C systems (procurement system, Core Services Accessioning System, etc.). This shall be included within 60 days of initial delivery of contract award. I.11 Software platform shall meet all applicable HHS IT security and risk assessment requirements included in the pre-sol certification and attached clauses. Shall be included in initial delivery at time of contract award. I.12 Software platform shall allow designated I/Cs administrators to access usage statistics, including number of logins, browse history and communications, for the RRM on a weekly or monthly basis. II. The RRM will be used by up to twenty three (23) NIH Institutes and Centers (I/Cs) of the IRP through the duration of the contract, including option years. The platform shall be extendable to include users and Core labs of all I/Cs of the IRP. III. Contractor shall make the RRM a dedicated, "private" platform accessible only to NIH IRP-affiliated investigators using their NIH Single Sign On (SSO) credentials. IV. Contractor shall update service categories of the RRM monthly during the award period to include the latest and most innovative research services and technologies available to biomedical researchers. New vendors and new capabilities of Core Labs shall be updated on a monthly basis, or as requested by the IRP. V. Contractor shall provide a trained Site Manager who will be the main Point of Contact for managing all aspects of customization, development and deployment of the RRM to the IRP. V.1 Site Manager shall have at a minimum a Ph.D. degree and should have at IRP Core Lab & External Vendor Catalog Platform SOW 5 least 2-years of experience in providing project management support for a similar platform to an Academic, Commercial or Government organization. V.2 Site Manager shall coordinate, and perform if needed, content update for participating IRP Core Labs. V.3 Site Manager will either coordinate training through a team, or directly train, if needed, IRP Core Managers and I/C users on using the Research Resources Marketplace. V.4 Site Manager will coordinate marketing and outreach strategy for each participating NIH I/C through their designated I/C Points of Contacts (POCs). V.5 Site Manager will be required to meet virtually at least 3-days a month with the NIH onsite RRM program managers and POCs within participating I/Cs and for outreach to I/C Core Lab Managers. V.6 Site Manager will host bi-weekly web-meetings with IRP POC, to provide updates on RRM development, platform usage, serve as an interface between the Vendor’s software engineering team and the I/C POC. V.7 Site Manager will host monthly RRM "User training sessions" with various I/Cs and develop videos or tools that enable users to adopt the platform. VI. Contractor will provide trained FTEs as part of a Sourcing Specialist Team. VI.1 Sourcing specialist shall have at a minimum a M.S. or higher degree in the Biological Sciences and a minimum of 1 year experience supporting a similar RRM platform. VI.2 Sourcing team will review IRP users’ requests to help add qualified suppliers (Cores and vendors) as needed and as requested by users. VI.3 Sourcing Team will follow up with IRP Core labs and external vendors to ensure they provide timely responses to every IRP request submitted. VII. Contractor shall perform, or get a qualified third party to perform, IT security testing of the software platform according to the requirements and at the frequency detailed in the attached Security plan. Results will be made available to the NIH IRP COR.