Difference: GppaWorkflow (1 vs. 17)

Revision 17
18 Oct 2012 - Main.FangfangYu
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

GSICS Procedure for Product Acceptance (GPPA) Workflow

Line: 85 to 85
 

GPPA Exempt Clauses from Demo to Pre-Operational Phase

Changed:
<
<
1. Normally, positive comments from at least two potential product users are needed.  If insufficient feedback is received during one year period, GCC will make the suggestion to the EP based on the GPAT's review comments.

2. In case of incomplete documentation that are not considered to jeopardize product quality by the GPAT and external users,  GCC will make the suggestion to the EP based on the GPAT and users‘ feedback.   However, all the required documentations shall be completed and submitted for review purpose in the pre-operational phase.
>
>
1. If insufficient feedback is received from the beta-testers outside the GSICS algorithm development community during one year test period, GCC will make the suggestion to the EP based on the GPAT's review comments. The product provider(s) should systematically seek external feedback.
 
Added:
>
>
2. In case of incomplete documentation that are not considered to jeopardize product quality, GCC will make the suggestion to the EP based on the GPAT and users‘ feedback. However, all the required documentations shall be completed and submitted for review purpose in the pre-operational phase.
 

Pre-operational Phase

Revision 16
12 Jun 2012 - Main.FangfangYu
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

GSICS Procedure for Product Acceptance (GPPA) Workflow

Line: 83 to 83
 
    • Who: GCC Director in consultation with the GPAT
    • Due: Within one year of the product entering the Demonstration Phase
Added:
>
>

GPPA Exempt Clauses from Demo to Pre-Operational Phase

1. Normally, positive comments from at least two potential product users are needed.  If insufficient feedback is received during one year period, GCC will make the suggestion to the EP based on the GPAT's review comments.

2. In case of incomplete documentation that are not considered to jeopardize product quality by the GPAT and external users,  GCC will make the suggestion to the EP based on the GPAT and users‘ feedback.   However, all the required documentations shall be completed and submitted for review purpose in the pre-operational phase.
 

Pre-operational Phase

  1. Send notification and GPAT Product recommendations to the Executive Panel regarding the Product.
Revision 15
21 Jul 2011 - Main.RobertIacovazzi
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

GSICS Procedure for Product Acceptance (GPPA) Workflow

Line: 110 to 110
 
    • Who: GCC Director
    • Due: One week following the GPAT review.
Changed:
<
<
META FILEATTACHMENT attachment="GSICS_GCC_GPPA_V02.1.pdf" attr="" comment="GSICS Procedure for Product Acceptance" date="1273024888" name="GSICS_GCC_GPPA_V02.1.pdf" path="GSICS_GCC_GPPA_V02.1.pdf" size="355032" stream="IO::File=GLOB(0xb0fcec0)" tmpFilename="/usr/tmp/CGItemp32640" user="RobertIacovazzi" version="1"
META FILEATTACHMENT attachment="GSICS_GCC_GPAF_V01.2.doc" attr="" comment="GSICS Product Acceptance Form" date="1273025834" name="GSICS_GCC_GPAF_V01.2.doc" path="GSICS_GCC_GPAF_V01.2.doc" size="241152" stream="IO::File=GLOB(0x94041e4)" tmpFilename="/usr/tmp/CGItemp32994" user="RobertIacovazzi" version="1"
>
>
META FILEATTACHMENT attachment="GSICS_GCC_GPPA_V02.1.pdf" attr="" comment="GSICS Procedure for Product Acceptance" date="1311254509" name="GSICS_GCC_GPPA_V02.1.pdf" path="GSICS_GCC_GPPA_V02.1.pdf" size="231469" user="RobertIacovazzi" version="3"
META FILEATTACHMENT attachment="GSICS_GCC_GPAF_V01.2.doc" attr="" comment="GSICS Product Acceptance Form" date="1311254089" name="GSICS_GCC_GPAF_V01.2.doc" path="GSICS_GCC_GPAF_V01.2.doc" size="356352" user="RobertIacovazzi" version="2"
 
META FILEATTACHMENT attachment="GSICS_GCC_GPERF_V01.0.doc" attr="" comment="GSICS Product External Review Form" date="1294235394" name="GSICS_GCC_GPERF_V01.0.doc" path="GSICS_GCC_GPERF_V01.0.doc" size="152064" stream="IO::File=GLOB(0x9a4a784)" tmpFilename="/usr/tmp/CGItemp29900" user="RobertIacovazzi" version="1"
Revision 14
14 Jan 2011 - Main.RobertIacovazzi
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

GSICS Procedure for Product Acceptance (GPPA) Workflow

Related documents:
  • GSICS Procedure for Product Acceptance (GPPA), version 2.1 UPDATED
  • GSICS Product Acceptance Form (GPAF), version 1.2 UPDATED
Changed:
<
<
  • GSICS Product External Review Form GPERF), version 1.0 UPDATED
>
>
  • GSICS Product External Review Form (GPERF), version 1.0 UPDATED
 

Product Submission Phase

Revision 13
05 Jan 2011 - Main.RobertIacovazzi
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

GSICS Procedure for Product Acceptance (GPPA) Workflow

Related documents:
Changed:
<
<
  • GSICS Procedure for Product Acceptance, version 2.1 UPDATED
  • GSICS Product Acceptance Form, version 1.2 UPDATED
>
>
  • GSICS Procedure for Product Acceptance (GPPA), version 2.1 UPDATED
  • GSICS Product Acceptance Form (GPAF), version 1.2 UPDATED
  • GSICS Product External Review Form GPERF), version 1.0 UPDATED
 

Product Submission Phase

