NRC-Alpha SOW.docx

Contents

National Oceanic and Atmospheric Administration (NOAA) Statement of Work for the replacement of the National Reconditioning Center’s (NRC) Alpha system’s user interfaces, user reports and data storage.

GENERAL

This statement of work is for Contractor services necessary to convert or replace the web accessible User Interfaces and User Reports of the National Weather Service (NWS)/National Reconditioning Center’s (NRC) Alpha inventory and maintenance system. These are fundamental system components of NOAA8223.

1.1 BACKGROUND

The Alpha system is designed to provide for the accounting, distribution and management of repairable items stored at the National Reconditioning Center (NRC). Its primary function is to function as an inventory management system, guiding all user interactions in the administration and manipulation of physical repairable inventories in safe, controlled and accountable ways. As such, the Alpha system supports the NRC’s client agency requirements by providing for the detailed tracking, accounting, maintenance and management of its repairable inventory, as well as well as imparting the ability to generate and produce a whole host of required management reports. Alpha is an interactive, menu–driven application, and it provides the following types of activities, functions and capabilities:

· User authentication and validation, which allow granular role-based access control to various aspects of the system, as determined by their job requirements, management’s needs, and IT security requirements.

· Detailed accounting of all repairable items received to and sent from the system, from a variety of internal and external agencies.

· Comprehensive equipment properties of current repairable items, as well as the status, tracking and accounting of repairable items as they pass through various aspects of the NRC’s repair processes.

· Thorough status, tracking and accounting of repairable items as they are sent to and received from approved vendors

· The ability to handle and process broad details about the inspection status of new consumables and NWS repairable items.

· The ability to link repair activities and movement with contract specific information, such as will need to happen with external repair vendor repairs.

· The ability to provide a variety of reports detailing aspects of the repairable items in the system. These reports are generated in both electronic and physical formats. Physical formats include 8.5” x11 paper reports, 2” x 4” printed labels, RFID labels, and a variety of Avery standardized labels, as selected by the user. Electronic formats include Portable Document Format (PDF), various text delimited documents such as Comma Separated Value (CSV), Semi-Colon Separated Value (SCSV), Extensible Markup Language (XML), Office Open XML(OOXML), and Open Document Format (ODF).

· Finally, Alpha uses both internal programs and a variety of reports to analyze statistical data, which is then used to develop and implement programs and procedures for the purpose of minimizing shortages of spares available to the field.

Alpha is component of the NOAA8223 CLS system, and is part of the NOAA accreditation and authorization designation of NOAA8223. Alpha consists of a single system, built out of Oracle Forms and Reports components, and relies on a data store currently accessed via an Oracle database.

· The Forms component handles all user interface (UI) actions. The Forms UI elements are built on top of Oracle Weblogic 12.2.1.3. While there are upgrades available for Forms and Weblogic, the requirement of Oracle Reports (next section) limits the migration potential of the Forms components.

· The Reports component is responsible for providing the reporting output as dictated by the Forms UI component, in whatever form is requested. Used extensively by the users of Alpha, Report options are expansive, and must include a wide variety of both physical and electronic formats. Physical reports need to appear on anything from standard 8.5” x 11” paper reports, to sheets of labels, to RFID tags, or to single 2”x4” printed labels printed on a dedicated label printers. Alpha Reports is built using Oracle Reports, which is depreciated as of Oracle Forms and Reports 12.2.1.3. This is primary limiting reason why Oracle Forms upgrades cannot be actuated.

· Both systems rely upon an Oracle Database 21c Pluggable database, which houses all of the current and historical repairable data.

The Alpha application is currently maintained by NRC personnel, who oversees changes to the application, to include content structure, quality control, and accessibility.

1.2 SCOPE

