Inactive

Scope of work – manufacturer a high-definition video borescope for mine roof lithology Background: The Mining Systems Safety Branch requires the manufacture of a flexible videoscope, viewing monitor, ... Scope of work – manufacturer a high-definition video borescope for mine roof lithology Background: The Mining Systems Safety Branch requires the manufacture of a flexible videoscope, viewing monitor, and microphone that can be used to view and record video and audio to determine the roof lithology within a 1-inch diameter borehole in underground mine environments. This videoscope and monitor is intended for use in harsh underground mining environments. It will potentially be subjected to several environmental factors that will require a certain ruggedness in the design. The videoscope and associated viewing monitor must have the following capabilities. Detailed requirements: The videoscope The videoscope will be used in underground environments to examine the roof lithology of drillholes as small as 1 inch in diameter and as long as 30 feet. The videoscope must be able to maintain focus in both 1 inch and 1 3/8-inch diameter boreholes. The videoscope must be durable enough to be repeatedly inserted into thousands of drill holes through its life cycle. To accomplish this, the borescope should be surrounded by a tubing that meets IP68 standard for resistance of water and dust. Measurement indications must be placed on the videoscope tubing to allow the user to see how far the videoscope is up vertically inside the borehole in 10ths of a foot increments. The head of the scope must be angled at 90 degrees to view the lithology within the vertical drillhole. The camera at the head of the scope should have the capability to record a 4K (3840 x 2160 pixels) video and take still pictures. The camera head must be recessed and built a protective covering to ensure that rock and other debris will not scratch the camera lens and meet IP68 standards. A set of LED lights must be built into the scope head to illuminate the viewing area to provide identification of lithology and micro features as thin as 1mm thick. The videoscope must be waterproof to IP68 standards since many mine environments can have actual running water coming from the roof boreholes. The video display monitor The video display must be able to show color images in 1080p (1920 x 1080 pixels) at a minimum, but 4K is preferred. The display should be durable as it will be used in an underground mine environment. The display should be at least 8 inches measured diagonally in size and use high-capacity SD (or micro-SD) cards to record video and audio. Audio will require a microphone to record the comments of the user as the drillhole is being examined. The monitor should be water resistant to IP68 standards and durable. The monitor can be a tablet or a standalone monitor. The data link between the videoscope and monitor can be either via wire or wireless. The monitor should also have controls for brightness, contrast, tint, and color. The depth of the fiberscope into the borehole should be displayed on the video monitor as well as have the manual depths on the scope itself as stated previously. Batteries The batteries can consist of 3-4 hour, or 2-8 hour, or 1-16 hour interchangeable battery pack that can be recharged within 12 hours. Carry case and videoscope delivery system The entire system (videoscope, batteries, charger, and monitor) will fit into a rugged carry case that will not weight more than 45 pounds. The case should mount to an adjustable tripod with the videoscope deployed from a hand cranked reel. Government provided No government provided items will be required in the completion of this contract. Deliverables A high definition 30 foot video borescope with monitor, carry case, tripod, hand crank for the videoscope, batteries, and a battery charger. Baseline Security Requirements Hardware Card Readers. The Contractor (and/or any subcontractor) shall include Federal Information Processing Standard (FIPS) 201-compliant smart card readers (referred to as LACS Transparent Readers) with the purchase of servers, printers, desktops, and laptops. Mobile Devices. The contractor shall follow NIST 800-124, Rev. 1, Guidelines for Managing the Security of Mobile Devices in the Enterprise when using mobile devices that process or store HHS data. Contracts for information systems, components, or services must meet the privacy requirements. The Contractor (and/or any subcontractor) shall Include privacy controls in the security testing and evaluation and minimize the use of live data in development and testing. The Contractor shall produce a design specification and security architecture that accurately and completely describes the privacy requirements, and the allocation of security and privacy controls among physical and logical components for any developed information system, system component, or information system service. The Contractor (and/or any subcontractor) shall apply the Multifunction Device and Network Printers (MFD) STIG Version 2 to MFDs and printers to secure implementation as these devices are subject to network and physical security concerns. The Contractor (and/or any subcontractor) shall mark and display a notice indicating appropriate usage of Printers and Copier. Banners & markings shall include: Sensitive Data/Information: Information that has a degree of confidentiality such that its loss, misuse, unauthorized access, or modification could compromise the element of confidentiality and thereby adversely affect national health interests, the conduct of HHS programs, or the privacy of individuals’ information protected by The Privacy Act or the Health Insurance Portability and Accountability Act (HIPAA). Information technology (IT) security personnel and system owners can equate this definition of sensitive information with data that has a FIPS 199 security impact level of moderate or high for the Confidentiality security objective. This definition of sensitive information is media neutral, applying to information as it appears in either electronic or hardcopy format (HHS Memo - Updated Departmental Standard for the Definition of Sensitive Information). Personally Identifiable Information (PII): means information that can be used to distinguish or trace an individual's identity, either alone or when combined with other information that is linked or linkable to a specific individual (OMB M-17-12). Non-Public Information: Information that the employee gains by reason of Federal employment and that he knows or reasonably should know has not been made available to the general public. It includes information that he knows or reasonably should know: (a) Is routinely exempt from disclosure under 5 U.S.C. 552 or otherwise protected from disclosure by statute, Executive order or regulation; (b) Is designated as confidential by an agency; or (c) Has not actually been disseminated to the general public and is not authorized to be made available to the public on request (5 CFR 2635.703). Public Information: Any information, regardless of form or format, that an agency discloses, disseminates, or makes available to the public. (OMB Circular A-130). Information Technology Application Design, Development, or Support Computer programs that comprise a series of instructions, rules, routines, or statements, regardless of the media in which recorded, that allow or cause a computer to perform a specific operation or series of operations; and Recorded information comprising source code listings, design details, algorithms, processes, flow charts, formulas, and related material that would enable the computer program to be produced, created, or compiled. “Computer software” does not include computer databases or computer software documentation. The Contractor (and/or any subcontractor) shall ensure IT applications designed and developed for CDC/NIOSH must not require elevated or administrative privileges running in any context. The Contractor (and/or any subcontractor) shall ensure non-interactive applications and the associated accounts running on servers (e.g., server applications, application servers, system applications, middleware, databases, containers, etc.) do not run with or require full administrative or elevated privileges. The Contractor (and/or any subcontractor) shall follow secure coding best practice requirements, as directed by United States Computer Emergency Readiness Team (US-CERT) specified standards and the Open Web Application Security Project (OWASP), that will limit system software vulnerability exploits. The Contractor (and/or any subcontractor) shall ensure that computer software developed on behalf of HHS or tailored from an open-source product, is fully functional and operates correctly on systems configured in accordance with government policy and federal configuration standards. The contractor shall test applicable products and versions with all relevant and current updates and patches updated prior to installing in the HHS environment. No sensitive data shall be used during software testing. The Contractor (and/or any subcontractor) shall protect information that is deemed sensitive from unauthorized disclosure to persons, organizations or subcontractors who do not have a need to know the information. Information which, either alone or when compared with other reasonably-available information, is deemed sensitive or proprietary by HHS shall be protected as instructed in accordance with the magnitude of the loss or harm that could result from inadvertent or deliberate disclosure, alteration, or destruction of the data. This language also applies to all subcontractors that are performing under this contract. The Contractor (and/or any subcontractor) shall remediate all risks or vulnerabilities immediately after the risks or vulnerabilities have been identified in the software. When transferring information between different security domains, the Contractor (and/or any subcontractor) shall examine for the presence of unsanctioned information for malicious code and prohibits the transfer of such information. Unsanctioned information (information not authorized to be stored, processed or transmitted by the system) is any information not owned by the Institute nor covered by an existing DUA, DSA, MOU or other authorization. When trust relationships are established with external information systems (systems that are outside of the authorization boundary to access, process, store, or transmit PII), the Contractor (and/or any subcontractor) shall limit access to PII from external information systems with a binding agreement to terms and conditions of the privacy requirements. The Contractor (and/or any subcontractor) shall review of user privileges to ensure privileges are revoked for those who no longer require access to PII or PHI and limit the following: limit maximum number of concurrent sessions for system accounts globally, by account type, by account, or a combination thereof Limit access to PII from mobile devices, if applicable Non-Commercial and Open Source Computer Software Procurements The Contractor (and/or any subcontractor) shall follow secure coding best practice requirements, as directed by the United States Computer Emergency Readiness Team (US-CERT) specified standards and the Open Web Application Security Project (OWASP) that will limit system software vulnerability exploits. HHSAR Provision, 352.239-73: Electronic and Information Technology Accessibility Notice (a) Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. 794d), as amended by the Workforce Investment Act of 1998 and the Architectural and Transportation Barriers Compliance Board Electronic and Information (EIT) Accessibility Standards (36 CFR part 1194), require that when Federal agencies develop, procure, maintain, or use electronic and information technology, Federal employees with disabilities have access to and use of information and data that is comparable to the access and use by Federal employees who are not individuals with disabilities, unless an undue burden would be imposed on the agency. Section 508 also requires that individuals with disabilities, who are members of the public seeking information or services from a Federal agency, have access to and use of information and data that is comparable to that provided to the public who are not individuals with disabilities, unless an undue burden would be imposed on the agency. (b) Accordingly, any offeror responding to this solicitation must comply with established HHS EIT accessibility standards. Information about Section 508 is available at http://www.hhs.gov/web/508. The complete text of the Section 508 Final Provisions can be accessed at http://www.access-board.gov/sec508/standards.htm. (c) The Section 508 accessibility standards applicable to this contract are: 1194. 205 WCAG 2.0 Level A & AA Success Criteria 302 Functional Performance Criteria 402 Closed Functionality 403 Biometrics 404 Preservation of Information Provided for Accessibility 405 Privacy 406 Standard Connections 407 Operable Parts 408 Display Screens 409 Status Indicators 410 Color Coding 411 Audible Signals 502 Inoperability with Assistive Technology 503 Applications 504 Authoring Tools 602 Support Documentation 603 Support Services In order to facilitate the Government's determination whether proposed EIT supplies meet applicable Section 508 accessibility standards, offerors must submit an HHS Section 508 Product Assessment Template, in accordance with its completion instructions. The purpose of the template is to assist HHS acquisition and program officials in determining whether proposed EIT supplies conform to applicable Section 508 accessibility standards. The template allows offerors or developers to self-evaluate their supplies and documentation detail - whether they conform to a specific Section 508 accessibility standard, and any underway remediation efforts addressing conformance issues. Instructions for preparing the HHS Section 508 Evaluation Template are available under Section 508 policy on the HHS Web site http://hhs.gov/web/508. In order to facilitate the Government's determination whether proposed EIT services meet applicable Section 508 accessibility standards, offerors must provide enough information to assist the Government in determining that the EIT services conform to Section 508 accessibility standards, including any underway remediation efforts addressing conformance issues. (d) Respondents to this solicitation must identify any exception to Section 508 requirements. If a offeror claims its supplies or services meet applicable Section 508 accessibility standards, and it is later determined by the Government, i.e., after award of a contract or order, that supplies or services delivered do not conform to the accessibility standards, remediation of the supplies or services to the level of conformance specified in the contract will be the responsibility of the Contractor at its expense. (e) Electronic content must be accessible to HHS acceptance criteria. Checklist for various formats are available at http://508.hhs.gov/, or from the Section 508 Coordinator listed at https://www.hhs.gov/web/section-508/additional-resources/section-508-contacts/index.html. Materials that are final items for delivery should be accompanied by the appropriate checklist, except upon approval of the Contracting Officer or Representative. This is a request for competitive quotations .Any quotation/response should be emailed to contract specialist at MSo9@cdc.gov by COB 16 July 2021