Line: 111 to 112
 

META FILEATTACHMENT attachment="GSICS_GCC_GPPA_V02.1.pdf" attr="" comment="GSICS Procedure for Product Acceptance" date="1273024888" name="GSICS_GCC_GPPA_V02.1.pdf" path="GSICS_GCC_GPPA_V02.1.pdf" size="355032" stream="IO::File=GLOB(0xb0fcec0)" tmpFilename="/usr/tmp/CGItemp32640" user="RobertIacovazzi" version="1"
META FILEATTACHMENT attachment="GSICS_GCC_GPAF_V01.2.doc" attr="" comment="GSICS Product Acceptance Form" date="1273025834" name="GSICS_GCC_GPAF_V01.2.doc" path="GSICS_GCC_GPAF_V01.2.doc" size="241152" stream="IO::File=GLOB(0x94041e4)" tmpFilename="/usr/tmp/CGItemp32994" user="RobertIacovazzi" version="1"
Added:
>
>
META FILEATTACHMENT attachment="GSICS_GCC_GPERF_V01.0.doc" attr="" comment="GSICS Product External Review Form" date="1294235394" name="GSICS_GCC_GPERF_V01.0.doc" path="GSICS_GCC_GPERF_V01.0.doc" size="152064" stream="IO::File=GLOB(0x9a4a784)" tmpFilename="/usr/tmp/CGItemp29900" user="RobertIacovazzi" version="1"
Revision 12
05 May 2010 - Main.RobertIacovazzi
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

GSICS Procedure for Product Acceptance (GPPA) Workflow

Related documents:
Changed:
<
<
  • GSICS Procedure for Product Acceptance, version 2.0
  • GSICS Product Acceptance Form, version 1.1 UPDATED
>
>
  • GSICS Procedure for Product Acceptance, version 2.1 UPDATED
  • GSICS Product Acceptance Form, version 1.2 UPDATED
 

Product Submission Phase

Line: 12 to 12
 
    • Who: Product provider
  1. Submit the GPAF and preliminary ATBD for review to the GSICS Product Acceptance Team (GPAT) via the GSICS Coordination Center (GCC) Deputy.
    • Who: Product provider
Changed:
<
<
  1. Determine if the GPAF is filled out correctly, and make a consensus decision regarding whether or not the product scope is within the GSICS domain?
>
>
  1. Determine if the GPAF is filled out correctly and decide if the product theoretical basis is adequate and the product scope is within the GSICS domain.
 
    • Who: GPAT
    • Due: 6 weeks after the GPAF submission
  1. GPAT feedback given to the Product provider.
Line: 21 to 21
 
  1. Upload a sample file to a GSICS data server if GPAT feedback is affirmative.
    • Who: Product provider, GDWG Chairman
    • Due: One week after GPAT feedback regarding GPAF form submission
Changed:
<
<
  1. Determine if the sample file follows the GSICS netCDF and file naming conventions?
>
>
  1. Determine if the sample file follows the GSICS netCDF and file naming conventions.
 
    • Who: GDWG Chairman
    • Due: 2 weeks after successful product sample file upload
  1. Remediate any GPAF issues according to the GPAT feedback.
Line: 109 to 109
 
    • Who: GCC Director
    • Due: One week following the GPAT review.
Changed:
<
<
META FILEATTACHMENT attachment="GSICS_GCC_GPPA_V02.0.pdf" attr="" comment="GSICS Procedure for Product Acceptance" date="1269628222" name="GSICS_GCC_GPPA_V02.0.pdf" path="GSICS_GCC_GPPA_V02.0.pdf" size="283938" stream="IO::File=GLOB(0xafcc2fc)" tmpFilename="/usr/tmp/CGItemp14908" user="AleksandarJelenak" version="1"
META FILEATTACHMENT attachment="GSICS_GCC_GPAF_V01.1.doc" attr="" comment="GSICS Product Acceptance Form" date="1269905152" name="GSICS_GCC_GPAF_V01.1.doc" path="GSICS_GCC_GPAF_V01.1.doc" size="256000" stream="IO::File=GLOB(0x9da1fb0)" tmpFilename="/usr/tmp/CGItemp10877" user="AleksandarJelenak" version="1"
>
>
META FILEATTACHMENT attachment="GSICS_GCC_GPPA_V02.1.pdf" attr="" comment="GSICS Procedure for Product Acceptance" date="1273024888" name="GSICS_GCC_GPPA_V02.1.pdf" path="GSICS_GCC_GPPA_V02.1.pdf" size="355032" stream="IO::File=GLOB(0xb0fcec0)" tmpFilename="/usr/tmp/CGItemp32640" user="RobertIacovazzi" version="1"
META FILEATTACHMENT attachment="GSICS_GCC_GPAF_V01.2.doc" attr="" comment="GSICS Product Acceptance Form" date="1273025834" name="GSICS_GCC_GPAF_V01.2.doc" path="GSICS_GCC_GPAF_V01.2.doc" size="241152" stream="IO::File=GLOB(0x94041e4)" tmpFilename="/usr/tmp/CGItemp32994" user="RobertIacovazzi" version="1"
Revision 11
03 May 2010 - Main.RobertIacovazzi
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

GSICS Procedure for Product Acceptance (GPPA) Workflow

Line: 8 to 8
 

Product Submission Phase

Changed:
<
<
  1. Fill out Sections I, II, III.1.A.1, and III.1.A.2 of the GSICS Product Acceptance Form (GPAF).