This acquisition contract is for software development services to convert the existing Alpha system to a new, supportable, web-browser based application. The UI and User Experience (UX) should be both user friendly and responsive, capable of user customizations to things including color and text size. Additionally, the new application will need to be able to access and modify the existing data stores, whether or not that is on the current storage solution, or a substantially similar product that is capable of supporting the applications needs. The vendor will conduct a thorough assessment of the current system, and provide the NRC with a plan for conversion and migration to the new application. The scope of the work for the Alpha redesign involves all planning, execution, implementation, and training for the new on-premise Alpha web application.

1.3 OBJECTIVE

This acquisition contract may be in multiple parts:

A. Forms conversion: Replace or convert no more than 350 Forms compiled programs. This includes creation, installation, configuration, testing and documentation of all aspects of the new user interface.

B. Reports conversion: Convert/replace no more than 350 Reports compiled programs. This includes creation, installation, configuration, testing and documentation of all aspects of the reporting infrastructure. This will include physical testing of the new reporting solution, with a variety of in-use printers and browsers.

C. Data management: Provide for the access and modification of current data stores, whether or not that is on the current storage solution, or a substantially similar product that is capable of supporting the applications needs. This will also include testing interaction and data transfer with the National Logistic and Supply Center’s (NLSC) CLS application.

1.4 APPLICABLE DOCUMENT

1.4.1 COMPLIANCE DOCUMENTS

The following documents provide specifications, standards, or guidelines that must be complied with in order to meet the requirements of this contract:

National Weather Service Directive 80-304 Software Development

2.0 SPECIFIC REQUIREMENTS/TASKS

The Contractor and associated subcontractors shall perform the following tasks:

1) Provide certification of the necessary software development skills and capacity required to complete the conversion. Determination of those adequate skills and capacity will be at the discretion of the NWS project team.

2) Provide all software development tools and computer systems necessary (i.e., software development environment) for replacing/converting the Alpha application and dependent data needs.

3) Conduct a document review and analysis of all generated code with the NWS project team with the aim of ensuring compliance with the projects scope

4) Collaborate with NWS project team to review software development and test environments that will support updating the project’s development.

5) Review the methodology used to complete the replacement/conversion of the Alpha system, with particular emphasis on the UI elements.

6) Review the methodology used to complete the replacement/conversion of the Alpha system, with particular emphasis on the Reporting elements.

7) Provide troubleshooting support to resolve any infrastructure issues that prevent NWS project team testers from completing their development or testing of the Alpha replacement project.

8) Establish a schedule for conducting a weekly review of activities occurring to achieve the replacement of the NRC Alpha system with NWS project team.

9) Deliver all computer software code, scripts, libraries, documentation, testing evidence and any other associated items required to complete the Alpha UI replacement to the NWS project team.

10) Deliver all computer software code, scripts, libraries, documentation, testing evidence and any other associated items required to complete the Alpha system’s reporting replacement to the NWS project team.

11) Deliver all computer software code, scripts, libraries, documentation, testing evidence and any other associated items required to complete any migration of data for the new Alpha system replacement to the NWS project team.

12) Deliver documentation for all procedures utilized to install, operate and maintain the replacement of the NRC’s Alpha system. Such documentation should cover all aspects necessary to sustain future maintenance of the delivered Alpha system, to include any UI elements, Reporting functionality and/or data migration.

13) Provide technical support to resolve application performance and processing errors (bugs) for the completed product that for one year after the completion of the project.

3.0 CONTRACTOR PERSONNEL

The Contractor and any associated subcontractors shall meet the following qualifications: Provide certification of the necessary software development skills and capacity required to complete the replacement/conversion of the Alpha system. Determination will be at the discretion of the NWS project team.

3.1 QUALIFIED PERSONNEL

The Contractor shall provide qualified personnel to perform all requirements specified in this SOW.

3.2 CONTINUITY OF SUPPORT

The Contractor shall ensure that the contractually required level of support for this requirement is maintained at all times. The Contractor shall ensure that all contract support personnel are present for all hours of the workday. If for any reason the Contractor staffing levels are not maintained due to vacation, leave, appointments, etc., and replacement personnel will not be provided, the Contractor shall provide e-mail notification to the Contracting Officer's Representative (COR) prior to employee absence. Otherwise, the Contractor shall provide a fully qualified replacement.

