R.2 -- Attachment 3 - 1305M320RNRMN0002 - Statement of Objective (SOO) Amendment 02 - Track Changes.pdf

ATTACHMENT 3 – R.21 EARTH PREDICTION INNOVATION CENTER (EPIC)

Department of Commerce (DOC) National Oceanic and Atmospheric Administration (NOAA)

Office of Oceanic and Atmospheric Research (OAR) Office of Weather and Air Quality (OWAQ)

INDEFINITE DELIVERY INDEFINITE QUANTITY (IDIQ)

STATEMENT OF OBJECTIVES (SOO)

Earth Prediction Innovation Center (EPIC)

ATTACHMENT 3

1305M320RNRMN0002

REVISION 21

Contents

1. 3

2. 3

3. 8

4. 8

5. 9

6. 9

7. 10

8. 13

9. 13

10. 14

11. 15

1. INTRODUCTION

The Department of Commerce (DOC), National Oceanic and Atmospheric Administration (NOAA), Office of Oceanic and Atmospheric Research (OAR) Office of Weather and Air Quality (OWAQ) supports world-class weather and air quality research to save lives, reduce property damage, and enhance the national economy.

In pursuit of its vision and mission, OWAQ works closely with the National Weather Service (NWS) to help develop and transition to operations weather and air quality research, including hurricanes, severe thunderstorms, heavy precipitation, and air pollution. Additionally, OWAQ utilizes social science to learn how to deal with the uncertainties weather presents and to inform its engagement and communication with researchers, decision makers, and the public. See NOAA’s definition of social science here.

Furthermore, OWAQ selects and funds research that supports and fosters collaborations — within NOAA's research laboratories and across the Weather Enterprise (i.e. NOAA, other Federal agencies and entities, state and local governments, academia, and the private sector).

2. BACKGROUND

The Weather Research and Forecasting Innovation Act of 2017 (WRFIA), P.L. 115-25, instructs NOAA to prioritize improving weather data, modeling, computing, forecasting and warnings for the protection of life and property and for the enhancement of the national economy. Additionally, the National Integrated Drought Information System Reauthorization Act of 2018 (NIDISRA), P.L. 115-423, instructs NOAA to establish the Earth Prediction Innovation Center (EPIC) to accelerate community-developed scientific and technological enhancements into the operational applications for numerical weather prediction (NWP). Specifically, Section 4 of NIDISRA articulates Congress’ vision for the EPIC program and charges NOAA with the following responsibilities:

“Advancing weather modeling skill, reclaiming and maintaining international leadership in the area of numerical weather prediction, and improving the transition of research into operations by—

A. leveraging the Weather Enterprise to provide expertise on removing barriers to improving numerical weather prediction;

B. enabling scientists and engineers to effectively collaborate in areas important for improving operational global numerical weather prediction skill, including model development, data assimilation techniques, systems architecture integration, and computational efficiencies;

C. strengthening the National Oceanic and Atmospheric Administration’s ability to undertake research projects in pursuit of substantial advancements in weather forecast skill;

D. utilizing and leveraging existing resources across the National Oceanic and Atmospheric Administration enterprise; and

E. creating a community global weather research modeling system that—

i. is accessible by the public;

ii. meets basic end-user requirements for running on computers and networks apart from and not associated with secure NOAA information and technology systems; and

iii. utilizes, whenever appropriate and cost-effective, innovative strategies and methods, including cloud-based computing capabilities, for hosting and management of part or all of the system described in this subsection”.

The amended WRFIA language for EPIC describes NWP in the global scale context. Therefore, the near-term program formulation will be focused on the end-to-end operational Global Forecast System (GFS) or UFS Weather Application that is composed of the Global Data Assimilation System (GDAS), the model and Unified Post Processor (UPP). EPIC will work closely with NOAA and the broader community to support and release experimental versions of the UFS Weather Application in the near term. It is expected that the scope of EPIC will expand to include other operational model applications and mission priorities outlined in the 2017 WRFIA such as convective allowing models (i.e., High Resolution Rapid Refresh) and fully coupled subseasonal-to-seasonal (S2S) forecast systems (i.e., the Climate Forecast System (CFS), National Water Model (NWM) and Ocean Forecast Systems). NOAA also recognizes the need to extend Research to Operations and Operations to Research (R2O/O2R) standards and practices to all disciplines within the agency and to create the advanced capability needed to extend weather model output downstream to water, land, living resources, and human communities.

