Docstoc

Draft - FAACO - Federal Aviation Administration Contract Opportunities

Document Sample
Draft - FAACO - Federal Aviation Administration Contract Opportunities Powered By Docstoc
					             Common Support System-Weather System Specification Document
                                        Draft

 1




 2

 3

 4            Common Support Services – Weather
 5                      (CSS-Wx)
 6
 7            System Specification Document (SSD)
 8                                DRAFT
 9

10

11

12   Approved by:      ____            Date: ____________

13   (TBD)

14

15   Submitted By:     ____            Date: ____________

16   (TBD)

17
18
19
20                             Federal Aviation Administration
21                              800 Independence Avenue SW
22                                 Washington, DC 20591
23

24



                                          i
                            Common Support System-Weather System Specification Document
                                                                         Draft

25   TABLE OF CONTENTS
26   1     SCOPE .................................................................................................................................... 1
27       1.1     Identification .................................................................................................................... 1
28       1.2     System Overview ............................................................................................................. 1
29       1.3     Document Overview ........................................................................................................ 3
30   2     APPLICABLE DOCUMENTS .............................................................................................. 4
31       2.1     Government Documents ................................................................................................... 4
32         2.1.1        FAA Documents ....................................................................................................... 4
33         2.1.2        Other Government Documents ................................................................................. 5
34       2.2     Non-Government Documents .......................................................................................... 6
35         2.2.1        ANSI Standards ........................................................................................................ 6
36         2.2.2        NFPA Standards........................................................................................................ 6
37         2.2.3        ISO Standards Compliance ....................................................................................... 6
38         2.2.4        General Standards ..................................................................................................... 7
39         2.2.5        Technical Standards Framework............................................................................... 7
40       2.3     Order of Precedence ......................................................................................................... 8
41   3     REQUIREMENTS .................................................................................................................. 9
42       3.1     System Definition ............................................................................................................. 9
43         3.1.1        High-Level System Description ................................................................................ 9
44         3.1.2        System Architecture ................................................................................................ 12
45         3.1.3        System States and Modes........................................................................................ 14
46       3.2     System Functional Requirements ................................................................................... 15
47         3.2.1        Common Functional Requirements ........................................................................ 15
48         3.2.2        Registry/Repository ................................................................................................ 27
49         3.2.3        Service Adaptors ..................................................................................................... 32
50         3.2.4        Web Coverage Service (WCS) ............................................................................... 35
51         3.2.5        Web Feature Service (WFS) ................................................................................... 42
52         3.2.6        Web Map Service (WMS) ...................................................................................... 49
53         3.2.7        Complex Query Service .......................................................................................... 57
54         3.2.8        Weather Alert Service ............................................................................................. 58
55         3.2.9        Dynamic Load Handling ......................................................................................... 58
56         3.2.10 Query Optimization ................................................................................................ 58


                                                                            ii
                       Common Support System-Weather System Specification Document
                                                                   Draft

57     3.2.11 System Administration and Maintenance Software ................................................ 59
58   3.3    Performance Requirements ............................................................................................ 59
59     3.3.1       Reliability................................................................................................................ 59
60     3.3.2       Maintainability ........................................................................................................ 59
61     3.3.3       Availability ............................................................................................................. 60
62     3.3.4       Extensibility ............................................................................................................ 60
63     3.3.5       Scalability ............................................................................................................... 60
64     3.3.6       Portability................................................................................................................ 61
65     3.3.7       Interchangeability ................................................................................................... 61
66     3.3.8       Latency/Response Time .......................................................................................... 61
67     3.3.9       Quality of Service ................................................................................................... 64
68     3.3.10 Reserve Capacity .................................................................................................... 65
69   3.4    Interface Requirements .................................................................................................. 65
70     3.4.1       Legacy Weather Consumer Interfaces .................................................................... 65
71     3.4.2       OGC-Compliant Consumer Interfaces .................................................................... 66
72     3.4.3       Legacy Weather Provider Interfaces ....................................................................... 66
73     3.4.4       OGC-Compliant Weather Provider System Interfaces ........................................... 67
74     3.4.5       Radar System Interfaces ......................................................................................... 67
75     3.4.6       FAA SWIM Interface ............................................................................................. 67
76     3.4.7       Remote Monitoring Management System Interface ............................................... 67
77     3.4.8       External NAS User System Interface ..................................................................... 67
78   3.5    Design and Construction ................................................................................................ 68
79     3.5.1       Software Design ...................................................................................................... 68
80     3.5.2       Hardware Design .................................................................................................... 68
81     3.5.3       Installation............................................................................................................... 68
82     3.5.4       Power Requirements ............................................................................................... 68
83     3.5.5       Hardware Requirements.......................................................................................... 69
84     3.5.6       Hardware Interfaces ................................................................................................ 69
85     3.5.7       Equipment Cabinetry .............................................................................................. 69
86     3.5.8       Physical Requirements ............................................................................................ 70
87     3.5.9       Standards of Manufacture ....................................................................................... 71
88     3.5.10 Environmental Safety and Health ........................................................................... 71
89     3.5.11 Human Factors Engineering ................................................................................... 73
                                                                      iii
                           Common Support System-Weather System Specification Document
                                                                         Draft

 90   4     QUALIFICATION REQUIREMENTS................................................................................ 76
 91       4.1    Test Planning/Procedures ............................................................................................... 76
 92       4.2    Verification Methods...................................................................................................... 76
 93       4.3    Verification Requirements Traceability Matrix (VRTM) .............................................. 76
 94
 95
 96
 97   APPENDIX A                            ACRONYMS .................................................................................................... A-1
 98   APPENDIX B                            GLOSSARY ....................................................................................................... B-1
 99   APPENDIX C                            VERIFICATION REQUIREMENTS TRACEABILITY MATRIX .................. C-1

100
101
102
103                                                      TABLE OF FIGURES
104   Figure 1 High-Level Context Diagram ....................................................................................... 2
105   Figure 2 CSS-Wx System Functions ......................................................................................... 10
106   Figure 3: Detailed Notional Architecture of the CSS-Wx System .......................................... 13
107
108                                                       TABLE OF TABLES
109   Table 1 CSS-Wx System States and Modes Matrix ................................................................. 14
110

111

112




                                                                           iv
                    Common Support System-Weather System Specification Document
                                               Draft

113   Revision Record
        Version #              Date              Edits
        SSD-CSS-WX.SSD.001     06/30/2012        RFI_2 Draft SSD




                                                v
114   1   SCOPE
115       1.1 Identification
116   This specification establishes the functional, performance, and verification requirements for the
117   Common Support Services-Weather (CSS-Wx) System. The CSS-Wx Program is sponsored by
118   the Federal Aviation Administration (FAA) and is one element the NextGen weather capability
119   as described in the Joint Program Office Next Generation Air Transportation System Concept of
120   Operations [JPDO, NextGen Concept of Operations]. The CSS-Wx System is a component of
121   the FAA Common Support Services Weather (CSS-Wx) initiative previously called NextGen
122   Net-Enabled Weather (NNEW). References to the NNEW System and the CSS-WX System are
123   interchangeable.
124

125       1.2   System Overview
126   The operation of today's National Airspace System (NAS) is supported by a variety of weather
127   sensing and processing systems maintained by Federal Government agencies and private entities.
128   These disparate sources of aviation weather data sometimes conflict with one another, creating
129   challenges for efficient operational planning and decision making. Consistent NAS-wide weather
130   information is rarely available in any one location. As a result, NAS-wide operational
131   coordination requires excessive, ad hoc discussion and collaboration among stakeholders, which
132   is time consuming and inefficient.
133
134   Presently, the weather product producers send their products to consuming systems via tightly
135   coupled interfaces. The telecommunications infrastructure that supports aviation weather
136   information users consists of a complex network of point-to-point communication paths, local
137   area networks, and wide-area networks that rely on a diverse collection of legacy hardware,
138   software, and protocols. Additionally, weather product consumers may not need a weather
139   product exactly as produced by a weather information provider. For example, instead of
140   receiving all the forecast model output for a specific forecast time a user may only require the 6-
141   hour forecast for the 18,000 foot winds at the New York Air Route Traffic Control Center
142   (ARTCC). The delivery of weather products is insufficient for NextGen operations. A major
143   shift must be made in the way weather information is provided.
144
145   The realization of NextGen will require changes to the FAA’s weather architecture. The
146   integration of weather information into air traffic management decision-support tools will entail
147   an increased use of gridded weather data with high spatial and temporal resolutions and the
148   addition of new users to the network, which will impose significant demands on the capacity of
149   the FAA Telecommunications Infrastructure (FTI) Operations Internet Protocol network.
150
151   The CSS-Wx System provides a solution to address the inconsistency of weather data and the
152   limitations in network coverage and scalability. It will enable the efficient transmission of high-
153   resolution aviation weather data from the variety of producing systems to weather information



                                                      1
154   users throughout the NAS, and will provide users the required NAS-wide weather information
155   required for operational planning. The CSS-Wx System will also institute standard protocols for
156   communicating weather information with NAS systems and will be scalable to facilitate the
157   addition of new systems, thereby minimizing the need for service adaptors. Where required, the
158   CSS-Wx System service adaptors will provide an interface for each internal legacy system. The
159   service adaptors convert product formats and provide an interface to the SWIM Enterprise
160   Service Bus (ESB) so that legacy systems can provide or consume data to/from the CSS-Wx
161   System without requiring system modifications.
162
163   Figure 1 presents a high-level context diagram of the CSS-Wx System. The CSS-Wx System
164   receives input from FAA weather information providers including the NextGen Weather
165   Processor (NWP) and from external sources of weather products such as the National Oceanic
166   and Atmospheric Administration’s (NOAA) 4-Dimensional Weather Data Cube and customizes
167   the weather products as required to meet the needs of consumer systems. The functionality
168   provided by the CSS-Wx System includes geospatial and temporal filtering, map coordinate
169   system re-projections, measurement unit conversions, and resolution reduction. The CSS-Wx
170   System will communicate with external systems through the NAS Enterprise Security Gateway
171   (NESG) and with internal FAA NAS systems via the System Wide Information System (SWIM)
172   enterprise service bus (ESB) and FAA operational IP network.
173
                                                            NEXRAD,      ASOS,
                                                             TDWR.       AWOS,
                                                              ASR        AWSS
                                                                                    Canadian           NOAA Data
                                                                                      Radar
                                                                                                        Sources
                                                                          ADAS/
                                             ERAM, ATOP,                   RASP,
                                                                                                      (4D Wx Data
                                            DOTS+. FDP2K,                 WMSCR                          Cube)
                                            MEARTS, NIDS

                                                                                   External
                                                                                   Gateway
                                                             CSS-Wx
                                            NWP              (NNEW)                External
                   Displays                                                        Gateway
                                                                                                       External Users



            SWIM

                              TFDM, TFMS,
                                TBFM…                   FTI
                                                     NAS Ops IP                                      Legend

                                                      Network                                            CSS-Wx
                                                                                               FTI


174
175                                         Figure 1 High-Level Context Diagram
176
177   As shown in Figure 1, weather provider and consumer systems are outside of the CSS-Wx
178   System boundary. Weather Consumers are systems that use weather data to perform functions
179   required in support of end users including, but not limited to, Air Traffic Controllers, pilots,


                                                              2
180   Traffic Flow Managers, and meteorologists. In addition to weather providers and consumers,
181   system developers and Airway Transportation Systems Specialists will access the CSS-Wx
182   System to update metadata, perform maintenance and administer the system. CSS-Wx System
183   status information can be sent to any authorized user or reporting system on the network.
184
185   An important aspect of the CSS-Wx System and the NOAA 4-D Wx Data Cube is that they will
186   be developed in accordance with the Weather Data Model (WXCM, WXXM, and WXXS). This
187   model was developed by EUROCONTROL in partnership with the FAA CSS-Wx Program
188   Office and is developed in accordance with Open Geospatial Consortium (OGC)1 standards:
189   Web Feature Service (WFS), Web Coverage Service (WCS), and Web Map Service (WMS). The
190   use of international standards for exchanging weather products provides assurance of future
191   interoperability between weather information producers and consumers.
192   1.3      Document Overview
193   Section 1 provides an executive level summary of the CSS-WX program mission; Section 2
194   identifies the applicable documents referenced in the system specification; Section 3 describes
195   the system requirements pertaining to the functionality, performance, system management, data
196   management, interfaces, and physical characteristics; Section 0 addresses quality assurance and
197   verification requirements traceability. The appendices contain acronyms and definitions, and the
198   Verification Requirements Traceability Matrix (VRTM).
199
200




      1
          For information on OGC go to http://www.opengeospatial.org/



                                                              3
201   2     APPLICABLE DOCUMENTS
202   2.1   Government Documents

203       2.1.1 FAA Documents

204         2.1.1.1 Support/Historical Documentation
205                     a) National Airspace System (NAS) Requirements Document, dated
206                        September 30, 2011.
207                     b) JPDO, NextGen Concept of Operations, Version 3.0, October 1, 2009.
208                     c) NextGen Network-Enabled Weather Metadata Profile for the 4-D Weather
209                        Data Cube document. Project Report, ATC-354, Revision 2, April 10,
210                        2010
211                     d) NextGen Weather Concept of Operations, Version 1.0, May 13, 2006

212         2.1.1.2 Physical Integration
213                     a) DOT Specification FAA-G-2100H, Electronic Equipment, General
214                        Requirements, Personnel Safety and Health
215                     b) FAA-G-2100H, Electronic Equipment, General Requirements
216                     c) FAA-G-2100H, Chapter 3.3.5.5, Markings, Signs, Tags and Symbols, for
217                        marking electrical equipment

218         2.1.1.3 Human Integration
219                     a) FAA HF-STD-001, Human Factors Design Standard, May 2003

220         2.1.1.4 Security
221                     a)   FAA Order 1280.1B - Protecting Personally Identifiable Information (PII)
222                     b)   FAA Order 1370.79A Internet Use Policy
223                     c)   FAA Order 1370.82A Information System Security Program
224                     d)   FAA Order 1370.89 FAA Information Operations Condition
225                     e)   FAA Order 1370.92A Password/PIN Management
226                     f)   FAA Order 1370.93 FAA Web Management
227                     g)   FAA Order 1370.94A Wireless Technology Security Policy
228                     h)   FAA Order JO 1370.97 ATO Use of Non-FAA Workstations
229                     i)   FAA Order JO 1370.96 ATO System Access Control
230                     j)   FAA Order JO 1370.98 ATO IT Infrastructure Requirements for Non-
231                          FAA Connectivity
232                     k)   FAA Order JO 1370.99 ATO NAS Information System Security Patch
233                          Management Policy
234                     l)   FAA Order 1370.100 Media Sanitizing and Destruction Policy
235                     m)   FAA Order 1370.101 ATO Information Security Incident Reporting and
236                          Response Policy
237                     n)   FAA Order 1370.102 System Use Notification and Disclaimer
238                     o)   FAA Order 1370.103 Encryption Policy
239                     p)   FAA Order 1370.104 Digital Signature Policy
240                     q)   FAA Order 1370.105, Logical Access Control Policy


                                                     4
241                r) FAA Order 1370.106 Information System Security Awareness and
242                    Training Policy
243                s) FAA Order 1370.107 Rules of Behavior/System Use Policy
244                t) FAA Order 1370.109 Software Assurance Policy
245                u) FAA Order 1370.111 Removable Media Security Policy
246                v) FAA Order JO 1370.114 Implementation of Federal Aviation
247                    Administration (FAA) Telecommunications Infrastructure (FTI) Security
248                    Requirements in the NAS
249                w) FAA Order 1370.113 FAA Web Security Policy
250                x) FAA Order 1370.115 Domain Name System (DNS) Security Policy
251                y) FAA Order 1370.116 Boundary Protection Policy
252                z) FAA Order 1600.1E Human Resources and ASH Policy
253                aa) FAA Order 1600.6E Facility Security Policy
254                bb) FAA Order 1600.72 Contractor and Industrial Security Program
255                cc) FAA Order 1600.73 Contractor and Industrial Security Program Operating
256                    Procedures
257                dd) FAA Order 1600.75 Protecting Sensitive Unclassified Information (SUI)
258                ee) FAA Order JO 1900.47C Air Traffic Organization Operational
259                    Contingency Plan
260                ff) Air Traffic Organization (ATO) Information Systems Security (ISS)
261                    Authorization Handbook
262

263   2.1.2 Other Government Documents
264                a) 29 CFR 1910.145, Specifications for Accident Prevention Signs and Tags
265                b) DOT Order 1351.11
266                c) Executive Order 13423, Strengthening Federal Environmental, Energy,
267                   and Transportation Management.
268                d) Executive Order 13514, Federal Leadership in Environmental, Energy,
269                   and Economic Performance.
270                e) Clean Air Act
271                f) Toxic Substance Control Act
272                g) FAA-HDBK-006A federal aviation administration handbook: reliability,
273                   maintainability, and availability handbook (07 Jan 2008)
274

275     2.1.2.1 NIST Publications
276                a) SP 800-37 Guide for Applying the Risk Management Framework to
277                   Federal Information Systems: A Security Lifecycle Approach
278                b) SP 800-53 Recommended Security Controls for Federal Information
279                   Systems and Organizations
280                c) SP 800-53A Guide for Assessing the Security Controls in Federal
281                   Information Systems and Organizations: Building Effective Security
282                   Assessment Plans
283                d) FIPS 140 Security Requirements for Cryptographic Modules


                                              5
284                  e) FIPS 199 Standards for Security Categorization of Federal Information
285                     and Information Systems
286                  f) FIPS 200 Minimum Security Requirements for Federal Information and
287                     Information Systems
288
289   2.2   Non-Government Documents

290     2.2.1 ANSI Standards
291                  a) American National Standards Institute (ANSI) Z535.4, Product Safety
292                     Signs and Labels
293                  b) American National Standards Institute (ANSI)/Institute of Electrical and
294                     Electronics Engineers (IEEE) 1100-1992, Powering and Grounding
295                     Sensitive Electronic Equipment
296                  c) American National Standards Institute (ANSI)/Institute of Electrical and
297                     Electronics Engineers (IEEE) 1100-2005, Recommended Practice for
298                     Powering and Grounding Sensitive Electronic Equipment.

299     2.2.2 NFPA Standards
300                  a) NFPA Standard 70, National Electric Code®; and local codes
301                  b) NFPA 5000, Building Construction and Safety Code® clearance
302                     standards.

303     2.2.3 ISO Standards Compliance
304                  a)   ISO 19101.2002 Geographic Information - Reference Model
305                  b)   ISO 19103.2005 Geographic Information - Conceptual Schema Language
306                  c)   ISO 19107.2003 Geographic Information - Spatial Schema
307                  d)   ISO 19108.2002 Geographic Information - Temporal Schema
308                  e)   ISO 19108.2006 Geographic Information Temporal Schema -
309                       Corrigendum 1
310                  f)   ISO 19109.2005 Geographic Information - Rules for Application Schema
311                  g)   ISO 19110.2005 Geographic Information - Methodology for Feature
312                       Cataloging
313                  h)   ISO 19111.2007 Geographic Information - Spatial Referencing by
314                       Coordinates
315                  i)   ISO 19115.2003 Geographic Information - Metadata
316                  j)   ISO 19115.2006 Geographic Information - Metadata - Corrigendum 1
317                  k)   ISO 19118.2005 Geographic Information - Encoding
318                  l)   ISO 19119.2005 Geographic Information - Services
319                  m)   ISO 19121.2000 Geographic Information - Imagery and gridded data
320                  n)   ISO 19123.2005 Geographic Information - Schema for coverage geometry
321                       and functions
322                  o)   ISO 19127.2005 Geographic Information - Geodetic codes and Parameters
323                  p)   ISO 19136 Geography Markup Language (GML)
324                  q)   ISO 19139.2007 Geographic Information - Metadata - XML Schema
325                       Implementation


                                                 6
326                r) ISO 8601.2004 Data Elements and Interchange Format – Representation
327                   of Dates and Times
328                s) ISO/IEC JTC1 SC32 N1105: Information technology — Metadata
329                   Interoperability and Bindings (MDIB) Part 002: Common vocabulary:
330                   2004-04-12
331                t) ISO/IEC 11179, Information Technology – Metadata Registries (MDR),
332                   Parts 1 – 6
333                u) ISO/IEC 12207:1995 Information technology -- Software life cycle
334                   processes

335   2.2.4 General Standards
336                a) Web Service Description Requirements, W3C Working Draft, J.
337                   Schlimmer, 28
338                b) Web Service Semantics - WSDL-S W3C Member Submission 7
339                   November 2005
340                c) XML Information Set (Second Edition) W3C Recommendation 4
341                   February 2004
342                d) OGC WFS Schemas 2.0.0
343                e) OASIS Reference Model for Service Oriented Architecture 1.0, 12
344                   October 2006
345                f) OASIS Web Services Notification (WSN) Base Notification 1.3
346                g) IETF RFC 3986 Uniform Resource Identifier (URI): Generic Syntax,
347                   Network Working Group, January 2005

348   2.2.5 Technical Standards Framework
349                a)   WCS Implementation Standard, version 1.1.2
350                b)   OpenGIS Web Feature Service 2.0 Interface Standard
351                c)   OpenGIS Filtering Encoding 2.0 Encoding Standard
352                d)   OpenGIS Web Map Service Implementation Specification, version 1.3.0
353                e)   OGC Catalog Service (CS/W) Version 2.0.2
354                f)   OGC Sensor Model Language (SensorML) Version 1.0
355                g)   OpenGIS Web Services (OWS) Common Version 1.1.0
356                h)   Java Management Extensions (JMX), Version 1.2
357                i)   Simple Network Management Protocol, Version 3.0
358                j)   Security Assertion Markup Language (SAML), Version 2.0
359                k)   eXtensible Access Control Markup Language (XACML), Version 2.0
360                l)   Web Services-Security, (WS-Security), Version 1.1
361                m)   XML Signature, Version 1.1
362                n)   Web Services-Reliable Messaging Policy Assertion (WS-RM Policy),
363                     Version 1.2
364                o)   Web Services-Reliable Messaging (WS-Reliable Messaging), Version 1.2
365                p)   ebXML Registry Information Model (ebRIM) Version 4
366                q)   ebXML Registry Services (RS) and Protocols Version 4
367                r)   Web Services Description Language (WSDL) Version 2.0 Part 2: Message
368                     Exchange Patterns W3C Working Draft 26 March 2004
369                s)   Web Ontology Language (OWL), Version 2


                                               7
370                     t)  Resource Description Framework (RDF)
371                     u)  Joint Photographic Experts Group (JPEG)
372                     v)  Graphics Interchange Format (GIF)
373                     w)  Portable Network Graphics (PNG)
374                     x)  Network Common Data Form (NetCDF), Version 4.0
375                     y)  Weather Information Exchange Model/Schema (WXXM/WXXS), Version
376                         1.1
377                     z) Geographic Markup Language (GML), Version 3.2.1
378                     aa) ISO 8601.2004 Data elements and interchange formats - Representation of
379                         dates and times
380                     bb) Extensible Markup Language (XML) 1.0 (Fourth Edition), W3C
381                         Recommendation 16 August, 2006, edited in place 29 September, 2006
382                     cc) World Wide Web Consortium (W3C) XML Schema
383                     dd) XML Path Language (XPath), Version 2.0
384                     ee) XML Query Language (XQuery), Version 1.0
385                     ff) XSL Transformations (XSLT), Version 2.0
386                     gg) Efficient XML Interchange (EXI), Format 1.0
387                     hh) W3C Simple Object Access Protocol (SOAP)
388                     ii) Web Services Notification (WS-Notification)
389                     jj) SOAP Messages with Attachments
390                     kk) Web Services Addressing (WS-Addressing), Version 1.0
391                     ll) Hypertext Transfer Protocol – HTTP/S 1.1
392                     mm)         Java Messaging Service (JMS), Version 1.1
393                     nn) File Transfer Protocol (FTP), RFC 959, October 1985
394                     oo) Transport Layer Security (TLS)
395   2.3   Order of Precedence
396   In the event of a conflict between the text of this document and the references cited herein, the
397   text of this document takes precedence. Nothing in this document, however, supersedes
398   applicable laws and regulations unless a specific exemption has been obtained.
399




                                                     8
400   3     REQUIREMENTS
401   Sub-section 3.1 provides descriptive information about the CSS-Wx System. Sub-sections 3.2
402   and beyond define the requirements for the CSS-Wx System. When used in this document, the
403   word “shall” refers to an explicit requirement of a CSS-Wx System component or the complete
404   CSS-Wx System.
405   3.1     System Definition
406   The CSS-Wx System is comprised of weather data, metadata, data processing hardware,
407   software, and a mechanism for maintenance technicians and administrative personnel to support
408   system management and maintenance functions. The CSS-Wx System filters weather data,
409   converts units of measure, transforms weather data formats, and other value-added functionality
410   that supports specific user requests.

411       3.1.1 High-Level System Description
412   The CSS-Wx System provides NAS stakeholders with access to aviation weather information
413   through an OGC-compliant interface. Legacy weather data producers and consumer systems
414   interface the CSS-Wx System via Service Adaptors that perform the necessary transformations to
415   enable transparent access to weather data.
416   The CSS-Wx System provides the following capabilities:
417         1. Discovery of available weather products, their characteristics, and their associated terms
418             of use. This capability will be provided by a registry/repository that contains metadata
419             about the weather services and datasets and supports discovery of weather datasets
420             designated as Single Authoritative Source (SAS). The SAS provides a “common weather
421             picture” that facilitates shared situational awareness and eliminates the need to choose
422             among potentially conflicting weather products.
423         2. Messaging services allow consumers to subscribe to or query weather data products from
424             weather data providers through various message exchange patterns.
425         3. Data sub-setting, filtering, compression, storage, and queuing techniques. These
426             capabilities minimize the bandwidth used to publish weather information and provide
427             consumers with only the data that is needed.
428         4. Publication of raw radar data products to the SWIM Enterprise Service Bus (ESB).
429         5. Receive and translate requests, retrieve weather data and reformat the data into legacy
430             formats for legacy consumers.
431         6. The capability to proxy weather data to consumers to enable a more rapid response to ad
432             hoc queries.
433         7. Conversion of units of measurements to meet consumer needs.
434         8. Re-projection of weather data from one map projection to another.
435         9. The capability to reduce geographic resolutions to meet consumer requirements also
436             reduces bandwidth requirements.
437         10. Complex Retrieval functionality that aggregates multiple responses to a multi-part query
438             into a single response in a common format.
439         11. Replay of a stored query to replicate the CSS-Wx System response in support of accident
440             and incident reporting.


                                                        9
441        12. Data recording and playback capability to support verification and validation testing.
442          Figure 2 depicts a conceptual overview of the CSS-Wx System functionality in the
443   context of weather producers and consumers with product dissemination via the SWIM ESB.

          Inputs                                                                                                                                                             Outputs
                                                                                     CSS Wx System
                                   IP Interface




      Legacy Wx                                   Consumer
                                                                                                                                                                                     Tailored Wx




                                                                                                                                                        IP Interface
      Data Consumer       Query                    Service                                                                                   Consumer
                                                                  Formatted Query                                                                                                    Products for
                                                  Adaptors                                                                                    Service                    Legacy
                                                                                                                       Tailored Weather                                              Legacy
                                                                                                                           Products          Adaptors                   Formatted
                                                                                                                                                                       Wx Products   Consumers
                                                                                       WCS
      CSS Wx Admin
      Monitor & Control
      Workstation                                     Query/Command                                   Discovery
                                                                                                  Filter/Extraction
                                                                                                   Re-projection
                                                                                       WFS      Resolution Reduction      Tailored Weather
                                                                                                  Unit Conversion             Products
                                                                                                   Data Archiving
                                                                                                 Monitor & Control
                                  IP Interface




                                                  Producer
       Legacy                                      Service
       Producers      Wx Data                                    Formatted Wx Data     WMS
                                                  Adaptors

                                                                                                                         CSS WX
                                                                                                                       Service Status
              NWP                                    Formated Wx Data
                                  IP Interface




                                                    Radar
         Radar
                                                    Ingest
         Producers        Radar                                    Net-enabled
                          Data
                                                   Adaptors        Radar Data
                                                                                          Run-Time Reg/Rep

                                                                                                                                                                            Internal FAA
                                                                                         Design-Time Reg/Rep                                                                Native Consumers
       Other Internal                                                                                                                                   Tailored
       FAA Producers        Wx Data                                                                                                                     Wx Data
                                                                                     SWIM Enterprise Services                                                               CSS Wx Service
                                                                                                                                                                            Status Consumer
                                                                                                                                                            Status

       NOAA 4-D Wx                                                                    FTI Boundary Protection
       Data & External       Wx Data                                                                                                                                       NOAA 4-D Wx
       Producers (native)                                                                                                                                                  Data & External
                                                                                                                                                        Tailored
                                                                                                                                                         Data              Consumers (native)
                                                                                         FAA Networks
444
445                                                                         Figure 2 CSS-Wx System Functions
446
447   Samples of data exchanges between native and legacy weather data producers and consumers of
448   the CSS-WX System are summarized below:
449
450   1) Native Wx Producers:
451      a) NOAA 4 -Wx Cube
452         i) The CSS-Wx System receives NOAA/NWS model data through the FTI Boundary
453              Protection and SWIM (via the NAS Enterprise Security Gateway [NESG]).
454         ii) The CSS-Wx System tailors the data (if needed) for each instance of a legacy
455              Automation system and for each instance of ITWS and for the NWP.
456         iii) The CSS-Wx System publishes the tailored subsets of model data to their
457              corresponding Topics on the ESB.
458         iv) Each Automation system CSS-Wx CSA subscribes to the appropriate Topics.



                                                                                                10
459         v) Each CSS-Wx CSA then converts the model data file format from the OGC format
460              (NetCDF4) to the automation systems legacy format (e.g., GRIB1).
461         vi) Each CSS-Wx CSA then transmits the tailored model data to the legacy consumer
462              system via IP.
463         vii) Each native consumer that requires the NOAA Products subscribes to the appropriate
464              topics
465
466      b) NWP
467         i) NWP subscribes from SWIM ESB to NOAA weather products, NEXRAD and
468              TDWR weather products.
469         ii) NWP generates composite reflectivity mosaics and forecasts and other weather
470              products and stores these products in a data storage system to which CSS-Wx has
471              access.
472         iii) CSS-Wx retrieves NWP weather products from the common storage it shares with
473              NWP.
474         iv) CSS-Wx tailors these products for use by consumer systems (ATOP, DOTS,
475              ERAM/DSR, MEARTS, TFMS, etc.). CSS-Wx creates a tailored subset of NWP
476              products for each instance of a consumer system.
477         v) CSS-Wx publishes the various subsets to their corresponding Topics on the SWIM
478              ESB.
479         vi) “Native” consumer systems subscribe to the appropriate Topics on the SWIM ESB to
480              receive the NWP products intended for them.
481         vii) For legacy consumer systems, their associated CSS-Wx CSA subscribes to the
482              appropriate Topics on the SWIM ESB. The CSS-Wx CSA then converts the OGC file
483              format to the legacy file format and transmits these files to the legacy consumer
484              system via IP.
485
486      c) Terminal Weather Producers
487         i) Each ITWS/ subscribes to NOAA/NWS products (model data, MDCRS, etc.), and to
488              the appropriate NEXRAD products.
489         ii) ITWS/ receives TDWR data directly without going through CSS-Wx.
490         iii) ITWS generates terminal weather products.
491         iv) CSS-Wx receives the Terminal weather products.
492         v) CSS-Wx creates subsets of these products corresponding to consumer system needs
493              and publishes them to the corresponding Topics on the SWIM ESB.
494         vi) “Native” consumer systems subscribe to the appropriate Topics on the SWIM ESB to
495              receive the terminal weather products intended for them.
496         vii) For legacy consumer systems, their associated CSS-Wx CSA subscribes to Topics on
497              the SWIM ESB. The CSS-Wx CSA then converts the OGC file format to the legacy
498              file format and transmits these files to the legacy consumer system via IP.
499         viii) For time critical weather products in addition to CSS-Wx distribution, direct
500              connections to display systems may be provided.
501
502   2) Legacy Wx Producer:


                                                   11