3.3 KEY PERSONNEL

See CAR Key Personnel clause - 1352.237-75.

3.4 PROJECT MANAGER

The Contractor shall provide a Project Manager who shall be responsible for all Contractor work performed under this SOW. The Project Manager shall be a single point of contact for the Contracting Officer and the COR. The name of the Project Manager, and the name(s) of any alternate(s) who shall act for the Contractor in the absence of the Project Manager, shall be provided to the Government as part of the Contractor's proposal. The Project Manager is further designated as Key by the Government. During any absence of Project Manager, only one alternate shall have full authority to act for the Contractor on all matters relating to work performed under this contract. The Project Manager and all designated alternates shall be able to read, write, speak and understand English. Additionally, the Contractor shall not replace the Project Manager without prior approval from the Contracting Officer.

3.4.1 The Project Manager shall be available to the COR via telephone between the hours of 9:00am and 5:00pm Central Time, Monday through Friday, and shall respond to a request for discussion or resolution of technical problems within 24 hours of notification.

EMPLOYEE IDENTIFICATION

3.5.1 Contractor employees visiting Government facilities shall wear an identification badge that, at a minimum, displays the Contractor name, the employee's photo, name, clearance-level and badge expiration date. Visiting Contractor employees shall comply with all Government escort rules and requirements. All Contractor employees shall identify themselves as Contractors when their status is not readily apparent and display all identification and visitor badges in plain view above the waist at all times.

3.5.2 Contractor employees working on-site at Government facilities shall wear a Government issued identification badge. All Contractor employees shall identify themselves as Contractors when their status is not readily apparent (in meetings, when answering Government telephones, in e-mail messages, etc.) and display the Government issued badge in plain view above the waist at all times.

3.6 EMPLOYEE CONDUCT

Contractor's employees shall comply with all applicable Government regulations, policies and procedures (e.g., fire, safety, sanitation, environmental protection, security, "off limits" areas, etc.) when visiting or working at Government facilities. The Contractor shall ensure Contractor employees present a professional appearance at all times and that their conduct shall not reflect discredit on the United States or the Department of Commerce. The Project Manager shall ensure Contractor employees understand and abide by Department of Commerce established rules, regulations and policies concerning safety and security.

3.7 REMOVING EMPLOYEES FOR MISCONDUCT OR SECURITY REASONS

The Government may, at its sole discretion (in coordination with the Contracting Officer where practical), direct the Contractor to remove any Contractor employee from NOAA facilities for misconduct or security reasons. Removal does not relieve the Contractor of the responsibility to continue providing the services required under the contract. The Contracting Officer will provide the Contractor with a written explanation to support any request to remove an employee.

4.0 OTHER APPLICABLE CONDITIONS

4.1 SECURITY

Contractor access to unclassified, but Security Sensitive Information may be required under this SOW. Contractor employees shall safeguard this information against unauthorized disclosure or dissemination.

4.2 PERIOD OF PERFORMANCE

The period of performance for this contract shall not exceed June 1, 2028.

4.3 PLACE OF PERFORMANCE

The primary place of performance will be the Contractor's facilities with frequent visits to the NOAA/NWS National Logistics and Reconditioning Center at 14200 Merritt Road, Grandview, MO 64030.

4.4 HOURS OF OPERATION

Contractor employees shall generally perform all work between the hours of 8:00am and 5:00pm EST, Monday through Friday (except Federal holidays). However, there may be occasions when Contractor employees shall be required to work other than normal business hours, including weekends and holidays, to fulfill requirements under this SOW.

4.5 TRAVEL

Contractor travel may be required to support this requirement. All travel required by the Government outside the local commuting area(s) will be reimbursed to the Contractor in accordance with the Federal Travel Regulations. The Contractor shall be responsible for obtaining COR approval (electronic mail is acceptable) for all reimbursable travel in advance of each travel event.

4.6 POST AWARD CONFERENCE

