Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This space contains:

Page Tree

ASDC
NameemailPositionNameemailPosition
Walt Baskinwalter.e.baskin@nasa.govGranule-level metadata at ASDCKaren Dragonkaren.c.dragon@jpl.nasa.govJPL PREFIRE Systems Engineer 
Susan Kizersusan.h.kizer@nasa.gov ASDC Group lead. Erin Hokanson Wagnerephokanson@wisc.eduPREFIRE Data System Manager
Ingrid Garcia-Soleraingrid.garcia-solera@nasa.govSatellite Mission Team Product OwnerKaren Michaelkaren.a.michael@nasa.govGSFC, ESDIS
Peter Piatkopeter.j.piatko@nasa.govLead developer at ASDCMary Whitemary.l.white@jpl.nasa.govPREFIRE Project Manager
Christopher Howardchristopher.k.howard@nasa.govDeveloper at ASDCBrian Drouinbrian.j.drouin@jpl.nasa.govPREFIRE Project Scientist
Wei Zhangwei.zhang-1@nasa.gov Developer at ASDCSteven Dutcher

steved@ssec.wisc.edu

SIPS
Susan Haberersusan.j.haberer@nasa.gov Metadata team leadStephanie Jones

stephanie.l.jones@jpl.nasa.gov

JPL PREFIRE V & V
Hazem Mahmoudhazem.mahmoud@nasa.gov Earth Scientist


Caroline Downeycaroline.r.downey@nasa.gov ASDC Collection level metadata coordinator