503      a) ADAS/RASP
504         i) CSS-Wx receives One Minute Observations (OMO) from ADAS/RASP via IP.
505         ii) The CSS-Wx PSA converts the OMO to OGC format.
506         iii) CSS-Wx publishes the OMO to appropriate Topics on the SWIM ESB.
507         iv) Various systems subscribe from SWIM ESB to the OMO that pertain to their area of
508              interest.
509      b) WMSCR
510         i) CSS-Wx receives Pilot Reports and certain other alphanumeric products from
511              WMSCR via IP.
512         ii) CSS-Wx converts the pilot reports to OGC format
513         iii) CSS-Wx publishes the pilot reports to appropriate topics on the SWIM ESB
514         iv) Native consumers subscribe from the SWIM ESB to the pilot report that pertains to
515              their area of interest
516      c) WSR-88D
517         i) CSS-Wx receives WSR-88D (NEXRAD) level III products via IP
518         ii) The CSS-Wx System published the NEXRAD products to the appropriate topics on
519              the SWIM ESB
520         iii) NWP subscribes from the SWIM ESB for the NEXRADs
521

522     3.1.2 System Architecture
523   The CSS-Wx System architectural approach places emphasis on the CSS-Wx System as a
524   modular, flexible, Content Delivery Network (CDN). The CSS-Wx CDN builds upon shared
525   SWIM/FTI content delivery mechanisms, adding capabilities specific to the weather domain,
526   while aligning with that infrastructure’s ability to change over time in response to future
527   NextGen requirements.
528
529   A more detailed, notional, high-level view of the CSS-Wx System is presented in Figure 3. It is a
530   NAS-wide view of the CSS-Wx System, which includes external NAS stakeholders and a
531   connection to NOAA’s 4-D Wx Data Cube. The CSS-Wx System may be deployed at the
532   Network Enterprise Management Centers (NEMCs) in Salt Lake City and Atlanta, at the Air
533   Traffic Control Systems Command Center (ATCSCC), at various Air Route Traffic Control
534   Centers (ARTCCs), at various Terminal Radar Approach Control Centers (TRACONs), and at
535   various Air Traffic Control Towers (ATCTs).
536




                                                     12
537
538                    Figure 3: Detailed Notional Architecture of the CSS-Wx System
539
540   From the data input perspective, CSS-Wx System Nodes at the two NEMC locations serve as
541   central aggregation points, ingesting data from a variety of NWS System nodes and FAA
542   weather data provider systems. CSS-Wx System nodes at ARTCCs and TRACONs serve as
543   regional aggregation points, ingesting data from radar sensors (NEXRADs and TDWRs) and
544   forwarding the data to NWP via the ESB.
545   In addition to the basic messaging functions provided by SWIM, the CSS-Wx System provides
546   filtering and caching functions, as well as a variety of higher-level functions, to minimize
547   aggregate network bandwidth demands and maximize weather data dissemination-related
548   software reuse. These functions are supported via CSS-Wx System nodes at locations with a
549   heavy user load, including the ATCSCC, the William J Hughes Technical Center (WJHTC),
550   ARTCCs, CERAPs, TRACONs, and some of the larger towers. The messaging nodes will be
551   highly agile, scalable, and configurable, to ensure they meet data access requirements at all these
552   locations.
553   The CSS-Wx System will also deploy a runtime registry/repository for dynamic discovery of
554   service endpoints, enhancing the overall agility and scalability of the system by providing a
555   means to manage consumer-to-provider service binding. ISO 19115 and SensorML 1.0 standards
556   are implemented.
557   The CSS-Wx architecture is envisioned to be based on Service Orientated Architecture
558   principles, whereby new functions are orchestrated from existing functions. For example, the
559   CSS-Wx weather alerting function could be orchestrated using its filtering and extraction



                                                      13
560   functions. Its complex query function can be orchestrated using its basic capabilities to handle
561   queries.
562
563   The CSS-Wx System architecture section will be supplied at a later date.

564     3.1.3 System States and Modes
565   A CSS-Wx System Node State describes the condition from which a CSS-Wx System Node
566   operates. A Mode of Operation is the method or manner in which the CSS-Wx System Node
567   performs work. The correlation between CSS-Wx System Node States and CSS-Wx System
568   Modes of Operation is depicted in Table 1.
569
            State/Mode         Operating Mode     Standby Mode        Maintenance          Failed
                                                                        Mode               Mode

      Operational State              X                    X


      Degraded State                 X                                     X


      Catastrophic State                                                                     X

570
571                          Table 1 CSS-Wx System States and Modes Matrix

572        3.1.3.1 Node State
573   The state of a CSS-Wx System Node is determined by observable, measurable system
574   parameters, as described in the conditions below.

575   3.1.3.1.1 Operational State
576   The CSS-Wx System Node is operating as designed, supporting full functionality, components
577   are configured, online, active, and meet or exceed the operational availability requirements in
578   paragraph 3.3.3.

579   3.1.3.1.2 Degraded State
580   The CSS-Wx System Node is no longer operating as designed, has limited functionality,
581   components are no longer configurable, components are offline, inactive, or otherwise fail to
582   meet the operational availability requirement in paragraph 3.3.3.

583   3.1.3.1.3 Catastrophic State
584   The CSS-Wx System Node has failed and is unrecoverable. (CSS-Wx Service is down for all
585   interfacing consumers and Producers.)

586        3.1.3.2 Modes of Operation



                                                     14
587   3.1.3.2.1 Operating Mode
588   The CSS-Wx System Node executes routine administrative commands and functions in an
589   Operating Mode.

590   3.1.3.2.2 Maintenance Mode
591   The CSS-Wx System maintenance technician will execute a set of commands to perform offline
592   maintenance. Corrective or preventive maintenance activities are required to maintain, repair, or
593   replace one or more CSS-Wx System Node components. Upon completion of maintenance, the
594   execution of performance self-checks and responses to test commands will be executed. The
595   Maintenance Mode is considered a subset of Degraded State.
596

597   3.1.3.2.3 Ready Mode
598   A CSS-Wx System Backup Node is in Ready Mode if a backup node is available, configured as
599   required, and ready for activation (hot stand-by). The Ready Mode is a subset of Operational
600   State when the CSS-Wx System Node operates in a hot stand-by condition.

601   3.1.3.2.4 Failed Mode
602   A CSS-Wx System server no longer performs work as designed. In a Failed Mode, which the
603   CSS-Wx System Node interfaces are inoperable, data is not flowing and weather data is not
604   being processed. A component in Failed Mode can be associated with both Degraded State and
605   Catastrophic State.
606
607   3.2   System Functional Requirements
608   This System Specification Document associates functional requirements with functional
609   components of the CSS-Wx System. These components are not allocated to a physical system
610   architecture. The contractor will design the system to meet the required performance
611   specifications. The common functional components include system management software,
612   messaging software, and security software that are common to all CSS-Wx System nodes, the
613   CSS-Wx Registry Repository facilitates dataset and service discovery. Service Adaptors support
614   legacy system interface requirements and data ingest. The geospatial web services components
615   of the CSS-Wx System are the Web Coverage Service software, Web Feature Service software,
616   and Web Map Service software and any associated extensions to the OGC standards. Additional
617   components facilitate required functionality including software to handle complex queries,
618   weather alerts, dynamic load management and query optimization.
619

620     3.2.1 Common Functional Requirements
621   Common functions apply to any software implemented on the CSS-Wx System. Common
622   functional requirements implement system management processes for monitor and control, logs,
623   reports, fault tolerance; messaging; and security functions. Unique requirements are included
624   under each component.
625


                                                     15
626        3.2.1.1 System Management Software
627   CSS-Wx System Management software resides on all CSS-Wx System Nodes to monitor system
628   performance, log system events, respond to monitoring and control commands, and perform fault
629   detection and recovery. The CSS-Wx System Management software enables and facilitates
630   system administration and maintenance.
631   System Management applications, functions and associated data are accessed controlled and
632   accessible via local and remote administrative and maintenance workstations. The functions are
633   summarized below:
634              1. Performance Monitoring– software used to monitor performance of System
635                 components, compare current values to established thresholds and generate alarms
636                 and alerts.
637              2. Event Logging – software used to record configurable hardware and software
638                 events for CSS-Wx System analysis and reporting.
639              3. Fault Recovery – techniques used to clean up and restart a process or component
640                 after a failure has occurred.
641              4. Performance Reporting – software used to assemble, display, print and
642                 disseminate System performance reports.
643              5. Metrics Reporting – software used to analyze software and hardware events to
644                 report on current measurements and trends.
645              6. Endpoint Control – software used to start, stop, and resume data from an endpoint
646                 interface based upon a predefined condition or user’s request.
647              7. CSS-Wx System Control – software used to start, stop, and resume a CSS-Wx
648                 System process based upon a predefined condition or user’s request.
649              8. CSS-Wx System Configuration – software used to configure the CSS-Wx System
650                 components including access privileges and adaptation data.

651   3.2.1.1.1 Performance Monitoring

652   3.2.1.1.1.1 System Performance Monitoring
      R.1.3.100.100.100          The CSS-Wx System shall monitor throughput of each CSS-Wx System
                                 Node at the network interface.
      R.1.3.100.400.100          The CSS-Wx System shall monitor System data access response time.
      R.1.3.100.400.200          The CSS-Wx System shall monitor System web service response
                                 time.
      R.1.3.100.400.300          The CSS-Wx System shall monitor System disk access response
                                 time.
      R.1.3.100.400.400         The CSS-Wx System shall monitor System operational state changes in
                                relationship to each CSS-Wx System mode.
      R.1.3.100.700.100.100.100 The CSS-Wx System shall detect System hardware faults.
      R.1.3.100.700.100.200.100 The CSS-Wx System shall detect System software faults.
      R.1.3.100.700.200.100.100 The CSS-Wx System shall isolate System hardware faults.
      R.1.3.100.700.200.200.100 The CSS-Wx System shall isolate System software faults.

653   3.2.1.1.1.2 System Component Monitoring


                                                     16
      R.1.3.100.600.100.100 The CSS-Wx System shall monitor storage utilization.
      R.1.3.100.600.200.100 The CSS-Wx System shall monitor resident memory utilization.
      R.1.3.100.600.300.100 The CSS-Wx System shall monitor central processing unit utilization.
      R.1.3.100.600.400.100 The CSS-Wx System shall monitor database capacity, if applicable.
      R.1.3.100.200.100       The CSS-Wx System shall monitor CSS-Wx System hardware availability.
      R.1.3.100.300.100       The CSS-Wx System shall monitor CSS-Wx System usage by transaction type.
      R.1.3.100.600.001       The CSS-Wx System shall monitor for equipment operating temperature as
                              determined by equipment manufacture specifications.
      R.1.3.100.600.002       The CSS-Wx System shall monitor power supply status.

654   3.2.1.1.2 Manage Logs

655   3.2.1.1.2.1 Event Logging
      R.1.3.300.200.100.100.100 The CSS-Wx System shall log System event types.
      R.1.3.300.200.100.100.200 The CSS-Wx System shall log user-selectable System event types per a
                                user’s request.
      R.1.3.300.200.100.200.100 The CSS-Wx System shall log the specific event that triggered a log entry.
      R.1.3.300.200.100.300.100 The CSS-Wx System shall log the time of the event.
      R.1.3.300.200.100.400.100 The CSS-Wx System shall log any alerts generated as a result of an event.
      R.1.3.300.200.200.100.100 The CSS-Wx System shall log requests for information in a Request for
                                Information log.

656   3.2.1.1.2.2 Log Requests for Information
      R.1.3.300.200.200.200.100 The CSS-Wx System shall log the requestor’s identification in a Request for
                                Information log.
      R.1.3.300.200.200.300.100 The CSS-Wx System shall log the time of the request in the Requests for
                                Information log.
      R.1.3.300.200.200.400.100 The CSS-Wx System shall indicate if the request was fulfilled in a Request
                                for Information Log.
      R.1.3.300.200.200.500.100 The CSS-Wx System shall log the name of the provider system that fulfilled
                                the request in a Request for Information Log.

657   3.2.1.1.2.3 Log Configuration Changes
      R.1.3.300.200.300.100.100 The CSS-Wx System shall log configuration item changes in the
                                Configuration Change Log.
      R.1.3.300.200.300.200.100 The CSS-Wx System shall log the date of a configuration item change in
                                the Configuration Change Log.
      R.1.3.300.200.300.300.100 The CSS-Wx System shall log the time of a configuration item change in
                                the Configuration Change Log.
      R.1.3.300.200.300.400.100 The CSS-Wx System shall log the user name of the user making the
                                configuration item change in the Configuration Change Log.

658   3.2.1.1.2.4 Store Logs
      R.1.3.300.200.400.100.100 The CSS-Wx System shall store all system logs for 90 days.



                                                       17
      R.1.3.300.200.400.100.200 The CSS-Wx System shall store user-specified log entries to removable
                                media based upon a user’s request.
      R.1.2.200.100.001         The CSS-Wx System shall store CSS-Wx System data to removable storage
                                based upon a user’s request.
      R.1.3.300.200.200.100.200 The CSS-Wx System shall find weather data requests in the Requests for
                                Information Log based upon configurable search parameters.
      R.1.3.300.200.200.100.300 The CSS-Wx System shall find stored request for information attributes for
                                each request in the Requests for Information Log based upon configurable
                                search parameters.

659   3.2.1.1.2.5 Log Recording and Playback
      R.1.2.900.100.100.100 The CSS-Wx System shall enable recording of CSS-Wx System data for
                            playback and analysis within a configurable date/time range less than or equal to
                            15 days.
      R.1.2.900.100.100.200 The CSS-Wx System shall playback recorded CSS-Wx System data for a user
                            specified date/time range.
      R.1.2.900.100.100.300 The CSS-Wx System shall pause the playback of recorded CSS-Wx System
                            data.
      R.1.2.900.100.100.400 The CSS-Wx System shall fast-forward the playback of recorded CSS-Wx
                            System data.
      R.1.2.900.100.100.500 The CSS-Wx System shall rewind the playback of recorded CSS-Wx System
                            data.
      R.1.2.900.100.100.600 The CSS-Wx System shall stop the playback of recorded CSS-Wx System data.
      R.1.2.900.100.100.700 The CSS-Wx System shall restart the playback of recorded CSS-Wx System
                            data.

660   3.2.1.1.2.6 Printer Management
      R.5.1.1700.300 The CSS-Wx System shall write a copy of the system log to the CSS-Wx System
                     printer upon a user's request.
      R.5.1.1700.400 The CSS-Wx System shall adjust the font size and typeface used for menus, product
                     displays, and hardcopy printouts based upon a user’s request.
      R.5.1.1700.500 The CSS-Wx System shall abort a printing operation based upon a user’s request.
      R.5.1.1700.600 The CSS-Wx System shall pause a printing operation based upon a user’s request.
      R.5.1.1700.700 The CSS-Wx System shall clear a print operation and continue printing subsequent
                     print queue entries based upon a user’s request.
      R.5.1.1700.800 The CSS-Wx System shall display the system log at the CSS-Wx System
                     Administrative/Maintenance workstation upon user's request.
      R.5.1.1700.900 The CSS-Wx System shall display the system log as it is updated.

661   3.2.1.1.3 Fault Recovery
                                The CSS-Wx System shall recover from hardware faults to maintain the CSS-
      R.1.3.400.100.100.100 Wx System RMA requirements.
                                The CSS-Wx System shall recover from software faults to maintain the CSS-
      R.1.3.400.100.200.100 Wx System RMA requirements.

662   3.2.1.1.4 Performance Reporting

663   3.2.1.1.4.1 Alarms and Alerts


                                                        18
      R.1.3.300.300.100.1000 The CSS-Wx System shall store configurable system alert conditions for
                             monitored CSS-Wx System components.
      R.1.3.300.300.100.1100 The CSS-Wx System shall store configurable system alert conditions for
                             monitored CSS-Wx System modes and states.
      R.1.3.300.300.100.1200 The CSS-Wx System shall store configurable system alert conditions for
                             monitored CSS-Wx System processes.
      R.1.3.300.300.100.1300 The CSS-Wx System shall store configurable system alert conditions for
                             monitored CSS-Wx System performance measurements.
      R.1.3.300.300.100.1400 The CSS-Wx System shall generate alerts when alert conditions are met.
      R.1.3.300.300.100.1500 The CSS-Wx System shall send alerts to a configurable destination address.
                             (For example send the alert to a local maintenance workstation or centralized
                             maintenance and monitoring system).
      R.1.3.300.300.100.1600 The CSS-Wx System shall generate alerts with configurable notification
                             methods listed below:
                                       a) Audible alarms
                                       b) Lights
                                       c) Text
      R.1.3.300.300.100.1700 The CSS-Wx System shall generate alerts with configurable attributes as listed
                             below:
                                       a)   Valid time period for the alarm/alert types
                                       b)   Alarm Volume
                                       c)   Alarm Duration
                                       d)   Variable tone sequence over the range 500-3000 Hertz (Hz)
                                       e)   Alarm acknowledgement requirement
      R.1.3.300.300.100.1800 The CSS-Wx System shall suppress audible alarms upon a user’s request.
      R.1.3.300.300.100.1900 The CSS-Wx System shall suppress visual alerts upon a user’s request.
      R.1.3.300.300.100.2000 The CSS-Wx System shall clear alerts/ alarms upon a user’s request.

664   3.2.1.1.4.2 Reporting
      R.1.3.300.100.100.100     The CSS-Wx System shall produce ad-hoc performance reports based upon
                                system logs.
      R.1.3.300.100.100.200     The CSS-Wx System shall produce ad-hoc performance reports to match
                                user-specified reporting parameters in a user’s request.
      R.1.3.300.100.200.100     The CSS-Wx System shall produce periodic performance reports, where the
                                period is configurable from no less than one day up to and including ninety
                                days.
      R.1.3.300.100.300.100.100 The CSS-Wx System shall report the identity of the CSS-Wx System
                                component where the software fault occurred.
      R.1.3.300.100.300.200.100 The CSS-Wx System shall report the type of software fault.
      R.1.3.300.100.300.300.100 The CSS-Wx System shall report the level of software faults as critical or
                                non-critical based upon pre-defined levels configured by a user with
                                administrative privileges.
      R.1.3.300.100.300.400.100 The CSS-Wx System shall report the time a software fault occurred.
      R.1.3.300.100.300.500.100 The CSS-Wx System shall report alerts that were generated as a result of a
                                software fault.
      R.1.3.300.100.300.600.100 The CSS-Wx System shall report the actions that were taken to isolate or
                                correct a software fault.



                                                        19
      R.1.3.300.100.400.100.100 The CSS-Wx System shall report the identity of the CSS-Wx System sub-
                                component where a hardware fault occurred.
      R.1.3.300.100.400.200.100 The CSS-Wx System shall report the type of hardware fault.
      R.1.3.300.100.400.300.100 The CSS-Wx System shall report the level of a hardware fault as critical or
                                non-critical based upon pre-defined levels configured by a user with
                                administrative privileges.
      R.1.3.300.100.400.400.100 The CSS-Wx System shall report the time a hardware fault occurred.
      R.1.3.300.100.400.500.100 The CSS-Wx System shall report any alerts that were generated as a result
                                of a hardware fault.
      R.1.3.300.100.400.600.100 The CSS-Wx System shall report the actions that were taken to isolate or
                                correct a hardware fault.
      R.1.3.300.100.100.300     The CSS-Wx System shall report a summary of alerts based upon user-
                                specified alert attributes. (For example, date, time, location, type of alert.)
      R.1.3.300.100.100.400     The CSS-Wx System shall write a copy of a system report to the CSS-Wx
                                System printer upon a user's request.
      R.1.3.300.100.100.500     The CSS-Wx System shall produce system reports to match a user-specified
                                report format.

665   3.2.1.1.5 Metrics Reporting
      R.1.3.300.100.500.100.100 The CSS-Wx System shall report consumer usage statistics based on
                                configurable reporting criteria. (For example, usage by user, usage by
                                service, usage by location, etc.)
      R.1.3.300.100.500.200.100 The CSS-Wx System shall report dataset usage statistics based on
                                configurable criteria.
      R.1.3.300.100.500.300.100 The CSS-Wx System shall report service usage statistics based on
                                configurable criteria.
      R.1.3.300.100.500.400.100 The CSS-Wx System shall report performance statistics based on
                                configurable criteria.
      R.1.3.300.200.400.100.300 The CSS-Wx System shall store reports for 90 days.
      R.1.3.300.200.400.100.400 The CSS-Wx System shall store CSS-Wx System performance statistics in
                                the registry/repository to support load balancing.
      R.1.3.300.200.400.100.500 The CSS-Wx System shall update CSS-Wx System performance statistics
                                in the registry/repository once every 5 minutes.

666   3.2.1.1.6 Endpoint Control
      R.1.3.400.300.300.100 The CSS-Wx System shall start weather service endpoints at Node initialization.
      R.1.3.400.300.400.100 The CSS-Wx System shall stop weather service endpoints upon a user’s request.
      R.1.3.400.300.300.200 The CSS-Wx System shall resume weather service endpoints upon a user’s
                            request.
      R.1.3.400.300.500.100 The CSS-Wx System shall shutdown weather service endpoints upon a user’s
                            request.

667   3.2.1.1.7 System Control
      R.2.2.100.200.100 The CSS-Wx System shall switch a CSS-Wx System component to backup in less
                        than or equal to 5 seconds, allowing a component to be taken offline to perform
                        maintenance upon a user’s request.
      R.2.2.100.200.200 The CSS-Wx System shall switch from backup Node to primary based upon a
                        configurable event.


                                                         20
668   3.2.1.1.8 System Configuration
      R.1.3.400.100.300.100 The CSS-Wx System shall switch CSS-Wx System software from the latest
                            software baseline to the previous software baseline upon a user’s request.
      R.1.3.400.100.400.100 The CSS-Wx System shall switch a CSS-Wx System software baseline from the
                            previous software baseline to the latest software baseline upon a user’s request.
      R.1.3.400.100.600.100 The CSS-Wx System shall allow for two versions of the CSS-Wx System Web
                            Coverage Service-Implementation (WCS-I) to be run concurrently in the same
                            environment on the same node.
      R.1.3.400.100.500.100 The CSS-Wx System shall allow for two versions of the CSS-Wx System Web
                            Feature Service-Implementation (WFS-I) to be run concurrently in the same
                            environment on the same node.
      R.1.3.400.100.700.100 The CSS-Wx System shall allow for two versions of the CSS-Wx System Web
                            Map Service-Implementation (WMS-I) to be run concurrently in the same
                            environment on the same node.
      R.1.3.500.200.001     The CSS-Wx System shall store CSS-Wx System configuration parameter
                            values for a configurable amount of time.
      R.1.3.500.300.100     The CSS-Wx System shall modify CSS-Wx System configuration parameter
                            values based upon a user’s request.
      R.1.3.500.200.100.100 The CSS-Wx System shall store user-access permissions based upon a user’s
                            request.
      R.1.3.500.400.100     The CSS-Wx System shall associate priorities with weather products in
                            accordance with adaptation data.
      R.1.3.500.400.200     The CSS-Wx System shall configure the functionality provided by a CSS-Wx
                            System Node in accordance with adaptation data.
      R.1.3.500.400.300     The CSS-Wx System shall configure a CSS-Wx System Node’s Subscriptions to
                            specified Topics in accordance with adaptation data.
      R.1.3.500.400.400     The CSS-Wx System shall configure a CSS-Wx System Node tailoring of
                            specified weather products in accordance with adaptation data.

669        3.2.1.2 Common Security Management Components

670   3.2.1.2.1 Information Security

671   3.2.1.2.1.1    Access Control
       R.1.4.100.500.100        The CSS-Wx System shall separate user functionality from information
                                system management functionality. (Derived from [NIST 800-53, SC-2].)
       R.1.4.400.200.1100.100   The CSS-Wx System shall grant access to system resources based on the
                                rights and privileges defined for each authenticated identity. (Derived from
                                [NIST 800-53, AC-2, AC-5] and [FAA Order 1370.96].)
       R.1.4.400.200.1800.100   The CSS-Wx System shall implement access based on least privilege.
                                (Derived from [NIST 800-53 AC-6] and [FAA Order 1370.96].)
       R.1.4.400.200.1900.100   The CSS-Wx System shall protect access control lists from unauthorized
                                addition. (Derived from [NIST 800-53] and [AC-2EN4].)
       R.1.4.400.200.2000.100   The CSS-Wx System shall protect access control lists from unauthorized
                                deletion. (Derived from [NIST 800-53] and [AC-2EN4].)
       R.1.4.400.200.2100.100   The CSS-Wx System shall protect access control lists from unauthorized
                                modification. (Derived from [NIST 800-53] and [AC-2EN4].)
       R.1.4.400.200.2200.100   The CSS-Wx System shall protect access control lists from unauthorized
                                access. (Derived from [NIST 800-53] and [AC-2EN4].)



                                                        21
      R.6.2.100.100.100        The CSS-Wx System shall implement privileged user accounts. (Derived
                               from [NIST 800-53, AC-5].)
      R.1.4.400.200.1100.200   The CSS-Wx System shall restrict modifications of the System to users with
                               administrative privileges. (Derived from [NIST 800-53, AC-6EN1].)
      R.1.4.100.100.100        The CSS-Wx System shall audit privileged role assignments. (Derived from
                               [NIST 800-53, AC-2EN4].)
      R.1.4.400.200.1200.100   The CSS-Wx System shall disable an account after an adaptable period from
                               30 to 180 days of continuous inactivity. (Derived from [NIST 800-53, AC-
                               2EN3].)
      R.1.4.400.200.1200.200   The CSS-Wx System shall terminate temporary and emergency accounts after
                               an adaptable time period of 1 to 30 days. (Derived from [NIST 800-53, AC-
                               2EN2].)
      R.1.4.400.200.2200.200   The CSS-Wx System shall enforce assigned authorizations for controlling
                               access to the system. (Derived from [NIST 800-53, AC-3] and [FAA Order
                               1370.96].)
      R.1.4.400.200.1100.300   The CSS-Wx System shall enforce separation of duties through assigned
                               access authorizations. (Derived from [NIST 800-53, AC-3, AC-6] and [FAA
                               Order 1370.96].)
      R.1.4.400.200.1100.400   The CSS-Wx System shall explicitly limit security functions to a user with
                               security administrator privileges. (Derived from [NIST 800-53, AC-6EN1].)
      R.1.4.400.200.900.100    The CSS-Wx System shall display an FAA system use notification message
                               to potential users before granting System access. (Derived from [NIST 800-
                               53, AC-8] and [FAA Order 1370.102].)
      R.1.4.400.200.900.200    The CSS-Wx System shall retain the use of a notification message on-screen
                               until users take explicit actions to further logon to the System. (Derived from
                               [NIST 800-53, AC-8] and [FAA Order 1370.102].)
      R.1.4.400.200.1200.300   The CSS-Wx System shall initiate a session lock/logout for a user with
                               administrative privileges after an adaptable time period of 15 – 30 minutes.
                               (Derived from [NIST 800-53, AC-11].)
      R.1.4.400.200.1200.400   The CSS-Wx System shall initiate a user session lock/logout upon a user’s
                               request. (Derived from [NIST 800-53, AC-11].)
      R.1.4.400.200.300.100    The CSS-Wx System shall retain a user session lock/logout until the user
                               reestablishes access and follows the appropriate identification and
                               authentication procedures. (Derived from [NIST 800-53, AC-11].)
      R.1.4.400.200.1100.500   The CSS-Wx System shall identify specific user actions that can be performed
                               on the System without identification or authentication. (For example, when
                               individuals access public websites or other publicly accessible federal
                               information systems such as http://www.usa.gov). (Derived from [NIST
                               800-53, AC-14].)
      R.1.5.500.200.100        The CSS-Wx System shall use cryptography to protect the confidentiality and
                               integrity of remote access sessions. (Derived from [NIST 800-53, AC-
                               17EN2].)
      R.1.5.600.100.300        The CSS-Wx System shall route all remote access through FAA authorized
                               access control points. (Derived from [NIST 800-53, AC-17EN3].)

672   3.2.1.2.1.2 Audit and Accountability
      R.1.4.100.100.200           The CSS-Wx System shall generate audit records for those items identified
                                  in FAA Order 1370.105, Logical Access Control Policy and FAA Order
                                  1370.101 Information Security Reporting and Response Policy. (Derived


                                                       22
                           from [NIST 800-53, AU-3EN1] and [FAA Orders 1370.101, 1370.105].)
R.1.4.100.400.200         The CSS-Wx System shall generate internal timestamps for logs. (Derived
                          from [NIST 800-53, AU-8].)
R.1.4.400.200.1400.100    The CSS-Wx System shall record creation of an account in the audit log.
                          (Derived from NIST 800-53, AC-2EN4] and [FAA Order 1370.96].)
R.1.4.400.200.1500.100    The CSS-Wx System shall record modification of an account in the audit
                          log. (Derived from [NIST 800-53, AC-2EN4] and [FAA Order 1370.96].)
R.1.4.400.200.1600.100    The CSS-Wx System shall record disabling of an account in the audit log.
                          (Derived from [NIST 800-53, AC-2EN4] and [FAA Order 1370.96].)
R.1.4.400.200.1700.100    The CSS-Wx System shall record termination of an account in the audit
                          log. (Derived from [NIST 800-53, AC-2EN4] and [FAA Order 1370.96].)
R.1.3.300.300.200.100     The CSS-Wx System shall send an alert to the administrative and
                          maintenance workstation when accounts are modified. (Derived from
                          [NIST 800-53, AC-2EN4] and [FAA Order 1370.101].)
R.1.4.100.100.400         The CSS-Wx System shall record execution of privileged functions and
                          account in the audit log. (Derived from [NIST 800-53, AU-2EN4].)
R.1.4.100.100.500         The CSS-Wx System shall produce audit logs that contain information to
                          establish the sources of the events, and the outcomes of the events.
                          (Derived from [NIST 800-53, AU-3].)
R.1.4.100.100.600         The CSS-Wx System shall produce audit logs that include detailed
                          information about events based on type, location, or subject. (Derived
                          from [NIST 800-53, AU-3].)
R.1.4.100.100.700         The CSS-Wx System shall store audit logs for a configurable amount of
                          time. (Derived from [NIST 800-53, AU-11].)
R.1.4.100.100.800         The CSS-Wx System shall configure its audit log storage capacity to
                          reduce the likelihood of such capacity being exceeded. (Derived from
                          [NIST 800-53, AU-4].)
R.1.4.100.100.900         The CSS-Wx System shall generate an alert in the event of an audit
                          processing failure. (Derived from [NIST 800-53, AU-5].)
R.1.4.100.100.1000        The CSS-Wx System shall review and analyze information system audit
                          logs for unusual activity, and generate an alert when unusual activity
                          occurs. (Derived from [NIST 800-53, IR-6].)
R.1.4.100.100.1100        The CSS-Wx System shall adjust the level of audit review, analysis, and
                          reporting within the CSS-Wx System upon a user’s request. (Derived from
                          [NIST 800-53, AU-6].)