>
>
  1. Fill out Sections I, II, III.1.A.1, and III.1.A.2 of the GSICS Product Acceptance Form (GPAF). Also, fill out Section III.1.B (ATBD) of the GPAF, but during the Submission Phase the ATBD needs only to be a preliminary version. The ATBD could be a journal article, technical memorandum or other documentation of the method used to make the product.
 
    • Who: Product provider
Changed:
<
<
  1. Submit the GPAF for review to the GSICS Product Acceptance Team (GPAT) via the GSICS Coordination Center (GCC) Deputy.
>
>
  1. Submit the GPAF and preliminary ATBD for review to the GSICS Product Acceptance Team (GPAT) via the GSICS Coordination Center (GCC) Deputy.
 
    • Who: Product provider
  1. Determine if the GPAF is filled out correctly, and make a consensus decision regarding whether or not the product scope is within the GSICS domain?
    • Who: GPAT
Changed:
<
<
    • Due: 2 weeks after the GPAF submission
>
>
    • Due: 6 weeks after the GPAF submission
 
  1. GPAT feedback given to the Product provider.
    • Who: GCC Director
Changed:
<
<
    • Due: 3 weeks from GPAF submission
>
>
    • Due: 7 weeks from GPAF submission
 
  1. Upload a sample file to a GSICS data server if GPAT feedback is affirmative.
    • Who: Product provider, GDWG Chairman
    • Due: One week after GPAT feedback regarding GPAF form submission
Line: 26 to 26
 
    • Due: 2 weeks after successful product sample file upload
  1. Remediate any GPAF issues according to the GPAT feedback.
    • Who: Product provider, GCC Director
Changed:
<
<
    • Due: Within 24 days after sending GPAT feedback to the Product provider
>
>
    • Due: Within 20 days after sending GPAT feedback to the Product provider
 
  1. Once all issues are resolved, the product enters the Demonstration Phase.
    • Who: GCC Director in consultation with the GPAT
Changed:
<
<
    • Due: Within 45 days of the GPAF submission
>
>
    • Due: Within 90 days of the GPAF submission
 

Demonstration Phase

Revision 10
14 Apr 2010 - Main.RobertIacovazzi
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

GSICS Procedure for Product Acceptance (GPPA) Workflow

Line: 12 to 12
 
    • Who: Product provider
  1. Submit the GPAF for review to the GSICS Product Acceptance Team (GPAT) via the GSICS Coordination Center (GCC) Deputy.
    • Who: Product provider
Changed:
<
<
  1. Upload a sample file to a GSICS data server.
    • Who: Product provider, GDWG Chairman
    • Due: Coordinated with the GPAF form submission
  2. Determine if the GPAF is filled out correctly?
>
>
  1. Determine if the GPAF is filled out correctly, and make a consensus decision regarding whether or not the product scope is within the GSICS domain?
 
    • Who: GPAT
    • Due: 2 weeks after the GPAF submission
Deleted:
<
<
  1. Determine if the sample file follows the GSICS netCDF and file naming conventions?
    • Who: GDWG Chairman
    • Due: 2 weeks after successful product sample file upload
 
  1. GPAT feedback given to the Product provider.
    • Who: GCC Director
    • Due: 3 weeks from GPAF submission
Added:
>
>
  1. Upload a sample file to a GSICS data server if GPAT feedback is affirmative.
    • Who: Product provider, GDWG Chairman
    • Due: One week after GPAT feedback regarding GPAF form submission
  2. Determine if the sample file follows the GSICS netCDF and file naming conventions?
    • Who: GDWG Chairman
    • Due: 2 weeks after successful product sample file upload
 
  1. Remediate any GPAF issues according to the GPAT feedback.
    • Who: Product provider, GCC Director
    • Due: Within 24 days after sending GPAT feedback to the Product provider
Line: 63 to 63
 
  1. Remediate any document or data issues according to the GPAT and user feedback.
    • Who: Product provider, GCC Director
    • Due: One month after receiving GPAT feedback
Changed:
<
<
  1. [Major milestone] Make a decision whether or not to continue the Product acceptance process.
>
>
  1. [Major milestone] Make a consensus decision whether or not to continue the Product acceptance process.
 
    • Who: GPAT
    • Due: Two weeks after the remediation process ends for the documents regarding the radiative transfer models and cal/val supporting measurements
  1. Notify the Executive Panel on the status of the Product's acceptance process.
Revision 9
31 Mar 2010 - Main.AleksandarJelenak
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

GSICS Procedure for Product Acceptance (GPPA) Workflow

Line: 110 to 110
 
    • Due: One week following the GPAT review.

META FILEATTACHMENT attachment="GSICS_GCC_GPPA_V02.0.pdf" attr="" comment="GSICS Procedure for Product Acceptance" date="1269628222" name="GSICS_GCC_GPPA_V02.0.pdf" path="GSICS_GCC_GPPA_V02.0.pdf" size="283938" stream="IO::File=GLOB(0xafcc2fc)" tmpFilename="/usr/tmp/CGItemp14908" user="AleksandarJelenak" version="1"
Deleted:
<
<
META FILEATTACHMENT attachment="GSICS_ProductAcceptanceForm_Updated.doc" attr="" comment="GSICS Product Acceptance Form" date="1269904937" name="GSICS_ProductAcceptanceForm_Updated.doc" path="GSICS_GCC_GPAF_V01.1.doc" size="256000" stream="IO::File=GLOB(0xa47baa4)" tmpFilename="/usr/tmp/CGItemp15583" user="AleksandarJelenak" version="2"
 
