Embed Size (px)
Citation preview
November 28, 2005
GDAC User RequirementsGDAC User Requirements
Ditto - Craig’s presentation!
Maintain consistent Application and User Support among GHRSST-PP organizations
Establish the process to fulfill the Application and User Services Model
Understand the vision of GEOSS and IOOS and link their societal benefits to GHRSST-PP applications
Ditto - Craig’s presentation!
Maintain consistent Application and User Support among GHRSST-PP organizations
Establish the process to fulfill the Application and User Services Model
Understand the vision of GEOSS and IOOS and link their societal benefits to GHRSST-PP applications
November 28, 2005
GDAC Customer Relationship Management Diagram
GDAC Customer Relationship Management Diagram
Regional Data Assembly Centers/
Value Added Providers/LTSRF
ｷ Medspirationｷ NAVOCEANOｷ Bluelinkｷ JAXAｷ BLUELinkｷ MODIS ｷ MISSTｷ NODC
Data User Communities
DiscoveryData AccessKnowledge-
BuildingQueries
Applications
NOAANASA
GHRSST-PPJPL
GDAC AUSCustomer
Relationship
Reports:Data Flow, Customer
Metrics
November 28, 2005
GDAC User Requirements DocumentGDAC User Requirements Document
Purpose Document the
history, system processes and data products.
Identify key strategies and activities for Applications and User Services.
Purpose Document the
history, system processes and data products.
Identify key strategies and activities for Applications and User Services.
Draft URD (11/17/2005)
Living document Data product updates Customer Profile
updates Key Activities and
Strategies
Draft URD (11/17/2005)
Living document Data product updates Customer Profile
updates Key Activities and
Strategies
November 28, 2005
GDAC User Requirements Document Contents
GDAC User Requirements Document Contents
1. Background/Intro GHRSST-PP GDAC Data Products GDAC Data
Processing Model Master Metadata
Repository (MMR) Matchup Database
(MDB) Application and User
Services (AUS)
1. Background/Intro GHRSST-PP GDAC Data Products GDAC Data
Processing Model Master Metadata
Repository (MMR) Matchup Database
(MDB) Application and User
Services (AUS)
2. GDAC User Profiles RDAC’s LTSRF IOOS
Organization Contact info
SST Requirements Parameters,
resolution, accuracy, data formats, delivery methods.
2. GDAC User Profiles RDAC’s LTSRF IOOS
Organization Contact info
SST Requirements Parameters,
resolution, accuracy, data formats, delivery methods.
November 28, 2005
U.S. GHRSST-PP User Requirements Document
U.S. GHRSST-PP User Requirements Document
3. Consolidated User Requirements for GDAC Product coverage
(spatial and temporal)
3. Consolidated User Requirements for GDAC Product coverage
(spatial and temporal)
4. GDAC Product & Service Specifications Processing System Input Data Definitions Data Storage Data Products Data Distribution MMR Functional Req. MDB Functional Req. AUS Strategies &
Activities
4. GDAC Product & Service Specifications Processing System Input Data Definitions Data Storage Data Products Data Distribution MMR Functional Req. MDB Functional Req. AUS Strategies &
Activities
November 28, 2005
GDAC URD Next StepsGDAC URD Next Steps Update draft URD with comments from this
meeting Finalize URD and release to GHRSST-PP group Prioritize Activities, assign budget, create
action plan for the next year Today: We have a fish on the line!
How do we reel in the GLOS projects and move forward with a demonstration of GHRSST-PP data use? How do we leverage a GLOS success to move forward with other IOOS Regional Areas?
Update draft URD with comments from this meeting
Finalize URD and release to GHRSST-PP group Prioritize Activities, assign budget, create
action plan for the next year Today: We have a fish on the line!
How do we reel in the GLOS projects and move forward with a demonstration of GHRSST-PP data use? How do we leverage a GLOS success to move forward with other IOOS Regional Areas?
November 28, 2005
Mahalo Nui LoaMahalo Nui Loa
808.982.9175
808.982.9175
November 28, 2005
4.7.2 Application and User Support The goal of the US GDAC AUS is to ensure a high level of customer satisfaction through user advocacy and gain new users of diverse applications. The AUS follows a GDAC Customer Relationship Management (CRM) Plan, which guides customer support activities.
US GDAC Web Portal - develop and maintain website to facilitate access to data and information.
o Data information and access portal, unique to GHRSST-PP US GD AC (ghrsst.jpl.nasa.gov). Site was established congruently with the initial release of GD AC data (September, 2005)
o Actively m aintain frequently asked questions page. Anticipate new questions and opportunities from the comm unity and post answers expeditiously.
o Maintain data product access pages – docum entation, ftp, Aspera, data tools & services, software, known problems, what’s new, references, related links and help. Links are now available on the web page and should be updated as needed.
o Informational page about the GHRSST -PP. Web page includes a link to the ghrsst-pp page, GODAE, GOO S, etc.
o Applications page to solicit societal benefits from data use. The US GD AC can provide application information on US users. This is quite helpful in assessing where to find new users, help existing users find more use of the data and assist stakeholders with project justification. The Applications page could be organized to more emphasize the GEOSS societal benefits.
o Maintain website compliancy with NASA and First Gov policies. Provide regular 508 compliance checks and JPL docum entation number.
o Provide regular, new web content with images, news, biographies and short application stories.
o Institute an automatic subscription service for data and application news.
November 28, 2005
User Services Support - Internal and External Activities to maintain customer base and feedback.
o Populate static FAQ’s - on-going maintenance. There are currently 6 FAQ’s available in the RNT Knowledge Base.
o Receive inquiries from customers, log, provide referrals, and follow up questions with suggested FAQs to circumvent future questions, close the loop with customers. Communication channels include email, telephone, fax, and personal interaction. User support available during Pacifi c Time business hours. Web portal with FAQ’s and documentation available 24/7.
o Identify points of contacts at RDACs for customer inquiry and follow-ups. Outline and agree on a response plan to customers.
o Send data and informational announcements as needed o Maintain user database o Institute privacy policy with stakeholders and communicate to data customers o Develop collateral materials for project as needed. Facili tate branding and
presence at professional conferences, workshops, meetings, etc. Target the GHRSST-PP USA Review meeting in Miami (November 2005, User meeting in Brest (Dec 2005,) the Oceans AGU (February 2006), IOOS meetings and the 7th GHRSST-PP Science Team meeting in Boulder (March, 2006).
o Organize a GHRSST-PP US users meeting to target potential customers from IOOS RA’ s and other Application communities.
o Bridge the level of customer service between NRT data flows and Long Term Archive between NASA and NOAA. Continue planning discussions with NODC management and User Services.
ß FAQ’s ß Data lifecycle history ß Customers ß Announcements
o Solicit feedback with closed end survey from data customers. Consolidate information and analyze with the Applications trend information gathered from web page. Provide yearly or quarterly report.
o Maintain consistent application and user services with the European GHRSST-PP effort and the RDACs.
Identify mechanism to collect statistic information on communications – how many, frequency, etc.
November 28, 2005
Measures of Effectiveness and Evaluation Mechanisms
o Develop and transmit monthly reports to Stakeholders on data management activities outlined below in Evaluation Mechanisms
o Report quarterly on Applications use of data (solicited from the Applications page)
o Provide monthly analytic reports to stakeholders on customer statistics ß Number of Customers accessing data via electronic transfer, subsetting
tools ß Characterization of customers ß Number of customer interactions ß Results of closed end surveys to customers accessing data
o Provide monthly statistics on data access, availability and transfer:
ß Number of successful data transfers ß Number of data files served (volume?) ß FTP statistics
• Number o f ,Users • Number o f Files downloaded • Data volume transferred
o Provide data quality metrics ß Quantify number of customers providing feedback for validation studies
against climatologies, in-situ data, etc.