The transition of R2O/O2R has been studied and reported on for decades. NOAA established testbeds and proving grounds to facilitate the orderly transition of research capabilities to operational implementation through development testing in testbeds, and pre-deployment testing and operational readiness/suitability evaluation in operational proving grounds (NOAA Testbeds and Proving Grounds Portal). At least two of the testbeds are focused on NWP and based on interagency agreements between NOAA, the National Aeronautics and Space Administration (NASA), the United States Air Force (USAF), The United States Navy (USN) and the National Center for Atmospheric Research (NCAR) to specifically address: 1) satellite data assimilation, via the Joint Center for Satellite Data Assimilation (JCSDA), established in 2001; and 2) mesoscale modeling, via the Developmental Testbed Center (DTC), established in 1999. The amended WRFIA states EPIC will utilize and leverage existing resources across NOAA. Given that the initial scope of EPIC is focused on global NWP it must effectively leverage activities under the JCSDA and DTC to be successful.

What is the Unified Forecast System (UFS)?

The UFS is a community-based, coupled, comprehensive Earth modeling system. The UFS numerical applications span local to global domains and predictive time scales from sub-hourly analyses to seasonal predictions. It is designed to support the Weather Enterprise and to be the source system for NOAA's operational numerical weather prediction applications.

NOAA is responsible for providing the official weather and climate forecasts and warnings in the United States. First and foremost, the UFS provides a framework to engage the extensive research enterprise in the US. It creates an environment to more efficiently and effectively translate research advances into operational outcomes. The UFS also enables NOAA to simplify its production suite of forecasting models from a great many independent systems, each of which has to be improved and maintained, to a single seamless system.

The UFS community is defined as researchers, developers and users from NOAA, educational institutions, other federal agencies, and the private sector, this includes both earth scientists and computer scientists. The UFS supports research and development in the community and accelerates the transition of research successes to operations.

UFS applications share numerical forecast system elements, including Earth-system model components (e.g.

atmosphere, ocean, sea ice, land, chemistry, etc.), observation processing, pre-processing, data assimilation, forward forecasting, ensemble and probabilistic processing, and post-processing. The applications share infrastructure such as model coupling tools and workflow software.

The UFS supports configurations for applications with varying levels of complexity. Unified infrastructure at the application level allows for coupled interactions among components while retaining:

● the ability to run simulations with different collections of model and workflow components,

● the ability to substitute prognostic model components with prescribed data components, and

● the ability to run ensembles and multiple instances of model components.

Unified infrastructure at the workflow level allows for runs with or without pre-processing, data assimilation, forward forecasting, reanalysis and reforecasting, ensemble and probabilistic processing, post-processing, and verification.

The UFS effort is working toward a verification and validation plan that spans UFS applications and supports evidence-based decision making. Infrastructure to support the execution of the plan is being developed in parallel to the plan itself.

A balance is sustained between the need to periodically update and synchronize components and infrastructure and the need for developers to work in their areas of interest without affecting or being affected by development in other areas. Areas of interest range from a single column physics routine to fully coupled applications.

NOAA Repository Plan using Gitflow

The idea of Gitflow originated from a blog that was written by Vincent Driessen in 2010. The original blog can be seen here. Gitflow is a philosophy for managing branches in a development repository. It is very clean and straightforward and has been adopted as the standard for code management all over the world. The figure from Vincent’s blog is reproduced below.

This is not a new idea and many code development communities are well aware of this approach. While the main idea has been for getting codes released for the public, the same principles apply for getting codes ready for transition to operations. At its heart the concept of Gitflow is a series of branches with strict functions:

Develop: This is the main development trunk. All code development uses this branch for syncing and coordinating. This is different from the master in very definite ways. Updates to develop can only be done by the code manager after the code has been approved by a team of assigned reviewers

Master: This is the branch that is the mature part of the development. It is the one that will be either released to the public or will be put in operations etc. It is updated much less frequently than the develop branch. It follows a strict testing protocol process before it is updated. Updates to master can only be done by the code manager after all the tests have been completed and reviewed by assigned reviewers

Feature: These are the branches where developers work. They are always created off of the develop branch to develop new ideas.

Release: This branch is created once the development reaches a certain stage that you are ready to “freeze” the code for a) release to the community and b) transition to operations. A release branch is where detailed exhaustive testing happens and bugs are fixed. This branch keeps getting merged back to develop to ensure that bug fixes get back to the main development trunk.