Resources

  1. netCDF ToolsUI (Unidata/UCAR) - UDunits to format units in the netCDF files
  2. CF Compliance checker
  3. HDF Product Designer
  1. Email/PDF: Assignment of the missions to ASDC by ESDIS
  2. Doc: 90-day plan document for ESDIS (within 90-days of the assignment) 
  3. Doc: Data Management Plan (DMP) between the data provider (Science Team's Data Manager) and ASDC
  4. Doc: Interface Control Document(s) (ICDs) between various entities involved
  5. Meeting: Set up regular (weekly/monthly) meetings with the science team:
    1. discuss data/file format, file naming convention,
    2. metadata content/format (UMM-C for collections, UMM-G for granules),
    3. ingest/delivery
    4. Distribution services/APIs/Subsetters
    5. Visualization: GIBS/WorldView
    6. NRT (near-real time) requirements
    7. End-to-end testing 
  6. Support the Science Team for various reviews:
    1. PDR (Preliminary Design Review),
    2. CDR (Critical DR),
    3. ORR (Operational Readiness Review)
  7. Support the Science Team for Early data access and Early adopters workshops
    1. Limited access to certain granules on CMR/EDSearch based on user-list 



Dateline

DateEventResponsibleLocation Notes
1-Dec-2023SRB membership letterPSOOneSpan esign
18-Dec-2023Safety ReviewJPLWebex
3-Jan-2024Deliver GP documents to SRBProjectmail in
4-Jan-2024Institutional Readiness To Proceed (to ORR/MRR)8XJPL / Webex
9-Jan-2024SRB Readiness Telecon (SRB chair, ESD, PM)SRBESD Teams
16-Jan-2024CoFR 3, includes ITL and TAYFEProjectJPL / Webex
17-Jan-2024SRB Chair Readiness AssessmentSRBmail in
17-Jan-2024Institutional Risk Review8XJPL / Webex
19-Jan-2024SRB Kickoff MeetingSRB?SRB only, not project
1-Feb-2024ORRSRBJPL / Webex
2-Feb-2024SRB Snapshot ReportSRBmail in1 page, expected in 24 to 48 hours
7-Feb-2024Snapshot Report BriefingESDESD Teams
14-Feb-2024Mission Integration Readiness ReviewRLRL Zoom
16-Feb-2024SRB ORR Board ReportSRBmail in
27-Feb-2024Transportation Planning ReviewProjectWebexJPL Type 3, project convened, Div38 led
5-Mar-2024Safety SurveyJPLWebex3 weeks prior to shipment of CubeSats from BCT to RL Long Beach
7-Mar-2024Delta CubeSats Pre Ship Review and MRRIRTJPL / BCT / Webex
16-Mar-2024Launch Processing Readiness ReviewRLRL Zoom
18-Mar-2024DMC (8X)8XJPL / Webex
20-Mar-2024Pre-brief to Flight/ESSP

Schwinger and Law
25-Mar-2024Pre-brief to ESD DirectorESDESD TeamsSt. Germain
25-Mar-2024CoFR (launch)OCEJPL / Webex
27-Mar-2024Final Mission Analysis Review (RL led)RLRL Zoom
28-Mar-2024KDP-E (dPMC)NASA ESDNASA and Teams?
2-Apr-2024Ship from RL Long BeachRLRL LB
24-Apr-2024Ship from BCTESSPBCT
14-May-2024Launch Readiness Review #1 (RL led)RLRL Zoom
15-May-2024Launch #1RLRL MahiaFM2
2-Jun-2024Launch Readiness Review #2 (RL led)RLRL Zoom
3-Jun-2024Launch #2RLRL MahiaFM1
19-Jun-2024PLARIRTJPL / Webex





Dates are TBD

Complete these tasks to get started

  •  Edit this home page - Click Edit in the top right of this screen to customize your Space home page
  •  Create your first page - Click the Create button in the header to get started
  •  Brand your Space - Click Configure Sidebar in the left panel to update space details and logo
  •  Set permissions - Click Space Tools in the left sidebar to update permissions and give others access

Recent space activity

Recently Updated
typespage, comment, blogpost
max5
hideHeadingtrue
themesocial

Space contributors

Contributors
modelist
scopedescendants
limit5
showLastTimetrue
orderupdate







UI Tabs
UI Tab
titleMission Documents

Key Mission Documents

DocumentOwner (Name, Org)Artifact(s) 
PLRA
https://wiki.earthdata.nasa.gov/download/attachments/31164000/PREFIRE%20PLRA%20Baseline%20Signed.pdf?version=1&modificationDate=1562958201939&api=v2
IPA
COMET: 423-ESDIS-451
DAAC Selection Memo

Data Management Plan



ICD


COMET: 423-ICD-026
MOU

GITC ICD Updates
GIBS ICD Appendix - ASDC (Working Draft) - Google Sheets
UI Tab
titleMission Milestones

Key Mission Milestones

MilestoneDateArtifact(s)Features Required to Meet Milestone

PDR

 

2 Days
CDR

 

3 Days Review
Mission Test(s)

 

PREFIRE Test plan https://wiki.earthdata.nasa.gov/display/ASDCCLOUD/PREFIRE+Test+Plan
ESDIS Review Gate (ERG)2022CUMULUS ERG 2022
End-To-End Performance Test

 

Load Testing in UAT - ASDC Cloud - Earthdata Wiki (nasa.gov)
ESDIS Production Readiness Review (PRR)

 

Ingest System CUMULUS PRR Spring 2023
ORR

-  

https://wiki.earthdata.nasa.gov/download/attachments/31164000/ESDIS04344%3AESSPO-0001%3A20171101_FINAL%20ESSPPO-0001%20Program%20Plan%20Rev%20B%2020180702.pdf?version=1&modificationDate=1701724777621&api=v2

Launch #1

 

SAT-2

Jira
serverEarthdata Ticketing System
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyIART-683

Launch #2

 

SAT-1
PLAR

 



Public Data Release

 

 

 


L0 6 collections IOC+3month

L1 IOC+6 months

L2 IOC+9 months

L3 IOC+12months


Jira
serverEarthdata Ticketing System
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyTRT-504

Jira
serverEarthdata Ticketing System
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyTRT-505

DOIs / Dataset Landing Pages / User Guides / Tutorials / Announcements through comms teams / Approach to advertising at conferences / is everything required for open science published / etc?









UI Tab
titleTechnical Factors

Technical Factors

This list of factors can impact enterprise applications, please keep this list up to date so that enterprise teams can evolve the systems and cost projections as needed.  Changes in this list should trigger re-evaluation by corresponding trains.  

FactorResponseSystems ImpactedEnterprise Change Required?
Ingest ProtocolSDTPCumulusN
Daily Volume7.84 GB / dayEDC, CMRN
Daily # of Files282 files / dayCMR, CumulusN

End of Mission Volume

2.19 TBCumulusN

Largest File Size

136 MBCumulus, EDC (egress)N

Latency Requirements

30 days L0/L1

45 days L2

12 month L3

Cumulus, CMRN

Highest burst ingest rate

<110 files/minute>Cumulus, CMR

Highest reprocessing rate

<110 files/minute>Cumulus, CMR

File Name Format

L0, L1, L2 : PREFIRE_SAT#_Level#_PRODUCT_PRODUCTVERSION_COLLECTIONVERSION_STARTUTC_PROCESSINGUTC.nc

payload filename:  prefire_0#_payload_tlm_STARTUTC_ENDUTC_CREATIONUTC.bin

bus: prefire_0#_bus_tlm_STARTUTC_ENDUTC_CREATIONUTC.csv

CumulusN
CMR Metadata Format

Granules: UMM-G

Collections: UMM-C

CMR

CMR queries needed for

ingest or reprocessing? (y/n)

Estimated Query Volume: N/A

CMRN
ORCA Integration

None, per ICD ("The PREFIRE project will have a backup of all data that is needed for reprocessing and will not be dependent upon the DAAC to provide this data.  There will also be a second backup for this data at the University of Michigan (transferred via SDTP) for the duration of the mission.")

ORCA, EDCN
LZARDS Integration

None, per ICD ("The PREFIRE project will have a backup of all data that is needed for reprocessing and will not be dependent upon the DAAC to provide this data.  There will also be a second backup for this data at the University of Michigan (transferred via SDTP) for the duration of the mission.")

LZARDSN
Hi-Res Imagery

Organization responsible for generating the imagery: GITC

Pathway for submission to GIBS: Cumulus Task + HyBig → GIBS? YES

Volume: GIBS ICD Appendix - ASDC (Working Draft) - Google Sheets

GITC, Cumulus

Jira
serverEarthdata Ticketing System
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyTRT-504

Browse Imagery

Organization responsible for generating the imagery: UW

Pathway for submission to GIBS: 

Volume: GIBS ICD Appendix - ASDC (Working Draft) - Google Sheets

GITC, Cumulus?
Level of Service Compliance

How will this mission comply with the Levels of Service Policy?  Which transformation services will be needed for the data?  (Note:  This is a complex answer, please link to a separate document as neeeded)

OPeNDAP, Harmony (and associated backend services), EGIS, TBD other Transformation tools
Custom Code Required

List code that needs to be developed specifically for this mission (e.g. ingest adapters, new Cumulus tasks, new transformation services, etc.)

HyBIG calls and SDTP

Varied
UI Tab
titleMission Requirements Traceability

Requirement Traceability

The table below summarizes the requirements for ESDIS as a part of this mission.   Of note, the team designated 'Responsible Team' is the one ultimately responsible for validating this requirement.

SourceTextResponsible TeamImplementation ApproachStatus

423-IPA-016, Rev A

Provide the ingest, archive and distribution of the PREFIRE data via ESDIS/ASDC.

ASDCStandard: Ingest/distribution via Cumulus/TEA.  Discovery via CMR.Done

423-IPA-016, Rev A

Archive and openly distribute all standard data products and corresponding metadata, scientific source code for algorithm software, coefficients and ancillary data used to generate these products during routine operations. Public release of these data shall conform to the NASA Earth Science Data and Information Policy.

ASDCStandard: Ingest/distribution via Cumulus/TEA.  Discovery via CMR.Done

423-IPA-016, Rev A

Lead the development and maintenance of an ICD between PREFIRE SDPS and ASDC.

ASDCASDC to implement and maintain ICDDone

423-IPA-016, Rev A

Implement the system interface to obtain PREFIRE forward processed and reprocessed data from PREFIRE SDPS in accordance with the established ICD between PREFIRE and ASDC.

ASDC

Cumulus will pull data from PREFIRE SDPS using the SDTP (HTTPS) interface

Done

423-IPA-016, Rev A

Capture archive and distribution metrics using the EOSDIS Metrics System. Make these metrics available to the PREFIRE Project.

ASDCStandard: Cumulus to Cloud Metrics to EMS

423-IPA-016, Rev A

Lead the development and maintenance of Product User Guide documentation and other associated dataset documents.  Make these documents publicly available to users.

ASDC

Where are these posted? ASDC website?  Linked via CMR metadata?

These documents are still v0 draft. We will post v1 on ASDC website.

Yes, the links below are from S3 bucket for documents, and they are added to CMR UAT UMM-C collection as a related URL - Hazem

https://data.asdc.earthdata.nasa.gov/asdc-prod-public/mission-support-documents/PREFIRE/PREFIRE_Data_User_Guide_Aux-Met_R00.docx 

https://data.asdc.earthdata.nasa.gov/asdc-prod-public/mission-support-documents/PREFIRE/PREFIRE_L1-L2-L3-ATBD.pdf

Ongoing

423-IPA-016, Rev A

Provide and maintain Digital Object Identifiers (DOIs) for PREFIRE data products.

ASDCStandard: Generate DOI, linked to landing page, and provide via CMR metadata

423-IPA-016, Rev A

Support the PREFIRE Project in defining the format and content of the metadata associated with all of the PREFIRE standard data products.

ASDC

423-IPA-016, Rev A

Support the PREFIRE Project by testing all interfaces between the PREFIRE SDPS and the ESDIS/ASDC including the ingest and distribution of simulated data sets.

ASDC

423-IPA-016, Rev A

Lead the development of an Appendix to the Network ICD (Reference Document 423-ICD-002) that specifies the network requirements to support forward processing and reprocessing for the mission lifetime. 

ASDC

423-IPA-016, Rev A

Participate in major PREFIRE Project Reviews as requested by the PREFIRE Project and defined in the PREFIRE integrated schedule.

ASDC
Ongoing

423-IPA-016, Rev A

Support the PREFIRE SDPS in the identification of the end-of-mission artifact collection for the long-term archive of the PREFIRE datasets.  Provide the long-term archive for the artifacts and data.

ASDC
Ongoing

423-IPA-016, Rev A

Provide User Services and assist data recipients with information related to archive and distribution functions.

ASDC
Ongoing
423-ICD-026

ASDC supports the delivery of science and metadata files via the HTTPS requests defined by the Science Data Transfer Protocol (SDTP).

  1. The subscriber requests the file contents by performing a HTTPS GET containing the fileid.
  2. The provider returns the file contents.
  3. The subscriber acknowledges the file transfer by performing a HTTPS DELETE containing the fileid of the file, and the provider records this acknowledgement.
  4. The provider removes the file from the queue for the subscriber and returns a HTTPS Success status.
ASDC
Done
423-ICD-026

Per the request of the PREFIRE project, the ASDC will maintain the most recent version (for each independent product) in its archive

ASDC
Ongoing




















UI Tab
titleESDIS Checklist

ESDIS Checklist

  • ... coming soon... the list of all the things we must do inside ESDIS to meet the ADURD / adhere to policy / etc.   This would be used both to make it easier to not skip any steps when implementing, but also as a 'gate' so that we can all agree ESDIS is ready for various phases in the mission lifecycle.  Ideally it will come with easy 'compliance checkers', for example something like 'run this command on your CMR metadata to validate that all best practices are adhered to'.  


UI Tab
titleDecision Register

Key Decision Register

Document any key decisions, especially those that may result in deviation from ESDIS requirements or architecture or have schedule or cost implications.

CriteriaOptions ConsideredOption SelectedApproval Details



(include date, location and approver name/role. e.g. OB DAAC ERG, 10/31/2023, Ted Sobchak ESDIS PM)

Hide child pages

hide-comments