META FILEATTACHMENT attachment="GSICS_GCC_GPAF_V01.1.doc" attr="" comment="GSICS Product Acceptance Form" date="1269905152" name="GSICS_GCC_GPAF_V01.1.doc" path="GSICS_GCC_GPAF_V01.1.doc" size="256000" stream="IO::File=GLOB(0x9da1fb0)" tmpFilename="/usr/tmp/CGItemp10877" user="AleksandarJelenak" version="1"
Revision 8
29 Mar 2010 - Main.AleksandarJelenak
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

GSICS Procedure for Product Acceptance (GPPA) Workflow

Related documents:
  • GSICS Procedure for Product Acceptance, version 2.0
Changed:
<
<
  • GSICS Product Acceptance Form, version 1.0
>
>
  • GSICS Product Acceptance Form, version 1.1 UPDATED
 

Product Submission Phase

Line: 110 to 110
 
    • Due: One week following the GPAT review.

META FILEATTACHMENT attachment="GSICS_GCC_GPPA_V02.0.pdf" attr="" comment="GSICS Procedure for Product Acceptance" date="1269628222" name="GSICS_GCC_GPPA_V02.0.pdf" path="GSICS_GCC_GPPA_V02.0.pdf" size="283938" stream="IO::File=GLOB(0xafcc2fc)" tmpFilename="/usr/tmp/CGItemp14908" user="AleksandarJelenak" version="1"
Changed:
<
<
META FILEATTACHMENT attachment="GSICS_ProductAcceptanceForm_Updated.doc" attr="" comment="GSICS Product Acceptance Form" date="1269628995" name="GSICS_ProductAcceptanceForm_Updated.doc" path="GSICS_ProductAcceptanceForm_Updated.doc" size="242176" stream="IO::File=GLOB(0x8834b28)" tmpFilename="/usr/tmp/CGItemp10566" user="AleksandarJelenak" version="1"
>
>
META FILEATTACHMENT attachment="GSICS_ProductAcceptanceForm_Updated.doc" attr="" comment="GSICS Product Acceptance Form" date="1269904937" name="GSICS_ProductAcceptanceForm_Updated.doc" path="GSICS_GCC_GPAF_V01.1.doc" size="256000" stream="IO::File=GLOB(0xa47baa4)" tmpFilename="/usr/tmp/CGItemp15583" user="AleksandarJelenak" version="2"
META FILEATTACHMENT attachment="GSICS_GCC_GPAF_V01.1.doc" attr="" comment="GSICS Product Acceptance Form" date="1269905152" name="GSICS_GCC_GPAF_V01.1.doc" path="GSICS_GCC_GPAF_V01.1.doc" size="256000" stream="IO::File=GLOB(0x9da1fb0)" tmpFilename="/usr/tmp/CGItemp10877" user="AleksandarJelenak" version="1"
Revision 7
29 Mar 2010 - Main.RobertIacovazzi
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

GSICS Procedure for Product Acceptance (GPPA) Workflow

Line: 8 to 8
 

Product Submission Phase

Changed:
<
<
  1. Fill out Sections I, II, III.2.A.1, and III.2.A.2 of the GSICS Product Acceptance Form (GPAF).
>
>
  1. Fill out Sections I, II, III.1.A.1, and III.1.A.2 of the GSICS Product Acceptance Form (GPAF).
 
    • Who: Product provider
  1. Submit the GPAF for review to the GSICS Product Acceptance Team (GPAT) via the GSICS Coordination Center (GCC) Deputy.
    • Who: Product provider
Line: 42 to 42
 
  1. Notify GSICS users and invite feedback from them.
    • Who: GCC Director
    • Due: As soon as routine upload is completed and the file retention policy is resolved.
Changed:
<
<
  1. Complete documents associated with GPAF Sections III.1.A (ATBD) and III.1.B (product traceability to standards) and submit them to the GCC Director.
>
>
  1. Complete documents associated with GPAF Sections III.1.B (ATBD) and III.1.C (product traceability to standards) and submit them to the GCC Director.
 
    • Who: Product provider
    • Due: Three months after entering the Demonstration phase
  1. Examine the submitted documents (ATBD and product traceability to standards).
Line: 51 to 51
 
  1. Remediate any document issues according to the GPAT and user feedback.
    • Who: Product provider, GCC Director
    • Due: One month after receiving GPAT feedback
Changed:
<
<
  1. Complete documents associated with GPAF Sections III.2.B (radiative transfer models) and III.2.C (cal/val supporting measurements).
>
>
  1. Complete documents associated with GPAF Sections III.2.A (radiative transfer models) and III.2.B (cal/val supporting measurements).
 
    • Who: Product provider
    • Due: Six months after entering the Demonstration phase
  1. Collect and disseminate user feedback regarding product's data usability and format
Line: 93 to 93
 
  1. GCC Director notifies the Product provider about the Executive Panel feedback.
    • Who: GCC Director
    • Due: Two weeks after receiving feedback from the Executive Panel