Hotfix: This is a bugfix branch that is only created from the master. This is to address immediate fixes that were overlooked in the testing process (it will happen, rest assured).

Figure 1: A Git Flow branching Strategy taken from Vincent Driessen’s blog

EPIC is responsible for all UFS applications. These applications will integrate the modeling components that are under development by the scientific community. User support of the community and testing of the UFS applications is the responsibility of EPIC.

Description of Hierarchical System Development

Hierarchical system development (HSD) is the ability to engage in development and testing at multiple levels of complex prediction software, essential capabilities for advancing UFS. It is critical for supporting research because it enables researchers to have multiple entry points into development that reflect their interests. Those interests may include aspects of specific system components such as atmospheric physics, ocean and ice dynamics, or data assimilation for land models and other individual Earth system components. It may also include more integrative aspects such as coupled modeling or data assimilation. HSD is likewise critical for operations because both localized and integrative, coupled processes must be improved to develop excellence in forecasts. UFS collaborators developed a short article that outlines the types of tests and development practices that will enable HSD to become an integral part of UFS.

The Unified Forecast System (UFS) as envisioned will consist of a series of applications. Each of these applications will be an umbrella repository that will point to multiple authoritative repositories. Figure 2 provides a schematic representation of a UFS application.

Figure 2: Schematic representation of a UFS application

Figure 3. EPIC’s UFS Infrastructure graphic showing how community models are connected to a single UFS Weather Application. A multitude of partners will be doing development on both the component model side and application side. EPIC is responsible for pulling together the robust application.

In Figure 3, it shows the UFS Weather Application on Github (repository is publically available) with different entities/partners that are capable of running a version of this application using their own HPC systems. The community models on the right is where the scientific innovation is developed by researchers and shared across a common code base (i.e. FV3dycore) that allows innovation across organizational boundaries. For instance, NOAA labs and NASA may do development on the FV3dycore, it’s the job of EPIC to test these innovations for the UFS Weather Application. NOAA has code managers for each of the component models.

3. PURPOSE

The purpose of this effort is to develop and support the establishment of EPIC. EPIC will create a community earth system model, initially focusing on the operational weather prediction system, which is accessible to the public and utilizes innovative strategies to host and manage the modeling system. EPIC will leverage existing NOAA resources to accelerate advances to the Unified Forecast System, a community-based, state of the science, coupled Earth system model designed to impact NOAA's operational forecast mission to protect life and property and improve economic growth.

4. SCOPE OF WORK

The scope of the resulting contract will include all necessary personnel, equipment, materials, facilities, supplies and services for the development and support of the EPIC and the Unified Forecast System (UFS) as outlined in this Statement of Objectives (SOO).

5. PLACE OF PERFORMANCE

To be determined at the task order level.

6. PERFORMANCE OBJECTIVES

The Government anticipates establishing EPIC with the following performance objectives, which the contractor shall be capable of supporting:

A. EPIC will be an established, respected, and highly sought after organization that supports the development and advancement of an end-to-end UFS in collaboration with scientists from the federal, academic, and private sectors.

B. EPIC will support community model development for the UFS using a comprehensive set of modern development tools and infrastructure. This includes modernized and state of the science UFS code, workflow, build (i.e. cmake), tests, documentation (English language), data pre- and post-processing for UFS applications. The current set of applications include:

a. Medium-Range Weather - Atmospheric behavior out to about two weeks

b. Subseasonal-to-Seasonal - Atmospheric and ocean behavior from about two weeks to about one year

c. Short-Range Weather/Convection-Allowing - Atmospheric behavior from less than an hour to several days

d. Hurricane - Hurricane track, intensity, and related effects out to about one week

e. Space Weather - Upper atmosphere geophysical activity and solar behavior out to about one month

f. Marine and Cryosphere - Ocean and ice behavior out to about ten days

g. Coastal - Storm surge and other coastal phenomena out to about one week

h. Air Quality - Aerosol and atmospheric composition out to several days

C. EPIC will accelerate the transition of research to operations, with the objective of improving numerical guidance from NOAA Operational modeling systems and products.

D. EPIC will manage and develop open source software and access repositories that are adopted by the community and defined by NOAA.