The Contractor shall attend a Post Award Conference with the Contracting Officer and the COR no later than 10 business days after the date of award. The purpose of the Post Award Conference, which will be chaired by the Contracting Officer, is to discuss technical and contracting objectives of this contract and review the Contractor's draft project plan. The Post Award Conference will be held at the Government's facility the NOAA/NWS National Logistics and Reconditioning Center, which is located at 14200 Merritt Road, Grandview, MO 64030 or via virtual conference.

4.7 PROJECT PLAN

The Contractor shall provide a draft Project Plan at the Post Award Conference for Government review and comment. The Contractor shall provide a final Project Plan to the COR not later than 10 business days after the Post Award Conference. The vendor’s project plan should include the following:

Table 4.1 - Required Project Plan Components

-Scope of Work

-Milestones & Deadlines -Phases of development (design, implementation, testing, etc)

-Resource loading

-Recommended mitigations -Contingency Plans

-Sprint planning roadmap

-Estimate of total time to test & number of tests -Regression testing

-Stakeholder engagement strategies (i.e. direct to FAA)

-Includes but not limited to: Manuals, RTMs, ICDs, Security Compliance tables, test reports

-Defined exit & acceptance criteria

4.8 BUSINESS CONTINUITY PLAN

The Contractor shall prepare and submit a Business Continuity Plan (BCP) to the Government. The BCP Plan shall be due 20 business days after the date of award, and will be updated on a quarterly (3-month) basis. The BCP shall document Contractor plans and procedures to maintain support during an emergency, including natural disasters and acts of terrorism. The BCP, at a minimum, shall include the following:

A description of the Contractor's emergency management procedures and policy A description of how the Contractor will account for their employees during an emergency How the Contractor will communicate with the Government during emergencies A list of primary and alternate Contractor points of contact, each with primary and alternate:

Telephone numbers E-mail addresses 4.8.1 Individual BCPs shall be activated immediately after determining that an emergency has occurred, shall be operational within 48 hours of activation or as directed by the Government, and shall be sustainable until the emergency situation is resolved and normal conditions are restored or the contract is terminated, whichever comes first. In case of a life-threatening emergency, the COR shall immediately make contact with the Contractor Project Manager to ascertain the status of any Contractor personnel who were located in Government controlled space affected by the emergency. When any disruption of normal, daily operations occurs, the Contractor Project Manager and the COR shall promptly open an effective means of communication and verify:

Key points of contact (Government and contractor) Temporary work locations (alternate office spaces, telework, virtual offices, etc.)

Means of communication available under the circumstances (e.g., email, webmail, telephone, FAX, courier, etc.)

Essential Contractor work products expected to be continued, by priority 4.8.2 The Government and Contractor Project Manager shall make use of the resources and tools available to continue contracted functions to the maximum extent possible under emergency circumstances. Contractors shall obtain approval from the Contracting Officer prior to incurring costs over and above those allowed for under the terms of this contract. Regardless of contract type, and of work location, Contractors performing work in support of authorized tasks within the scope of their contract shall charge those hours accurately in accordance with the terms of this contract.

4.9 PROGRESS REPORTS

The Project manager shall provide a weekly progress report to the Contracting Officer and COR via electronic mail. This report shall include a summary of all Contractor work performed, including a breakdown of labor hours by labor category, all direct costs by line item, an assessment of technical progress, schedule status, any travel conducted and any Contractor concerns or recommendations for the previous reporting period.

4.10 PROGRESS MEETINGS

The Project Manager shall meet with the COR on a weekly basis to discuss progress, exchange information and resolve emergent technical problems and issues. These meetings shall take place by virtual conference or upon COR request at the NOAA/NWS National Logistics and Reconditioning Center, 14200 Merritt Road, Grandview, MO 64030

4.11 GENERAL REPORT REQUIREMENTS

The Contractor shall provide all written reports in electronic format with read/write capability using applications that are compatible with NOAA workstations (e.g., Microsoft Windows and Microsoft Office Applications). Transmission of these reports shall be by email to COR and NWS Project Team.