R.1.4.100.100.1200        The CSS-Wx System shall implement audit tools to perform audit review,
                          analysis, and reporting. (Derived from [NIST 800-53, AU-7EN1].)
R.1.4.200.300.300         The CSS-Wx System shall monitor for unauthorized remote connections
                          to the CSS-Wx System. (Derived from [NIST 800-53, AC-17EN1] and
                          [FAA Order 1370.116].)
R.1.4.200.100.200         The CSS-Wx System shall disconnect unauthorized remote connections to
                          the CSS-Wx System. (Derived from [NIST 800-53, AC-17EN4] and [FAA
                          Order 1370.116].)
R.1.3.300.200.100.100.500 The CSS-Wx System shall log unauthorized remote connections to the
                          CSS-Wx System. (Derived from [NIST 800-53, AC-17EN5] and [FAA
                          Order 1370.116].)
R.1.4.100.100.1300        The CSS-Wx System shall record remote sessions that access privileged
                          accounts in the audit log. (Derived from [NIST 800-53, AC-17EN7] and
                          [FAA Order 1370.116].)




                                               23
673   3.2.1.2.1.3     Configuration Management
       R.1.4.100.300.100         The CSS-Wx System shall detect unauthorized changes to software and
                                 data. (Derived from [NIST 800-53, CM-6EN3].)
       R.1.4.400.200.1100.700    The CSS-Wx System shall implement the mandatory configuration
                                 settings employed within the CSS-Wx System that reflects the most
                                 restrictive approach. (Derived from [NIST 800-53, CM-7].)
       R.1.3.300.200.300.100.200 The CSS-Wx System shall monitor changes to configuration settings.
                                 (Derived from [NIST 800-53, CM-6].)
       R.1.3.500.300.200         The CSS-Wx System shall only allow users with administrative privileges
                                 to change configuration settings. (Derived from [NIST 800-53, CM-6].)

674   3.2.1.2.1.4 Identification and Authentication
      R.6.2.300.100.100 The CSS-Wx System shall require passwords be at least eight [8] characters in
                        length, containing at least one upper case letter, one lower case letter, one number,
                        and one special character. (Derived from [NIST 800-53, IA-5EN1] and [FAA Order
                        1370.92A].)
      R.6.2.300.100.200 The CSS-Wx System shall require passwords less than 13 characters in length to be
                        changed at least every 90 days. (Derived from [NIST 800-53, IA-5EN1] and [FAA
                        Order 1370.92A].)
      R.6.2.300.100.300 The CSS-Wx System shall allow passwords of 13 or more characters in length that
                        are consistent with FAA Order 1370.92A. (Derived from [NIST 800-53, IA-5EN1]
                        and [FAA Order 1370.92A].)
      R.6.2.300.100.400 The CSS-Wx System shall encrypt passwords in storage and in transmission, for
                        password-based authentication. (Derived from [NIST 800-53, AC5EN1] and [FAA
                        Order 1370.92A].)
      R.6.2.300.100.500 The CSS-Wx System shall prohibit password reuse for ten generations. (Derived
                        from [NIST 800-53, AC5EN1] and [FAA Order 1370.92A].)
      R.6.2.300.100.600 The CSS-Wx System shall verify the identity of the individual and/or device
                        requesting access. (Derived from [NIST 800-53, IA-5EN1].)

675   3.2.1.2.1.5 Incident Response
       R.1.4.100.100.300 The CSS-Wx System shall record security incidents to a CSS-Wx System-managed
                         Security Incident and Event Manager service. (Derived from [NIST 800-53, IR-
                         4EN1].)

676   3.2.1.2.1.6 Media Protection
       R.1.4.300.100.400 The CSS-Wx System shall employ cryptographic mechanisms to protect the
                         confidentiality and integrity of information stored on removable digital media.
                         (Derived from [NIST 800-53, MP-5EN4] and [FAA Order 1370.111].)

677   3.2.1.2.1.7 System and Communications Protection
       R.1.4.100.200.100 The CSS-Wx System shall protect against denial of service attacks. (Derived from
                         [NIST 800-53, SC-5].)
       R.1.4.100.600.100 The CSS-Wx System shall prevent unauthorized information transfer via shared
                         system resources. (Derived from [NIST 800-53, SC-4].)
       R.1.4.100.600.200 The CSS-Wx System shall deny network traffic by default and allow network
                         traffic by exception. (Derived from [NIST 800-53, SC-7EN5].)
       R.1.4.200.100.100 The CSS-Wx System shall prohibit remote activation of collaborative computing
                         mechanisms and alert local users with an explicit indication. (Derived from [NIST


                                                        24
                          800-53, SC-15].)
      R.1.4.200.300.100 The CSS-Wx System shall monitor the use of mobile code within the System.
                        (Derived from [NIST 800-53, SC-18].)
      R.1.4.200.300.200 The CSS-Wx System shall control the use of mobile code within the System.
                        (Derived from [NIST 800-53, SC-18].)
      R.1.4.300.100.500 The CSS-Wx System shall implement mechanisms to protect the authenticity of
                        communications sessions. (Derived from [NIST 800-53, SC-23].)
      R.1.4.300.100.600 The CSS-Wx System shall protect the confidentiality and integrity of information at
                        rest. (Derived from [NIST 800-53, SC-28].)

678   3.2.1.2.1.8 System and Information Integrity
      R.1.4.300.100.700      The CSS-Wx System shall perform integrity and security checks of weather
                             data.
      R.1.4.100.300.200      The CSS-Wx System shall implement malicious code protection. (Derived
                             from [NIST 800-53, SI-3] and [FAA Order 1370.116].)
      R.1.4.100.300.300      The CSS-Wx System shall manage malicious code protection mechanisms at
                             the system level. (Derived from [NIST 800-53, SI-3EN1].)
      R.1.4.100.300.400      The CSS-Wx System shall automatically update malicious code protection
                             mechanisms. (Derived from [NIST 800-53, SI-3EN2].)
      R.1.4.400.200.1800.200 The CSS-Wx System shall prevent non-privileged users from circumventing
                             malicious code protection capabilities. (Derived from [NIST 800-53, SI-
                             3EN3].)
      R.1.4.100.300.500      The CSS-Wx System shall be configured to detect and scan connected,
                             removable media for malicious software. (Derived from [NIST 800-53, SI-
                             3].)
      R.1.3.100.300.200      The CSS-Wx System shall employ automated tools to support near-real-time
                             analysis of events. (Derived from [NIST 800-53, Si-4EN2].)
      R.1.4.100.300.600      The CSS-Wx System shall detect unauthorized changes to software. (Derived
                             from [NIST 800-53, SI-7].)

679   3.2.1.2.2 Privacy
      R.6.2.300.100.700      The CSS-Wx System shall protect any Personally Identifiable Information
                             from unauthorized disclosure. (Derived from [NIST 800-53, IA-8] and [FAA
                             Order 1280.1B, 1370.111].)
      R.6.2.300.100.800      The CSS-Wx System shall encrypt any Personally Identifiable Information.
                             (Derived from [FAA Order1370.111].)
      R.1.4.400.200.1100.600 The CSS-Wx System shall limit the distribution of proprietary data to
                             authorized users.

680        3.2.1.3 Messaging Management
681   The NAS Enterprise Messaging Service (NEMS) of the SWIM Enterprise Service Bus (ESB)
682   provides messaging services for the CSS-Wx System. The CSS-Wx System nodes send
683   messages to the NEMS nodes and the CSS-Wx System consumers connect to the NEMS node to
684   receive the messages.
685   Java Message Service (JMS) is an Application Program Interface (API) for accessing the NEMS
686   from the CSS-Wx System. Error! Reference source not found.Figure 4 shows CSS-Wx
687   System publish/subscribe messaging to the NEMS JMS Topics and JMS Queues.
688


                                                      25
689          a) JMS-based Topic messaging is characterized as an addressable messaging channel
690             with which messages are associated and applications/consumers subscribe to the
691             NEMS node to receive the message data.
692          b) JMS Queue messaging is point-to-point messaging where the message is consumed
693             once and only once by a consumer. JMS Queue messaging may be adopted when the
694             weather data providers have to communicate with a single known target application,
695             for example, a metadata update is targeted for the CSS-Wx System
696             Registry/Repository and the update is received by the CSS-Wx System
697             Registry/Repository.
698
699   The CSS-Wx System supports publish and subscribe and request-reply messaging patterns. The
700   CSS-Wx System functional requirements to support publish and subscribe capabilities are
701   described below:

702   3.2.1.3.1 Publish/Subscribe Messaging Pattern
       R.1.5.200.100.001 The CSS-Wx System shall create a JMS message containing data from a CSS-Wx
                         System Provider before publishing data.
       R.1.5.200.100.002 The CSS-Wx System shall send JMS messages to static topics, where appropriate.
       R.1.5.200.100.003 The CSS-Wx System shall send JMS messages to dynamic topics, where
                         appropriate.
       R.1.5.200.100.004 The CSS-Wx System shall send JMS messages to static queues, where appropriate.
       R.1.5.200.100.005 The CSS-Wx System shall send JMS messages to dynamic queues, where
                         appropriate.
       R.1.5.200.100.006 The CSS-Wx System shall publish JMS messages at user-specified intervals which
                         are greater than or equal to the weather product refresh rate.
       R.1.5.100.100.001 The CSS-Wx System shall subscribe to static topics for CSS-Wx System Consumer
                         Service Adaptors.
       R.1.5.100.100.002 The CSS-Wx System shall subscribe to dynamic topics for CSS-Wx System
                         Consumer Service Adaptors.
       R.1.5.100.100.003 The CSS-Wx System subscribe to static queues for CSS-Wx System Consumer
                         Service Adaptors.
       R.1.5.100.100.004 The CSS-Wx System shall subscribe to dynamic queues for CSS-Wx System
                         Consumer Service Adaptors.
703
704   Weather data can be composed of large datasets and, in order to conserve bandwidth, additional
705   techniques of receiving weather out-of-band may be needed. In the case of a subscription to
706   NEMS for large datasets, the CSS-Wx System Consumer Service or Proxy Service may receive
707   only a notification of where the data is located and not the dataset. The CSS-Wx System would
708   use the reference address in the received message to locate and retrieve the coverage dataset.

709   3.2.1.3.2 Request/Reply Messaging Pattern
710   The CSS-Wx System will have an HTTP-based messaging processor for requests and responses
711   as shown in Error! Reference source not found.Figure 5. The CSS-Wx System messaging
712   processor will receive request redirects and forwards from a NEMS proxy and the response to
713   the requests will be constructed by retrieval of data from other components in the CSS-Wx
714   System.


                                                     26
715   3.2.1.3.2.1 Forward/Redirect Request
      R.1.5.600.100.100 The CSS-Wx System shall forward messages received from a NEMS node.
      R.1.5.600.100.200 The CSS-Wx System shall redirect messages received from a NEMS node.

716   3.2.1.3.2.2 Respond to a Request
      R.1.5.300.100.100 The CSS-Wx System shall receive data for sending a response to a request for data.
      R.1.5.400.100.100 The CSS-Wx System shall receive response messages and forward responses to a
                        NEMS node.

717   3.2.1.3.2.3 Publish through Web Service
      R.1.5.200.200.100.100 The CSS-Wx System shall publish data using web services hosted on the
                            NEMS.

718   3.2.1.3.2.4 Consume through Web Service
      R.1.5.100.100.100 The CSS-Wx System Consumer Service Adaptor shall consume data using web
                        services hosted on the NEMS.
      R.1.5.100.100.200 The CSS-Wx System Consumer Service Adaptor shall consume messages and
                        retrieve data from the messages.
      R.1.5.100.100.300 The CSS-Wx System Consumer Service Adaptor shall consume messages and
                        further retrieve data from a uniform resource locator address using the HTTP
                        protocol.

719   3.2.1.3.2.5 Perform Reliable Messaging
      R.1.5.800.100.100 The CSS-Wx System shall send reliable message notifications to subscribed
                        consumers for weather metadata changes achieving at least one delivery assurance
                        acknowledgement.

720   3.2.1.3.2.6 Prioritize Messaging
       R.1.5.700.100.100 The CSS-Wx System shall add a message header to each message indicating
                         the priority at which the message needs to be expedited based upon Service
                         Level Objectives.


721     3.2.2 Registry/Repository
722   The CSS-Wx System Registry/Repository is an ebXML Registry/Repository that allows for
723   ISO19139 metadata and CSS-Wx System documentation to be added, maintained, removed, and
724   discovered by CSS-Wx System weather data publishers, consumers, and authorized maintainers.
725   The CSS-Wx System design-time registry refers to an offline CSS-Wx System
726   Registry/Repository used to stage data for the CSS-Wx System runtime environment. This is not
727   a reference to the NAS Registry/Repository.
728

729        3.2.2.1 Manage Discovery

730   3.2.2.1.1 Manage Design-time Discovery
      R.1.1.100.100.100.100 The CSS-Wx System Registry/Repository shall perform design-time discovery


                                                      27
                               of static messaging publish/subscribe topics based upon a user’s request.
      R.1.1.100.100.200.100 The CSS-Wx System Registry/Repository shall perform design-time discovery
                            of dynamic publish/subscribe topic based upon a user’s request.
      R.1.1.100.100.300.100 The CSS-Wx System Registry/Repository shall perform design-time discovery
                            of weather datasets based on matching of ISO 19139 metadata from the CSS-
                            Wx System Weather Ontology.
      R.1.1.100.100.400.100 The CSS-Wx System Registry/Repository shall perform design-time discovery
                            of weather services based on matching of ISO 19139 metadata from the CSS-
                            Wx System Weather Ontology.
      R.1.1.100.100.500.100 The CSS-Wx System Registry/Repository shall perform design-time discovery
                            of sensor data based on matching of SensorML metadata.
      R.1.1.100.100.600.100 The CSS-Wx System Registry/Repository shall return the service endpoint(s)
                            in response to a search request.

731   3.2.2.1.2 Manage Runtime Discovery
732
      R.1.1.100.200.100.100 The CSS-Wx System Registry/Repository shall perform runtime discovery of
                            static publish/subscribe topics upon a user’s request.
      R.1.1.100.200.200.100 The CSS-Wx System Registry/Repository shall perform runtime discovery of
                            dynamic publish/subscribe topics upon a user’s request.
      R.1.1.100.200.300.100 The CSS-Wx System Registry/Repository shall perform runtime discovery of
                            weather datasets based on matching of ISO 19139 metadata using the CSS-Wx
                            System Weather Ontology.
      R.1.1.100.200.400.100 The CSS-Wx System Registry/Repository shall perform runtime discovery of
                            weather services based on matching of ISO 19139 metadata using the CSS-Wx
                            System Weather Ontology.
      R.1.1.100.200.500.100 The CSS-Wx System Registry/Repository shall perform runtime discovery of
                            sensor data based on matching of SensorML metadata using the CSS-Wx
                            System Weather Ontology.
      R.1.1.100.200.600.100 The CSS-Wx System Registry/Repository shall return multiple endpoints for a
                            given logical service in support of load balancing and fault tolerance.
      R.1.1.100.200.700.100 The CSS-Wx System Registry/Repository shall include CSS-Wx System
                            resource usage statistics to the list of services returned to the client in support
                            of resource-sensitive service discovery.
      R.1.1.100.200.800.100 The CSS-Wx System Registry/Repository shall perform runtime discovery of
                            CSS-Wx System services based on their dynamic tailoring capabilities.

733   3.2.2.1.3 Manage Weather Metadata Notifications
      R.1.1.200.100.100 The CSS-Wx System Registry/Repository shall store weather metadata notification
                        subscriptions in response to a subscriber’s request.
      R.1.1.200.200.100 The CSS-Wx System Registry/Repository shall modify weather metadata
                        notification subscriptions in response to a subscriber’s request.
      R.1.1.200.300.100 The CSS-Wx System Registry/Repository shall remove weather metadata
                        notification subscriptions in response to a subscriber’s request.
734

      3.2.2.1.3.1 Notify Weather Metadata Subscribers
      R.1.1.200.400.100.100 The CSS-Wx System Registry/Repository shall notify subscribers when new



                                                        28
                              weather metadata are added based on the subscription notification parameters.
      R.1.1.200.400.200.100 The CSS-Wx System Registry/Repository shall notify subscribers of weather
                            metadata modifications based on the notification parameters specified by each
                            subscriber.
      R.1.1.200.400.300.100 The CSS-Wx System Registry/Repository shall notify subscribers of weather
                            metadata removal based on the notification parameters specified by the
                            consumer.

735       3.2.2.2 Manage Weather Metadata

      3.2.2.2.1 Update Weather Metadata
      R.1.1.300.100.200.100     The CSS-Wx System Registry/Repository shall modify weather metadata
                                upon a user’s request.
      R.1.1.300.100.200.200     The CSS-Wx System Registry/Repository shall modify taxonomy
                                associations to metadata upon a user’s request.
      R.1.1.300.100.300.100     The CSS-Wx System Registry/Repository shall remove weather metadata
                                upon a user’s request.
      R.1.1.300.100.300.200     The CSS-Wx System Registry/Repository shall remove artifacts upon a
                                user’s request.
      R.1.1.300.100.300.300     The CSS-Wx System Registry/Repository shall remove taxonomy
                                associations to metadata upon a user’s request.
736

      3.2.2.2.2 Manage Taxonomies
      R.1.1.300.200.100.600 The CSS-Wx System Registry/Repository shall allow creation of taxonomies.
      R.1.1.300.100.200.300 The CSS-Wx System Registry/Repository shall allow modification of
                            taxonomies.
      R.1.1.300.100.300.400 The CSS-Wx System Registry/Repository shall allow deletion of taxonomies.
      R.1.1.300.100.200.400 The CSS-Wx System Registry/Repository shall support customizable,
                            extensible, and composable taxonomies in addition to the taxonomies required
                            by [NAS Registry IRD], [CSS-Wx Metadata Profile] and [FAA-STD-065].
      R.1.1.300.200.100.700 The CSS-Wx System Registry/Repository shall be able to import and export
                            taxonomies as XML files.
      R.1.1.300.100.200.500 The CSS-Wx System Registry/Repository shall allow definition and extension
                            of taxonomy-based elements by means of an interactive user interface.
      R.1.1.300.200.100.800 The CSS-Wx System Registry/Repository shall ensure the uniqueness of
                            publisher-assigned reference keys in the registry via partitioning of the key
                            space or other mechanism, in accordance with [FAA-STD-064].
      R.1.1.300.100.200.600 The CSS-Wx System Registry/Repository shall add taxonomy associations to
                            metadata based upon a user’s request.
737

      3.2.2.2.3 Store Weather Metadata
      R.1.1.300.200.100.100 The CSS-Wx System Registry/Repository shall store metadata for CSS-Wx
                            System services to the CSS-Wx System metadata repository upon receipt.




                                                      29
      R.1.1.300.200.200.100 The CSS-Wx System Registry/Repository shall store metadata for weather
                            datasets to the CSS-Wx System metadata repository upon receipt.
      R.1.1.300.200.200.200 The CSS-Wx System Registry/Repository shall store sensor metadata to the
                            CSS-Wx System metadata repository upon receipt.

738

      3.2.2.2.3.1 Store Metadata for Named Geospatial Points.
      R.1.1.300.200.300.100.100 The CSS-Wx System Registry/Repository shall store ISO 19139 metadata
                                to support queries for services with Named Geospatial Points.
      R.1.1.300.200.300.200.100 The CSS-Wx System Registry/Repository shall store ISO 19139 metadata
                                to support queries for datasets with Named Geospatial Points.
      R.1.1.300.200.300.300.100 The CSS-Wx System Registry/Repository shall store ISO 19139 metadata
                                to support queries for datasets for Named Geospatial Line Segments.
      R.1.1.300.200.300.400.100 The CSS-Wx System Registry/Repository shall store ISO 19139 metadata
                                to support queries for datasets for Named Geospatial 2-D Polygons.
      R.1.1.300.200.300.500.100 The CSS-Wx System Registry/Repository shall store ISO 19139 metadata
                                to support queries for datasets for Named Geospatial Circles.
      R.1.1.300.200.300.600.100 The CSS-Wx System Registry/Repository shall store ISO 19139 metadata
                                to support queries for datasets for Named Geospatial 3-D Polygons.
      R.1.1.300.200.300.700.100 The CSS-Wx System Registry/Repository shall store ISO 19139
                                  metadata to support queries for datasets for Named Geospatial
                                  Cylinders.
739

      3.2.2.2.3.2 Store User-defined Queries and Metadata
      R.1.1.300.200.400.100.100 The CSS-Wx System Registry/Repository shall store weather data filtering
                                queries.
      R.1.1.300.200.400.200.100 The CSS-Wx System Registry/Repository shall store ISO 19139 metadata
                                for user-defined filtering queries.
      R.1.1.300.200.500.100.100 The CSS-Wx System Registry/Repository shall store service interface
                                schemas. (i.e., XML Schema Definition for downloading by service
                                providers).
      R.1.1.300.200.200.300     The CSS-Wx System Registry/Repository shall store weather provider
                                information in accordance with [FAA-STD-064] and [FAA-STD-065].
                                (For example, organization information, contact name(s), phone numbers,
                                locations, and e-mail addresses.)
      R.1.1.300.200.100.900     The CSS-Wx System Registry/Repository shall store weather consumer
                                information, organization information in accordance with [FAA-STD-064]
                                and [FAA-STD-065]. (For example, contact name(s), phone numbers,
                                locations, and e-mail addresses.)
      R.1.1.300.200.100.200     The CSS-Wx System Registry/Repository shall store service information
                                in accordance with [FAA-STD-064] and [FAA-STD-065]. (For example,
                                binding, versioning, and lifecycle stage information, and relationships to
                                other services.)
      R.1.1.300.200.100.300     The CSS-Wx System Registry/Repository shall store service artifacts in
                                accordance with [FAA-STD-064] and [FAA-STD-065]. (For example,
                                IRDs, WSDL files, WS-Policy files, XSD files and service-level
                                agreements.)


                                                      30
      R.1.1.300.200.100.400        The CSS-Wx System Registry/Repository shall store all documentary
                                   elements of service contracts in accordance with [FAA-STD-064] and
                                   [FAA-STD-065]. (For example, static quality of service (QoS) objectives
                                   for services, if any.)
      R.1.1.300.200.100.500        The CSS-Wx System Registry/Repository shall store metadata for multiple
                                   versions of a service, in accordance with [FAA-STD-064] and [FAA-STD-
                                   065].
740

      3.2.2.2.3.3 Store Policies
      R.1.1.300.200.500.100.200 The CSS-Wx System Registry/Repository shall store policies that comply
                                with FAA Web Services Policy and Web Service Security Policy [FAA
                                Order 1370.113].
      R.1.1.300.200.500.100.300 The CSS-Wx System Registry/Repository shall store policies for
                                consumption of NAS services, in accordance with [FAA-STD-064] and
                                [FAA-STD-065].

741   3.2.2.2.3.4 Store Coordinate Reference System Definitions
      R.1.1.300.200.300.200.200 The CSS-Wx System Registry/Repository shall store coordinate reference
                                system definitions containing Uniform Resource Identifiers which can
                                manifest as Uniform Resource Locators.

      3.2.2.2.3.5    Archive Repository Contents
      R.1.1.300.200.400.200.200 The CSS-Wx System Registry/Repository shall archive weather metadata
                                upon based upon configurable parameters.
      R.1.1.300.200.400.100.200 The CSS-Wx System Registry/Repository shall archive weather Service
                                Information upon configurable parameters.

742   3.2.2.2.4 Manage Weather Metadata across Registries/Repositories
      R.1.1.300.300.100 The CSS-Wx System Registry/Repository shall synchronize weather metadata
                        among CSS-Wx System registries /repositories based upon user-configurable,
                        event-based parameters. (Examples include date, time, day of the week, time of
                        day, metadata description.)
743

      3.2.2.2.5 Facilitate Navigation and Browsing
      R.1.1.100.100.001 The CSS-Wx System Registry/Repository Graphical User Interface shall allow
                        authorized users to browse weather metadata.
      R.1.1.100.100.002 The CSS-Wx System Registry/Repository Graphical User Interface shall execute
                        parameterized queries.
      R.1.1.100.100.003 The CSS-Wx System Registry/Repository Graphical User Interface shall provide
                        both textual and graphical views of metadata defined by [FAA-STD-064] and
                        [FAA-STD-065]. (Graphical view refers to the types of presentations offered by
                        commercial WSDL editors or XML viewers.)
      R.1.1.100.100.004 The CSS-Wx System Registry/Repository Graphical User Interface shall provide a
                        means for consumers to view and/or download CSS-Wx System service artifacts
                        defined by [FAA-STD-064] and [FAA-STD-065].
      R.1.1.100.100.005 The CSS-Wx System Registry/Repository Graphical User Interface shall support


                                                      31
                          role-based access to metadata for different user roles and user groups.
      R.1.1.100.100.006 The CSS-Wx System Registry/Repository Graphical User Interface shall allow
                        search and navigation to artifacts.
      R.1.1.100.100.007 The CSS-Wx System Registry/Repository Graphical User Interface shall validate
                        weather metadata format.

744     3.2.3 Service Adaptors

745        3.2.3.1 System Ingest Adaptors (SIA)
746   The CSS-Wx SIA is a notional software component that provides the function of System Data
747   Ingest for legacy provider systems. It is planned to be deployed on a CSS-Wx System node
748   alongside other developed and COTS software, such as a database, WCS-Implementation (I), a
749   WFS-I, a WMS-I, and a service container. Altogether the collection of software components is
750   referred to as the Provider Service Adaptor (PSA) as depicted in the box in Figure 4. Interfaces
751   for data transfer vary by each geospatial web service implementation (WCS-I, WFS-I, and
752   WMS-I) and are dependent on the connecting legacy system. It is assumed that the each web
753   service implementation is resident/co-hosted on the same hardware server as the SIA, but in
754   some circumstances the SIA could be deployed on separate hardware.
755




756
757                    Figure 4 High-Level Components of a Provider Service Adaptor
758   Although Figure 4 seemingly appears to depict a hierarchy, in actuality the connecting lines
759   show only a relationship of components to each other. The service container will likely host both
760   the SIA and the geospatial web service implementations, while the database will simply be
761   hosted on the server node.
762

763   3.2.3.1.1 Connect
      R.1.2.200.100.100.100      The CSS-Wx System shall connect to a legacy provider system via the
                                 legacy provider system’s external interface.
      R.1.2.200.100.100.200      The CSS-Wx System shall attempt to retrieve the current datasets once a


                                                        32
                                connection is established to the legacy provider system. (In the case where a
                                connection is dropped, the SIA will not recover data missed during the
                                downtime. Instead, the SIA will only retrieve, either through request or the
                                data being pushed to the SIA, the most current data.)
      R.1.3.300.100.300.500.300 The CSS-Wx System shall send an alert if a connection to the legacy
                                provider system is not available. (This is a general requirement that if, for
                                any reason, the legacy system is not available, an alert should be sent.)
      R.1.3.300.100.300.500.200 The CSS-Wx System shall send an alert if there is a problem receiving data
                                from the legacy provider system.
      R.1.2.200.100.100.300     The CSS-Wx System shall be configured to request a dataset or group of
                                datasets as needed and where the capability exists from the legacy provider
                                system. (This is specified as an administrative function. If, for any reason,
                                the service maintainer requires that data be ingested or re-ingested, the SIA
                                should provide that capability. This will assist a simulation/playback
                                capability.)
      R.1.2.200.100.100.400     The CSS-Wx System shall be configured to request and process data
                                starting at a specific date and time as needed and where the capability exists
                                to make such requests from the legacy provider automation system. (This is
                                a playback capability function. It could also perform recovery if that
                                function was ever desired in the future.)

764   3.2.3.1.2 Receive
      R.1.2.200.100.100.500     The CSS-Wx System shall ingest all data as the data become available from
                                the legacy provider system.
      R.1.1.100.100.300.200     The CSS-Wx System shall poll the legacy provider system for new data at
                                configurable intervals if it is not persistently connected.
      R.1.4.100.400.100         The CSS-Wx System shall timestamp the data that it receives. (The
                                timestamps will be used to keep track of when the products were received
                                and the time that they were valid.)
      R.1.3.300.200.100.100.300 The CSS-Wx System shall log all data that it receives.

765   3.2.3.1.3 Validate Data
      R.1.4.300.100.100         The CSS-Wx System shall validate data integrity as data is received.
      R.1.4.300.100.200         The CSS-Wx System shall validate that a dataset it receives is complete.
                                (Ensure that it is a complete data product.)
      R.1.4.300.100.300         The CSS-Wx System shall request data it receives again if the data do not
                                validate, where the capability exists to make such requests from the legacy
                                system. (If the data are not valid, the SIA should attempt to retrieve the data
                                again before notifying the service owner/manager of a potential problem.
                                The capability to request to receive the data again may or may not be
                                available depending on the providing system.)
      R.1.3.300.300.100.2100    The CSS-Wx System shall send an alert if a received dataset does not
                                achieve validation.
      R.1.3.300.200.100.100.400 The CSS-Wx System shall log all data validation activities. (As data are
                                being validated, it should be noted in the SIA logs.)

766   3.2.3.1.4 Transform Data
      R.1.2.100.200.100            The CSS-Wx System shall transform non-gridded products into a WXXM
                                   format.



                                                         33
      R.1.3.300.100.300.100.100 The CSS-Wx System shall send an alert if data from the legacy provider
                                automation system cannot be transformed.
      R.1.3.300.200.100.100.600 The CSS-Wx System shall log all transformation activities. (Information
                                about the data that has been transformed will be logged including the
                                outcome, success, or failure.)
767

768   3.2.3.1.5 Transfer Data
      R.1.2.200.200.100.100     The CSS-Wx System shall transfer non-gridded data products into the CSS-
                                Wx System WFS-I via the CSS-Wx System WFS-Transaction protocol.
      R.1.2.200.200.200.100     The CSS-Wx System shall save gridded data products into the CSS-Wx
                                System WCS-I file directory.
      R.1.2.200.200.001         The CSS-Wx System shall store data being transferred from a provider
                                locally if the transfer failed because the intended geospatial web service
                                recipient was not available. (If the web services implementations are not
                                available, the data should be cached or stored in the SIA until the web
                                services implementations become available again.)
      R.4.1.100.003             The CSS-Wx System shall continue attempting to transfer the data to the
                                web services implementations until it is successful or until a new dataset
                                supersedes the current dataset. (Simply continue to try until the web
                                services implementations become available again.)
      R.1.3.300.200.100.100.700 The CSS-Wx System shall send an alert if the transfer of data is not
                                successful.
769

770        3.2.3.2 Radar Ingest Adaptor (RIA)
771   The RIA is similar to the CSS-Wx System Ingest Adaptor in that it brings data into the CSS-Wx
772   System, but the similarities end there. The RIA connects to the radar site, ingests the radar data
773   (compressing TDWR data at the time of ingest), and passes the radar data without modifying the
774   underlying, native data format.
775
      R.1.2.200.200.400.100       The CSS-Wx System shall store radar data until the radar data have
                                  expired, the radar data are refreshed, or the radar data have exceeded a
                                  configurable amount of time from product generation time up to 24 hours.
      R.1.2.1100.100.100          The CSS-Wx System shall compress TDWR data.
      R.1.2.200.200.400.200       The CSS-Wx System shall retrieve stored radar data.
      R.1.2.300.200.100         The CSS-Wx System shall publish CSS-Wx System-compressed TDWR
                                data when the CSS-Wx System receives TDWR data directly from a
                                TDWR.
      R.1.2.300.100.100         The CSS-Wx System shall publish WSR-88D data without modification,
                                when the CSS-Wx System receives WSR-88D data directly from a WSR-
                                88D.
      R.1.2.300.300.100         The CSS-Wx System shall publish CANRAD data without modification,
                                when the CSS-Wx System receives CANRAD data directly from a
                                CANRAD.
      R.1.3.300.200.100.100.900 The CSS-Wx System shall log all events of the Radar Ingest Adaptor.



                                                       34