E. When required pursuant to a Task Order award, EPIC will provide a facility for innovation, training, workshops, and collaboration among NOAA and other interested federal staff, industry, other interested members of the public, and members of the academic community doing community model research and development on the UFS. [Note that for large community workshops and meetings NOAA will provide workshop space at one of its facilities with large conference capability, most likely at one of the following three locations: Silver Spring Metro Center Building 4 in Silver Spring, Maryland, Earth System Research Laboratory in Boulder, Colorado, and the National Severe Storms Laboratory in Norman, Oklahoma.]

F. EPIC will engage with the broader weather community by way of hosting breakout sessions at community forums, such as, AGU and AMS.

G. EPIC will develop and monitor github metrics for community engagement, development and downloads of UFS Codes.

H. Use project management principles to monitor, track, and report on UFS progress.

I. EPIC will integrate social science insights to make UFS and its processes more efficient.

J. EPIC will develop a containerized (docker, singularity, etc…) version of the UFS running and supported in the cloud.

K. EPIC will leverage and collaborate with existing UFS development and framework efforts as appropriate.

L. EPIC will use modern software engineering practices and design a DevSecOps

(https://www.redhat.com/en/topics/devops/what-is-devsecops) approach to UFS development.

M. EPIC will conduct business using an evidence-based decision making approach.

N. EPIC contractors will be accessible to UFS community developers.

O. EPIC will employ a governance model that aligns with its vision and mission.

7. REQUIREMENTS

The requirements in this section are a minimum capability, condition, or attribute required of the EPIC support contractor. EPIC will:

a. Project Management (Key Personnel)

i. A Project Manager will provide the primary interface with the NOAA Program Lead, Contracting Officer, Contracting Specialist, and Contracting Officer’s Representative.

ii. As the EPIC contractor lead, the Project Manager shall provide overall responsibility for the success of the EPIC contract, including working with the lead architect and software engineer providing leadership, vision, and guidance to the EPIC contractor staff.

iii. Shall be responsible for tracking progress on EPIC milestones, reporting on progress to the Government, and bringing issues and proposed solutions to the attention of the Government throughout the life of the contract.

iv. The Project Manager shall be responsible for recruiting, training, and retaining a high-quality, highly technical, and diverse workforce (with the required education, specialized training, licenses, and/or certifications).

v. Project Manager - shall possess a PMP Certification at the time of proposal submission, or, if the candidate does not possess a PMP Certification at the time of proposal submission, documentation demonstrating that the proposed candidate will have obtained a PMP Certification by no later than Contract Award, which is currently anticipated for the month of September 2020.

b. Cloud System Architect (Key Personnel)

i. Shall develop a cloud-based HPC Software Program Architecture that easily works on traditional HPC environments.

ii. Architecture shall include EPIC user community outreach programs, UFS code improvement services in collaboration with scientists, comprehensive code and science-based documentation, services and support for the development and integration of scientific software components, tools for user support requests, user facing documentation such as user’s guides, release notes, known issues, tutorials and developer’s guides, scientific software and HPC oriented training and tutorials both online and in person, designing, providing and supporting scientific code hackathons, sprints and workshops, and developing and maintaining infrastructure to help enable culture change toward community development, R2O/O2R and other approaches such as web presence, innovation hubs and other social media.

c. Lead Cloud Computer Scientist/Software Engineer (Key Personnel)

i. Develops continuous integration and continuous delivery pipelines for EPIC software development

ii. Leads the Cloud software engineering efforts that will lead to UFS code improvement services in collaboration with scientists, comprehensive code and science-based documentation, services and support for the development and integration of scientific software components, development and use of tools for user support requests, development and maintenance of user facing documentation such as user’s guides, release notes, known issues, tutorials and developer’s guides, scientific software and HPC oriented training and tutorials both online and in person, designing, providing and supporting scientific code hackathons, sprints and workshops, and developing and maintaining infrastructure to help enable culture change toward community development, R2O/O2R and other approaches such as web presence, innovation hubs and other social media.

d. Software Engineering

i. EPIC will employ a team of professional software, infrastructure and computational engineers to work directly with scientists in an integrated cross-disciplinary environment to ensure that the UFS code is easily maintainable, extensible and performance optimized.

ii. Employ modularity, the design principle known as separation of concerns (SoC1).

iii. Develop and execute clear project deliverables and success metrics.

e. User Support Services

i. Provide support for configurations of the UFS applications with varying levels of complexity. Support services will be low (~20-40 requests per month) and will increase (100-200 per month) as UFS applications are added and adoption of modeling systems by the user community increases due to outreach and user-friendly nature of the UFS modeling systems supported by EPIC. Support is required for, but not limited to:

1. the ability to run simulations with different collections of model and workflow components,

2. the ability to substitute prognostic model components with prescribed data components, and

3. the ability to run ensembles and multiple instances of model components.

ii. Work with Government provided communications platform, or provide a communications platform (such as slack) for interaction within the UFS community that includes researchers, developers and users from NOAA, educational institutions, other federal agencies, and the private sector.

iii. Provide code-improvement services for, and in collaboration with, scientists, such as integration of new algorithms, code refactoring, and optimization of the code as software and computing platforms evolve.

iv. Provide comprehensive code and science-based documentation. The documentation will address all four core technology capabilities, including: how the code is managed and code versions are controlled; the types of administrative code management activities that are performed; best practices that will be enforced to ensure model code portability to a variety

1. 1In computer science, separation of concerns (SoC) is a design principle for separating a computer program into distinct sections, so that each section addresses a separate concern. A concern is a set of information that affects the code of a computer program.

of computing platforms; and the test cases and verification packages used.

v. Provide services and support for the development and integration of the component models used in the UFS which currently consist of the Finite Volume Cubed (FV3) atmosphere, the Common Community Physics Package (CCPP), the Modular Ocean Model 6 (MOM6), the WAVEWATCH III wave model, the Los Alamos sea ice model 5 (CICE5), the Noah and Noah-MP land models, the Goddard Chemistry Aerosol Radiation and Transport (GOCART) aerosol model, the Ionosphere-Plasmasphere Electrodynamics (IPE) model, National Water Model, and the ocean models for storm surge, tides, and coastal circulation including Regional Ocean Modeling System (ROMS), Finite Volume Community Ocean Model (FVCOM), and Advanced Circulation model (ADCIRC).

vi. Provide IT Service Management tools that allows provenance traceability, self-service, automation, and escalation of user support requests.

vii. Produce online user’s guide, release notes, known issues, tutorials, and developers guide with each release of software produced by EPIC.

viii. Provide training/tutorials online and in person at a suitable facility for EPIC and learning of UFS tools and software.

ix. Design and support hackathons, code sprints, and scientific workshops to solve problems identified by the UFS community.

x. Maintain a web presence that enables information sharing with the community.

xi. Provide access to an innovation hub that will allow collaboration with scientists from the weather community and onsite training for students and model developers of the UFS, as needed

xii. Support, foster, and encourage NOAA’s culture change to open source community modeling, cloud computing, and improvements in R2O/O2R processes.

xiii. The contractor will aid the government in defining and implementing a NOAA cloud computing transformation process. The contractor shall possess knowledge of enterprise architecture consolidation techniques sufficient to enable NOAA to migrate to a common end-to-end cloud architecture. The contractor shall have led cloud-based HPC and non-HPC transform or enterprise consolidation efforts for government clients.

f. Software Infrastructure

i. Provide partnership and leadership in the technical aspects of developing a world-class UFS as a community-based, coupled, comprehensive Earth system model.

ii. Provide advanced infrastructure and software to improve UFS applications that are ensemble-based and span local to global domains and predictive time scales from hours to greater than one year.

iii. Provide a workflow management process to configure, build (i.e. cmake), test, and run the UFS across all applications.

iv. Provide a UFS code that is innovative, modern, maintainable, extensible, performance optimized, and appropriately portable to on-premise (Weather and Climate Operational Supercomputing System [WCOSS] and other NOAA systems) and cloud HPC architectures.

v. Provide an enterprise-level agile development approach to accelerate software testing across multiple infrastructure environments.

vi. Provide cloud-ready containerization of the UFS and provide and support container technology to improve developer productivity, efficiency, and application portability. Cloud computing deliverables shall be compatible with the AWS, Google, and Azure platforms.

vii. Provide a comprehensive testing infrastructure that encompasses regression, hierarchical and unit, quality assurance, code coverage and performance testing. Incorporation of unit tests through complete system tests will be required for any new code to be accepted into the

UFS.

viii. Review all codes from the community and ensure proper IT security measures prior to transition of code to master copy. IT security measures will be provided by NOAA when contract is awarded.

ix. Provide code management of UFS applications and use business practices that employ Continuous Integration/Continuous Deployment (CI/CD) approaches that automatically build and test all proposed code changes in its testing infrastructure.

x. Ensure the hierarchical testing framework works across all UFS modeling components.

g. Provide recommended governance model for oversight and management of EPIC.

8. CONSTRAINTS

● Future budgets are unknown and may impact the successful continuation or completion of this statement of objectives.

● General government participation and involvement will be high due to NOAA corporate priorities.

9. EPIC AND UFS INFORMATION AND DOCUMENTATION

The following documents are provided for guidance:

See UFS website: UFS Portal (ufscommunity.org) https://ufscommunity.org/ Most recent UFS Medium Range Weather Application Current UFS Medium Range Weather Release on Github (model and wiki) UFS Development Goals and Priorities for Medium-Range and S2S Applications UFS Research to Operations Plan UFS Repository Management Plan Annual Update of UFS Strategic Implementation Plan (current version is FY19-21) Strategic Implementation Plan Communications and Outreach PlanStrategic Implementation Plan Communications and Outreach Plan Community Modeling Review Committee Report (https://ufscommunity.org/wp-content/uploads/2019/11/CMCAugust2018Report_Final.pdf) NCAR-NOAA Memorandum of Agreement (MOA) for Co-development of a Common Modeling Infrastructure NOAA Software and Software Products Public Release GuidanceNOAA Software and Software Products Public Release Guidance https://ufscommunity.org/wp-content/uploads/2019/11/20171113_NOAA_Software_Public_Release_Guidance_FINAL.pdf NOAA GitHub.com Usage GuidelinesNOAA GitHub.com Usage Guidelines https://ufscommunity.org/wp-content/uploads/2019/11/20170823_NOAA_GitHub_Usage_Guidelines.pdf DRAFT EPIC Strategic Plan (https://wpo.noaa.gov/portals/0/Draft%20__%20EPIC%20Strategic%20Plan%202020- 0316_V3.pdf?ver=2020-03-20-085659-220) DRAFT EPIC Governance Principles (https://wpo.noaa.gov/portals/0/Draft%20EPIC%20Governance%20Principles%202020- 0319.pdf?ver=2020-03-20-094702-973)

10. EPIC DELIVERABLES

Item Deliverable Frequency/Date of First Submission

Medium/Format Submit To

1 Kickoff Meeting Within 20 business days after award

Meeting OWAQ (COR and Task Manager)

2 Monthly Progress Report Monthly, due on the 5th of each month following award

Electronic copy in format TBD by COR or OWAQ Program Office

OWAQ (COR

and Task Manager)

3 Produce Project Management Plan, Update Project Development Roadmap and Plan, Updated Repository Management Plan, all coordinated with UFS Leadership

Within 12 months of award

Electronic copy in format TBD by COR or OWAQ Program Office and presentation to the EPIC community

OWAQ (COR

and Task Manager)

4 Quarterly reviews Quarterly/3-months after award

Meeting with quarterly report submitted via Electronic copy in format TBD by COR or OWAQ Program Office

OWAQ

5 Actively participate in UFS Governance

Could be weekly to biweekly

Meeting OWAQ

6 Unified Forecast System Medium-Range Weather Application Release (including user’s guide, release notes, known issues, tutorial, and developers guide)

Annually (deliver in year 1 and years 2- 5)

Online Github OWAQ

7 Unified Forecast System Seasonal Application Release (user’s guide, release notes, known issues, tutorial, and developers guide)

Annually (deliver in year 2 and 3-5)

Online Github OWAQ

8 Unified Forecast System Short Annually (deliver in Online Github OWAQ

Range Weather/Convection Allowing Application Release (user’s guide, release notes, known issues, tutorial, and developers guide) year 1 or 2 and years 3-5)

9 Unified Forecast System Hurricane Application Release (user’s guide, release notes, known issues, tutorial, and developers guide)

Annually (deliver in year 2 or 3 and years 4-5)

Online Github OWAQ

10 Other Unified Forecast System Applications for Release

Annually (yr 4-5) Online Github OWAQ

11. GOVERNMENT FURNISHED EQUIPMENT (GFE)

1. Cloud access to FEDRamp Moderate (Google, Azure, and AWS). NOAA will not pay for the user community to access cloud-based tools developed by the EPIC contractor.

2. Access to UFS Github repositories (links in section 9)

3. Access to UFS Community Portal as communications platform