PWS.pdf
PDF 420 KB Posted
- Attached to
- NOAA Video Studio CatDV Asset Management upgrade, Storage Upgrade, and service level agreement
- Solicitation number
- NC-NA2600-22-00679
About this file
This performance work statement outlines requirements for upgrading the CatDV asset management system, storage solution, and related services for the NOAA video studio. The NOAA seeks to migrate from its current CatDV Pro system to CatDV Pegasus, upgrade the existing Cohesity storage to a Quantum or equivalent solution certified for CatDV Pegasus, and obtain a one-year service level agreement with the option to renew annually for four years. Key requirements include CatDV Pegasus licensing, configuration, and training; a minimum of 240TB of usable Quantum or equivalent storage with StorNext file system; and professional installation and integration services within the stated period of performance from August 2022 to July 2027. Responses to the related sources sought notice are due by May 31, 2022 to inform the procurement approach.
View the file
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
(NC-NA2600-22-00679/NOAA Studio Asset Management and Storage Upgrades)
Performance Work Statement (PWS) Version 3/25/2022
U.S. Department of Commerce
NOS/AAMB/Communications and Education
Asset Management and Storage Upgrade for the NOAA Video Studio
Performance Work Statement
PART 1
INFORMATION
1.0 Detailed PWS Information
1.01 Background: The National Ocean Service (NOS) is a line office of the National Oceanic and Atmospheric Administration (NOAA), which is a bureau of the United States Department of Commerce. The mission of NOS is broad and includes a variety of technical and scientific services in support of coastal ocean natural resource stewardship and navigation support. Within NOS are program offices that are charged with carrying out the NOS mission.
The Communications and Education Division (CED) is a division of NOS’s Management and Budget (MB) Office located at NOS Headquarters in Silver Spring, MD. The CED manages the operation of a 1,389 square foot video studio space located on the 9th floor of 1305 East-West Hwy, Silver Spring MD 20910. As part of this project the existing CatDV asset management system and the shared storage systems requires upgrading to optimize multiple editors working on multimedia assets that consist of video, audio, imagery and text documents. Shared access to all assets must begin with a project creation tool that the contractor configures and trains the NOAA Studio video staff on how to use. A minimum of 240 Terabytes (TB) of usable shared storage is required with the ability to be expanded.
The contractor must install, configure, document, and train on all hardware devices installed as part of this system within the NOAA 6001 boundary. Supervision from NOS domain infrastructure staff that support the NOAA 6001 system must be present during all work that is within scope.
1.02 Objectives: The NOAA Video studio has the following objectives that are within the scope.
● Trade-in of Existing CatDV Software Licensing;
● CatDV Pegasus Software Upgrades;
● CatDV Pegasus Training,
● Quantum Xcellis Workflow Director and Metadata Storage,
● Quantum QXS-412 Storage (minimum 240 terabytes usable storage),
● StorNext File System and Storage Manager Training,
● Mellanox 1U SN2100 100GbE/10GbE Ethernet Switches,
● Professional Services, and
● a service level agreement.
The contractor shall deliver a fully functional and integrated CatDV Pegasus Studio Asset Management and Quantum Storage solution for the NOAA video studio according to the description and narrative described here-in.
1.03 Scope/High-level Description:
Asset Management System: The NOAA has a video studio that includes three dedicated edit bays, one shared edit bay for audio recording, an independent video studio and a shared producer’s space. The three design areas have unique needs with similar shared underpinnings. The NOAA video team currently uses a storage solution that is inadequate for shared editing. This action requires an authorized reseller to implement an upgrade and migration from our current CatDV Pro system to a CatDV Pegasus asset management system. A credit for our existing CatDV software and support is requested under the enterprise maintenance agreement currently in place. This includes upgrading and migrating our single CatDV worker node to a three instance CatDV Pegasus worker node to speed transcoding. We require licensing and installation of seven (7) CatDV Pegasus desktop clients and one (1) CatDV Pegasus web server with one process. We require a plugin and the configuration of this plugin to backup all media assets to our existing Microsoft Azure cloud service. We also require a project creation template that must allow for the creation of a new project which automatically assigns a unique ID to the project assets, creates a folder structure on the storage system, creates worker node actions to monitor for incoming files and uploads to the correct catalog and moves to correct level of storage, plus automatic tagging based on folder structure and project number. This includes deployment of this project creation template and training on its use. This system must include a workflow to allow for a video editor to publish selected clips to a publicly accessible website that will be known as the NOAA b-roll library. Licensing and setup of this website is an optional item that should be priced as well as training on its maintenance and use. Training is required to allow the NOAA video team to become familiar with the CatDV Pegasus system. Maintenance and support of the entire Asset Management System as described is needed for a 12-month period from award with the opportunity for four (4) option year renewals through a service level agreement (SLA).
Storage System: We require an upgrade and migration from our existing Cohesity storage solution to a Quantum (or exact equivalent) storage solution certified to work with the CatDV Pegasus asset management solution described above. It must support multiple editors' access to the shared media assets for day-to-day creation and editing of projects over the existing NOAA fiber network to the existing fiber attached Mac workstations. Mellanox or exact equivalent network switches must be provided with the necessary transceivers, adapters, and patch cables to support the engineered storage system. A minimum of 240 terabytes of usable storage is required with the ability for future expansion. We require the necessary software licensing and configuration of a tiered backup and archiving process of this system to the existing Cohesity storage system and the Microsoft Azure Cloud storage provided by NOAA. Training on the use of the front-end system as well as training on the back-end hardware is required through the qualified firm. We also require a service level agreement (SLA) to support both the front-end and back-end systems with up to four (4) option year renewals of this agreement in support of both the CatDV Pegasus asset management and Quantum storage solutions as engineered. Recommendations on how best to implement these systems are encouraged along with recommendations on the equipment.
Work associated with this action must take place under guidance from the staff of the Information Management Office’s Domain Infrastructure (DIT) and Network Infrastructure teams (NIT). This staff must be trained on how to diagnose and perform high-level maintenance. The SLA must include points of contact and a four (4) hour response time frame within normal business hours (see section 1.09 below).
1.04 Requirements and Functional Equivalency:
The contractor shall use the list and table below to engineer the components described above for a fully functional CatDV Pegasus asset management and storage systems for the NOAA video studio. The hardware components listed throughout this document are brand name or equal, any substitutions must be identified and approved. The vendor must certify and demonstrate that their engineered solution would fulfill the needs identified above. Specifically, the hardware items identified are:
● Quantum Xcellis Workflow Director and Metadata Storage- an equivalent system must combine compute, client access, and storage to create an efficient and powerful core of a workflow storage solution. It must support third-party workflow applications as virtual machines for flexible and cost-effective deployment. It must allow the ability to add storage arrays to scale from the initial 240 Terrabytes. It must support multi-protocol access enabling all clients access to the same data regardless of protocol, on a SAN or on a LAN. It must support billions of files across multiple virtual file systems. It must scale to hundreds of petabytes. It must also scale to include use of Azure or AMS cloud, object storage, or tape. It must support flexible connectivity options such as 16Gb FC, 8Gb FC, 1Gb Ethernet, 10Gb Ethernet, 40Gb Ethernet, and FDR InfiniBand.
Xcellis is designed to get the most out of StorNext, a Quantum solution. StorNext File System (SNFS) is a shared disk file system made by Quantum Corporation. StorNext enables multiple Windows, Linux and Apple workstations to access shared block storage over a Fibre Channel network. With the StorNext file system installed, these computers can read and write to the same storage volume at the same time enabling what is known as a "file-locking SAN." A functionally equivalent system must meet the shared disk file system requirements as described for a multi-video editor environment.
● Quantum QXS-412 Storage (minimum 240 terabytes usable storage) - an equivalent system must be a high-performance, reliable, expandable storage array, designed and demonstrated to cost-effectively accelerate video workflows. It must offer a storage foundation for StorNext or an equivalent locking file system that is proven to allow multiple video editors to simultaneously interact with and edit video and audio projects while connected to and using this storage solution. It must be optimized to deliver maximum throughput and sequential I/O performance, designed with no single point of failure with 99.999% uptime when properly maintained. It must be highly configurable and flexible with chassis options that do not require a forklift option for future replacement.
● StorNext File System and Storage Manager Training - as mentioned above when describing Xcellis, StorNext File System (SNFS) is a shared disk file system made by Quantum Corporation. StorNext enables multiple Windows, Linux and Apple workstations to access shared block storage over a Fibre Channel network. With the StorNext file system installed, these computers can read and write to the same storage volume at the same time enabling what is known as a "file-locking SAN." A functionally equivalent system must meet the shared disk file system requirements as described for a multi-video editor environment. We require a file system that allows multiple editors to edit video and audio projects using Adobe Premiere and fiber attached Macintosh workstations.
● Mellanox 1U SN2100 100GbE/10GbE Ethernet Switches- a functional equivalent network switch must provide a high density, side-by-side 100GbE switching solution which scales up to 128 ports in 1RU for the NOAA Studio video demands as described above. The network switch is the spine that must allow maximum flexibility, with port speeds spanning from 10Gb/s to 100Gb/s per port and port density that enables full rack connectivity to any server at any speed. The uplink ports must allow a variety of blocking ratios that suit any video application requirement. The SN2100 or equivalent must have at least 16 ports running at 100GbE with a throughput of 3.2Tb/s and 2.38Bpps processing capacity in a 1RU form factor. A network switch equivalent must be demonstrated to meet these needs.
1.05 Deliverables:
Deliverable Frequency Medium/Format/# of Copies
Submit To
Kick Off Meeting Within 20 days of award
In person Consult with Task Manager or COR to schedule
Installation Calendar Within 7 days of kick off meeting
In person or via email
Task Manager
Follow up Meeting to review design and provide recommendations
Within 7 days of kick off meeting
In person Consult with Task Manager or COR to schedule
Weekly Activity Report
By COB Friday of every week via email Task Manager
Detailed Interconnect Binder with Documentation
Within 2-days of completion
One physical binder with printouts of all documentation and an electronic copy (pdf format)
Task Manager
Hardware warranty and specifications Binder
At completion One physical binder that contains all warranty information organized by functional area
Task Manager
Hand Off Meeting and Training
At completion In person meeting and training session
Consult with TM, COR, and CO to schedule
1.06 Constraints:
Connecting any owner furnished equipment (OFE) equipment is outside the scope of this action. Additionally, access to the Cohesity and Microsoft Azure storage will be provided through the National Ocean Service DIT and NIT. Any issues arising from any delays will be mitigated by open communication between the parties. Any necessary personnel, network and Internet connections will be provided as needed through the task manager (TM) identified below or DIT/NIT staff the TM identifies.
1.07 Period of Performance: The period of performance shall be for one (1) Base Year and (4) Option Years. The Period of Performance reads as follows:
Base Year – August 1, 2022 – July 31, 2023 Option Year 1 - August 1, 2023 – July 31, 2024 Option Year 2 – August 1, 2024 – July 31, 2025 Option Year 3 – August 1, 2025 – July 31, 2026 Option Year 4 - August 1, 2026 – July 31, 2027
1.08 Type of Order: The government anticipates the award of a Firm Fixed Price (FFP) contract.
1.09 Hours of Operation/Place of Performance: The contractor is responsible for performing any installation and configuration work between the hours of 8AM to 5PM during weekdays, Monday through Friday, except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. The contractor must at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this statement of work when the Government facility is not closed for any reason, including recognized holidays listed in section 1.011. When hiring personnel, the contractor shall keep in mind that the stability and continuity of the workforce are essential.
Work will normally be performed in the studio area located on the 9th floor of 1305 East-West Hwy, Silver Spring, MD 20910.
1.010 Special Qualifications: The contractor is expected to provide a fully trained workforce to the government; therefore, personal development training costs and hours are not billable to the government.
1.011 Recognized Holidays:
New Year’s Day Labor Day Martin Luther King Jr.’s Birthday Columbus Day President’s Day Veteran’s Day Memorial Day Thanksgiving Day Independence Day Christmas Day
In addition to the days designated as holidays, the Government observes the following days:
Any other day designated by Federal Statute Any other day designated by Executive Order Any other day designated by a President's Proclamation
It is understood and agreed between the Government and the contractor that observance of such days by Government personnel shall not otherwise be a reason for an additional period of performance or entitlement to compensation except as set forth within the contract. If a contractor believes that an unplanned absence has an impact on the price or period of performance, it should notify the contracting officer (CO) of the changed condition and submit a claim for equitable adjustment (see FAR 52.233-1).
Nothing in this clause abrogates the rights and responsibilities of the parties relating to "stop work" provisions as cited in other sections of this contract.
1.012 Security Requirements
IT Hardware and/or Software
IT Security Requirements
a. The Assessment and Authorization (A&A) requirements of Clause 48 CFR 1352.239-72 do not apply, and a Security Accreditation Package is not required.
b. The Contractor shall only supply Information Technology (e.g., hardware, software, firmware, etc.) and/or product license and shall not require the use of any contractor owned equipment. The contractor will not have remote access to any government owned equipment. The Contractor shall ensure the acquiring Information Technology provided disables “phone home” or similar capabilities.
c. The Contractor shall include the necessary product support and supporting documentation that allows the sanitization for the acquiring Information Technology and/or product license upon the disposal of the product. The Contractor shall not destroy any information unless specifically authorized by the Contracting Officer Representative/Task Manager. The Contractor upon request of the COR/TM shall use one of the approved methods for secure destruction of unclassified but sensitive information. Approved methods include NIST Special Publications 800-88 Guidelines for Media Sanitization (https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-88r1.pdf) or the National Security Agency in the Media
Destruction Guidance (https://www.nsa.gov/Resources/Media-Destruction-Guidance/).
d. The Contractor shall ensure the custom solutions and/or acquiring information technology are engineered for trustworthy and security. The Contractor shall work with the government assigned ISSO to determine the applicable security requirements that must be addressed. The Contractor shall throughout the lifecycle of this contract all custom/acquired solutions are consistent with the engineering-based trustworthy secure solutions as outlined in NIST Special Publication 800-160 Systems Security Engineering: Considerations for a Multidisciplinary Approach in the Engineering of Trustworthy Secure Systems (https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-160v2.pdf).
e. The Contractor shall provide sufficient documents demonstrating the acquiring information technology complies with Office of Management and Budget Memorandum M-07-18 Ensuring New Acquisitions Include Common Security Configurations and the Federal Acquisitions Regulations (FAR) 39.101(d) regulations require NIST common security configuration checklists including United States Government Configuration Baseline (USGCB) initiative. The Contractor shall provide sufficient documentation, which demonstrates the acquiring information technology or service(s) has implemented common security configuration checklists. Common security configuration checklists are available at National Checklist Program (NCP), (https://nvd.nist.gov/ncp/repository), the U.S. government repository of publicly available security checklists (or benchmarks) that provide detailed low-level guidance on setting the security configuration of operating systems and applications. If the Contractor does not have common security configuration checklist for the acquiring information technology or service(s), then the Contractor shall provide a rationale for not meeting the OMB M-07-18 requirement.
f. The Contractor shall ensure that the acquiring information technology complies with the Homeland Security Presidential Directive 12 (HSPD-12) Policy for a Common Identification Standard for Federal Employees and Contractors requirements from FAR 4.1302 stating: (a) In order to comply with Federal Information Processing Standard (FIPS) 201, agencies must purchase only approved personal identity verification products and services, (b) Agencies may acquire the approved products and services from the GSA, Federal Supply Schedule 70, Special Item Number (SIN) 132-62, HSPD-12 Product and Service Components, in accordance with ordering procedures outlined in FAR Subpart 8.4. If the Contractor does not comply with HSPD-12 requirement for the acquiring information technology, then the Contractor shall provide a rationale for not meeting the HSPD-12 requirement.
g. The Contractor shall ensure that the acquiring information technology complies with Internet Protocol Version 6 (IPv6) requirements from FAR part 11.002 requirements. FAR part 11.002 requirements state that unless the agency Chief Information Officer waives the requirement, when acquiring information technology using Internet Protocol, the requirements documents shall include reference to the appropriate technical capabilities defined in the USGv6 Profile (https://www.nist.gov/programs-projects/usgv6-program) and the corresponding declarations of conformance defined in the USGv6 Test Program. DOC acquisition of IP protocol technology shall express requirements for IPv6 capabilities in terms of the USGv6 Profile (e.g., using the USGV6 Capabilities Check List) and vendors shall be required to document their product’s support of the requested capabilities through the USGv6 test program (reference https://www.nist.gov/programs-projects/usgv6-program) using the USGv6 Suppliers Declaration of Conformity. If the Contractor does not meet the IPv6 / FAR part 11.002 requirements for the acquiring information technology, then the Contractor shall provide a rationale for not meeting the FAR part 11.002 requirement.
h. The Contractor shall provide all supporting documentation or a reference to obtain the necessary material, which describes the security capabilities, the design and development processes and the testing and evaluation procedures used by the acquiring information technology. The Contractor shall provide all supporting documentation or a reference to obtain the necessary material, which describes all information technology updates and enhancements when implemented. The https://www.nsa.gov/Resources/Media-Destruction-Guidance/ https://www.whitehouse.gov/wp-content/uploads/2018/07/M-18-21.pdf information technology supporting documentation examples include, but not limited to the user guide, system administrator guides and/or hardening guide. The Contractor shall provide document(s) or a reference to obtain the information that describes the functional properties of the security controls employed to permit the analysis and testing of the security controls for the acquiring information technology.
i. The Contractor shall provide sufficient document demonstrating the acquiring information technology provided complies with the following:
a) The standard installation, operation, maintenance, updates and/or patching of software shall not alter the common secure configuration settings (e.g., USGCB and/or other secure baseline),
b) Applications designed for normal end users shall run in the standard user context without requiring elevated system administration privileges.
Developed Solutions using GFE
The Contractor shall comply with the following DOC Department Administrative Orders (DAO): DAO 200-0 Department of Commerce Handbooks and Manuals and DAO 207-1 Security Programs (available at:
https://www.osec.doc.gov/opog/dmp/daos.html). The Contractor shall comply with the following DOC Department Organization Orders (DOOs) DOO 15-23 Chief Information Officer (available at:
https://www.osec.doc.gov/opog/dmp/doos.html). The Contractor shall comply with the NOAA Administrative Orders (NAO) NAO 212-13 NOAA Information Technology Security Policy and NAO 212-15 Management of Environmental Data and Information (available at: https://www.noaa.gov/organization/administration/noaa-administrative-orders). DOC issues policies under DAO 200-0, DAO 207-1 and DOO 15-23. NOAA issues cybersecurity policies under NAO 212-13. The DAO, DOO, NAO and corresponding policies are sensitive controlled unclassified information (CUI) documents that shall be limited to use only on Government Furnished Equipment and will be provide after contract award.
The DAOs, DOO and NAOs and corresponding policies may not specifically identify requirements for Contractor developed solutions residing within their area of responsibility (e.g., application(s), web site(s), database(s), servers, virtual machine(s), network component, etc.), but the Contractor developed solutions shall comply with the applicable cybersecurity requirements. The Contractor shall work with the government assigned Information System Security Officer (ISSO) to determine the applicable cybersecurity requirements that must be addressed. The Contractor shall ensure the developed solutions and/or acquiring information technology or service(s) are engineered for trustworthy and cybersecurity. The Contractor shall throughout the lifecycle of this contract all developed/acquired solutions are consistent with the engineering-based trustworthy secure solutions as outlined in NIST Special Publication 800-160 Systems Security Engineering:
Considerations for a Multidisciplinary Approach in the Engineering of Trustworthy Secure Systems (https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-160v2.pdf) or later publication.
The Contactor shall ensure all work is performed upon government furnished equipment and/or information technology and/or service(s) residing within the ISSO assigned FISMA boundary. If additional information technology and/or service(s) is/are needed, the contractor shall submit a request for the additional requirements to the Contracting Officer Representative
(COR).
The Contractor shall work with the government assigned ISSO for identifying security controls, documenting security and privacy controls and ongoing continuous monitoring of security and privacy controls in support DOC, NOAA and NOS cybersecurity requirements. The Contractor shall provide their security and privacy controls implementation including applicable architecture, diagrams, documentation, standard operating procedures, secure baselines and other relevant documentation supporting the development and operation of their solution. The Contractor shall work with the government assigned ISSO to ensure development, obtain baseline deviation approval, and implementation of a secure baseline/benchmark is applied to all components (e.g., application(s), web site(s), database(s), servers, virtual machine(s), network component, etc.) supporting their developed solutions residing within their area of responsibility prior to being placed into production.
The Contractor shall work with the government assigned ISSO to ensure all components (e.g., application(s), web site(s), database(s), servers, virtual machine(s), network component, etc.) supporting their developed solutions residing within their area of responsibility undergo vulnerability scanning, secure baseline compliance scanning and mitigation of vulnerabilities and/or compliance findings. The Contractor shall provide the appropriate documentation to the government for each update demonstrating the requirements have been met prior to placing the changes into production. The Contractor shall perform vulnerability scanning and remediation on all public facing components residing within their area of responsibility (e.g., application(s), web site(s), database(s), servers, virtual machine(s), network component, etc.) at least every 7 days and non-public components residing within their area of responsibility at least every 60 days. The Contractor shall perform secure baseline scanning at least monthly on all components (e.g., application(s), web site(s), database(s), servers, virtual machine(s), network component, etc.) supporting their developed solutions residing within their area of responsibility. The Contractor shall work with the government assigned ISSO to address all baseline deviation(s) not approved upon detection within 60 days for all components (e.g., application(s), web site(s), database(s), servers, virtual machine(s), network component, etc.) supporting their developed solutions residing within their area of responsibility. The Contractor shall throughout the lifecycle of this contract provide updates to their developed solution residing within their area of responsibility when changes to their solution(s), policy changes and/or changes to NIST guidance and legislation.
The Contractor shall ensure their developed solutions residing within their area of responsibility does not contain any spyware, malicious software, coding flaws or programming backdoors to circumvent the application functionality or the security of the application as described by the government. The Contractor shall ensure their developed solutions residing within their area of responsibility does not access data stored on the device or request end user information without following all government (including OMB) requirements. The Contractor shall ensure their developed solutions residing within their area of responsibility does not transmit stored data from the installed device without clearly notifying, fully describing the required data being transmitted and receiving the government’s approval.
The Contractor shall work with the government assigned ISSO to ensure secure management of user credentials (storing, transmitting, authenticating of user credentials shall be encrypted).
The Contractor shall ensure cybersecurity and privacy requirements are included into needs assessment, requirements gathering, development and testing by the Contractor for all solutions by the Contractor. The Contractor shall incorporate the cybersecurity and privacy requirements into the development lifecycle along with the user functional requirements for their developed solutions residing within their area of responsibility. The Contractor shall ensure data encryption in transit and secure authentication for their developed solutions residing within their area of responsibility.
The Contractor shall work with the government assigned ISSO perform a full source code review and application code scanning for vulnerabilities and remediation performed at least every 60 days with public facing systems being vulnerability scanning and remediation performed at least weekly. Any identified source code review deficiencies or scanner identified vulnerabilities and/or secure baseline findings, the Contractor shall mitigate and any other generated supporting documentation including the raw vulnerability scanner reports shall be provided. The Contractor shall ensure all source code updates undergo a full source code review, full source code scanning and mitigation of vulnerabilities and secure baseline findings with the appropriate documentation provided to the government for each update demonstrating this security requirement has been maintained. The Contractor shall provide the source code to the government for each product update, enhancement and/or security flaw remediation.
1.013 Task Manager (TM): The TM is:
Mike Shelby 1305 East-West Highway, N/MB6 SSMC4, Suite 9623 Silver Spring, MD 20910
(240) 533-0876 Email: Mike.Shelby@noaa.gov Cell: (443) 745-0400
The TM or delegate monitors all technical aspects of the contract and assists in contract administration. The TM is authorized to perform the following functions: assure that the contractor performs the technical requirements of the contract; perform inspections necessary in connection with contract performance; maintain written and oral communications with the contractor concerning technical aspects of the contract; issue written interpretations of technical requirements, including Government drawings, designs, specifications; monitor contractor's performance and notify the Contracting Officer, COR and contractor of any deficiencies; coordinate availability of government furnished property, and provide site entry and badging of contractor personnel. The TM is not authorized to change any of the terms and conditions of the resulting order.
1.1 General PWS Information
1.10 Conservation of Utilities. The contractor shall instruct employees in utilities conservation practices. The contractor shall be responsible for operating under conditions that preclude the waste of utilities, which include turning off the water faucets or valves after using the required amount to accomplish cleaning vehicles and equipment.
1.11 Post Award Conference/Periodic Progress Meetings: The contractor agrees to attend any post award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5. The Contracting Officer, Contracting Officer’s Representative (COR), Task Manager (TM), and other Government personnel, as appropriate, may meet periodically with the contractor to review the contractor's performance. At these meetings the Contracting Officer will apprise the contractor of how the government views the contractor's performance and the contractor will apprise the Government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the government.
mailto:Mike.Shelby@noaa.gov
1.12 Contract Manager: The contractor shall provide a contract manager who shall be responsible for the performance of the work. The name of this person and an alternate who shall act for the contractor when the manager is absent shall be designated in writing to the Contracting Officer. The contract manager or alternate shall have full authority to act for the contractor on all contract matters relating to daily operation of this contract.
1.13 Processing and Identification of Contractor Employees: Prior to commencing work under this contract, the contractor shall submit or have their employees submit the required security forms and number of copies as informed by the Task Manager. The contractor, when notified that the Government rejected the suitability assessment forms shall either have the rejected forms made compliant and resubmitted or withdraw the employee from consideration from working under this contract.
All contract personnel attending meetings, answering Government telephones, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are Government officials. They must also ensure that all documents or reports produced by contractors are suitably marked as contractor products or that contractor participation is appropriately disclosed.
1.14 Quality Assurance: The contractor shall ensure quality assurance in accordance with the approved QAP as applicable to the services performed in accordance with this PWS. The contractor shall develop and implement procedures specific to this requirement to identify, prevent, and ensure non-recurrence of defective services. The contractor’s quality assurance program is the means by which he assures himself that his work complies with the requirement of the task order. At a minimum, the contractor shall develop quality assurance procedures that address the areas identified in Technical Exhibit 1, “Performance Requirements Summary.”
Quality Assurance Surveillance Plan: The government shall evaluate the contractor’s performance under this task order in accordance with the Quality Assurance Surveillance Plan. This plan is primarily focused on what the Government must do to ensure that the contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s).
Government Remedies: The contracting officer shall pursue remedies for the contractor’s failure to perform satisfactory services or failure to correct non-conforming services in accordance with the terms and conditions of the contract.
PART 2
DEFINITIONS & ACRONYMS
● PWS – Performance Work Statement
● Contracting Officer’s Representative (COR). A representative from the requiring activity assigned by the Contracting Officer to perform surveillance and to act as liaison to the contractor.
● Defective Service. A service output that does not meet the standard of performance associated with it in the Performance
Work Statement.
● Owner Furnished Equipment (OFE). hardware that is provided by the Government.
● Quality Assurance Surveillance Plan (QASP). An organized written document specifying the surveillance methodology to be used for surveillance of contractor performance to assure services meets the requirements of the Performance Work
Statement.
● Quality Assurance. Those actions taken by a contractor to control the performance of services so that they meet the requirements of the PWS.
PART 3
GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, AND SERVICES
3.01 General: The government shall provide a fully operational studio, fiber and copper network and fiber/copper attached computers located on the 9th floor of 1305 East-West Hwy, Silver Spring MD 20910 in which to install, configure and test all Pegasus asset management and Quantum storage solutions as part of this action.
3.011 Facilities and Equipment: The Government will provide access to the studio space and all areas necessary for installation, configuration and testing of the asset management and storage systems requested as part of this action.
3.012 Equipment: The Government will provide GFE computers, rack space, necessary power and cooling to house the storage solution requested as part of this action. The existing rack is 18U (1U occupies 1.75”) with a depth of 33 inches.
PART 4
CONTRACTOR FURNISHED ITEMS AND SERVICES
4.01 General: Except for those items specifically stated to be government furnished in Part 3, the contractor shall furnish everything required to perform this PWS. This includes all hardware and software items necessary to engineer the asset management and storage solutions as described. Migration of the existing CatDV to CatDV Pegasus asset management system and migration of all media assets housed on the existing Cohesity storage to Quantum storage solutions can not be overstated. The contractor shall budget sufficient time and resources to ensure migration of both systems is completed and verified in the time stated for delivery.
PART 5
APPLICABLE PUBLICATIONS
5.01 Publications applicable to this PWS are listed below.
Not applicable.
Publication Date Page(s) Internet Address Mandatory/Advisory
NOS_Video_WS_Sum mary_Report
June 5, 2009 15 https://oceantoday.noaa.gov/o ceannewskiosk/otksoftware/do cs/NOS_Video_WS_Summary _Report.pdf
Advisory (metadata used in current CatDV system) https://oceantoday.noaa.gov/oceannewskiosk/otksoftware/docs/NOS_Video_WS_Summary_Report.pdf
TECHNICAL EXHIBIT 1
Performance Requirements Summary
PERFORMANCE REQUIREMENT SUMMARY (PRS) -
Item Performance Objective
Acceptable Quality Level
(AQL)
Method of Surveillance
Incentive/Disincentive Sample Size (optional)
Frequency (optional)
Fully Functioning CatDV Pegasus Asset Management System
Video editor is able to set up a new project and complete work tasks using Adobe Premiere, accessing existing media assets while using a system within the studio boundaries.
100% 100% inspection Incentive = none as this is the task they have been hired to complete.
Disincentive = Corrective action plan submitted to TM and COR for review
3 Once per editor.
Fully Functioning Quantum Storage System.
NOAA video editor is able to access and store media assets without permission issues while using a system within the studio boundaries.
100% 100% inspection Incentive = none as this is the task they have been hired to complete.
Disincentive = Corrective action plan submitted to TM and COR for review
3 Once per editor.
Fully Functioning CatDV Pegasus Desktop and Web clients.
NOAA video editor is able to search, browse and access media assets without permission issues while using a system within the studio boundaries.
100% 100% inspection Incentive = none as this is the task they have been hired to complete.
Disincentive = Corrective action plan submitted to TM and COR for review
3 Once per editor.
Detailed Interconnect Binder with Documentation
One completed binder
100% 100% inspection Incentive = none as this is the task they have been hired to complete.
1 Once
Disincentive = Corrective action plan submitted to TM and COR for review
Hardware warranty and specifications Binder
One completed binder
100% 100% inspection Incentive = none as this is the task they have been hired to complete.
Disincentive = Corrective action plan submitted to TM and COR for review
1 Once
Types of Surveillance to select from:
Random Sampling: Appropriate for frequently recurring tasks. Evaluate randomly selected samples of the lot to determine the acceptability of the entire lot.
Random Inspection Guide, Method of surveillance, Lot size, Sample size, Performance requirement, Sampling procedure, Inspection procedure 100 % Inspection: Appropriate for tasks that occur infrequently. Inspect and evaluate performance each time task is performed Periodic Surveillance: Evaluation of samples selected on other than 100% or statistically random basis. (i.e. monthly, quarterly, semi-annually, etc.)
Validated Customer Complaint: Complaints must be validated.
File details come from the government source that posted it. Updated .