776

777        3.2.3.3 Consumer Service Adaptor
778   A Consumer Service Adaptor is software that provides an interface between the CSS-Wx System
779   and legacy consumer automation systems. Error! Reference source not found.Figure 7 is a
780   depiction of the functions and the functional flow of the Consumer Service Adaptor.
781
782   The adaptor’s main function is to provide an interface to accept new requests from internal
783   legacy consumers, such as ad hoc queries or subscriptions for CSS-Wx System data, transform
784   those requests into functions that can interact with the CSS-Wx System’s geospatial web
785   services, and then send those queries to be processed. Upon receiving a response, the service
786   adaptor will repackage that response into a format that the legacy consumer automation system
787   can understand and then send the response to the legacy consumer automation system.
788
789   There is a one-to-one relationship with Consumer Service Adaptors and their consuming internal
790   legacy systems. In other words, for every consuming legacy system, there will be a single
791   Consumer Service Adaptor.
792
793   Below are the functional requirements for a Consumer Service Adaptor.
794
      R.4.1.100.001             The CSS-Wx System shall maintain a connection to its legacy consumer
                                system, in accordance with the CSS-Wx System-to-legacy system
                                interface requirements.
      R.1.2.1100.200.100        The CSS-Wx System shall un-compress CSS-Wx System-compressed
                                TDWR data, as needed.
      R.1.2.800.100.100         The CSS-Wx System shall reformat CF-netCDF4 formatted data into
                                specified legacy formats in accordance with the CSS-Wx System-to-
                                (legacy system) interface requirements.
      R.1.2.800.400.100         The CSS-Wx System shall reformat WXXM formatted data into
                                specified legacy formats in accordance with CSS-Wx System-to-(legacy
                                system) interface requirements.
      R.1.3.300.200.100.100.800 The CSS-Wx System shall send an alert when a request cannot be
                                satisfied.

795     3.2.4 Web Coverage Service (WCS)
796   The [Web Coverage Service Implementation Standard, version 1.1.2], developed by the OGC,
797   specifies a standard access protocol for coverage data. According to the OGC’s Reference
798   Model:
799
800      Coverage defines a data model that associates spatio-temporal positions to data values.
801      The data attributes of coverage vary across its spatio-temporal extent.
802



                                                    35
803   Coverages can be roughly defined as any type of data that include a number of attributes relevant
804   to a particular geographic location; this includes any conditions that are universally applied to a
805   geographic area. For example, a surface observation that includes measurements of air
806   temperature, humidity, and cloud ceiling may be considered a coverage. A forecast for a single
807   turbulence condition over an area might also be viewed similarly. A regularly spaced grid of
808   points of forecast icing severities is also a coverage. Irregularly spaced grids are beyond the
809   scope of the requirements, and though support for these types of coverages may be provided in
810   the future, there is no current requirement for them.
811

812        3.2.4.1 OGC Specification Implementation
      R.1.2.600.001             The CSS-Wx System WCS-I shall advertise supported coordinate
                                reference systems as part of the DescribeCoverage response. [WCS
                                Implementation Standard, version 1.1.2, Section 9.3.1.1 Table 11]
      R.1.2.200.100.200.100     The CSS-Wx System WCS-I shall archive native dataset format files for
                                15 days. (Native files are those files that are received from the provider in
                                the original provider provided format.)
      R.1.2.200.100.200.200     The CSS-Wx System WCS-I shall remove a native data file that has been
                                retained past 15 days upon request of a user with administrative privileges.
      R.1.2.200.100.200.300     The CSS-Wx System WCS-I shall retain native data files past 15 days
                                upon request of a user with administrative privileges.
      R.4.5.400.100a.100        The CSS-Wx System WCS-I shall handle version negotiation for client-
                                server interactions in accordance with [WCS Implementation Standard,
                                version 1.1.2, Section 8.2.1]
      R.4.5.400.700c.100        The CSS-Wx System WCS-I shall implement SOAP 1.2 binding
                                associated with the [WCS Implementation Standard, version 1.1.2,
                                Sections 8.2.4, 8.3.5, 9.2.4, 9.3.4, 10.2.4, 10.3.11.4, Annex E].
      R.4.5.400.100a.200        The CSS-Wx System WCS-I shall implement those portions of the [WCS
                                Implementation Standard, version 1.1.2] that include the mandatory
                                functionality of the specification and the functionality necessary to satisfy
                                the requirements contained within this document.
      R.2.5.200.200             The CSS-Wx System WCS-I shall run both on Windows and Linux
                                operating systems.
      R.1.3.100.700.300.100.100 The CSS-Wx System WCS-I shall run a diagnostic self-test upon initial
                                start-up when configured to do so.
      R.4.5.400.100a.300        The CSS-Wx System WCS-I shall be backward compatible to the previous
                                version at the web services interface/protocol level.
      R.1.3.500.200.002         The CSS-Wx System WCS-I shall store the configuration for the title of
                                coverages. [WCS Implementation Standard, version 1.1.2, Section 8.3.3.1]
      R.1.3.500.200.003         The CSS-Wx System WCS-I shall store the configuration for unique
                                identifiers for coverages.
      R.1.3.500.200.004         The CSS-Wx System WCS-I shall store the configuration for the root
                                location for the coverage data files.
      R.1.3.500.200.005         The CSS-Wx System WCS-I shall store the configuration for the HTTP
                                URL for the WCS-I instance. (That is, host, path and port – aka endpoint.)
      R.1.3.500.200.006         The CSS-Wx System WCS-I shall store the configuration for fields that
                                will be offered as part of a coverage, on a coverage-by-coverage basis.
      R.1.3.500.200.007         The CSS-Wx System WCS-I shall store the configuration for all static
                                metadata as required by the GetCapabilities and DescribeCoverage


                                                       36
                        responses.
R.1.3.500.200.008       The CSS-Wx System WCS-I shall store the configuration for the
                        advertised name of offered fields within a coverage.
R.1.3.500.200.009       The CSS-Wx System WCS-I shall store the configuration for coordinate
                        reference systems supported for a coverage.
R.1.2.200.200.200.200   The CSS-Wx System WCS-I shall store the amount of time to keep native
                        data files stored, as a configurable parameter on a per-dataset basis. (See
                        archive requirements.)
R.1.2.400.100.100.100   The CSS-Wx System WCS-I shall filter weather data by the basic
                        geometries in accordance with BoundingBox data structure, as specified in
                        [WCS Implementation Standard, version 1.1.2 Section 10.2.1.1 Table 23].
R.1.2.400.200.400.100   The CSS-Wx System WCS-I shall filter weather data by a valid time and
                        the most recently generated forecast when a product generation time is not
                        specified.
R.1.2.400.002.100       The CSS-Wx System WCS-I shall filter weather data for a set of user-
                        provided field names. (Using RangeSubset.)
R.1.2.400.200.300.100   The CSS-Wx System WCS-I shall return time series responses from
                        GetCoverage requests as described in [WCS Implementation Standard,
                        version 1.1.2, Section 10.2.1.1]
R.1.5.300.100.200       The CSS-Wx System WCS-I shall accept SOAP encoding over HTTP
                        POST for the GetCoverage request. [WCS Implementation Standard,
                        version 1.1.2, Section 10.2.4]
R.1.5.300.100.300       The CSS-Wx System WCS-I shall accept user-specified Sections
                        parameters for GetCapabilities requests. [WCS Implementation Standard,
                        version 1.1.2, Section 8.2.1]
R.1.5.300.100.400       The CSS-Wx System WCS-I shall accept Key-Value Pair encoding over
                        HTTP GET for the GetCapabilities request. [WCS Implementation
                        Standard, version 1.1.2, Section 8.2.2]
R.1.5.300.100.500       The CSS-Wx System WCS-I shall accept SOAP encoding over HTTP
                        POST for the GetCapabilities request. [WCS Implementation Standard,
                        version 1.1.2, Section 8.2.4]
R.1.5.400.100.200       The WCS shall return "application/x-netcdf" as the value for the
                        SupportedFormat attribute in the GetCapabilities and DescribeCoverage
                        responses. [WCS Implementation Standard, version 1.1.2, Section 8.3.3.2]
R.1.5.300.100.600       The CSS-Wx System WCS-I shall accept SOAP encoding over HTTP
                        POST for the DescribeCoverage request. [WCS Implementation Standard,
                        version 1.1.2, Section 9.2.4]
R.1.5.400.100.300       The CSS-Wx System WCS-I shall return a TemporalDomain for
                        DescribeCoverage responses as outlined in [WCS Implementation
                        Standard, version 1.1.2, Section 9.3.1.2 Table 12].
R.1.2.900.100.100.800   The CSS-Wx System WCS-I shall recreate the response to a previously
                        executed request, given the original parameterized request and an
                        additional parameter specifying the timestamp of when the original request
                        was executed.
R.1.5.400.100.400       The CSS-Wx System WCS-I shall return re-projected coverages according
                        to information specified in the Output data structure of the GetCoverage
                        request. [WCS Implementation Standard, version 1.1.2, Section 10.2.1.1
                        Table 24]
R.1.2.700.100.100       The CSS-Wx System WCS-I shall change the geographic resolution of
                        gridded weather data products in accordance with a user-specified



                                            37
                     resolution upon request. [WCS Implementation Standard, version 1.1.2,
                     Section 10.3.4]
R.1.2.600.002        The CSS-Wx System WCS-I shall use defined coordinate reference
                     systems for re-projection transformations. [WCS Implementation Standard,
                     version 1.1.2, Section 10.3.4]
R.1.2.600.100.100    The CSS-Wx System WCS-I shall re-project the positions of weather data
                     from parameterized Lambert Conformal map projection coordinates to
                     parameterized Lambert Azimuthal Equal-Area map projection coordinates
                     upon request. [WCS Implementation Standard, version 1.1.2, Section
                     10.3.4]
R.1.2.600.200.100    The CSS-Wx System WCS-I shall re-project the positions of weather data
                     from parameterized Lambert Conformal coordinates to parameterized
                     Latitude/Longitude map projection coordinates upon request. [WCS
                     Implementation Standard, version 1.1.2, Section 10.3.4]
R.1.2.600.300.100    The CSS-Wx System WCS-I shall re-project the positions of weather data
                     from parameterized Lambert Conformal coordinates to parameterized
                     Mercator map projection coordinates upon request. [WCS Implementation
                     Standard, version 1.1.2, Section 10.3.4]
R.1.2.600.400.100    The CSS-Wx System WCS-I shall re-project the positions of weather data
                     from parameterized Lambert Conformal coordinates to parameterized NAS
                     Projection map projection coordinates upon request. [WCS
                     Implementation Standard, version 1.1.2, Section 10.3.4]
R.1.2.600.500.100    The CSS-Wx System WCS-I shall re-project the positions of weather data
                     from parameterized Lambert Conformal coordinates to parameterized
                     Cartesian coordinates upon request. [WCS Implementation Standard,
                     version 1.1.2, Section 10.3.4]
R.1.2.600.600.100    The CSS-Wx System WCS-I shall re-project the positions of weather data
                     from parameterized Latitude/Longitude coordinates to parameterized
                     Lambert Azimuthal Equal-Area map projection coordinates upon request.
                     [WCS Implementation Standard, version 1.1.2, Section 10.3.4]
R.1.2.600.700.100    The CSS-Wx System WCS-I shall re-project the positions of weather data
                     from parameterized Latitude/Longitude coordinates to parameterized
                     Mercator map projection coordinates upon request. [WCS Implementation
                     Standard, version 1.1.2, Section 10.3.4]
R.1.2.600.800.100    The CSS-Wx System WCS-I shall re-project the positions of weather data
                     from parameterized Latitude/Longitude coordinates to parameterized NAS
                     Projection map projection coordinates upon request. [WCS
                     Implementation Standard, version 1.1.2, Section 10.3.4]
R.1.2.600.900.100    The CSS-Wx System WCS-I shall re-project the positions of weather data
                     from parameterized Latitude/Longitude coordinates to parameterized
                     Cartesian coordinates upon request. [WCS Implementation Standard,
                     version 1.1.2, Section 10.3.4]
R.1.2.600.1000.100   The CSS-Wx System WCS-I shall re-project the positions of weather data
                     from parameterized Mercator coordinates to parameterized Lambert
                     Azimuthal Equal-Area map projection coordinates upon request. [WCS
                     Implementation Standard, version 1.1.2, Section 10.3.4]
R.1.2.600.1100.100   The CSS-Wx System WCS-I shall re-project the positions of weather data
                     from parameterized Mercator coordinates to parameterized
                     Latitude/Longitude map projection coordinates upon request. [WCS
                     Implementation Standard, version 1.1.2, Section 10.3.4]



                                        38
R.1.2.600.1200.100   The CSS-Wx System WCS-I shall re-project the positions of weather data
                     from parameterized Mercator coordinates to parameterized NAS
                     Projection map projection coordinates upon request. [WCS
                     Implementation Standard, version 1.1.2, Section 10.3.4]
R.1.2.600.1400.100   The CSS-Wx System WCS-I shall re-project the positions of weather data
                     from parameterized Stereographic (including polar) coordinates to
                     parameterized Lambert Azimuthal Equal-Area map projection coordinates
                     upon request. [WCS Implementation Standard, version 1.1.2, Section
                     10.3.4]
R.1.2.600.1500.100   The CSS-Wx System WCS-I shall re-project the positions of weather data
                     from parameterized Stereographic (including polar) coordinates to
                     parameterized Latitude/Longitude map projection coordinates upon
                     request. [WCS Implementation Standard, version 1.1.2, Section 10.3.4]
R.1.2.600.1600.100   The CSS-Wx System WCS-I shall re-project the positions of weather data
                     from parameterized Stereographic (including polar) coordinates to
                     parameterized Mercator map projection coordinates upon request. [WCS
                     Implementation Standard, version 1.1.2, Section 10.3.4]
R.1.2.600.1700.100   The CSS-Wx System WCS-I shall re-project the positions of weather data
                     from parameterized Stereographic (including polar) coordinates to
                     parameterized NAS Projection map projection coordinates upon request.
                     [WCS Implementation Standard, version 1.1.2, Section 10.3.4]
R.1.2.600.1800.100   The CSS-Wx System WCS-I shall re-project the positions of weather data
                     from parameterized Stereographic (including polar) coordinates to
                     parameterized Cartesian coordinates upon request. [WCS Implementation
                     Standard, version 1.1.2, Section 10.3.4]
R.1.2.600.1900.100   The CSS-Wx System WCS-I shall re-project the positions of weather data
                     from parameterized coordinates for radar products coordinates to
                     parameterized Lambert Azimuthal Equal-Area map projection coordinates
                     upon request. [WCS Implementation Standard, version 1.1.2, Section
                     10.3.4]
R.1.2.600.2000.100   The CSS-Wx System WCS-I shall re-project the positions of weather data
                     from parameterized coordinates for radar products coordinates to
                     parameterized Latitude/Longitude map projection coordinates upon
                     request. [WCS Implementation Standard, version 1.1.2, Section 10.3.4]
R.1.2.600.2100.100   The CSS-Wx System WCS-I shall re-project the positions of weather data
                     from parameterized coordinates for radar products to parameterized
                     Mercator map projection coordinates upon request. [WCS Implementation
                     Standard, version 1.1.2, Section 10.3.4]
R.1.2.600.2200.100   The CSS-Wx System WCS-I shall re-project the positions of weather data
                     from parameterized coordinates for radar products to parameterized
                     Stereographic (including polar) map projection upon request. [WCS
                     Implementation Standard, version 1.1.2, Section 10.3.4]
R.1.2.600.2300.100   The CSS-Wx System WCS-I shall re-project the positions of weather data
                     from parameterized coordinates for radar products to parameterized NAS
                     Projection map projection coordinates upon request. [WCS
                     Implementation Standard, version 1.1.2, Section 10.3.4]
R.1.2.600.2400.100   The CSS-Wx System WCS-I shall re-project the positions of weather data
                     from parameterized coordinates for radar products coordinates to
                     parameterized Cartesian coordinates upon request. [WCS Implementation
                     Standard, version 1.1.2, Section 10.3.4]



                                        39
R.1.2.600.2500.100      The CSS-Wx System WCS-I shall re-project the positions of weather data
                        from parameterized NAS Projection coordinates to parameterized
                        Latitude/Longitude map projection coordinates upon request. [WCS
                        Implementation Standard, version 1.1.2, Section 10.3.4]
R.1.2.600.2600.100      The CSS-Wx System WCS-I shall re-project the positions of weather data
                        from parameterized NAS Projection coordinates to parameterized
                        Mercator map projection coordinates upon request. [WCS Implementation
                        Standard, version 1.1.2, Section 10.3.4]
R.1.2.600.2700.100      The CSS-Wx System WCS-I shall re-project the positions of weather data
                        from parameterized NAS Projection coordinates to parameterized
                        Cartesian coordinates upon request. [WCS Implementation Standard,
                        version 1.1.2, Section 10.3.4]
R.1.2.500.100.100.100   The CSS-Wx System WCS-I shall convert the positions of weather data
                        from spherical coordinates to NAD83 earth models/datum coordinates as
                        needed. [WCS Implementation Standard, version 1.1.2, Section 10.3.4]
R.1.2.500.100.200.100   The CSS-Wx System WCS-I shall convert the positions of weather data
                        from spherical coordinates to WGS84 earth models/datum coordinates as
                        needed. [WCS Implementation Standard, version 1.1.2, Section 10.3.4]
R.1.2.500.100.300.100   The CSS-Wx System WCS-I shall convert the positions of weather data
                        from NAD83 coordinates to spherical earth models/datum coordinates as
                        needed. [WCS Implementation Standard, version 1.1.2, Section 10.3.4]
R.1.2.500.100.400.100   The CSS-Wx System WCS-I shall convert the positions of weather data
                        from WGS84 coordinates to spherical earth models/datum coordinates as
                        needed. [WCS Implementation Standard, version 1.1.2, Section 10.3.4]
R.1.2.500.100.500.100   The CSS-Wx System WCS-I shall convert the positions of weather data
                        from NAD83 coordinates to WGS84 earth models/datum coordinates as
                        needed. [WCS Implementation Standard, version 1.1.2, Section 10.3.4]
R.1.2.500.100.600.100   The CSS-Wx System WCS-I shall convert the positions of weather data
                        from WGS84 coordinates to NAD83 earth models/datum coordinates as
                        needed. [WCS Implementation Standard, version 1.1.2, Section 10.3.4]
R.1.2.700.100.200       The CSS-Wx System WCS-I shall use "nearest neighbor" as the default
                        method of spatial interpolation. [WCS Implementation Standard, version
                        1.1.2, Sections 9.3.1.3, 10.2.1.2, Annex H]
R.1.2.900.200.100.100   The CSS-Wx System WCS-I shall read data stored in GRIB2 as a native
                        dataset format.
R.1.1.300.200.200.400   The CSS-Wx System WCS-I shall add (including metadata) offered
                        coverages. (Dynamic exposure of coverages at runtime without requiring a
                        restart is a caveat to be considered.)
R.1.1.300.100.200.700   The CSS-Wx System WCS-I shall update (including metadata) offered
                        coverages. (Dynamic exposure of coverages at runtime without requiring a
                        restart is a caveat to be considered.)
R.1.1.300.100.300.500   The CSS-Wx System WCS-I shall remove (including metadata) offered
                        coverages. (Dynamic exposure of coverages at runtime without requiring a
                        restart is a caveat to be considered.)
R.1.5.400.100.500       The CSS-Wx System WCS-I shall return Soap-With-Attachments as the
                        GetCoverage response encoding.
R.1.2.900.200.100.200   The CSS-Wx System WCS-I shall read data stored in CF-netCDF3 as a
                        native dataset format.
R.1.2.900.200.100.300   The CSS-Wx System WCS-I shall read data stored in GRIB1 as a native
                        dataset format.



                                            40
813

814       3.2.4.2 Extension to the OGC Specification
      R.1.2.500.001          The CSS-Wx System WCS-I shall advertise the Units of Measure for each
                             field within a coverage as part of the Coverage Summary Results.
      R.1.3.500.200.010      The CSS-Wx System WCS-I shall store the configuration for repeater or
                             delegator messaging patterns for the WCS-I instance on a product-by-product
                             basis.
      R.1.2.500.200.100.100 The CSS-Wx System WCS-I shall convert flight level to feet above ground
                             level, upon user request.
      R.1.2.500.200.200.100 The CSS-Wx System WCS-I shall convert flight level to feet above mean sea
                             level, upon user request.
      R.1.2.500.200.300.100 The CSS-Wx System WCS-I shall convert meters above mean sea level to
                             flight level, upon user request.
      R.1.2.500.200.400.100 The CSS-Wx System WCS-I shall convert meters above mean sea level to
                             feet above ground level, upon user request.
      R.1.2.500.200.500.100 The CSS-Wx System WCS-I shall convert meters above mean sea level to
                             feet above mean sea level, upon user request.
      R.1.2.500.200.600.100 The CSS-Wx System WCS-I shall convert feet above ground level to flight
                             level, upon user request.
      R.1.2.500.200.700.100 The CSS-Wx System WCS-I shall convert feet above ground level to feet
                             above mean sea level, upon user request.
      R.1.2.500.200.800.100 The CSS-Wx System WCS-I shall convert feet above mean sea level to flight
                             level, upon user request.
      R.1.2.500.200.900.100 The CSS-Wx System WCS-I shall convert feet above mean sea level to feet
                             above ground level, upon user request.
      R.1.2.500.200.1000.100 The CSS-Wx System WCS-I shall convert standard pressure to flight level,
                             upon user request.
      R.1.2.500.200.1100.100 The CSS-Wx System WCS-I shall convert standard pressure to feet above
                             ground level, upon user request.
      R.1.2.500.200.1200.100 The CSS-Wx System WCS-I shall convert standard pressure to feet above
                             mean sea level, upon user request.
      R.1.2.400.200.400.200 The CSS-Wx System WCS-I shall filter weather data by a valid time and a
                             product generation time.
      R.1.2.400.200.500.100 The CSS-Wx System WCS-I shall filter temporally aggregated datasets for
                             trajectory-related geometries.
      R.4.5.400.700a.100     The CSS-Wx System WCS-I shall publish notifications using Web Service
                             Notifications to indicate where new data can be found according to consumer
                             established subscriptions.
      R.1.5.600.100.400      The CSS-Wx System WCS-I shall delegate requests for data and metadata for
                             configured coverages to another WCS-I instance (i.e., ad hoc Delegator for
                             proxying data).
      R.1.5.600.100.500      The CSS-Wx System WCS-I shall subscribe to configured coverages supplied
                             by another WCS-I instance and make those coverages available to its
                             consumers. (i.e., subscription Repeater for proxying data).
      R.1.5.400.100.600      The CSS-Wx System WCS-I shall return the complete WSDL definition
                             through http://wcs-endpoint?WSDL upon request.
      R.1.5.400.100.700      The CSS-Wx System WCS-I shall return metadata in response to a
                             GetMetadata operation according to user-specified parameters and filters.
      R.1.5.400.100.800      The CSS-Wx System WCS-I shall return CF-netCDF4 formatted data as the



                                                     41
                                binary coverage data within GetCoverage responses.
      R.1.2.900.200.100.400     The CSS-Wx System WCS-I shall read data stored in CF-netCDF4 as a native
                                dataset format.

815        3.2.4.3 Additional Plug-in Functionality
816   The plug-in functionality is two-fold. There will be a plug-in API created to extend the
817   functionality of the geospatial data access services to clients that wish to “plug-in” to web
818   services and directly utilize their functionality while maintaining autonomy. The other
819   capabilities will extend the functionality of the geospatial data access services, yet they aren’t
820   considered extensions and don’t require additional descriptions and documentation.
821
      R.2.3.100.200          The CSS-Wx System WCS-I shall provide a Plug-in API to permit the
                             addition of software components (Plug-ins) such that additional processing
                             can be performed on existing products found in the CSS-Wx System WCS
                             data store.
      R.1.3.500.200.011      The CSS-Wx System WCS-I shall allow the configuration of up to (TBD)
                             Plug-ins into the service.
      R.1.5.400.100.900      The CSS-Wx System WCS-I shall permit the return of any new data products
                             produced by the Plug-in capability to the requesting client’s endpoint.
      R.1.5.300.100.700      The CSS-Wx System WCS-I shall make the entire incoming WCS XML or
                             KVP request accessible to the Plug-in component, to help minimize changes
                             to the API if the XML requests are augmented in the future.
      R.2.3.100.300          The CSS-Wx System WCS-I shall ensure that the fact that a Plug-in is
                             involved in satisfying a given data request is transparent to a requesting client.
      R.1.2.1400.100.100     The CSS-Wx System WCS-I shall quantize weather data for user-specified
                             parameters.
      R.1.2.500.200.1300.100 The CSS-Wx System WCS-I shall convert units of direction for weather data
                             between true north and magnetic north.
      R.1.2.400.300.100.100 The CSS-Wx System WCS-I shall filter for weather data above a user-
                             specified weather parameter value.
      R.1.2.400.300.200.100 The CSS-Wx System WCS-I shall filter for weather data below a user-
                             specified weather parameter value.
      R.1.2.400.300.300.100 The CSS-Wx System WCS-I shall filter for weather data equal to a user-
                             specified weather parameter value.
      R.1.2.400.300.400.100 The CSS-Wx System WCS-I shall filter for weather data between two user-
                             specified weather parameter values.
822

823     3.2.5 Web Feature Service (WFS)
824   The [OpenGIS Web Feature Service 2.0 Interface Standard] was chosen as the standard for
825   publishing feature weather data for the CSS-Wx System. According to the OGC’s Reference
826   Model:
827
828          A feature is an abstraction of a real world phenomenon. A geographic feature is a
829          feature associated with a location relative to the Earth. A digital representation of
830          the real world can be thought of as a set of features. [...] A feature is not defined


                                                        42
831          in terms of a single geometry, but rather as a conceptually meaningful object
832          within a particular information or application community, one or more of the
833          feature's properties may be geometric.[...] A feature collection is a feature that
834          represents a collection of features that have common metadata and formal
835          relationships. Collections possess all the characteristics of a feature.
836
837   The OGC WFS Implementation specification has broad geospatial applicability beyond the
838   weather domain. This allows other disciplines—such as aeronautical, environmental, and air
839   traffic information—to share data and access protocols through geospatial constructs rather than
840   through domain-specific (e.g., weather-specific) constructs.
841

