WRAPTechnical Support System

Project Update

AoH CallOctober 19, 2005

Overview

• Review of TSS and Scoping Study goals• Scoping study work completed to date• TSS design• Next steps

TSS Project Goals

• Provide a single web-based location for access and display of technical data, display of analytical results, and the reference location for related documentation to support the regional haze implementation plans.

• Provide specific analysis tools to synthesize technical and contextual data and GIS layers, conduct analyses, and store results for subregional/local/Class I area-specific regional haze planning.

• Provide the analysis and display tools for Phase 2 analyses, and the technical support documentation for WRAP region SIPs and TIPs for regional haze.

Scoping Study Goals

• Identify, understand, and refine the user/system requirements– Match products types with user needs (e.g., SIP outline)– Identify a set of case studies that illustrate the system’s use

• Explore the architectural options– Select and evaluate a candidate architecture (feasibility, available

expertise)– Revisit system requirements – changes needed?– Finalize selection: create set of documents and diagrams that

describe system architecture, team member roles• Generate a detailed project plan

– What is feasible with available time/funds?– What cannot be done at this time?– Minimum requirement: MUST support SIP preparation

• Scoping study to be completed in November 2005

Scoping Study Work Completed (1)• Consolidate the Requirements (90% complete):

– Initial requirements have been studied, refined, categorized, and prioritized

– Supplemental requirements have been suggested– Requirements have been “mapped” to products

• Identify scenarios (50% complete):– Key data products have been identified; usage scenarios are being

designed• Explore the Architectural Options (40% complete):

– GIS options (ARC/IMS and Manifold) have been evaluated with regard to functionality, maintainability, performance, and interoperability)

– Data and metadata schemas have been explored– Communication protocols (XML, HTTP, SOAP) have been

evaluated– Server software has been determined (Windows Server 2003, IIS,

SQL Server)– Implementation options have been explored

Scoping Study Work Completed (2)• Produce a Candidate Architecture (40% complete):

– Key system components have been diagrammed– Data flows have been described– Communication with a remote GIS server has been tested– Performing WMS calls from a web page has been demonstrated– Recommendations are being compiled

• Evaluate the Architecture (ongoing):– Draft architecture has been iteratively evaluated with respect to

requirements

• Rework the Architecture (ongoing):– Architecture is being refined as merited by the findings of the

scoping study (GIS interaction has been refined; database schema has been updated; recommendations for partner roles have been revised)

Scoping Study Work Completed (3)• Revisit the Requirements (90% complete):

– Requirements have been reexamined and refinements suggested

• Finalize the Logical Model of the System (50% complete):– TSS logical model is taking shape– Architectural diagrams and descriptions are being refined and will

be presented at the November meeting– Important design questions are being explored and answered

Important Ongoing TSS Questions• Do we understand the user requirements?

– Yes (to be confirmed by AoH work group, Nov 2005 – Feb 2006)• How should products and features be prioritized?

– Products that support SIP development first priority• What are the data volumes and data types expected?• How should the data be organized and accessed?• What hardware and software components will be necessary?• What GIS functionality and interactivity is required?• What primary GIS platform should we choose?

– Arc IMS and Manifold currently under review, decision not important to critical decision path

• What are the technical issues that we might confront?• What are the respective roles of the TSS development partners?• How much time will it take to develop various phases of the TSS?• Should the proposed scope be adjusted?

TSS

• Client Layer: what the user sees – data, products, tools

• Web Services Layer: the TSS Map Tool can request data from multiple Web Mapping Services (WMS) which are independent of the project databases, and may or may not reside on the TSS server

• Data Layer: The various WMS can retrieve data from multiple sources, including air quality databases, specific data products, and various GIS layers

GIS Subsystem Overview

Display Raw Data

Create Chart

Create Map

ASP .NET Page

Mapping Service Call Map Image

TSS Database Server

Database Query Formatted Data

TSS GIS Server

TSS Web Server

Chart Request

Chart ImagePage

Request

User visits a page on the TSS web site and

specifies map arguments using controls on

the web page (layers, centroid, zoom, etc.)

TSS web server executes (submits)

the appropriate ASP .NET page.

ASP .NET page requests a map from the

mapping service on the GIS server, via

HTTP GET, SOAP, or similar protocol.

The mapping service assembles the requested layers into a map image

using the specified centroid and zoom, then returns the image to the page.

The page displays the image.

1

2

3 4

5

TSS Architectural Overview:Displaying a MapThis example gives a very high-level description of the procedural steps involved in requesting, creating, and displaying a map using the proposed TSS mapping component and/or web service. Created: 10/4/2005

TSS Architecture (in development)

Next Steps

• TSS Development:– Complete Scoping Study document(s) by end of

November 2005– Present Scoping Study results at November 2005 AoH

meeting– Present draft web site at January 2006 AoH meeting

• Phase 2 Analysis:– Present draft WOE approach at November 2005 AoH

meeting– Begin to assimilate/synthesize final 2002 data/modeling

results following November 2005 AoH meeting

Review of AoH Project Schedule

Phase 2

Report