Id.
Number
|
NEVS System Functional Requirements
|
NEVS Phase
|
|
Business Process
|
|
2.2.1
|
NEVS shall be a component of the NextGen systems of systems for the Cube.
|
Phase 1
|
2.2.2
|
NEVS shall provide verification services to the NWS and the FAA.
|
Phase 1
|
2.2.3
|
NEVS shall provide capabilities for all the RTVS weather forecast verification functionality.
|
Phase 1
|
2.2.4
|
NEVS shall provide data to the Cube using web services.
|
Phase 2
|
|
System Interfaces
|
|
2.2.5
|
NEVS shall have an interface to the Cube systems.
|
Phase 1
|
2.2.6
|
NEVS shall interface to other NWS verification systems.
|
Phase 2
|
|
System Modes and States
|
|
2.2.7
|
NEVS shall run in operational and backup mode
|
Phase 1
|
2.2.8
|
NEVS data ingest and processing on the operational system shall be mirrored on the backup system.
|
Phase 1
|
2.2.9
|
NEVS data storage shall be mirrored on the backup system.
|
Phase 1
|
2.2.10
|
NEVS data dissemination shall be mirrored on the backup system.
|
Phase 2
|
2.2.11
|
NEVS shall have a system maintenance mode that allows continuous data ingest and processing to proceed on the primary and backup systems without interruption.
|
Phase 1
|
2.2.12
|
NEVS system backup components shall be physically located with those of the 4-D Weather Cube IT infrastructure.
|
Phase 1
|
2.2.13
|
NEVS shall have backup capabilities for data ingest which mirror the primary data ingest.
|
Phase 1
|
2.2.14
|
NEVS shall have system backup hardware components for operational use during failover.
|
Phase 2
|
2.2.15
|
NEVS primary system components shall be physically located with those of the 4-D Weather Cube IT infrastructure.
|
Phase 1
|
|
Major System Capabilities
|
|
2.2.16
|
NEVS shall ingest forecasts required for verification processes from the Cube using Cube services.
|
Phase 1
|
2.2.17
|
NEVS shall ingest observations and analyses required for verification processes from the Cube.
|
Phase 1
|
2.2.18
|
NEVS shall store verification information required to maintain a historical record of product quality.
|
Phase 1
|
2.2.19
|
NEVS shall provide a web user interface to visualize verification results.
|
Phase 1
|
2.2.20
|
NEVS shall provide verification results to the Cube using web services.
|
Phase 2
|
2.2.21
|
NEVS shall ingest Aviation specific information required from the Cube.
|
Phase 2
|
|
Major System Conditions and Constraints
|
|
2.2.22
|
NEVS software shall be delivered in stages with Phase 1-3 using software releases.
|
Phase 1
|
2.2.23
|
NEVS capabilities for verification shall be extended incrementally.
|
Phase 1
|
2.2.24
|
All forecast data required for verification processing in NEVS shall be provided by the Cube.
|
Phase 1
|
2.2.25
|
All observational data required for verification processing in NEVS shall be provided by the Cube.
|
Phase 1
|
2.2.26
|
All subscriptions for verification data from NEVS will be managed by the Cube.
|
Phase 1
|
2.2.27
|
All subscription requests from the Cube for NEVS verification results shall be sent from the Cube to NEVS.
|
Phase 1
|
|
User Characteristics
|
|
2.2.28
|
NEVS shall provide verification results for a variety of authorized users.
|
Phase 1
|
2.2.29
|
NEVS shall provide access to verification users with a valid user login and access password.
|
Phase 1
|
2.2.30
|
NEVS shall provide remote access to verification results.
|
Phase 1
|
2.2.31
|
NEVS shall provide access to verification results for a minimum of 100 simultaneous users.
|
Phase 1
|
2.2.32
|
NEVS shall be able to distinguish user types.
|
Phase 1
|
2.2.33
|
NEVS shall have configurable permission settings
|
Phase 1
|
|
Assumptions and Dependencies
|
|
2.2.34
|
NEVS shall provide weather forecast verification functionality when the Cube is available and providing access to data.
|
Phase 1
|
2.2.35
|
NEVS shall provide verification data to AWIPS II.
|
Phase 2
|
2.2.36
|
NEVS shall ingest, process and provide verification results using verification data from Stats on Demand.
|
Phase 2
|
2.2.37
|
NEVS shall provide verification information to the Stats on Demand.
|
Phase 2
|
2.2.38
|
NEVS shall ingest verification data from the National Digital Forecast Database (NDFD) verification system.
|
Phase 2
|
2.2.39
|
NEVS shall provide verification reports as described in the FAA’s Quality Manual for the Quality Management System (QMS).
|
Phase 1
|
|
Operational Scenarios
|
|
2.2.40
|
NEVS shall provide capabilities for automated reporting of verification results for NWS Aviation Services Products in the Cube.
|
Phase 1
|
2.2.41
|
NEVS shall provide capabilities for automated reporting of verification results for selected data in the Cube.
|
Phase 1
|
2.2.42
|
NEVS shall provide capabilities for interactive selection of verification results from a web based interface.
|
Phase 1
|
2.2.43
|
NEVS shall provide verification reporting to support the manual determination of the SAS contents.
|
Phase 1
|
2.2.44
|
NEVS shall provide verification capabilities for a continuous historical record of product and data performance.
|
Phase 1
|
2.2.45
|
NEVS shall provide verification capabilities to support establishment of a performance baseline for new and existing products.
|
Phase 1
|
2.2.46
|
NEVS shall provide verification reporting to support performance management of NWS products.
|
Phase 1
|
2.2.47
|
NEVS shall provide web services for system to system exchange of data with authorized systems.
|
Phase 2
|
2.2.48
|
NEVS shall provide web services for delivery of verification results.
|
Phase 2
|
|
Construction
|
|
2.2.49
|
NEVS shall be installed in a facility that enables system hardware component maintenance on an as needed basis.
|
Phase 1
|
2.2.50
|
NEVS shall be installed in a facility that provides backup power capabilities.
|
Phase 1
|
2.2.51
|
NEVS shall be installed in a facility that is environmentally controlled.
|
Phase 1
|
2.2.52
|
NEVS shall be installed in a facility that enables periodic archival of data and software.
|
Phase 1
|
2.2.53
|
NEVS shall be installed in a facility that enables preventative maintenance.
|
Phase 1
|
2.2.54
|
NEVS shall be installed in a physical location that provides environmental and physical controls.
|
Phase 1
|
|
Durability
|
|
2.2.55
|
The facility where NEVS hardware is located shall comply with all Occupational Safety and Health Administration (OSHA) standards for electronic equipment and systems.
|
Phase 1
|
2.2.56
|
NEVS shall be designed so that it can remain fully operational for a minimum of a 15 year lifecycle.
|
Phase 1
|
2.2.57
|
NEVS performance shall be monitored and performance exceptions shall be logged.
|
Phase 1
|
|
Adaptability
|
|
2.2.58
|
NEVS hardware shall be extendable to meet anticipated growth in NEVS software capabilities out until 2022.
|
Phase 1
|
2.2.59
|
NEVS hardware shall be refreshed on a scheduled basis every three years:
-
To maintain system operations.
-
To improve the system performance.
-
To enable the system functionality to be extended.
-
To enable the data processing for the system to be extended.
-
To expand to interface with other verification systems.
|
Phase 2
|
2.2.60
|
NEVS shall process additional datasets as each subsequent major software release is implemented.
|
Phase 2
|
2.2.61
|
NEVS shall have connectivity to the communications systems for AWIPS II Data Delivery.
|
Phase 2
|
2.2.62
|
NEVS shall be interfaced with external verification systems for data exchange.
|
Phase 2
|
2.2.63
|
NEVS shall access aviation flight data from the FAA via the Cube in near real-time.
|
Phase 2
|
|
Environmental Conditions
|
|
2.2.64
|
NEVS hardware shall be maintained in a temperature controlled environment:
-
Temperature range between 10 degrees Celsius (C) and 35 degrees C.
|
Phase 1
|
2.2.65
|
NEVS hardware shall be maintained in a humidity controlled environment:
-
Humidity range between 30-80%
|
Phase 1
|
2.2.66
|
NEVS hardware shall be maintained in an environment with an elevation of up to 3000 meters above Mean Sea Level.
|
Phase 1
|
|
System Capabilities and Performance Characteristics
|
|
2.2.67
|
NEVS shall have system backup hardware components for operational use during failover.
|
Phase 1
|
2.2.68
|
NEVS primary system components shall be physically located with the centralized hardware subsystems of the Cube infrastructure.
|
Phase 1
|
2.2.69
|
NEVS system backup components shall be physically located with the centralized backup hardware subsystems of the Cube infrastructure.
|
Phase 1
|
2.2.70
|
NEVS shall have backup capabilities for data ingest which mirror the primary data ingest.
|
Phase 1
|
|
Information Management
|
|
2.2.71
|
Subscriptions to NEVS verification data provided via web services shall be processed by the Cube.
|
Phase 2
|
2.2.72
|
NEVS shall process subscriber requests for verification results from the Cube.
|
Phase 2
|
2.2.73
|
NEVS shall process Ad hoc requests for specified verification results from the Cube.
|
Phase 2
|
2.2.74
|
NEVS metadata shall be discoverable in the Cube.
|
Phase 2
|
2.2.75
|
NEVS metadata shall be provided for verification results.
|
Phase 2
|
2.2.76
|
Requests to NEVS for verification data shall be logged.
|
Phase 2
|
2.2.77
|
NEVS shall provide a graphical user interface for management of QMS verification reporting.
|
Phase 1
|
2.2.78
|
NEVS shall provide access control for the graphical user interface for QMS verification reporting.
|
Phase 1
|
2.2.79
|
After satisfying original QMS query, subsequent resubmission of that query shall be satisfied within one minute for a minimum of 15 days.
|
Phase 1
|
2.2.80
|
NEVS shall provide verification results using web services for AWIPS II.
|
Phase 2
|
2.2.81
|
NEVS shall publish verification results using web services for the Cube.
|
Phase 2
|
2.2.82
|
NEVS shall ingest verification data from the Stats on Demand verification system.
|
Phase 2
|
2.2.83
|
NEVS shall provide verification data to the Stats on Demand verification system.
|
Phase 2
|
2.2.84
|
NEVS shall ingest data from the National Digital Forecast Database verification system.
|
Phase 2
|
2.2.85
|
NEVS shall provide a storage system for data management that is extensible.
|
Phase 1
|
2.2.86
|
NEVS shall process data, forecasts, and observations in real-time.
|
Phase 1
|
2.2.87
|
NEVS verification results shall be made accessible within 15 minutes from the processing of the observational data required to verify the associated forecast.
|
Phase 1
|
2.2.88
|
NEVS shall provide a help desk function with web-based tools for users to interactively report on software defects.
|
Phase 1
|
2.2.89
|
NEVS shall provide a help desk function for users to interactively report on software enhancements and new functionality needed.
|
Phase 1
|
2.2.90
|
NEVS shall conform to World Wide Web Consortium (W3C) standards for HyperText Markup Language (HTML), XML and HyperText Transfer Protocol (HTTP) and HyperText Transfer Protocol Secure (HTTPS).
|
Phase 1
|
|
System Human Factors
|
|
2.2.91
|
NEVS shall provide gross error checks and logging of erroneous data occurrences for:
-
quality control of observational data processed for verification of forecasts
-
quality control of forecasts processed for verification
|
Phase 1
|
2.2.92
|
NEVS shall provide continuous monitoring and error handling for notification of any interruption in observational and forecast data ingest and processing.
|
Phase 1
|
2.2.93
|
NEVS shall provide error handling for exceptions occurring from user interface menu option selection interactions.
|
Phase 1
|
2.2.94
|
NEVS shall provide error handling for exceptions occurring in verification processing.
|
Phase 1
|
2.2.95
|
NEVS shall provide a user interface with a consistent presentation display for the various verification options.
|
Phase 1
|
2.2.96
|
NEVS shall provide visual notifications to users to acknowledge execution of requests that are not provided immediately.
|
Phase 1
|
2.2.97
|
NEVS shall provide a user interface with color schemes designed to accommodate use by color blind individuals.
|
Phase 1
|
2.2.98
|
NEVS shall provide capabilities for use by visually impaired individuals and meet NOAA standards for Section 508 compliance.
|
Phase 1
|
|
System Maintainability
|
|
2.2.99
|
NEVS system shall be maintained and monitored 24 hours a day and 7 days per week.
|
Phase 1
|
2.2.100
|
NEVS maximum downtime shall be 24 hours for each unplanned event.
|
Phase 1
|
2.2.101
|
NEVS mean time between software maintenance releases shall be 6 months.
|
Phase 1
|
2.2.102
|
NEVS shall have a mean time to repair of 8 hours for unplanned maintenance.
|
Phase 1
|
2.2.103
|
NEVS system maintenance reaction time shall be less than 1 hour after a critical defect which compromises essential operational functionality is identified.
|
Phase 1
|
2.2.104
|
NEVS system preventive software maintenance shall be performed on average every 6 months.
|
Phase 1
|
2.2.105
|
NEVS shall provide capabilities for system monitoring to report metrics on system performance and record the peak and average Central Processing Unit (CPU) utilization per 24 hour period.
|
Phase 1
|
2.2.106
|
NEVS shall provide metrics and record the number of data and products processed for verification per 24 hour period.
|
Phase 1
|
|
System Reliability
|
|
2.2.107
|
NEVS shall provide a failure on demand rate for user requests for services of greater than 0.001 (1 in 1000 requests will fail).
|
Phase 1
|
2.2.108
|
NEVS shall provide a failure occurrence rate of unexplained behavior (e.g., hanging software) greater than 0.02. (This shall be less than 2 occurrences of unexplained behavior per 100 days).
|
Phase 1
|
2.2.109
|
NEVS shall provide a Mean time to Failure rate of less than 100 days. (1 failure or fewer each 100 days)
|
Phase 1
|
2.2.110
|
NEVS shall provide availability greater than 0.99 for unplanned outages. (The system shall be available to users 99% of the time, or shall be in failure mode no more than 1% of the time)
|
Phase 1
|
2.2.111
|
NEVS connectivity to the data provided by the Cube system shall have an availability greater than 0.999. (The Cube system shall be available to NEVS for access to the required data 99.9% of the time)
|
Phase 1
|
|
Policy and Regulation
|
|
2.2.112
|
NEVS shall comply with the federal government policy for IT systems, and conform to guidelines and policies enacted at the federal, agency, and line office levels such as:
-
Federal Information Security Management Act of 2002 (FISMA)
-
FISMA 2010 requirements for continuous monitoring of security.
-
Federal Information Processing Standard (FIPS) 199, Standards for Security Categorization of Federal Information and Information Systems.
|
Phase 1
|
2.2.113
|
NEVS shall comply with NWS policy for Aviation Services products documented in NWS I 10-803, 10-811 and 10-813.
|
Phase 1
|
2.2.114
|
NEVS shall comply with NWS Verification Policy documented in the NWS I 10-1601.
|
Phase 1
|
2.2.115
|
NEVS shall comply with FAA QMS policy for verification reporting to meet ICAO requirements.
|
Phase 1
|
2.2.116
|
NEVS shall comply with NextGen standards for data exchange as a consumer and provider.
|
Phase 1
|
2.2.117
|
NEVS shall comply with NOAA guidance for Section 508 and be accessible to Federal employees with disabilities.
|
Phase 1
|
|
System Life Cycle Sustainment
|
|
2.2.118
|
NEVS shall log data processing execution for critical functionality to support quality reporting:
-
Data ingest of required observational data for verification.
-
Data ingest of required forecast products for verification.
-
High-level execution steps of verification processing.
|
Phase 1
|
2.2.119
|
NEVS shall centrally manage auditing, and limit access to audit logs to authorized security personnel.
|
Phase 1
|
2.2.120
|
NEVS shall log verification reporting for QMS to support quality assurance.
|
Phase 1
|
2.2.121
|
NEVS shall log verification results subscriptions.
|
Phase 1
|
2.2.122
|
NEVS shall provide auditing of the following events on a daily basis:
-
Account logon events
-
Account management events
-
Directory service access events
-
Object access failures
-
Policy change failures
-
Privilege use failures
-
System events
|
Phase 1
|
2.2.123
|
NEVS shall audit the following events:
-
User events
-
Successful and failed authentication attempts
-
File access
-
Account changes
-
Security policy changes
-
Use of system privileges
-
Time and nature of the event
-
User id associated with the event
|
Phase 1
|
2.2.124
|
NEVS audit records shall provide:
-
Type of event
-
Date and time (expressed in Coordinated Universal Time) of event
-
Location of event
-
Source of event
-
Outcome of event
-
User associated with event
-
Process associated with event
-
Success or failure
-
Filenames
-
Event description
-
Access control or flow control rules invoked
|
Phase 1
|
2.2.125
|
NEVS auditing capability shall provide a real-time alert to system custodians in the event of audit processing failures due to:
-
Software or hardware errors
-
Failures in the audit capturing mechanisms
-
Audit storage capacity being reached or exceeded.
|
Phase 1
|
2.2.126
|
When required to maintain auditing data storage levels below 75% capacity, NEVS auditing capability shall take the following actions:
|
Phase 1
|
2.2.127
|
NEVS auditing capability must protect against and individual falsely denying having performed the following action:
|
Phase 1
|
|
User Documentation
|
|
2.2.128
|
Training for NEVS shall be provided on the NOAA Commerce Learning Center.
|
Phase 1
|
2.2.129
|
System documentation for NEVS shall be provided to the Maintenance Organization.
|
Phase 1
|
2.2.130
|
Software documentation for the NEVS shall be provided to the Maintenance Organization for each NEVS software release.
|
Phase 1
|
2.2.131
|
NEVS shall provide web-based documentation via the help desk functionality for frequently asked questions.
|
Phase 1
|
|
Software Quality Attributes
|
|
2.2.132
|
NEVS developers shall test and document the software and system tests conducted throughout the project lifecycle for:
-
Unit testing
-
Integration testing
-
System testing
|
Phase 1
|
2.2.133
|
NEVS developers shall provide documentation to support the NEVS User Acceptance testing.
|
Phase 1
|
2.2.134
|
A change management process shall be established for NEVS requirement changes.
|
Phase 1
|
2.2.135
|
NEVS software shall be under configuration management throughout the development and testing phases.
|
Phase 1
|
2.2.136
|
NEVS developers shall follow the following Institute of Electrical and Electronics Engineers (IEEE) standards for software development, configuration, quality management and testing:
-
1220 Application and Management of the Systems Engineering Process
-
12207 Systems and Software Engineering – Software Life Cycle Process
-
828 Standard for Software Configuration Management Plans
-
730 Standard for Software Quality Assurance Plans
|
Phase 1
|
2.2.137
|
NEVS shall perform quality control of all data processed for verification of Aviation Services Products and selected data in the Cube.
|
Phase 1
|
2.2.138
|
Procedures for identification, evaluation, and reporting of erroneous data occurrences shall be implemented for data quality control in NEVS.
|
Phase 1
|
2.2.139
|
NEVS will provide logging of data processing to enable traceability of erroneous data.
|
Phase 1
|
2.2.140
|
Critical software defects identified during integration testing shall be resolved prior to the start of the NEVS Factory Acceptance Test.
|
Phase 1
|
2.2.141
|
NEVS shall maintain data integrity for the observations and forecast data processed.
|
Phase 1
|
2.2.142
|
NEVS shall provide data integrity checks and flag data that are outside the range of expected values.
|
Phase 1
|
2.2.143
|
NEVS shall provide data format checks and flag data that are improperly formatted.
|
Phase 1
|
2.2.144
|
NEVS shall maintain a record of all flagged data, products and observations.
|
Phase 1
|
2.2.145
|
NEVS shall not use observations, data or forecasts that have been flagged as suspect in the automated verification process.
|
Phase 1
|
2.2.146
|
NEVS shall maintain a list of known suspect data sources for which the observational data should not be used in the verification process.
|
Phase 1
|
2.2.147
|
NEVS shall provide an interactive graphical user interface option for user selection for either the inclusion or the exclusion of flagged observations, products and data to be used in the computation of the verification results.
|
Phase 2
|
|
Data Storage
|
|
2.2.148
|
NEVS shall provide a historical archive of verification results.
|
Phase 1
|
2.2.149
|
NEVS shall store results from QMS verification queries.
|
Phase 1
|
2.2.150
|
NEVS shall maintain a permanent record of all flagged observations, products and data.
|
Phase 1
|
2.2.151
|
NEVS shall store security audit records for a minimum of 90 days.
|
Phase 1
|
2.2.152
|
NEVS audit record storage shall be configured to minimize the likelihood of storage capacity being exceeded.
|
Phase 1
|
2.2.153
|
NEVS auditing capability must provide a warning when the allocated audit record storage volume reaches 75% of maximum audit record storage capacity.
|
Phase 1
|
|
Data Distribution
|
|
2.2.154
|
NEVS shall provide verification results to the Cube using web services.
|
Phase 2
|
2.2.155
|
NEVS shall provide verification results to AWIPS II via Data Delivery using web services.
|
Phase 2
|
2.2.156
|
NEVS shall provide selected verification data to the SOD verification system.
|
Phase 2
|
2.2.157
|
NEVS shall provide audit records on hardware-enforced, write once media.
|
Phase 1
|
2.2.158
|
NEVS shall generate audit records for retention of perimeter device electronic files for up to one year.
|
Phase 1
|
|
System Interfaces
|
|
2.2.159
|
NEVS shall interface to the Stats on Demand verification to provide selected verification data.
|
Phase 2
|
2.2.160
|
NEVS shall interface to the Stats on Demand verification system to access performance statistics for the Terminal Aerodrome Forecast (TAF) product.
|
Phase 2
|
2.2.161
|
NEVS shall interface to the National Digital Forecast Database (NDFD) to access performance statistics of gridded NDFD forecast data.
|
Phase 1
|
2.2.162
|
NEVS shall interface to the NextGen Cube systems.
|
Phase 1
|
2.2.163
|
NEVS shall consume data and products from the Cube.
|
Phase 1
|
2.2.164
|
NEVS shall publish verification results via web services:
-
Web mapping
-
Web coverage
-
Web feature
using extensions of Open Geospatial Consortium (OGC) standards.
|
Phase 2
|
2.2.165
|
NEVS shall provide verification data to AWIPS II sites via Data Delivery capabilities.
|
Phase 2
|
2.2.166
|
NEVS verification results shall be provided to AWIPS II via a non-SBN data ingest through the AWIPS WAN.
|
Phase 2
|
2.2.167
|
NEVS verification results shall be pulled to AWIPS II via the 4-D Weather Data Cube web services:
-
Web mapping
-
Web coverage
-
Web feature
using extensions of Open Geospatial Consortium (OGC) standards.
|
Phase 2
|
2.2.168
|
NEVS verification results shall be displayable in the AWIPS II Common AWIPS Visualization Environment (CAVE).
|
Phase 2
|
2.2.169
|
NEVS verification results shall be delivered to AWIPS II using the following delivery paradigms:
-
Subscription delivery
-
Ad-Hoc
-
Occasional
|
Phase 2
|
|
User Interfaces
|
|
2.2.170
|
NEVS shall provide a graphical user interface for user log in.
|
Phase 1
|
2.2.171
|
NEVS shall use the NOAA directory services and Lightweight Directory Access Protocol (LDAP) directory for account names and passwords for NOAA user access.
|
Phase 1
|
2.2.172
|
NEVS shall provide single sign on capabilities for NOAA users.
|
Phase 1
|
2.2.173
|
NEVS shall provide a graphical user interface for display of verification results.
|
Phase 1
|
2.2.174
|
NEVS shall provide graphical user interfaces for user selection of desired product verification.
|
Phase 1
|
2.2.175
|
NEVS shall provide graphical user interfaces for help desk functions.
|
Phase 1
|
2.2.176
|
NEVS shall provide a central main page with access to:
-
Users Manual
-
FAQ for NEVS
-
Glossary for definition of verification terms
-
NEVS Help Desk
-
Software Defect Reporting
-
NEVS Software Change Tracking
-
NEVS Verification Applications
-
Verification period of record available for each product verified by NEVS
-
Flagged Data and Observations
-
QMS Menu
|
Phase 1
|
2.2.177
|
NEVS shall provide user configurable verification queries which are saved and can be modified for:
-
User selectable periods including monthly, seasonal, quarterly, and annual periods.
-
User selectable parameters.
-
Sharing queries with other users.
-
Saving queries under a specific user identifier.
|
Phase 1
|
2.2.178
|
NEVS user interface shall be flexible and extensible.
|
Phase 1
|
2.2.179
|
The NEVS user interface shall provide a separate menu for QMS verification result report generation.
|
Phase 1
|
2.2.180
|
The NEVS user interface shall provide user access to view the quality controlled flagged products, observations and data.
|
Phase 1
|
2.2.181
|
NEVS shall provide capabilities for generation of user selectable automated reports as:
-
Comma Separated Values (CSV)
-
Graphical images as files in Portable Network Graphics (PNG) format
|
Phase 1
|
2.2.182
|
NEVS shall provide capabilities for generation of user selectable verification reports as:
|
Phase 1
|
2.2.183
|
NEVS shall provide capabilities for generation of reports of flagged verification data, products and observations for user selectable periods of time.
|
Phase 2
|
|
Software Interfaces
|
|
2.2.184
|
NEVS verification results for the NWS Aviation Services Products shall be made available for display in the AWIPS II Common AWIPS Visualization Environment (CAVE).
|
Phase 2
|
2.2.185
|
NEVS verification results shall be delivered to AWIPS II using the following delivery paradigms:
-
Subscription delivery
-
Ad-Hoc
-
Occasional
|
Phase 2
|
2.2.186
|
NEVS shall interface to a NEVS Service Adaptor for access to all required decoded data from the Cube.
|
Phase 1
|
|
Communications Interfaces
|
|
2.2.187
|
NEVS shall interface to the 4-Dimensional Weather Data Cube.
|
Phase 1
|
2.2.188
|
NEVS shall interface to NOAA users via the private Internet, with no public access
|
Phase 1
|
2.2.189
|
NEVS communication interface to other verification systems shall be via OPSNet.
|
Phase 1
|
These NEVS decoding requirements pertain to the feature-based observational data provided in Pilot Reports (PIREPs), and two AWC issued products: the Airmen’s Meteorological Information (AIRMET), and the Significant Meteorological Information (SIGMET).