842        3.2.5.1 OGC Specification Implementation
      R.1.5.300.100.1400         The CSS-Wx System WFS-I shall accept Key-Value Pair (KVP) encoding
                                 over HTTP GET for the DescribeFeature request. (KVP encoding for
                                 DescribeFeature is [OpenGIS Web Feature Service 2.0 Interface Standard,
                                 Section 9.2.3])
      R.1.5.300.100.1500         The CSS-Wx System WFS-I shall accept Key-Value Pair encoding over
                                 HTTP GET for the GetCapabilities request. (The Key-Value Pair encoding
                                 is defined in [OpenGIS Web Feature Service 2.0 Interface Standard,
                                 Section 6.2.5]. Using KVP for GetCapabilities is defined in [OpenGIS
                                 Web Feature Service 2.0 Interface Standard, Sections 6.2.5, 8.2.3].
      R.1.5.300.100.1600         The CSS-Wx System WFS-I shall accept SOAP encoding over HTTP
                                 POST for the GetCapabilities request. [OpenGIS Web Feature Service 2.0
                                 Interface Standard, Appendix A, Section 1.6]
      R.1.1.300.200.200.700      The CSS-Wx System WFS-I shall add (including metadata) offered
                                 features at runtime without requiring a restart.
      R.1.2.500.002              The CSS-Wx System WFS-I shall advertise features as GML within the
                                 interface. (The version of GML as specified by the [OpenGIS Web Feature
                                 Service 2.0 Interface Standard, Section 8.3.4])
      R.1.2.600.005              The CSS-Wx System WFS-I shall advertise supported coordinate reference
                                 systems as part of the DescribeFeature response. [OpenGIS Web Feature
                                 Service 2.0 Interface Standard, Section 7.9.2.4.4]
      R.1.2.1300.100.300         The CSS-Wx System WFS-I shall aggregate multiple weather datasets into
                                 a single dataset. [OpenGIS Web Feature Service 2.0 Interface Standard,
                                 Sections 11.3.2, 11.3.3.4, 11.3]
      R.1.2.200.100.200.600      The CSS-Wx System WFS-I shall archive feature data for 15 days.
      R.4.5.400.100b.100         The CSS-Wx System WFS-I shall be backward compatible to the previous
                                 version at the web services interface/protocol level. [OpenGIS Web
                                 Feature Service 2.0 Interface Standard, Section 6.2]
      R.1.2.500.100.300.300      The CSS-Wx System WFS-I shall convert the positions of weather data
                                 from NAD83 coordinates to spherical earth models/datum coordinates as
                                 needed.
      R.1.2.500.100.500.300      The CSS-Wx System WFS-I shall convert the positions of weather data
                                 from NAD83 coordinates to WGS84 earth models/datum coordinates as
                                 needed.
      R.1.2.500.100.100.300      The CSS-Wx System WFS-I shall convert the positions of weather data
                                 from spherical coordinates to NAD83 earth models/datum coordinates as


                                                    43
                         needed.
R.1.2.500.100.200.300    The CSS-Wx System WFS-I shall convert the positions of weather data
                         from spherical coordinates to WGS84 earth models/datum coordinates as
                         needed.
R.1.2.500.100.600.300    The CSS-Wx System WFS-I shall convert the positions of weather data
                         from WGS84 coordinates to NAD83 earth models/datum coordinates as
                         needed.
R.1.2.500.100.400.300    The CSS-Wx System WFS-I shall convert the positions of weather data
                         from WGS84 coordinates to spherical earth models/datum coordinates as
                         needed.
R.1.2.400.100.300.100    The CSS-Wx System WFS-I shall filter weather data by Geospatial Line
                         Segments. [OpenGIS Filtering Encoding 2.0 Encoding Standard]
R.1.2.400.100.100.300    The CSS-Wx System WFS-I shall filter weather data by Geospatial Points.
                         [OpenGIS Filtering Encoding 2.0 Encoding Standard]
R.1.2.400.100.100.400    The CSS-Wx System WFS-I shall filter weather data by the basic
                         geometries in accordance with BoundingBox data structure, as specified in
                         [OpenGIS Filtering Encoding 2.0 Encoding Standard].
R.1.2.400.200.200.100    The CSS-Wx System WFS-I shall filter weather data by two specified
                         times. (For example, a forecast time and a product generation time.)
                         [OpenGIS Filtering Encoding 2.0 Encoding Standard]
R.1.2.400.002.300        The CSS-Wx System WFS-I shall filter weather data for a set of user-
                         selected field names. (Includes single or multiple parameters.) [OpenGIS
                         Filtering Encoding 2.0 Encoding Standard]
R.1.2.400.100.1400.100   The CSS-Wx System WFS-I shall filter weather data for user-specified
                         trajectory-related geometries. (That is, a geospatial volume surrounding a
                         user-specified line segment, a user-specified horizontal distance, and a
                         user-specified vertical distance above and below the line segments.)
                         [OpenGIS Filtering Encoding 2.0 Encoding Standard]
R.1.2.400.100.500.100    The CSS-Wx System WFS-I shall filter weather data within a Geospatial
                         2-D Polygon. [OpenGIS Filtering Encoding 2.0 Encoding Standard]
R.1.2.400.100.600.100    The CSS-Wx System WFS-I shall filter weather data within a Geospatial
                         Circle. [OpenGIS Filtering Encoding 2.0 Encoding Standard]
R.4.5.400.100b.200       The CSS-Wx System WFS-I shall handle version negotiation as outlined in
                         the [OpenGIS Web Feature Service 2.0 Interface Standard, Section 6.2.3]
R.4.5.400.100b.300       The CSS-Wx System WFS-I shall implement the Transactional WFS,
                         Basic WFS, and Simple WFS. [OpenGIS Web Feature Service 2.0
                         Interface Standard, Appendix A, Section 1.3]
R.4.5.400.100b.400       The CSS-Wx System WFS-I shall implement those portions of the
                         [OpenGIS Web Feature Service 2.0 Interface Standard] and [OpenGIS
                         Filtering Encoding 2.0 Encoding Standard] that include the mandatory
                         functionality of the specifications and the functionality necessary to satisfy
                         the requirements contained within this document.
R.1.5.400.100.2100       The CSS-Wx System WFS-I shall output an XML document containing
                         the feature member elements for each requested feature. [OpenGIS Web
                         Feature Service 2.0 Interface Standard, Section 11.3.1]
R.1.5.400.100.2200       The CSS-Wx System WFS-I shall output an XML document that conforms
                         to a GML Application Schema, upon request. (The version of the GML
                         used will be determined by the version of the [OpenGIS Web Feature
                         Service 2.0 Interface Standard, Section 8.3.4])
R.1.2.600.006            The CSS-Wx System WFS-I shall process data using the European



                                              44
                         Petroleum Survey Group (EPSG) 4979 CRS for 3-D datasets and EPSG
                         4326 for 2-D datasets as the default CRS if no CRS is specified. [OpenGIS
                         Web Feature Service 2.0 Interface Standard, Section 7.9.2.4.5]
R.1.2.600.007            The CSS-Wx System WFS-I shall process data with a user-specified
                         coordinate reference system (CRS) described by a composite CRS in
                         URI/URL form. [OpenGIS Web Feature Service 2.0 Interface Standard,
                         Section 7.9.2.4.6]
R.1.2.900.100.100.1000   The CSS-Wx System WFS-I shall recreate the response to a previously
                         executed request, given the original parameterized request and an
                         additional parameter specifying the timestamp of when the original request
                         was executed.
R.1.1.300.100.300.700    The CSS-Wx System WFS-I shall remove (including metadata) offered
                         features at runtime without requiring a restart.
R.1.2.200.100.200.700    The CSS-Wx System WFS-I shall remove data that have been retained
                         past 15 days upon request of a user with administrative privileges.
R.1.2.600.2400.300       The CSS-Wx System WFS-I shall re-project the positions of weather data
                         from parameterized coordinates for radar products coordinates to
                         parameterized Cartesian coordinates upon request.
R.1.2.600.1900.300       The CSS-Wx System WFS-I shall re-project the positions of weather data
                         from parameterized coordinates for radar products coordinates to
                         parameterized Lambert Azimuthal Equal-Area map projection coordinates
                         upon request.
R.1.2.600.2000.300       The CSS-Wx System WFS-I shall re-project the positions of weather data
                         from parameterized coordinates for radar products coordinates to
                         parameterized Latitude/Longitude map projection coordinates upon
                         request.
R.1.2.600.2100.300       The CSS-Wx System WFS-I shall re-project the positions of weather data
                         from parameterized coordinates for radar products coordinates to
                         parameterized Mercator map projection coordinates upon request.
R.1.2.600.2300.300       The CSS-Wx System WFS-I shall re-project the positions of weather data
                         from parameterized coordinates for radar products to parameterized NAS
                         Projection map projection coordinates upon request.
R.1.2.600.2200.300       The CSS-Wx System WFS-I shall re-project the positions of weather data
                         from parameterized coordinates for radar products to parameterized
                         Stereographic (including polar) map projection upon request.
R.1.2.600.500.300        The CSS-Wx System WFS-I shall re-project the positions of weather data
                         from parameterized Lambert Conformal coordinates to parameterized
                         Cartesian coordinates upon request.
R.1.2.600.200.300        The CSS-Wx System WFS-I shall re-project the positions of weather data
                         from parameterized Lambert Conformal coordinates to parameterized
                         Latitude/Longitude map projection coordinates upon request.
R.1.2.600.300.300        The CSS-Wx System WFS-I shall re-project the positions of weather data
                         from parameterized Lambert Conformal coordinates to parameterized
                         Mercator map projection coordinates upon request.
R.1.2.600.400.300        The CSS-Wx System WFS-I shall re-project the positions of weather data
                         from parameterized Lambert Conformal coordinates to parameterized NAS
                         Projection map projection coordinates upon request.
R.1.2.600.100.300        The CSS-Wx System WFS-I shall re-project the positions of weather data
                         from parameterized Lambert Conformal map projection coordinates to
                         parameterized Lambert Azimuthal Equal-Area map projection coordinates
                         upon request.


                                             45
R.1.2.600.900.300       The CSS-Wx System WFS-I shall re-project the positions of weather data
                        from parameterized Latitude/Longitude coordinates to parameterized
                        Cartesian coordinates upon request.
R.1.2.600.600.300       The CSS-Wx System WFS-I shall re-project the positions of weather data
                        from parameterized Latitude/Longitude coordinates to parameterized
                        Lambert Azimuthal Equal-Area map projection coordinates upon request.
R.1.2.600.700.300       The CSS-Wx System WFS-I shall re-project the positions of weather data
                        from parameterized Latitude/Longitude coordinates to parameterized
                        Mercator map projection coordinates upon request.
R.1.2.600.800.300       The CSS-Wx System WFS-I shall re-project the positions of weather data
                        from parameterized Latitude/Longitude coordinates to parameterized NAS
                        Projection map projection coordinates upon request.
R.1.2.600.1000.300      The CSS-Wx System WFS-I shall re-project the positions of weather data
                        from parameterized Mercator coordinates to parameterized Lambert
                        Azimuthal Equal-Area map projection coordinates upon request.
R.1.2.600.1100.300      The CSS-Wx System WFS-I shall re-project the positions of weather data
                        from parameterized Mercator coordinates to parameterized
                        Latitude/Longitude map projection coordinates upon request.
R.1.2.600.1200.300      The CSS-Wx System WFS-I shall re-project the positions of weather data
                        from parameterized Mercator coordinates to parameterized NAS
                        Projection map projection coordinates upon request.
R.1.2.600.2700.300      The CSS-Wx System WFS-I shall re-project the positions of weather data
                        from parameterized NAS Projection coordinates to parameterized
                        Cartesian coordinates upon request.
R.1.2.600.2600.300      The CSS-Wx System WFS-I shall re-project the positions of weather data
                        from parameterized NAS Projection coordinates to parameterized
                        Latitude/Longitude map projection coordinates upon request.
R.1.2.600.2500.300      The CSS-Wx System WFS-I shall re-project the positions of weather data
                        from parameterized NAS Projection coordinates to parameterized
                        Mercator map projection coordinates upon request.
R.1.2.600.1800.300      The CSS-Wx System WFS-I shall re-project the positions of weather data
                        from parameterized Stereographic (including polar) coordinates to
                        parameterized Cartesian coordinates upon request.
R.1.2.600.1400.300      The CSS-Wx System WFS-I shall re-project the positions of weather data
                        from parameterized Stereographic (including polar) coordinates to
                        parameterized Lambert Azimuthal Equal-Area map projection coordinates
                        upon request.
R.1.2.600.1500.300      The CSS-Wx System WFS-I shall re-project the positions of weather data
                        from parameterized Stereographic (including polar) coordinates to
                        parameterized Latitude/Longitude map projection coordinates upon
                        request.
R.1.2.600.1600.300      The CSS-Wx System WFS-I shall re-project the positions of weather data
                        from parameterized Stereographic (including polar) coordinates to
                        parameterized Mercator map projection coordinates upon request.
R.1.2.600.1700.300      The CSS-Wx System WFS-I shall re-project the positions of weather data
                        from parameterized Stereographic (including polar) coordinates to
                        parameterized NAS Projection map projection coordinates upon request.
R.1.2.200.100.200.800   The CSS-Wx System WFS-I shall retain data past 15 days upon request of
                        a user with administrative privileges.
R.1.2.900.100.200.100   The CSS-Wx System WFS-I shall retrieve archived feature data, according
                        to user-specified parameters.


                                           46
      R.1.2.900.200.200.100     The CSS-Wx System WFS-I shall retrieve stored feature data, according to
                                user-specified parameters.
      R.1.3.100.700.300.100.300 The CSS-Wx System WFS-I shall run a diagnostic self-test upon initial
                                start-up when configured to do so.
      R.2.5.200.400             The CSS-Wx System WFS-I shall run on both Windows and Linux
                                operating systems.
      R.1.2.200.200.100.200     The CSS-Wx System WFS-I shall store feature data in the associated
                                WFS-I database.
      R.1.3.500.200.025         The CSS-Wx System WFS-I shall store the amount of time to keep data
                                stored, as a configuration parameter. (See archive requirements.)
      R.1.3.500.200.026         The CSS-Wx System WFS-I shall store the configuration for all metadata
                                about the WFS-I. (This includes capabilities, feature availability, interface
                                description, and the available endpoint operations of the WFS-I.)
      R.1.3.500.200.027         The CSS-Wx System WFS-I shall store the configuration for coordinate
                                reference systems supported for a feature. [OpenGIS Web Feature Service
                                2.0 Interface Standard, Section 7.6.5.5]
      R.1.3.500.200.028         The CSS-Wx System WFS-I shall store the configuration for feature data
                                relations.
      R.1.3.500.200.029         The CSS-Wx System WFS-I shall store the configuration for how offered
                                fields within a feature are advertised by the WFS-I.
      R.1.3.500.200.030         The CSS-Wx System WFS-I shall store the configuration for messaging
                                patterns for a WFS-I instance on a product-by-product basis.
      R.1.3.500.200.031         The CSS-Wx System WFS-I shall store the configuration for metadata that
                                describes endpoint operations for the web service.
      R.1.3.500.200.032         The CSS-Wx System WFS-I shall store the configuration for the location
                                of a relational database data store for storing non-gridded data.
      R.1.3.500.200.033         The CSS-Wx System WFS-I shall store the configuration for the name of
                                features.
      R.1.3.500.200.034         The CSS-Wx System WFS-I shall store the configuration for unique
                                identifiers for features.
      R.1.1.300.100.200.900     The CSS-Wx System WFS-I shall update (including metadata) offered
                                features at runtime without requiring a restart.
843

844       3.2.5.2 Extension to the OGC Specification
      R.1.5.300.100.1700        The CSS-Wx System WFS-I shall accept data as WXXM 1.1 encodings of
                                XML.
      R.1.2.500.003             The CSS-Wx System WFS-I shall advertise the Units of Measure for each
                                field within a feature as part of the Feature Summary Results.
      R.1.2.500.200.700.300     The CSS-Wx System WFS-I shall convert feet above ground level to feet
                                above mean sea level.
      R.1.2.500.200.600.300     The CSS-Wx System WFS-I shall convert feet above ground level to flight
                                level.
      R.1.2.500.200.900.300     The CSS-Wx System WFS-I shall convert feet above mean sea level to feet
                                above ground level.
      R.1.2.500.200.800.300     The CSS-Wx System WFS-I shall convert feet above mean sea level to flight
                                level.
      R.1.2.500.200.100.300     The CSS-Wx System WFS-I shall convert flight level to feet above ground
                                level.



                                                       47
      R.1.2.500.200.200.300  The CSS-Wx System WFS-I shall convert flight level to feet above mean sea
                             level.
      R.1.2.500.200.400.300 The CSS-Wx System WFS-I shall convert meters above mean sea level to feet
                             above ground level.
      R.1.2.500.200.500.300 The CSS-Wx System WFS-I shall convert meters above mean sea level to feet
                             above mean sea level.
      R.1.2.500.200.300.300 The CSS-Wx System WFS-I shall convert meters above mean sea level to
                             flight level.
      R.1.2.500.200.1100.300 The CSS-Wx System WFS-I shall convert standard pressure to feet above
                             ground level.
      R.1.2.500.200.1200.300 The CSS-Wx System WFS-I shall convert standard pressure to feet above
                             mean sea level.
      R.1.2.500.200.1000.300 The CSS-Wx System WFS-I shall convert standard pressure to flight level.
      R.1.5.600.100.900       The CSS-Wx System WFS-I shall delegate requests for data and metadata for
                              configured features to another WFS-I instance when proxying data. (That is,
                              ad hoc Delegator for proxying data).
      R.4.5.400.100b.500      The CSS-Wx System WFS-I shall implement SOAP 1.2 binding associated
                              with the [OpenGIS Web Feature Service 2.0 Interface Standard] and
                              [OpenGIS Filtering Encoding 2.0 Encoding Standard].
      R.4.5.400.100b.600      The CSS-Wx System WFS-I shall implement the WFS -Transaction protocol
                              2.0. (Allows the WFS-I to publish data to consumers.)
      R.1.5.400.100.2300      The CSS-Wx System WFS-I shall output data as efficient XML, i.e., W3C
                              EXI format, encodings of WXXM 1.1, when required.
      R.1.5.400.100.2400      The CSS-Wx System WFS-I shall output data as GZIPed XML, upon user
                              request.
      R.1.5.400.100.2500      The CSS-Wx System WFS-I shall output data as WXXM 1.1 encodings of
                              XML, when required.
      R.1.5.200.100.100.100   The CSS-Wx System WFS-I shall publish (push) filtered data as the data
                              becomes available. (an extension to the [OpenGIS Web Feature Service 2.0
                              Interface Standard])
      R.1.5.400.100.2600      The CSS-Wx System WFS-I shall return metadata in an ISO 19139 format,
                              upon request and in response to a GetMetadata operation according to user-
                              specified parameters and filters (Through an extension to the [OpenGIS Web
                              Feature Service 2.0 Interface Standard (also ISO 19142)])
      R.1.5.400.100.2700      The CSS-Wx System WFS-I shall return re-projected features according to
                              information specified in the Output data structure of the GetFeature request.
      R.1.5.400.100.2800      The CSS-Wx System WFS-I shall return the complete WSDL definition
                              through http://wfs-endpoint?WSDL.
      R.1.3.500.200.035       The CSS-Wx System WFS-I shall store the configuration for the available
                              features/datasets that will be served by the WFS-I.
      R.1.5.600.100.1000      The CSS-Wx System WFS-I shall subscribe to configured features supplied
                              by another WFS-I instance and make those features available to its consumers
                              when proxying data. (That is, subscription Repeater for proxying data).

845        3.2.5.3 Additional Plug-in Functionality
846   The plug-in functionality is two-fold. There will be a plug-in API created to extend the
847   functionality of the geospatial data access services to clients that wish to “plug-in” to web
848   services and directly utilize their functionality while maintaining autonomy. The other




                                                     48
849   capabilities will extend the functionality of the geospatial data access services, yet they aren’t
850   considered extensions and don’t require additional descriptions and documentation.
851
      R.1.3.500.200.036      The CSS-Wx System WFS-I shall allow the configuration of up to XXX
                             Plug-ins into the service.
      R.1.2.500.200.1300.300 The CSS-Wx System WFS-I shall convert units of direction for weather data
                             between true north and magnetic north.
      R.2.3.100.600          The CSS-Wx System WFS-I shall ensure that the fact that a Plug-in is
                             involved in satisfying a given data request is transparent to a requesting client.
      R.1.2.400.300.100.300 The CSS-Wx System WFS-I shall filter for weather data above a user-
                             specified weather parameter value.
      R.1.2.400.300.200.300 The CSS-Wx System WFS-I shall filter for weather data below a user-
                             specified weather parameter value.
      R.1.2.400.300.400.300 The CSS-Wx System WFS-I shall filter for weather data between two user-
                             specified weather parameter values.
      R.1.2.400.300.300.300 The CSS-Wx System WFS-I shall filter for weather data equal to a user-
                             specified weather parameter value.
      R.1.5.300.100.1800     The CSS-Wx System WFS-I shall make the entire incoming WFS XML or
                             KVP request accessible to the Plug-in component, to help minimize changes
                             to the API if the XML requests are augmented in the future.
      R.1.5.400.100.2900     The CSS-Wx System WFS-I shall permit the return of any new data products
                             produced by the Plug-in capability to the requesting client’s endpoint.
      R.2.3.100.600          The CSS-Wx System WFS-I shall provide a Plug-in API to permit the
                             addition of software components (Plug-ins) such that additional processing
                             can be performed on existing products found in the CSS-Wx System WFS-I
                             data store.
852

853     3.2.6 Web Map Service (WMS)
854   The CSS-Wx System WMS-I performs temporary and persistent storage of image file-formatted
855   weather products, data filtering, coordinate conversion, map re-projection, and query
856   management.

857        3.2.6.1 OGC Specification Implementation
      R.1.2.600.003                The CSS-Wx System WMS-I shall advertise supported coordinate
                                   reference systems as part of the GetCapabilities response.
      R.4.5.400.100c.100           The CSS-Wx System WCS-I shall implement those portions of the
                                   [OpenGIS Web Map Service Implementation Specification, version 1.3.0],
                                   that include the mandatory functionality of the specification and the
                                   functionality necessary to satisfy the requirements contained within this
                                   document.
      R.4.5.400.100c.200           The CSS-Wx System WMS-I shall handle version negotiation for client-
                                   server interactions in accordance with [OpenGIS Web Map Service
                                   Implementation Specification, version 1.3.0, Section 6.2]
      R.1.5.300.100.800            The CSS-Wx System WMS-I shall accept Key-Value Pair encoding over
                                   HTTP GET for the GetCapabilities request. [OpenGIS Web Map Service
                                   Implementation Specification, version 1.3.0, Sections 6.3, 6.3.2, 6.3.3]
      R.1.3.500.200.012            The CSS-Wx System WMS-I shall store the configuration for coordinate



                                                        49
                        reference systems supported for a product. [OpenGIS Web Map Service
                        Implementation Specification, version 1.3.0, Sections 6.7, 7.2.4.6.6,
                        7.2.4.6.7, 7.2.4.6.8, Annex B]
R.1.5.400.100.1000      The CSS-Wx System WMS-I shall return "image/png" as the value for the
                        SupportedFormat attribute in the GetCapabilities and GetFeatureInfo
                        responses upon request. (MIME extension for the PNG binary Image
                        Format.) [OpenGIS Web Map Service Implementation Specification,
                        version 1.3.0, Section 6.9.3, 7.2.3.1, 7.3.3.7]
R.1.5.400.100.1100      The CSS-Wx System WMS-I shall return "image/jpeg" as the value for the
                        SupportedFormat attribute in the GetCapabilities and GetFeatureInfo
                        responses upon request. (MIME extension for the JPG binary Image
                        Format.) [OpenGIS Web Map Service Implementation Specification,
                        version 1.3.0, Sections 6.9.3, 7.2.3.1, 7.3.3.7]
R.1.5.400.100.1200      The CSS-Wx System WMS-I shall return "image/gif" as the value for the
                        SupportedFormat attribute in the GetCapabilities and GetFeatureInfo
                        responses upon request. (MIME extension for the GIF binary Image
                        Format.) [OpenGIS Web Map Service Implementation Specification,
                        version 1.3.0, Sections 6.9.3, 7.2.3.1, 7.3.3.7]
R.1.5.400.100.1300      The CSS-Wx System WMS-I shall return "image/geotiff" as the value for
                        the SupportedFormat attribute in the GetCapabilities and GetFeatureInfo
                        responses upon request. (MIME extension for the GeoTIFF binary Image
                        Format.) [OpenGIS Web Map Service Implementation Specification,
                        version 1.3.0, Sections 6.9.3, 7.2.3.1, 7.3.3.7]
R.1.5.400.100.1400      The CSS-Wx System WMS-I shall return "application/vnd.google-
                        earth.kmz" as the value for the SupportedFormat attribute in the
                        GetCapabilities and GetFeatureInfo responses upon request. (MIME
                        extension for the compressed KML (KMZ) Format.) [OpenGIS Web Map
                        Service Implementation Specification, version 1.3.0, Sections 6.9.3,
                        7.2.3.1, 7.3.3.7]
R.1.3.500.200.013       The CSS-Wx System WMS-I shall store the configuration for the title of
                        images/maps. [OpenGIS Web Map Service Implementation Specification,
                        version 1.3.0, Section 7.2.4.2]
R.1.3.500.200.014       The CSS-Wx System WMS-I shall store the configuration for the
                        advertised name of offered fields within a product. [OpenGIS Web Map
                        Service Implementation Specification, version 1.3.0, Section 7.2.4.2]
R.1.2.400.002.200       The CSS-Wx System WMS-I shall filter weather data for a set of user-
                        provided field names. (RangeSubset.) [OpenGIS Web Map Service
                        Implementation Specification, version 1.3.0, Sections 7.2.4.2, 7.3.3.3]
R.1.3.500.200.015       The CSS-Wx System WMS-I shall store the configuration for all static
                        metadata as required by the GetCapabilities and GetMetadata responses.
                        [OpenGIS Web Map Service Implementation Specification, version 1.3.0,
                        Sections 7.2.4.3, 7.2.4.4]
R.1.3.500.200.016       The CSS-Wx System WMS-I shall store the configuration for all styles
                        supported by each product. [OpenGIS Web Map Service Implementation
                        Specification, version 1.3.0, Sections 7.2.4.5, 7.2.4.6.5]
R.1.2.900.200.400.100   The CSS-Wx System WMS-I shall create an image/map with a user
                        specified background color upon request and in accordance with the
                        [OpenGIS Web Map Service Implementation Specification, version 1.3.0
                        sections 7.3.3.10, 7.3.2 Table 8]
R.1.2.900.200.400.200   The CSS-Wx System WMS-I shall create an image/map with a transparent
                        background upon request and in accordance with the [OpenGIS Web Map


                                           50
                        Service Implementation Specification, version 1.3.0 sections 7.3.3.9, 7.3.2
                        Table 8]
R.1.1.300.200.200.500   The CSS-Wx System WMS-I shall advertise the styles available for each
                        product on a product by product basis. (GetCapabilities.) [OpenGIS Web
                        Map Service Implementation Specification, version 1.3.0, Section 7.3.3.4]
R.1.2.400.100.100.200   The CSS-Wx System WMS-I shall filter weather data by the basic
                        geometries in accordance with BoundingBox data structure, as specified in
                        [OpenGIS Web Map Service Implementation Specification, version 1.3.0
                        Sections 7.3.3.5, 7.3.3.6]
R.1.2.700.100.300       The CSS-Wx System WCS-I shall change the geographic resolution of
                        gridded weather data products in accordance with a user-specified
                        resolution upon request. [OpenGIS Web Map Service Implementation
                        Specification, version 1.3.0, Sections 7.3.3.5, 7.3.3.6, 7.3.5]
R.1.2.600.004           The CSS-Wx System WMS-I shall use defined coordinate reference
                        systems for re-projection transformations. [OpenGIS Web Map Service
                        Implementation Specification, version 1.3.0, Sections 7.3.3.5, 7.3.3.6,
                        7.3.5]
R.1.2.600.100.200       The CSS-Wx System WMS-I shall re-project the positions of weather data
                        from parameterized Lambert Conformal map projection coordinates to
                        parameterized Lambert Azimuthal Equal-Area map projection coordinates
                        upon request. [OpenGIS Web Map Service Implementation Specification,
                        version 1.3.0, Sections 7.3.3.5, 7.3.3.6, 7.3.5]
R.1.2.600.200.200       The CSS-Wx System WMS-I shall re-project the positions of weather data
                        from parameterized Lambert Conformal coordinates to parameterized
                        Latitude/Longitude map projection coordinates upon request. [OpenGIS
                        Web Map Service Implementation Specification, version 1.3.0, Sections
                        7.3.3.5, 7.3.3.6, 7.3.5]
R.1.2.600.300.200       The CSS-Wx System WMS-I shall re-project the positions of weather data
                        from parameterized Lambert Conformal coordinates to parameterized
                        Mercator map projection coordinates upon request. [OpenGIS Web Map
                        Service Implementation Specification, version 1.3.0, Sections 7.3.3.5,
                        7.3.3.6, 7.3.5]
R.1.2.600.400.200       The CSS-Wx System WMS-I shall re-project the positions of weather data
                        from parameterized Lambert Conformal coordinates to parameterized NAS
                        Projection map projection coordinates upon request. [OpenGIS Web Map
                        Service Implementation Specification, version 1.3.0, Sections 7.3.3.5,
                        7.3.3.6, 7.3.5]
R.1.2.600.500.200       The CSS-Wx System WMS-I shall re-project the positions of weather data
                        from parameterized Lambert Conformal coordinates to parameterized
                        Cartesian coordinates upon request. [OpenGIS Web Map Service
                        Implementation Specification, version 1.3.0, Sections 7.3.3.5, 7.3.3.6,
                        7.3.5]
R.1.2.600.600.200       The CSS-Wx System WMS-I shall re-project the positions of weather data
                        from parameterized Latitude/Longitude coordinates to parameterized
                        Lambert Azimuthal Equal-Area map projection coordinates upon request.
                        [OpenGIS Web Map Service Implementation Specification, version 1.3.0,
                        Sections 7.3.3.5, 7.3.3.6, 7.3.5]
R.1.2.600.700.200       The CSS-Wx System WMS-I shall re-project the positions of weather data
                        from parameterized Latitude/Longitude coordinates to parameterized
                        Mercator map projection coordinates upon request. [OpenGIS Web Map
                        Service Implementation Specification, version 1.3.0, Sections 7.3.3.5,


                                            51
                     7.3.3.6, 7.3.5]
R.1.2.600.800.200    The CSS-Wx System WMS-I shall re-project the positions of weather data
                     from parameterized Latitude/Longitude coordinates to parameterized NAS
                     Projection map projection coordinates upon request. [OpenGIS Web Map
                     Service Implementation Specification, version 1.3.0, Sections 7.3.3.5,
                     7.3.3.6, 7.3.5]
R.1.2.600.900.200    The CSS-Wx System WMS-I shall re-project the positions of weather data
                     from parameterized Latitude/Longitude coordinates to parameterized
                     Cartesian coordinates upon request. [OpenGIS Web Map Service
                     Implementation Specification, version 1.3.0, Sections 7.3.3.5, 7.3.3.6,
                     7.3.5]
R.1.2.600.1000.200   The CSS-Wx System WMS-I shall re-project the positions of weather data
                     from parameterized Mercator coordinates to parameterized Lambert
                     Azimuthal Equal-Area map projection coordinates upon request.
                     [OpenGIS Web Map Service Implementation Specification, version 1.3.0,
                     Sections 7.3.3.5, 7.3.3.6, 7.3.5]
R.1.2.600.1100.200   The CSS-Wx System WMS-I shall re-project the positions of weather data
                     from parameterized Mercator coordinates to parameterized
                     Latitude/Longitude map projection coordinates upon request. [OpenGIS
                     Web Map Service Implementation Specification, version 1.3.0, Sections
                     7.3.3.5, 7.3.3.6, 7.3.5]
R.1.2.600.1200.200   The CSS-Wx System WMS-I shall re-project the positions of weather data
                     from parameterized Mercator coordinates to parameterized NAS
                     Projection map projection coordinates upon request. [OpenGIS Web Map
                     Service Implementation Specification, version 1.3.0, Sections 7.3.3.5,
                     7.3.3.6, 7.3.5]
R.1.2.600.1400.200   The CSS-Wx System WMS-I shall re-project the positions of weather data
                     from parameterized Stereographic (including polar) coordinates to
                     parameterized Lambert Azimuthal Equal-Area map projection coordinates
                     upon request. [OpenGIS Web Map Service Implementation Specification,
                     version 1.3.0, Sections 7.3.3.5, 7.3.3.6, 7.3.5]
R.1.2.600.1500.200   The CSS-Wx System WMS-I shall re-project the positions of weather data
                     from parameterized Stereographic (including polar) coordinates to
                     parameterized Latitude/Longitude map projection coordinates upon
                     request. [OpenGIS Web Map Service Implementation Specification,
                     version 1.3.0, Sections 7.3.3.5, 7.3.3.6, 7.3.5]
R.1.2.600.1600.200   The CSS-Wx System WMS-I shall re-project the positions of weather data
                     from parameterized Stereographic (including polar) coordinates to
                     parameterized Mercator map projection coordinates upon request.
                     [OpenGIS Web Map Service Implementation Specification, version 1.3.0,
                     Sections 7.3.3.5, 7.3.3.6, 7.3.5]
R.1.2.600.1700.200   The CSS-Wx System WMS-I shall re-project the positions of weather data
                     from parameterized Stereographic (including polar) coordinates to
                     parameterized NAS Projection map projection coordinates upon request.
                     [OpenGIS Web Map Service Implementation Specification, version 1.3.0,
                     Sections 7.3.3.5, 7.3.3.6, 7.3.5]
R.1.2.600.1800.200   The CSS-Wx System WMS-I shall re-project the positions of weather data
                     from parameterized Stereographic (including polar) coordinates to
                     parameterized Cartesian coordinates upon request. [OpenGIS Web Map
                     Service Implementation Specification, version 1.3.0, Sections 7.3.3.5,



                                        52
                        7.3.3.6, 7.3.5]
R.1.2.600.1900.200      The CSS-Wx System WMS-I shall re-project the positions of weather data
                        from parameterized coordinates for radar products to parameterized
                        Lambert Azimuthal Equal-Area map projection coordinates upon request.
                        [OpenGIS Web Map Service Implementation Specification, version 1.3.0,
                        Sections 7.3.3.5, 7.3.3.6, 7.3.5]
R.1.2.600.2000.200      The CSS-Wx System WMS-I shall re-project the positions of weather data
                        from parameterized coordinates for radar products to parameterized
                        Latitude/Longitude map projection coordinates upon request. [OpenGIS
                        Web Map Service Implementation Specification, version 1.3.0, Sections
                        7.3.3.5, 7.3.3.6, 7.3.5]
R.1.2.600.2100.200      The CSS-Wx System WMS-I shall re-project the positions of weather data
                        from parameterized coordinates for radar products to parameterized
                        Mercator map projection coordinates upon request. [OpenGIS Web Map
                        Service Implementation Specification, version 1.3.0, Sections 7.3.3.5,
                        7.3.3.6, 7.3.5]
R.1.2.600.2200.200      The CSS-Wx System WMS-I shall re-project the positions of weather data
                        from parameterized coordinates for radar products to parameterized
                        Stereographic (including polar) map projection upon request. [OpenGIS
                        Web Map Service Implementation Specification, version 1.3.0, Sections
                        7.3.3.5, 7.3.3.6, 7.3.5]
R.1.2.600.2300.200      The CSS-Wx System WMS-I shall re-project the positions of weather data
                        from parameterized coordinates for radar products to parameterized NAS
                        Projection map projection coordinates upon request. [OpenGIS Web Map
                        Service Implementation Specification, version 1.3.0, Sections 7.3.3.5,
                        7.3.3.6, 7.3.5]
R.1.2.600.2400.200      The CSS-Wx System WMS-I shall re-project the positions of weather data
                        from parameterized coordinates for radar products to parameterized
                        Cartesian coordinates upon request. [OpenGIS Web Map Service
                        Implementation Specification, version 1.3.0, Sections 7.3.3.5, 7.3.3.6,
                        7.3.5]
R.1.2.600.2500.200      The CSS-Wx System WMS-I shall re-project the positions of weather data
                        from parameterized NAS Projection coordinates to parameterized
                        Latitude/Longitude map projection coordinates upon request. [OpenGIS
                        Web Map Service Implementation Specification, version 1.3.0, Sections
                        7.3.3.5, 7.3.3.6, 7.3.5]
R.1.2.600.2600.200      The CSS-Wx System WMS-I shall re-project the positions of weather data
                        from parameterized NAS Projection coordinates to parameterized
                        Mercator map projection coordinates upon request. [OpenGIS Web Map
                        Service Implementation Specification, version 1.3.0, Sections 7.3.3.5,
                        7.3.3.6, 7.3.5]
R.1.2.600.2700.200      The CSS-Wx System WMS-I shall re-project the positions of weather data
                        from parameterized NAS Projection coordinates to parameterized
                        Cartesian coordinates upon request. [OpenGIS Web Map Service
                        Implementation Specification, version 1.3.0, Sections 7.3.3.5, 7.3.3.6,
                        7.3.5]
R.1.2.500.100.100.200   The CSS-Wx System WMS-I shall convert the positions of weather data
                        from spherical coordinates to NAD83 earth models/datum coordinates as
                        needed. [OpenGIS Web Map Service Implementation Specification,
                        version 1.3.0, Sections 7.3.3.5, 7.3.3.6, 7.3.5]



                                           53
R.1.2.500.100.200.200     The CSS-Wx System WMS-I shall convert the positions of weather data
                          from spherical coordinates to WGS84 earth models/datum coordinates as
                          needed. [OpenGIS Web Map Service Implementation Specification,
                          version 1.3.0, Sections 7.3.3.5, 7.3.3.6, 7.3.5]
R.1.2.500.100.300.200     The CSS-Wx System WMS-I shall convert the positions of weather data
                          from NAD83 coordinates to spherical earth models/datum coordinates as
                          needed. [OpenGIS Web Map Service Implementation Specification,
                          version 1.3.0, Sections 7.3.3.5, 7.3.3.6, 7.3.5]
R.1.2.500.100.400.200     The CSS-Wx System WMS-I shall convert the positions of weather data
                          from WGS84 coordinates to spherical earth models/datum coordinates as
                          needed. [OpenGIS Web Map Service Implementation Specification,
                          version 1.3.0, Sections 7.3.3.5, 7.3.3.6, 7.3.5]
R.1.2.500.100.500.200     The CSS-Wx System WMS-I shall convert the positions of weather data
                          from NAD83 coordinates to WGS84 earth models/datum coordinates as
                          needed. [OpenGIS Web Map Service Implementation Specification,
                          version 1.3.0, Sections 7.3.3.5, 7.3.3.6, 7.3.5]
R.1.2.500.100.600.200     The CSS-Wx System WMS-I shall convert the positions of weather data
                          from WGS84 coordinates to NAD83 earth models/datum coordinates as
                          needed. [OpenGIS Web Map Service Implementation Specification,
                          version 1.3.0, Sections 7.3.3.5, 7.3.3.6, 7.3.5]
R.1.5.400.100.1500        The CSS-Wx System WMS-I shall return re-projected images/maps
                          according to information specified in the Output data structure of the
                          GetMap request. [OpenGIS Web Map Service Implementation
                          Specification, version 1.3.0, Section 7.3.5]
R.1.2.400.200.400.300     The CSS-Wx System WMS-I shall filter weather data by a valid time and
                          the most recently generated forecast when a product generation time is not
                          specified. [OpenGIS Web Map Service Implementation Specification,
                          version 1.3.0, Annex C]
R.1.2.400.200.300.200     The CSS-Wx System WMS-I shall return time series responses from
                          GetMap requests as described in [OpenGIS Web Map Service
                          Implementation Specification, version 1.3.0, Annex C.3.4, C.3.5]
R.1.2.700.100.400         The CSS-Wx System WMS-I shall use "nearest neighbor" as the default
                          method of spatial interpolation. [OpenGIS Web Map Service
                          Implementation Specification, version 1.3.0, Annex C.4.3]
R.1.2.200.100.200.400     The CSS-Wx System WMS-I shall retain native data files past 15 days
                          upon request of a user with administrative privileges.
R.1.2.200.100.200.500     The CSS-Wx System WMS-I shall remove a native data file that has been
                          retained past 15 days upon request of a user with administrative privileges.
R.2.5.200.300             The CSS-Wx System WMS-I shall run on both Windows and Linux
                          operating systems.
R.1.3.100.700.300.100.200 The CSS-Wx System WMS-I shall run a diagnostic self-test upon initial
                          start-up when configured to do so.
R.4.5.400.100c.300        The CSS-Wx System WMS-I shall be backward compatible to the
                          previous version at the web services interface/protocol level.
R.1.3.500.200.017         The CSS-Wx System WMS-I shall store the configuration for unique
                          identifiers for images/maps.
R.1.3.500.200.018         The CSS-Wx System WMS-I shall store the configuration for the root
                          location for the data files. (The location may be the same as the WCS-I
                          storage.)
R.1.3.500.200.019         The CSS-Wx System WMS-I shall store the configuration for the HTTP
                          URL for the WMS-I instance. (That is, host, path and port – aka endpoint.)


                                                 54
R.1.3.500.200.020       The CSS-Wx System WMS-I shall store the configuration for fields that
                        will be offered as part of a product, on a product-by-product basis.
R.1.3.500.200.021       The CSS-Wx System WMS-I shall store the configuration for all style
                        information required to generate images from a WFS-I dataset.
R.1.3.500.200.022       The CSS-Wx System WMS-I shall store the amount of time to keep native
                        data files stored, as a configuration parameter. (See archive requirements.)
R.1.2.1300.100.100      The CSS-Wx System WMS-I shall aggregate metadata from the WCS-I
                        GetCapabilities response.
R.1.2.1300.100.200      The CSS-Wx System WMS-I shall aggregate metadata from the WFS-I
                        GetCapabilities response.
R.1.5.300.100.900       The CSS-Wx System WMS-I shall accept user-specified Section
                        parameters for GetCapabilities requests.
R.1.5.600.100.600       The CSS-Wx System WMS-I shall request a dataset from a non-local
                        WCS-I instance, as configured and upon request. (Non-local assumes that
                        the WMS-I will read the data store of any local WCS-I instance and not
                        make a request to the WCS-I instance.)
R.1.5.100.100.400       The CSS-Wx System WMS-I shall subscribe to a dataset from a non-local
                        WCS-I instance, as configured and/or upon subscription request. (Non-
                        local assumes that the WMS-I will read the data store of any local WCS-I
                        instance and not make a request of it.)
R.1.5.300.100.1000      The CSS-Wx System WMS-I shall request metadata from the WCS-I using
                        the GetCapabilities request.
R.1.5.300.100.1100      The CSS-Wx System WMS-I shall request a dataset from a WFS-I
                        instance, as configured and upon request. (The WMS- I may or may not be
                        collocated with the WMS-I instance.)
R.1.5.100.100.500       The CSS-Wx System WMS-I shall subscribe to a dataset from a WFS-I
                        instance, as configured and/or upon subscription request. (The CSS-Wx
                        System WMS-I may or may not be collocated with the WMS-I instance.)
R.1.5.300.100.1200      The CSS-Wx System WMS-I shall request metadata from a WFS-I using
                        the GetCapabilities request.
R.1.5.400.100.1700      The CSS-Wx System WMS-I shall return the complete WSDL definition
                        through http://WMS-endpoint?WSDL upon request.
R.1.2.900.100.100.900   The CSS-Wx System WMS-I shall recreate the response to a previously
                        executed request, given the original parameterized request and an
                        additional parameter specifying the timestamp of when the original request
                        was executed.
R.1.1.300.200.200.600   The CSS-Wx System WMS-I shall add (including metadata) offered
                        images/maps. (Dynamic exposure of images/maps at runtime without
                        requiring a restart is a caveat to be considered.)
R.1.1.300.100.200.800   The CSS-Wx System WMS-I shall remove (including metadata) offered
                        images/maps. (Dynamic exposure of images/maps at runtime without
                        requiring a restart is a caveat to be considered.)
R.1.1.300.100.300.600   The CSS-Wx System WMS-I shall update (including metadata) offered
                        images/maps. (Dynamic exposure of images/maps at runtime without
                        requiring a restart is a caveat to be considered.)
R.1.2.900.200.100.500   The CSS-Wx System WMS-I shall read data stored in CF-netCDF4 as a
                        native dataset format.
R.1.2.900.200.100.600   The CSS-Wx System WMS-I shall read data stored in CF-netCDF3 as a
                        native dataset format.
R.1.2.900.200.100.700   The CSS-Wx System WMS-I shall read data stored in GRIB1 as a native
                        dataset format.


                                             55
      R.1.2.900.200.100.800      The CSS-Wx System WMS-I shall read data stored in GRIB2 as a native
                                 dataset format.
      R.1.2.900.200.300.100      The CSS-Wx System WMS-I shall read data stored in GeoTiff as a native
                                 dataset format.
      R.1.5.400.100.1800         The CSS-Wx System WMS-I shall apply different styles to product upon
                                 request.

858       3.2.6.2 Extension to the OGC Specification
      R.1.3.500.200.023      The CSS-Wx System WMS-I shall store the configuration for repeater or
                             delegator messaging patterns for the WMS-I instance on a product-by-product
                             basis.
      R.1.2.500.200.100.200 The CSS-Wx System WMS-I shall convert flight level to feet above ground
                             level as needed.
      R.1.2.500.200.200.200 The CSS-Wx System WMS-I shall convert flight level to feet above mean sea
                             level as needed.
      R.1.2.500.200.300.200 The CSS-Wx System WMS-I shall convert meters above mean sea level to
                             flight level as needed.
      R.1.2.500.200.400.200 The CSS-Wx System WMS-I shall convert meters above mean sea level to
                             feet above ground level as needed.
      R.1.2.500.200.500.200 The CSS-Wx System WMS-I shall convert meters above mean sea level to
                             feet above mean sea level as needed.
      R.1.2.500.200.600.200 The CSS-Wx System WMS-I shall convert feet above ground level to flight
                             level as needed.
      R.1.2.500.200.700.200 The CSS-Wx System WMS-I shall convert feet above ground level to feet
                             above mean sea level as needed.
      R.1.2.500.200.800.200 The CSS-Wx System WMS-I shall convert feet above mean sea level to flight
                             level as needed.
      R.1.2.500.200.900.200 The CSS-Wx System WMS-I shall convert feet above mean sea level to feet
                             above ground level as needed.
      R.1.2.500.200.1000.200 The CSS-Wx System WMS-I shall convert standard pressure to flight level as
                             needed.
      R.1.2.500.200.1100.200 The CSS-Wx System WMS-I shall convert standard pressure to feet above
                             ground level as needed.
      R.1.2.500.200.1200.200 The CSS-Wx System WMS-I shall convert standard pressure to feet above
                             mean sea level as needed.
      R.1.2.400.200.500.200 The CSS-Wx System WMS-I shall filter temporally aggregated datasets for
                             trajectory-related geometries.
      R.1.5.600.100.700      The CSS-Wx System WMS-I shall delegate requests for data and metadata for
                             configured images/maps to another WMS-I instance. (That is, Delegator.)
      R.1.5.600.100.800      The CSS-Wx System WMS-I shall subscribe to configured images/maps
                             supplied by another WMS-I instance and make those images/maps available
                             to its consumers. (That is, Repeater.)
      R.4.5.400.700a.200     The CSS-Wx System WMS-I shall publish notifications using Web Service
                             Notifications to indicate where new data can be found according to consumer
                             established subscriptions.
      R.1.5.400.100.1600     The CSS-Wx System WMS-I shall return metadata in response to a
                             GetMetadata operation according to user-specified parameters and filters.
      R.1.5.400.100.1900     The CSS-Wx System WMS-I shall return a TemporalDomain for
                             GetFeatureInfo responses as outlined in WSDD Section TBD.




                                                     56
859        3.2.6.3 Additional Plug-in Functionality
860   The plug-in functionality is two-fold. There will be a plug-in API created to extend the
861   functionality of the geospatial data access services to clients that wish to “plug-in” to web
862   services and directly utilize their functionality while maintaining autonomy. The other
863   capabilities will extend the functionality of the geospatial data access services, yet they aren’t
864   considered extensions and don’t require additional descriptions and documentation.
865
      R.1.2.1400.100.200     The CSS-Wx System WMS-I shall quantize weather data for user-specified
                             parameters.
      R.2.3.100.400          The CSS-Wx System WMS-I shall provide a Plug-in API to permit the
                             addition of software components (Plug-ins) such that additional processing
                             can be performed on existing products found in the CSS-Wx System WMS
                             data store.
      R.1.3.500.200.024      The CSS-Wx System WMS-I shall allow the configuration of up to XXX
                             Plug-ins into the service.
      R.1.5.400.100.2000     The CSS-Wx System WMS-I shall permit the return of any new data products
                             produced by the Plug-in capability to the requesting client’s endpoint.
      R.1.5.300.100.1300     The CSS-Wx System WMS-I shall make the entire incoming WMS XML or
                             KVP request accessible to the Plug-in component, to help minimize changes
                             to the API if the XML requests are augmented in the future.
      R.2.3.100.500          The CSS-Wx System WMS-I shall ensure that the fact that a Plug-in is
                             involved in satisfying a given data request is transparent to a requesting client.
      R.1.2.500.200.1300.200 The CSS-Wx System WMS-I shall convert units of direction for weather data
                             between true north and magnetic north.
      R.1.2.400.300.100.200 The CSS-Wx System WMS-I shall filter for weather data above a user-
                             specified weather parameter value.
      R.1.2.400.300.200.200 The CSS-Wx System WMS-I shall filter for weather data below a user-
                             specified weather parameter value.
      R.1.2.400.300.300.200 The CSS-Wx System WMS-I shall filter for weather data equal to a user-
                             specified weather parameter value.
      R.1.2.400.300.400.200 The CSS-Wx System WMS-I shall filter for weather data between two user-
                             specified weather parameter values.
866

867     3.2.7 Complex Query Service
868   The Complex Query Service (CQS) is envisioned as additional, higher-level service of the CSS-
869   Wx System that will allow for querying multiple data products, types, and formats with a single
870   query and allow for that query to yield a single response. It is an access point to the CSS-Wx
871   System where consumers can send a single query to request multiple products and multiple
872   product types that are aggregated and returned to the consumer as a single response.
873
874   The functional requirements for the Complex Query Service are as follows:
875
       R.1.2.1000.100.100 The CSS-Wx System shall process Complex Retrieval requests.




                                                        57
       R.1.2.1000.100.200 The CSS-Wx System shall construct multiple, simple queries for weather data
                          from a single complex request for weather data.
       R.1.2.1000.100.300 The CSS-Wx System shall send queries for weather data to the appropriate data
                          access service (i.e., WCS, WFS, or WMS) for data retrieval.
       R.1.2.1000.100.400 The CSS-Wx System shall assemble the responses to a complex request in a single
                          response.
       R.1.2.1000.100.500 The CSS-Wx System shall pass along simple responses for data without
                          modifying the response.
       R.1.2.1000.100.600 The CSS-Wx System shall send the consumer an error if one or all of the
                          responses to the request cannot be satisfied.
       R.1.2.1000.100.700 The CSS-Wx System shall timeout the operation of a complex request after a user-
                          specified amount of time has been exceeded.

876

877     3.2.8 Weather Alert Service
878   The CSS-Wx System Weather Alert Service stores user-specified weather parameter thresholds,
879   monitors the parameters within the context of the weather products, and generates an alert when
880   the thresholds are crossed.
881
       R.1.2.1200.100.100 The CSS-Wx System shall store subscriber-specified weather parameter threshold
                          values.
       R.1.2.1200.200.200 The CSS-Wx System shall publish a weather alert to the subscriber when a
                          subscriber-specified weather threshold parameter is crossed


882     3.2.9 Dynamic Load Handling
883   If a combination of load-sharing and fail-over strategy is not sufficient to service the full demand
884   on CSS-Wx System resources, then the CSS-Wx System will implement a load-shedding
885   strategy (graceful degradation) by servicing higher-priority requests while neglecting lower
886   priority requests until such time as all higher priority requests have been serviced. The CSS-Wx
887   System Web Services Dynamic Load Handling provides the ability for the CSS-Wx System to
888   gracefully degrade when under stress (due to excess load or faulted components), based on QoS
889   parameters associated with products and/or consumers.
890
       R.1.5.700.100.200 The CSS-Wx System shall process requests for weather data in accordance with
                         QoS parameters in the event of an overload condition. (That is, reply to all requests
                         that have a higher QoS before replying to queries with a lower QoS.)


891     3.2.10 Query Optimization
892
       R.1.2.1000.100.800 The CSS-Wx System shall combine overlapping queries from multiple service
                          consumers into a single query to minimize the number of requests to a CSS-Wx
                          System web service. (WCS-I, WFS-I, WMS-I).




                                                         58
893

894      3.2.11 System Administration and Maintenance Software
895   The CSS-Wx System Management software allows users with CSS-Wx System administration
896   and maintenance privileges to monitor CSS-Wx System performance and change a CSS-Wx
897   System Node configuration by applying control commands and modifying local and system-wide
898   adaptation parameters. CSS-Wx System Management workstations are used to connect to local
899   CSS-Wx System Nodes. Users with administrative and maintenance privileges also have remote
900   access via network connectivity to perform CSS-Wx System monitor and control procedures,
901   select and display items that are monitored, and select and print logs and reports .
902
       R.2.2.200.200.100 The CSS-Wx System shall execute administrative and maintenance commands
                         entered via a system management user interface.
       R.1.3.100.001     The CSS-Wx System shall display items that are monitored by the CSS-Wx System
                         upon a user’s request.
       R.5.1.1700.1200   The CSS-Wx System shall print items that are monitored by the CSS-Wx System
                         upon a user’s request.
903   3.3   Performance Requirements
904   This section provides the quality factors requirements of the CSS-Wx System including the
905   reliability, maintainability, availability, extensibility, scalability, portability, interchangeability,
906   latency/response time, response times for ad hoc queries, registry/repository performance,
907   quality of service levels, and reserve capacity.

908      3.3.1 Reliability
909   The CSS-Wx System is a repairable system that must operate continuously; therefore, reliability
910   is expressed as the probability that the CSS-Wx System will perform a required function under
911   specific conditions for a stated period of time. CSS-Wx is expressed as the raw Mean Time
912   Between Failures (MTBF), in hours.
913
914   A CSS-Wx System failure places a CSS-Wx Node out of service and in need of repair. Failures
915   which occur that can be left as is or maintained in an unrepaired condition, and do not place the
916   Node out of service, are not considered failures under this definition. CSS-Wx System failure
917   conditions exclude the following:
918          a. Improper or incomplete operation of equipment and facilities external to the CSS-Wx
919          System;
920          b. Data recording and playback functions.
921
       R.2.9.100.100 The CSS-Wx System Mean Time Between Failure for a Node shall be greater than or
                     equal to 5000 hours.

922      3.3.2 Maintainability




                                                        59
923   The CSS-Wx characteristic of design and installation that is expressed as the probability that an
924   item will be retained in, or restored to a specified condition within a given period of time, when
925   the maintenance is performed in accordance with prescribed procedures and resources.

926            3.3.2.1   Mean Time to Repair
927   The Mean Time to Repair period includes all time necessary to localize, repair, test, and restore a failed
928   system/unit to normal operating conditions.
929
          R.2.9.200.100 The CSS-Wx System Mean Time to Repair shall be less than or equal to 0.5 hours.2

930            3.3.2.2 Preventive Maintenance
          R.2.9.300.100 A CSS-Wx System Node shall require no more than four (4) annual preventive
                        maintenance actions that cause disruptions to service by requiring a system restart.

931           3.3.2.3 Corrective Maintenance
          R.2.9.300.200 The CSS-Wx System shall be designed so that corrective maintenance actions will not
                           degrade the inherent availability of the CSS-Wx System.

932        3.3.3 Availability
933   The CSS-Wx System Node availability is measured as: Availability = MTBF + MTTR/MTBF in
934   accordance with [FAA-HDBK-006A].
935
          R.2.9.300.300 The CSS-Wx System shall have an inherent availability of 0.9999.

936        3.3.4 Extensibility
937   The CSS-Wx System is designed to include mechanisms for expanding and/or enhancing the
938   CSS-Wx System with new capabilities without having to make major changes to the CSS-Wx
939   System infrastructure.
940
          R.2.3.100.100 The CSS-Wx System shall accommodate significant extensions of its capabilities
                        without significant changes in basic software architecture.

941        3.3.5 Scalability
942   The ability of the CSS-Wx System to handle increasing and/or decreasing amounts of work
943   performed without degrading operational performance of the CSS-Wx System.

944            3.3.5.1 Horizontal Scalability
945   Additional CSS-Wx System Nodes can be added to accommodate additional load.
946

      2
          See FAA-HDBK-006A for additional MTTR guidance.




                                                            60
      R.2.4.100.100.100 The CSS-Wx System shall scale to accommodate at least 100% increase in the total
                        capacity of the CSS-Wx System above the baseline configuration established at
                        Initial Operating Capability.
      R.2.4.100.200.100 The CSS-Wx System shall scale to accommodate at least 10% increase in the
                        number of Consumer Service Adapters above the baseline configuration established
                        at Initial Operating Capability.

947        3.3.5.2 Vertical Scalability
948   A CSS-Wx System Node can be reconfigured with components such as processors, random
949   access memory, and storage to change work performed and still meets operational requirements.
950
      R.2.4.200.100.100    A CSS-Wx System Node shall scale to accommodate greater than or equal
                           to 150% increase in processor capacity above the baseline configuration
                           established for Initial Operating Capability.
      R.2.4.200.200.100    A CSS-Wx System Node shall scale to accommodate greater than or equal
                           to 150% increase of total random access memory above the baseline
                           configuration established for Initial Operating Capability.
      R.2.4.200.300.100    A CSS-Wx System Node shall scale to accommodate greater than or equal
                           to 150% increase in storage above the baseline configuration established for
                           Initial Operating Capability.

951     3.3.6 Portability
952   The CSS-Wx System portability of application software may be achieved by installing program
953   files to the next operating system upgrade or reverting back to the previous operating system
954   revision located on the same hardware platform. When porting back or forth between operating
955   system revisions functional and performance requirements should not be adversely impacted.
956
      R.2.5.100.100 The CSS-Wx System application software shall be portable to the extent that porting it
                    to another hardware platform shall satisfy all the functional and performance
                    requirements and 95% of the code must be portable without change.
      R.2.5.200.100 The CSS-Wx System application software shall be portable to the extent that porting it
                    to another operating system on the same hardware platform shall satisfy all functional
                    and performance requirements and 98% of the code must be portable without change.

957     3.3.7 Interchangeability
958   Interchangeability refers to all CSS-Wx System equipment and parts supplied by the Contractor
959   that are interchangeable or replaceable.
960
      R.2.8.100.100 The CSS-Wx System equipment and parts supplied by the Contractor that are
                    interchangeable or replaceable shall conform to [FAA-G-2100, Section 3.3.4].

961     3.3.8 Latency/Response Time
962   For the purposes of this specification, CSS-Wx System Latency is defined as the time the CSS-
963   Wx System processes a weather product. It is measured from the time a weather product file is
964   presented to the CSS-Wx System input interface to the time the CSS-Wx System places the


                                                       61
965   processed product at its output interface. If multiple CSS-Wx nodes are used to process a
966   weather product file then the processing time of all of the involved CSS-Wx System nodes (that
967   are in series) constitutes the latency time for the operation. (In this version of the specification
968   we listed latency requirements associated with specific weather products. In the final
969   version of the specification we intend to specify latency requirements for service classes. A
970   CSS-Wx System service class will be defined by the number of each type of operation (e.g.,
971   filtering, re-projection, format conversion) that CSS-Wx System has to perform and the
972   total time within which it needs to perform these operations.)

973        3.3.8.1 Specific Weather Products

974   3.3.8.1.1 Terminal Weather Products
975
       R.2.10.400.100 The CSS-Wx System shall publish Microburst Detection and Prediction Products
                      within TBD milliseconds of product receipt.
       R.2.10.400.200 The CSS-Wx System shall publish Gust Front Detection and Prediction Products
                      within TBD milliseconds of product receipt.
       R.2.10.400.300 The CSS-Wx System shall publish Tornado Detections Products within TBD
                      milliseconds of product receipt.
       R.2.10.400.400 The CSS-Wx System shall publish “Runway Configuration Product” within TBD
                      milliseconds of product receipt.
       R.2.10.400.500 The CSS-Wx System shall publish “Wind Profile Product” within TBD milliseconds
                      of product receipt.
976

977   3.3.8.1.2 Lightning Products
         R.2.10.400.600 The CSS-Wx System shall geospatially subset (details TBD) and publish
                        Lightning data in TBD seconds.

978

979   3.3.8.1.3 Radar Products
       R.2.10.400.700 The CSS-Wx System shall publish NEXRAD products within TBD milliseconds after
                      the receipt of a complete product.
       R.2.10.400.800 The CSS-Wx System shall publish TDWR products within TBD milliseconds after the
                      receipt of a complete product.
       R.2.10.400.900 The CSS-Wx System shall publish ASR products within TBD milliseconds after the
                      receipt of a complete product.
980

981   3.3.8.1.4 National Composite Reflectivity Mosaic Product
       R.2.10.100.100 The CSS-Wx System shall geospatially subset the National Composite Reflectivity
                      Mosaic into 24 subsets which correspond to areas of responsibility of the individual
                      ERAMs, ATOPs, and MEARTS, and publish the resulting subsets within 6 seconds.
       R.2.10.100.200 The CSS-Wx System CSA shall convert the received subset of the National Composite
                      Reflectivity Mosaic to the legacy format of the DSR within 5 seconds.




                                                      62
982

983   3.3.8.1.5 NWP Satellite Product
      R.2.10.100.300 The CSS-Wx System shall geospatially subset (details TBD), quantize (details TBD),
                     and publish Satellite Mosaic Products in TBD seconds.

984

985   3.3.8.1.6 NOAA/NWS Model Data
      R.2.10.100.400    The CSS-Wx System shall reduce resolution (from 13 km to 40 km) and then
                        geospatially subset WRF-RR model data into twenty subsets, which correspond to
                        areas of responsibility of the individual ERAMs, and publish the resulting subsets
                        within TBD seconds.
      R.2.10.100.500    The CSS-Wx System CSA shall convert the received subset of the WRF-RR model
                        data to the legacy format of ERAM within 5 seconds.
      R.2.10.100.600    The CSS-Wx System shall geospatially subset WRF-RR model data into 35 subsets,
                        which correspond to areas of responsibility of the individual ITWSs, and publish the
                        resulting subsets within TBD seconds.
      R.2.10.100.700    The CSS-Wx System CSA shall convert the received subset of the WRF-RR model
                        data to the legacy format of ITWS within 5 seconds.
      R.2.10.100.800    The CSS-Wx System shall geospatially subset GFS model data into three subsets,
                        which correspond to areas of responsibility of the individual ATOPs, and publish the
                        resulting subsets within TBD seconds.
      R.2.10.100.900    The CSS-Wx System CSA shall convert the received subset of the GFS model data to
                        the legacy format of ATOP within 5 seconds.
      R.2.10.100.1000   The CSS-Wx System shall geospatially subset UKMet model data into three subsets,
                        which correspond to areas of responsibility of the individual ATOPs, and publish the
                        resulting subsets within TBD seconds.
      R.2.10.100.1100   The CSS-Wx System CSA shall convert the received subset of the UKMet model
                        data to the legacy format of ATOP within 5 seconds.
      R.2.10.100.1200   The CSS-Wx System shall geospatially subset GFS model data into four subsets,
                        which correspond to areas of responsibility of the individual DOTS, and publish the
                        resulting subsets within TBD seconds.
      R.2.10.100.1300   The CSS-Wx System CSA shall convert the received subset of the GFS model data to
                        the legacy format of DOTS within 5 seconds.
      R.2.10.100.1400   The CSS-Wx System shall publish the North American Mesoscale (NAM) model
                        data within TBD seconds.
      R.2.10.100.1500   The CSS-Wx System CSA shall convert the received subset of the NAM model data
                        to the legacy format of the FDP2K within 5 seconds.
986

987   3.3.8.1.7 Alpha-Numeric Products
       R.2.10.400.1000 The CSS-Wx System shall publish alpha-numeric products in TBD seconds.



988   3.3.8.1.8 VIL Products
      R.2.10.100.1600 The CSS-Wx System shall geospatially subset (details TBD), quantize (details TBD),
                      and publish VIL Mosaic Products in TBD seconds.



                                                      63
        R.2.10.100.1700 The CSS-Wx System shall geospatially subset (details TBD), quantize (details TBD),
                        and publish VIL Forecast Products in TBD seconds.
        R.2.10.100.1800 The CSS-Wx System shall geospatially subset (details TBD) and publish VIL
                        Contours (standard and winter mode) in TBD seconds.
        R.2.10.100.1900 The CSS-Wx System shall geospatially subset (details TBD) and publish Growth and
                        Decay Contours in TBD seconds.
        R.2.10.100.2000 The CSS-Wx System shall publish “Forecast Accuracy: Standard VIL” in TBD
                        seconds.
        R.2.10.100.2100 The CSS-Wx System shall publish “Forecast Accuracy: Winter VIL” in TBD
                        seconds.
 989

 990   3.3.8.1.9 Echo Tops Products
        R.2.10.100.2200 The CSS-Wx System shall geospatially subset (details TBD), quantize (details TBD),
                        and publish Echo Tops Mosaic Products in TBD seconds.
        R.2.10.100.2300 The CSS-Wx System shall geospatially subset (details TBD), quantize (details TBD),
                        and publish Echo Tops Forecast Products in TBD seconds.
        R.2.10.100.2400 The CSS-Wx System shall geospatially subset (details TBD) and publish Echo Tops
                        Contours in TBD seconds.
        R.2.10.100.2500 The CSS-Wx System shall publish “Forecast Accuracy: Echo Tops” in TBD seconds.

 991

 992   3.3.8.1.10 Storm Information Products
        R.2.10.300.100 The CSS-Wx System shall geospatially subset (details TBD) and publish “Storm Info:
                       Echo Tops Tags” in TBD seconds.
        R.2.10.300.200 The CSS-Wx System shall geospatially subset (details TBD) and publish “Storm Info:
                       Leading Edge” in TBD seconds.
        R.2.10.300.300 The CSS-Wx System shall geospatially subset (details TBD) and publish “Storm Info:
                       Motion Vectors” in TBD seconds.
 993
 994

 995   3.3.8.1.11 ADAS/RASP Products
        R.2.10.400.1100    The CSS-Wx System shall ingest, geospatially subset into 21 airport area
                           subsets, and publish ADAS/RASP products within 2 seconds.

 996        3.3.8.2 General Weather Products
 997   General weather products are products that are not specifically mentioned in the paragraphs
 998   above.
 999          Requirements TBD

1000     3.3.9 Quality of Service
1001   The CSS-Wx System Quality of Service (QoS) will be managed by designating different user-
1002   specified priority (For example: to different applications, users, or data flows, or to guarantee
1003   and manage a certain level of performance to a data flow).


                                                        64
1004
       R.2.1.100.100.100 The CSS-Wx System shall designate the priority of a message in the message
                         header in accordance with the [CSS-Wx System-to SWIM System Interface
                         Requirements Document (TBD)].


1005     3.3.10 Reserve Capacity
       R.2.6.100.100 All CSS-Wx System Nodes shall contain 50% reserve processing capacity, above the
                     baseline configuration established for Initial Operating Capability, so that the mean
                     utilization over any 1-minute interval does not exceed 90% of the maximum processing
                     capacity.
       R.2.6.200.100 All CSS-Wx System Nodes shall contain reserve memory capacity, above the baseline
                     configuration established for Initial Operating Capability, so that memory utilization
                     does not exceed 75% of the maximum memory capacity.
       R.2.6.300.100 All CSS-Wx System Nodes shall contain reserve online storage capacity, above the
                     baseline configuration established for Initial Operating Capability, so that the storage
                     utilization does not exceed 50% of the maximum online storage capacity.

1006
1007   3.4   Interface Requirements
1008   This section describes the interfaces between the CSS-Wx System and the new or existing
1009   systems within or external to the FAA security boundary, which it must interact, either
1010   physically or functionally.
1011
1012   As indicated above, the CSS-Wx System will support users (weather data consuming systems)
1013   external to the FAA. These users are subject to NextGen governance and standards and include:
1014   Commercial Aviation Weather Providers, other Government Agencies, and NAS Operators. The
1015   CSS-Wx System supports subscriptions and queries from such authorized external users.
1016   External users are classified as native weather data consumers; thus all weather data are provided
1017   in the native format and no Consumer Service Adapter support is provided. The CSS-Wx
1018   System provides geospatial filtering; however, mapping such filtered weather data to individual
1019   aircraft flight paths is an External User application.

1020     3.4.1 Legacy Weather Consumer Interfaces
1021   Weather consumer systems will present their legacy interface for obtaining weather products to a
1022   CSS-Wx System Consumer Service Adapter (CSA). The CSS-Wx System CSA will
1023   accommodate this interface by establishing a connection to and from the CSS-Wx System and
1024   converting the requested data into a useable format, as required.
1025
        R.4.1.100.200.50        The CSS-Wx System shall interface with legacy consumers via consumer
                                service adaptors.
        R.4.1.100.200.100       The CSS-Wx System shall interface with Advanced Technologies and
                                Oceanic Procedures (ATOP) in accordance with [NAS-(IRD #)].
        R.4.1.100.300.100       The CSS-Wx System shall interface with Dynamic Ocean Track System
                                Plus (DOTS Plus) in accordance with [NAS-(IRD #)].
        R.4.1.100.100.100       The CSS-Wx System shall interface with En Route Automation



                                                         65
                              Modernization (ERAM) in accordance with [NAS-(IRD #)] for radar
                              mosaics.
       R.4.1.100.100.105      The CSS-Wx System shall interface with En Route Automation
                              Modernization (ERAM) in accordance with [NAS-(IRD #)] for radar
                              mosaics.
       R.4.1.100.400.100      The CSS-Wx System shall interface with Flight Data Processor 2000
                              (FDP2K) in accordance with [NAS-(IRD #)].
       R.4.1.100.800.100      The CSS-Wx System shall interface with Microprocessor En Route
                              Automated Radar Tracking System (MEARTS) in accordance with [NAS-
                              (IRD #)].
       R.4.1.100.800.101      The CSS-Wx System shall interface with Traffic Management Advisor
                              (TMA) in accordance with [NAS-IRD/WSRD #].
       R.4.1.100.900.100      The CSS-WX System shall interface with Integrated Terminal
                              Weather System (ITWS) in accordance with [NAS-(IRD #)].
       R.4.1.100.900.200      The CSS-Wx System shall interface with NAS Information Display
                              System (NIDS) in accordance with [NAS-(IRD #)].
1026

1027     3.4.2 OGC-Compliant Consumer Interfaces
1028   OGC-compliant systems do not require the CSS-Wx System to convert the format of the weather
1029   products. These systems will interface with the CSS-Wx System for product tailoring. Product
1030   tailoring may include content filtering, measurement conversion, and map projection
1031   transformation.
       R.4.1.200.001     The CSS-Wx System shall publish weather information to Future Flight Services
                         Program (FFSP) system in accordance with [NAS-IRD/WSRD #].
       R.4.1.200.100.100 The CSS-Wx System shall publish with NextGen Weather Processor (NWP) in
                         accordance with [NAS-IRD/WSRD #].
       R.4.1.200.002     The CSS-Wx System shall publish weather information to external consumers in
                         accordance with [NAS-IRD/WSRD #].
       R.4.1.200.005     The CSS-Wx System shall publish weather information to NOAA National
                         Weather System (also known as the NOAA 4D Weather Cube) in accordance with
                         [NAS-IRD/WSRD #].
       R.4.1.200.007     The CSS-Wx System shall publish weather information to Center for Advanced
                         Aviation System Development Analysis Platform for En Route (CAPER) in
                         accordance with [NAS-IRD/WSRD #].
       R.4.1.200.009     The CSS-Wx System shall publish weather information to Time Based Flow
                         Management. (TBFM) System in accordance with [NAS-IRD/WSRD #].
       R.4.1.200.010     The CSS-Wx System shall publish weather information to Traffic Flow
                         Management System (TFMS) in accordance with [NAS-IRD/WSRD #].
       R.4.1.200.011     The CSS-Wx System shall publish weather information to Terminal Flight Data
                         Manager (TFDM) in accordance with [NAS-IRD/WSRD #].
1032

1033     3.4.3 Legacy Weather Provider Interfaces
1034   Weather Provider systems will present their legacy interface for transmitting weather products to
1035   the CSS-Wx System PSA. The CSS-Wx System PSA will accommodate this interface by
1036   converting the requested data into a useable format, as required.


                                                      66
1037
       R.4.1.300.100.100 The CSS-Wx System shall interface with Regional Automated Weather Observing
                         System Data Acquisition System (ADAS) Support Processor (RASP) in accordance
                         with [NAS-(ICD-#)].
       R.4.1.300.002     The CSS-Wx System shall interface with Automated Weather Observing System
                         Data Acquisition System (ADAS) in accordance with [NAS-ICD #].
       R.4.1.300.003     The CSS-Wx System shall interface with Weather Message Switching Center
                         Replacement (WMSCR) in accordance with [NAS-ICD #].
1038

1039     3.4.4 OGC-Compliant Weather Provider System Interfaces
1040   OGC-compliant systems do not require the CSS-Wx System to convert the format of the weather
1041   products. These systems will interface with the CSS-Wx System to transmit weather data and
1042   products for product tailoring (for example, content filtering, measurement conversion, map
1043   projection transformation) as required by the weather product consumers.
       R.4.1.400.100.100 The CSS-Wx System shall interface with NextGen Weather Processor (NWP)
                         in accordance with [NAS-IRD/WSRD (#)].
       R.4.1.400.100.002 The CSS-Wx System shall interface with NOAA’s National Weather Service
                         (also known as the NOAA 4D Weather Cube) in accordance with [NAS-
                         (#document)].
       R.4.1.400.001     The CSS-Wx System shall interface with Aeronautical Information
                         Management (AIM) system in accordance with [NAS-IRD/WSRD (#)].
1044

1045     3.4.5 Radar System Interfaces
       R.4.1.300.400.100 The CSS-Wx System shall interface with Terminal Doppler Weather Radar
                         (TDWR) in accordance with [NAS-ICD-(#)].
       R.4.1.300.300.100 The CSS-Wx System shall interface with WSR-88D (also known as Next
                         Generation Weather Radar) in accordance with [NAS-ICD-(#)].
       R.4.1.300.500.100 The CSS-Wx System shall interface with Canadian Radar (CANRAD) system in
                         accordance with [NAS-ICD-(#)].

1046    3.4.6 FAA SWIM Interface
       R.4.1.500.300.100 The CSS-Wx System shall interface with the System Wide Information
                         Management NAS Enterprise Messaging (SWIM) Service in accordance with
                         [NAS-IRD/WSDD (#)].

1047    3.4.7 Remote Monitoring Management System Interface
       R.4.1.500.400.100 The CSS-Wx System shall interface with Remote Maintenance Monitoring
                         System (RMMS) in accordance with [NAS-ICD #].

1048     3.4.8 External NAS User System Interface
1049   The term external NAS user refers to a non-FAA weather data consumer that will access weather
1050   datasets from the CSS-Wx System from a system that is external to the FAA- operational
1051   network.
1052


                                                    67
       R.1.4.200.200.100 The CSS-Wx System shall interface with external NAS consumers in
                          accordance with [NAS-ICD #??].
1053
1054   3.5   Design and Construction

1055     3.5.1 Software Design
1056          Reserved

1057     3.5.2 Hardware Design
1058          Reserved

1059    3.5.3 Installation
       R.3.1.200.200 The CSS-Wx System shall be installed at the ARTCC sites as specified in the
                     [ARTCC IRD#].
       R.3.1.200.300 The CSS-Wx System shall be installed at the ATCSCC as specified in the
                     [ATCSCC IRD #].
       R.3.1.200.400 The CSS-Wx System shall be installed at the TRACON sites as specified in the
                     TRACON IRD #].
       R.3.1.200.500 The CSS-Wx System shall be installed at the ATCT sites as specified in the
                     [ATCT IRD #].
       R.3.1.200.600 The CSS-Wx System shall be installed at the NEMC sites as specified in the
                     [NEMC IRD #].

1060     3.5.4 Power Requirements

1061        3.5.4.1 Protection
       R.3.6.100.200 The CSS-Wx System equipment shall comply with transient power protection,
                     grounding, bonding, and shielding requirements in accordance with [FAA-STD-
                     020B] and [FAA-STD-019E].

1062        3.5.4.2 Power Load
       R.3.9.100.100.300 The CSS-Wx System shall comply with the electrical power requirements
                         specified in [FAA-G-2100H Electronic Equipment, General Requirements,
                         Section 3.1.1, including only subsections 3.1.1.3 and 3.1.1.5].
       R.3.9.100.100.400 The CSS-Wx System shall meet power factor requirements [IAW FAA-F-
                          2100H, Section 3.1.1.3.1].
       R.3.9.100.100.500 The CSS-Wx System shall meet inrush current requirements [IAW FAA-
                         2100H, Section 3.1.1.3.2].
       R.3.9.100.100.600 The CSS-Wx System shall meet harmonics requirements [IAW FAA-F-
                         2011H, Section 3.1.1.5].

1063        3.5.4.3 Cooling
       R.3.5.100.100 The internal temperature of operating CSS-Wx System components shall
                     conform to the operating limits, as specified by supplying vendors, without


                                                       68
                         requiring special cooling equipment other then forced-air cooling.

1064        3.5.4.4 Convenience Receptacles
       R.3.9.200.100.100 The convenience receptacles, if applicable, shall not be connected to critical
                         power bus.

1065    3.5.5 Hardware Requirements
       R.2.8.100.200 All CSS-Wx System hardware components shall be commercial off-the-shelf.

1066       3.5.5.1 Workstation Hardware Components
       R.5.1.2200.100 The CSS-Wx System workstation shall contain the following hardware
                       components:
                   (a) One full American National Standard Code for Information Interchange QWERTY
                       keyboard with numeric keypad
                   (b) One mouse or trackball
                  (c) One color graphics monitor with the following characteristics:
                    i.      Flat panel display using Liquid Crystal Display technology
                   ii.      A diagonal screen of at least 20 inches
                  iii.      A native pixel resolution of at least 1280 by 1024
                   iv.      Screen refresh rate of at least 60 Hertz
                   v.       Digital interface to workstation (i.e., Digital Visual Interface or High
                            Definition Multimedia Interface)

1067       3.5.5.2 System Printer
       R.5.1.1700.100 Each CSS-Wx System Node shall consist of one printer with the following
                       characteristics:
                   (a) Laser technology
                  (b) Print speed of 30 pages per minute or better in black
                  (c) Paper handling of 8.5" x 11"
                  (d) Network enabled

1068    3.5.6 Hardware Interfaces
       R.5.1.2100.100 The CSS-Wx System hardware shall include the following interfaces:
                  (a) 10/100/1000 Base-T Ethernet
                  (b) Universal Serial Bus (USB)

1069    3.5.7 Equipment Cabinetry
       R.3.1.200.700      The CSS-Wx System equipment cabinet dimensions shall be less than or equal to 24
                          inches in width, 43 inches in depth, and 78.5 inches in height.
       R.3.1.200.800      The CSS-Wx equipment cabinets shall accommodate 19 inch rack mounted
                          equipment.
       R.3.1.200.900      The CSS-Wx System equipment shall be designed to be free of mechanical hazards



                                                         69
                      that may injure personnel (sharp projections, unguarded moving parts, etc.), in
                      accordance with [FAA-G-2100H, Electronic Equipment, General Requirements,
                      Section 3.3.5.4].
       R.3.1.200.1000 The CSS-Wx System equipment shall be equipped with the capacity for lockout, in
                      accordance with [FAA Order 3900.19B, Chapter 13].
1070

1071     3.5.8 Physical Requirements

1072        3.5.8.1 Weight Limits

1073   3.5.8.1.1 Floor Loading
       R.3.1.200.1100 The CSS-Wx System, including the cabinets and frames, shall be within the weight
                      limitations specified in the [ARTCC IRD#].
       R.3.1.200.1200 The CSS-Wx System, including the cabinets and frames, shall be within the weight
                      limitations specified in the [ATCSCC IRD #].
       R.3.1.200.1300 The CSS-Wx System, including the cabinets and frames, shall be within the weight
                      limitations specified in the TRACON IRD #].
       R.3.1.200.1400 The CSS-Wx System, including the cabinets and frames, shall be within the weight
                      limitations specified in the [ATCT IRD #].
       R.3.1.200.1500 The CSS-Wx System, including the cabinets and frames, shall be within the weight
                      limitations specified in the [NEMC IRD #].

1074   3.5.8.1.2 Point Loads
       R.3.1.200.1600 The CSS-Wx System point loads shall meet the requirements specified in the [ARTCC
                      IRD#].
       R.3.1.200.1700 The CSS-Wx System point loads shall meet the requirements specified in the
                      [ATCSCC IRD#].
       R.3.1.200.1800 The CSS-Wx System point loads shall meet the requirements specified in the
                      [TRACON IRD#].
       R.3.1.200.1900 The CSS-Wx System point loads shall meet the requirements specified in the [ATCT
                      IRD#].
       R.3.1.200.2000 The CSS-Wx System point loads shall meet the requirements specified in the [NEMC
                      IRD#].

1075        3.5.8.2 Size

1076   3.5.8.2.1 Floor Space
       R.3.1.200.2100 The CSS-Wx System computers and communications equipment floor space at an
                      ARTCC shall not exceed those values specified in [ARTCC IRD#].
       R.3.1.200.2200 The CSS-Wx System computers and communications equipment floor space at an
                      ATCSCC shall not exceed those values specified in [ATCSCC IRD #].
       R.3.1.200.2300 The CSS-Wx System computers and communications equipment floor space at a
                      TRACON shall not exceed those values specified in the [TRACON IRD #].
       R.3.1.200.2400 The CSS-Wx System computers and communications equipment floor space at an



                                                      70
                       ATCT shall not exceed those values specified in the [ATCT IRD #].
       R.3.1.200.2500 The CSS-Wx System computers and communications equipment floor space at an
                      NEMC shall not exceed those values specified in the [NEMC IRD #].

1077       3.5.8.3 Maintenance Access
       R.3.1.200.2600 The CSS-Wx System cabinets and frames shall provide front and rear access as needed
                      for maintenance and repair activities.

1078       3.5.8.4 Durability
       R.3.1.200.2700 The structural strength and rigidity of the CSS-Wx System cabinets and frames shall
                      be such that common carrier handling in load, shipping, unloading, and setting into
                      position for installation shall not cause damage or deformation to any CSS-Wx System
                      component.

1079    3.5.9 Standards of Manufacture
       R.3.1.200.2800 The CSS-Wx System cabinets and frames and associated peripherals shall meet
                      National Fire Protection Association 5000, Building Construction and Safety Code™
                      clearance standards.

1080    3.5.10 Environmental Safety and Health

1081       3.5.10.1 Environmental
       R.3.3.200.200 The CSS-Wx System equipment shall be in accordance with FAA Order 1050.10,
                     Prevention, Control and Abatement of Environmental Pollution at FAA Facilities.
       R.3.3.400.100 The CSS-Wx System equipment shall conform to environmental protection
                     requirements in accordance with 40 CFR, Protection of Environment.

1082       3.5.10.2 Energy Conservation
       R.3.4.200.100 The CSS-Wx System equipment shall meet energy conservation requirements in
                      accordance with:
                  (a) Executive Order 13423, Strengthening Federal Environmental, Energy, and
                      Transportation Management.
                 (b) Executive Order 13514, Federal Leadership in Environmental, Energy, and Economic
                      Performance.

1083       3.5.10.3 Grounding, Bonding, Shielding, Lightning Protection
       R.3.6.100.300 The CSS-Wx System equipment shall be protected in accordance with FAA-STD-019E,
                     Lightning Protection, Grounding, Bonding, and Shielding for Facilities.
       R.3.6.300.100 The CSS-Wx System equipment shall be protected in accordance with American
                     National Standards Institute (ANSI)/Institute of Electrical and Electronics Engineers
                     (IEEE) 1100-2005, Recommended Practice for Powering and Grounding Sensitive
                     Electronic Equipment.
       R.3.6.400.100 The CSS-Wx System equipment shall be protected in accordance with NFPA Standard
                     70, National Electric Code®, and local codes.

1084       3.5.10.4 Hazardous Materials
       R.3.8.100.100 The CSS-Wx System equipment shall minimize use of hazardous materials in



                                                      71
                     accordance with Executive Order 13423, Strengthening Federal Environmental, Energy,
                     and Transportation Management, and Executive Order 13514, Federal Leadership in
                     Environmental, Energy, and Economic Performance.
       R.3.8.100.200 The CSS-Wx System equipment shall be free of asbestos, in accordance with the Clean
                     Air Act and Toxic Substances Control Act.
       R.3.8.100.300 The CSS-Wx System equipment shall be free of lead in accordance with FAA Order
                     1050.10C, Prevention, Control, and Abatement of FAA Environmental Pollution.
       R.3.8.100.400 The CSS-Wx System equipment shall be free of mercury, in accordance with FAA
                     Order 1050.10C, Prevention, Control, and Abatement of FAA Environmental Pollution.

1085       3.5.10.5 Special Considerations for Seismic Safety
       R.3.11.100.100.100 The CSS-Wx System equipment shall be designed to meet seismic safety
                          requirements in accordance with FAA-G-2100H, Electronic Equipment, General
                          Requirements, to ensure the safety of personnel during a seismic event.

1086       3.5.10.6 Occupational Safety and Health
       R.3.1.200.100 The CSS-Wx System equipment racks and associated peripherals shall be installed in
                      accordance with NFPA 5000, Building Construction and Safety Code® clearance
                      standards.
       R.3.8.600.100 The CSS-Wx System equipment shall meet personnel safety requirements in accordance
                      with:
                  (a) 29 CFR 1910
                  (b) 29 CFR 1926
                  (c) FAA Order 3900.19B
                  (d) FAA Standard HF-STD-001
       R.3.8.600.200 The CSS-Wx System equipment shall meet Nationally Recognized Testing Laboratory
                      program requirements in accordance with 29 CFR 1910 Subpart S.

1087       3.5.10.7 Equipment Labeling
       R.3.8.700.100 CSS-Wx System equipment that presents a potential safety hazard shall be marked with
                      appropriate warning labels or placards, in accordance with:
                  (a) 29 CFR 1910.145, Specifications for Accident Prevention Signs and Tags
                  (b) FAA HF-STD-001, Human Factors Design Standard, Chapter 12.16, Safety Labels and
                      Placards
                  (c) American National Standards Institute Z535.4, Product Safety Signs and Labels

1088       3.5.10.8 Electrical Safety
       R.3.6.100.100 CSS-Wx System electrical equipment shall adhere to electrical safety requirements in
                      accordance with:
                  (a) 29 CFR 1910, Subpart S, Electrical.
                  (b) DOT Specification FAA-G-2100H, Electronic Equipment, General Requirements.
                  (c) NFPA 70, National Electrical Code.
                  (d) NFPA 70E, Standard for Electrical Safety in the Workplace.
                  (e) FAA-G-2100H, Chapter 3.3.5.5, Markings, Signs, Tags and Symbols, for marking
                      electrical equipment.

1089       3.5.10.9 Battery Safety
       R.3.9.100.100.100 CSS-Wx System backup batteries shall be in accordance with:


                                                       72
                        (a) FAA Order 3900.19B, FAA Occupational Safety and Health Program
                        (b) FAA Order 6980.25C, Maintenance of Batteries for Standby Power
                        (c) NFPA 70, National Electrical Code®, Article 480

1090        3.5.10.10          Occupational Noise
       R.3.9.100.100.200 The CSS-Wx System shall not exceed noise levels as specified in FAA-G-2100H.
                       b) The CSS-Wx System equipment shall meet occupational noise requirements in
                          accordance with:
                      (a) FAA Order 3900.19B, FAA Occupational Safety and Health Program
                      (b) FAA Standard HF-STD-001, Human Factors Design Standard, Section 13.5.2
                          Noise
                      (c) 29 CFR 1910.95, Occupational Noise Exposure

1091        3.5.10.11          Indoor Air Quality
       R.3.3.200.100 CSS-Wx System equipment shall comply with indoor air quality standards at FAA
                      facilities, in accordance with:
                  (a) FAA Order 3900.19B, FAA Occupational Safety and Health Program
                  (b) U.S. Environmental Protection Agency primary and secondary standards

1092        3.5.10.12          Material Handling
       R.5.1.2500.100 The CSS-Wx System equipment labels shall be affixed to any line replaceable unit
                      weighing 30 pounds or greater that indicate its weight, center of gravity, and the
                      number of people recommended lifting or carrying the LRU, in accordance with FAA
                      Standard HF-STD-001, Human Factors Design Standard, Chapter 12.16.14 Center of
                      Gravity and Chapter 12.16.15 Weight Labels.”

1093     3.5.11 Human Factors Engineering
1094   The human factors requirements below are applicable to CSS-Wx System workstations used for
1095   system administrative and maintenance tasks.

1096        3.5.11.1 User Interface Requirements

1097   3.5.11.1.1 User Display Control for Technical Operations

1098   3.5.11.1.1.1 Workstation Monitors for Technical Operations
       R.5.1.1700.1100      Each CSS-Wx System user display shall be controlled by input devices,
                            consisting of a keyboard, mouse and/or trackball that are dedicated to that
                            display in accordance with FAA-HF-001, Human Factors Design Standard,
                            Chapter 9, Input Devices

1099   3.5.11.1.1.2 Computer Monitor Interactions
       R.5.1.1700.1000      The CSS-Wx System interactions with a computer monitor shall be
                            independent of interactions with other monitors.

1100   3.5.11.1.2 User Input
       R.5.1.2200.200 The CSS-Wx System shall provide access to all CSS-Wx System functions and
                      products from a CSS-Wx System workstation with no more than five user actions
                      using workstation input devices.


                                                         73
       R.5.1.2200.300 The CSS-Wx System shall provide the following methods for accessing CSS-Wx
                       System functions and products:
                   (a) Through a Java look and feel programmable user interface provide a cross-platform
                       graphical user interface.
                  (b) Through the use of a newly generated or previously created and stored procedure/
                       command string that can be executed via a simple operator request or initiated by the
                       occurrence of an event recognizable by the CSS-Wx System.
                   (c) Through the use of single-action, preprogrammed function-select keys.

1101   3.5.11.1.3 Feedback to User
       R.1.3.300.300.100.100 The CSS-Wx System shall provide a text message, or other distinct indication,
                             confirming that a requested action has not been performed in response to a
                             user’s request.
       R.1.3.300.300.100.200 The CSS-Wx System shall provide a text message, or other distinct indication,
                             confirming that a requested action cannot be performed in response to a user’s
                             request.
       R.1.3.300.300.100.300 The CSS-Wx System shall provide a text message, or other distinct indication
                             that the CSS-Wx System is processing a requested action in response to a
                             user’s request if the action takes more than three seconds to complete.

1102   3.5.11.1.3.1 Messages
       R.1.3.300.300.100.400 The CSS-Wx System shall generate system error messages and user input error
                             messages written in English text.

1103   3.5.11.1.3.2 Deletion Message
       R.1.3.300.300.100.500 The CSS-Wx System shall confirm commands that result in deletion of
                             data and a product.
       R.1.3.300.300.100.600 The CSS-Wx System shall ask for user confirmation of a request in
                             response to a user’s request to delete data and a product.
       R.1.3.300.300.100.700 The CSS-Wx System shall execute a command to delete data and a
                             product only after the user confirms the command.

1104   3.5.11.1.3.3 Command Response
       R.1.3.300.300.100.800 The CSS-Wx System shall respond to all fulfilled user’s requests with an
                             acknowledgment indicating successful completion.

1105   3.5.11.1.3.4 Command Error Messages
       R.1.3.300.300.100.900 The CSS-Wx System shall respond to a command that cannot be fulfilled,
                             by identifying errors in the command or an indication of a system error
                             detected in attempting to carry out the action requested.

1106        3.5.11.2 Monitor Display

1107   3.5.11.2.1 Monitor Positions
       R.5.1.1700.200 The CSS-Wx System monitors shall be continuously adjustable as follows:
                   (a) Tilt 15 degree total: 10 degree forward and 5 degree backward from the vertical axis
                   (b) Swivel 90 degree total: 45 degree left and 45 degree right from normal line of sight.



                                                         74
1108




       75
1109   4     QUALIFICATION REQUIREMENTS
1110   4.1   Test Planning/Procedures
1111   The Air Traffic Organization NextGen and Operations Planning Services (ATO-P) Test and
1112   Evaluation (T&E) Handbook Document # VVSPT-A2-PDD-013, Version 2.1.1, dated August
1113   31, 2010, will be used to ensure that the Contractor has met and implemented the requirements of
1114   this Specification, associated interface requirements and control documents. The Handbook
1115   identifies the roles, responsibilities, and test activities. At a minimum, system tests of the CSS-
1116   Wx System will include system performance testing under the following conditions:
1117           a. Normal data flow, data loading and operations
1118           b. Limit and overload of system inputs, processing, outputs, and storage
1119           c. Erroneous/invalid data inputs and recovery from errors
1120           d. System failures and recovery.
1121   4.2   Verification Methods
1122   The verifications methods defined below and allocated in the Appendix C, Verification
1123   Requirements Traceability Matrix (VRTM), is mandatory for all CSS-Wx System testing. Where
1124   applicable, pass/fail criteria for each verified requirement will be defined and placed in the
1125   appropriate subordinate level test documentation. Any failure to meet an appropriate verification
1126   test requirement pass/fail criteria shall be cause for rejection.
1127           (a) Inspection (denoted by “I” in Appendix C): Inspection is validation by visual
1128               examination of the item, reviewing descriptive documentation, and comparing the
1129               appropriate characteristics with a predetermined or reference standard, to determine
1130               compliance with requirements, without the use of special laboratory equipment or
1131               procedures
1132           (b) Analysis (denoted by “A” in Appendix C): Analysis is validation by
1133               technical/mathematical evaluation or simulation using mathematical representation
1134               (i.e., mathematical models, algorithms, and/or equations), charts, graphs, circuit
1135               diagrams, data reduction/recording, and representative data to prove that specified
1136               requirements are met. Representative data may include data collected from previous
1137               or other equipment and system verification
1138           (c) Demonstration (denoted by “D” in Appendix C): Demonstration is an un-
1139               instrumented test, where success is determined from observation alone. Included in
1140               this category are tests whose results can easily be determined on a pass-fail basis
1141           (d) Test (denoted by “T” in Appendix C): Test is validation, through systematic
1142               exercising of an item under all appropriate conditions, along with collection, analysis,
1143               and evaluation of quantitative data for predetermined performance characteristics.
1144               Acceptability is determined by the comparison of the data with pre-established
1145               quantitative requirements and occurrences.
1146   4.3   Verification Requirements Traceability Matrix (VRTM)
1147   Appendix C defines, for each requirement in Section 3 of this System Specification, the
1148   verification method or a combination of methods used to validate CSS-Wx System requirements.
1149   The VRTM consists of the following information:
1150           (a) CSS-Wx System Specification paragraph number of each specification requirement,
1151           (b) Paragraph name of each specification requirement, and,
1152           (c) Itemized method of test (I, A, D, or T) for each specification requirement.


                                                       76
                              CSS-Wx System Specification Document
                                                Draft

1153   APPENDIX A         ACRONYMS
       4-D Wx Data Cube   4 Dimensional Weather Data Cube
       ADAS               AWOS Data Acquisition System
       AIM                Aeronautical Information Management
       ANSI               American National Standards Institute
       ARTCC              Air Route Traffic Control Centers
       ASR                Airport Surveillance Radar
       ATCSCC             Air Traffic Control System Command Center
       ATCT               Air Traffic Control Tower
       ATOP               Advanced Technologies and Oceanic Procedures
       CAA                Clean Air Act
       CANRAD             Canadian Radar
       CAPER              CAASD Analysis Platform for En Route
       CDN                Content Delivery Network
       CERAP              Combined Center Radar Approach Control
       CIWS               Corridor Integrated Weather System
       ConOPS             Concept of Operations
       COTS               Commercial Off The Shelf
       CQS                Complex Query Service
       CRP                Complex Retrieval Process
       CRS                Coordinate Reference System
       CSA                Consumer Service Adaptor
       DDS                Data Distribution System
       DOT                Department of Transportation
       DOTS               Dynamic Ocean Tracking System
       DTS                Dedicated Transmission Service
       DVI                Digital Visual Interface
       ebRIM              ebXML Registry Information Model
       EIA                Electronic Industries Association
       EPSG               European Survey Group
       ERAM               En Route Automation Modernization
       ESB                Enterprise Service Bus
       EXI                Efficient XML Interchange
       FAA                Federal Aviation Administration
       FAST               FAA Acquisition System Toolset
       FDP2K              Flight Data Processor 2000
       FFSP               Future Flight Services Program
       FTI                FAA Telecommunication Infrastructure
       FTP                File Transfer Protocol
       GIF                Graphics Interchange Format
       GML                Geography Markup Language
       HDMI               High Definition Multimedia Interface
       HTTP               Hypertext Transfer Protocol


                                                A-1
               CSS-Wx System Specification Document
                                  Draft

IEEE      Institute of Electrical and Electronics
IRD       Interface Requirements Document
JMS       JAVA Messaging Service
JMX       JAVA Management Extensions
JPDO      Joint Planning and Development Office
JPEG      Joint Photographic Experts Group
KVP       Key-Value Pair
LRU       Line Replaceable Unit
MEARTS    Microprocessor En Route Automated Radar Tracking System
METAR     Meteorological Weather Observation
MSDS      Material Safety Data Sheets
MTBF      Mean-Time-Between-Failures
MTTR      Mean-Time-To-Repair
NAS       National Airspace System
NEMC      Network Enterprise Management Centers
NEMS      NAS Enterprise Messaging Service
NESG      NAS Enterprise Security Gateway
NetCDF    Network Common Data Form
NextGen   Next Generation Air Transportation System
NFPA      National Fire Protection Association
NIDS      NAS Information Display System
NNEW      NextGen Network Enabled Weather
NOAA      National Oceanic and Atmospheric Administration
NRTL      Nationally Recognized Testing Laboratory
NWP       Numerical Weather Processor
OGC       Open Geospatial Consortium
OMO       One Minute Observations
OWL       Web Ontology Language
OWS       OpenGIS Web Services
PNG       Portable Network Graphics
POX       Plain Old XML
PSA       Provider Service Adaptor
QOS       Quality of Service
RAM       Random Access Memory
RASP      Regional ADAS Service Processor
RDF       Resource Description Framework
RIA       Radar Service Adaptor
RMMS      Remote Monitoring Management System
RS        Registry Services
SA        Service Adaptor
SAML      Security Assertion Markup Language
SAS       Single Authoritative Source
SIA       System Ingest Adaptor


                                  A-2
                              CSS-Wx System Specification Document
                                                Draft

       SOA               System Oriented Architecture
       SOAP              Simple Object Access Protocol
       SWIM              System Wide Information Management
       TAF               Terminal Aerodrome Forecast
       TBFM              Time Based Flow Management
       TDWR              Terminal Doppler Weather Radar
       TFM               Traffic Flow Management
       TFMS              Traffic Flow Management System
       TMA               Traffic Management Advisor
       TRACON            Terminal Radar Approach Control
       TSCA              Toxic Substances Control Act
       UML               Universal Modeling Language
       URI               Uniform Resource Identifier
       URL               Uniform Resource Locator
       USB               Uniform Service Bus
       VIL               Vertically Integrated Liquid
       VRTM              Verification Requirements Traceability Matrix
       WARP              Weather and Radar Processor
       WAS               Weather Alerts Service
       WCS               Web Coverage Service
       WCS-I
       WFS               Web Feature Service
       WFS-I
       WGS               World Geodetic System
       WINS              Weather Information Network Server
       WJHTC             William J Hughes Technical Center (FAA)
       WMS               Web Map Service
       WMS-I
       WS-Addressing     Web-Services Addressing
       WSDL              Web Services Description Language
       WS-I              Web Service Implementation
       WSN               Web Services Notification
       WS-Notification   Web Services Notification
       WSR-88D           Weather Service Radar 88D
       WXXM/WXXS         Weather Information Exchange Model/Schema
       XACML             eXtensible Access Control Markup Language
       XML               Extensible Markup Language
       Xpath             XML Path Language
       Xquery            XML Query Language
       XSLT              XSL Transformations

1154
1155


                                                 A-3
                                   CSS-Wx System Specification Document
                                                      Draft

1156   APPENDIX B            GLOSSARY
1157   The list below defines terminology associated with the CSS-Wx System requirements.
1158
       2-D Region: A region defined by (x,y), (y,z), or (x,z) coordinate points.
       3-D Bounded Box: A volume defined by (x,y,z) coordinate points.
       Access Control: Protection of system resources against unauthorized access; a process by
       which use of system resources is regulated according to a security policy and is permitted by
       only authorized entities.
       Adaptation Data: Data used to customize elements of the CSS-Wx System Node for its
       designated purpose or location.
       Add Wx Metadata Subscriptions: To allow users to subscribe to notifications about weather
       metadata updates.
       Add Wx Metadata: To register new weather metadata.
       Aggregate Wx Data: To take multiple datasets and make a single dataset from those datasets.
       Airway: An officially designated air route with sectors defined as specific courses to or from
       directional radio stations.
       Alert Conditions: A set of CSS-Wx system parameters and threshold values that are
       monitored and when met meet the criteria to generate an alert message.
       Altitude: The height of a level, point, or object measured in feet Above Ground Level (AGL)
       or from Mean Sea Level (MSL).
       Archive Wx Data: To record and save weather data for long term and potential reuse.
       Assign Data Expiration Condition: To set the threshold by which the data will be removed
       from where it is stored.
       Audit Data: Chronological record of system activities to enable the reconstruction and
       examination of the sequence of events and changes in an event.
       Authenticate Wx Consumer: To examine, validate, and confirm the identity claims of the
       user or system attempting to gain access to the CSS-Wx System.
       Authorize Wx Consumer: To examine, validate, and confirm the access claims of the user or
       system on the CSS-Wx System.
       Availability: The CSS-Wx System Node availability is measured as: Availability = Mean
       Time Between Failures (MTBF) + Mean Time To Restore (MTTR)/MTBF in accordance
       with FAA-STD-065.
       Baseline: One deployed configuration of a CSS-Wx System element (hardware, software).
       Business Function: A characteristic action or activity that needs to be performed to achieve a
       desired objective, or in the context of this standard, to achieve a real world effect.
       Cartesian coordinates: Specifies each point uniquely in a plane by a pair of numerical
       coordinates, which are the signed distances from the point to two fixed perpendicular directed
       lines, measured in the same unit of length. Each reference line is called a coordinate axis or
       just axis of the system, and the point where they meet is its origin, usually at ordered pair (0,0).
       Catastrophic State: The CSS-Wx System Node has failed and is unrecoverable. Both the
       primary and backup nodes have failed.
       Complex Retrieval: A query service of the CSS-Wx System where consumers can send a
       single query to produce multiple products, multiple product types, and/or multiple formats that
       are aggregated into a CSS-Wx-specific format and returned to the consumer as a single



                                                       B-4
                           CSS-Wx System Specification Document
                                            Draft

response.
Configuration Item: A software or hardware component of the CSS-Wx System under
configuration control.
Configuration Parameters: The attributes of the CSS-Wx System that can be predefined by
an authorized user and adapted for site-specific functionality.
Constraint: The parameters used to define filtering requests and the subsequent subset.
Contiguous United States: The 48 U.S. states on the continent of North America that are
south of Canada, plus the District of Columbia.
CONUS: See Contiguous United States.
Convert Coordinate Systems: To take weather data that uses a particular coordinate system
and transform that weather data to a different coordinate system.
Convert Wx Measurements: To transform the measurements used in weather data (e.g.,
altitude) from one measurement type to another.
Corrective maintenance: Repairing System nodes by updating software or replacing faulty
hardware.
Corridor: A volume surrounding a path between two points.
Coverage: A conceptual dataset representing a single gridded data product, which may be
composed of several different data files and fields, and may pertain to a general time range.
CPU Usage measurements: Information from processor counters used to monitor CSS-Wx
Server CPU activity.
Create Logs: To generate new logs.
Create Reports: To generate new reports.
Critical Software Error(fault): An error which prevents an operational function from
performing as defined in applicable specifications (e.g. causes a program to stop, an unusable
product, or no product).
Data Element: A unit of data that is considered, in context, to be indivisible.
Data: The collection of datasets, products, and information provided by the CSS-Wx System.
Dataset: May be composed of several files or a time series of data that comprise a single
logical product. Examples include RUC, Icing/CIP, GOES satellite imagery, etc. This is
equivalent to the ISO 19115 “Dataset series” terminology.
Datum: In geodesy, a datum is a set of reference points on the Earth's surface against which
position measurements are made, and (often) an associated model of the shape of the earth
(reference ellipsoid) to define a geographic coordinate system.
Degraded State: The CSS-Wx System Node is no longer operating as designed, limited in
functionality, components are no longer configurable, offline, inactive, fail to meet the
operational availability criteria described IAW paragraph 3.2.1.3 of this specification.
Design-Time Discovery: A manual search for information about weather data performed by a
user.
Detect Intrusions: To actively observe and act on malicious intrusions to System networks,
resources, and data.
Discovery: The processes through which a service consumer may search for and find services,
(generally done by providing criteria to search for against a corpus of service metadata which
service providers have provided to describe their services).
Disk Usage measurements : Information from physical disk counters used to monitor CSS-
Wx Server disk I/O, paging, and disk activity.
Display – A computer display is a thin panel output device (Plasma Display Panel, Cathode


                                             B-5
                            CSS-Wx System Specification Document
                                              Draft

Ray Tube, and Liquid Crystal Display) of which an electronic input of information is supplied.
Encode/Decode message: To construct or de-construct (or to convert, or translate from one
form to another) a message for delivery based on the type and size of the message data (e.g.
binary data may be encoded and decoded).
End Point: An association between a fully-specified concrete protocol and/or a data format
and a network address, often specified by a URI that is used to communicate with an instance
of a web service.
Enforce Wx Security: To exert authority over the ability to allow or deny access to systems,
resources, and data.
Ensure Wx Data Message Confidentiality: To examine and validate that privacy was
maintained during the communications process.
Enterprise Service Bus: The ESB provides a highly distributed, event-driven Service Oriented
Architecture (SOA) that combines Message Oriented Middleware (MOM), Web services,
intelligent routing based on content, and XML data transformation.
Error Event Types: The occurrence of an exception to expected behavior. Examples include
component failures, message transmission errors, unknown subscribers, unknown providers,
application errors, etc.
Error: Part of the CSS-Wx System state which may lead to a failure.
Extensibility: The CSS-Wx System is designed to include mechanisms for expanding and/or
enhancing the CSS-Wx System with new capabilities without having to make major changes to
the CSS-Wx System architecture.
Failure: Occurs when the observed system behavior differs from the expected one. Note that
the reference is the expected behavior, not the specification, since even the spec could be false.
Fault: A condition that causes a functional unit to fail to perform its required function.
Federated Discovery: To enable searching for metadata across multiple linked discovery
mechanisms, such as a registry/repository.
Federated Registries: A group of individual metadata registry instances that operate
independently yet are linked to allow for cross-organizational data discovery.
Federated: A number of individual components that are linked to virtually form a single,
centralized unit, within which each component keeps some internal autonomy.
Filter Wx Data Geospatially: To create a subset of weather data from a set of weather data
using geographic or spatial parameters.
Filter Wx Data Temporally: To create a subset of weather data from a set of weather data
using time parameters.
Filtering: The capability of extracting a subset of data from a weather dataset.
Flight Level: A level of constant atmospheric pressure related to a reference datum of 29.92
inches of mercury. Each is stated in three digits that represent hundreds of feet. For example,
flight level (FL) 250 represents a barometric altimeter indication of 25,000 feet, FL 255, an
indication of 25,500 feet.
Full Operational State: The CSS-Wx Node is operating as designed, supporting full
functionality within pre-defined performance thresholds.
Generate Alerts: To supply a notification that a problem with the CSS-Wx System has
occurred
Geo-referenced map image: A subset of non-gridded data that consists of maps that are
generally rendered in a pictorial format such as PNG, GIF, or JPEG, or occasionally as vector-
based graphical elements in Scalable Vector Graphics (SVG) or Web Computer Graphics


                                               B-6
                           CSS-Wx System Specification Document
                                             Draft

Metafile (WebCGM) formats. (Reference: OpenGIS® Web Map Server Implementation
Specification OGC 06-042, Version 1.3.0). Also known as Map Data.
Geospatial 2-D Polygons: Any two-dimensional polygon of regular or irregular shape.
Geospatial 3-D Polygon: A three-dimensional polygon of regular or irregular shape.
Geospatial Circle: A two-dimensional plane of a circumscribed circle.
Geospatial Cylinder: A three-dimensional volume of a geometric shape that has parallel sides
and a circular cross-section.
Geospatial Line Segment: A portion of a straight line connected by any two geospatial points.
Geospatial Line: Any two geospatial points connected by a line segment.
Geospatial Point: Any point in space defined by a user-specified latitude, longitude, and
altitude.
Geospatial Volume: A bounded three-dimensional space that could occur anywhere and could
extend from the surface of the Earth and above.
Government Furnished Equipment: Property that is acquired directly by the government and
then made available to the contractor for use.
Gridded Data: Data that are represented as an N-dimensional (1 or more dimensions)—
typically regularly spaced—grid of data values. For example, a vertical profile or a series of
aircraft observations are a 1-dimensional grid. A national radar composite without vertical
information may be represented as a 2-dimensional (latitude/longitude) grid. The same radar
composite with vertical information may be represented as a 3-dimensional grid.
(latitude/longitude/altitude above the surface).
Hardware Fault : A hardware failure. Hardware failures occur most frequently in moving
mechanical parts, such as fans and disk drives.
Horizontal Cross-Section: The (x,y) plane.
Horizontal Scalability - Additional CSS-Wx System Nodes can be added to accommodate
additional load.
Inherent Availability (Ai) - The maximum availability theoretically within the capabilities of
the CSS-Wx System or constituent piece.
Input: Data entered into, or the process of entering data into, an information processing system
or any of its parts for storage or processing.
Inspect Wx Data: To validate the message data to check against un-needed modification.
Interchangeability: Equipment and parts supplied by the Contractor that are interchangeable
or replaceable.
Internal NAS: FAA side of firewall
Java: A programming language
Lambert Conformal Conic Projection: A type of conformal map in which features on a
sphere are projected onto a cone. The cone can either be tangent to the sphere, for which
contact is along one circle, or pass through the sphere, for which contact is along two circles.
Latency: Latency is defined as the time CSS-Wx processes a weather product. It is measured
from the time a weather product file is presented to the CSS-Wx input interface to the time
CSS-Wx places the processed product at its output interface. If multiple CSS-Wx nodes are
used to process a weather product file then the processing time of all of the involved CSS-Wx
nodes (that are in series) constitutes the latency time for the operation.
Latitude/Longitude Projection: A projection that plots latitude and longitude degree
coordinates as if they were Y and X coordinates.


                                              B-7
                            CSS-Wx System Specification Document
                                              Draft

Latitude: The location north or south in reference to the equator, which is designated at zero
(0) degrees. Lines of latitude are parallel to the equator and circle the globe. The North and
South poles are at 90 degrees North and South latitude.
Longitude: The location east or west in reference to the Prime Meridian, which is designated
as zero (0) degrees longitude. The distance between lines of longitude is greater at the equator
and smaller at the higher latitudes, intersecting at the earth's North and South Poles. Time
zones are correlated to longitude.
Lookup Exact Wx Keyword Match: To search for semantically equivalent entries according
to a parameterized request.
Lookup Inexact Wx Keyword Match: To search for semantically similar entries according to
a parameterized request.
Maintainability - A characteristic of design and installation that is expressed as the probability
that an item will be retained in, or restored to a specified condition within a given period of
time, when the maintenance is performed in accordance with prescribed procedures and
resources.
Maintenance mode: The CSS-Wx System Node executes corrective or preventive
maintenance commands. The Node is offline.
Map Data: See Geo-Referenced Map Image.
Map Projection: A map projection is any method of representing the surface of a sphere or
other shape on a plane.
Mean Time between Failures (MTBF) – The measure of time between failures is computed
by dividing the total operating hours by the number of failures.
Mean Time to Repair (MTTR) - The Mean Time to Repair period includes all time necessary
to localize, repair, test, and restore a failed system/unit to normal operating conditions, divided
by the total number of failures experienced by that system.
Mediate SOA Protocol: To apply intermediary transforming functions to SOA protocol for
transport (e.g. JMS to HTTP Web proxy).
Mediate Wx Messages: To apply intermediary transforming functions to messages between
providers and consumers.
Memory Usage measurements: Information from the memory counters used to isolate CSS-
Wx Server memory usage.
Mercator Projection: A cylindrical map projection with a linear scale that is constant in all
directions around any point preserving the angles and the shapes of small objects, the Mercator
projection distorts the size and shape of large objects, as the scale increases from the Equator
to the poles, where it becomes infinite.
Messaging Channel: A Messaging channel to which messages are forwarded and from which
many receivers can get a message.
Metadata: Structured information that describes, explains, locates, or otherwise makes it
easier to retrieve, use, or manage an information resource. Metadata are often called “data
about data.”
Modify Wx Metadata Subscriptions: To change existing subscriptions.
Modify Wx Metadata: To change the weather metadata description.
Computer Monitor – A computer monitor is comprised of the display device, circuitry and
enclosure.
NAD83: North American Datum of 1983.
Named: A distinctive, predefined designation of some aspect of the NAS or other commonly


                                               B-8
                            CSS-Wx System Specification Document
                                              Draft

recognized points, lines, areas, and volumes, such as the designation of an approach fix (e.g.,
SPLAT), an airport (e.g., ORD), an airway (e.g., V484), special use airspace (e.g., 104A), an
airway intersection (e.g., BORED), TRACON airspace (e.g., Northern California TRACON),
Kansas, etc.
NAS Projection (NAS Plane, NAS System Plane): A stereographic map projection
coordinate system used to represent aircraft or weather position data on controllers' displays for
En-Route and Oceanic Air Traffic Control in the National Airspace System (NAS). The map
projection is formed by placing a map image plane tangent to the earth's surface at a location
called the Point of Tangency. Target position data are converted from geodetic earth
coordinates to conformal spherical coordinates followed by a conformal stereographic
projection process whereby conformal spherical coordinates are converted to Cartesian
Coordinates onto the tangential map image plane. This conversion process results in a highly
accurate placement of 3-dimensional target positions onto a-2 dimensional display surface.
Each Air Route Traffic Control Center (ARTCC) has its own unique NAS system plane which
is defined by the ARTCC's adapted Point of Tangency and the radius of the Conformal Sphere.
NetCDF4: Network Common Data Form Version 4 is a set of software libraries and self-
describing, machine-independent data formats that support the creation, access, and sharing of
array-oriented scientific data.
Non-Critical Software Fault: An error which degrades the performance of an operational
function as defined in applicable specifications and for which a reasonable alternative work-
around solution exists.
Non-gridded Data: Data that does not fall into the category of gridded data. Non-gridded
weather data are also referred to as features. Examples of non-gridded data formats are text,
BUFR, and geo-referenced map images (e.g., GIF, JPEG).
Notify Wx Metadata Subscribers: Forward alerts to subscribers when Metadata Updates are
made (based on subscriber-defined parameters).
Offline Maintenance: The operational mode where a System Node is limited to performing
maintenance. The computer system can be either powered or unpowered depending on the
maintenance being performed. When taking the computer system offline, you remove the
computer from controlling a whole system. The computer is limited to interfacing with only a
single system, such as a display system or a peripheral system, to perform controlled tests or a
diagnostic to test itself. In the offline mode, you can perform preventive and corrective
maintenance.
Open Standard: A recognized national or international platform-independent standard that is
developed collaboratively through due process, is vendor neutral, and does not rely on
commercial intellectual property.
Open System: a system that employs modular design, uses widely supported and consensus
based standards for its key interfaces, and has been subjected to successful V&V tests to ensure
the openness of its key interfaces" (per the DoD OSJTF).
Operating mode: The CSS-Wx System Node executes routine administrative commands and
functions. Start-up activities are subsumed by the operating mode. The CSS-Wx System Node
is online and is a subset of Operational State or Degraded State, depending on conditions.
Operational Mode: The CSS-Wx System Node executes routine administrative commands
and functions. Start-up activities are subsumed by the operating mode. The CSS-Wx System
Node is online and is a subset of Operational State or Degraded State, depending on
conditions.



                                               B-9
                           CSS-Wx System Specification Document
                                            Draft

Operational State: The CSS-Wx System Node is operating as designed, supporting full
functionality, components are configured, online, and active, meeting operational availability
criteria described IAW paragraph 3.2.1.3 of this specification.
Output: Data transferred out of, or the process by which an information processing system or
any of its parts transfers data out of, that system or part.
Performance Statistics: Metrics based on throughput, reliability, availability, latency,
response time, and data accuracy that help to gauge the efficiency of System operations.
Performance Threshold Values: See Performance Threshold.
Performance Threshold: A value or set of values that is/are used to determine when The
CSS-Wx System is not meeting its defined operational efficiency.
Persistent Storage: Physical data storage available for online retrieval.
Playback: To play previously recorded CSS-Wx System data for off-line analysis.
Point: A single location on the dimensionless geospatial location.
Polar Radar Projection: TBD
Portability: The portability of application software may be achieved by installing program
files to the next operating system upgrade or reverting back to the previous operating system
revision located on the same hardware platform. When porting back or forth between
operating system revisions functional and performance requirements should not be adversely
impacted.
Precondition: A state or condition that is required to be true before an action can be
successfully invoked.
Predefined Filtering Query: A stored request to filter weather data by a defined set of
parameters. This stored request is discoverable for reuse.
Preventive Maintenance - Maintenance actions performed in an attempt to retain an item in a
specified condition by providing systematic inspection, detection, and prevention of incipient
failure.
Previous Baseline: One version of an CSS-Wx System element (hardware, software) back
from the current version.
Prioritize Messaging: To deliver messages based on the critical nature of the underlying
message (e.g., high importance message are delivered before low importance messages).
Priority Routing: A mechanism to send messages based on a pre-defined order of precedence
when network problems occur.
Privileged User: A user that has administrative rights on the System.
Process Wx Data Response: To prepare a response for the consumer.
Process Wx Request: To perform operations related to request protocol and specifications that
messages use (e.g. HTTP, REST or SOAP SOA protocol engine).
Process Wx Response: To perform operations related to response protocol and specifications
that messages use. (For example, HTTP, REST or SOAP SOA protocol engine).
Product category: A type of weather product; categories include weather mosaics,
observations and alerts.
Product refresh: When the latest update to weather product replaces an older update of a
weather product.
Product Update Cycles: The pre-defined frequency for product refresh.
Protocol: A formal set of conventions governing the format and control of interaction among
communicating functional units.
Publish between One-to-Many: To deliver messages between one provider and many


                                            B-10
                            CSS-Wx System Specification Document
                                              Draft

receivers.
Publish between Point-to-Point: To deliver messages between one provider and one receiver.
Publish Wx Messages: To push messages to consumers that have subscribed for messages.
Quality of Service: The ability to provide different priority to different applications, users, or
data flows, or to guarantee and manage a certain level of performance to a data flow.
Quantize Wx Data: To create new data by grouping a range of values to a single number,
code, or classification from an existing product or dataset.
Queue Messaging Channel: A Messaging channel to which messages are forwarded and from
which a receiver can get a message.
Ready Mode: An CSS-Wx System Node is available, configured as required, and ready for
activation (hot stand-by). Ready Mode is a subset of Operational State.
Record/Recording: To capture the system data for playback and analysis. Record and
playback functions support system testing activities.
Reduce Geographic Resolutions: To increase the horizontal spacing between grid points
which decreases the size of the data file.
Reduce Radar Reflectivity Resolutions: To decrease the amount vertical spacing radar
sweeps through quantization.
Reformat Gridded Data into netCDF4: To rearrange the weather data into a predefined
gridded data format.
Reformat netCDF4 into Legacy Gridded Data Format: To rearrange CF-netCDF4
formatted weather data into a format that’s usable by a legacy System.
Reformat Non-Gridded Data into WXXM: To rearrange the weather data into a predefined
non-gridded data format.
Reformat WXXM into Legacy Non-Gridded Data Format: To rearrange WXXM formatted
weather data into a format that’s usable by a legacy System.
Registry: An enabling infrastructure that uses a formal registration process to store, catalog,
and manage metadata relevant to the services. A registry supports the search, identification,
and understanding of resources, as well as query capabilities. (FAA-STD-064)
Reliability - CSS-Wx is a repairable systems that must operate continuously, therefore,
reliability is expressed as the probability that the CSS-Wx System will perform a required
function under specific conditions for a stated period of time. CSS-Wx is expressed as the raw
Mean Time between Failures (MTBF) value, in hours.
Reliable Messaging: The delivery of the message to the consumer is guaranteed
Remove Wx Data: To eliminate the existence of weather data from where it is stored.
Remove Wx Metadata Subscriptions: To eliminate a subscription for notifications on
weather metadata updates (upon request)
Remove Wx Metadata: To eliminate stored weather metadata.
Replay: The ability to recreate the response to a request for information. The goal is to
replicate the original response for accident investigation purposes.
Response Time: In real-time system such as CSS-Wx, the response time of a thread is defined
as the time elapsed between the time the Wx data becomes available to CSS-Wx for execution,
plus the time the Wx data completes its delivery to the consuming system, plus the time a
receipt acknowledgement is received by CSS-Wx.
Retrieve Gridded Wx Data: To query a data provider for gridded formatted data.
Retrieve Image Wx Data: To query a data provider for Image formatted data.
Retrieve Non-Gridded Wx Data: To query a data provider for non-gridded formatted data


                                              B-11
                            CSS-Wx System Specification Document
                                               Draft

Role: A predefined set of rules establishing the allowed interactions between a service
consumer and the service.
Role-Based Access Control (RBAC): A form of identity-based access control where The
CSS-Wx System entities that are identified and controlled are functional positions in an
organization or process.
Routing Message: To route messages based on data found in the message (e.g. content based
routing of DEX or Camel in FUSE).
Runtime Discovery: Automated weather data lookup performed by CSS-Wx System nodes.
Scalability: The ability of a system or network to handle increasing and/or decreasing amounts
of work performed without degrading operational performance of the CSS-Wx System.
Sector: An air traffic sector is a specific area of airspace defined by lateral and vertical limits.
Secure Boundary: To defend the outer edges of the CSS-Wx System as it is defined from
unauthorized access.
Secure Messages: To protect message data from un-intended or malicious modifications
between the sending and the receiving system.
Security Information and Event Management: A computerized tool used to provide real-
time monitoring, centralized storage, interpretation of logs or events, and historical reporting of
information security incidents from networks, servers, systems, and applications.
Service Adaptor: A software component that translates formats and communication protocols
between a legacy system and a SOA system (such as the CSS-Wx System).
Service Level Agreement (SLA): The SLA establishes the acceptable performance values
related to outages, restoration times, availability, response time and latency.
Service Levels: Measures the probability that all customer orders arriving within a given time
interval will be completely delivered.
Service Oriented Architecture (SOA): A paradigm for organizing and utilizing distributed
capabilities that may be under the control of different ownership domains. A SOA provides a
uniform means to offer, discover, interact with and use capabilities to produce desired effects
consistent with measurable preconditions and expectations.
Service Thread: Service threads are strings of systems that support one or more service/
capabilities to a user or specialist.
Shutdown: A deliberate, but sudden and abrupt, termination of System components and/or
nodes.
Software Fault: The cause of an error during the execution of a program, attributable to
software, of failure of the software to perform as designed.
Sort Wx Metadata Lookup Results: To organize weather metadata search results based on
user-defined criteria in search command.
Sounding: A vertical profile of atmospheric properties over a specific location.
Standard Atmospheric Pressure: Unit of Pressure defined as equal to 29.92inHg or
1013.25mb
Stereographic Projection: A type of conformal map in which features on a sphere are
projected onto a plane tangent to the sphere
Stop: To halt the execution of a process.
Store Logs: To preserve logs for future use.
Store Reports: To preserve reports for future use.
Store Wx Data: To record weather data for use within 24 hours.
Store Wx Metadata: To record weather metadata.


                                               B-12
                           CSS-Wx System Specification Document
                                            Draft

Subscribe To Queue Messaging: To register consumer for receiving data from queue (also
called Point-to-Point) messaging channel.
Subscribe To Topic Messaging: To register consumer for receiving data from topic (also
called Publish/Subscribe Channel or Brokered Notification) messaging channel.
Subscribe Wx Consumer: To register consumer for receiving data as it becomes available
Subscribe: Register for services, products and datasets.
Subset: The data returned by a filtering capability.
Synchronize Wx Metadata: To ensure that for each unique product/dataset that the weather
metadata are identical—across all its components and across participating agencies.
System Configuration: The set-up of all computer hardware and software parameters and
values that affect the CSS-Wx System node operations, connectivity and interoperability of
CSS-Wx and interfacing systems.
System Events: System events include, but are not limited to, the following:
        CSS-Wx System log-on, log-off, and all unsuccessful log-on attempts with three or
        more times in 15 minutes;
        System state and mode changes;
        Hardware, software, and communications errors detected;
        Problems with the timeliness of products (as determined by products exceeding
        latencies or expiration times);
        Changes to field settable adaptation;
        Changes to CSS-Wx System Node configuration.
System Mode: A System Mode is the method or manner in which the CSS-Wx System Node
performs work. CSS-Wx Nodes perform work in the following operational mode: an operating
Mode, a maintenance Mode, and a safe Mode.
System Node State: A System Node State describes the condition from which an CSS-Wx
System Node operates. The state of an CSS-Wx System Node is determined by observable,
measurable system parameters. An CSS-Wx System Node is considered to be in one of the
following System States: Operational State, Degraded State and Catastrophic State.
Taxonomy: A controlled list of values by which to categorize or classify objects. (FAA-STD-
064)
Three -dimensional Objects: A shape defined by (x,y,z) points.
Threshold: The measurable pre-defined parameter value or range of values within which The
CSS-Wx System function is expended to perform.
Throughput: The volume of data that flows through a networked device.
Topic Messaging Channel: A Messaging channel to which messages are forwarded and from
which many receivers can get a message.
Trajectory: The path followed by an object moving through space.
Transform: To convert data to a common weather data format.
Transform Wx Map Projections: To perform a cartographic re-projection from one
projection type to another.
Two-dimensional Line: A line defined by (x,y,) points.
User Access Permissions: The attributes that allow a user to retrieve weather data.
User: Human or software application that accesses the system. The rights and privileges of the
user are defined under the principle of least privilege.
Verify Wx Message Integrity: To examine and validate that the weather data message was


                                            B-13
                                  CSS-Wx System Specification Document
                                                    Draft

       not maliciously modified in transit or at rest.
       Vertical Cross-Section: The (x,z) plane.
       Vertical Scalability - The CSS-Wx System Nodes are reconfigured with components such as
       processors, random access memory, and storage to change work performed and still meet
       operational requirements.
       Web Feature Service: A service standard developed by the Open Geospatial Consortium that
       encompasses a standard protocol for accessing feature-based (typically non-gridded) data.
       Web Service Description Language (WSDL): A mechanism to associate semantic
       annotations with Web services that are described using Web Service Description Language.
       Web Service Modeling: Ontology (WSMO) WSMO is an ontology for describing various
       aspects related to Semantic Web services. See http://www.wsmo.org/.
       Web Services Notification: a group of specifications related to the WS-Resource framework
       that allows event driven programming between web services
       Web Service: A self-describing, self-contained, modular unit of software application logic that
       provides defined business functionality. Web services are consumable software services that
       typically include some combination of business logic and data. (FAA Order 1375.1d)
       WGS 84: WGS 84 is the World Geodetic System of 1984.
       WXXM: Weather Information Exchange Model, is a UML-based structural definition for the
       exchange of information. It defines a common vocabulary for exchanging weather information
       between organizations.
1159




                                                    B-14
                                 CSS-Wx System Specification Document
                                                Draft

1160   APPENDIX C           VERIFICATION REQUIREMENTS TRACEABILITY
1161     MATRIX
1162   <insert VRTM into final version>
1163
1164
1165
1166




                                                C-15
                                  CSS-Wx System Specification Document
                                                      Draft


1167   APPENDIX D           REQUIREMENTS NUMBERING BREAKDOWN
1168   The numbering used in the tables above are intended to create unique objects identifiers for
1169   requirements. These numbers provide a trace to the CSS-Wx Functional Hierarchy and CSS-Wx
1170   Program Requirements. Below is a summary translation to the requirements numbering. For a
1171   comprehensive breakdown, please see EA product XXXXX (CSS-Wx Functional Hierarchy
1172   [SV4-4??]). Note that some categories may not be used.
1173
             R.1 Functional Requirement
           R.1.1 Weather Discovery Management Requirement
           R.1.2 Weather Data Management Requirement
           R.1.3 Weather Service Management Requirement
           R.1.4 Weather Security Management Requirement
           R.1.5 Weather Messaging Requirement
             R.2 Performance Requirement
             R.3 Physical Integration Requirement
             R.4 Functional Integration Requirement
             R.5 Human Integration Requirement
             R.6 Physical Security Requirement
             R.7 In-Service Support Requirement
             R.8 Test and Evaluation Requirement
             R.9 Implementation and Transition Requirement
            R.10 Quality Assurance Requirement
            R.11 Configuration Management Requirement
            R.12 In-Service Management Requirement
            R.13 System Safety Requirement

1174




                                                      D-16

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:1
posted:11/26/2012
language:Unknown
pages:97