Changed:
<
<
  1. Complete documents associated with GPAF Sections III.2.D (Product version control plan), III.3.B (operations and distribution plan), and III.3.C (data user's guide) and submit the documents to the GCC.
>
>
  1. Complete documents associated with GPAF Sections III.2.C (Analysis software documentation), III.2.D (Product version control plan), III.3.B (operations and distribution plan), and III.3.C (data user's guide) and submit the documents to the GCC.
 
    • Who: Product provider
    • Due: Three months after entering the Pre-operational phase
  1. Examine the submitted documents (product version control plan, operations and distribution plan, and data user's guide).
Revision 6
26 Mar 2010 - Main.AleksandarJelenak
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

GSICS Procedure for Product Acceptance (GPPA) Workflow

Added:
>
>
Related documents:
  • GSICS Procedure for Product Acceptance, version 2.0
  • GSICS Product Acceptance Form, version 1.0
 

Product Submission Phase

  1. Fill out Sections I, II, III.2.A.1, and III.2.A.2 of the GSICS Product Acceptance Form (GPAF).
Line: 104 to 108
 
  1. GCC Director notifies the Executive Panel that the product has satisfied all the requirements for entering the Operational Phase.
    • Who: GCC Director
    • Due: One week following the GPAT review.
Added:
>
>

META FILEATTACHMENT attachment="GSICS_GCC_GPPA_V02.0.pdf" attr="" comment="GSICS Procedure for Product Acceptance" date="1269628222" name="GSICS_GCC_GPPA_V02.0.pdf" path="GSICS_GCC_GPPA_V02.0.pdf" size="283938" stream="IO::File=GLOB(0xafcc2fc)" tmpFilename="/usr/tmp/CGItemp14908" user="AleksandarJelenak" version="1"
META FILEATTACHMENT attachment="GSICS_ProductAcceptanceForm_Updated.doc" attr="" comment="GSICS Product Acceptance Form" date="1269628995" name="GSICS_ProductAcceptanceForm_Updated.doc" path="GSICS_ProductAcceptanceForm_Updated.doc" size="242176" stream="IO::File=GLOB(0x8834b28)" tmpFilename="/usr/tmp/CGItemp10566" user="AleksandarJelenak" version="1"
Revision 5
17 Mar 2010 - Main.RobertIacovazzi
Line: 1 to 1
 
META TOPICPARENT name="WebHome"
Changed:
<
<

GPPA Workflow

>
>

GSICS Procedure for Product Acceptance (GPPA) Workflow

 

Product Submission Phase

Changed:
<
<
  1. Fill out Sections I, II, III.2.A.1, and III.2.A.2 of the GPAF.
>
>
  1. Fill out Sections I, II, III.2.A.1, and III.2.A.2 of the GSICS Product Acceptance Form (GPAF).
 
    • Who: Product provider
Changed:
<
<
  1. Submit the GPAF for review.
>
>
  1. Submit the GPAF for review to the GSICS Product Acceptance Team (GPAT) via the GSICS Coordination Center (GCC) Deputy.
 
    • Who: Product provider
  1. Upload a sample file to a GSICS data server.
    • Who: Product provider, GDWG Chairman
    • Due: Coordinated with the GPAF form submission
Changed:
<
<
  1. Is the GPAF filled out correctly?
    • Who: GSICS Product Acceptance Team (GPAT)
    • Due: 2 weeks after the form submission
  2. Sample file follows the GSICS netCDF and file naming conventions?
>
>
  1. Determine if the GPAF is filled out correctly?
    • Who: GPAT
    • Due: 2 weeks after the GPAF submission
  2. Determine if the sample file follows the GSICS netCDF and file naming conventions?
 
    • Who: GDWG Chairman
    • Due: 2 weeks after successful product sample file upload
Changed:
<
<
  1. GPAT feedback given to the product provider.
>
>
  1. GPAT feedback given to the Product provider.
 
    • Who: GCC Director
    • Due: 3 weeks from GPAF submission
  1. Remediate any GPAF issues according to the GPAT feedback.
Changed:
<
<
    • Who: GCC Director, Product provider
>
>
    • Who: Product provider, GCC Director
 
    • Due: Within 24 days after sending GPAT feedback to the Product provider
Changed:
<
<
  1. Once all issues are resolved, the product enters the Demonstration phase.
>
>
  1. Once all issues are resolved, the product enters the Demonstration Phase.
 
    • Who: GCC Director in consultation with the GPAT
    • Due: Within 45 days of the GPAF submission

Demonstration Phase

Changed:
<
<
  1. Notify the Executive Panel about the product entering the Demonstration phase.
>
>
  1. Notify the Executive Panel about the Product entering Demonstration Phase.
 
    • Who: GCC Director
Changed:
<
<
    • Due: Two weeks upon the product entering the Demonstration phase.
  1. Arrange for routine upload to a GSICS data server and agree on file retention policy.
>
>
    • Due: Two weeks after the Product enters Demonstration Phase.
  1. Arrange for routine upload of the Product to a GSICS data server and agree on file retention policy.
 
    • Who: GDWG Chairman, GRWG Chairman, and Product provider
    • Due: One month after entering the Demonstration phase
Changed:
<
<
  1. Notify GSICS users and invite feedback.
>
>
  1. Notify GSICS users and invite feedback from them.
 
    • Who: GCC Director
Changed:
<
<
    • Due: As soon as routine upload and file retention is resolved.
  1. Complete Sections III.1.A (ATBD) and III.1.B (product traceability to standards) of the GPAF and submit it to the GCC.
>
>
    • Due: As soon as routine upload is completed and the file retention policy is resolved.
  1. Complete documents associated with GPAF Sections III.1.A (ATBD) and III.1.B (product traceability to standards) and submit them to the GCC Director.
 
    • Who: Product provider
    • Due: Three months after entering the Demonstration phase
Changed:
<
<
  1. Examine the submitted documents (ATBD and product traceability).
>
>
  1. Examine the submitted documents (ATBD and product traceability to standards).
 
    • Who: GPAT and product users
    • Due: One month after GCC received the documents
Changed:
<
<
  1. Remediate any documents issues according to the GPAT and user feedback.
>
>
  1. Remediate any document issues according to the GPAT and user feedback.
 
    • Who: Product provider, GCC Director
    • Due: One month after receiving GPAT feedback
Changed:
<
<
  1. Complete Sections III.2.B (radiative transfer models) and III.2.C (cal/val supporting measurements) of the GPAF.
>
>
  1. Complete documents associated with GPAF Sections III.2.B (radiative transfer models) and III.2.C (cal/val supporting measurements).
 
    • Who: Product provider
    • Due: Six months after entering the Demonstration phase
  1. Collect and disseminate user feedback regarding product's data usability and format
    • Who: Product users, GCC Director
    • Due: Six months after entering the Demonstration phase
Changed:
<
<
  1. Examine the submitted documents (ATBD and product traceability) and user feedback.
>
>
  1. Examine the submitted documents (radiative transfer models and cal/val supporting measurements).
 
    • Who: GPAT
    • Due: One month after GCC received the documents
Changed:
<
<
  1. Remediate any documents or data issues according to the GPAT and user feedback.
>
>
  1. Remediate any document or data issues according to the GPAT and user feedback.
 
    • Who: Product provider, GCC Director
Changed:
<
<
    • Due: One month after receiving GPAT and user feedback
  1. [Major milestone] Make a decision whether or not to continue the product acceptance process.
>
>
    • Due: One month after receiving GPAT feedback
  1. [Major milestone] Make a decision whether or not to continue the Product acceptance process.
 
    • Who: GPAT
Changed:
<
<
    • Due: Two weeks after the remediation process ended
  1. Notify the Executive Panel on the status of the product's acceptance process.
>
>
    • Due: Two weeks after the remediation process ends for the documents regarding the radiative transfer models and cal/val supporting measurements
  1. Notify the Executive Panel on the status of the Product's acceptance process.
 
    • Who: GCC Director
Changed:
<
<
    • Due: Two weeks following the GPAT decision on the product's acceptance process.
  1. Complete and submit Section III.3.A (product quality) of the GPAF.
>
>
    • Due: Two weeks following the GPAT decision on the Product's acceptance process.
  1. Complete and submit Section III.3.A (Product quality) of the GPAF.
 
    • Who: Product provider
    • Due: Ten months after entering the Demonstration phase
Changed:
<
<
  1. Examine the submitted document (product quality).
>
>
  1. Examine the submitted Product quality document.
 
    • Who: GPAT
Changed:
<
<
    • Due: One month after GCC received the document
>
>
    • Due: One month after GCC receives the document
 
  1. Remediate any document issues according to the GPAT feedback.
    • Who: Product provider, GCC Director
    • Due: One month after receiving GPAT feedback
Changed:
<
<
  1. Once all issues are resolved, the product enters the Pre-operational phase.
>
>
  1. Once all issues are resolved, the Product enters the Pre-operational Phase.
 
    • Who: GCC Director in consultation with the GPAT
Changed:
<
<
    • Due: Within one year of the product entering the Demonstration phase
>
>
    • Due: Within one year of the product entering the Demonstration Phase
 

Pre-operational Phase

Changed:
<
<
  1. Send notification and GPAT recommendations to the Executive Panel regarding the new product.
>
>
  1. Send notification and GPAT Product recommendations to the Executive Panel regarding the Product.
 
    • Who: GCC Director
Changed:
<
<
    • Due: Two weeks after the product enters the Pre-operational phase.
  1. Executive Panel review of the GPAT recommendation. Executive Panel feedback regarding the product sent to the GCC Director.
>
>
    • Due: Two weeks after the Product enters the Pre-operational Phase.
  1. Executive Panel review of the GPAT recommendations. Executive Panel feedback regarding the product sent to the GCC Director.
 
    • Who: GSICS Executive Panel
    • Due: Six weeks after being notified
Changed:
<
<
  1. GCC Director notifies the product provider about the Executive Panel.
>
>
  1. GCC Director notifies the Product provider about the Executive Panel feedback.
 
    • Who: GCC Director
    • Due: Two weeks after receiving feedback from the Executive Panel
Changed:
<
<
  1. Complete Sections III.2.D (product version control plan), III.3.B (operations and distribution plan), and III.3.C (data user's guide) of the GPAF and submit the documents to the GCC.
>
>
  1. Complete documents associated with GPAF Sections III.2.D (Product version control plan), III.3.B (operations and distribution plan), and III.3.C (data user's guide) and submit the documents to the GCC.
 
    • Who: Product provider
    • Due: Three months after entering the Pre-operational phase
  1. Examine the submitted documents (product version control plan, operations and distribution plan, and data user's guide).
Line: 100 to 100
 
    • Due: One month after receiving feedback
  1. GPAT reviews the remediation material and decides if the requirements are now satisfied. Sends final recommendation to the GCC Director.
    • Who: GPAT and GCC Director
Changed:
<
<
    • Due: Thee weeks following conclusion of the remediation period.
  1. GCC Director notifies the Executive Panel that the product has satisfied all the requirements for entering the Operational phase.
>
>
    • Due: Thee weeks following conclusion of the document remediation period.
  1. GCC Director notifies the Executive Panel that the product has satisfied all the requirements for entering the Operational Phase.
 
    • Who: GCC Director
    • Due: One week following the GPAT review.
\ No newline at end of file
Revision 4
12 Mar 2010 - Main.AleksandarJelenak
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

GPPA Workflow

Line: 10 to 10
 
    • Who: Product provider
  1. Upload a sample file to a GSICS data server.
    • Who: Product provider, GDWG Chairman
Changed:
<
<
    • Due: Corrdinated with the GPAF form submission
>
>
    • Due: Coordinated with the GPAF form submission
 
  1. Is the GPAF filled out correctly?
    • Who: GSICS Product Acceptance Team (GPAT)
    • Due: 2 weeks after the form submission
  2. Sample file follows the GSICS netCDF and file naming conventions?
Changed:
<
<
    • Who: GDWG Chairmain
>
>
    • Who: GDWG Chairman
 
    • Due: 2 weeks after successful product sample file upload
  1. GPAT feedback given to the product provider.
    • Who: GCC Director
Line: 24 to 24
 
    • Who: GCC Director, Product provider
    • Due: Within 24 days after sending GPAT feedback to the Product provider
  1. Once all issues are resolved, the product enters the Demonstration phase.
Changed:
<
<
    • Who: GCC Director in consultion with the GPAT
>
>
    • Who: GCC Director in consultation with the GPAT
 
    • Due: Within 45 days of the GPAF submission

Demonstration Phase

Added:
>
>
  1. Notify the Executive Panel about the product entering the Demonstration phase.
    • Who: GCC Director
    • Due: Two weeks upon the product entering the Demonstration phase.
 
  1. Arrange for routine upload to a GSICS data server and agree on file retention policy.
    • Who: GDWG Chairman, GRWG Chairman, and Product provider
    • Due: One month after entering the Demonstration phase
Line: 47 to 50
 
  1. Complete Sections III.2.B (radiative transfer models) and III.2.C (cal/val supporting measurements) of the GPAF.
    • Who: Product provider
    • Due: Six months after entering the Demonstration phase
Changed:
<
<
  1. Collect and disseminate user feedback regarding product's data useability and format
>
>
  1. Collect and disseminate user feedback regarding product's data usability and format
 
    • Who: Product users, GCC Director
    • Due: Six months after entering the Demonstration phase
  1. Examine the submitted documents (ATBD and product traceability) and user feedback.
Line: 59 to 62
 
  1. [Major milestone] Make a decision whether or not to continue the product acceptance process.
    • Who: GPAT
    • Due: Two weeks after the remediation process ended
Added:
>
>
  1. Notify the Executive Panel on the status of the product's acceptance process.
    • Who: GCC Director
    • Due: Two weeks following the GPAT decision on the product's acceptance process.
 
  1. Complete and submit Section III.3.A (product quality) of the GPAF.
    • Who: Product provider
    • Due: Ten months after entering the Demonstration phase
Line: 69 to 75
 
    • Who: Product provider, GCC Director
    • Due: One month after receiving GPAT feedback
  1. Once all issues are resolved, the product enters the Pre-operational phase.
Changed:
<
<
    • Who: GCC Director in consultion with the GPAT
>
>
    • Who: GCC Director in consultation with the GPAT
 
    • Due: Within one year of the product entering the Demonstration phase

Pre-operational Phase

Added:
>
>

  1. Send notification and GPAT recommendations to the Executive Panel regarding the new product.
    • Who: GCC Director
    • Due: Two weeks after the product enters the Pre-operational phase.
  2. Executive Panel review of the GPAT recommendation. Executive Panel feedback regarding the product sent to the GCC Director.
    • Who: GSICS Executive Panel
    • Due: Six weeks after being notified
  3. GCC Director notifies the product provider about the Executive Panel.
    • Who: GCC Director
    • Due: Two weeks after receiving feedback from the Executive Panel
  4. Complete Sections III.2.D (product version control plan), III.3.B (operations and distribution plan), and III.3.C (data user's guide) of the GPAF and submit the documents to the GCC.
    • Who: Product provider
    • Due: Three months after entering the Pre-operational phase
  5. Examine the submitted documents (product version control plan, operations and distribution plan, and data user's guide).
    • Who: GPAT
    • Due: One month after GCC received the documents
  6. Remediate any documentation and overall product issues following the Executive Panel and GPAT feedback.
    • Who: Product provider, GCC Director
    • Due: One month after receiving feedback
  7. GPAT reviews the remediation material and decides if the requirements are now satisfied. Sends final recommendation to the GCC Director.
    • Who: GPAT and GCC Director
    • Due: Thee weeks following conclusion of the remediation period.
  8. GCC Director notifies the Executive Panel that the product has satisfied all the requirements for entering the Operational phase.
    • Who: GCC Director
    • Due: One week following the GPAT review.
  \ No newline at end of file
Revision 3
08 Mar 2010 - Main.AleksandarJelenak
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

GPPA Workflow

Product Submission Phase

Changed:
<
<
  1. Fill out Sections I, II, III.2.A.1, and III.2.A.2 of the GPAP form.
>
>
  1. Fill out Sections I, II, III.2.A.1, and III.2.A.2 of the GPAF.
 
    • Who: Product provider
Changed:
<
<
  1. Submit the GPAP form for review.
>
>
  1. Submit the GPAF for review.
 
    • Who: Product provider
  1. Upload a sample file to a GSICS data server.
    • Who: Product provider, GDWG Chairman
    • Due: Corrdinated with the GPAF form submission
Changed:
<
<
  1. Is the GPAP form filled out correctly?
>
>
  1. Is the GPAF filled out correctly?
 
    • Who: GSICS Product Acceptance Team (GPAT)
    • Due: 2 weeks after the form submission
  1. Sample file follows the GSICS netCDF and file naming conventions?
Line: 23 to 23
 
  1. Remediate any GPAF issues according to the GPAT feedback.
    • Who: GCC Director, Product provider
    • Due: Within 24 days after sending GPAT feedback to the Product provider
Changed:
<
<
  1. Once all issues are resolved, the product enters the Demonstration Mode.
>
>
  1. Once all issues are resolved, the product enters the Demonstration phase.
 
    • Who: GCC Director in consultion with the GPAT
    • Due: Within 45 days of the GPAF submission
Changed:
<
<

Demonstration Mode

>
>

Demonstration Phase

 

  1. Arrange for routine upload to a GSICS data server and agree on file retention policy.
Changed:
<
<
  1. Notify GSICS users and invite feedback; notify the GPAP Review Team.
  2. Complete Sections III.1.A (ATBD) and III.1.B (product traceability to standards) of the GPAP form.
  3. Complete Sections III.2.B and III.2.C of the GPAP form.
  4. Complete Section III.3.A of the GPAP form.
  5. Evaluate the user and Review Team feedback.
  6. If user/review feedback positive, enter the Pre-operational Mode.
>
>
    • Who: GDWG Chairman, GRWG Chairman, and Product provider
    • Due: One month after entering the Demonstration phase
  1. Notify GSICS users and invite feedback.
    • Who: GCC Director
    • Due: As soon as routine upload and file retention is resolved.
  2. Complete Sections III.1.A (ATBD) and III.1.B (product traceability to standards) of the GPAF and submit it to the GCC.
    • Who: Product provider
    • Due: Three months after entering the Demonstration phase
  3. Examine the submitted documents (ATBD and product traceability).
    • Who: GPAT and product users
    • Due: One month after GCC received the documents
  4. Remediate any documents issues according to the GPAT and user feedback.
    • Who: Product provider, GCC Director
    • Due: One month after receiving GPAT feedback
  5. Complete Sections III.2.B (radiative transfer models) and III.2.C (cal/val supporting measurements) of the GPAF.
    • Who: Product provider
    • Due: Six months after entering the Demonstration phase
  6. Collect and disseminate user feedback regarding product's data useability and format
    • Who: Product users, GCC Director
    • Due: Six months after entering the Demonstration phase
  7. Examine the submitted documents (ATBD and product traceability) and user feedback.
    • Who: GPAT
    • Due: One month after GCC received the documents
  8. Remediate any documents or data issues according to the GPAT and user feedback.
    • Who: Product provider, GCC Director
    • Due: One month after receiving GPAT and user feedback
  9. [Major milestone] Make a decision whether or not to continue the product acceptance process.
    • Who: GPAT
    • Due: Two weeks after the remediation process ended
  10. Complete and submit Section III.3.A (product quality) of the GPAF.
    • Who: Product provider
    • Due: Ten months after entering the Demonstration phase
  11. Examine the submitted document (product quality).
    • Who: GPAT
    • Due: One month after GCC received the document
  12. Remediate any document issues according to the GPAT feedback.
    • Who: Product provider, GCC Director
    • Due: One month after receiving GPAT feedback
  13. Once all issues are resolved, the product enters the Pre-operational phase.
    • Who: GCC Director in consultion with the GPAT
    • Due: Within one year of the product entering the Demonstration phase
 
Changed:
<
<

Pre-operational Mode

>
>

Pre-operational Phase

Revision 2
08 Mar 2010 - Main.AleksandarJelenak
Line: 1 to 1
 
META TOPICPARENT name="WebHome"
Changed:
<
<

GPAP Workflow

>
>

GPPA Workflow

 
Changed:
<
<

Development Mode

>
>

Product Submission Phase

 
Changed:
<
<
  1. Fill out Sections I, II, III.2.A.1, and III.2.A.2 of the GPAP form.
  2. Submit the GPAP form for review.
  3. Upload a sample file to a GSICS data server
  4. Is the GPAP form filled out correctly?
  5. Sample file follows the GSICS netCDF and file naming conventions?
  6. Enter the Demonstration Mode.
>
>
  1. Fill out Sections I, II, III.2.A.1, and III.2.A.2 of the GPAP form.
    • Who: Product provider
  2. Submit the GPAP form for review.
    • Who: Product provider
  3. Upload a sample file to a GSICS data server.
    • Who: Product provider, GDWG Chairman
    • Due: Corrdinated with the GPAF form submission
  4. Is the GPAP form filled out correctly?
    • Who: GSICS Product Acceptance Team (GPAT)
    • Due: 2 weeks after the form submission
  5. Sample file follows the GSICS netCDF and file naming conventions?
    • Who: GDWG Chairmain
    • Due: 2 weeks after successful product sample file upload
  6. GPAT feedback given to the product provider.
    • Who: GCC Director
    • Due: 3 weeks from GPAF submission
  7. Remediate any GPAF issues according to the GPAT feedback.
    • Who: GCC Director, Product provider
    • Due: Within 24 days after sending GPAT feedback to the Product provider
  8. Once all issues are resolved, the product enters the Demonstration Mode.
    • Who: GCC Director in consultion with the GPAT
    • Due: Within 45 days of the GPAF submission
 

Demonstration Mode

Changed:
<
<
  1. Arrange for routine upload to a GSICS data server and agree on file retention policy.
  2. Notify GSICS users and invite feedback; notify the GPAP Review Team.
  3. Complete Sections III.1.A (ATBD) and III.1.B (product traceability to standards) of the GPAP form.
  4. Complete Sections III.2.B and III.2.C of the GPAP form.
  5. Complete Section III.3.A of the GPAP form.
  6. Evaluate the user and Review Team feedback.
  7. If user/review feedback positive, enter the Pre-operational Mode.
>
>
  1. Arrange for routine upload to a GSICS data server and agree on file retention policy.
  2. Notify GSICS users and invite feedback; notify the GPAP Review Team.
  3. Complete Sections III.1.A (ATBD) and III.1.B (product traceability to standards) of the GPAP form.
  4. Complete Sections III.2.B and III.2.C of the GPAP form.
  5. Complete Section III.3.A of the GPAP form.
  6. Evaluate the user and Review Team feedback.
  7. If user/review feedback positive, enter the Pre-operational Mode.
 

Pre-operational Mode

 
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding GSICS Wiki? Send feedback