Download - 4-D Wx Data Cube Data Formats & Decoders

4-D Wx Data CubeData Formats & Decoders

Introduction & Overview

Agenda for the Week• Monday

– Logistics (host)– Introductions– Meeting Objectives (Tom & Mark)– Major Activities/Milestones Through End of FY11– FY10 IT Demonstration

• Objectives• Participants• Demonstration Plan• Demonstration Test Plan

– Product Format & Decoders• 4-D Wx Data Cube Product Overview• 4-D Wx Data Cube Decoder Overview

• Tuesday & Wednesday– Data Format & Decoder Discussions & Planning

• Thursday– General Discussion

Meeting Objectives

• Develop a plan for– proceeding with developing additional data formats: a prioritized

list with assigned organization & completion date for each– which data sets can be published as part of the FY10 IT Demo

and by whom• Discuss issues with decoders as related to the 4-D Wx

Data Cube and develop a plan with dates for resolution• Gain a mutual understanding of high-level schedule of 4-

D Wx Data Cube activities through the end of FY11• Gain a mutual understanding of objectives and current

planning status for the FY10 IT Demo• Gain an understanding of significant issues and

concerns

Major Activities/Milestones Through End of FY11

Completion Dates for Selected Activities

Metadata Guidelines, Version 2 Dec-09

4-D Wx Data Cube System Spec Dec-09

Design Review Feb-10

Version 2 of WCS and WFS RIs Jul-10

NOAA Group 1 Service Adapters Aug-10

IOC Final Version (V3) Metadata Guidelines Complete (MIT/LL) Aug-10

FAA Detailed Architecture Sep-10

FY 10 IT Demo Sep-10

FAA IOC Service Adapters Mar-11

NOAA Detailed Architecture Apr-11

Version 3 of WCS and WFS RI Apr-11

Update 1 (V4) Metadata Guidelines (MIT/LL) Aug-11

NOAA Group 2 Service Adapters Sep-11

FY 11 IT Demo Sep-11

Design Review

• The 4-D Wx Data Cube Team has decided to schedule a Cube Design Review early in CY10

• The purpose is to conduct an in depth look at all aspects of the development efforts including:– Architecture– RIs– Reg/Rep– Service Adapters

• The Design Review will be discussed this Thursday

FY10 IT Demonstration

Objectives• Utilize:

– NOAAnet & FTI to communicate between NOAA & FAA– presumed elements of operational architecture to the maximum

extent possible

• Maximize products published by NOAA & FAA• Demonstrate a SAS-like capability (manual & automatic)• Measure & report communications & processor

performance• Publish NEVS data• Implement security measures • Utilize appropriate standards

• Utilize a simulator to make requests for data in order to exercise the software

• Clearly separate non-Cube functionality from Cube functionality

• Develop our own front end (separate from ADDS)

• Develop and exercise more rigorous testing, followed by a demonstration


Other

Lessons Learned - 2009 IT Demo

Preparation (including dry-run)Description Application to FY10 IT Demo

There were too many people present at the dry-run. Permit only pertinent personnel to participate in dry-runs. Everyone is welcomed to witness Formal Demonstrations.

NWEC Lab space is too small to host everyone from Labs, NWS, and FAA.

Allocate additional space from surrounding area for general gatherings. Additionally, conference rooms will be schedule for sidebar meetings.

The time allotted for the dry-run needs to be longer than 1 day.

The FY10 dry-run will be conducted over a 3-day period. Extending the duration of the dry-run will allow for troubleshooting that may be necessary as a result of unexpected problems.

The expected test duration needs to be more accurately depicted.

The 3-day dry run will allocate time to not only troubleshoot, but also accurately determine the length of the demonstration.

The Test Plan needs to be available for Tech Center/Labs/PO comments at least a month prior to the demonstration.

ESRL/GSD will provide a draft version of the Test Plan to the Labs/PO/Tech center NLT August 1, 2010. Comments will be due on August 15, 2010. ESRL/GSD will then have until September 1, 2010 to finalize the document.

Test Plan format needs improvement. FAA will be closely involved in the development of the Test Plan throughout the year to assist with both the content and format.

The Test Plan should include Test Verification Requirements Tractability Matrix (VRTM).

Clearly defined test requirements will be included in the test plan.


Formal IT DemonstrationDescription Application to FY10 IT Demo

The Common Viewing Area was a great location for the formal demonstration.

The Common Viewing Area will be reserved for the FY10 demonstration.

The audience should have a copy of the test plan in hand for the demonstration.

A hard copy of the Test Plan (Kinko bounded) will be provided to the audience.

An additional conference room would be beneficial for the duration of the demonstration to allow for side meetings/presentations.

The Tech Center will reserve an additional conference room for the NNEW demonstration in addition to the Common Viewing Area.

The Test Plan should be displayed on the two end screens with the actual demonstration taking place on the middle screen.

As in FY09, this will be continued for FY10.

The FY10 IT Demonstration dates and schedule need to be determined in the very near future in order to reserve the necessary space.

The demonstration dates will be determined by the end of the calendar year.

A person should be the assigned scribe that notes successes, failures, action items, potential new capabilities, etc. This should be someone whose sole purpose is to basically cover all that was done in the demo and provide a written account.

One person will be in charged of noting the successes, failures, action items, key questions, etc. This person will also provide a formal write-up after the demonstration covering the points mentioned above.


Formal IT Demonstration (cont)Description Application to FY10 IT Demo

We should have a microphone for the tester (not hand held), a microphone for the technical expert that can explain what a particular test is showing and why that is important, and a microphone for the audience to use to ask questions. We may actually want to have two different microphones for the audience so that wait time is minimized.