4.12 INTELLECTUAL PROPERTY

All software and documentation provided to the Contractor from the NOAA8223 Alpha system shall remain the intellectual property of the Government. The software, documentation, data and other work products generated by the Contractor to fulfill the requirements of updating the NRC’s Alpha system shall be the intellectual property of the Government.

4.13 PROTECTION OF INFORMATION

Contractor access to proprietary information is required under this SOW. Contractor employees shall safeguard this information against unauthorized disclosure or dissemination in accordance with the Privacy Act, 0MB rv106-16 (PII) and other pertinent laws and regulations governing the confidentiality of privileged information and safeguarding Sensitive but Unclassified (SBU) (For Official Use Only) Information. The Contractor shall ensure that all Contractor personnel having access to business or procurement sensitive information sign a NOAA Non-Disclosure Agreement.

4.14 SECTION 508 COMPLIANCE

Pursuant to Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. 794d) as amended by P.L. 105-220 under Title IV (Rehabilitation Act Amendments of 1998) all Electronic and Information Technology (EIT) developed, procured, maintained and/or used under this contract shall be in compliance with the "Electronic and Information Technology Accessibility Standards" set forth by the Architectural and Transportation Barriers Compliance Board (also referred to as the "Access Board") in 36 CFR Part 1194. The complete text of Section 508 Standards can be accessed at https://www.access-board.gov/ or at https://www.section508.gov.

5.0 GOVERNMENT TERMS & DEFINITIONS

BCP - Business Continuity Plan CLS - Consolidated Logistics System COR - Contracting Officer's Representative DOC - Department of Commerce FISMA - Federal Information Security Modernization Act NOAA - National Oceanic and Atmospheric Administration NLRC – National Logistics and Reconditioning Center NRC – National Reconditioning Center NWS- National Weather Service OMB - Office of Management and Budget SBU - Sensitive but Unclassified SOW -Statement of Work

6.0 GOVERNMENT FURNISHED RESOURCES

The Government will provide all necessary information, data and documents to the Contractor for work required under this contract.

The Contractor shall use Government furnished information, data and documents only for the performance of work under this contract, and shall be responsible for returning all Government furnished information, data and documents to the Government at the end of the performance period. The Contractor shall not release Government furnished information, data and documents to outside parties without the prior and explicit consent of the Contracting Officer.

7.0 CONTRACTOR FURNISHED PROPERTY

The Contractor shall furnish all facilities, materials, equipment and services necessary to fulfill the requirements of this contract, except for the Government Furnished Resources specified in SOW 2.0 and SOW 6.0.

8.0 GOVERNMENT ACCEPTANCE PERIOD

The COR will review deliverables prior to acceptance and provide the contractor with an e-mail that provides documented reasons for non-acceptance. If the deliverable is acceptable, the COR will send an e-mail to the Contractor notifying it that the deliverable has been accepted.

8.1 The COR will have the right to reject or require correction of any deficiencies found in the deliverables that are contrary to the information contained in the Contractor's accepted proposal. In the event of a rejected deliverable, the Contractor will be notified in writing by the COR of the specific reasons for rejection. The Contractor may have an opportunity to correct the rejected deliverable and return it per delivery instructions.

8.2 The COR will have 20 business days to review deliverables and make comments. The Contractor shall have 20 business days to make corrections and redeliver.

8.3 All other review times and schedules for deliverables shall be agreed upon by the parties based on the final approved Project Plan. The Contractor shall be responsible for timely delivery to Government personnel in the agreed upon review chain, at each stage of the review. The Contractor shall work with personnel reviewing the deliverables to assure that the established schedule is maintained.

9.0 DELIVERABLES

The Contractor shall consider items in BOLD as having mandatory due dates. Items in italics are deliverables or events that must be reviewed and/or approved by the COR prior to proceeding to next deliverable or

Contracting Officer

Contracting Officer

Contracting Officer