1 / 7

External Subsetter System Configuration Management Processes Jeanne Behnke July 11, 2002

External Subsetter System Configuration Management Processes Jeanne Behnke July 11, 2002. ESS Phases. Design Phase - done Development Phase - in process HSA/HEW V1.08 EDG 3.4 ECS 6... Test Phase - in process Operational Phase - to be determined at this meeting

kslezak
Download Presentation

External Subsetter System Configuration Management Processes Jeanne Behnke July 11, 2002

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. External Subsetter SystemConfiguration ManagementProcessesJeanne BehnkeJuly 11, 2002

  2. ESS Phases • Design Phase - done • Development Phase - in process • HSA/HEW V1.08 • EDG 3.4 • ECS 6... • Test Phase - in process • Operational Phase - to be determined at this meeting • Operational/OSS Phase - Fall 2002

  3. NCR Process Steps • 1. Non-Conformance Reports (NCRs) are generated at the DAACs and at the ECS test facilities in Landover, Md. • 2. NCRs are assigned a severity (Sev). • Sev 1 means that a functional thread (in this case, external subsetting) is inoperable. • Sev 2 means that a functional thread is seriously degraded. • Sev 3 means that a functional thread • is somewhat degraded. • Sev 4 is a minor problem. • Sev 5 is an enhancement request.

  4. NCR Process Steps (continued) • 3. NCRs are prioritized by the DAACs and globally prioritized across DAACs by ESDIS/ECS. Sometimes need dates are assigned if the problem impacts an upcoming mission milestone. • 4. When an external subsetter NCR is received, ECS will assign a severity and priority and forward it to UAH. • 5. UAH will analyze and fix NCRs in priority order within their resource constraints.

  5. NCR Process Steps (continued) • 6. UAH will provide ECS with an estimated fix date on Sev 1 NCRs within 24 hours of receipt of the NCR. • 7. UAH will provide ECS with an estimated fix date on Sev 2 NCRs within a week of receipt of the NCR. • 8. UAH would coordinate directly with the DAACs to obtain additional information about an NCR, if required.

  6. NCR Process Steps (continued) • 9. UAH will coordinate with ECS to determine how NCR fixes should be packaged into external subsetter deliveries and to coordinate delivery schedules. • 10. UAH will provide a POC for the DAACs to contact if they need assistance in installing, operating, or troubleshooting external subsetter problems.

  7. NCR Process Steps (continued) • 11. Software deliveries also containing NCR fixes will include, for each NCR fix: NCR number, analysis of the problem, and a description of how it was resolved. ECS will enter this information into the NCR tracking database. After installation of the new software at the DAACs, the DAACs will verify that each NCR has been fixed and then the NCRs will be closed.

More Related