Four microphones will be available at the demonstration. One for the “tester”, one for the “technical expert”, and two for “microphone personnel” to provide to any audience members who may have questions throughout the demonstration.

The audience’s mindset needs to be prepared before diving into the lower level nature of the test plan.

A couple of background slides will be briefed before the demo and will include the current architecture, Accomplishments for the FY09 Demo/Goals for the FY10 Demo, differentiations between NOAA and FAA contributions, weather products that will be shown in the demo, etc.

The “tester” should not be the primary speaker. A “technical speaker” should be up in front of the audience discussing what the “tester” is doing and provide technical background on the tests.

A technical person from the Labs will be in front of the audience providing commentary while the tests are being performed.

Considering the number of people that will be attending in FY10, setting standard times to ask questions may be necessary.


MiscellaneousDescription Application to FY10 IT Demo

A tour of the entire Tech Center should be provided. There is a good possibility that we’ll have more than just folks who are familiar with the Tech Center.

A tour will be offered to attendees when they first arrive at the Tech Center. This would be very good gesture on our part. The tour would show folks all that Building 300 has as well as the broader capabilities of the Tech Center.

15 minutes should be set aside before the demonstration for people to introduce themselves and their affiliations.

A list of attendees should be known a few months prior to the demonstration.

Collecting a list of attendees early will ensure that there will be enough space, ample test plans printed and binded, etc. The list of attendees will be finalized by August 1, 2010.

• Purpose: Provide a single point of reference for all aspects of the demo

• Owner: 4-D Wx Data Cube Team

• Input from: all players


Demonstration Plan

• Test Case 1: WFSRI version 2.0• Test Case 2: WCSRI version 2.0• Test Case 3: SAS• Test Case 4: NEVS• Test Case 5: Service Adapters• Test Case 6: Performance & Latency• Test Case 7: Security• Test Case 8: Standards• Regression Test:

– WFSRI version 1.0 – WCSRI version 1.0– WellFleet Registry/Repository– Standards


Notional Test Outline

FY10 IT DemonstrationProcedures Format

• Follow FAA AMS Guidelines for test document development

• Will incorporate the following:– Test step w/ expected results– Space for to indicate step completed (or Failed)– Reference requirement being tested– Sign-off sheet for each Test Case noting time/date of

completion, section for comments, signatures for Q/A and Test Conductor

1.0 Introduction: Includes Purpose and Scope

2.0 Reference Documents:

3.0 Test Description3.1 System Under Test

3.2 Interface Under Test

3.3 Test Setup

3.4 Test Equipment

3.5 Personnel

3.6 Location

Schedule


Demo Test Procedures


Demo Test Procedures (cont)4.0 Test Conduct

4.1 Safety Considerations

4.2 Requirements Under Test

4.3 Procedures

4.4 Test Data Reduction and Analysis

Appendix A – Requirement Traceability Matrix

(More information and description of each section can be found in Appendix C-6 at http://fasteditapp.faa.gov/ams/do_action?do_action=ListTOC&contentUID=20 )

http://fasteditapp.faa.gov/ams/do_action?do_action=ListTOC&contentUID=20


Program Trouble Report (PTR)• Form used to identify issues that are

encountered during testing• Each failed test steps will result in a PTR• PTR from will consist of:

– Time and Date of PTR– Test Case / Step / Page– Who generated PTR– Issue– Explanation– Resolution

• iTKO Lisa Tool– http://www.itko.com/lisa

• Progress Software Actional– http://web.progress.com/actional/

• ESRI ArcGIS• Unidata Integrated Data Viewer (IDV)

– http://www.unidata.ucar.edu/software/idv/

• NextGen Evaluation Weather Tool (NEWT)


Simulator / Tools

FY10 IT Demonstration NOAA Testbed Design

FY10 IT Demonstration NWEC Testbed Design


Milestones (requires dates)• Draft 1 of Demonstration Procedures• Draft 2 of Demonstration Procedures• Software baselined / frozen• Dry-Runs at NOAA• Draft 3 of Demonstration Procedures• Dry-Runs at FAA• Finalized Demonstration Procedures• Test Readiness Review• Formal FY10 IT Demonstration (Full Test)• Formal FY10 IT Demonstration (High-Level Test)• FY10 IT Demonstration Quick Look Report• FY10 IT Demonstration Report

Product Format & Publishing Discussion

• Formats– Some formats have been developed; others are under

development– Goal is to plan, through end of FY11, for developing

formats beyond those already completed or planned—including which organization is responsible for which product formats, and when they will be completed

• Publishing– Goal is to decide—for the FY10 Demo—which

products will be published and by whom

Decoder DiscussionWednesday, November 18

1. Scope of Decoder Discussion

2. What Decoder-Related Problems Should Be Anticipated?a. Based on experienceb. Based on foresight

3. What Standards Apply (OFCM, WMO, …)?a. Differing standards versionsb. Dealing with overlapping standards

4. Legacy Systems Transition

5. Decoder Metadata & Need for Consistency• Example: Site Identification Inconsistency

6. Rules (what is allowed, not allowed?)• Example: METAR remarks field• Example: Concatenated messages

Decoder Discussion - continuedWednesday, November 18

7. Local Tables

8. Other Decoder Challenges (Input from Group)

9. Governancea. Definition and establishment of governanceb. Leveraging existing governance bodiesc. Authoritative (oversight) and technical (execution) layers neededd. Need for ongoing interagency collaboration– a long-term activity

10. Next Steps• Very near term (e.g., FY10) and beyond FY10

Backup slides